Availability | SPARQL endpoint availability check for Korespondencja Emila Szramka z Janem Kuderą took 4.410743713378906e-05s
Availability | VoID file availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.4365096092224121s
Completeness | Calculation of interlinking completeness for Korespondencja Emila Szramka z Janem Kuderą took 0.3439300060272217s
Reputation | Calculation of the PageRank for Korespondencja Emila Szramka z Janem Kuderą took 0.6197047233581543s
Interlinking | Calculation of Degree of Connection for Korespondencja Emila Szramka z Janem Kuderą took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Korespondencja Emila Szramka z Janem Kuderą took 0.0008711814880371094s
Interlinking | Calculation of Clustering coefficient for Korespondencja Emila Szramka z Janem Kuderą took 0.00046825408935546875s
Believability | Calculation of trust value for Korespondencja Emila Szramka z Janem Kuderą took 1.33514404296875e-05s
INFO | --- Analysis for 0080-3626 took 4.952188730239868s
Availability | SPARQL endpoint availability check for 土地利用图 took 9.250640869140625e-05s
Availability | VoID file availability check for 土地利用图 took 3.093374729156494s
Completeness | Calculation of interlinking completeness for 土地利用图 took 0.3869776725769043s
Reputation | Calculation of the PageRank for 土地利用图 took 0.021885395050048828s
Interlinking | Calculation of Degree of Connection for 土地利用图 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for 土地利用图 took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for 土地利用图 took 3.147125244140625e-05s
Believability | Calculation of trust value for 土地利用图 took 1.811981201171875e-05s
INFO | --- Analysis for 10.12041geodata.290864223.ver1.db_ took 6.101032972335815s
Availability | SPARQL endpoint availability check for 113322 took 8.630752563476562e-05s
Availability | VoID file availability check for 113322 took 0.3466048240661621s
Completeness | Calculation of interlinking completeness for 113322 took 0.5458145141601562s
Reputation | Calculation of the PageRank for 113322 took 0.02127242088317871s
Interlinking | Calculation of Degree of Connection for 113322 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for 113322 took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for 113322 took 2.8133392333984375e-05s
Believability | Calculation of trust value for 113322 took 1.2159347534179688e-05s
INFO | --- Analysis for 11 took 4.709273815155029s
Availability | SPARQL endpoint availability check for Korepetycje Buki took 9.083747863769531e-05s
Availability | VoID file availability check for Korepetycje Buki took 0.6430840492248535s
Completeness | Calculation of interlinking completeness for Korepetycje Buki took 0.378415584564209s
Reputation | Calculation of the PageRank for Korepetycje Buki took 0.020840167999267578s
Interlinking | Calculation of Degree of Connection for Korepetycje Buki took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Korepetycje Buki took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Korepetycje Buki took 3.1948089599609375e-05s
Believability | Calculation of trust value for Korepetycje Buki took 1.3113021850585938e-05s
INFO | --- Analysis for 12323 took 2.9188501834869385s
Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 2.409193992614746s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 1.2396478652954102s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.41648054122924805s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.021135568618774414s
Interlinking | Calculation of Degree of Connection for 2000 U.S. Census in RDF (rdfabout.com) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for 2000 U.S. Census in RDF (rdfabout.com) took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 9.131431579589844e-05s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 1.0728836059570312e-05s
INFO | --- Analysis for 2000-us-census-rdf took 9.047478199005127s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 2.2816333770751953s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 1.2686357498168945s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.48288583755493164s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.022490501403808594s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 4.00543212890625e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 1.0967254638671875e-05s
INFO | --- Analysis for 2001-spanish-census-to-rdf took 7.645683288574219s
Availability | SPARQL endpoint availability check for Open Data Web took 13.162182569503784s
Availability | VoID file availability check for Open Data Web took 3.9051661491394043s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.6053526401519775s
Reputation | Calculation of the PageRank for Open Data Web took 0.02014756202697754s
Interlinking | Calculation of Degree of Connection for Open Data Web took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.719329833984375e-05s
Believability | Calculation of trust value for Open Data Web took 7.152557373046875e-06s
INFO | --- Analysis for _data.odw.tw took 19.279465675354004s
Availability | SPARQL endpoint availability check for 土地利用 took 9.369850158691406e-05s
Availability | VoID file availability check for 土地利用 took 0.0011317729949951172s
Completeness | Calculation of interlinking completeness for 土地利用 took 0.3575470447540283s
Reputation | Calculation of the PageRank for 土地利用 took 0.020617961883544922s
Interlinking | Calculation of Degree of Connection for 土地利用 took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for 土地利用 took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for 土地利用 took 2.7179718017578125e-05s
Believability | Calculation of trust value for 土地利用 took 6.9141387939453125e-06s
INFO | --- Analysis for _data1.odw.tw took 2.003760814666748s
Availability | SPARQL endpoint availability check for 土地利用模型 took 4.172325134277344e-05s
Availability | VoID file availability check for 土地利用模型 took 2.1064038276672363s
Completeness | Calculation of interlinking completeness for 土地利用模型 took 0.36220407485961914s
Reputation | Calculation of the PageRank for 土地利用模型 took 0.020626544952392578s
Interlinking | Calculation of Degree of Connection for 土地利用模型 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for 土地利用模型 took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for 土地利用模型 took 2.7179718017578125e-05s
Believability | Calculation of trust value for 土地利用模型 took 1.0967254638671875e-05s
INFO | --- Analysis for _data2.odw.tw took 5.44255256652832s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 8.726119995117188e-05s
Availability | VoID file availability check for Indian Biodiversity took 1.4297983646392822s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 1.7287077903747559s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.022011518478393555s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.7179718017578125e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.1920928955078125e-05s
INFO | --- Analysis for _https:data.bioontology.orgontologiesBOFdownloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb&download_format=rdf took 6.679533243179321s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 9.775161743164062e-05s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.0007448196411132812s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.6368887424468994s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.020588159561157227s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 2.7179718017578125e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 1.1682510375976562e-05s
INFO | --- Analysis for a-collection-of-papers-for-lrec2014-and-related-workshops took 4.078349590301514s
Availability | SPARQL endpoint availability check for ITS TEST DATASET took 8.58306884765625e-05s
Availability | VoID file availability check for ITS TEST DATASET took 1.4318830966949463s
Completeness | Calculation of interlinking completeness for ITS TEST DATASET took 0.40751028060913086s
Reputation | Calculation of the PageRank for ITS TEST DATASET took 0.020308732986450195s
Interlinking | Calculation of Degree of Connection for ITS TEST DATASET took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for ITS TEST DATASET took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for ITS TEST DATASET took 2.6702880859375e-05s
Believability | Calculation of trust value for ITS TEST DATASET took 9.298324584960938e-06s
INFO | --- Analysis for A1 took 7.086359024047852s
Availability | SPARQL endpoint availability check for SummerOlympics took 1.1942224502563477s
Availability | VoID file availability check for SummerOlympics took 0.008205652236938477s
Completeness | Calculation of interlinking completeness for SummerOlympics took 0.533052921295166s
Reputation | Calculation of the PageRank for SummerOlympics took 0.020328044891357422s
Interlinking | Calculation of Degree of Connection for SummerOlympics took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for SummerOlympics took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for SummerOlympics took 6.341934204101562e-05s
Believability | Calculation of trust value for SummerOlympics took 1.0728836059570312e-05s
INFO | --- Analysis for abc took 6.256941795349121s
Availability | SPARQL endpoint availability check for Test_m took 8.535385131835938e-05s
Availability | VoID file availability check for Test_m took 0.3603208065032959s
Completeness | Calculation of interlinking completeness for Test_m took 0.35060548782348633s
Reputation | Calculation of the PageRank for Test_m took 0.020817995071411133s
Interlinking | Calculation of Degree of Connection for Test_m took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Test_m took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Test_m took 2.956390380859375e-05s
Believability | Calculation of trust value for Test_m took 1.3113021850585938e-05s
INFO | --- Analysis for ABC took 3.2156858444213867s
Availability | SPARQL endpoint availability check for my intro took 8.392333984375e-05s
Availability | VoID file availability check for my intro took 0.4410843849182129s
Completeness | Calculation of interlinking completeness for my intro took 0.3876519203186035s
Reputation | Calculation of the PageRank for my intro took 0.020836591720581055s
Interlinking | Calculation of Degree of Connection for my intro took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for my intro took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for my intro took 3.0517578125e-05s
Believability | Calculation of trust value for my intro took 1.1920928955078125e-05s
INFO | --- Analysis for abhay_intro took 3.9392929077148438s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.2342069149017334s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.00021409988403320312s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.31284642219543457s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.02105879783630371s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 0.0001246929168701172s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 1.2636184692382812e-05s
INFO | --- Analysis for abs-linked-data took 2.5865590572357178s
Availability | SPARQL endpoint availability check for Academic Offer of UNL took 260.474422454834s
Availability | VoID file availability check for Academic Offer of UNL took 0.0008409023284912109s
Completeness | Calculation of interlinking completeness for Academic Offer of UNL took 0.3655872344970703s
Reputation | Calculation of the PageRank for Academic Offer of UNL took 0.020746946334838867s
Interlinking | Calculation of Degree of Connection for Academic Offer of UNL took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Academic Offer of UNL took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Academic Offer of UNL took 3.266334533691406e-05s
Believability | Calculation of trust value for Academic Offer of UNL took 1.2874603271484375e-05s
INFO | --- Analysis for academic-offer-of-unl took 395.1064474582672s
Availability | SPARQL endpoint availability check for AcadOnto took 9.632110595703125e-05s
Availability | VoID file availability check for AcadOnto took 0.00040221214294433594s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.5205771923065186s
Reputation | Calculation of the PageRank for AcadOnto took 0.020806312561035156s
Interlinking | Calculation of Degree of Connection for AcadOnto took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for AcadOnto took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 3.600120544433594e-05s
Believability | Calculation of trust value for AcadOnto took 1.2874603271484375e-05s
INFO | --- Analysis for acadonto took 4.783217668533325s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 9.27779507637024s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 3.2329204082489014s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.3597431182861328s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.02041029930114746s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.1682510375976562e-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.601478576660156e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 5.7220458984375e-06s
INFO | --- Analysis for acorn-sat took 35.767465353012085s
Availability | SPARQL endpoint availability check for Addgene took 5.555152893066406e-05s
Availability | VoID file availability check for Addgene took 1.465604305267334s
Completeness | Calculation of interlinking completeness for Addgene took 0.327038049697876s
Reputation | Calculation of the PageRank for Addgene took 0.020220041275024414s
Interlinking | Calculation of Degree of Connection for Addgene took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Addgene took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Addgene took 3.4809112548828125e-05s
Believability | Calculation of trust value for Addgene took 1.1682510375976562e-05s
INFO | --- Analysis for addgene took 16.58945608139038s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 0.00010371208190917969s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 1.466360092163086s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.43186330795288086s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.021488666534423828s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 9.679794311523438e-05s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 1.1682510375976562e-05s
INFO | --- Analysis for aegp-spanish-textile-and-clothing-association took 8.322454452514648s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 0.456348180770874s
Availability | VoID file availability check for AEMET metereological dataset took 0.16159486770629883s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.3242058753967285s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.021018028259277344s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 3.981590270996094e-05s
Interoperability | Check the re-using of existing vocabs for AEMET metereological dataset took 9.5367431640625e-07s
Believability | Calculation of trust value for AEMET metereological dataset took 2.7894973754882812e-05s
INFO | --- Analysis for aemet took 4.864961862564087s
Availability | SPARQL endpoint availability check for Agenda de Zaragoza took 7.104873657226562e-05s
Availability | VoID file availability check for Agenda de Zaragoza took 0.0001747608184814453s
Completeness | Calculation of interlinking completeness for Agenda de Zaragoza took 0.9158337116241455s
Reputation | Calculation of the PageRank for Agenda de Zaragoza took 0.02053666114807129s
Interlinking | Calculation of Degree of Connection for Agenda de Zaragoza took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Agenda de Zaragoza took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Agenda de Zaragoza took 3.075599670410156e-05s
Believability | Calculation of trust value for Agenda de Zaragoza took 8.58306884765625e-06s
INFO | --- Analysis for agenda-de-zaragoza took 3.573026418685913s
Availability | SPARQL endpoint availability check for AgriNepalData took 0.049627065658569336s
Availability | VoID file availability check for AgriNepalData took 0.0001544952392578125s
Completeness | Calculation of interlinking completeness for AgriNepalData took 0.36251068115234375s
Reputation | Calculation of the PageRank for AgriNepalData took 0.020717859268188477s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 7.534027099609375e-05s
Believability | Calculation of trust value for AgriNepalData took 1.239776611328125e-05s
INFO | --- Analysis for agrinepaldata took 1.952444076538086s
Availability | SPARQL endpoint availability check for AGRIS took 262.5963077545166s
Availability | VoID file availability check for AGRIS took 0.3610804080963135s
Completeness | Calculation of interlinking completeness for AGRIS took 0.4342308044433594s
Reputation | Calculation of the PageRank for AGRIS took 0.020694494247436523s
Interlinking | Calculation of Degree of Connection for AGRIS took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for AGRIS took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for AGRIS took 8.821487426757812e-05s
Believability | Calculation of trust value for AGRIS took 1.3113021850585938e-05s
INFO | --- Analysis for agris took 432.1016104221344s
Availability | SPARQL endpoint availability check for AGROVOC took 0.10278034210205078s
Availability | VoID file availability check for AGROVOC took 0.6527519226074219s
Extra | Recovery of all triples for AGROVOC took 21.05674123764038s
Performance | Total latancy measurement for AGROVOC took 0.4102962017059326s
Amount of data | Number of triples check for AGROVOC took 23.264145374298096s
Interoperability | New terms check for AGROVOC took 4.2429585456848145s
Versatility | Languages check for AGROVOC took 45.0788996219635s
Interpretability | Number of blank nodes check for AGROVOC took 15.28495454788208s
Interpretability | RDF structures check for AGROVOC took 0.06585884094238281s
Versatility | Serialization formats check for AGROVOC took 0.08050227165222168s
Availability | RDF dump link check for AGROVOC took 0.05699729919433594s
License | MR license check for AGROVOC took 0.05997467041015625s
License | HR license check for AGROVOC took 0.6467976570129395s
Amount of data | Number of property check for AGROVOC took 0.06943583488464355s
Understandability | Number of label check for AGROVOC took 27.53671908378601s
Understandability | URI regex check for AGROVOC took 0.13889098167419434s
Understandability | Vocabs check for AGROVOC took 0.06959676742553711s
Verifiability | Authors check for AGROVOC took 0.1030418872833252s
Verifiability | Publishers check for AGROVOC took 0.03518176078796387s
Performance | Throughput check for AGROVOC took 10.393171548843384s
Amount of data | Check the number of entities for AGROVOC took 8.463859558105469e-05s
Verifiability | Contribs. check for AGROVOC took 0.056218624114990234s
Interlinking | sameAs chians check for AGROVOC took 0.06612682342529297s
Interlinking | skos check for AGROVOC took 0.42168664932250977s
Interlinking | skos check for AGROVOC took 0.11279678344726562s
Timeliness | dataset update frequency check for AGROVOC took 0.09022331237792969s
Currency | Creation date check for AGROVOC took 3.852564811706543s
Currency | Modification date check for AGROVOC took 1.3741936683654785s
Rep.Conc. | URIs length for AGROVOC took 68.74952483177185s
Interoperability | New vocabularies check for AGROVOC took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for AGROVOC took 0.07171392440795898s
Accuracy | Check Functional Property for AGROVOC took 0.03520345687866211s
Accuracy | Check Inverse Functional Property for AGROVOC took 0.05791878700256348s
Accuracy | Check Empty annotation labels for AGROVOC took 20.112228631973267s
Accuracy | Check White space in annotation for AGROVOC took 2.9776997566223145s
Accuracy | Check Datatype consistency for AGROVOC took 4.470160007476807s
Consistency | Disjoint class check for AGROVOC took 0.05513954162597656s
Consistency | Check Misplaced properties for AGROVOC took 18.154682159423828s
Consistency | Check Ontology hijacking for AGROVOC took 46.856818199157715s
Consistency | Check Invalid usage of undefined properties for AGROVOC took 19.401493787765503s
Conciseness | Check Extensional conciseness for AGROVOC took 2.616556406021118s
Conciseness | Check Intensional conciseness for AGROVOC took 0.042685747146606445s
Security | Sign check for AGROVOC took 0.10332798957824707s
Availability | Check URIs Dereferenciability for AGROVOC took 5.383652925491333s
Completeness | Calculation of interlinking completeness for AGROVOC took 1.2597758769989014s
Reputation | Calculation of the PageRank for AGROVOC took 0.020391225814819336s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 0.00011038780212402344s
Interoperability | Check the re-using of existing vocabs for AGROVOC took 2.1457672119140625e-06s
Believability | Calculation of trust value for AGROVOC took 1.239776611328125e-05s
INFO | --- Analysis for agrovoc took 1272.4065330028534s
Availability | SPARQL endpoint availability check for AGROVOC took 8.034706115722656e-05s
Availability | VoID file availability check for AGROVOC took 0.00020265579223632812s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.7013466358184814s
Reputation | Calculation of the PageRank for AGROVOC took 0.021908283233642578s
Interlinking | Calculation of Degree of Connection for AGROVOC took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 5.602836608886719e-05s
Believability | Calculation of trust value for AGROVOC took 1.1205673217773438e-05s
INFO | --- Analysis for agrovoc-skos took 4.759331703186035s
Availability | SPARQL endpoint availability check for Analytics India Magazine took 1.1360948085784912s
Availability | VoID file availability check for Analytics India Magazine took 5.850143909454346s
Extra | Recovery of all triples for Analytics India Magazine took 3.321706533432007s
Performance | Total latancy measurement for Analytics India Magazine took 3.426699638366699s
Amount of data | Number of triples check for Analytics India Magazine took 1.3055717945098877s
Versatility | Languages check for Analytics India Magazine took 1.0461244583129883s
Interpretability | Number of blank nodes check for Analytics India Magazine took 1.2300982475280762s
Interpretability | RDF structures check for Analytics India Magazine took 1.2799491882324219s
Versatility | Serialization formats check for Analytics India Magazine took 1.830641508102417s
Availability | RDF dump link check for Analytics India Magazine took 1.2947320938110352s
License | MR license check for Analytics India Magazine took 1.523390769958496s
License | HR license check for Analytics India Magazine took 1.4526026248931885s
Amount of data | Number of property check for Analytics India Magazine took 1.4353647232055664s
Understandability | Number of label check for Analytics India Magazine took 1.2573816776275635s
Understandability | URI regex check for Analytics India Magazine took 3.272693634033203s
Understandability | Vocabs check for Analytics India Magazine took 1.430722713470459s
Verifiability | Authors check for Analytics India Magazine took 1.2768871784210205s
Verifiability | Publishers check for Analytics India Magazine took 1.2942962646484375s
Performance | Throughput check for Analytics India Magazine took 15.035602807998657s
Amount of data | Check the number of entities for Analytics India Magazine took 9.822845458984375e-05s
Verifiability | Contribs. check for Analytics India Magazine took 1.1629624366760254s
Interlinking | sameAs chians check for Analytics India Magazine took 1.1829452514648438s
Interlinking | skos check for Analytics India Magazine took 1.3397843837738037s
Interlinking | skos check for Analytics India Magazine took 0.9722986221313477s
Timeliness | dataset update frequency check for Analytics India Magazine took 1.437856674194336s
Currency | Creation date check for Analytics India Magazine took 3.222134828567505s
Currency | Modification date check for Analytics India Magazine took 2.518413543701172s
Rep.Conc. | URIs length for Analytics India Magazine took 2.3266091346740723s
Interoperability | New vocabularies check for Analytics India Magazine took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for Analytics India Magazine took 1.2323894500732422s
Consistency | Disjoint class check for Analytics India Magazine took 1.3895862102508545s
Consistency | Check Ontology hijacking for Analytics India Magazine took 1.255448579788208s
Consistency | Check Invalid usage of undefined properties for Analytics India Magazine took 2.453274726867676s
Conciseness | Check Extensional conciseness for Analytics India Magazine took 0.0001442432403564453s
Security | Sign check for Analytics India Magazine took 1.0282824039459229s
Completeness | Calculation of interlinking completeness for Analytics India Magazine took 0.6963329315185547s
Reputation | Calculation of the PageRank for Analytics India Magazine took 0.020227670669555664s
Interlinking | Calculation of Degree of Connection for Analytics India Magazine took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Analytics India Magazine took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Analytics India Magazine took 2.86102294921875e-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 1.1682510375976562e-05s
INFO | --- Analysis for AIM took 106.1275429725647s
Availability | SPARQL endpoint availability check for All India Survey of Higher Education took 262.13376092910767s
Availability | VoID file availability check for All India Survey of Higher Education took 0.00916910171508789s
Completeness | Calculation of interlinking completeness for All India Survey of Higher Education took 2.141831159591675s
Reputation | Calculation of the PageRank for All India Survey of Higher Education took 0.021001338958740234s
Interlinking | Calculation of Degree of Connection for All India Survey of Higher Education took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for All India Survey of Higher Education took 0.0007905960083007812s
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.2874603271484375e-05s
INFO | --- Analysis for AISHE took 266.9589228630066s
Availability | SPARQL endpoint availability check for  equipment ontology took 8.7738037109375e-05s
Availability | VoID file availability check for  equipment ontology took 0.05144453048706055s
Completeness | Calculation of interlinking completeness for  equipment ontology took 0.38921499252319336s
Reputation | Calculation of the PageRank for  equipment ontology took 0.02083444595336914s
Interlinking | Calculation of Degree of Connection for  equipment ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for  equipment ontology took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for  equipment ontology took 2.9325485229492188e-05s
Believability | Calculation of trust value for  equipment ontology took 1.1444091796875e-05s
INFO | --- Analysis for akash took 5.459041357040405s
Availability | SPARQL endpoint availability check for aksw.org Research Group dataset took 1.5064260959625244s
Availability | VoID file availability check for aksw.org Research Group dataset took 0.7949066162109375s
Completeness | Calculation of interlinking completeness for aksw.org Research Group dataset took 0.35140228271484375s
Reputation | Calculation of the PageRank for aksw.org Research Group dataset took 0.022499799728393555s
Interlinking | Calculation of Degree of Connection for aksw.org Research Group dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for aksw.org Research Group dataset took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for aksw.org Research Group dataset took 3.0994415283203125e-05s
Believability | Calculation of trust value for aksw.org Research Group dataset took 1.33514404296875e-05s
INFO | --- Analysis for aksworg took 13.47889757156372s
Availability | SPARQL endpoint availability check for AlchemyAPI took 8.559226989746094e-05s
Availability | VoID file availability check for AlchemyAPI took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for AlchemyAPI took 0.3234827518463135s
Reputation | Calculation of the PageRank for AlchemyAPI took 0.020981788635253906s
Interlinking | Calculation of Degree of Connection for AlchemyAPI took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for AlchemyAPI took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for AlchemyAPI took 3.170967102050781e-05s
Believability | Calculation of trust value for AlchemyAPI took 1.1205673217773438e-05s
INFO | --- Analysis for alchemyapi took 4.887064695358276s
Availability | SPARQL endpoint availability check for Alexandria Digital Library (ADL) Gazetteer took 392.9123818874359s
Availability | VoID file availability check for Alexandria Digital Library (ADL) Gazetteer took 262.1440255641937s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library (ADL) Gazetteer took 0.48368167877197266s
Reputation | Calculation of the PageRank for Alexandria Digital Library (ADL) Gazetteer took 0.02129817008972168s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library (ADL) Gazetteer took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Alexandria Digital Library (ADL) Gazetteer took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library (ADL) Gazetteer took 4.1961669921875e-05s
Believability | Calculation of trust value for Alexandria Digital Library (ADL) Gazetteer took 1.1205673217773438e-05s
INFO | --- Analysis for alexandria-digital-library-adl-gazetteer took 787.9840548038483s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 262.7967426776886s
Availability | VoID file availability check for aliada-scanbit-net took 1.029076099395752s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 2.189394950866699s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.021507740020751953s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.00011277198791503906s
Believability | Calculation of trust value for aliada-scanbit-net took 1.0728836059570312e-05s
INFO | --- Analysis for aliada-scanbit-net took 1316.5396132469177s
Availability | SPARQL endpoint availability check for Allen Brain Atlas took 9.369850158691406e-05s
Availability | VoID file availability check for Allen Brain Atlas took 2.00252103805542s
Completeness | Calculation of interlinking completeness for Allen Brain Atlas took 0.4328575134277344s
Reputation | Calculation of the PageRank for Allen Brain Atlas took 0.02051830291748047s
Interlinking | Calculation of Degree of Connection for Allen Brain Atlas took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Allen Brain Atlas took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Allen Brain Atlas took 3.600120544433594e-05s
Believability | Calculation of trust value for Allen Brain Atlas took 1.2159347534179688e-05s
INFO | --- Analysis for allen-brain-atlas took 17.41624355316162s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 0.6282796859741211s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 3.2976837158203125s
Extra | Recovery of all triples for Allie Abbreviation And Long Form Database in Life Science took 140.64536476135254s
Performance | Total latancy measurement for Allie Abbreviation And Long Form Database in Life Science took 2.7347047328948975s
Amount of data | Number of triples check for Allie Abbreviation And Long Form Database in Life Science took 1.3915836811065674s
Interoperability | New terms check for Allie Abbreviation And Long Form Database in Life Science took 3.4498724937438965s
Versatility | Languages check for Allie Abbreviation And Long Form Database in Life Science took 300.0937035083771s
Interpretability | Number of blank nodes check for Allie Abbreviation And Long Form Database in Life Science took 3.800398349761963s
Security | Check HTTPS for Allie Abbreviation And Long Form Database in Life Science took 1.932814359664917s
Interpretability | RDF structures check for Allie Abbreviation And Long Form Database in Life Science took 0.7595219612121582s
Versatility | Serialization formats check for Allie Abbreviation And Long Form Database in Life Science took 0.5770421028137207s
Availability | RDF dump link check for Allie Abbreviation And Long Form Database in Life Science took 0.5936980247497559s
License | MR license check for Allie Abbreviation And Long Form Database in Life Science took 0.6113290786743164s
License | HR license check for Allie Abbreviation And Long Form Database in Life Science took 30.23405885696411s
Amount of data | Number of property check for Allie Abbreviation And Long Form Database in Life Science took 0.5896821022033691s
Understandability | Number of label check for Allie Abbreviation And Long Form Database in Life Science took 0.8043060302734375s
Understandability | URI regex check for Allie Abbreviation And Long Form Database in Life Science took 1.1990492343902588s
Understandability | Vocabs check for Allie Abbreviation And Long Form Database in Life Science took 0.5750072002410889s
Verifiability | Authors check for Allie Abbreviation And Long Form Database in Life Science took 0.5673394203186035s
Verifiability | Publishers check for Allie Abbreviation And Long Form Database in Life Science took 0.5760948657989502s
Performance | Throughput check for Allie Abbreviation And Long Form Database in Life Science took 11.052963018417358s
Amount of data | Check the number of entities for Allie Abbreviation And Long Form Database in Life Science took 8.559226989746094e-05s
Verifiability | Contribs. check for Allie Abbreviation And Long Form Database in Life Science took 0.544649600982666s
Interlinking | sameAs chians check for Allie Abbreviation And Long Form Database in Life Science took 0.5672605037689209s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.5851268768310547s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.6114575862884521s
Timeliness | dataset update frequency check for Allie Abbreviation And Long Form Database in Life Science took 0.591907262802124s
Currency | Creation date check for Allie Abbreviation And Long Form Database in Life Science took 0.6492834091186523s
Currency | Modification date check for Allie Abbreviation And Long Form Database in Life Science took 0.5999796390533447s
Rep.Conc. | URIs length for Allie Abbreviation And Long Form Database in Life Science took 53.59526467323303s
Interoperability | New vocabularies check for Allie Abbreviation And Long Form Database in Life Science took 1.2974498271942139s
Consistency | Deprecated classes/propertiers check for Allie Abbreviation And Long Form Database in Life Science took 0.5793716907501221s
Accuracy | Check Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6513197422027588s
Accuracy | Check Inverse Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.632432222366333s
Accuracy | Check Empty annotation labels for Allie Abbreviation And Long Form Database in Life Science took 38.71727228164673s
Accuracy | Check White space in annotation for Allie Abbreviation And Long Form Database in Life Science took 3.1033260822296143s
Accuracy | Check Datatype consistency for Allie Abbreviation And Long Form Database in Life Science took 2.599290609359741s
Consistency | Disjoint class check for Allie Abbreviation And Long Form Database in Life Science took 0.6370103359222412s
Consistency | Check Misplaced properties for Allie Abbreviation And Long Form Database in Life Science took 10.090907335281372s
Consistency | Misplaced classes for Allie Abbreviation And Long Form Database in Life Science took 9.034310579299927s
Consistency | Check Ontology hijacking for Allie Abbreviation And Long Form Database in Life Science took 33.95576214790344s
Consistency | Check Invalid usage of undefined classes for Allie Abbreviation And Long Form Database in Life Science took 1.4132020473480225s
Consistency | Check Invalid usage of undefined properties for Allie Abbreviation And Long Form Database in Life Science took 10.83627724647522s
Conciseness | Check Extensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 2.8371121883392334s
Conciseness | Check Intensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 0.8521063327789307s
Security | Sign check for Allie Abbreviation And Long Form Database in Life Science took 0.5593452453613281s
Availability | Check URIs Dereferenciability for Allie Abbreviation And Long Form Database in Life Science took 14344.355221033096s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 180.32608652114868s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.021123647689819336s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0007832050323486328s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 8.487701416015625e-05s
Interoperability | Check the re-using of existing vocabs for Allie Abbreviation And Long Form Database in Life Science took 1.4787633419036865s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 1.239776611328125e-05s
INFO | --- Analysis for allie-abbreviation-and-long-form-database-in-life-science took 15276.295907974243s
Availability | SPARQL endpoint availability check for Alojamientos took 4.0531158447265625e-05s
Availability | VoID file availability check for Alojamientos took 0.00029587745666503906s
Completeness | Calculation of interlinking completeness for Alojamientos took 60.94968509674072s
Reputation | Calculation of the PageRank for Alojamientos took 0.021176576614379883s
Interlinking | Calculation of Degree of Connection for Alojamientos took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Alojamientos took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Alojamientos took 3.24249267578125e-05s
Believability | Calculation of trust value for Alojamientos took 2.2172927856445312e-05s
INFO | --- Analysis for alojamientos-zaragoza took 244.42307710647583s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 0.25566673278808594s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 0.3230752944946289s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.021015644073486328s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 5.173683166503906e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 1.1920928955078125e-05s
INFO | --- Analysis for alpino-rdf took 272.62497878074646s
Availability | SPARQL endpoint availability check for AAT-atawil took 8.320808410644531e-05s
Availability | VoID file availability check for AAT-atawil took 1.356874704360962s
Completeness | Calculation of interlinking completeness for AAT-atawil took 0.33268165588378906s
Reputation | Calculation of the PageRank for AAT-atawil took 0.021026134490966797s
Interlinking | Calculation of Degree of Connection for AAT-atawil took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for AAT-atawil took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for AAT-atawil took 3.0517578125e-05s
Believability | Calculation of trust value for AAT-atawil took 7.62939453125e-06s
INFO | --- Analysis for Altawil took 5.66860032081604s
Availability | SPARQL endpoint availability check for Auckland Museum Collections Online took 6.9350762367248535s
Availability | VoID file availability check for Auckland Museum Collections Online took 0.0008764266967773438s
Completeness | Calculation of interlinking completeness for Auckland Museum Collections Online took 1.1663260459899902s
Reputation | Calculation of the PageRank for Auckland Museum Collections Online took 0.02068042755126953s
Interlinking | Calculation of Degree of Connection for Auckland Museum Collections Online took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Auckland Museum Collections Online took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Auckland Museum Collections Online took 3.218650817871094e-05s
Believability | Calculation of trust value for Auckland Museum Collections Online took 1.1920928955078125e-05s
INFO | --- Analysis for am-collections-online took 11.181246995925903s
Availability | SPARQL endpoint availability check for Amer Nejma took 4.0531158447265625e-05s
Availability | VoID file availability check for Amer Nejma took 2.2795610427856445s
Completeness | Calculation of interlinking completeness for Amer Nejma took 0.3676137924194336s
Reputation | Calculation of the PageRank for Amer Nejma took 0.026450157165527344s
Interlinking | Calculation of Degree of Connection for Amer Nejma took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Amer Nejma took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for Amer Nejma took 3.24249267578125e-05s
Believability | Calculation of trust value for Amer Nejma took 7.62939453125e-06s
INFO | --- Analysis for Amer_Nejma took 4.323987245559692s
Availability | SPARQL endpoint availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 3.933906555175781e-05s
Availability | VoID file availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.00017213821411132812s
Completeness | Calculation of interlinking completeness for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.7842280864715576s
Reputation | Calculation of the PageRank for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.020923137664794922s
Interlinking | Calculation of Degree of Connection for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 3.0279159545898438e-05s
Believability | Calculation of trust value for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 8.821487426757812e-06s
INFO | --- Analysis for amon took 3.382911443710327s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.7742955684661865s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.5850820541381836s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.37696266174316406s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.02072286605834961s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 9.059906005859375e-05s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.0967254638671875e-05s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 3.9004745483398438s
Availability | SPARQL endpoint availability check for Analisi del blog http://www.beppegrillo.it/ took 4.1961669921875e-05s
Availability | VoID file availability check for Analisi del blog http://www.beppegrillo.it/ took 0.00044989585876464844s
Completeness | Calculation of interlinking completeness for Analisi del blog http://www.beppegrillo.it/ took 0.31479406356811523s
Reputation | Calculation of the PageRank for Analisi del blog http://www.beppegrillo.it/ took 0.02103447914123535s
Interlinking | Calculation of Degree of Connection for Analisi del blog http://www.beppegrillo.it/ took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Analisi del blog http://www.beppegrillo.it/ took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Analisi del blog http://www.beppegrillo.it/ took 2.86102294921875e-05s
Believability | Calculation of trust value for Analisi del blog http://www.beppegrillo.it/ took 1.1205673217773438e-05s
INFO | --- Analysis for analisi-del-blog-http-www-beppegrillo-it took 4.40387487411499s
Availability | SPARQL endpoint availability check for Animal Diversity Web took 4.291534423828125e-05s
Availability | VoID file availability check for Animal Diversity Web took 1.3423335552215576s
Completeness | Calculation of interlinking completeness for Animal Diversity Web took 0.3070850372314453s
Reputation | Calculation of the PageRank for Animal Diversity Web took 0.02091836929321289s
Interlinking | Calculation of Degree of Connection for Animal Diversity Web took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Animal Diversity Web took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Animal Diversity Web took 2.9802322387695312e-05s
Believability | Calculation of trust value for Animal Diversity Web took 1.0251998901367188e-05s
INFO | --- Analysis for animal-diversity-web took 18.337186574935913s
Availability | SPARQL endpoint availability check for Anime Dataset took 7.486343383789062e-05s
Availability | VoID file availability check for Anime Dataset took 0.37063169479370117s
Completeness | Calculation of interlinking completeness for Anime Dataset took 0.3825831413269043s
Reputation | Calculation of the PageRank for Anime Dataset took 0.021245479583740234s
Interlinking | Calculation of Degree of Connection for Anime Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Anime Dataset took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Anime Dataset took 3.218650817871094e-05s
Believability | Calculation of trust value for Anime Dataset took 7.62939453125e-06s
INFO | --- Analysis for Anime took 4.076982736587524s
Availability | SPARQL endpoint availability check for ANNO took 7.390975952148438e-05s
Availability | VoID file availability check for ANNO took 0.5507662296295166s
Completeness | Calculation of interlinking completeness for ANNO took 0.3245875835418701s
Reputation | Calculation of the PageRank for ANNO took 0.020805835723876953s
Interlinking | Calculation of Degree of Connection for ANNO took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ANNO took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for ANNO took 3.528594970703125e-05s
Believability | Calculation of trust value for ANNO took 7.62939453125e-06s
INFO | --- Analysis for anno took 6.716877460479736s
Availability | SPARQL endpoint availability check for Antique Cars Collection (Linked Cars) took 4.124641418457031e-05s
Availability | VoID file availability check for Antique Cars Collection (Linked Cars) took 0.23841071128845215s
Completeness | Calculation of interlinking completeness for Antique Cars Collection (Linked Cars) took 0.3160080909729004s
Reputation | Calculation of the PageRank for Antique Cars Collection (Linked Cars) took 0.02130913734436035s
Interlinking | Calculation of Degree of Connection for Antique Cars Collection (Linked Cars) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Antique Cars Collection (Linked Cars) took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Antique Cars Collection (Linked Cars) took 9.441375732421875e-05s
Believability | Calculation of trust value for Antique Cars Collection (Linked Cars) took 8.106231689453125e-06s
INFO | --- Analysis for AntiqueCarsCollection took 2.9455013275146484s
Availability | SPARQL endpoint availability check for apache took 4.220008850097656e-05s
Availability | VoID file availability check for apache took 0.00020384788513183594s
Completeness | Calculation of interlinking completeness for apache took 0.3066108226776123s
Reputation | Calculation of the PageRank for apache took 0.020946741104125977s
Interlinking | Calculation of Degree of Connection for apache took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for apache took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for apache took 5.817413330078125e-05s
Believability | Calculation of trust value for apache took 8.106231689453125e-06s
INFO | --- Analysis for apache took 2.9675614833831787s
Availability | SPARQL endpoint availability check for Apertium RDF took 1.2674219608306885s
Availability | VoID file availability check for Apertium RDF took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.41423821449279785s
Reputation | Calculation of the PageRank for Apertium RDF took 0.02057671546936035s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 4.482269287109375e-05s
Believability | Calculation of trust value for Apertium RDF took 1.1920928955078125e-05s
INFO | --- Analysis for apertium-rdf took 16.87742328643799s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 0.29938364028930664s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.0004520416259765625s
Extra | Recovery of all triples for Apertium RDF CA-IT took 253.0264174938202s
Performance | Total latancy measurement for Apertium RDF CA-IT took 1.348299264907837s
Amount of data | Number of triples check for Apertium RDF CA-IT took 2.1838746070861816s
Interoperability | New terms check for Apertium RDF CA-IT took 3.0005667209625244s
Versatility | Languages check for Apertium RDF CA-IT took 44.43498468399048s
Interpretability | Number of blank nodes check for Apertium RDF CA-IT took 1.531243085861206s
Security | Check HTTPS for Apertium RDF CA-IT took 0.1472775936126709s
Interpretability | RDF structures check for Apertium RDF CA-IT took 0.34165453910827637s
Versatility | Serialization formats check for Apertium RDF CA-IT took 0.3403768539428711s
Availability | RDF dump link check for Apertium RDF CA-IT took 0.30640530586242676s
License | MR license check for Apertium RDF CA-IT took 0.3485550880432129s
License | HR license check for Apertium RDF CA-IT took 0.4685707092285156s
Amount of data | Number of property check for Apertium RDF CA-IT took 0.3067653179168701s
Understandability | Number of label check for Apertium RDF CA-IT took 0.36983299255371094s
Understandability | URI regex check for Apertium RDF CA-IT took 0.6364035606384277s
Understandability | Vocabs check for Apertium RDF CA-IT took 0.26855945587158203s
Verifiability | Authors check for Apertium RDF CA-IT took 0.35769200325012207s
Verifiability | Publishers check for Apertium RDF CA-IT took 0.2962150573730469s
Performance | Throughput check for Apertium RDF CA-IT took 11.45546007156372s
Amount of data | Check the number of entities for Apertium RDF CA-IT took 0.00010943412780761719s
Verifiability | Contribs. check for Apertium RDF CA-IT took 0.2827906608581543s
Interlinking | sameAs chians check for Apertium RDF CA-IT took 0.33582019805908203s
Interlinking | skos check for Apertium RDF CA-IT took 0.2827270030975342s
Interlinking | skos check for Apertium RDF CA-IT took 0.25344109535217285s
Timeliness | dataset update frequency check for Apertium RDF CA-IT took 0.32373905181884766s
Currency | Creation date check for Apertium RDF CA-IT took 0.330890417098999s
Currency | Modification date check for Apertium RDF CA-IT took 0.3235905170440674s
Rep.Conc. | URIs length for Apertium RDF CA-IT took 101.20410203933716s
Interoperability | New vocabularies check for Apertium RDF CA-IT took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF CA-IT took 0.3509049415588379s
Accuracy | Check Functional Property for Apertium RDF CA-IT took 0.26842212677001953s
Accuracy | Check Inverse Functional Property for Apertium RDF CA-IT took 0.29741621017456055s
Accuracy | Check Empty annotation labels for Apertium RDF CA-IT took 0.9288280010223389s
Accuracy | Check White space in annotation for Apertium RDF CA-IT took 0.009916305541992188s
Accuracy | Check Datatype consistency for Apertium RDF CA-IT took 2.675520181655884s
Consistency | Disjoint class check for Apertium RDF CA-IT took 0.28698205947875977s
Consistency | Check Misplaced properties for Apertium RDF CA-IT took 4.591097831726074s
Consistency | Misplaced classes for Apertium RDF CA-IT took 8.235988140106201s
Consistency | Check Ontology hijacking for Apertium RDF CA-IT took 91.98127317428589s
Consistency | Check Invalid usage of undefined classes for Apertium RDF CA-IT took 1.5825836658477783s
Consistency | Check Invalid usage of undefined properties for Apertium RDF CA-IT took 5.734065532684326s
Conciseness | Check Extensional conciseness for Apertium RDF CA-IT took 2.972696542739868s
Conciseness | Check Intensional conciseness for Apertium RDF CA-IT took 0.38840293884277344s
Security | Sign check for Apertium RDF CA-IT took 0.27401256561279297s
Availability | Check URIs Dereferenciability for Apertium RDF CA-IT took 4.038638591766357s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.5706391334533691s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.020677566528320312s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 4.5299530029296875e-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.1444091796875e-05s
INFO | --- Analysis for apertium-rdf-ca-it took 615.0624749660492s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 0.2893209457397461s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.0008623600006103516s
Extra | Recovery of all triples for Apertium RDF EN-CA took 265.80574464797974s
Performance | Total latancy measurement for Apertium RDF EN-CA took 1.2696542739868164s
Amount of data | Number of triples check for Apertium RDF EN-CA took 2.111539840698242s
Interoperability | New terms check for Apertium RDF EN-CA took 3.149339199066162s
Versatility | Languages check for Apertium RDF EN-CA took 44.45189929008484s
Interpretability | Number of blank nodes check for Apertium RDF EN-CA took 1.2338836193084717s
Security | Check HTTPS for Apertium RDF EN-CA took 0.12452077865600586s
Interpretability | RDF structures check for Apertium RDF EN-CA took 0.3014216423034668s
Versatility | Serialization formats check for Apertium RDF EN-CA took 0.2917909622192383s
Availability | RDF dump link check for Apertium RDF EN-CA took 0.2718966007232666s
License | MR license check for Apertium RDF EN-CA took 0.27794718742370605s
License | HR license check for Apertium RDF EN-CA took 0.39853453636169434s
Amount of data | Number of property check for Apertium RDF EN-CA took 0.2668313980102539s
Understandability | Number of label check for Apertium RDF EN-CA took 0.3462996482849121s
Understandability | URI regex check for Apertium RDF EN-CA took 0.6220419406890869s
Understandability | Vocabs check for Apertium RDF EN-CA took 0.27840256690979004s
Verifiability | Authors check for Apertium RDF EN-CA took 0.30808448791503906s
Verifiability | Publishers check for Apertium RDF EN-CA took 0.318401575088501s
Performance | Throughput check for Apertium RDF EN-CA took 11.657508611679077s
Amount of data | Check the number of entities for Apertium RDF EN-CA took 4.0531158447265625e-05s
Verifiability | Contribs. check for Apertium RDF EN-CA took 0.3176722526550293s
Interlinking | sameAs chians check for Apertium RDF EN-CA took 0.29052305221557617s
Interlinking | skos check for Apertium RDF EN-CA took 0.26636695861816406s
Interlinking | skos check for Apertium RDF EN-CA took 0.2223644256591797s
Timeliness | dataset update frequency check for Apertium RDF EN-CA took 0.3016548156738281s
Currency | Creation date check for Apertium RDF EN-CA took 0.30622291564941406s
Currency | Modification date check for Apertium RDF EN-CA took 0.2963271141052246s
Rep.Conc. | URIs length for Apertium RDF EN-CA took 96.696448802948s
Interoperability | New vocabularies check for Apertium RDF EN-CA took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF EN-CA took 0.3144078254699707s
Accuracy | Check Functional Property for Apertium RDF EN-CA took 0.2898745536804199s
Accuracy | Check Inverse Functional Property for Apertium RDF EN-CA took 0.28740906715393066s
Accuracy | Check Empty annotation labels for Apertium RDF EN-CA took 0.9358758926391602s
Accuracy | Check White space in annotation for Apertium RDF EN-CA took 0.009933948516845703s
Accuracy | Check Datatype consistency for Apertium RDF EN-CA took 2.6365060806274414s
Consistency | Disjoint class check for Apertium RDF EN-CA took 0.30983614921569824s
Consistency | Check Misplaced properties for Apertium RDF EN-CA took 4.6234869956970215s
Consistency | Misplaced classes for Apertium RDF EN-CA took 8.518108606338501s
Consistency | Check Ontology hijacking for Apertium RDF EN-CA took 104.70770072937012s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EN-CA took 1.5522172451019287s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EN-CA took 5.686378717422485s
Conciseness | Check Extensional conciseness for Apertium RDF EN-CA took 3.0615835189819336s
Conciseness | Check Intensional conciseness for Apertium RDF EN-CA took 0.33423829078674316s
Security | Sign check for Apertium RDF EN-CA took 0.3022956848144531s
Availability | Check URIs Dereferenciability for Apertium RDF EN-CA took 3.6934189796447754s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.6023416519165039s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.021525144577026367s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0008029937744140625s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 5.8650970458984375e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EN-CA took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF EN-CA took 1.4781951904296875e-05s
INFO | --- Analysis for apertium-rdf-en-ca took 632.7450573444366s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 0.24002933502197266s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.0008234977722167969s
Extra | Recovery of all triples for Apertium RDF EN-ES took 282.26356983184814s
Performance | Total latancy measurement for Apertium RDF EN-ES took 1.4110171794891357s
Amount of data | Number of triples check for Apertium RDF EN-ES took 2.1121599674224854s
Interoperability | New terms check for Apertium RDF EN-ES took 3.117283582687378s
Versatility | Languages check for Apertium RDF EN-ES took 44.12442421913147s
Interpretability | Number of blank nodes check for Apertium RDF EN-ES took 1.1080989837646484s
Security | Check HTTPS for Apertium RDF EN-ES took 0.12196588516235352s
Interpretability | RDF structures check for Apertium RDF EN-ES took 0.3089158535003662s
Versatility | Serialization formats check for Apertium RDF EN-ES took 0.2941160202026367s
Availability | RDF dump link check for Apertium RDF EN-ES took 0.2717874050140381s
License | MR license check for Apertium RDF EN-ES took 0.2985842227935791s
License | HR license check for Apertium RDF EN-ES took 0.3823237419128418s
Amount of data | Number of property check for Apertium RDF EN-ES took 0.2759425640106201s
Understandability | Number of label check for Apertium RDF EN-ES took 0.3268747329711914s
Understandability | URI regex check for Apertium RDF EN-ES took 0.63922119140625s
Understandability | Vocabs check for Apertium RDF EN-ES took 0.30099034309387207s
Verifiability | Authors check for Apertium RDF EN-ES took 0.3491513729095459s
Verifiability | Publishers check for Apertium RDF EN-ES took 0.3213222026824951s
Performance | Throughput check for Apertium RDF EN-ES took 12.01975679397583s
Amount of data | Check the number of entities for Apertium RDF EN-ES took 9.036064147949219e-05s
Verifiability | Contribs. check for Apertium RDF EN-ES took 0.28210949897766113s
Interlinking | sameAs chians check for Apertium RDF EN-ES took 0.3002340793609619s
Interlinking | skos check for Apertium RDF EN-ES took 0.29046082496643066s
Interlinking | skos check for Apertium RDF EN-ES took 0.2693004608154297s
Timeliness | dataset update frequency check for Apertium RDF EN-ES took 0.27966761589050293s
Currency | Creation date check for Apertium RDF EN-ES took 0.31063175201416016s
Currency | Modification date check for Apertium RDF EN-ES took 0.28004026412963867s
Rep.Conc. | URIs length for Apertium RDF EN-ES took 85.84955859184265s
Interoperability | New vocabularies check for Apertium RDF EN-ES took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EN-ES took 0.3918004035949707s
Accuracy | Check Functional Property for Apertium RDF EN-ES took 0.3059258460998535s
Accuracy | Check Inverse Functional Property for Apertium RDF EN-ES took 0.2918999195098877s
Accuracy | Check Empty annotation labels for Apertium RDF EN-ES took 0.873767614364624s
Accuracy | Check White space in annotation for Apertium RDF EN-ES took 0.010033369064331055s
Accuracy | Check Datatype consistency for Apertium RDF EN-ES took 2.7125589847564697s
Consistency | Disjoint class check for Apertium RDF EN-ES took 0.31194591522216797s
Consistency | Check Misplaced properties for Apertium RDF EN-ES took 4.75979208946228s
Consistency | Misplaced classes for Apertium RDF EN-ES took 8.452866792678833s
Consistency | Check Ontology hijacking for Apertium RDF EN-ES took 85.44204831123352s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EN-ES took 1.4961497783660889s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EN-ES took 6.029762268066406s
Conciseness | Check Extensional conciseness for Apertium RDF EN-ES took 3.162275791168213s
Conciseness | Check Intensional conciseness for Apertium RDF EN-ES took 0.3590106964111328s
Security | Sign check for Apertium RDF EN-ES took 0.31116700172424316s
Availability | Check URIs Dereferenciability for Apertium RDF EN-ES took 3.6880710124969482s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.3796837329864502s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.021034955978393555s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 4.839897155761719e-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.1682510375976562e-05s
INFO | --- Analysis for apertium-rdf-en-es took 618.9141538143158s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 0.24815654754638672s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.0008196830749511719s
Extra | Recovery of all triples for Apertium RDF EN-GL took 255.49831223487854s
Performance | Total latancy measurement for Apertium RDF EN-GL took 1.336540937423706s
Amount of data | Number of triples check for Apertium RDF EN-GL took 2.161311388015747s
Interoperability | New terms check for Apertium RDF EN-GL took 2.939225435256958s
Versatility | Languages check for Apertium RDF EN-GL took 44.140196323394775s
Interpretability | Number of blank nodes check for Apertium RDF EN-GL took 1.267226219177246s
Security | Check HTTPS for Apertium RDF EN-GL took 0.14995670318603516s
Interpretability | RDF structures check for Apertium RDF EN-GL took 0.28211402893066406s
Versatility | Serialization formats check for Apertium RDF EN-GL took 0.32513928413391113s
Availability | RDF dump link check for Apertium RDF EN-GL took 0.2643110752105713s
License | MR license check for Apertium RDF EN-GL took 0.35890936851501465s
License | HR license check for Apertium RDF EN-GL took 0.4490334987640381s
Amount of data | Number of property check for Apertium RDF EN-GL took 0.2829101085662842s
Understandability | Number of label check for Apertium RDF EN-GL took 0.35460758209228516s
Understandability | URI regex check for Apertium RDF EN-GL took 0.6407186985015869s
Understandability | Vocabs check for Apertium RDF EN-GL took 0.30593156814575195s
Verifiability | Authors check for Apertium RDF EN-GL took 0.31502795219421387s
Verifiability | Publishers check for Apertium RDF EN-GL took 0.3196549415588379s
Performance | Throughput check for Apertium RDF EN-GL took 11.893242359161377s
Amount of data | Check the number of entities for Apertium RDF EN-GL took 4.029273986816406e-05s
Verifiability | Contribs. check for Apertium RDF EN-GL took 0.2991492748260498s
Interlinking | sameAs chians check for Apertium RDF EN-GL took 0.2866041660308838s
Interlinking | skos check for Apertium RDF EN-GL took 0.3260352611541748s
Interlinking | skos check for Apertium RDF EN-GL took 0.2037639617919922s
Timeliness | dataset update frequency check for Apertium RDF EN-GL took 0.3230757713317871s
Currency | Creation date check for Apertium RDF EN-GL took 0.323819637298584s
Currency | Modification date check for Apertium RDF EN-GL took 0.29343175888061523s
Rep.Conc. | URIs length for Apertium RDF EN-GL took 92.202143907547s
Interoperability | New vocabularies check for Apertium RDF EN-GL took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF EN-GL took 0.3397984504699707s
Accuracy | Check Functional Property for Apertium RDF EN-GL took 0.3000006675720215s
Accuracy | Check Inverse Functional Property for Apertium RDF EN-GL took 0.30826520919799805s
Accuracy | Check Empty annotation labels for Apertium RDF EN-GL took 0.9135432243347168s
Accuracy | Check White space in annotation for Apertium RDF EN-GL took 0.009961843490600586s
Accuracy | Check Datatype consistency for Apertium RDF EN-GL took 2.6740567684173584s
Consistency | Disjoint class check for Apertium RDF EN-GL took 0.3230011463165283s
Consistency | Check Misplaced properties for Apertium RDF EN-GL took 4.571791410446167s
Consistency | Misplaced classes for Apertium RDF EN-GL took 8.422099351882935s
Consistency | Check Ontology hijacking for Apertium RDF EN-GL took 85.09548711776733s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EN-GL took 1.4923875331878662s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EN-GL took 5.7344443798065186s
Conciseness | Check Extensional conciseness for Apertium RDF EN-GL took 3.0704269409179688s
Conciseness | Check Intensional conciseness for Apertium RDF EN-GL took 0.3470633029937744s
Security | Sign check for Apertium RDF EN-GL took 0.3374979496002197s
Availability | Check URIs Dereferenciability for Apertium RDF EN-GL took 3.7397725582122803s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.35980939865112305s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.020635604858398438s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-GL took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-GL took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 4.744529724121094e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EN-GL took 1.9073486328125e-06s
Believability | Calculation of trust value for Apertium RDF EN-GL took 1.1920928955078125e-05s
INFO | --- Analysis for apertium-rdf-en-gl took 600.6969957351685s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 0.24495172500610352s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.0008678436279296875s
Extra | Recovery of all triples for Apertium RDF EO-CA took 251.88145303726196s
Performance | Total latancy measurement for Apertium RDF EO-CA took 1.3889906406402588s
Amount of data | Number of triples check for Apertium RDF EO-CA took 2.1456496715545654s
Interoperability | New terms check for Apertium RDF EO-CA took 3.1361629962921143s
Versatility | Languages check for Apertium RDF EO-CA took 44.11966300010681s
Interpretability | Number of blank nodes check for Apertium RDF EO-CA took 1.119553804397583s
Security | Check HTTPS for Apertium RDF EO-CA took 0.14939141273498535s
Interpretability | RDF structures check for Apertium RDF EO-CA took 0.3097059726715088s
Versatility | Serialization formats check for Apertium RDF EO-CA took 0.3247666358947754s
Availability | RDF dump link check for Apertium RDF EO-CA took 0.308626651763916s
License | MR license check for Apertium RDF EO-CA took 0.28015637397766113s
License | HR license check for Apertium RDF EO-CA took 0.3817315101623535s
Amount of data | Number of property check for Apertium RDF EO-CA took 0.29251575469970703s
Understandability | Number of label check for Apertium RDF EO-CA took 0.3262801170349121s
Understandability | URI regex check for Apertium RDF EO-CA took 0.6265544891357422s
Understandability | Vocabs check for Apertium RDF EO-CA took 0.3338758945465088s
Verifiability | Authors check for Apertium RDF EO-CA took 0.3172128200531006s
Verifiability | Publishers check for Apertium RDF EO-CA took 0.33440399169921875s
Performance | Throughput check for Apertium RDF EO-CA took 11.794461250305176s
Amount of data | Check the number of entities for Apertium RDF EO-CA took 8.630752563476562e-05s
Verifiability | Contribs. check for Apertium RDF EO-CA took 0.3117859363555908s
Interlinking | sameAs chians check for Apertium RDF EO-CA took 0.32108569145202637s
Interlinking | skos check for Apertium RDF EO-CA took 0.2706184387207031s
Interlinking | skos check for Apertium RDF EO-CA took 0.23793649673461914s
Timeliness | dataset update frequency check for Apertium RDF EO-CA took 0.28714418411254883s
Currency | Creation date check for Apertium RDF EO-CA took 0.3004496097564697s
Currency | Modification date check for Apertium RDF EO-CA took 0.32492709159851074s
Rep.Conc. | URIs length for Apertium RDF EO-CA took 103.45347428321838s
Interoperability | New vocabularies check for Apertium RDF EO-CA took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EO-CA took 0.31712985038757324s
Accuracy | Check Functional Property for Apertium RDF EO-CA took 0.317401647567749s
Accuracy | Check Inverse Functional Property for Apertium RDF EO-CA took 0.3099985122680664s
Accuracy | Check Empty annotation labels for Apertium RDF EO-CA took 0.8487143516540527s
Accuracy | Check White space in annotation for Apertium RDF EO-CA took 0.010254383087158203s
Accuracy | Check Datatype consistency for Apertium RDF EO-CA took 2.638505220413208s
Consistency | Disjoint class check for Apertium RDF EO-CA took 0.308274507522583s
Consistency | Check Misplaced properties for Apertium RDF EO-CA took 4.835622549057007s
Consistency | Misplaced classes for Apertium RDF EO-CA took 8.462000370025635s
Consistency | Check Ontology hijacking for Apertium RDF EO-CA took 92.33908200263977s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EO-CA took 1.6082942485809326s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EO-CA took 5.736419677734375s
Conciseness | Check Extensional conciseness for Apertium RDF EO-CA took 3.2181544303894043s
Conciseness | Check Intensional conciseness for Apertium RDF EO-CA took 0.3396720886230469s
Security | Sign check for Apertium RDF EO-CA took 0.31859278678894043s
Availability | Check URIs Dereferenciability for Apertium RDF EO-CA took 3.671999931335449s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 1.3090717792510986s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.020954608917236328s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 4.792213439941406e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EO-CA took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF EO-CA took 1.3828277587890625e-05s
INFO | --- Analysis for apertium-rdf-eo-ca took 622.8288233280182s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 0.21862316131591797s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.0009200572967529297s
Extra | Recovery of all triples for Apertium RDF EO-EN took 283.5399830341339s
Performance | Total latancy measurement for Apertium RDF EO-EN took 1.374783992767334s
Amount of data | Number of triples check for Apertium RDF EO-EN took 2.155223846435547s
Interoperability | New terms check for Apertium RDF EO-EN took 2.9385578632354736s
Versatility | Languages check for Apertium RDF EO-EN took 44.46870970726013s
Interpretability | Number of blank nodes check for Apertium RDF EO-EN took 1.0931510925292969s
Security | Check HTTPS for Apertium RDF EO-EN took 0.13867425918579102s
Interpretability | RDF structures check for Apertium RDF EO-EN took 0.2703702449798584s
Versatility | Serialization formats check for Apertium RDF EO-EN took 0.3006720542907715s
Availability | RDF dump link check for Apertium RDF EO-EN took 0.2969245910644531s
License | MR license check for Apertium RDF EO-EN took 0.3000965118408203s
License | HR license check for Apertium RDF EO-EN took 0.3863952159881592s
Amount of data | Number of property check for Apertium RDF EO-EN took 0.32041192054748535s
Understandability | Number of label check for Apertium RDF EO-EN took 0.33124351501464844s
Understandability | URI regex check for Apertium RDF EO-EN took 0.5885388851165771s
Understandability | Vocabs check for Apertium RDF EO-EN took 0.26406335830688477s
Verifiability | Authors check for Apertium RDF EO-EN took 0.342090368270874s
Verifiability | Publishers check for Apertium RDF EO-EN took 0.31488823890686035s
Performance | Throughput check for Apertium RDF EO-EN took 11.869352102279663s
Amount of data | Check the number of entities for Apertium RDF EO-EN took 9.179115295410156e-05s
Verifiability | Contribs. check for Apertium RDF EO-EN took 0.34387874603271484s
Interlinking | sameAs chians check for Apertium RDF EO-EN took 0.3145887851715088s
Interlinking | skos check for Apertium RDF EO-EN took 0.33945131301879883s
Interlinking | skos check for Apertium RDF EO-EN took 0.2441713809967041s
Timeliness | dataset update frequency check for Apertium RDF EO-EN took 0.32207632064819336s
Currency | Creation date check for Apertium RDF EO-EN took 0.3068883419036865s
Currency | Modification date check for Apertium RDF EO-EN took 0.3094816207885742s
Rep.Conc. | URIs length for Apertium RDF EO-EN took 96.45803380012512s
Interoperability | New vocabularies check for Apertium RDF EO-EN took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EO-EN took 0.38189125061035156s
Accuracy | Check Functional Property for Apertium RDF EO-EN took 0.2898859977722168s
Accuracy | Check Inverse Functional Property for Apertium RDF EO-EN took 0.31969356536865234s
Accuracy | Check Empty annotation labels for Apertium RDF EO-EN took 0.8065268993377686s
Accuracy | Check White space in annotation for Apertium RDF EO-EN took 0.01006460189819336s
Accuracy | Check Datatype consistency for Apertium RDF EO-EN took 2.6823229789733887s
Consistency | Disjoint class check for Apertium RDF EO-EN took 0.327425479888916s
Consistency | Check Misplaced properties for Apertium RDF EO-EN took 4.711564064025879s
Consistency | Misplaced classes for Apertium RDF EO-EN took 8.335636854171753s
Consistency | Check Ontology hijacking for Apertium RDF EO-EN took 105.13535833358765s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EO-EN took 1.4979844093322754s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EO-EN took 6.027535676956177s
Conciseness | Check Extensional conciseness for Apertium RDF EO-EN took 3.0880191326141357s
Conciseness | Check Intensional conciseness for Apertium RDF EO-EN took 0.320145845413208s
Security | Sign check for Apertium RDF EO-EN took 0.30031561851501465s
Availability | Check URIs Dereferenciability for Apertium RDF EO-EN took 3.6475467681884766s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.45606112480163574s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.020506858825683594s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-EN took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-EN took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 4.5299530029296875e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EO-EN took 2.1457672119140625e-06s
Believability | Calculation of trust value for Apertium RDF EO-EN took 1.2159347534179688e-05s
INFO | --- Analysis for apertium-rdf-eo-en took 662.3392474651337s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 0.2126178741455078s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.00045943260192871094s
Extra | Recovery of all triples for Apertium RDF EO-ES took 294.5712196826935s
Performance | Total latancy measurement for Apertium RDF EO-ES took 3.4598031044006348s
Amount of data | Number of triples check for Apertium RDF EO-ES took 2.204256057739258s
Interoperability | New terms check for Apertium RDF EO-ES took 2.9510416984558105s
Versatility | Languages check for Apertium RDF EO-ES took 44.02651047706604s
Interpretability | Number of blank nodes check for Apertium RDF EO-ES took 1.101801872253418s
Security | Check HTTPS for Apertium RDF EO-ES took 0.16697049140930176s
Interpretability | RDF structures check for Apertium RDF EO-ES took 0.31453514099121094s
Versatility | Serialization formats check for Apertium RDF EO-ES took 0.3005392551422119s
Availability | RDF dump link check for Apertium RDF EO-ES took 0.31995153427124023s
License | MR license check for Apertium RDF EO-ES took 0.30374860763549805s
License | HR license check for Apertium RDF EO-ES took 0.37580108642578125s
Amount of data | Number of property check for Apertium RDF EO-ES took 0.30122804641723633s
Understandability | Number of label check for Apertium RDF EO-ES took 0.32708215713500977s
Understandability | URI regex check for Apertium RDF EO-ES took 0.6289341449737549s
Understandability | Vocabs check for Apertium RDF EO-ES took 0.3196098804473877s
Verifiability | Authors check for Apertium RDF EO-ES took 0.33226442337036133s
Verifiability | Publishers check for Apertium RDF EO-ES took 0.32753801345825195s
Performance | Throughput check for Apertium RDF EO-ES took 11.921579599380493s
Amount of data | Check the number of entities for Apertium RDF EO-ES took 8.487701416015625e-05s
Verifiability | Contribs. check for Apertium RDF EO-ES took 0.3099672794342041s
Interlinking | sameAs chians check for Apertium RDF EO-ES took 0.3207387924194336s
Interlinking | skos check for Apertium RDF EO-ES took 0.28676295280456543s
Interlinking | skos check for Apertium RDF EO-ES took 0.2597501277923584s
Timeliness | dataset update frequency check for Apertium RDF EO-ES took 0.3084855079650879s
Currency | Creation date check for Apertium RDF EO-ES took 0.3264648914337158s
Currency | Modification date check for Apertium RDF EO-ES took 0.2940833568572998s
Rep.Conc. | URIs length for Apertium RDF EO-ES took 91.91517663002014s
Interoperability | New vocabularies check for Apertium RDF EO-ES took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EO-ES took 0.3117024898529053s
Accuracy | Check Functional Property for Apertium RDF EO-ES took 0.3303194046020508s
Accuracy | Check Inverse Functional Property for Apertium RDF EO-ES took 0.28708362579345703s
Accuracy | Check Empty annotation labels for Apertium RDF EO-ES took 0.7782859802246094s
Accuracy | Check White space in annotation for Apertium RDF EO-ES took 0.010002613067626953s
Accuracy | Check Datatype consistency for Apertium RDF EO-ES took 2.6551122665405273s
Consistency | Disjoint class check for Apertium RDF EO-ES took 0.27785444259643555s
Consistency | Check Misplaced properties for Apertium RDF EO-ES took 4.666044473648071s
Consistency | Misplaced classes for Apertium RDF EO-ES took 8.444118022918701s
Consistency | Check Ontology hijacking for Apertium RDF EO-ES took 92.72004771232605s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EO-ES took 1.5220072269439697s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EO-ES took 5.793596267700195s
Conciseness | Check Extensional conciseness for Apertium RDF EO-ES took 3.1126255989074707s
Conciseness | Check Intensional conciseness for Apertium RDF EO-ES took 0.3406369686126709s
Security | Sign check for Apertium RDF EO-ES took 0.30040836334228516s
Availability | Check URIs Dereferenciability for Apertium RDF EO-ES took 3.799229621887207s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.377640962600708s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.0207669734954834s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 4.458427429199219e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EO-ES took 2.1457672119140625e-06s
Believability | Calculation of trust value for Apertium RDF EO-ES took 1.3113021850585938e-05s
INFO | --- Analysis for apertium-rdf-eo-es took 654.3494787216187s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 0.26822328567504883s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.0008020401000976562s
Extra | Recovery of all triples for Apertium RDF EO-FR took 293.1391694545746s
Performance | Total latancy measurement for Apertium RDF EO-FR took 1.347121238708496s
Amount of data | Number of triples check for Apertium RDF EO-FR took 2.2864484786987305s
Interoperability | New terms check for Apertium RDF EO-FR took 2.906113862991333s
Versatility | Languages check for Apertium RDF EO-FR took 44.160850524902344s
Interpretability | Number of blank nodes check for Apertium RDF EO-FR took 1.0848503112792969s
Security | Check HTTPS for Apertium RDF EO-FR took 0.11966991424560547s
Interpretability | RDF structures check for Apertium RDF EO-FR took 0.32239627838134766s
Versatility | Serialization formats check for Apertium RDF EO-FR took 0.2878682613372803s
Availability | RDF dump link check for Apertium RDF EO-FR took 0.3258235454559326s
License | MR license check for Apertium RDF EO-FR took 0.29361486434936523s
License | HR license check for Apertium RDF EO-FR took 0.3589661121368408s
Amount of data | Number of property check for Apertium RDF EO-FR took 0.28669095039367676s
Understandability | Number of label check for Apertium RDF EO-FR took 0.3363158702850342s
Understandability | URI regex check for Apertium RDF EO-FR took 0.6023833751678467s
Understandability | Vocabs check for Apertium RDF EO-FR took 0.31213879585266113s
Verifiability | Authors check for Apertium RDF EO-FR took 0.33919858932495117s
Verifiability | Publishers check for Apertium RDF EO-FR took 0.3078606128692627s
Performance | Throughput check for Apertium RDF EO-FR took 11.855926990509033s
Amount of data | Check the number of entities for Apertium RDF EO-FR took 8.58306884765625e-05s
Verifiability | Contribs. check for Apertium RDF EO-FR took 0.2654585838317871s
Interlinking | sameAs chians check for Apertium RDF EO-FR took 0.28299903869628906s
Interlinking | skos check for Apertium RDF EO-FR took 0.2667253017425537s
Interlinking | skos check for Apertium RDF EO-FR took 0.21718049049377441s
Timeliness | dataset update frequency check for Apertium RDF EO-FR took 0.31717872619628906s
Currency | Creation date check for Apertium RDF EO-FR took 0.2949645519256592s
Currency | Modification date check for Apertium RDF EO-FR took 0.31926918029785156s
Rep.Conc. | URIs length for Apertium RDF EO-FR took 91.73944282531738s
Interoperability | New vocabularies check for Apertium RDF EO-FR took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EO-FR took 0.32483792304992676s
Accuracy | Check Functional Property for Apertium RDF EO-FR took 0.3272085189819336s
Accuracy | Check Inverse Functional Property for Apertium RDF EO-FR took 0.29628682136535645s
Accuracy | Check Empty annotation labels for Apertium RDF EO-FR took 0.7923212051391602s
Accuracy | Check White space in annotation for Apertium RDF EO-FR took 0.009917259216308594s
Accuracy | Check Datatype consistency for Apertium RDF EO-FR took 2.6557188034057617s
Consistency | Disjoint class check for Apertium RDF EO-FR took 0.32508325576782227s
Consistency | Check Misplaced properties for Apertium RDF EO-FR took 4.774094820022583s
Consistency | Misplaced classes for Apertium RDF EO-FR took 8.433563232421875s
Consistency | Check Ontology hijacking for Apertium RDF EO-FR took 85.78182983398438s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EO-FR took 1.5683460235595703s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EO-FR took 5.796786546707153s
Conciseness | Check Extensional conciseness for Apertium RDF EO-FR took 3.1428616046905518s
Conciseness | Check Intensional conciseness for Apertium RDF EO-FR took 0.32571887969970703s
Security | Sign check for Apertium RDF EO-FR took 0.2835695743560791s
Availability | Check URIs Dereferenciability for Apertium RDF EO-FR took 20.1874680519104s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.616809606552124s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.021266698837280273s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 5.14984130859375e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EO-FR took 1.9073486328125e-06s
Believability | Calculation of trust value for Apertium RDF EO-FR took 1.430511474609375e-05s
INFO | --- Analysis for apertium-rdf-eo-fr took 672.9926126003265s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 0.20311260223388672s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.00046944618225097656s
Extra | Recovery of all triples for Apertium RDF ES-AN took 294.93166303634644s
Performance | Total latancy measurement for Apertium RDF ES-AN took 1.3277583122253418s
Amount of data | Number of triples check for Apertium RDF ES-AN took 2.1253104209899902s
Interoperability | New terms check for Apertium RDF ES-AN took 3.146191120147705s
Versatility | Languages check for Apertium RDF ES-AN took 44.192596197128296s
Interpretability | Number of blank nodes check for Apertium RDF ES-AN took 1.093276023864746s
Security | Check HTTPS for Apertium RDF ES-AN took 0.14787721633911133s
Interpretability | RDF structures check for Apertium RDF ES-AN took 0.3110029697418213s
Versatility | Serialization formats check for Apertium RDF ES-AN took 0.3207080364227295s
Availability | RDF dump link check for Apertium RDF ES-AN took 0.27863597869873047s
License | MR license check for Apertium RDF ES-AN took 0.31140613555908203s
License | HR license check for Apertium RDF ES-AN took 0.4020802974700928s
Amount of data | Number of property check for Apertium RDF ES-AN took 0.28797197341918945s
Understandability | Number of label check for Apertium RDF ES-AN took 0.3181445598602295s
Understandability | URI regex check for Apertium RDF ES-AN took 0.6160240173339844s
Understandability | Vocabs check for Apertium RDF ES-AN took 0.3220348358154297s
Verifiability | Authors check for Apertium RDF ES-AN took 0.33817625045776367s
Verifiability | Publishers check for Apertium RDF ES-AN took 0.29853129386901855s
Performance | Throughput check for Apertium RDF ES-AN took 11.654724597930908s
Amount of data | Check the number of entities for Apertium RDF ES-AN took 8.988380432128906e-05s
Verifiability | Contribs. check for Apertium RDF ES-AN took 0.30814528465270996s
Interlinking | sameAs chians check for Apertium RDF ES-AN took 0.31848883628845215s
Interlinking | skos check for Apertium RDF ES-AN took 0.3193964958190918s
Interlinking | skos check for Apertium RDF ES-AN took 0.2227928638458252s
Timeliness | dataset update frequency check for Apertium RDF ES-AN took 0.27698779106140137s
Currency | Creation date check for Apertium RDF ES-AN took 0.3356311321258545s
Currency | Modification date check for Apertium RDF ES-AN took 0.28014373779296875s
Rep.Conc. | URIs length for Apertium RDF ES-AN took 87.56950426101685s
Interoperability | New vocabularies check for Apertium RDF ES-AN took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-AN took 0.29409098625183105s
Accuracy | Check Functional Property for Apertium RDF ES-AN took 0.32065701484680176s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-AN took 0.32771730422973633s
Accuracy | Check Empty annotation labels for Apertium RDF ES-AN took 0.9589362144470215s
Accuracy | Check White space in annotation for Apertium RDF ES-AN took 0.010296106338500977s
Accuracy | Check Datatype consistency for Apertium RDF ES-AN took 2.641382932662964s
Consistency | Disjoint class check for Apertium RDF ES-AN took 0.3358912467956543s
Consistency | Check Misplaced properties for Apertium RDF ES-AN took 4.673580646514893s
Consistency | Misplaced classes for Apertium RDF ES-AN took 8.341906070709229s
Consistency | Check Ontology hijacking for Apertium RDF ES-AN took 98.46694612503052s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-AN took 1.525740385055542s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-AN took 5.796501159667969s
Conciseness | Check Extensional conciseness for Apertium RDF ES-AN took 3.1000473499298096s
Conciseness | Check Intensional conciseness for Apertium RDF ES-AN took 0.3203144073486328s
Security | Sign check for Apertium RDF ES-AN took 0.30811476707458496s
Availability | Check URIs Dereferenciability for Apertium RDF ES-AN took 3.704022169113159s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.39466238021850586s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.020852088928222656s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 5.269050598144531e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-AN took 1.9073486328125e-06s
Believability | Calculation of trust value for Apertium RDF ES-AN took 1.1682510375976562e-05s
INFO | --- Analysis for apertium-rdf-es-an took 649.101799249649s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 0.2658250331878662s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0004296302795410156s
Extra | Recovery of all triples for Apertium RDF ES-AST took 253.32637405395508s
Performance | Total latancy measurement for Apertium RDF ES-AST took 1.380666732788086s
Amount of data | Number of triples check for Apertium RDF ES-AST took 2.2852091789245605s
Interoperability | New terms check for Apertium RDF ES-AST took 3.1723477840423584s
Versatility | Languages check for Apertium RDF ES-AST took 43.93054938316345s
Interpretability | Number of blank nodes check for Apertium RDF ES-AST took 1.1272947788238525s
Security | Check HTTPS for Apertium RDF ES-AST took 0.17437148094177246s
Interpretability | RDF structures check for Apertium RDF ES-AST took 0.28135037422180176s
Versatility | Serialization formats check for Apertium RDF ES-AST took 0.2946665287017822s
Availability | RDF dump link check for Apertium RDF ES-AST took 0.29509449005126953s
License | MR license check for Apertium RDF ES-AST took 0.2914316654205322s
License | HR license check for Apertium RDF ES-AST took 0.39884519577026367s
Amount of data | Number of property check for Apertium RDF ES-AST took 0.3150060176849365s
Understandability | Number of label check for Apertium RDF ES-AST took 0.3388245105743408s
Understandability | URI regex check for Apertium RDF ES-AST took 0.6270360946655273s
Understandability | Vocabs check for Apertium RDF ES-AST took 0.30224037170410156s
Verifiability | Authors check for Apertium RDF ES-AST took 0.35256218910217285s
Verifiability | Publishers check for Apertium RDF ES-AST took 0.3056013584136963s
Performance | Throughput check for Apertium RDF ES-AST took 11.76742172241211s
Amount of data | Check the number of entities for Apertium RDF ES-AST took 3.814697265625e-05s
Verifiability | Contribs. check for Apertium RDF ES-AST took 0.30857324600219727s
Interlinking | sameAs chians check for Apertium RDF ES-AST took 0.3277242183685303s
Interlinking | skos check for Apertium RDF ES-AST took 0.3120079040527344s
Interlinking | skos check for Apertium RDF ES-AST took 0.2501797676086426s
Timeliness | dataset update frequency check for Apertium RDF ES-AST took 0.2850799560546875s
Currency | Creation date check for Apertium RDF ES-AST took 0.3418853282928467s
Currency | Modification date check for Apertium RDF ES-AST took 0.2962491512298584s
Rep.Conc. | URIs length for Apertium RDF ES-AST took 95.65656423568726s
Interoperability | New vocabularies check for Apertium RDF ES-AST took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-AST took 0.3205118179321289s
Accuracy | Check Functional Property for Apertium RDF ES-AST took 0.3040506839752197s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-AST took 0.3276548385620117s
Accuracy | Check Empty annotation labels for Apertium RDF ES-AST took 0.87961745262146s
Accuracy | Check White space in annotation for Apertium RDF ES-AST took 0.010284900665283203s
Accuracy | Check Datatype consistency for Apertium RDF ES-AST took 2.6323986053466797s
Consistency | Disjoint class check for Apertium RDF ES-AST took 0.31171321868896484s
Consistency | Check Misplaced properties for Apertium RDF ES-AST took 4.7616894245147705s
Consistency | Misplaced classes for Apertium RDF ES-AST took 8.379512310028076s
Consistency | Check Ontology hijacking for Apertium RDF ES-AST took 98.52970957756042s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-AST took 1.5687861442565918s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-AST took 5.7264204025268555s
Conciseness | Check Extensional conciseness for Apertium RDF ES-AST took 3.2492177486419678s
Conciseness | Check Intensional conciseness for Apertium RDF ES-AST took 0.3259878158569336s
Security | Sign check for Apertium RDF ES-AST took 0.3138613700866699s
Availability | Check URIs Dereferenciability for Apertium RDF ES-AST took 3.839522361755371s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.5472431182861328s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.020917892456054688s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 5.125999450683594e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-AST took 1.430511474609375e-06s
Believability | Calculation of trust value for Apertium RDF ES-AST took 1.430511474609375e-05s
INFO | --- Analysis for apertium-rdf-es-ast took 620.689112663269s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 0.23309803009033203s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.0002532005310058594s
Extra | Recovery of all triples for Apertium RDF ES-CA took 268.4161546230316s
Performance | Total latancy measurement for Apertium RDF ES-CA took 1.2320194244384766s
Amount of data | Number of triples check for Apertium RDF ES-CA took 2.1149425506591797s
Interoperability | New terms check for Apertium RDF ES-CA took 3.0884764194488525s
Versatility | Languages check for Apertium RDF ES-CA took 44.499839067459106s
Interpretability | Number of blank nodes check for Apertium RDF ES-CA took 1.2254350185394287s
Security | Check HTTPS for Apertium RDF ES-CA took 0.14756035804748535s
Interpretability | RDF structures check for Apertium RDF ES-CA took 0.307952880859375s
Versatility | Serialization formats check for Apertium RDF ES-CA took 0.3236575126647949s
Availability | RDF dump link check for Apertium RDF ES-CA took 0.27569580078125s
License | MR license check for Apertium RDF ES-CA took 0.28513383865356445s
License | HR license check for Apertium RDF ES-CA took 0.3873147964477539s
Amount of data | Number of property check for Apertium RDF ES-CA took 0.29173898696899414s
Understandability | Number of label check for Apertium RDF ES-CA took 0.3630180358886719s
Understandability | URI regex check for Apertium RDF ES-CA took 0.6634948253631592s
Understandability | Vocabs check for Apertium RDF ES-CA took 0.28388214111328125s
Verifiability | Authors check for Apertium RDF ES-CA took 0.350994348526001s
Verifiability | Publishers check for Apertium RDF ES-CA took 0.2953460216522217s
Performance | Throughput check for Apertium RDF ES-CA took 11.894930839538574s
Amount of data | Check the number of entities for Apertium RDF ES-CA took 0.0005774497985839844s
Verifiability | Contribs. check for Apertium RDF ES-CA took 0.31026172637939453s
Interlinking | sameAs chians check for Apertium RDF ES-CA took 0.2930419445037842s
Interlinking | skos check for Apertium RDF ES-CA took 0.3147275447845459s
Interlinking | skos check for Apertium RDF ES-CA took 0.25072550773620605s
Timeliness | dataset update frequency check for Apertium RDF ES-CA took 0.2988395690917969s
Currency | Creation date check for Apertium RDF ES-CA took 0.3089172840118408s
Currency | Modification date check for Apertium RDF ES-CA took 0.30283570289611816s
Rep.Conc. | URIs length for Apertium RDF ES-CA took 95.35823369026184s
Interoperability | New vocabularies check for Apertium RDF ES-CA took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-CA took 0.33307576179504395s
Accuracy | Check Functional Property for Apertium RDF ES-CA took 0.33189845085144043s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-CA took 0.2895948886871338s
Accuracy | Check Empty annotation labels for Apertium RDF ES-CA took 0.9187250137329102s
Accuracy | Check White space in annotation for Apertium RDF ES-CA took 0.010306596755981445s
Accuracy | Check Datatype consistency for Apertium RDF ES-CA took 2.7390952110290527s
Consistency | Disjoint class check for Apertium RDF ES-CA took 0.2678496837615967s
Consistency | Check Misplaced properties for Apertium RDF ES-CA took 4.67447829246521s
Consistency | Misplaced classes for Apertium RDF ES-CA took 8.434886693954468s
Consistency | Check Ontology hijacking for Apertium RDF ES-CA took 93.57451272010803s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-CA took 1.5662295818328857s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-CA took 5.8179285526275635s
Conciseness | Check Extensional conciseness for Apertium RDF ES-CA took 3.1344375610351562s
Conciseness | Check Intensional conciseness for Apertium RDF ES-CA took 0.37935543060302734s
Security | Sign check for Apertium RDF ES-CA took 0.2903144359588623s
Availability | Check URIs Dereferenciability for Apertium RDF ES-CA took 3.860583543777466s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 2.782715320587158s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.020875215530395508s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 5.340576171875e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-CA took 1.9073486328125e-06s
Believability | Calculation of trust value for Apertium RDF ES-CA took 1.4066696166992188e-05s
INFO | --- Analysis for apertium-rdf-es-ca took 655.5782177448273s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 0.24791193008422852s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.0004494190216064453s
Extra | Recovery of all triples for Apertium RDF ES-GL took 250.64444375038147s
Performance | Total latancy measurement for Apertium RDF ES-GL took 1.451582670211792s
Amount of data | Number of triples check for Apertium RDF ES-GL took 2.2113864421844482s
Interoperability | New terms check for Apertium RDF ES-GL took 2.916679620742798s
Versatility | Languages check for Apertium RDF ES-GL took 43.87827396392822s
Interpretability | Number of blank nodes check for Apertium RDF ES-GL took 1.2289769649505615s
Security | Check HTTPS for Apertium RDF ES-GL took 0.16379189491271973s
Interpretability | RDF structures check for Apertium RDF ES-GL took 0.28618764877319336s
Versatility | Serialization formats check for Apertium RDF ES-GL took 0.28409624099731445s
Availability | RDF dump link check for Apertium RDF ES-GL took 0.2854268550872803s
License | MR license check for Apertium RDF ES-GL took 0.29410290718078613s
License | HR license check for Apertium RDF ES-GL took 0.4104478359222412s
Amount of data | Number of property check for Apertium RDF ES-GL took 0.299025297164917s
Understandability | Number of label check for Apertium RDF ES-GL took 0.3395397663116455s
Understandability | URI regex check for Apertium RDF ES-GL took 0.6004219055175781s
Understandability | Vocabs check for Apertium RDF ES-GL took 0.31473851203918457s
Verifiability | Authors check for Apertium RDF ES-GL took 0.31029415130615234s
Verifiability | Publishers check for Apertium RDF ES-GL took 0.311417818069458s
Performance | Throughput check for Apertium RDF ES-GL took 11.32420539855957s
Amount of data | Check the number of entities for Apertium RDF ES-GL took 8.940696716308594e-05s
Verifiability | Contribs. check for Apertium RDF ES-GL took 0.2935607433319092s
Interlinking | sameAs chians check for Apertium RDF ES-GL took 0.3090779781341553s
Interlinking | skos check for Apertium RDF ES-GL took 0.32706570625305176s
Interlinking | skos check for Apertium RDF ES-GL took 0.26705121994018555s
Timeliness | dataset update frequency check for Apertium RDF ES-GL took 0.30385589599609375s
Currency | Creation date check for Apertium RDF ES-GL took 0.34047532081604004s
Currency | Modification date check for Apertium RDF ES-GL took 0.2862699031829834s
Rep.Conc. | URIs length for Apertium RDF ES-GL took 101.10564923286438s
Interoperability | New vocabularies check for Apertium RDF ES-GL took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-GL took 0.3660404682159424s
Accuracy | Check Functional Property for Apertium RDF ES-GL took 0.3141059875488281s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-GL took 0.2982020378112793s
Accuracy | Check Empty annotation labels for Apertium RDF ES-GL took 1.5432884693145752s
Accuracy | Check White space in annotation for Apertium RDF ES-GL took 0.009925365447998047s
Accuracy | Check Datatype consistency for Apertium RDF ES-GL took 2.7765681743621826s
Consistency | Disjoint class check for Apertium RDF ES-GL took 0.29616284370422363s
Consistency | Check Misplaced properties for Apertium RDF ES-GL took 4.561847686767578s
Consistency | Misplaced classes for Apertium RDF ES-GL took 8.584315061569214s
Consistency | Check Ontology hijacking for Apertium RDF ES-GL took 99.00991559028625s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-GL took 1.4944751262664795s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-GL took 5.706679105758667s
Conciseness | Check Extensional conciseness for Apertium RDF ES-GL took 3.1073994636535645s
Conciseness | Check Intensional conciseness for Apertium RDF ES-GL took 0.35575151443481445s
Security | Sign check for Apertium RDF ES-GL took 0.31742382049560547s
Availability | Check URIs Dereferenciability for Apertium RDF ES-GL took 3.5322399139404297s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.409329891204834s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.020887136459350586s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 4.792213439941406e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-GL took 1.9073486328125e-06s
Believability | Calculation of trust value for Apertium RDF ES-GL took 1.0967254638671875e-05s
INFO | --- Analysis for apertium-rdf-es-gl took 635.8433010578156s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 0.2407057285308838s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.0004928112030029297s
Extra | Recovery of all triples for Apertium RDF ES-PT took 250.11977529525757s
Performance | Total latancy measurement for Apertium RDF ES-PT took 1.3004026412963867s
Amount of data | Number of triples check for Apertium RDF ES-PT took 2.141697645187378s
Interoperability | New terms check for Apertium RDF ES-PT took 3.096038341522217s
Versatility | Languages check for Apertium RDF ES-PT took 44.119298458099365s
Interpretability | Number of blank nodes check for Apertium RDF ES-PT took 1.1627309322357178s
Security | Check HTTPS for Apertium RDF ES-PT took 0.14791035652160645s
Interpretability | RDF structures check for Apertium RDF ES-PT took 0.3393561840057373s
Versatility | Serialization formats check for Apertium RDF ES-PT took 0.3092024326324463s
Availability | RDF dump link check for Apertium RDF ES-PT took 0.3338661193847656s
License | MR license check for Apertium RDF ES-PT took 0.3091762065887451s
License | HR license check for Apertium RDF ES-PT took 0.40938735008239746s
Amount of data | Number of property check for Apertium RDF ES-PT took 0.30976366996765137s
Understandability | Number of label check for Apertium RDF ES-PT took 0.35159850120544434s
Understandability | URI regex check for Apertium RDF ES-PT took 0.6228976249694824s
Understandability | Vocabs check for Apertium RDF ES-PT took 0.3052818775177002s
Verifiability | Authors check for Apertium RDF ES-PT took 0.3634965419769287s
Verifiability | Publishers check for Apertium RDF ES-PT took 0.28134727478027344s
Performance | Throughput check for Apertium RDF ES-PT took 11.770222902297974s
Amount of data | Check the number of entities for Apertium RDF ES-PT took 3.9577484130859375e-05s
Verifiability | Contribs. check for Apertium RDF ES-PT took 0.27884674072265625s
Interlinking | sameAs chians check for Apertium RDF ES-PT took 0.319256067276001s
Interlinking | skos check for Apertium RDF ES-PT took 0.2953810691833496s
Interlinking | skos check for Apertium RDF ES-PT took 0.2723057270050049s
Timeliness | dataset update frequency check for Apertium RDF ES-PT took 0.35356736183166504s
Currency | Creation date check for Apertium RDF ES-PT took 0.30602216720581055s
Currency | Modification date check for Apertium RDF ES-PT took 0.2986607551574707s
Rep.Conc. | URIs length for Apertium RDF ES-PT took 92.7198007106781s
Interoperability | New vocabularies check for Apertium RDF ES-PT took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-PT took 0.34059572219848633s
Accuracy | Check Functional Property for Apertium RDF ES-PT took 0.3298776149749756s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-PT took 0.30916547775268555s
Accuracy | Check Empty annotation labels for Apertium RDF ES-PT took 0.9421079158782959s
Accuracy | Check White space in annotation for Apertium RDF ES-PT took 0.009956836700439453s
Accuracy | Check Datatype consistency for Apertium RDF ES-PT took 2.794154167175293s
Consistency | Disjoint class check for Apertium RDF ES-PT took 0.27776002883911133s
Consistency | Check Misplaced properties for Apertium RDF ES-PT took 4.706082344055176s
Consistency | Misplaced classes for Apertium RDF ES-PT took 8.583904266357422s
Consistency | Check Ontology hijacking for Apertium RDF ES-PT took 92.65202903747559s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-PT took 1.5722196102142334s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-PT took 5.744468927383423s
Conciseness | Check Extensional conciseness for Apertium RDF ES-PT took 3.0896756649017334s
Conciseness | Check Intensional conciseness for Apertium RDF ES-PT took 0.34978246688842773s
Security | Sign check for Apertium RDF ES-PT took 0.2968926429748535s
Availability | Check URIs Dereferenciability for Apertium RDF ES-PT took 4.035210847854614s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.483414888381958s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.021625041961669922s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 5.030632019042969e-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 1.3828277587890625e-05s
INFO | --- Analysis for apertium-rdf-es-pt took 610.2212131023407s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 0.24612021446228027s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.0008325576782226562s
Extra | Recovery of all triples for Apertium RDF ES-RO took 275.2661716938019s
Performance | Total latancy measurement for Apertium RDF ES-RO took 1.3490679264068604s
Amount of data | Number of triples check for Apertium RDF ES-RO took 2.2072572708129883s
Interoperability | New terms check for Apertium RDF ES-RO took 3.0762009620666504s
Versatility | Languages check for Apertium RDF ES-RO took 44.79455018043518s
Interpretability | Number of blank nodes check for Apertium RDF ES-RO took 1.1081602573394775s
Security | Check HTTPS for Apertium RDF ES-RO took 0.1500682830810547s
Interpretability | RDF structures check for Apertium RDF ES-RO took 0.2716813087463379s
Versatility | Serialization formats check for Apertium RDF ES-RO took 0.30518198013305664s
Availability | RDF dump link check for Apertium RDF ES-RO took 0.28322672843933105s
License | MR license check for Apertium RDF ES-RO took 0.3138918876647949s
License | HR license check for Apertium RDF ES-RO took 0.393817663192749s
Amount of data | Number of property check for Apertium RDF ES-RO took 0.30745482444763184s
Understandability | Number of label check for Apertium RDF ES-RO took 0.34854912757873535s
Understandability | URI regex check for Apertium RDF ES-RO took 0.5971448421478271s
Understandability | Vocabs check for Apertium RDF ES-RO took 0.3433570861816406s
Verifiability | Authors check for Apertium RDF ES-RO took 0.35725998878479004s
Verifiability | Publishers check for Apertium RDF ES-RO took 0.26808977127075195s
Performance | Throughput check for Apertium RDF ES-RO took 11.484144449234009s
Amount of data | Check the number of entities for Apertium RDF ES-RO took 0.0001068115234375s
Verifiability | Contribs. check for Apertium RDF ES-RO took 0.3267490863800049s
Interlinking | sameAs chians check for Apertium RDF ES-RO took 0.29563093185424805s
Interlinking | skos check for Apertium RDF ES-RO took 0.29711246490478516s
Interlinking | skos check for Apertium RDF ES-RO took 0.25706958770751953s
Timeliness | dataset update frequency check for Apertium RDF ES-RO took 0.31244492530822754s
Currency | Creation date check for Apertium RDF ES-RO took 0.30719470977783203s
Currency | Modification date check for Apertium RDF ES-RO took 0.30953407287597656s
Rep.Conc. | URIs length for Apertium RDF ES-RO took 93.19163513183594s
Interoperability | New vocabularies check for Apertium RDF ES-RO took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-RO took 0.3434627056121826s
Accuracy | Check Functional Property for Apertium RDF ES-RO took 0.2940387725830078s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-RO took 0.33724308013916016s
Accuracy | Check Empty annotation labels for Apertium RDF ES-RO took 0.9193644523620605s
Accuracy | Check White space in annotation for Apertium RDF ES-RO took 0.00995945930480957s
Accuracy | Check Datatype consistency for Apertium RDF ES-RO took 2.6682333946228027s
Consistency | Disjoint class check for Apertium RDF ES-RO took 0.3219726085662842s
Consistency | Check Misplaced properties for Apertium RDF ES-RO took 4.7242138385772705s
Consistency | Misplaced classes for Apertium RDF ES-RO took 8.499617338180542s
Consistency | Check Ontology hijacking for Apertium RDF ES-RO took 93.9394941329956s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-RO took 1.4937794208526611s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-RO took 5.6452789306640625s
Conciseness | Check Extensional conciseness for Apertium RDF ES-RO took 3.0793662071228027s
Conciseness | Check Intensional conciseness for Apertium RDF ES-RO took 0.30791807174682617s
Security | Sign check for Apertium RDF ES-RO took 0.2821383476257324s
Availability | Check URIs Dereferenciability for Apertium RDF ES-RO took 20.19255304336548s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.6917970180511475s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.02099919319152832s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 5.1021575927734375e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-RO took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF ES-RO took 1.4066696166992188e-05s
INFO | --- Analysis for apertium-rdf-es-ro took 661.7706544399261s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 0.21188616752624512s
Availability | VoID file availability check for Apertium RDF EU-EN took 0.000446319580078125s
Extra | Recovery of all triples for Apertium RDF EU-EN took 253.63787937164307s
Performance | Total latancy measurement for Apertium RDF EU-EN took 1.3966002464294434s
Amount of data | Number of triples check for Apertium RDF EU-EN took 2.120891571044922s
Interoperability | New terms check for Apertium RDF EU-EN took 3.113973617553711s
Versatility | Languages check for Apertium RDF EU-EN took 44.375937700271606s
Interpretability | Number of blank nodes check for Apertium RDF EU-EN took 1.272890567779541s
Security | Check HTTPS for Apertium RDF EU-EN took 0.17634177207946777s
Interpretability | RDF structures check for Apertium RDF EU-EN took 0.3453683853149414s
Versatility | Serialization formats check for Apertium RDF EU-EN took 0.3142693042755127s
Availability | RDF dump link check for Apertium RDF EU-EN took 0.31806373596191406s
License | MR license check for Apertium RDF EU-EN took 0.28553247451782227s
License | HR license check for Apertium RDF EU-EN took 0.3699321746826172s
Amount of data | Number of property check for Apertium RDF EU-EN took 0.2982206344604492s
Understandability | Number of label check for Apertium RDF EU-EN took 0.3754150867462158s
Understandability | URI regex check for Apertium RDF EU-EN took 0.6204438209533691s
Understandability | Vocabs check for Apertium RDF EU-EN took 0.33892130851745605s
Verifiability | Authors check for Apertium RDF EU-EN took 0.3269033432006836s
Verifiability | Publishers check for Apertium RDF EU-EN took 0.32697606086730957s
Performance | Throughput check for Apertium RDF EU-EN took 12.013604879379272s
Amount of data | Check the number of entities for Apertium RDF EU-EN took 9.179115295410156e-05s
Verifiability | Contribs. check for Apertium RDF EU-EN took 0.2883296012878418s
Interlinking | sameAs chians check for Apertium RDF EU-EN took 0.28626513481140137s
Interlinking | skos check for Apertium RDF EU-EN took 0.31651973724365234s
Interlinking | skos check for Apertium RDF EU-EN took 0.26064014434814453s
Timeliness | dataset update frequency check for Apertium RDF EU-EN took 0.33152079582214355s
Currency | Creation date check for Apertium RDF EU-EN took 0.28163695335388184s
Currency | Modification date check for Apertium RDF EU-EN took 0.29111385345458984s
Rep.Conc. | URIs length for Apertium RDF EU-EN took 92.31185030937195s
Interoperability | New vocabularies check for Apertium RDF EU-EN took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EU-EN took 0.35187363624572754s
Accuracy | Check Functional Property for Apertium RDF EU-EN took 0.30287671089172363s
Accuracy | Check Inverse Functional Property for Apertium RDF EU-EN took 0.33945393562316895s
Accuracy | Check Empty annotation labels for Apertium RDF EU-EN took 0.8029839992523193s
Accuracy | Check White space in annotation for Apertium RDF EU-EN took 0.010101795196533203s
Accuracy | Check Datatype consistency for Apertium RDF EU-EN took 2.6541800498962402s
Consistency | Disjoint class check for Apertium RDF EU-EN took 0.32588934898376465s
Consistency | Check Misplaced properties for Apertium RDF EU-EN took 4.725895166397095s
Consistency | Misplaced classes for Apertium RDF EU-EN took 8.500715970993042s
Consistency | Check Ontology hijacking for Apertium RDF EU-EN took 99.09653854370117s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EU-EN took 1.5008459091186523s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EU-EN took 5.732705354690552s
Conciseness | Check Extensional conciseness for Apertium RDF EU-EN took 3.088261365890503s
Conciseness | Check Intensional conciseness for Apertium RDF EU-EN took 0.33673882484436035s
Security | Sign check for Apertium RDF EU-EN took 0.33223462104797363s
Availability | Check URIs Dereferenciability for Apertium RDF EU-EN took 3.645634889602661s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.49245262145996094s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.02106475830078125s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 5.1975250244140625e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EU-EN took 1.9073486328125e-06s
Believability | Calculation of trust value for Apertium RDF EU-EN took 1.2636184692382812e-05s
INFO | --- Analysis for apertium-rdf-eu-en took 616.6809988021851s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 0.24500632286071777s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.0004253387451171875s
Extra | Recovery of all triples for Apertium RDF EU-ES took 252.79899191856384s
Performance | Total latancy measurement for Apertium RDF EU-ES took 1.3313701152801514s
Amount of data | Number of triples check for Apertium RDF EU-ES took 2.21716570854187s
Interoperability | New terms check for Apertium RDF EU-ES took 2.9532828330993652s
Versatility | Languages check for Apertium RDF EU-ES took 43.90563440322876s
Interpretability | Number of blank nodes check for Apertium RDF EU-ES took 1.1261248588562012s
Security | Check HTTPS for Apertium RDF EU-ES took 0.1469724178314209s
Interpretability | RDF structures check for Apertium RDF EU-ES took 0.3129458427429199s
Versatility | Serialization formats check for Apertium RDF EU-ES took 0.29164576530456543s
Availability | RDF dump link check for Apertium RDF EU-ES took 0.2755274772644043s
License | MR license check for Apertium RDF EU-ES took 0.3383471965789795s
License | HR license check for Apertium RDF EU-ES took 0.38622069358825684s
Amount of data | Number of property check for Apertium RDF EU-ES took 0.3454163074493408s
Understandability | Number of label check for Apertium RDF EU-ES took 0.35155487060546875s
Understandability | URI regex check for Apertium RDF EU-ES took 0.6701509952545166s
Understandability | Vocabs check for Apertium RDF EU-ES took 0.291445255279541s
Verifiability | Authors check for Apertium RDF EU-ES took 0.3026726245880127s
Verifiability | Publishers check for Apertium RDF EU-ES took 0.28255343437194824s
Performance | Throughput check for Apertium RDF EU-ES took 12.520188808441162s
Amount of data | Check the number of entities for Apertium RDF EU-ES took 8.749961853027344e-05s
Verifiability | Contribs. check for Apertium RDF EU-ES took 0.2907242774963379s
Interlinking | sameAs chians check for Apertium RDF EU-ES took 0.3198738098144531s
Interlinking | skos check for Apertium RDF EU-ES took 0.27780771255493164s
Interlinking | skos check for Apertium RDF EU-ES took 0.22369885444641113s
Timeliness | dataset update frequency check for Apertium RDF EU-ES took 0.32586097717285156s
Currency | Creation date check for Apertium RDF EU-ES took 0.2719457149505615s
Currency | Modification date check for Apertium RDF EU-ES took 0.2945585250854492s
Rep.Conc. | URIs length for Apertium RDF EU-ES took 101.51973915100098s
Interoperability | New vocabularies check for Apertium RDF EU-ES took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF EU-ES took 0.3479454517364502s
Accuracy | Check Functional Property for Apertium RDF EU-ES took 0.3147315979003906s
Accuracy | Check Inverse Functional Property for Apertium RDF EU-ES took 0.31267428398132324s
Accuracy | Check Empty annotation labels for Apertium RDF EU-ES took 0.9364025592803955s
Accuracy | Check White space in annotation for Apertium RDF EU-ES took 0.009958505630493164s
Accuracy | Check Datatype consistency for Apertium RDF EU-ES took 2.644145965576172s
Consistency | Disjoint class check for Apertium RDF EU-ES took 0.3040883541107178s
Consistency | Check Misplaced properties for Apertium RDF EU-ES took 5.01421332359314s
Consistency | Misplaced classes for Apertium RDF EU-ES took 8.310938119888306s
Consistency | Check Ontology hijacking for Apertium RDF EU-ES took 101.28995656967163s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EU-ES took 1.6192574501037598s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EU-ES took 5.776391267776489s
Conciseness | Check Extensional conciseness for Apertium RDF EU-ES took 3.2384018898010254s
Conciseness | Check Intensional conciseness for Apertium RDF EU-ES took 0.3471829891204834s
Security | Sign check for Apertium RDF EU-ES took 0.2823810577392578s
Availability | Check URIs Dereferenciability for Apertium RDF EU-ES took 4.025163173675537s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.40143513679504395s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.02112722396850586s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 5.745887756347656e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EU-ES took 1.9073486328125e-06s
Believability | Calculation of trust value for Apertium RDF EU-ES took 1.3589859008789062e-05s
INFO | --- Analysis for apertium-rdf-eu-es took 633.9969818592072s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 0.278728723526001s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.0008380413055419922s
Extra | Recovery of all triples for Apertium RDF FR-CA took 279.95702934265137s
Performance | Total latancy measurement for Apertium RDF FR-CA took 1.3596069812774658s
Amount of data | Number of triples check for Apertium RDF FR-CA took 2.287724494934082s
Interoperability | New terms check for Apertium RDF FR-CA took 2.9116482734680176s
Versatility | Languages check for Apertium RDF FR-CA took 44.11674952507019s
Interpretability | Number of blank nodes check for Apertium RDF FR-CA took 1.084488868713379s
Security | Check HTTPS for Apertium RDF FR-CA took 0.15235161781311035s
Interpretability | RDF structures check for Apertium RDF FR-CA took 0.3015460968017578s
Versatility | Serialization formats check for Apertium RDF FR-CA took 0.5420529842376709s
Availability | RDF dump link check for Apertium RDF FR-CA took 0.31708335876464844s
License | MR license check for Apertium RDF FR-CA took 0.30476856231689453s
License | HR license check for Apertium RDF FR-CA took 0.3600306510925293s
Amount of data | Number of property check for Apertium RDF FR-CA took 0.2833976745605469s
Understandability | Number of label check for Apertium RDF FR-CA took 0.3367645740509033s
Understandability | URI regex check for Apertium RDF FR-CA took 0.633756160736084s
Understandability | Vocabs check for Apertium RDF FR-CA took 0.32775092124938965s
Verifiability | Authors check for Apertium RDF FR-CA took 0.3401956558227539s
Verifiability | Publishers check for Apertium RDF FR-CA took 0.31920528411865234s
Performance | Throughput check for Apertium RDF FR-CA took 11.846765756607056s
Amount of data | Check the number of entities for Apertium RDF FR-CA took 9.298324584960938e-05s
Verifiability | Contribs. check for Apertium RDF FR-CA took 0.2864847183227539s
Interlinking | sameAs chians check for Apertium RDF FR-CA took 0.29389429092407227s
Interlinking | skos check for Apertium RDF FR-CA took 0.2850956916809082s
Interlinking | skos check for Apertium RDF FR-CA took 0.2676825523376465s
Timeliness | dataset update frequency check for Apertium RDF FR-CA took 0.29512572288513184s
Currency | Creation date check for Apertium RDF FR-CA took 0.3110835552215576s
Currency | Modification date check for Apertium RDF FR-CA took 0.30286550521850586s
Rep.Conc. | URIs length for Apertium RDF FR-CA took 101.22404193878174s
Interoperability | New vocabularies check for Apertium RDF FR-CA took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF FR-CA took 0.3265712261199951s
Accuracy | Check Functional Property for Apertium RDF FR-CA took 0.2990078926086426s
Accuracy | Check Inverse Functional Property for Apertium RDF FR-CA took 0.27651429176330566s
Accuracy | Check Empty annotation labels for Apertium RDF FR-CA took 0.8558475971221924s
Accuracy | Check White space in annotation for Apertium RDF FR-CA took 0.010135412216186523s
Accuracy | Check Datatype consistency for Apertium RDF FR-CA took 2.6357810497283936s
Consistency | Disjoint class check for Apertium RDF FR-CA took 0.3076286315917969s
Consistency | Check Misplaced properties for Apertium RDF FR-CA took 4.728119134902954s
Consistency | Misplaced classes for Apertium RDF FR-CA took 8.426518201828003s
Consistency | Check Ontology hijacking for Apertium RDF FR-CA took 104.77642226219177s
Consistency | Check Invalid usage of undefined classes for Apertium RDF FR-CA took 1.6202142238616943s
Consistency | Check Invalid usage of undefined properties for Apertium RDF FR-CA took 5.941328287124634s
Conciseness | Check Extensional conciseness for Apertium RDF FR-CA took 3.2220818996429443s
Conciseness | Check Intensional conciseness for Apertium RDF FR-CA took 0.33414602279663086s
Security | Sign check for Apertium RDF FR-CA took 0.2968118190765381s
Availability | Check URIs Dereferenciability for Apertium RDF FR-CA took 3.8018336296081543s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.8060698509216309s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.021543025970458984s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0008835792541503906s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 5.221366882324219e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF FR-CA took 2.1457672119140625e-06s
Believability | Calculation of trust value for Apertium RDF FR-CA took 1.3113021850585938e-05s
INFO | --- Analysis for apertium-rdf-fr-ca took 662.0047090053558s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 0.22892189025878906s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.0007839202880859375s
Extra | Recovery of all triples for Apertium RDF FR-ES took 282.79243874549866s
Performance | Total latancy measurement for Apertium RDF FR-ES took 1.4421894550323486s
Amount of data | Number of triples check for Apertium RDF FR-ES took 2.190016746520996s
Interoperability | New terms check for Apertium RDF FR-ES took 2.9154741764068604s
Versatility | Languages check for Apertium RDF FR-ES took 44.54373502731323s
Interpretability | Number of blank nodes check for Apertium RDF FR-ES took 1.098085880279541s
Security | Check HTTPS for Apertium RDF FR-ES took 0.12478041648864746s
Interpretability | RDF structures check for Apertium RDF FR-ES took 0.3175170421600342s
Versatility | Serialization formats check for Apertium RDF FR-ES took 0.3124678134918213s
Availability | RDF dump link check for Apertium RDF FR-ES took 0.28292417526245117s
License | MR license check for Apertium RDF FR-ES took 0.32828855514526367s
License | HR license check for Apertium RDF FR-ES took 0.4106299877166748s
Amount of data | Number of property check for Apertium RDF FR-ES took 0.3408846855163574s
Understandability | Number of label check for Apertium RDF FR-ES took 0.33432769775390625s
Understandability | URI regex check for Apertium RDF FR-ES took 0.5676164627075195s
Understandability | Vocabs check for Apertium RDF FR-ES took 0.3008410930633545s
Verifiability | Authors check for Apertium RDF FR-ES took 0.3062591552734375s
Verifiability | Publishers check for Apertium RDF FR-ES took 0.3006744384765625s
Performance | Throughput check for Apertium RDF FR-ES took 11.562932252883911s
Amount of data | Check the number of entities for Apertium RDF FR-ES took 8.535385131835938e-05s
Verifiability | Contribs. check for Apertium RDF FR-ES took 0.2997596263885498s
Interlinking | sameAs chians check for Apertium RDF FR-ES took 0.27085351943969727s
Interlinking | skos check for Apertium RDF FR-ES took 0.31200504302978516s
Interlinking | skos check for Apertium RDF FR-ES took 0.2333993911743164s
Timeliness | dataset update frequency check for Apertium RDF FR-ES took 0.3231658935546875s
Currency | Creation date check for Apertium RDF FR-ES took 0.3252842426300049s
Currency | Modification date check for Apertium RDF FR-ES took 0.2693634033203125s
Rep.Conc. | URIs length for Apertium RDF FR-ES took 85.8863091468811s
Interoperability | New vocabularies check for Apertium RDF FR-ES took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF FR-ES took 0.3362610340118408s
Accuracy | Check Functional Property for Apertium RDF FR-ES took 0.2888026237487793s
Accuracy | Check Inverse Functional Property for Apertium RDF FR-ES took 0.2921152114868164s
Accuracy | Check Empty annotation labels for Apertium RDF FR-ES took 0.943793773651123s
Accuracy | Check White space in annotation for Apertium RDF FR-ES took 0.010067462921142578s
Accuracy | Check Datatype consistency for Apertium RDF FR-ES took 2.7697370052337646s
Consistency | Disjoint class check for Apertium RDF FR-ES took 0.31082916259765625s
Consistency | Check Misplaced properties for Apertium RDF FR-ES took 4.6517815589904785s
Consistency | Misplaced classes for Apertium RDF FR-ES took 8.367085218429565s
Consistency | Check Ontology hijacking for Apertium RDF FR-ES took 93.94815731048584s
Consistency | Check Invalid usage of undefined classes for Apertium RDF FR-ES took 1.4975223541259766s
Consistency | Check Invalid usage of undefined properties for Apertium RDF FR-ES took 5.806282043457031s
Conciseness | Check Extensional conciseness for Apertium RDF FR-ES took 3.163682699203491s
Conciseness | Check Intensional conciseness for Apertium RDF FR-ES took 0.33414506912231445s
Security | Sign check for Apertium RDF FR-ES took 0.3255584239959717s
Availability | Check URIs Dereferenciability for Apertium RDF FR-ES took 3.6911754608154297s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.531686544418335s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.020623445510864258s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 4.649162292480469e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF FR-ES took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF FR-ES took 1.2874603271484375e-05s
INFO | --- Analysis for apertium-rdf-fr-es took 637.7430009841919s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 0.21882176399230957s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0008568763732910156s
Extra | Recovery of all triples for Apertium RDF OC-CA took 278.20601654052734s
Performance | Total latancy measurement for Apertium RDF OC-CA took 1.3340725898742676s
Amount of data | Number of triples check for Apertium RDF OC-CA took 2.0964274406433105s
Interoperability | New terms check for Apertium RDF OC-CA took 3.079101800918579s
Versatility | Languages check for Apertium RDF OC-CA took 44.20600771903992s
Interpretability | Number of blank nodes check for Apertium RDF OC-CA took 1.0981605052947998s
Security | Check HTTPS for Apertium RDF OC-CA took 0.15265750885009766s
Interpretability | RDF structures check for Apertium RDF OC-CA took 0.2878122329711914s
Versatility | Serialization formats check for Apertium RDF OC-CA took 0.3171825408935547s
Availability | RDF dump link check for Apertium RDF OC-CA took 0.3071136474609375s
License | MR license check for Apertium RDF OC-CA took 0.3194451332092285s
License | HR license check for Apertium RDF OC-CA took 0.3950676918029785s
Amount of data | Number of property check for Apertium RDF OC-CA took 0.29131102561950684s
Understandability | Number of label check for Apertium RDF OC-CA took 0.3480710983276367s
Understandability | URI regex check for Apertium RDF OC-CA took 0.5721251964569092s
Understandability | Vocabs check for Apertium RDF OC-CA took 0.26317477226257324s
Verifiability | Authors check for Apertium RDF OC-CA took 0.297745943069458s
Verifiability | Publishers check for Apertium RDF OC-CA took 0.29569029808044434s
Performance | Throughput check for Apertium RDF OC-CA took 11.463697671890259s
Amount of data | Check the number of entities for Apertium RDF OC-CA took 9.274482727050781e-05s
Verifiability | Contribs. check for Apertium RDF OC-CA took 0.305539608001709s
Interlinking | sameAs chians check for Apertium RDF OC-CA took 0.3013112545013428s
Interlinking | skos check for Apertium RDF OC-CA took 0.30977964401245117s
Interlinking | skos check for Apertium RDF OC-CA took 0.24805498123168945s
Timeliness | dataset update frequency check for Apertium RDF OC-CA took 0.301525354385376s
Currency | Creation date check for Apertium RDF OC-CA took 0.28431010246276855s
Currency | Modification date check for Apertium RDF OC-CA took 0.30396270751953125s
Rep.Conc. | URIs length for Apertium RDF OC-CA took 86.49394464492798s
Interoperability | New vocabularies check for Apertium RDF OC-CA took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF OC-CA took 0.31413698196411133s
Accuracy | Check Functional Property for Apertium RDF OC-CA took 0.3076047897338867s
Accuracy | Check Inverse Functional Property for Apertium RDF OC-CA took 0.3090803623199463s
Accuracy | Check Empty annotation labels for Apertium RDF OC-CA took 0.8121552467346191s
Accuracy | Check White space in annotation for Apertium RDF OC-CA took 0.009967803955078125s
Accuracy | Check Datatype consistency for Apertium RDF OC-CA took 2.717555046081543s
Consistency | Disjoint class check for Apertium RDF OC-CA took 0.286409854888916s
Consistency | Check Misplaced properties for Apertium RDF OC-CA took 4.673389911651611s
Consistency | Misplaced classes for Apertium RDF OC-CA took 8.423626184463501s
Consistency | Check Ontology hijacking for Apertium RDF OC-CA took 110.87484693527222s
Consistency | Check Invalid usage of undefined classes for Apertium RDF OC-CA took 1.5215919017791748s
Consistency | Check Invalid usage of undefined properties for Apertium RDF OC-CA took 6.003344774246216s
Conciseness | Check Extensional conciseness for Apertium RDF OC-CA took 3.156373977661133s
Conciseness | Check Intensional conciseness for Apertium RDF OC-CA took 0.42130112648010254s
Security | Sign check for Apertium RDF OC-CA took 0.3263428211212158s
Availability | Check URIs Dereferenciability for Apertium RDF OC-CA took 3.8129281997680664s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 0.3810920715332031s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.02060532569885254s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 4.7206878662109375e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF OC-CA took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF OC-CA took 1.2159347534179688e-05s
INFO | --- Analysis for apertium-rdf-oc-ca took 651.5506906509399s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 0.21575355529785156s
Availability | VoID file availability check for Apertium RDF OC-ES took 0.0008425712585449219s
Extra | Recovery of all triples for Apertium RDF OC-ES took 265.81555938720703s
Performance | Total latancy measurement for Apertium RDF OC-ES took 1.4398064613342285s
Amount of data | Number of triples check for Apertium RDF OC-ES took 2.247542381286621s
Interoperability | New terms check for Apertium RDF OC-ES took 3.047940254211426s
Versatility | Languages check for Apertium RDF OC-ES took 44.38535189628601s
Interpretability | Number of blank nodes check for Apertium RDF OC-ES took 1.2109689712524414s
Security | Check HTTPS for Apertium RDF OC-ES took 0.14809465408325195s
Interpretability | RDF structures check for Apertium RDF OC-ES took 0.30428385734558105s
Versatility | Serialization formats check for Apertium RDF OC-ES took 0.2838938236236572s
Availability | RDF dump link check for Apertium RDF OC-ES took 0.2929692268371582s
License | MR license check for Apertium RDF OC-ES took 0.3368675708770752s
License | HR license check for Apertium RDF OC-ES took 0.4243049621582031s
Amount of data | Number of property check for Apertium RDF OC-ES took 0.2866969108581543s
Understandability | Number of label check for Apertium RDF OC-ES took 0.3360722064971924s
Understandability | URI regex check for Apertium RDF OC-ES took 0.5838744640350342s
Understandability | Vocabs check for Apertium RDF OC-ES took 0.30010390281677246s
Verifiability | Authors check for Apertium RDF OC-ES took 0.3800668716430664s
Verifiability | Publishers check for Apertium RDF OC-ES took 0.32004213333129883s
Performance | Throughput check for Apertium RDF OC-ES took 12.167192220687866s
Amount of data | Check the number of entities for Apertium RDF OC-ES took 8.916854858398438e-05s
Verifiability | Contribs. check for Apertium RDF OC-ES took 0.26695680618286133s
Interlinking | sameAs chians check for Apertium RDF OC-ES took 0.2839844226837158s
Interlinking | skos check for Apertium RDF OC-ES took 0.286653995513916s
Interlinking | skos check for Apertium RDF OC-ES took 0.24378585815429688s
Timeliness | dataset update frequency check for Apertium RDF OC-ES took 0.30168771743774414s
Currency | Creation date check for Apertium RDF OC-ES took 0.28756213188171387s
Currency | Modification date check for Apertium RDF OC-ES took 0.28040647506713867s
Rep.Conc. | URIs length for Apertium RDF OC-ES took 96.31791353225708s
Interoperability | New vocabularies check for Apertium RDF OC-ES took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF OC-ES took 0.340224027633667s
Accuracy | Check Functional Property for Apertium RDF OC-ES took 0.28084349632263184s
Accuracy | Check Inverse Functional Property for Apertium RDF OC-ES took 0.27629899978637695s
Accuracy | Check Empty annotation labels for Apertium RDF OC-ES took 0.8741340637207031s
Accuracy | Check White space in annotation for Apertium RDF OC-ES took 0.009933233261108398s
Accuracy | Check Datatype consistency for Apertium RDF OC-ES took 2.685378313064575s
Consistency | Disjoint class check for Apertium RDF OC-ES took 0.2660534381866455s
Consistency | Check Misplaced properties for Apertium RDF OC-ES took 4.740456819534302s
Consistency | Misplaced classes for Apertium RDF OC-ES took 8.51117467880249s
Consistency | Check Ontology hijacking for Apertium RDF OC-ES took 105.67745971679688s
Consistency | Check Invalid usage of undefined classes for Apertium RDF OC-ES took 1.5727624893188477s
Consistency | Check Invalid usage of undefined properties for Apertium RDF OC-ES took 5.765783786773682s
Conciseness | Check Extensional conciseness for Apertium RDF OC-ES took 3.145850896835327s
Conciseness | Check Intensional conciseness for Apertium RDF OC-ES took 0.3652026653289795s
Security | Sign check for Apertium RDF OC-ES took 0.2832334041595459s
Availability | Check URIs Dereferenciability for Apertium RDF OC-ES took 18.719446897506714s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 0.5543019771575928s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.020966291427612305s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 4.57763671875e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF OC-ES took 1.9073486328125e-06s
Believability | Calculation of trust value for Apertium RDF OC-ES took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-oc-es took 657.7205808162689s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 0.23567795753479004s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.00034546852111816406s
Extra | Recovery of all triples for Apertium RDF PT-CA took 266.23220920562744s
Performance | Total latancy measurement for Apertium RDF PT-CA took 1.389404058456421s
Amount of data | Number of triples check for Apertium RDF PT-CA took 2.315596580505371s
Interoperability | New terms check for Apertium RDF PT-CA took 2.9328854084014893s
Versatility | Languages check for Apertium RDF PT-CA took 44.15055871009827s
Interpretability | Number of blank nodes check for Apertium RDF PT-CA took 1.0641908645629883s
Security | Check HTTPS for Apertium RDF PT-CA took 0.13815927505493164s
Interpretability | RDF structures check for Apertium RDF PT-CA took 0.33211827278137207s
Versatility | Serialization formats check for Apertium RDF PT-CA took 0.29834699630737305s
Availability | RDF dump link check for Apertium RDF PT-CA took 0.32337117195129395s
License | MR license check for Apertium RDF PT-CA took 0.3564033508300781s
License | HR license check for Apertium RDF PT-CA took 0.4470679759979248s
Amount of data | Number of property check for Apertium RDF PT-CA took 0.28873467445373535s
Understandability | Number of label check for Apertium RDF PT-CA took 0.35520243644714355s
Understandability | URI regex check for Apertium RDF PT-CA took 0.5984554290771484s
Understandability | Vocabs check for Apertium RDF PT-CA took 0.30293965339660645s
Verifiability | Authors check for Apertium RDF PT-CA took 0.34947943687438965s
Verifiability | Publishers check for Apertium RDF PT-CA took 0.31207799911499023s
Performance | Throughput check for Apertium RDF PT-CA took 11.432248830795288s
Amount of data | Check the number of entities for Apertium RDF PT-CA took 8.606910705566406e-05s
Verifiability | Contribs. check for Apertium RDF PT-CA took 0.3077208995819092s
Interlinking | sameAs chians check for Apertium RDF PT-CA took 0.32534337043762207s
Interlinking | skos check for Apertium RDF PT-CA took 0.3067471981048584s
Interlinking | skos check for Apertium RDF PT-CA took 0.23460745811462402s
Timeliness | dataset update frequency check for Apertium RDF PT-CA took 0.30036473274230957s
Currency | Creation date check for Apertium RDF PT-CA took 0.28255677223205566s
Currency | Modification date check for Apertium RDF PT-CA took 0.2703087329864502s
Rep.Conc. | URIs length for Apertium RDF PT-CA took 94.26376819610596s
Interoperability | New vocabularies check for Apertium RDF PT-CA took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF PT-CA took 0.3137516975402832s
Accuracy | Check Functional Property for Apertium RDF PT-CA took 0.3029351234436035s
Accuracy | Check Inverse Functional Property for Apertium RDF PT-CA took 0.3036050796508789s
Accuracy | Check Empty annotation labels for Apertium RDF PT-CA took 0.8801040649414062s
Accuracy | Check White space in annotation for Apertium RDF PT-CA took 0.010266304016113281s
Accuracy | Check Datatype consistency for Apertium RDF PT-CA took 2.664489984512329s
Consistency | Disjoint class check for Apertium RDF PT-CA took 0.29410648345947266s
Consistency | Check Misplaced properties for Apertium RDF PT-CA took 4.729306697845459s
Consistency | Misplaced classes for Apertium RDF PT-CA took 8.394381761550903s
Consistency | Check Ontology hijacking for Apertium RDF PT-CA took 92.55068922042847s
Consistency | Check Invalid usage of undefined classes for Apertium RDF PT-CA took 1.622328519821167s
Consistency | Check Invalid usage of undefined properties for Apertium RDF PT-CA took 5.9481518268585205s
Conciseness | Check Extensional conciseness for Apertium RDF PT-CA took 3.2288336753845215s
Conciseness | Check Intensional conciseness for Apertium RDF PT-CA took 0.3680264949798584s
Security | Sign check for Apertium RDF PT-CA took 0.35025501251220703s
Availability | Check URIs Dereferenciability for Apertium RDF PT-CA took 3.8908028602600098s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 0.5592813491821289s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.020509004592895508s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 4.38690185546875e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF PT-CA took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF PT-CA took 1.2159347534179688e-05s
INFO | --- Analysis for apertium-rdf-pt-ca took 625.010883808136s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 0.24524188041687012s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.0008168220520019531s
Extra | Recovery of all triples for Apertium RDF PT-GL took 250.64164400100708s
Performance | Total latancy measurement for Apertium RDF PT-GL took 1.3834221363067627s
Amount of data | Number of triples check for Apertium RDF PT-GL took 2.174051523208618s
Interoperability | New terms check for Apertium RDF PT-GL took 2.9250636100769043s
Versatility | Languages check for Apertium RDF PT-GL took 44.13477659225464s
Interpretability | Number of blank nodes check for Apertium RDF PT-GL took 1.3143701553344727s
Security | Check HTTPS for Apertium RDF PT-GL took 0.1401047706604004s
Interpretability | RDF structures check for Apertium RDF PT-GL took 0.3625757694244385s
Versatility | Serialization formats check for Apertium RDF PT-GL took 0.37851738929748535s
Availability | RDF dump link check for Apertium RDF PT-GL took 0.34438562393188477s
License | MR license check for Apertium RDF PT-GL took 0.33243894577026367s
License | HR license check for Apertium RDF PT-GL took 0.4454188346862793s
Amount of data | Number of property check for Apertium RDF PT-GL took 0.3489656448364258s
Understandability | Number of label check for Apertium RDF PT-GL took 0.404003381729126s
Understandability | URI regex check for Apertium RDF PT-GL took 0.7104952335357666s
Understandability | Vocabs check for Apertium RDF PT-GL took 0.3832056522369385s
Verifiability | Authors check for Apertium RDF PT-GL took 0.38875293731689453s
Verifiability | Publishers check for Apertium RDF PT-GL took 0.3687007427215576s
Performance | Throughput check for Apertium RDF PT-GL took 11.522736072540283s
Amount of data | Check the number of entities for Apertium RDF PT-GL took 8.130073547363281e-05s
Verifiability | Contribs. check for Apertium RDF PT-GL took 0.3673059940338135s
Interlinking | sameAs chians check for Apertium RDF PT-GL took 0.34439778327941895s
Interlinking | skos check for Apertium RDF PT-GL took 0.37674641609191895s
Interlinking | skos check for Apertium RDF PT-GL took 0.24141836166381836s
Timeliness | dataset update frequency check for Apertium RDF PT-GL took 0.39538097381591797s
Currency | Creation date check for Apertium RDF PT-GL took 0.3654444217681885s
Currency | Modification date check for Apertium RDF PT-GL took 0.3959312438964844s
Rep.Conc. | URIs length for Apertium RDF PT-GL took 86.37087631225586s
Interoperability | New vocabularies check for Apertium RDF PT-GL took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF PT-GL took 0.37143397331237793s
Accuracy | Check Functional Property for Apertium RDF PT-GL took 0.3156449794769287s
Accuracy | Check Inverse Functional Property for Apertium RDF PT-GL took 0.2858867645263672s
Accuracy | Check Empty annotation labels for Apertium RDF PT-GL took 0.8353791236877441s
Accuracy | Check White space in annotation for Apertium RDF PT-GL took 0.010019540786743164s
Accuracy | Check Datatype consistency for Apertium RDF PT-GL took 2.792334794998169s
Consistency | Disjoint class check for Apertium RDF PT-GL took 0.3295168876647949s
Consistency | Check Misplaced properties for Apertium RDF PT-GL took 4.726073503494263s
Consistency | Misplaced classes for Apertium RDF PT-GL took 8.409584760665894s
Consistency | Check Ontology hijacking for Apertium RDF PT-GL took 85.0330114364624s
Consistency | Check Invalid usage of undefined classes for Apertium RDF PT-GL took 1.5167744159698486s
Consistency | Check Invalid usage of undefined properties for Apertium RDF PT-GL took 5.744653701782227s
Conciseness | Check Extensional conciseness for Apertium RDF PT-GL took 3.1403496265411377s
Conciseness | Check Intensional conciseness for Apertium RDF PT-GL took 0.31329870223999023s
Security | Sign check for Apertium RDF PT-GL took 0.3012378215789795s
Availability | Check URIs Dereferenciability for Apertium RDF PT-GL took 3.782357692718506s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.4042072296142578s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.02087688446044922s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 4.744529724121094e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF PT-GL took 1.430511474609375e-06s
Believability | Calculation of trust value for Apertium RDF PT-GL took 1.2636184692382812e-05s
INFO | --- Analysis for apertium-rdf-pt-gl took 598.2495665550232s
Availability | SPARQL endpoint availability check for AragoDBPedia took 0.6065270900726318s
Availability | VoID file availability check for AragoDBPedia took 0.7701082229614258s
Extra | Recovery of all triples for AragoDBPedia took 2.7624704837799072s
Performance | Total latancy measurement for AragoDBPedia took 1.6895427703857422s
Amount of data | Number of triples check for AragoDBPedia took 0.8430173397064209s
Interoperability | New terms check for AragoDBPedia took 2.0682435035705566s
Versatility | Languages check for AragoDBPedia took 60.45604205131531s
Interpretability | Number of blank nodes check for AragoDBPedia took 4.178782939910889s
Security | Check HTTPS for AragoDBPedia took 0.2304532527923584s
Interpretability | RDF structures check for AragoDBPedia took 0.8202662467956543s
Versatility | Serialization formats check for AragoDBPedia took 0.3526780605316162s
Availability | RDF dump link check for AragoDBPedia took 0.3890111446380615s
License | MR license check for AragoDBPedia took 0.6388754844665527s
License | HR license check for AragoDBPedia took 6.196392297744751s
Amount of data | Number of property check for AragoDBPedia took 0.3353540897369385s
Understandability | Number of label check for AragoDBPedia took 0.6058018207550049s
Understandability | URI regex check for AragoDBPedia took 1.031719446182251s
Understandability | Vocabs check for AragoDBPedia took 0.46131086349487305s
Verifiability | Authors check for AragoDBPedia took 0.849311351776123s
Verifiability | Publishers check for AragoDBPedia took 0.4519634246826172s
Performance | Throughput check for AragoDBPedia took 11.976205110549927s
Amount of data | Check the number of entities for AragoDBPedia took 0.00015044212341308594s
Verifiability | Contribs. check for AragoDBPedia took 0.4883384704589844s
Interlinking | sameAs chians check for AragoDBPedia took 0.3829953670501709s
Interlinking | skos check for AragoDBPedia took 0.6483883857727051s
Interlinking | skos check for AragoDBPedia took 0.3225078582763672s
Timeliness | dataset update frequency check for AragoDBPedia took 0.5042142868041992s
Currency | Creation date check for AragoDBPedia took 0.377988338470459s
Currency | Modification date check for AragoDBPedia took 0.7954616546630859s
Rep.Conc. | URIs length for AragoDBPedia took 5.5819807052612305s
Interoperability | New vocabularies check for AragoDBPedia took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for AragoDBPedia took 0.3616619110107422s
Accuracy | Check Functional Property for AragoDBPedia took 0.45934557914733887s
Accuracy | Check Inverse Functional Property for AragoDBPedia took 0.4855642318725586s
Accuracy | Check Empty annotation labels for AragoDBPedia took 1.9400136470794678s
Accuracy | Check White space in annotation for AragoDBPedia took 0.02968311309814453s
Accuracy | Check Datatype consistency for AragoDBPedia took 0.029445648193359375s
Consistency | Disjoint class check for AragoDBPedia took 0.41468358039855957s
Consistency | Check Misplaced properties for AragoDBPedia took 4.115381717681885s
Consistency | Misplaced classes for AragoDBPedia took 0.5916347503662109s
Consistency | Check Ontology hijacking for AragoDBPedia took 2.4092843532562256s
Consistency | Check Invalid usage of undefined classes for AragoDBPedia took 1.4069745540618896s
Consistency | Check Invalid usage of undefined properties for AragoDBPedia took 5.15016770362854s
Conciseness | Check Extensional conciseness for AragoDBPedia took 0.03435015678405762s
Conciseness | Check Intensional conciseness for AragoDBPedia took 0.5530223846435547s
Security | Sign check for AragoDBPedia took 0.6623127460479736s
Availability | Check URIs Dereferenciability for AragoDBPedia took 2969.754665374756s
Completeness | Calculation of interlinking completeness for AragoDBPedia took 0.7951548099517822s
Reputation | Calculation of the PageRank for AragoDBPedia took 0.02393317222595215s
Interlinking | Calculation of Degree of Connection for AragoDBPedia took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for AragoDBPedia took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for AragoDBPedia took 4.3392181396484375e-05s
Interoperability | Check the re-using of existing vocabs for AragoDBPedia took 1.430511474609375e-06s
Believability | Calculation of trust value for AragoDBPedia took 1.0251998901367188e-05s
INFO | --- Analysis for aragodbpedia took 3153.569682598114s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 30.333566188812256s
Availability | VoID file availability check for Archives Hub Linked Data took 20.19371485710144s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.36538100242614746s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.021024227142333984s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 5.53131103515625e-05s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 5.3882598876953125e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 1.1682510375976562e-05s
INFO | --- Analysis for archiveshub-linkeddata took 83.03395485877991s
Availability | SPARQL endpoint availability check for Archivi ISMA took 30.137929439544678s
Availability | VoID file availability check for Archivi ISMA took 20.09997797012329s
Completeness | Calculation of interlinking completeness for Archivi ISMA took 0.7637138366699219s
Reputation | Calculation of the PageRank for Archivi ISMA took 0.020898818969726562s
Interlinking | Calculation of Degree of Connection for Archivi ISMA took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Archivi ISMA took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Archivi ISMA took 3.266334533691406e-05s
Believability | Calculation of trust value for Archivi ISMA took 1.1444091796875e-05s
INFO | --- Analysis for archivio-isma took 92.67822813987732s
Availability | SPARQL endpoint availability check for ARIADNE took 0.366161584854126s
Availability | VoID file availability check for ARIADNE took 0.00034928321838378906s
Completeness | Calculation of interlinking completeness for ARIADNE took 0.3690073490142822s
Reputation | Calculation of the PageRank for ARIADNE took 0.02115917205810547s
Interlinking | Calculation of Degree of Connection for ARIADNE took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for ARIADNE took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for ARIADNE took 3.552436828613281e-05s
Believability | Calculation of trust value for ARIADNE took 7.62939453125e-06s
INFO | --- Analysis for ariadne took 133.3213505744934s
Availability | SPARQL endpoint availability check for Aristotle University took 2.560704469680786s
Availability | VoID file availability check for Aristotle University took 0.03731489181518555s
Completeness | Calculation of interlinking completeness for Aristotle University took 0.3195180892944336s
Reputation | Calculation of the PageRank for Aristotle University took 0.02110004425048828s
Interlinking | Calculation of Degree of Connection for Aristotle University took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Aristotle University took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for Aristotle University took 3.814697265625e-05s
Believability | Calculation of trust value for Aristotle University took 7.62939453125e-06s
INFO | --- Analysis for aristotle-university took 7.812853097915649s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 24.46375012397766s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.00017905235290527344s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 0.33580899238586426s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.021193981170654297s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 4.9591064453125e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 8.344650268554688e-06s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 44.95974540710449s
Availability | SPARQL endpoint availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 4.1961669921875e-05s
Availability | VoID file availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.00013256072998046875s
Completeness | Calculation of interlinking completeness for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.3798232078552246s
Reputation | Calculation of the PageRank for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.021774768829345703s
Interlinking | Calculation of Degree of Connection for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 3.0040740966796875e-05s
Believability | Calculation of trust value for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 8.821487426757812e-06s
INFO | --- Analysis for arrayexpress_e-afmx-4 took 1.9088191986083984s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 22.89325451850891s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.000301361083984375s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.31888866424560547s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.020931482315063477s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.409385681152344e-05s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 4.4345855712890625e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.2636184692382812e-05s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 60.22809886932373s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 8.249282836914062e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 3.107112169265747s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.40886521339416504s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.02077651023864746s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.00010251998901367188s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.3113021850585938e-05s
INFO | --- Analysis for artenuevosmedios-gnoss took 13.887075185775757s
Availability | SPARQL endpoint availability check for Arthroscopy community took 4.124641418457031e-05s
Availability | VoID file availability check for Arthroscopy community took 2.5603387355804443s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 0.32480335235595703s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.020930767059326172s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 0.00010275840759277344s
Believability | Calculation of trust value for Arthroscopy community took 1.3589859008789062e-05s
INFO | --- Analysis for arthroscopy took 33.15939998626709s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 3.3015594482421875s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.6716523170471191s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.382188081741333s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.020802736282348633s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 7.843971252441406e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.33514404296875e-05s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 14.21730089187622s
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.356673002243042s
Availability | VoID file availability check for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 1.609180212020874s
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 1.0381050109863281s
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.021033287048339844s
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.00069427490234375s
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.987022399902344e-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.1205673217773438e-05s
INFO | --- Analysis for ASCDC-AS-NTUE-School-Art-Textbooks took 13.508366823196411s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.4740798473358154s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.5307979583740234s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.36356258392333984s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.021701574325561523s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 9.274482727050781e-05s
Believability | Calculation of trust value for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.33514404296875e-05s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 16.2583270072937s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.5780909061431885s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 1.6522085666656494s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 0.3709855079650879s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.021189451217651367s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 4.291534423828125e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 1.1205673217773438e-05s
INFO | --- Analysis for ASCDC-CRB took 16.64126706123352s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.380943775177002s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.6864919662475586s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.0666472911834717s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.021570205688476562s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.250640869140625e-05s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.1682510375976562e-05s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 14.832825422286987s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.437387466430664s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 1.7023520469665527s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 0.3896598815917969s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.021290302276611328s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 3.7670135498046875e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 8.106231689453125e-06s
INFO | --- Analysis for ASCDC-DQOT took 14.9785315990448s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.4265592098236084s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.6092824935913086s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.533564567565918s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.02156996726989746s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0008099079132080078s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 9.5367431640625e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.2874603271484375e-05s
INFO | --- Analysis for ASCDC-IHP-WCD took 14.983505249023438s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 3.6462693214416504s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 1.6232235431671143s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 1.0675396919250488s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.021219968795776367s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 8.463859558105469e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 1.239776611328125e-05s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 19.301731824874878s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.50770902633667s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 1.615062952041626s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 1.782714605331421s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.021190166473388672s
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.2159347534179688e-05s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 5.888938903808594e-05s
Believability | Calculation of trust value for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 8.58306884765625e-06s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 16.524758338928223s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.4235432147979736s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.6400153636932373s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.5167667865753174s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.021162986755371094s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 5.125999450683594e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.1920928955078125e-05s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 13.600938320159912s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 4.065628290176392s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.6255831718444824s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.36762046813964844s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.021130084991455078s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 4.8160552978515625e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.1205673217773438e-05s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 18.98094892501831s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.417677164077759s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.5828273296356201s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.5447123050689697s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.02154684066772461s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 9.679794311523438e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.3589859008789062e-05s
INFO | --- Analysis for ASCDC-Tibetan-Audio-Archive took 13.039390325546265s
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.456231117248535s
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 1.655400276184082s
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.3454608917236328s
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.02093052864074707s
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.1205673217773438e-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.0007269382476806641s
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.392333984375e-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 7.867813110351562e-06s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 14.974117517471313s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 2.5303874015808105s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 1.5776164531707764s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 0.33737850189208984s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.02133941650390625s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 4.792213439941406e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 8.106231689453125e-06s
INFO | --- Analysis for ASCDC_-_DNB took 14.395540237426758s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 4.38690185546875e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 3.1911418437957764s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 0.7773020267486572s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.021213769912719727s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 6.985664367675781e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 1.5020370483398438e-05s
INFO | --- Analysis for asit took 17.56929874420166s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 4.124641418457031e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.0007100105285644531s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.9114775657653809s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.020941734313964844s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 4.029273986816406e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 1.239776611328125e-05s
INFO | --- Analysis for asjp took 5.845249176025391s
Availability | SPARQL endpoint availability check for ASN:US took 262.5685703754425s
Availability | VoID file availability check for ASN:US took 0.5516185760498047s
Completeness | Calculation of interlinking completeness for ASN:US took 1.0999541282653809s
Reputation | Calculation of the PageRank for ASN:US took 0.02096390724182129s
Interlinking | Calculation of Degree of Connection for ASN:US took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for ASN:US took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for ASN:US took 7.62939453125e-05s
Believability | Calculation of trust value for ASN:US took 1.1920928955078125e-05s
INFO | --- Analysis for asn-us took 405.1881613731384s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 4.220008850097656e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.9586851596832275s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.8768308162689209s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.020455121994018555s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 2.7894973754882812e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 9.775161743164062e-06s
INFO | --- Analysis for aspire-mmu took 5.983198642730713s
Availability | SPARQL endpoint availability check for associations took 9.417533874511719e-05s
Availability | VoID file availability check for associations took 0.5813450813293457s
Completeness | Calculation of interlinking completeness for associations took 0.3359403610229492s
Reputation | Calculation of the PageRank for associations took 0.020731449127197266s
Interlinking | Calculation of Degree of Connection for associations took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for associations took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for associations took 6.914138793945312e-05s
Interoperability | Check the re-using of existing vocabs for associations took 0.7107806205749512s
Believability | Calculation of trust value for associations took 1.239776611328125e-05s
INFO | --- Analysis for associations took 8.802718877792358s
Availability | SPARQL endpoint availability check for ATC publikovaná SÚKL took 0.20765042304992676s
Availability | VoID file availability check for ATC publikovaná SÚKL took 0.00017261505126953125s
Completeness | Calculation of interlinking completeness for ATC publikovaná SÚKL took 0.3377964496612549s
Reputation | Calculation of the PageRank for ATC publikovaná SÚKL took 0.021619558334350586s
Interlinking | Calculation of Degree of Connection for ATC publikovaná SÚKL took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for ATC publikovaná SÚKL took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for ATC publikovaná SÚKL took 2.765655517578125e-05s
Believability | Calculation of trust value for ATC publikovaná SÚKL took 1.1205673217773438e-05s
INFO | --- Analysis for atc-publikovan--s-kl took 2.3878486156463623s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 8.392333984375e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 26.62843155860901s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 0.4970691204071045s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.020461082458496094s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 9.72747802734375e-05s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 1.1682510375976562e-05s
INFO | --- Analysis for athelia-rfid took 103.28138303756714s
Availability | SPARQL endpoint availability check for AUEB Linked Open Data took 4.87484073638916s
Availability | VoID file availability check for AUEB Linked Open Data took 0.0008871555328369141s
Completeness | Calculation of interlinking completeness for AUEB Linked Open Data took 0.4850611686706543s
Reputation | Calculation of the PageRank for AUEB Linked Open Data took 0.020166873931884766s
Interlinking | Calculation of Degree of Connection for AUEB Linked Open Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for AUEB Linked Open Data took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for AUEB Linked Open Data took 2.765655517578125e-05s
Believability | Calculation of trust value for AUEB Linked Open Data took 1.0967254638671875e-05s
INFO | --- Analysis for aueb-linked-open-data took 9.130746364593506s
Availability | SPARQL endpoint availability check for Augustini Confessiones in LiLa took 0.6435887813568115s
Availability | VoID file availability check for Augustini Confessiones in LiLa took 0.31033873558044434s
Completeness | Calculation of interlinking completeness for Augustini Confessiones in LiLa took 0.35037660598754883s
Reputation | Calculation of the PageRank for Augustini Confessiones in LiLa took 0.020428180694580078s
Interlinking | Calculation of Degree of Connection for Augustini Confessiones in LiLa took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Augustini Confessiones in LiLa took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Augustini Confessiones in LiLa took 4.744529724121094e-05s
Interoperability | Check the re-using of existing vocabs for Augustini Confessiones in LiLa took 3.5762786865234375e-06s
Believability | Calculation of trust value for Augustini Confessiones in LiLa took 1.1444091796875e-05s
INFO | --- Analysis for AugustiniConfessiones took 4.094066143035889s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 0.5516467094421387s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.43021059036254883s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.35363221168518066s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.0211639404296875s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Alpine Ski Racers of Austria took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 9.441375732421875e-05s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 1.3113021850585938e-05s
INFO | --- Analysis for austrian_ski_racers took 3.666858196258545s
Availability | SPARQL endpoint availability check for AVsOnto took 4.124641418457031e-05s
Availability | VoID file availability check for AVsOnto took 0.34563636779785156s
Completeness | Calculation of interlinking completeness for AVsOnto took 0.5929694175720215s
Reputation | Calculation of the PageRank for AVsOnto took 0.021054744720458984s
Interlinking | Calculation of Degree of Connection for AVsOnto took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for AVsOnto took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for AVsOnto took 2.86102294921875e-05s
Believability | Calculation of trust value for AVsOnto took 1.4543533325195312e-05s
INFO | --- Analysis for AVsOnto took 4.0739970207214355s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.20459675788879395s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.16069769859313965s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 13.73677659034729s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.543121337890625s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0581135749817s
Interoperability | New terms check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.4897277355194092s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0339891910553s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0117428302765s
Security | Check HTTPS for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.28175973892211914s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.20370268821716309s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.13014507293701172s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12414884567260742s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 192.71091485023499s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.10332012176514s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.17011022567749023s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 299.652028799057s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.3520936965942383s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10529136657714844s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 632.062433719635s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1053.3942112922668s
Performance | Throughput check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 12.665650844573975s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.00011777877807617188s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 55.5604031085968s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.1039848327637s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.15364336967468262s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12296199798583984s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.20343399047851562s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 140.55728602409363s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2669515609741211s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 173.6467616558075s
Interoperability | New vocabularies check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.14814233779907227s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 9.866142511367798s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.3832812309265137s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.590753555297852s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.15909194946289062s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.265946626663208s
Consistency | Misplaced classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 8.781145334243774s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 8.155364036560059s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 21986.070399045944s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.6887855529785156s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.062290906906128s
Conciseness | Check Intensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.18691301345825195s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1421959400177002s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.8011558055877686s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.835655927658081s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.021711349487304688s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 8.20159912109375e-05s
Interoperability | Check the re-using of existing vocabs for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.9073486328125e-06s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 8.821487426757812e-06s
INFO | --- Analysis for b3kat took 27331.30146098137s
Availability | SPARQL endpoint availability check for BabelNet took 0.6843743324279785s
Availability | VoID file availability check for BabelNet took 0.0008206367492675781s
Completeness | Calculation of interlinking completeness for BabelNet took 60.28955316543579s
Reputation | Calculation of the PageRank for BabelNet took 0.06756114959716797s
Interlinking | Calculation of Degree of Connection for BabelNet took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BabelNet took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.0001838207244873047s
Believability | Calculation of trust value for BabelNet took 1.239776611328125e-05s
INFO | --- Analysis for babelnet took 125.53514218330383s
Availability | SPARQL endpoint availability check for Bacevicius.lt took 0.000102996826171875s
Availability | VoID file availability check for Bacevicius.lt took 0.8984341621398926s
Completeness | Calculation of interlinking completeness for Bacevicius.lt took 0.7548549175262451s
Reputation | Calculation of the PageRank for Bacevicius.lt took 0.021069049835205078s
Interlinking | Calculation of Degree of Connection for Bacevicius.lt took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bacevicius.lt took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Bacevicius.lt took 2.9087066650390625e-05s
Believability | Calculation of trust value for Bacevicius.lt took 1.3113021850585938e-05s
INFO | --- Analysis for Bacevicius.lt took 123.82217192649841s
Availability | SPARQL endpoint availability check for Basisregistratie Adressen en Gebouwen took 0.6074981689453125s
Availability | VoID file availability check for Basisregistratie Adressen en Gebouwen took 0.7736177444458008s
Completeness | Calculation of interlinking completeness for Basisregistratie Adressen en Gebouwen took 60.414167404174805s
Reputation | Calculation of the PageRank for Basisregistratie Adressen en Gebouwen took 0.020923137664794922s
Interlinking | Calculation of Degree of Connection for Basisregistratie Adressen en Gebouwen took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Basisregistratie Adressen en Gebouwen took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Basisregistratie Adressen en Gebouwen took 5.412101745605469e-05s
Believability | Calculation of trust value for Basisregistratie Adressen en Gebouwen took 1.239776611328125e-05s
INFO | --- Analysis for bag took 245.6806242465973s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 0.289508581161499s
Availability | VoID file availability check for 红色经典歌曲 took 0.02269434928894043s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 120.3670585155487s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020748615264892578s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 2.6226043701171875e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.71661376953125e-05s
INFO | --- Analysis for baixue took 301.7475109100342s
Availability | SPARQL endpoint availability check for baixue composer took 8.487701416015625e-05s
Availability | VoID file availability check for baixue composer took 0.006574392318725586s
Completeness | Calculation of interlinking completeness for baixue composer took 0.34059762954711914s
Reputation | Calculation of the PageRank for baixue composer took 0.0209197998046875s
Interlinking | Calculation of Degree of Connection for baixue composer took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for baixue composer took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for baixue composer took 2.8371810913085938e-05s
Believability | Calculation of trust value for baixue composer took 1.2874603271484375e-05s
INFO | --- Analysis for baixue_composer took 122.94439721107483s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 8.630752563476562e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.007742643356323242s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.34523606300354004s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020699024200439453s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 2.8848648071289062e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.1682510375976562e-05s
INFO | --- Analysis for baixue_imagery took 6.082067251205444s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 8.559226989746094e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.008348703384399414s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.4922468662261963s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.02086186408996582s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 2.8371810913085938e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.3113021850585938e-05s
INFO | --- Analysis for baixue_imagery1 took 4.297344923019409s
Availability | SPARQL endpoint availability check for BAMS took 0.00010442733764648438s
Availability | VoID file availability check for BAMS took 20.271313190460205s
Completeness | Calculation of interlinking completeness for BAMS took 0.32803940773010254s
Reputation | Calculation of the PageRank for BAMS took 0.020477771759033203s
Interlinking | Calculation of Degree of Connection for BAMS took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for BAMS took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for BAMS took 3.933906555175781e-05s
Believability | Calculation of trust value for BAMS took 1.2159347534179688e-05s
INFO | --- Analysis for bams took 29.678595542907715s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 8.487701416015625e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.0008161067962646484s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 0.32114577293395996s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.02085709571838379s
Interlinking | Calculation of Degree of Connection for Basque EuroWordNet-lemon lexicon (3.0) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Basque EuroWordNet-lemon lexicon (3.0) took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 3.719329833984375e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 1.1444091796875e-05s
INFO | --- Analysis for basque-eurowordnet-lemon-lexicon-3-0 took 2.785658597946167s
Availability | SPARQL endpoint availability check for BBC Music took 0.3031949996948242s
Availability | VoID file availability check for BBC Music took 0.2602202892303467s
Completeness | Calculation of interlinking completeness for BBC Music took 0.31334662437438965s
Reputation | Calculation of the PageRank for BBC Music took 0.020907163619995117s
Interlinking | Calculation of Degree of Connection for BBC Music took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for BBC Music took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.0001323223114013672s
Believability | Calculation of trust value for BBC Music took 1.2636184692382812e-05s
INFO | --- Analysis for bbc-music took 3.2803759574890137s
Availability | SPARQL endpoint availability check for BBC Programmes took 0.2783162593841553s
Availability | VoID file availability check for BBC Programmes took 0.3759002685546875s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.29873156547546387s
Reputation | Calculation of the PageRank for BBC Programmes took 0.0204012393951416s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 0.00010466575622558594s
Believability | Calculation of trust value for BBC Programmes took 1.2874603271484375e-05s
INFO | --- Analysis for bbc-programmes took 9.867035865783691s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.30072474479675293s
Availability | VoID file availability check for BBC Wildlife Finder took 0.38010573387145996s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 0.3149874210357666s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.02164459228515625s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 0.00010657310485839844s
Believability | Calculation of trust value for BBC Wildlife Finder took 1.2159347534179688e-05s
INFO | --- Analysis for bbc-wildlife-finder took 8.400861024856567s
Availability | SPARQL endpoint availability check for BBOP took 8.440017700195312e-05s
Availability | VoID file availability check for BBOP took 0.48608970642089844s
Completeness | Calculation of interlinking completeness for BBOP took 0.34227585792541504s
Reputation | Calculation of the PageRank for BBOP took 0.020764827728271484s
Interlinking | Calculation of Degree of Connection for BBOP took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.743171691894531e-05s
Believability | Calculation of trust value for BBOP took 1.3589859008789062e-05s
INFO | --- Analysis for bbop took 19.532127857208252s
Availability | SPARQL endpoint availability check for BBOP took 8.58306884765625e-05s
Availability | VoID file availability check for BBOP took 0.5117940902709961s
Completeness | Calculation of interlinking completeness for BBOP took 0.3249664306640625s
Reputation | Calculation of the PageRank for BBOP took 0.020472049713134766s
Interlinking | Calculation of Degree of Connection for BBOP took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for BBOP took 2.8371810913085938e-05s
Believability | Calculation of trust value for BBOP took 1.4066696166992188e-05s
INFO | --- Analysis for bbop-selected took 18.186764240264893s
Availability | SPARQL endpoint availability check for Bdgp took 1.355515718460083s
Availability | VoID file availability check for Bdgp took 0.7584850788116455s
Completeness | Calculation of interlinking completeness for Bdgp took 0.3219411373138428s
Reputation | Calculation of the PageRank for Bdgp took 0.02027153968811035s
Interlinking | Calculation of Degree of Connection for Bdgp took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bdgp took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Bdgp took 2.8371810913085938e-05s
Believability | Calculation of trust value for Bdgp took 1.1682510375976562e-05s
INFO | --- Analysis for bdgp took 4.544830083847046s
Availability | SPARQL endpoint availability check for Bendev Junior took 8.177757263183594e-05s
Availability | VoID file availability check for Bendev Junior took 2.1284289360046387s
Completeness | Calculation of interlinking completeness for Bendev Junior took 0.37545251846313477s
Reputation | Calculation of the PageRank for Bendev Junior took 0.021124839782714844s
Interlinking | Calculation of Degree of Connection for Bendev Junior took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bendev Junior took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Bendev Junior took 3.218650817871094e-05s
Believability | Calculation of trust value for Bendev Junior took 1.3113021850585938e-05s
INFO | --- Analysis for bendevoficial took 4.82438063621521s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 2.328416347503662s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 3.670222043991089s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.3529064655303955s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.022503376007080078s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 6.723403930664062e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 9.775161743164062e-06s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 13.995409965515137s
Availability | SPARQL endpoint availability check for Berlin Offener Haushalt took 4.076957702636719e-05s
Availability | VoID file availability check for Berlin Offener Haushalt took 0.008260965347290039s
Completeness | Calculation of interlinking completeness for Berlin Offener Haushalt took 0.4417235851287842s
Reputation | Calculation of the PageRank for Berlin Offener Haushalt took 0.020923852920532227s
Interlinking | Calculation of Degree of Connection for Berlin Offener Haushalt took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Berlin Offener Haushalt took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Berlin Offener Haushalt took 2.956390380859375e-05s
Believability | Calculation of trust value for Berlin Offener Haushalt took 1.0967254638671875e-05s
INFO | --- Analysis for berlin-offener-haushalt took 2.013004779815674s
Availability | SPARQL endpoint availability check for berlios took 8.392333984375e-05s
Availability | VoID file availability check for berlios took 0.000316619873046875s
Completeness | Calculation of interlinking completeness for berlios took 0.3520073890686035s
Reputation | Calculation of the PageRank for berlios took 0.02122950553894043s
Interlinking | Calculation of Degree of Connection for berlios took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for berlios took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for berlios took 9.679794311523438e-05s
Believability | Calculation of trust value for berlios took 1.239776611328125e-05s
INFO | --- Analysis for berlios took 2.2285780906677246s
Availability | SPARQL endpoint availability check for Between Our Worlds took 8.606910705566406e-05s
Availability | VoID file availability check for Between Our Worlds took 0.3932485580444336s
Completeness | Calculation of interlinking completeness for Between Our Worlds took 0.38203859329223633s
Reputation | Calculation of the PageRank for Between Our Worlds took 0.020963668823242188s
Interlinking | Calculation of Degree of Connection for Between Our Worlds took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Between Our Worlds took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Between Our Worlds took 6.818771362304688e-05s
Believability | Calculation of trust value for Between Our Worlds took 1.3589859008789062e-05s
INFO | --- Analysis for betweenourworlds took 9.304885864257812s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.11693286895751953s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.00659942626953125s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.3100554943084717s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.020947933197021484s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.131431579589844e-05s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.5367431640625e-06s
INFO | --- Analysis for bfs-linked-data took 1.9159343242645264s
Availability | SPARQL endpoint availability check for BibBase took 0.0840904712677002s
Availability | VoID file availability check for BibBase took 0.008213996887207031s
Completeness | Calculation of interlinking completeness for BibBase took 0.44864964485168457s
Reputation | Calculation of the PageRank for BibBase took 0.020732879638671875s
Interlinking | Calculation of Degree of Connection for BibBase took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BibBase took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for BibBase took 9.5367431640625e-05s
Believability | Calculation of trust value for BibBase took 1.430511474609375e-05s
INFO | --- Analysis for bibbase took 2.2117059230804443s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 8.678436279296875e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 1.4739675521850586s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.571772575378418s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.02082347869873047s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 0.00011873245239257812s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 1.239776611328125e-05s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 11.74394679069519s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 8.535385131835938e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.00022792816162109375s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.42958784103393555s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.021510839462280273s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 9.894371032714844e-05s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 1.1205673217773438e-05s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 8.72139835357666s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 8.630752563476562e-05s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.000865936279296875s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.3241081237792969s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.02072310447692871s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 2.8133392333984375e-05s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 1.0728836059570312e-05s
INFO | --- Analysis for biblioteca-virtual-miguel-de-cervantes-bvmc-linked-open-data took 2.3933181762695312s
Availability | SPARQL endpoint availability check for BibSonomy - The blue social bookmark and publication sharing system. took 8.249282836914062e-05s
Availability | VoID file availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.7021429538726807s
Completeness | Calculation of interlinking completeness for BibSonomy - The blue social bookmark and publication sharing system. took 0.32402873039245605s
Reputation | Calculation of the PageRank for BibSonomy - The blue social bookmark and publication sharing system. took 0.021501779556274414s
Interlinking | Calculation of Degree of Connection for BibSonomy - The blue social bookmark and publication sharing system. took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BibSonomy - The blue social bookmark and publication sharing system. took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for BibSonomy - The blue social bookmark and publication sharing system. took 3.314018249511719e-05s
Believability | Calculation of trust value for BibSonomy - The blue social bookmark and publication sharing system. took 1.2636184692382812e-05s
INFO | --- Analysis for BibSonomy took 5.748423099517822s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 8.58306884765625e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.8522205352783203s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.48009467124938965s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.020526409149169922s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 3.0279159545898438e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 1.0728836059570312e-05s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 7.767422676086426s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 8.845329284667969e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.21055102348327637s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 1.1455786228179932s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.021362781524658203s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2010 took 3.0517578125e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2010 took 1.2159347534179688e-05s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 3.193018913269043s
Availability | SPARQL endpoint availability check for Bio2RDF::ACFSID took 1.3307018280029297s
Availability | VoID file availability check for Bio2RDF::ACFSID took 0.00029158592224121094s
Completeness | Calculation of interlinking completeness for Bio2RDF::ACFSID took 0.29674839973449707s
Reputation | Calculation of the PageRank for Bio2RDF::ACFSID took 0.022703170776367188s
Interlinking | Calculation of Degree of Connection for Bio2RDF::ACFSID took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::ACFSID took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::ACFSID took 3.743171691894531e-05s
Believability | Calculation of trust value for Bio2RDF::ACFSID took 1.0967254638671875e-05s
INFO | --- Analysis for bio2rdf-acfsid took 13.812621831893921s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 0.27738285064697266s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.7876782417297363s
Extra | Recovery of all triples for Bio2RDF::Affymetrix took 19.302721738815308s
Performance | Total latancy measurement for Bio2RDF::Affymetrix took 0.5520586967468262s
Amount of data | Number of triples check for Bio2RDF::Affymetrix took 45.596898794174194s
Interoperability | New terms check for Bio2RDF::Affymetrix took 42.29179763793945s
Versatility | Languages check for Bio2RDF::Affymetrix took 60.170472145080566s
Interpretability | Number of blank nodes check for Bio2RDF::Affymetrix took 0.1569819450378418s
Interpretability | RDF structures check for Bio2RDF::Affymetrix took 0.5347468852996826s
Versatility | Serialization formats check for Bio2RDF::Affymetrix took 0.16265535354614258s
Availability | RDF dump link check for Bio2RDF::Affymetrix took 3.07277250289917s
License | MR license check for Bio2RDF::Affymetrix took 0.39011216163635254s
License | HR license check for Bio2RDF::Affymetrix took 60.120630502700806s
Amount of data | Number of property check for Bio2RDF::Affymetrix took 0.14039969444274902s
Understandability | Number of label check for Bio2RDF::Affymetrix took 9.669963121414185s
Understandability | URI regex check for Bio2RDF::Affymetrix took 0.4244554042816162s
Understandability | Vocabs check for Bio2RDF::Affymetrix took 0.12718439102172852s
Verifiability | Authors check for Bio2RDF::Affymetrix took 0.1451871395111084s
Verifiability | Publishers check for Bio2RDF::Affymetrix took 0.38860583305358887s
Performance | Throughput check for Bio2RDF::Affymetrix took 10.644805192947388s
Verifiability | Contribs. check for Bio2RDF::Affymetrix took 0.4645564556121826s
Interlinking | sameAs chians check for Bio2RDF::Affymetrix took 0.18342137336730957s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.7217750549316406s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.20431256294250488s
Timeliness | dataset update frequency check for Bio2RDF::Affymetrix took 0.15477657318115234s
Currency | Creation date check for Bio2RDF::Affymetrix took 0.23515844345092773s
Currency | Modification date check for Bio2RDF::Affymetrix took 0.14599823951721191s
Rep.Conc. | URIs length for Bio2RDF::Affymetrix took 107.29866433143616s
Interoperability | New vocabularies check for Bio2RDF::Affymetrix took 18.990862131118774s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Affymetrix took 0.337841272354126s
Accuracy | Check Functional Property for Bio2RDF::Affymetrix took 0.16746187210083008s
Accuracy | Check Inverse Functional Property for Bio2RDF::Affymetrix took 0.13129782676696777s
Accuracy | Check Empty annotation labels for Bio2RDF::Affymetrix took 6.318398952484131s
Accuracy | Check White space in annotation for Bio2RDF::Affymetrix took 0.8916935920715332s
Accuracy | Check Datatype consistency for Bio2RDF::Affymetrix took 0.6493668556213379s
Consistency | Disjoint class check for Bio2RDF::Affymetrix took 0.3084890842437744s
Consistency | Check Misplaced properties for Bio2RDF::Affymetrix took 64.89423394203186s
Consistency | Misplaced classes for Bio2RDF::Affymetrix took 2.301692485809326s
Consistency | Check Ontology hijacking for Bio2RDF::Affymetrix took 6.602138996124268s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Affymetrix took 1.3627219200134277s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Affymetrix took 61.46288990974426s
Conciseness | Check Extensional conciseness for Bio2RDF::Affymetrix took 0.7587621212005615s
Conciseness | Check Intensional conciseness for Bio2RDF::Affymetrix took 0.2963392734527588s
Security | Sign check for Bio2RDF::Affymetrix took 0.11686015129089355s
Availability | Check URIs Dereferenciability for Bio2RDF::Affymetrix took 3.8648111820220947s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 9.54859471321106s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.021317243576049805s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0006844997406005859s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 9.274482727050781e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Affymetrix took 16.745789766311646s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 1.33514404296875e-05s
INFO | --- Analysis for bio2rdf-affymetrix took 1035.3313825130463s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 0.5843651294708252s
Availability | VoID file availability check for Bio2RDF::Biomodels took 1.0813162326812744s
Extra | Recovery of all triples for Bio2RDF::Biomodels took 17.64989733695984s
Performance | Total latancy measurement for Bio2RDF::Biomodels took 1.31666898727417s
Amount of data | Number of triples check for Bio2RDF::Biomodels took 44.65411925315857s
Interoperability | New terms check for Bio2RDF::Biomodels took 40.99667978286743s
Versatility | Languages check for Bio2RDF::Biomodels took 60.26562857627869s
Interpretability | Number of blank nodes check for Bio2RDF::Biomodels took 0.2732079029083252s
Security | Check HTTPS for Bio2RDF::Biomodels took 0.15628838539123535s
Interpretability | RDF structures check for Bio2RDF::Biomodels took 0.3108067512512207s
Versatility | Serialization formats check for Bio2RDF::Biomodels took 0.2592477798461914s
Availability | RDF dump link check for Bio2RDF::Biomodels took 2.9785125255584717s
License | MR license check for Bio2RDF::Biomodels took 0.2664649486541748s
License | HR license check for Bio2RDF::Biomodels took 60.27908158302307s
Amount of data | Number of property check for Bio2RDF::Biomodels took 0.26015400886535645s
Understandability | Number of label check for Bio2RDF::Biomodels took 8.949976682662964s
Understandability | URI regex check for Bio2RDF::Biomodels took 0.65604567527771s
Understandability | Vocabs check for Bio2RDF::Biomodels took 0.25738954544067383s
Verifiability | Authors check for Bio2RDF::Biomodels took 0.2922194004058838s
Verifiability | Publishers check for Bio2RDF::Biomodels took 0.5285646915435791s
Performance | Throughput check for Bio2RDF::Biomodels took 10.521546125411987s
Verifiability | Contribs. check for Bio2RDF::Biomodels took 0.6424000263214111s
Interlinking | sameAs chians check for Bio2RDF::Biomodels took 0.30655717849731445s
Interlinking | skos check for Bio2RDF::Biomodels took 0.3940563201904297s
Interlinking | skos check for Bio2RDF::Biomodels took 0.42967772483825684s
Timeliness | dataset update frequency check for Bio2RDF::Biomodels took 0.28726816177368164s
Currency | Creation date check for Bio2RDF::Biomodels took 0.380047082901001s
Currency | Modification date check for Bio2RDF::Biomodels took 0.23634910583496094s
Rep.Conc. | URIs length for Bio2RDF::Biomodels took 107.36204099655151s
Interoperability | New vocabularies check for Bio2RDF::Biomodels took 18.97786545753479s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Biomodels took 0.511127233505249s
Accuracy | Check Functional Property for Bio2RDF::Biomodels took 0.27966809272766113s
Accuracy | Check Inverse Functional Property for Bio2RDF::Biomodels took 0.2389986515045166s
Accuracy | Check Empty annotation labels for Bio2RDF::Biomodels took 7.435319423675537s
Accuracy | Check White space in annotation for Bio2RDF::Biomodels took 0.9046335220336914s
Accuracy | Check Datatype consistency for Bio2RDF::Biomodels took 0.6857140064239502s
Consistency | Disjoint class check for Bio2RDF::Biomodels took 0.3229489326477051s
Consistency | Check Misplaced properties for Bio2RDF::Biomodels took 65.10996508598328s
Consistency | Misplaced classes for Bio2RDF::Biomodels took 2.425692558288574s
Consistency | Check Ontology hijacking for Bio2RDF::Biomodels took 6.09706711769104s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Biomodels took 1.296539306640625s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Biomodels took 61.59308862686157s
Conciseness | Check Extensional conciseness for Bio2RDF::Biomodels took 0.7147035598754883s
Conciseness | Check Intensional conciseness for Bio2RDF::Biomodels took 0.4448668956756592s
Security | Sign check for Bio2RDF::Biomodels took 0.28162479400634766s
Availability | Check URIs Dereferenciability for Bio2RDF::Biomodels took 3.965914249420166s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 0.8108630180358887s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.020337343215942383s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0007898807525634766s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.00012040138244628906s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Biomodels took 18.69451665878296s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 1.3589859008789062e-05s
INFO | --- Analysis for bio2rdf-biomodels took 1033.2226614952087s
Availability | SPARQL endpoint availability check for Bio2RDF::BioModels::BioPAX took 0.15309453010559082s
Availability | VoID file availability check for Bio2RDF::BioModels::BioPAX took 0.0002033710479736328s
Completeness | Calculation of interlinking completeness for Bio2RDF::BioModels::BioPAX took 0.31219959259033203s
Reputation | Calculation of the PageRank for Bio2RDF::BioModels::BioPAX took 0.021450281143188477s
Interlinking | Calculation of Degree of Connection for Bio2RDF::BioModels::BioPAX took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::BioModels::BioPAX took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::BioModels::BioPAX took 3.218650817871094e-05s
Believability | Calculation of trust value for Bio2RDF::BioModels::BioPAX took 1.1444091796875e-05s
INFO | --- Analysis for bio2rdf-biomodels-biopax took 3.020221710205078s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 0.5194392204284668s
Availability | VoID file availability check for Bio2RDF::Bioportal took 1.0009856224060059s
Extra | Recovery of all triples for Bio2RDF::Bioportal took 18.890456914901733s
Performance | Total latancy measurement for Bio2RDF::Bioportal took 1.387460708618164s
Amount of data | Number of triples check for Bio2RDF::Bioportal took 45.07809662818909s
Interoperability | New terms check for Bio2RDF::Bioportal took 40.972249031066895s
Versatility | Languages check for Bio2RDF::Bioportal took 60.23091101646423s
Interpretability | Number of blank nodes check for Bio2RDF::Bioportal took 0.2753634452819824s
Security | Check HTTPS for Bio2RDF::Bioportal took 0.15804767608642578s
Interpretability | RDF structures check for Bio2RDF::Bioportal took 0.28248047828674316s
Versatility | Serialization formats check for Bio2RDF::Bioportal took 0.2857356071472168s
Availability | RDF dump link check for Bio2RDF::Bioportal took 3.135305643081665s
License | MR license check for Bio2RDF::Bioportal took 0.3318459987640381s
License | HR license check for Bio2RDF::Bioportal took 60.258124113082886s
Amount of data | Number of property check for Bio2RDF::Bioportal took 0.24736571311950684s
Understandability | Number of label check for Bio2RDF::Bioportal took 9.157176733016968s
Understandability | URI regex check for Bio2RDF::Bioportal took 0.6439738273620605s
Understandability | Vocabs check for Bio2RDF::Bioportal took 0.2482619285583496s
Verifiability | Authors check for Bio2RDF::Bioportal took 0.27448439598083496s
Verifiability | Publishers check for Bio2RDF::Bioportal took 0.35869407653808594s
Performance | Throughput check for Bio2RDF::Bioportal took 10.984636545181274s
Verifiability | Contribs. check for Bio2RDF::Bioportal took 0.6406073570251465s
Interlinking | sameAs chians check for Bio2RDF::Bioportal took 0.2644321918487549s
Interlinking | skos check for Bio2RDF::Bioportal took 0.4969313144683838s
Interlinking | skos check for Bio2RDF::Bioportal took 0.41849470138549805s
Timeliness | dataset update frequency check for Bio2RDF::Bioportal took 0.261458158493042s
Currency | Creation date check for Bio2RDF::Bioportal took 0.38515210151672363s
Currency | Modification date check for Bio2RDF::Bioportal took 0.26157689094543457s
Rep.Conc. | URIs length for Bio2RDF::Bioportal took 106.68295502662659s
Interoperability | New vocabularies check for Bio2RDF::Bioportal took 20.0349178314209s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Bioportal took 0.425342321395874s
Accuracy | Check Functional Property for Bio2RDF::Bioportal took 0.2700331211090088s
Accuracy | Check Inverse Functional Property for Bio2RDF::Bioportal took 0.2432999610900879s
Accuracy | Check Empty annotation labels for Bio2RDF::Bioportal took 6.795114278793335s
Accuracy | Check White space in annotation for Bio2RDF::Bioportal took 0.8983745574951172s
Accuracy | Check Datatype consistency for Bio2RDF::Bioportal took 0.6982071399688721s
Consistency | Disjoint class check for Bio2RDF::Bioportal took 0.2537410259246826s
Consistency | Check Misplaced properties for Bio2RDF::Bioportal took 64.86135673522949s
Consistency | Misplaced classes for Bio2RDF::Bioportal took 2.403883457183838s
Consistency | Check Ontology hijacking for Bio2RDF::Bioportal took 6.028586387634277s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Bioportal took 1.2939794063568115s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Bioportal took 61.586867332458496s
Conciseness | Check Extensional conciseness for Bio2RDF::Bioportal took 0.7378635406494141s
Conciseness | Check Intensional conciseness for Bio2RDF::Bioportal took 0.4349985122680664s
Security | Sign check for Bio2RDF::Bioportal took 0.3155500888824463s
Availability | Check URIs Dereferenciability for Bio2RDF::Bioportal took 3.8341588973999023s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 1.3285489082336426s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.024300575256347656s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.0004482269287109375s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Bioportal took 17.679790019989014s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 1.33514404296875e-05s
INFO | --- Analysis for bio2rdf-bioportal took 1045.1825952529907s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 0.15556097030639648s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.008640527725219727s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 0.6354646682739258s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.02215576171875s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 5.173683166503906e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-chembl took 24.38332200050354s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 0.5050747394561768s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 1.0500223636627197s
Extra | Recovery of all triples for Bio2RDF::Clinicaltrials took 18.3379123210907s
Performance | Total latancy measurement for Bio2RDF::Clinicaltrials took 1.320953130722046s
Amount of data | Number of triples check for Bio2RDF::Clinicaltrials took 45.167025566101074s
Interoperability | New terms check for Bio2RDF::Clinicaltrials took 40.80866599082947s
Versatility | Languages check for Bio2RDF::Clinicaltrials took 60.261165618896484s
Interpretability | Number of blank nodes check for Bio2RDF::Clinicaltrials took 0.2737748622894287s
Security | Check HTTPS for Bio2RDF::Clinicaltrials took 0.18693995475769043s
Interpretability | RDF structures check for Bio2RDF::Clinicaltrials took 0.2880382537841797s
Versatility | Serialization formats check for Bio2RDF::Clinicaltrials took 0.26428866386413574s
Availability | RDF dump link check for Bio2RDF::Clinicaltrials took 2.790208578109741s
License | MR license check for Bio2RDF::Clinicaltrials took 0.22606897354125977s
License | HR license check for Bio2RDF::Clinicaltrials took 60.29829430580139s
Amount of data | Number of property check for Bio2RDF::Clinicaltrials took 0.29764342308044434s
Understandability | Number of label check for Bio2RDF::Clinicaltrials took 9.337510347366333s
Understandability | URI regex check for Bio2RDF::Clinicaltrials took 0.6038527488708496s
Understandability | Vocabs check for Bio2RDF::Clinicaltrials took 0.28087306022644043s
Verifiability | Authors check for Bio2RDF::Clinicaltrials took 0.28018641471862793s
Verifiability | Publishers check for Bio2RDF::Clinicaltrials took 0.336620569229126s
Performance | Throughput check for Bio2RDF::Clinicaltrials took 10.560616254806519s
Verifiability | Contribs. check for Bio2RDF::Clinicaltrials took 0.6270232200622559s
Interlinking | sameAs chians check for Bio2RDF::Clinicaltrials took 0.28325390815734863s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.3632314205169678s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.34714293479919434s
Timeliness | dataset update frequency check for Bio2RDF::Clinicaltrials took 0.2914547920227051s
Currency | Creation date check for Bio2RDF::Clinicaltrials took 0.3774564266204834s
Currency | Modification date check for Bio2RDF::Clinicaltrials took 0.27393007278442383s
Rep.Conc. | URIs length for Bio2RDF::Clinicaltrials took 108.03510165214539s
Interoperability | New vocabularies check for Bio2RDF::Clinicaltrials took 17.860706329345703s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Clinicaltrials took 0.441880464553833s
Accuracy | Check Functional Property for Bio2RDF::Clinicaltrials took 0.27944517135620117s
Accuracy | Check Inverse Functional Property for Bio2RDF::Clinicaltrials took 0.3018980026245117s
Accuracy | Check Empty annotation labels for Bio2RDF::Clinicaltrials took 6.130194902420044s
Accuracy | Check White space in annotation for Bio2RDF::Clinicaltrials took 0.889664888381958s
Accuracy | Check Datatype consistency for Bio2RDF::Clinicaltrials took 0.6552364826202393s
Consistency | Disjoint class check for Bio2RDF::Clinicaltrials took 0.2623775005340576s
Consistency | Check Misplaced properties for Bio2RDF::Clinicaltrials took 64.9357807636261s
Consistency | Misplaced classes for Bio2RDF::Clinicaltrials took 2.4442789554595947s
Consistency | Check Ontology hijacking for Bio2RDF::Clinicaltrials took 5.896920442581177s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Clinicaltrials took 1.3084495067596436s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Clinicaltrials took 61.62449049949646s
Conciseness | Check Extensional conciseness for Bio2RDF::Clinicaltrials took 0.7357749938964844s
Conciseness | Check Intensional conciseness for Bio2RDF::Clinicaltrials took 0.5047247409820557s
Security | Sign check for Bio2RDF::Clinicaltrials took 0.2610154151916504s
Availability | Check URIs Dereferenciability for Bio2RDF::Clinicaltrials took 3.701061725616455s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 0.577716588973999s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.02057647705078125s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0006823539733886719s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 5.316734313964844e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Clinicaltrials took 17.074020862579346s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-clinicaltrials took 1027.4059073925018s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 0.5007121562957764s
Availability | VoID file availability check for Bio2RDF::Ctd took 1.0558745861053467s
Extra | Recovery of all triples for Bio2RDF::Ctd took 18.245391845703125s
Performance | Total latancy measurement for Bio2RDF::Ctd took 1.3214962482452393s
Amount of data | Number of triples check for Bio2RDF::Ctd took 45.193236112594604s
Interoperability | New terms check for Bio2RDF::Ctd took 40.69509220123291s
Versatility | Languages check for Bio2RDF::Ctd took 60.267616987228394s
Interpretability | Number of blank nodes check for Bio2RDF::Ctd took 0.2541632652282715s
Security | Check HTTPS for Bio2RDF::Ctd took 0.1828012466430664s
Interpretability | RDF structures check for Bio2RDF::Ctd took 0.2710762023925781s
Versatility | Serialization formats check for Bio2RDF::Ctd took 0.2887234687805176s
Availability | RDF dump link check for Bio2RDF::Ctd took 3.0728118419647217s
License | MR license check for Bio2RDF::Ctd took 0.23520517349243164s
License | HR license check for Bio2RDF::Ctd took 60.27125024795532s
Amount of data | Number of property check for Bio2RDF::Ctd took 0.23285317420959473s
Understandability | Number of label check for Bio2RDF::Ctd took 9.408069133758545s
Understandability | URI regex check for Bio2RDF::Ctd took 0.5771579742431641s
Understandability | Vocabs check for Bio2RDF::Ctd took 0.2737393379211426s
Verifiability | Authors check for Bio2RDF::Ctd took 0.28490161895751953s
Verifiability | Publishers check for Bio2RDF::Ctd took 0.3567025661468506s
Performance | Throughput check for Bio2RDF::Ctd took 10.813567161560059s
Verifiability | Contribs. check for Bio2RDF::Ctd took 0.6334562301635742s
Interlinking | sameAs chians check for Bio2RDF::Ctd took 0.2697105407714844s
Interlinking | skos check for Bio2RDF::Ctd took 0.3638467788696289s
Interlinking | skos check for Bio2RDF::Ctd took 0.363720178604126s
Timeliness | dataset update frequency check for Bio2RDF::Ctd took 0.24207067489624023s
Currency | Creation date check for Bio2RDF::Ctd took 0.35877418518066406s
Currency | Modification date check for Bio2RDF::Ctd took 0.2694580554962158s
Rep.Conc. | URIs length for Bio2RDF::Ctd took 106.98307347297668s
Interoperability | New vocabularies check for Bio2RDF::Ctd took 17.605344772338867s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ctd took 0.4139869213104248s
Accuracy | Check Functional Property for Bio2RDF::Ctd took 0.273090124130249s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ctd took 0.24251842498779297s
Accuracy | Check Empty annotation labels for Bio2RDF::Ctd took 6.328820466995239s
Accuracy | Check White space in annotation for Bio2RDF::Ctd took 0.8890349864959717s
Accuracy | Check Datatype consistency for Bio2RDF::Ctd took 0.6421318054199219s
Consistency | Disjoint class check for Bio2RDF::Ctd took 0.2552468776702881s
Consistency | Check Misplaced properties for Bio2RDF::Ctd took 64.83620309829712s
Consistency | Misplaced classes for Bio2RDF::Ctd took 2.303314208984375s
Consistency | Check Ontology hijacking for Bio2RDF::Ctd took 6.942333698272705s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ctd took 1.358058214187622s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ctd took 61.6597216129303s
Conciseness | Check Extensional conciseness for Bio2RDF::Ctd took 0.7306296825408936s
Conciseness | Check Intensional conciseness for Bio2RDF::Ctd took 0.45116353034973145s
Security | Sign check for Bio2RDF::Ctd took 0.2398681640625s
Availability | Check URIs Dereferenciability for Bio2RDF::Ctd took 3.923001527786255s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 2.1845788955688477s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.020689725875854492s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 6.532669067382812e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ctd took 17.125749588012695s
Believability | Calculation of trust value for Bio2RDF::Ctd took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-ctd took 1042.8963356018066s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 4.172325134277344e-05s
Availability | VoID file availability check for bio2rdf-dataset took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 0.38517141342163086s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.021711349487304688s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 5.269050598144531e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-dataset took 2.1960620880126953s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 0.5221309661865234s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 1.0542619228363037s
Extra | Recovery of all triples for Bio2RDF::Dbsnp took 18.375537157058716s
Performance | Total latancy measurement for Bio2RDF::Dbsnp took 1.252397060394287s
Amount of data | Number of triples check for Bio2RDF::Dbsnp took 44.311906814575195s
Interoperability | New terms check for Bio2RDF::Dbsnp took 41.46921706199646s
Versatility | Languages check for Bio2RDF::Dbsnp took 60.27922081947327s
Interpretability | Number of blank nodes check for Bio2RDF::Dbsnp took 0.28803539276123047s
Security | Check HTTPS for Bio2RDF::Dbsnp took 0.16872143745422363s
Interpretability | RDF structures check for Bio2RDF::Dbsnp took 0.28340721130371094s
Versatility | Serialization formats check for Bio2RDF::Dbsnp took 0.2945680618286133s
Availability | RDF dump link check for Bio2RDF::Dbsnp took 2.750033378601074s
License | MR license check for Bio2RDF::Dbsnp took 0.2413332462310791s
License | HR license check for Bio2RDF::Dbsnp took 60.28018879890442s
Amount of data | Number of property check for Bio2RDF::Dbsnp took 0.2659571170806885s
Understandability | Number of label check for Bio2RDF::Dbsnp took 9.351237297058105s
Understandability | URI regex check for Bio2RDF::Dbsnp took 0.5770759582519531s
Understandability | Vocabs check for Bio2RDF::Dbsnp took 0.2728278636932373s
Verifiability | Authors check for Bio2RDF::Dbsnp took 0.28455066680908203s
Verifiability | Publishers check for Bio2RDF::Dbsnp took 0.3859097957611084s
Performance | Throughput check for Bio2RDF::Dbsnp took 10.584083557128906s
Verifiability | Contribs. check for Bio2RDF::Dbsnp took 1.019197940826416s
Interlinking | sameAs chians check for Bio2RDF::Dbsnp took 0.2758948802947998s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.5127005577087402s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.3216524124145508s
Timeliness | dataset update frequency check for Bio2RDF::Dbsnp took 0.258620023727417s
Currency | Creation date check for Bio2RDF::Dbsnp took 0.35001564025878906s
Currency | Modification date check for Bio2RDF::Dbsnp took 0.263716459274292s
Rep.Conc. | URIs length for Bio2RDF::Dbsnp took 106.13547825813293s
Interoperability | New vocabularies check for Bio2RDF::Dbsnp took 15.674890041351318s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Dbsnp took 0.4588596820831299s
Accuracy | Check Functional Property for Bio2RDF::Dbsnp took 0.2272951602935791s
Accuracy | Check Inverse Functional Property for Bio2RDF::Dbsnp took 0.29154467582702637s
Accuracy | Check Empty annotation labels for Bio2RDF::Dbsnp took 6.123842716217041s
Accuracy | Check White space in annotation for Bio2RDF::Dbsnp took 0.8902420997619629s
Accuracy | Check Datatype consistency for Bio2RDF::Dbsnp took 0.6529099941253662s
Consistency | Disjoint class check for Bio2RDF::Dbsnp took 0.29984426498413086s
Consistency | Check Misplaced properties for Bio2RDF::Dbsnp took 65.33927321434021s
Consistency | Misplaced classes for Bio2RDF::Dbsnp took 2.366286277770996s
Consistency | Check Ontology hijacking for Bio2RDF::Dbsnp took 6.041010856628418s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Dbsnp took 1.2966761589050293s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Dbsnp took 61.64221119880676s
Conciseness | Check Extensional conciseness for Bio2RDF::Dbsnp took 0.7496359348297119s
Conciseness | Check Intensional conciseness for Bio2RDF::Dbsnp took 0.40105366706848145s
Security | Sign check for Bio2RDF::Dbsnp took 0.23693466186523438s
Availability | Check URIs Dereferenciability for Bio2RDF::Dbsnp took 3.674929141998291s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 1.4162306785583496s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.020931243896484375s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 6.246566772460938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 8.225440979003906e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Dbsnp took 15.275259256362915s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 1.33514404296875e-05s
INFO | --- Analysis for bio2rdf-dbsnp took 1023.8765549659729s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 0.4951765537261963s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.9935436248779297s
Extra | Recovery of all triples for Bio2RDF::Drugbank took 18.203513383865356s
Performance | Total latancy measurement for Bio2RDF::Drugbank took 1.3734352588653564s
Amount of data | Number of triples check for Bio2RDF::Drugbank took 45.49123001098633s
Interoperability | New terms check for Bio2RDF::Drugbank took 40.952221393585205s
Versatility | Languages check for Bio2RDF::Drugbank took 60.31380224227905s
Interpretability | Number of blank nodes check for Bio2RDF::Drugbank took 0.2896695137023926s
Security | Check HTTPS for Bio2RDF::Drugbank took 0.16687464714050293s
Interpretability | RDF structures check for Bio2RDF::Drugbank took 0.27292823791503906s
Versatility | Serialization formats check for Bio2RDF::Drugbank took 0.2987966537475586s
Availability | RDF dump link check for Bio2RDF::Drugbank took 2.8819832801818848s
License | MR license check for Bio2RDF::Drugbank took 0.2657475471496582s
License | HR license check for Bio2RDF::Drugbank took 60.30401587486267s
Amount of data | Number of property check for Bio2RDF::Drugbank took 0.2778482437133789s
Understandability | Number of label check for Bio2RDF::Drugbank took 9.2353994846344s
Understandability | URI regex check for Bio2RDF::Drugbank took 0.5645177364349365s
Understandability | Vocabs check for Bio2RDF::Drugbank took 0.29346299171447754s
Verifiability | Authors check for Bio2RDF::Drugbank took 0.32014918327331543s
Verifiability | Publishers check for Bio2RDF::Drugbank took 0.40491437911987305s
Performance | Throughput check for Bio2RDF::Drugbank took 10.957192659378052s
Verifiability | Contribs. check for Bio2RDF::Drugbank took 0.6560897827148438s
Interlinking | sameAs chians check for Bio2RDF::Drugbank took 0.3004329204559326s
Interlinking | skos check for Bio2RDF::Drugbank took 0.7519433498382568s
Interlinking | skos check for Bio2RDF::Drugbank took 0.5288558006286621s
Timeliness | dataset update frequency check for Bio2RDF::Drugbank took 0.2438957691192627s
Currency | Creation date check for Bio2RDF::Drugbank took 0.37877964973449707s
Currency | Modification date check for Bio2RDF::Drugbank took 0.2783341407775879s
Rep.Conc. | URIs length for Bio2RDF::Drugbank took 106.2410192489624s
Interoperability | New vocabularies check for Bio2RDF::Drugbank took 17.897979021072388s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Drugbank took 0.5010297298431396s
Accuracy | Check Functional Property for Bio2RDF::Drugbank took 0.27977561950683594s
Accuracy | Check Inverse Functional Property for Bio2RDF::Drugbank took 0.26094579696655273s
Accuracy | Check Empty annotation labels for Bio2RDF::Drugbank took 6.836502552032471s
Accuracy | Check White space in annotation for Bio2RDF::Drugbank took 0.8861613273620605s
Accuracy | Check Datatype consistency for Bio2RDF::Drugbank took 0.6628997325897217s
Consistency | Disjoint class check for Bio2RDF::Drugbank took 0.27086639404296875s
Consistency | Check Misplaced properties for Bio2RDF::Drugbank took 64.74587512016296s
Consistency | Misplaced classes for Bio2RDF::Drugbank took 2.956289529800415s
Consistency | Check Ontology hijacking for Bio2RDF::Drugbank took 6.449634552001953s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Drugbank took 1.3401274681091309s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Drugbank took 61.53587031364441s
Conciseness | Check Extensional conciseness for Bio2RDF::Drugbank took 0.7114987373352051s
Conciseness | Check Intensional conciseness for Bio2RDF::Drugbank took 0.46681976318359375s
Security | Sign check for Bio2RDF::Drugbank took 0.2796194553375244s
Availability | Check URIs Dereferenciability for Bio2RDF::Drugbank took 3.726198196411133s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 0.9572272300720215s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.020209789276123047s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.00010514259338378906s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Drugbank took 18.32448697090149s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-drugbank took 1040.2547478675842s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 0.5266890525817871s
Availability | VoID file availability check for Bio2RDF::Genage took 1.0691688060760498s
Extra | Recovery of all triples for Bio2RDF::Genage took 18.128535747528076s
Performance | Total latancy measurement for Bio2RDF::Genage took 1.2597968578338623s
Amount of data | Number of triples check for Bio2RDF::Genage took 44.88302135467529s
Interoperability | New terms check for Bio2RDF::Genage took 40.990259647369385s
Versatility | Languages check for Bio2RDF::Genage took 60.25848722457886s
Interpretability | Number of blank nodes check for Bio2RDF::Genage took 0.25238656997680664s
Security | Check HTTPS for Bio2RDF::Genage took 0.18786907196044922s
Interpretability | RDF structures check for Bio2RDF::Genage took 0.242875337600708s
Versatility | Serialization formats check for Bio2RDF::Genage took 0.26574182510375977s
Availability | RDF dump link check for Bio2RDF::Genage took 2.924408435821533s
License | MR license check for Bio2RDF::Genage took 0.2960991859436035s
License | HR license check for Bio2RDF::Genage took 60.27289819717407s
Amount of data | Number of property check for Bio2RDF::Genage took 0.2404477596282959s
Understandability | Number of label check for Bio2RDF::Genage took 8.885716199874878s
Understandability | URI regex check for Bio2RDF::Genage took 0.6413288116455078s
Understandability | Vocabs check for Bio2RDF::Genage took 0.2704744338989258s
Verifiability | Authors check for Bio2RDF::Genage took 0.2416849136352539s
Verifiability | Publishers check for Bio2RDF::Genage took 0.35288357734680176s
Performance | Throughput check for Bio2RDF::Genage took 10.64308762550354s
Verifiability | Contribs. check for Bio2RDF::Genage took 0.6358687877655029s
Interlinking | sameAs chians check for Bio2RDF::Genage took 0.28557372093200684s
Interlinking | skos check for Bio2RDF::Genage took 0.3423604965209961s
Interlinking | skos check for Bio2RDF::Genage took 0.3413863182067871s
Timeliness | dataset update frequency check for Bio2RDF::Genage took 0.24465441703796387s
Currency | Creation date check for Bio2RDF::Genage took 0.369901180267334s
Currency | Modification date check for Bio2RDF::Genage took 0.26334667205810547s
Rep.Conc. | URIs length for Bio2RDF::Genage took 106.77174282073975s
Interoperability | New vocabularies check for Bio2RDF::Genage took 17.727458477020264s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Genage took 0.43166136741638184s
Accuracy | Check Functional Property for Bio2RDF::Genage took 0.2849280834197998s
Accuracy | Check Inverse Functional Property for Bio2RDF::Genage took 0.2357501983642578s
Accuracy | Check Empty annotation labels for Bio2RDF::Genage took 6.443161725997925s
Accuracy | Check White space in annotation for Bio2RDF::Genage took 0.8919022083282471s
Accuracy | Check Datatype consistency for Bio2RDF::Genage took 0.6849954128265381s
Consistency | Disjoint class check for Bio2RDF::Genage took 0.4265248775482178s
Consistency | Check Misplaced properties for Bio2RDF::Genage took 64.86534261703491s
Consistency | Misplaced classes for Bio2RDF::Genage took 2.474231004714966s
Consistency | Check Ontology hijacking for Bio2RDF::Genage took 5.969469785690308s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Genage took 1.3571033477783203s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Genage took 61.62788939476013s
Conciseness | Check Extensional conciseness for Bio2RDF::Genage took 0.7549927234649658s
Conciseness | Check Intensional conciseness for Bio2RDF::Genage took 0.4551424980163574s
Security | Sign check for Bio2RDF::Genage took 0.25371265411376953s
Availability | Check URIs Dereferenciability for Bio2RDF::Genage took 3.874070167541504s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 4.728747367858887s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.02042531967163086s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 5.5789947509765625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Genage took 17.509989500045776s
Believability | Calculation of trust value for Bio2RDF::Genage took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-genage took 1037.9022359848022s
Availability | SPARQL endpoint availability check for Bio2RDF::GenBank took 0.1531391143798828s
Availability | VoID file availability check for Bio2RDF::GenBank took 0.009585380554199219s
Completeness | Calculation of interlinking completeness for Bio2RDF::GenBank took 0.8061299324035645s
Reputation | Calculation of the PageRank for Bio2RDF::GenBank took 0.022479772567749023s
Interlinking | Calculation of Degree of Connection for Bio2RDF::GenBank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::GenBank took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::GenBank took 6.031990051269531e-05s
Believability | Calculation of trust value for Bio2RDF::GenBank took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-genbank took 6.112335920333862s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 0.49312925338745117s
Availability | VoID file availability check for Bio2RDF::Gendr took 1.0928378105163574s
Extra | Recovery of all triples for Bio2RDF::Gendr took 18.755737781524658s
Performance | Total latancy measurement for Bio2RDF::Gendr took 1.365049123764038s
Amount of data | Number of triples check for Bio2RDF::Gendr took 45.654191732406616s
Interoperability | New terms check for Bio2RDF::Gendr took 43.47535943984985s
Versatility | Languages check for Bio2RDF::Gendr took 60.28996181488037s
Interpretability | Number of blank nodes check for Bio2RDF::Gendr took 0.26963186264038086s
Security | Check HTTPS for Bio2RDF::Gendr took 0.20281744003295898s
Interpretability | RDF structures check for Bio2RDF::Gendr took 0.25160789489746094s
Versatility | Serialization formats check for Bio2RDF::Gendr took 0.28197693824768066s
Availability | RDF dump link check for Bio2RDF::Gendr took 2.9228675365448s
License | MR license check for Bio2RDF::Gendr took 0.24716639518737793s
License | HR license check for Bio2RDF::Gendr took 60.27052450180054s
Amount of data | Number of property check for Bio2RDF::Gendr took 0.29654979705810547s
Understandability | Number of label check for Bio2RDF::Gendr took 9.468668699264526s
Understandability | URI regex check for Bio2RDF::Gendr took 0.6122546195983887s
Understandability | Vocabs check for Bio2RDF::Gendr took 0.25810980796813965s
Verifiability | Authors check for Bio2RDF::Gendr took 0.2555966377258301s
Verifiability | Publishers check for Bio2RDF::Gendr took 0.38332438468933105s
Performance | Throughput check for Bio2RDF::Gendr took 10.842992305755615s
Verifiability | Contribs. check for Bio2RDF::Gendr took 0.6766843795776367s
Interlinking | sameAs chians check for Bio2RDF::Gendr took 0.2746446132659912s
Interlinking | skos check for Bio2RDF::Gendr took 0.36992359161376953s
Interlinking | skos check for Bio2RDF::Gendr took 0.3885781764984131s
Timeliness | dataset update frequency check for Bio2RDF::Gendr took 0.2621309757232666s
Currency | Creation date check for Bio2RDF::Gendr took 0.34063005447387695s
Currency | Modification date check for Bio2RDF::Gendr took 0.27938294410705566s
Rep.Conc. | URIs length for Bio2RDF::Gendr took 107.68299436569214s
Interoperability | New vocabularies check for Bio2RDF::Gendr took 18.601665496826172s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Gendr took 0.438201904296875s
Accuracy | Check Functional Property for Bio2RDF::Gendr took 0.2776963710784912s
Accuracy | Check Inverse Functional Property for Bio2RDF::Gendr took 0.2901787757873535s
Accuracy | Check Empty annotation labels for Bio2RDF::Gendr took 6.639554738998413s
Accuracy | Check White space in annotation for Bio2RDF::Gendr took 0.8948161602020264s
Accuracy | Check Datatype consistency for Bio2RDF::Gendr took 0.6516187191009521s
Consistency | Disjoint class check for Bio2RDF::Gendr took 0.2721891403198242s
Consistency | Check Misplaced properties for Bio2RDF::Gendr took 65.21049571037292s
Consistency | Misplaced classes for Bio2RDF::Gendr took 2.4380738735198975s
Consistency | Check Ontology hijacking for Bio2RDF::Gendr took 6.231870174407959s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Gendr took 1.3626213073730469s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Gendr took 61.595250606536865s
Conciseness | Check Extensional conciseness for Bio2RDF::Gendr took 0.7167191505432129s
Conciseness | Check Intensional conciseness for Bio2RDF::Gendr took 0.45929694175720215s
Security | Sign check for Bio2RDF::Gendr took 0.2845573425292969s
Availability | Check URIs Dereferenciability for Bio2RDF::Gendr took 3.930075168609619s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 0.6316928863525391s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.020793437957763672s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 6.0558319091796875e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Gendr took 17.17309308052063s
Believability | Calculation of trust value for Bio2RDF::Gendr took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-gendr took 1044.1511232852936s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 0.5257761478424072s
Availability | VoID file availability check for Bio2RDF::Goa took 1.0058133602142334s
Extra | Recovery of all triples for Bio2RDF::Goa took 17.924540996551514s
Performance | Total latancy measurement for Bio2RDF::Goa took 1.3877403736114502s
Amount of data | Number of triples check for Bio2RDF::Goa took 46.12525773048401s
Interoperability | New terms check for Bio2RDF::Goa took 41.23423719406128s
Versatility | Languages check for Bio2RDF::Goa took 60.267683029174805s
Interpretability | Number of blank nodes check for Bio2RDF::Goa took 0.31381702423095703s
Security | Check HTTPS for Bio2RDF::Goa took 0.16912150382995605s
Interpretability | RDF structures check for Bio2RDF::Goa took 0.276705265045166s
Versatility | Serialization formats check for Bio2RDF::Goa took 0.245802640914917s
Availability | RDF dump link check for Bio2RDF::Goa took 2.906418561935425s
License | MR license check for Bio2RDF::Goa took 0.32993054389953613s
License | HR license check for Bio2RDF::Goa took 60.248366355895996s
Amount of data | Number of property check for Bio2RDF::Goa took 0.28168225288391113s
Understandability | Number of label check for Bio2RDF::Goa took 9.758639812469482s
Understandability | URI regex check for Bio2RDF::Goa took 0.556729793548584s
Understandability | Vocabs check for Bio2RDF::Goa took 0.2543015480041504s
Verifiability | Authors check for Bio2RDF::Goa took 0.2861487865447998s
Verifiability | Publishers check for Bio2RDF::Goa took 0.394977331161499s
Performance | Throughput check for Bio2RDF::Goa took 10.771154403686523s
Verifiability | Contribs. check for Bio2RDF::Goa took 0.653203010559082s
Interlinking | sameAs chians check for Bio2RDF::Goa took 0.2779998779296875s
Interlinking | skos check for Bio2RDF::Goa took 0.6264402866363525s
Interlinking | skos check for Bio2RDF::Goa took 0.34401869773864746s
Timeliness | dataset update frequency check for Bio2RDF::Goa took 0.2524445056915283s
Currency | Creation date check for Bio2RDF::Goa took 0.33331847190856934s
Currency | Modification date check for Bio2RDF::Goa took 0.25199460983276367s
Rep.Conc. | URIs length for Bio2RDF::Goa took 109.30117797851562s
Interoperability | New vocabularies check for Bio2RDF::Goa took 18.076707124710083s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Goa took 0.4443056583404541s
Accuracy | Check Functional Property for Bio2RDF::Goa took 0.2227632999420166s
Accuracy | Check Inverse Functional Property for Bio2RDF::Goa took 0.2792372703552246s
Accuracy | Check Empty annotation labels for Bio2RDF::Goa took 6.861344814300537s
Accuracy | Check White space in annotation for Bio2RDF::Goa took 0.8928089141845703s
Accuracy | Check Datatype consistency for Bio2RDF::Goa took 0.6580135822296143s
Consistency | Disjoint class check for Bio2RDF::Goa took 0.3177454471588135s
Consistency | Check Misplaced properties for Bio2RDF::Goa took 65.13148331642151s
Consistency | Misplaced classes for Bio2RDF::Goa took 2.3103506565093994s
Consistency | Check Ontology hijacking for Bio2RDF::Goa took 5.704368352890015s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Goa took 1.3078582286834717s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Goa took 61.596935510635376s
Conciseness | Check Extensional conciseness for Bio2RDF::Goa took 0.7222020626068115s
Conciseness | Check Intensional conciseness for Bio2RDF::Goa took 0.4804103374481201s
Security | Sign check for Bio2RDF::Goa took 0.27668237686157227s
Availability | Check URIs Dereferenciability for Bio2RDF::Goa took 3.754709243774414s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 1.201509714126587s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.020309925079345703s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 6.461143493652344e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Goa took 18.945299863815308s
Believability | Calculation of trust value for Bio2RDF::Goa took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-goa took 1088.6163511276245s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 0.4879796504974365s
Availability | VoID file availability check for Bio2RDF::Hgnc took 1.0103609561920166s
Extra | Recovery of all triples for Bio2RDF::Hgnc took 18.34968662261963s
Performance | Total latancy measurement for Bio2RDF::Hgnc took 1.343170166015625s
Amount of data | Number of triples check for Bio2RDF::Hgnc took 45.07806038856506s
Interoperability | New terms check for Bio2RDF::Hgnc took 40.779659032821655s
Versatility | Languages check for Bio2RDF::Hgnc took 60.22432732582092s
Interpretability | Number of blank nodes check for Bio2RDF::Hgnc took 0.2768826484680176s
Security | Check HTTPS for Bio2RDF::Hgnc took 0.1412968635559082s
Interpretability | RDF structures check for Bio2RDF::Hgnc took 0.2528390884399414s
Versatility | Serialization formats check for Bio2RDF::Hgnc took 0.2737557888031006s
Availability | RDF dump link check for Bio2RDF::Hgnc took 3.0611214637756348s
License | MR license check for Bio2RDF::Hgnc took 0.2517085075378418s
License | HR license check for Bio2RDF::Hgnc took 60.25985336303711s
Amount of data | Number of property check for Bio2RDF::Hgnc took 0.3070378303527832s
Understandability | Number of label check for Bio2RDF::Hgnc took 9.58592677116394s
Understandability | URI regex check for Bio2RDF::Hgnc took 0.6382541656494141s
Understandability | Vocabs check for Bio2RDF::Hgnc took 0.263838529586792s
Verifiability | Authors check for Bio2RDF::Hgnc took 0.24277663230895996s
Verifiability | Publishers check for Bio2RDF::Hgnc took 0.39794278144836426s
Performance | Throughput check for Bio2RDF::Hgnc took 10.849755048751831s
Verifiability | Contribs. check for Bio2RDF::Hgnc took 0.6660323143005371s
Interlinking | sameAs chians check for Bio2RDF::Hgnc took 0.29671740531921387s
Interlinking | skos check for Bio2RDF::Hgnc took 0.3606433868408203s
Interlinking | skos check for Bio2RDF::Hgnc took 0.38271450996398926s
Timeliness | dataset update frequency check for Bio2RDF::Hgnc took 0.2363588809967041s
Currency | Creation date check for Bio2RDF::Hgnc took 0.40511298179626465s
Currency | Modification date check for Bio2RDF::Hgnc took 0.27039551734924316s
Rep.Conc. | URIs length for Bio2RDF::Hgnc took 108.85895156860352s
Interoperability | New vocabularies check for Bio2RDF::Hgnc took 18.24487853050232s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Hgnc took 0.4557669162750244s
Accuracy | Check Functional Property for Bio2RDF::Hgnc took 0.24852633476257324s
Accuracy | Check Inverse Functional Property for Bio2RDF::Hgnc took 0.2485651969909668s
Accuracy | Check Empty annotation labels for Bio2RDF::Hgnc took 6.956366777420044s
Accuracy | Check White space in annotation for Bio2RDF::Hgnc took 0.894132137298584s
Accuracy | Check Datatype consistency for Bio2RDF::Hgnc took 0.6723458766937256s
Consistency | Disjoint class check for Bio2RDF::Hgnc took 0.24139189720153809s
Consistency | Check Misplaced properties for Bio2RDF::Hgnc took 64.79368686676025s
Consistency | Misplaced classes for Bio2RDF::Hgnc took 2.380826950073242s
Consistency | Check Ontology hijacking for Bio2RDF::Hgnc took 6.253901481628418s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Hgnc took 1.333033561706543s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Hgnc took 61.54070329666138s
Conciseness | Check Extensional conciseness for Bio2RDF::Hgnc took 0.775153636932373s
Conciseness | Check Intensional conciseness for Bio2RDF::Hgnc took 0.408583402633667s
Security | Sign check for Bio2RDF::Hgnc took 0.28089451789855957s
Availability | Check URIs Dereferenciability for Bio2RDF::Hgnc took 20.111468076705933s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 0.5832781791687012s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.020330429077148438s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.00011610984802246094s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Hgnc took 17.28736114501953s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-hgnc took 1047.8797237873077s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 0.4908585548400879s
Availability | VoID file availability check for Bio2RDF::Homologene took 1.0350604057312012s
Extra | Recovery of all triples for Bio2RDF::Homologene took 17.873547792434692s
Performance | Total latancy measurement for Bio2RDF::Homologene took 1.3291633129119873s
Amount of data | Number of triples check for Bio2RDF::Homologene took 44.82020401954651s
Interoperability | New terms check for Bio2RDF::Homologene took 40.076005935668945s
Versatility | Languages check for Bio2RDF::Homologene took 60.22663903236389s
Interpretability | Number of blank nodes check for Bio2RDF::Homologene took 0.2620353698730469s
Security | Check HTTPS for Bio2RDF::Homologene took 0.16300463676452637s
Interpretability | RDF structures check for Bio2RDF::Homologene took 0.38488245010375977s
Versatility | Serialization formats check for Bio2RDF::Homologene took 0.28523802757263184s
Availability | RDF dump link check for Bio2RDF::Homologene took 2.92380952835083s
License | MR license check for Bio2RDF::Homologene took 0.39040040969848633s
License | HR license check for Bio2RDF::Homologene took 60.288169145584106s
Amount of data | Number of property check for Bio2RDF::Homologene took 0.27909040451049805s
Understandability | Number of label check for Bio2RDF::Homologene took 8.871548652648926s
Understandability | URI regex check for Bio2RDF::Homologene took 0.5763001441955566s
Understandability | Vocabs check for Bio2RDF::Homologene took 0.25437259674072266s
Verifiability | Authors check for Bio2RDF::Homologene took 0.3101925849914551s
Verifiability | Publishers check for Bio2RDF::Homologene took 0.4008772373199463s
Performance | Throughput check for Bio2RDF::Homologene took 10.747686386108398s
Verifiability | Contribs. check for Bio2RDF::Homologene took 0.587653636932373s
Interlinking | sameAs chians check for Bio2RDF::Homologene took 0.30629563331604004s
Interlinking | skos check for Bio2RDF::Homologene took 0.6944794654846191s
Interlinking | skos check for Bio2RDF::Homologene took 0.41375112533569336s
Timeliness | dataset update frequency check for Bio2RDF::Homologene took 0.2852511405944824s
Currency | Creation date check for Bio2RDF::Homologene took 0.39760303497314453s
Currency | Modification date check for Bio2RDF::Homologene took 0.2759735584259033s
Rep.Conc. | URIs length for Bio2RDF::Homologene took 107.4876754283905s
Interoperability | New vocabularies check for Bio2RDF::Homologene took 17.695347547531128s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Homologene took 0.46127867698669434s
Accuracy | Check Functional Property for Bio2RDF::Homologene took 0.24190926551818848s
Accuracy | Check Inverse Functional Property for Bio2RDF::Homologene took 0.3283569812774658s
Accuracy | Check Empty annotation labels for Bio2RDF::Homologene took 6.684910297393799s
Accuracy | Check White space in annotation for Bio2RDF::Homologene took 0.8948910236358643s
Accuracy | Check Datatype consistency for Bio2RDF::Homologene took 0.669076681137085s
Consistency | Disjoint class check for Bio2RDF::Homologene took 0.27582263946533203s
Consistency | Check Misplaced properties for Bio2RDF::Homologene took 64.86968398094177s
Consistency | Misplaced classes for Bio2RDF::Homologene took 2.4527926445007324s
Consistency | Check Ontology hijacking for Bio2RDF::Homologene took 6.217858552932739s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Homologene took 1.3237879276275635s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Homologene took 61.56755542755127s
Conciseness | Check Extensional conciseness for Bio2RDF::Homologene took 0.7487375736236572s
Conciseness | Check Intensional conciseness for Bio2RDF::Homologene took 0.5020742416381836s
Security | Sign check for Bio2RDF::Homologene took 0.3042604923248291s
Availability | Check URIs Dereferenciability for Bio2RDF::Homologene took 3.8559839725494385s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 0.6051900386810303s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.020363569259643555s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 5.364418029785156e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Homologene took 17.3927903175354s
Believability | Calculation of trust value for Bio2RDF::Homologene took 1.3589859008789062e-05s
INFO | --- Analysis for bio2rdf-homologene took 1032.1809587478638s
Availability | SPARQL endpoint availability check for Bio2RDF::INOH took 0.9600951671600342s
Availability | VoID file availability check for Bio2RDF::INOH took 0.0002396106719970703s
Completeness | Calculation of interlinking completeness for Bio2RDF::INOH took 1.1069045066833496s
Reputation | Calculation of the PageRank for Bio2RDF::INOH took 0.021683216094970703s
Interlinking | Calculation of Degree of Connection for Bio2RDF::INOH took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::INOH took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::INOH took 3.337860107421875e-05s
Believability | Calculation of trust value for Bio2RDF::INOH took 1.33514404296875e-05s
INFO | --- Analysis for bio2rdf-inoh took 6.731146574020386s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 0.4651949405670166s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.9493997097015381s
Extra | Recovery of all triples for Bio2RDF::Interpro took 18.49191951751709s
Performance | Total latancy measurement for Bio2RDF::Interpro took 1.3635947704315186s
Amount of data | Number of triples check for Bio2RDF::Interpro took 44.63728976249695s
Interoperability | New terms check for Bio2RDF::Interpro took 41.20493292808533s
Versatility | Languages check for Bio2RDF::Interpro took 60.27961468696594s
Interpretability | Number of blank nodes check for Bio2RDF::Interpro took 0.27387547492980957s
Security | Check HTTPS for Bio2RDF::Interpro took 0.16950345039367676s
Interpretability | RDF structures check for Bio2RDF::Interpro took 0.2768094539642334s
Versatility | Serialization formats check for Bio2RDF::Interpro took 0.2571580410003662s
Availability | RDF dump link check for Bio2RDF::Interpro took 2.989283561706543s
License | MR license check for Bio2RDF::Interpro took 0.2765500545501709s
License | HR license check for Bio2RDF::Interpro took 60.27010154724121s
Amount of data | Number of property check for Bio2RDF::Interpro took 0.2736027240753174s
Understandability | Number of label check for Bio2RDF::Interpro took 9.424829959869385s
Understandability | URI regex check for Bio2RDF::Interpro took 0.6154344081878662s
Understandability | Vocabs check for Bio2RDF::Interpro took 0.2894406318664551s
Verifiability | Authors check for Bio2RDF::Interpro took 0.2554631233215332s
Verifiability | Publishers check for Bio2RDF::Interpro took 0.35640501976013184s
Performance | Throughput check for Bio2RDF::Interpro took 10.605540990829468s
Verifiability | Contribs. check for Bio2RDF::Interpro took 0.6405205726623535s
Interlinking | sameAs chians check for Bio2RDF::Interpro took 0.29662466049194336s
Interlinking | skos check for Bio2RDF::Interpro took 0.5725109577178955s
Interlinking | skos check for Bio2RDF::Interpro took 0.3565409183502197s
Timeliness | dataset update frequency check for Bio2RDF::Interpro took 0.2583620548248291s
Currency | Creation date check for Bio2RDF::Interpro took 0.38033223152160645s
Currency | Modification date check for Bio2RDF::Interpro took 0.2490673065185547s
Rep.Conc. | URIs length for Bio2RDF::Interpro took 107.34517860412598s
Interoperability | New vocabularies check for Bio2RDF::Interpro took 18.88506555557251s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Interpro took 0.4369513988494873s
Accuracy | Check Functional Property for Bio2RDF::Interpro took 0.29741430282592773s
Accuracy | Check Inverse Functional Property for Bio2RDF::Interpro took 0.2880253791809082s
Accuracy | Check Empty annotation labels for Bio2RDF::Interpro took 6.667650938034058s
Accuracy | Check White space in annotation for Bio2RDF::Interpro took 0.8961145877838135s
Accuracy | Check Datatype consistency for Bio2RDF::Interpro took 0.6524410247802734s
Consistency | Disjoint class check for Bio2RDF::Interpro took 0.42319369316101074s
Consistency | Check Misplaced properties for Bio2RDF::Interpro took 64.99697852134705s
Consistency | Misplaced classes for Bio2RDF::Interpro took 2.3782644271850586s
Consistency | Check Ontology hijacking for Bio2RDF::Interpro took 6.200075626373291s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Interpro took 1.2953927516937256s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Interpro took 61.56978249549866s
Conciseness | Check Extensional conciseness for Bio2RDF::Interpro took 0.722158670425415s
Conciseness | Check Intensional conciseness for Bio2RDF::Interpro took 0.4683961868286133s
Security | Sign check for Bio2RDF::Interpro took 0.27135348320007324s
Availability | Check URIs Dereferenciability for Bio2RDF::Interpro took 3.4898855686187744s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 0.4122605323791504s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.02048182487487793s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0006861686706542969s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 0.00010013580322265625s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Interpro took 17.56490182876587s
Believability | Calculation of trust value for Bio2RDF::Interpro took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-interpro took 1033.1245021820068s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 0.14753389358520508s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.0073506832122802734s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 2.989907741546631s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.019994020462036133s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0006842613220214844s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 7.43865966796875e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-iproclass took 25.300907850265503s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 0.48831987380981445s
Availability | VoID file availability check for Bio2RDF::Irefindex took 1.0437326431274414s
Extra | Recovery of all triples for Bio2RDF::Irefindex took 18.189417600631714s
Performance | Total latancy measurement for Bio2RDF::Irefindex took 1.2739789485931396s
Amount of data | Number of triples check for Bio2RDF::Irefindex took 46.04837775230408s
Interoperability | New terms check for Bio2RDF::Irefindex took 40.5936484336853s
Versatility | Languages check for Bio2RDF::Irefindex took 60.28298282623291s
Interpretability | Number of blank nodes check for Bio2RDF::Irefindex took 0.2831535339355469s
Security | Check HTTPS for Bio2RDF::Irefindex took 0.1703786849975586s
Interpretability | RDF structures check for Bio2RDF::Irefindex took 0.26912474632263184s
Versatility | Serialization formats check for Bio2RDF::Irefindex took 0.25539374351501465s
Availability | RDF dump link check for Bio2RDF::Irefindex took 2.7969229221343994s
License | MR license check for Bio2RDF::Irefindex took 0.43194007873535156s
License | HR license check for Bio2RDF::Irefindex took 60.24414777755737s
Amount of data | Number of property check for Bio2RDF::Irefindex took 0.2610960006713867s
Understandability | Number of label check for Bio2RDF::Irefindex took 9.146620512008667s
Understandability | URI regex check for Bio2RDF::Irefindex took 0.627530574798584s
Understandability | Vocabs check for Bio2RDF::Irefindex took 0.2730448246002197s
Verifiability | Authors check for Bio2RDF::Irefindex took 0.26508164405822754s
Verifiability | Publishers check for Bio2RDF::Irefindex took 0.414642333984375s
Performance | Throughput check for Bio2RDF::Irefindex took 10.578470945358276s
Verifiability | Contribs. check for Bio2RDF::Irefindex took 0.6712706089019775s
Interlinking | sameAs chians check for Bio2RDF::Irefindex took 0.2767002582550049s
Interlinking | skos check for Bio2RDF::Irefindex took 0.736243486404419s
Interlinking | skos check for Bio2RDF::Irefindex took 0.3591156005859375s
Timeliness | dataset update frequency check for Bio2RDF::Irefindex took 0.254044771194458s
Currency | Creation date check for Bio2RDF::Irefindex took 0.3791508674621582s
Currency | Modification date check for Bio2RDF::Irefindex took 0.28585362434387207s
Rep.Conc. | URIs length for Bio2RDF::Irefindex took 108.35817074775696s
Interoperability | New vocabularies check for Bio2RDF::Irefindex took 18.50878119468689s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Irefindex took 0.5116922855377197s
Accuracy | Check Functional Property for Bio2RDF::Irefindex took 0.26850366592407227s
Accuracy | Check Inverse Functional Property for Bio2RDF::Irefindex took 0.26900696754455566s
Accuracy | Check Empty annotation labels for Bio2RDF::Irefindex took 6.70955753326416s
Accuracy | Check White space in annotation for Bio2RDF::Irefindex took 0.8980076313018799s
Accuracy | Check Datatype consistency for Bio2RDF::Irefindex took 0.6617410182952881s
Consistency | Disjoint class check for Bio2RDF::Irefindex took 0.43804073333740234s
Consistency | Check Misplaced properties for Bio2RDF::Irefindex took 64.85840606689453s
Consistency | Misplaced classes for Bio2RDF::Irefindex took 2.3597397804260254s
Consistency | Check Ontology hijacking for Bio2RDF::Irefindex took 6.449338912963867s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Irefindex took 1.3068461418151855s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Irefindex took 61.63028836250305s
Conciseness | Check Extensional conciseness for Bio2RDF::Irefindex took 0.7447242736816406s
Conciseness | Check Intensional conciseness for Bio2RDF::Irefindex took 0.4538700580596924s
Security | Sign check for Bio2RDF::Irefindex took 0.2640674114227295s
Availability | Check URIs Dereferenciability for Bio2RDF::Irefindex took 3.6536126136779785s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 0.9304060935974121s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.020704030990600586s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 9.679794311523438e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Irefindex took 18.239603757858276s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-irefindex took 1037.1196281909943s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG took 0.48153042793273926s
Availability | VoID file availability check for Bio2RDF::KEGG took 0.0003695487976074219s
Extra | Recovery of all triples for Bio2RDF::KEGG took 17.79960322380066s
Performance | Total latancy measurement for Bio2RDF::KEGG took 1.353994369506836s
Amount of data | Number of triples check for Bio2RDF::KEGG took 45.25518536567688s
Interoperability | New terms check for Bio2RDF::KEGG took 40.11464238166809s
Versatility | Languages check for Bio2RDF::KEGG took 60.25479078292847s
Interpretability | Number of blank nodes check for Bio2RDF::KEGG took 0.2602674961090088s
Security | Check HTTPS for Bio2RDF::KEGG took 0.18409085273742676s
Interpretability | RDF structures check for Bio2RDF::KEGG took 0.27424049377441406s
Versatility | Serialization formats check for Bio2RDF::KEGG took 0.2577359676361084s
Availability | RDF dump link check for Bio2RDF::KEGG took 2.9246881008148193s
License | MR license check for Bio2RDF::KEGG took 0.3175220489501953s
License | HR license check for Bio2RDF::KEGG took 60.25123620033264s
Amount of data | Number of property check for Bio2RDF::KEGG took 0.2740349769592285s
Understandability | Number of label check for Bio2RDF::KEGG took 9.738305807113647s
Understandability | URI regex check for Bio2RDF::KEGG took 0.6107945442199707s
Understandability | Vocabs check for Bio2RDF::KEGG took 0.28986668586730957s
Verifiability | Authors check for Bio2RDF::KEGG took 0.2624232769012451s
Verifiability | Publishers check for Bio2RDF::KEGG took 0.36354780197143555s
Performance | Throughput check for Bio2RDF::KEGG took 10.560571908950806s
Verifiability | Contribs. check for Bio2RDF::KEGG took 0.6489622592926025s
Interlinking | sameAs chians check for Bio2RDF::KEGG took 0.2855832576751709s
Interlinking | skos check for Bio2RDF::KEGG took 0.3760240077972412s
Interlinking | skos check for Bio2RDF::KEGG took 0.38761281967163086s
Timeliness | dataset update frequency check for Bio2RDF::KEGG took 0.2939488887786865s
Currency | Creation date check for Bio2RDF::KEGG took 0.3610708713531494s
Currency | Modification date check for Bio2RDF::KEGG took 0.24689340591430664s
Rep.Conc. | URIs length for Bio2RDF::KEGG took 110.20130920410156s
Interoperability | New vocabularies check for Bio2RDF::KEGG took 17.801313638687134s
Consistency | Deprecated classes/propertiers check for Bio2RDF::KEGG took 0.49182820320129395s
Accuracy | Check Functional Property for Bio2RDF::KEGG took 0.27985262870788574s
Accuracy | Check Inverse Functional Property for Bio2RDF::KEGG took 0.3065159320831299s
Accuracy | Check Empty annotation labels for Bio2RDF::KEGG took 7.187045335769653s
Accuracy | Check White space in annotation for Bio2RDF::KEGG took 0.8896505832672119s
Accuracy | Check Datatype consistency for Bio2RDF::KEGG took 0.6671459674835205s
Consistency | Disjoint class check for Bio2RDF::KEGG took 0.2947196960449219s
Consistency | Check Misplaced properties for Bio2RDF::KEGG took 65.13124108314514s
Consistency | Misplaced classes for Bio2RDF::KEGG took 2.4604392051696777s
Consistency | Check Ontology hijacking for Bio2RDF::KEGG took 6.371171951293945s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::KEGG took 1.3576796054840088s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::KEGG took 61.6133086681366s
Conciseness | Check Extensional conciseness for Bio2RDF::KEGG took 0.7321901321411133s
Conciseness | Check Intensional conciseness for Bio2RDF::KEGG took 0.42880821228027344s
Security | Sign check for Bio2RDF::KEGG took 0.2922353744506836s
Availability | Check URIs Dereferenciability for Bio2RDF::KEGG took 3.5378127098083496s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG took 0.481414794921875s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG took 0.020864486694335938s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG took 6.699562072753906e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::KEGG took 17.85761022567749s
Believability | Calculation of trust value for Bio2RDF::KEGG took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-kegg took 1027.6486704349518s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG::BioPAX took 0.1316671371459961s
Availability | VoID file availability check for Bio2RDF::KEGG::BioPAX took 0.0005567073822021484s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG::BioPAX took 0.5099365711212158s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG::BioPAX took 0.021567821502685547s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG::BioPAX took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG::BioPAX took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG::BioPAX took 3.2901763916015625e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG::BioPAX took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-kegg-biopax took 7.569984436035156s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 0.1429147720336914s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.009129762649536133s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 2.5550334453582764s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.020403623580932617s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 2.86102294921875e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 9.059906005859375e-06s
INFO | --- Analysis for bio2rdf-linkedspl took 16.253001928329468s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 0.4975588321685791s
Availability | VoID file availability check for Bio2RDF::Lsr took 1.0289943218231201s
Extra | Recovery of all triples for Bio2RDF::Lsr took 19.84780502319336s
Performance | Total latancy measurement for Bio2RDF::Lsr took 1.2942240238189697s
Amount of data | Number of triples check for Bio2RDF::Lsr took 45.421619176864624s
Interoperability | New terms check for Bio2RDF::Lsr took 41.47800898551941s
Versatility | Languages check for Bio2RDF::Lsr took 60.27524209022522s
Interpretability | Number of blank nodes check for Bio2RDF::Lsr took 0.25830626487731934s
Security | Check HTTPS for Bio2RDF::Lsr took 0.18416213989257812s
Interpretability | RDF structures check for Bio2RDF::Lsr took 0.24446845054626465s
Versatility | Serialization formats check for Bio2RDF::Lsr took 0.2567574977874756s
Availability | RDF dump link check for Bio2RDF::Lsr took 2.9386425018310547s
License | MR license check for Bio2RDF::Lsr took 0.260204553604126s
License | HR license check for Bio2RDF::Lsr took 60.25585651397705s
Amount of data | Number of property check for Bio2RDF::Lsr took 0.24771761894226074s
Understandability | Number of label check for Bio2RDF::Lsr took 9.62921690940857s
Understandability | URI regex check for Bio2RDF::Lsr took 0.667395830154419s
Understandability | Vocabs check for Bio2RDF::Lsr took 0.27086806297302246s
Verifiability | Authors check for Bio2RDF::Lsr took 0.23227906227111816s
Verifiability | Publishers check for Bio2RDF::Lsr took 0.3934156894683838s
Performance | Throughput check for Bio2RDF::Lsr took 11.016786813735962s
Verifiability | Contribs. check for Bio2RDF::Lsr took 0.6174290180206299s
Interlinking | sameAs chians check for Bio2RDF::Lsr took 0.2764270305633545s
Interlinking | skos check for Bio2RDF::Lsr took 0.6931138038635254s
Interlinking | skos check for Bio2RDF::Lsr took 0.367717981338501s
Timeliness | dataset update frequency check for Bio2RDF::Lsr took 0.25556135177612305s
Currency | Creation date check for Bio2RDF::Lsr took 0.34311938285827637s
Currency | Modification date check for Bio2RDF::Lsr took 0.2621598243713379s
Rep.Conc. | URIs length for Bio2RDF::Lsr took 110.18476963043213s
Interoperability | New vocabularies check for Bio2RDF::Lsr took 17.288859128952026s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Lsr took 0.4496185779571533s
Accuracy | Check Functional Property for Bio2RDF::Lsr took 0.25809764862060547s
Accuracy | Check Inverse Functional Property for Bio2RDF::Lsr took 0.2509572505950928s
Accuracy | Check Empty annotation labels for Bio2RDF::Lsr took 6.920629501342773s
Accuracy | Check White space in annotation for Bio2RDF::Lsr took 0.8880460262298584s
Accuracy | Check Datatype consistency for Bio2RDF::Lsr took 0.6689660549163818s
Consistency | Disjoint class check for Bio2RDF::Lsr took 0.4455752372741699s
Consistency | Check Misplaced properties for Bio2RDF::Lsr took 64.8830451965332s
Consistency | Misplaced classes for Bio2RDF::Lsr took 2.447441339492798s
Consistency | Check Ontology hijacking for Bio2RDF::Lsr took 6.289713382720947s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Lsr took 1.3640470504760742s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Lsr took 61.574137926101685s
Conciseness | Check Extensional conciseness for Bio2RDF::Lsr took 0.7276833057403564s
Conciseness | Check Intensional conciseness for Bio2RDF::Lsr took 0.46077704429626465s
Security | Sign check for Bio2RDF::Lsr took 0.2777974605560303s
Availability | Check URIs Dereferenciability for Bio2RDF::Lsr took 3.867349624633789s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 0.5780377388000488s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.020557165145874023s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 5.53131103515625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Lsr took 18.83044672012329s
Believability | Calculation of trust value for Bio2RDF::Lsr took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-lsr took 1037.2756133079529s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 0.474137544631958s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.9944136142730713s
Extra | Recovery of all triples for Bio2RDF::Mesh took 19.296894550323486s
Performance | Total latancy measurement for Bio2RDF::Mesh took 1.29298734664917s
Amount of data | Number of triples check for Bio2RDF::Mesh took 45.08509373664856s
Interoperability | New terms check for Bio2RDF::Mesh took 42.755000829696655s
Versatility | Languages check for Bio2RDF::Mesh took 60.287179946899414s
Interpretability | Number of blank nodes check for Bio2RDF::Mesh took 0.28383851051330566s
Security | Check HTTPS for Bio2RDF::Mesh took 0.14391350746154785s
Interpretability | RDF structures check for Bio2RDF::Mesh took 0.24513578414916992s
Versatility | Serialization formats check for Bio2RDF::Mesh took 0.2669241428375244s
Availability | RDF dump link check for Bio2RDF::Mesh took 2.9799909591674805s
License | MR license check for Bio2RDF::Mesh took 0.44407081604003906s
License | HR license check for Bio2RDF::Mesh took 60.2646164894104s
Amount of data | Number of property check for Bio2RDF::Mesh took 0.2907402515411377s
Understandability | Number of label check for Bio2RDF::Mesh took 8.681710481643677s
Understandability | URI regex check for Bio2RDF::Mesh took 0.6280655860900879s
Understandability | Vocabs check for Bio2RDF::Mesh took 0.25548267364501953s
Verifiability | Authors check for Bio2RDF::Mesh took 0.2787601947784424s
Verifiability | Publishers check for Bio2RDF::Mesh took 0.35768771171569824s
Performance | Throughput check for Bio2RDF::Mesh took 10.905367612838745s
Verifiability | Contribs. check for Bio2RDF::Mesh took 0.6392149925231934s
Interlinking | sameAs chians check for Bio2RDF::Mesh took 0.2920563220977783s
Interlinking | skos check for Bio2RDF::Mesh took 0.45201897621154785s
Interlinking | skos check for Bio2RDF::Mesh took 0.3683464527130127s
Timeliness | dataset update frequency check for Bio2RDF::Mesh took 0.26550960540771484s
Currency | Creation date check for Bio2RDF::Mesh took 0.35448551177978516s
Currency | Modification date check for Bio2RDF::Mesh took 0.26987528800964355s
Rep.Conc. | URIs length for Bio2RDF::Mesh took 106.38801145553589s
Interoperability | New vocabularies check for Bio2RDF::Mesh took 18.24540424346924s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mesh took 0.523637056350708s
Accuracy | Check Functional Property for Bio2RDF::Mesh took 0.23659896850585938s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mesh took 0.2748086452484131s
Accuracy | Check Empty annotation labels for Bio2RDF::Mesh took 7.5042724609375s
Accuracy | Check White space in annotation for Bio2RDF::Mesh took 0.9010288715362549s
Accuracy | Check Datatype consistency for Bio2RDF::Mesh took 0.6523985862731934s
Consistency | Disjoint class check for Bio2RDF::Mesh took 0.2785670757293701s
Consistency | Check Misplaced properties for Bio2RDF::Mesh took 65.51818799972534s
Consistency | Misplaced classes for Bio2RDF::Mesh took 2.431264638900757s
Consistency | Check Ontology hijacking for Bio2RDF::Mesh took 6.0657055377960205s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mesh took 1.3001525402069092s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mesh took 61.64957880973816s
Conciseness | Check Extensional conciseness for Bio2RDF::Mesh took 0.7875401973724365s
Conciseness | Check Intensional conciseness for Bio2RDF::Mesh took 0.42947912216186523s
Security | Sign check for Bio2RDF::Mesh took 0.30044126510620117s
Availability | Check URIs Dereferenciability for Bio2RDF::Mesh took 3.8567423820495605s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 1.4745252132415771s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.021186351776123047s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 7.2479248046875e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mesh took 17.598807096481323s
Believability | Calculation of trust value for Bio2RDF::Mesh took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-mesh took 1039.4423546791077s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 0.5317997932434082s
Availability | VoID file availability check for Bio2RDF::Mgi took 1.0390944480895996s
Extra | Recovery of all triples for Bio2RDF::Mgi took 18.37312388420105s
Performance | Total latancy measurement for Bio2RDF::Mgi took 1.426133394241333s
Amount of data | Number of triples check for Bio2RDF::Mgi took 45.617810010910034s
Interoperability | New terms check for Bio2RDF::Mgi took 40.86565613746643s
Versatility | Languages check for Bio2RDF::Mgi took 60.252485275268555s
Interpretability | Number of blank nodes check for Bio2RDF::Mgi took 0.2682831287384033s
Security | Check HTTPS for Bio2RDF::Mgi took 0.15953421592712402s
Interpretability | RDF structures check for Bio2RDF::Mgi took 0.24726033210754395s
Versatility | Serialization formats check for Bio2RDF::Mgi took 0.26044774055480957s
Availability | RDF dump link check for Bio2RDF::Mgi took 2.9940805435180664s
License | MR license check for Bio2RDF::Mgi took 0.3912086486816406s
License | HR license check for Bio2RDF::Mgi took 60.249542474746704s
Amount of data | Number of property check for Bio2RDF::Mgi took 0.22898030281066895s
Understandability | Number of label check for Bio2RDF::Mgi took 9.401188135147095s
Understandability | URI regex check for Bio2RDF::Mgi took 0.5903306007385254s
Understandability | Vocabs check for Bio2RDF::Mgi took 0.2770726680755615s
Verifiability | Authors check for Bio2RDF::Mgi took 0.30515503883361816s
Verifiability | Publishers check for Bio2RDF::Mgi took 0.45234203338623047s
Performance | Throughput check for Bio2RDF::Mgi took 11.295737266540527s
Verifiability | Contribs. check for Bio2RDF::Mgi took 0.6391031742095947s
Interlinking | sameAs chians check for Bio2RDF::Mgi took 0.2942929267883301s
Interlinking | skos check for Bio2RDF::Mgi took 0.5858023166656494s
Interlinking | skos check for Bio2RDF::Mgi took 0.32333946228027344s
Timeliness | dataset update frequency check for Bio2RDF::Mgi took 0.2681899070739746s
Currency | Creation date check for Bio2RDF::Mgi took 0.3831782341003418s
Currency | Modification date check for Bio2RDF::Mgi took 0.24788618087768555s
Rep.Conc. | URIs length for Bio2RDF::Mgi took 107.0950198173523s
Interoperability | New vocabularies check for Bio2RDF::Mgi took 19.552621841430664s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mgi took 0.451763391494751s
Accuracy | Check Functional Property for Bio2RDF::Mgi took 0.2534065246582031s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mgi took 0.27399516105651855s
Accuracy | Check Empty annotation labels for Bio2RDF::Mgi took 7.054522275924683s
Accuracy | Check White space in annotation for Bio2RDF::Mgi took 0.8936619758605957s
Accuracy | Check Datatype consistency for Bio2RDF::Mgi took 0.699404239654541s
Consistency | Disjoint class check for Bio2RDF::Mgi took 0.41676855087280273s
Consistency | Check Misplaced properties for Bio2RDF::Mgi took 65.10569262504578s
Consistency | Misplaced classes for Bio2RDF::Mgi took 2.4055309295654297s
Consistency | Check Ontology hijacking for Bio2RDF::Mgi took 5.727104425430298s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mgi took 1.3086414337158203s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mgi took 61.628249168395996s
Conciseness | Check Extensional conciseness for Bio2RDF::Mgi took 0.7657904624938965s
Conciseness | Check Intensional conciseness for Bio2RDF::Mgi took 0.5144524574279785s
Security | Sign check for Bio2RDF::Mgi took 0.2565653324127197s
Availability | Check URIs Dereferenciability for Bio2RDF::Mgi took 3.8153371810913086s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 1.6898396015167236s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.020269393920898438s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 9.202957153320312e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mgi took 18.817850589752197s
Believability | Calculation of trust value for Bio2RDF::Mgi took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-mgi took 1051.044183731079s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 0.4775974750518799s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 1.0627262592315674s
Extra | Recovery of all triples for Bio2RDF::Ncbigene took 18.058618545532227s
Performance | Total latancy measurement for Bio2RDF::Ncbigene took 1.2882280349731445s
Amount of data | Number of triples check for Bio2RDF::Ncbigene took 45.262993812561035s
Interoperability | New terms check for Bio2RDF::Ncbigene took 40.85092902183533s
Versatility | Languages check for Bio2RDF::Ncbigene took 60.26591396331787s
Interpretability | Number of blank nodes check for Bio2RDF::Ncbigene took 0.25755810737609863s
Security | Check HTTPS for Bio2RDF::Ncbigene took 0.1414930820465088s
Interpretability | RDF structures check for Bio2RDF::Ncbigene took 0.40622711181640625s
Versatility | Serialization formats check for Bio2RDF::Ncbigene took 0.2747659683227539s
Availability | RDF dump link check for Bio2RDF::Ncbigene took 3.050530195236206s
License | MR license check for Bio2RDF::Ncbigene took 0.4674832820892334s
License | HR license check for Bio2RDF::Ncbigene took 60.26337146759033s
Amount of data | Number of property check for Bio2RDF::Ncbigene took 0.27016401290893555s
Understandability | Number of label check for Bio2RDF::Ncbigene took 9.397394895553589s
Understandability | URI regex check for Bio2RDF::Ncbigene took 0.5940556526184082s
Understandability | Vocabs check for Bio2RDF::Ncbigene took 0.26403331756591797s
Verifiability | Authors check for Bio2RDF::Ncbigene took 0.2456355094909668s
Verifiability | Publishers check for Bio2RDF::Ncbigene took 0.4774904251098633s
Performance | Throughput check for Bio2RDF::Ncbigene took 11.02329421043396s
Verifiability | Contribs. check for Bio2RDF::Ncbigene took 0.6565940380096436s
Interlinking | sameAs chians check for Bio2RDF::Ncbigene took 0.2803785800933838s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.8472907543182373s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.39188480377197266s
Timeliness | dataset update frequency check for Bio2RDF::Ncbigene took 0.28261613845825195s
Currency | Creation date check for Bio2RDF::Ncbigene took 0.4282963275909424s
Currency | Modification date check for Bio2RDF::Ncbigene took 0.26654672622680664s
Rep.Conc. | URIs length for Bio2RDF::Ncbigene took 107.6057379245758s
Interoperability | New vocabularies check for Bio2RDF::Ncbigene took 18.64789080619812s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ncbigene took 0.5061702728271484s
Accuracy | Check Functional Property for Bio2RDF::Ncbigene took 0.31593918800354004s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ncbigene took 0.28655457496643066s
Accuracy | Check Empty annotation labels for Bio2RDF::Ncbigene took 6.543952703475952s
Accuracy | Check White space in annotation for Bio2RDF::Ncbigene took 0.8869013786315918s
Accuracy | Check Datatype consistency for Bio2RDF::Ncbigene took 0.64825439453125s
Consistency | Disjoint class check for Bio2RDF::Ncbigene took 0.3875448703765869s
Consistency | Check Misplaced properties for Bio2RDF::Ncbigene took 65.15795636177063s
Consistency | Misplaced classes for Bio2RDF::Ncbigene took 2.443603992462158s
Consistency | Check Ontology hijacking for Bio2RDF::Ncbigene took 6.456317186355591s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ncbigene took 1.3590545654296875s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ncbigene took 61.58235502243042s
Conciseness | Check Extensional conciseness for Bio2RDF::Ncbigene took 0.7372946739196777s
Conciseness | Check Intensional conciseness for Bio2RDF::Ncbigene took 0.42818760871887207s
Security | Sign check for Bio2RDF::Ncbigene took 0.2485032081604004s
Availability | Check URIs Dereferenciability for Bio2RDF::Ncbigene took 3.584409475326538s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 0.6747004985809326s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.02006816864013672s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0006852149963378906s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.00012946128845214844s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ncbigene took 18.24113178253174s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 1.3589859008789062e-05s
INFO | --- Analysis for bio2rdf-ncbigene took 1044.818783044815s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 0.48052501678466797s
Availability | VoID file availability check for Bio2RDF::Ndc took 1.0706913471221924s
Extra | Recovery of all triples for Bio2RDF::Ndc took 19.00511860847473s
Performance | Total latancy measurement for Bio2RDF::Ndc took 1.364483118057251s
Amount of data | Number of triples check for Bio2RDF::Ndc took 45.697500705718994s
Interoperability | New terms check for Bio2RDF::Ndc took 41.02344012260437s
Versatility | Languages check for Bio2RDF::Ndc took 60.24196147918701s
Interpretability | Number of blank nodes check for Bio2RDF::Ndc took 0.2868385314941406s
Security | Check HTTPS for Bio2RDF::Ndc took 0.18195462226867676s
Interpretability | RDF structures check for Bio2RDF::Ndc took 0.24779272079467773s
Versatility | Serialization formats check for Bio2RDF::Ndc took 0.2943704128265381s
Availability | RDF dump link check for Bio2RDF::Ndc took 2.705174446105957s
License | MR license check for Bio2RDF::Ndc took 0.30164170265197754s
License | HR license check for Bio2RDF::Ndc took 60.26589107513428s
Amount of data | Number of property check for Bio2RDF::Ndc took 0.27333569526672363s
Understandability | Number of label check for Bio2RDF::Ndc took 9.484450817108154s
Understandability | URI regex check for Bio2RDF::Ndc took 0.6054325103759766s
Understandability | Vocabs check for Bio2RDF::Ndc took 0.27982211112976074s
Verifiability | Authors check for Bio2RDF::Ndc took 0.24510908126831055s
Verifiability | Publishers check for Bio2RDF::Ndc took 0.3623840808868408s
Performance | Throughput check for Bio2RDF::Ndc took 10.735749244689941s
Verifiability | Contribs. check for Bio2RDF::Ndc took 0.7963500022888184s
Interlinking | sameAs chians check for Bio2RDF::Ndc took 0.28863072395324707s
Interlinking | skos check for Bio2RDF::Ndc took 0.5619299411773682s
Interlinking | skos check for Bio2RDF::Ndc took 0.34249305725097656s
Timeliness | dataset update frequency check for Bio2RDF::Ndc took 0.2518436908721924s
Currency | Creation date check for Bio2RDF::Ndc took 0.37579870223999023s
Currency | Modification date check for Bio2RDF::Ndc took 0.26694703102111816s
Rep.Conc. | URIs length for Bio2RDF::Ndc took 109.0068576335907s
Interoperability | New vocabularies check for Bio2RDF::Ndc took 17.941284656524658s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ndc took 0.5166115760803223s
Accuracy | Check Functional Property for Bio2RDF::Ndc took 0.289395809173584s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ndc took 0.22681260108947754s
Accuracy | Check Empty annotation labels for Bio2RDF::Ndc took 6.437786102294922s
Accuracy | Check White space in annotation for Bio2RDF::Ndc took 0.893939733505249s
Accuracy | Check Datatype consistency for Bio2RDF::Ndc took 0.7029800415039062s
Consistency | Disjoint class check for Bio2RDF::Ndc took 0.3265674114227295s
Consistency | Check Misplaced properties for Bio2RDF::Ndc took 65.02785563468933s
Consistency | Misplaced classes for Bio2RDF::Ndc took 2.4133388996124268s
Consistency | Check Ontology hijacking for Bio2RDF::Ndc took 5.985493183135986s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ndc took 1.3086581230163574s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ndc took 61.60060977935791s
Conciseness | Check Extensional conciseness for Bio2RDF::Ndc took 0.7542569637298584s
Conciseness | Check Intensional conciseness for Bio2RDF::Ndc took 0.4443655014038086s
Security | Sign check for Bio2RDF::Ndc took 0.2781641483306885s
Availability | Check URIs Dereferenciability for Bio2RDF::Ndc took 4.4467809200286865s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 24.874995470046997s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.02082967758178711s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 4.935264587402344e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ndc took 16.386574506759644s
Believability | Calculation of trust value for Bio2RDF::Ndc took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-ndc took 1075.1364583969116s
Availability | SPARQL endpoint availability check for Bio2RDF::NetPath took 0.1411283016204834s
Availability | VoID file availability check for Bio2RDF::NetPath took 0.00016832351684570312s
Completeness | Calculation of interlinking completeness for Bio2RDF::NetPath took 0.41464877128601074s
Reputation | Calculation of the PageRank for Bio2RDF::NetPath took 0.021318912506103516s
Interlinking | Calculation of Degree of Connection for Bio2RDF::NetPath took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::NetPath took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::NetPath took 3.337860107421875e-05s
Believability | Calculation of trust value for Bio2RDF::NetPath took 1.4066696166992188e-05s
INFO | --- Analysis for bio2rdf-netpath took 151.88290095329285s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 0.1883533000946045s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.0002033710479736328s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.3178555965423584s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.022418737411499023s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 3.4332275390625e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-nextprot took 3.3319690227508545s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 0.514146089553833s
Availability | VoID file availability check for Bio2RDF::Omim took 1.0974934101104736s
Extra | Recovery of all triples for Bio2RDF::Omim took 19.588385105133057s
Performance | Total latancy measurement for Bio2RDF::Omim took 1.3014984130859375s
Amount of data | Number of triples check for Bio2RDF::Omim took 44.99370336532593s
Interoperability | New terms check for Bio2RDF::Omim took 42.77112936973572s
Versatility | Languages check for Bio2RDF::Omim took 60.24003481864929s
Interpretability | Number of blank nodes check for Bio2RDF::Omim took 0.28302526473999023s
Security | Check HTTPS for Bio2RDF::Omim took 0.19572162628173828s
Interpretability | RDF structures check for Bio2RDF::Omim took 0.2533750534057617s
Versatility | Serialization formats check for Bio2RDF::Omim took 0.276623010635376s
Availability | RDF dump link check for Bio2RDF::Omim took 2.7851107120513916s
License | MR license check for Bio2RDF::Omim took 0.3426797389984131s
License | HR license check for Bio2RDF::Omim took 60.2635064125061s
Amount of data | Number of property check for Bio2RDF::Omim took 0.2521097660064697s
Understandability | Number of label check for Bio2RDF::Omim took 9.814534902572632s
Understandability | URI regex check for Bio2RDF::Omim took 0.6606736183166504s
Understandability | Vocabs check for Bio2RDF::Omim took 0.28124523162841797s
Verifiability | Authors check for Bio2RDF::Omim took 0.2396564483642578s
Verifiability | Publishers check for Bio2RDF::Omim took 0.38219761848449707s
Performance | Throughput check for Bio2RDF::Omim took 11.159235000610352s
Verifiability | Contribs. check for Bio2RDF::Omim took 0.7646639347076416s
Interlinking | sameAs chians check for Bio2RDF::Omim took 0.28095269203186035s
Interlinking | skos check for Bio2RDF::Omim took 0.7099807262420654s
Interlinking | skos check for Bio2RDF::Omim took 0.35189175605773926s
Timeliness | dataset update frequency check for Bio2RDF::Omim took 0.28634166717529297s
Currency | Creation date check for Bio2RDF::Omim took 0.40958094596862793s
Currency | Modification date check for Bio2RDF::Omim took 0.24585843086242676s
Rep.Conc. | URIs length for Bio2RDF::Omim took 110.09281587600708s
Interoperability | New vocabularies check for Bio2RDF::Omim took 19.435540914535522s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Omim took 0.44057297706604004s
Accuracy | Check Functional Property for Bio2RDF::Omim took 0.27216458320617676s
Accuracy | Check Inverse Functional Property for Bio2RDF::Omim took 0.2539525032043457s
Accuracy | Check Empty annotation labels for Bio2RDF::Omim took 6.977221250534058s
Accuracy | Check White space in annotation for Bio2RDF::Omim took 0.8990085124969482s
Accuracy | Check Datatype consistency for Bio2RDF::Omim took 0.6664309501647949s
Consistency | Disjoint class check for Bio2RDF::Omim took 0.40087008476257324s
Consistency | Check Misplaced properties for Bio2RDF::Omim took 65.06323742866516s
Consistency | Misplaced classes for Bio2RDF::Omim took 2.4331905841827393s
Consistency | Check Ontology hijacking for Bio2RDF::Omim took 6.616050720214844s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Omim took 1.3495702743530273s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Omim took 61.62476301193237s
Conciseness | Check Extensional conciseness for Bio2RDF::Omim took 0.7251853942871094s
Conciseness | Check Intensional conciseness for Bio2RDF::Omim took 0.47056031227111816s
Security | Sign check for Bio2RDF::Omim took 0.25982046127319336s
Availability | Check URIs Dereferenciability for Bio2RDF::Omim took 3.6408956050872803s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 0.4865598678588867s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.020762205123901367s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.00012683868408203125s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Omim took 17.38504433631897s
Believability | Calculation of trust value for Bio2RDF::Omim took 1.1444091796875e-05s
INFO | --- Analysis for bio2rdf-omim took 1041.9616639614105s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 0.00011658668518066406s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.0008618831634521484s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.31087327003479004s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.02069854736328125s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 3.62396240234375e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-omim-resources took 4.657911539077759s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 0.5039045810699463s
Availability | VoID file availability check for Bio2RDF::Orphanet took 1.0375440120697021s
Extra | Recovery of all triples for Bio2RDF::Orphanet took 19.949666261672974s
Performance | Total latancy measurement for Bio2RDF::Orphanet took 1.31632399559021s
Amount of data | Number of triples check for Bio2RDF::Orphanet took 45.33849859237671s
Interoperability | New terms check for Bio2RDF::Orphanet took 41.15149521827698s
Versatility | Languages check for Bio2RDF::Orphanet took 60.25470161437988s
Interpretability | Number of blank nodes check for Bio2RDF::Orphanet took 0.25014519691467285s
Security | Check HTTPS for Bio2RDF::Orphanet took 0.16949868202209473s
Interpretability | RDF structures check for Bio2RDF::Orphanet took 0.3443634510040283s
Versatility | Serialization formats check for Bio2RDF::Orphanet took 0.27902698516845703s
Availability | RDF dump link check for Bio2RDF::Orphanet took 3.0755531787872314s
License | MR license check for Bio2RDF::Orphanet took 0.4148383140563965s
License | HR license check for Bio2RDF::Orphanet took 60.27051281929016s
Amount of data | Number of property check for Bio2RDF::Orphanet took 0.27840471267700195s
Understandability | Number of label check for Bio2RDF::Orphanet took 9.376944303512573s
Understandability | URI regex check for Bio2RDF::Orphanet took 0.592402458190918s
Understandability | Vocabs check for Bio2RDF::Orphanet took 0.26657700538635254s
Verifiability | Authors check for Bio2RDF::Orphanet took 0.24783539772033691s
Verifiability | Publishers check for Bio2RDF::Orphanet took 0.49594759941101074s
Performance | Throughput check for Bio2RDF::Orphanet took 10.802219867706299s
Verifiability | Contribs. check for Bio2RDF::Orphanet took 0.6608750820159912s
Interlinking | sameAs chians check for Bio2RDF::Orphanet took 0.33115553855895996s
Interlinking | skos check for Bio2RDF::Orphanet took 0.8638014793395996s
Interlinking | skos check for Bio2RDF::Orphanet took 0.36699604988098145s
Timeliness | dataset update frequency check for Bio2RDF::Orphanet took 0.2599353790283203s
Currency | Creation date check for Bio2RDF::Orphanet took 0.3797941207885742s
Currency | Modification date check for Bio2RDF::Orphanet took 0.27845048904418945s
Rep.Conc. | URIs length for Bio2RDF::Orphanet took 106.37673854827881s
Interoperability | New vocabularies check for Bio2RDF::Orphanet took 15.626378536224365s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Orphanet took 0.4122276306152344s
Accuracy | Check Functional Property for Bio2RDF::Orphanet took 0.2957606315612793s
Accuracy | Check Inverse Functional Property for Bio2RDF::Orphanet took 0.26653480529785156s
Accuracy | Check Empty annotation labels for Bio2RDF::Orphanet took 6.4821343421936035s
Accuracy | Check White space in annotation for Bio2RDF::Orphanet took 0.8927624225616455s
Accuracy | Check Datatype consistency for Bio2RDF::Orphanet took 0.6920483112335205s
Consistency | Disjoint class check for Bio2RDF::Orphanet took 0.47304677963256836s
Consistency | Check Misplaced properties for Bio2RDF::Orphanet took 64.8308036327362s
Consistency | Misplaced classes for Bio2RDF::Orphanet took 2.411393880844116s
Consistency | Check Ontology hijacking for Bio2RDF::Orphanet took 6.56476354598999s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Orphanet took 1.3395652770996094s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Orphanet took 61.67964220046997s
Conciseness | Check Extensional conciseness for Bio2RDF::Orphanet took 0.7539114952087402s
Conciseness | Check Intensional conciseness for Bio2RDF::Orphanet took 0.39801836013793945s
Security | Sign check for Bio2RDF::Orphanet took 0.28183436393737793s
Availability | Check URIs Dereferenciability for Bio2RDF::Orphanet took 3.8485159873962402s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 1.015181303024292s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.02098393440246582s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 0.00010275840759277344s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Orphanet took 15.38681697845459s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-orphanet took 1043.1351878643036s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 0.14015722274780273s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.010512113571166992s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 1.08013916015625s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.020676612854003906s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0006804466247558594s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 2.956390380859375e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-pathwaycommons took 10.611993074417114s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 1.3117427825927734s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 1.0514144897460938s
Extra | Recovery of all triples for Bio2RDF::Pharmgkb took 18.175400972366333s
Performance | Total latancy measurement for Bio2RDF::Pharmgkb took 1.2633764743804932s
Amount of data | Number of triples check for Bio2RDF::Pharmgkb took 44.899559020996094s
Interoperability | New terms check for Bio2RDF::Pharmgkb took 40.289642095565796s
Versatility | Languages check for Bio2RDF::Pharmgkb took 60.309510707855225s
Interpretability | Number of blank nodes check for Bio2RDF::Pharmgkb took 0.2692756652832031s
Security | Check HTTPS for Bio2RDF::Pharmgkb took 0.15927338600158691s
Interpretability | RDF structures check for Bio2RDF::Pharmgkb took 0.2783823013305664s
Versatility | Serialization formats check for Bio2RDF::Pharmgkb took 0.25030088424682617s
Availability | RDF dump link check for Bio2RDF::Pharmgkb took 3.0167298316955566s
License | MR license check for Bio2RDF::Pharmgkb took 0.27185964584350586s
License | HR license check for Bio2RDF::Pharmgkb took 60.229809522628784s
Amount of data | Number of property check for Bio2RDF::Pharmgkb took 0.2654545307159424s
Understandability | Number of label check for Bio2RDF::Pharmgkb took 9.0951247215271s
Understandability | URI regex check for Bio2RDF::Pharmgkb took 0.5881109237670898s
Understandability | Vocabs check for Bio2RDF::Pharmgkb took 0.2436509132385254s
Verifiability | Authors check for Bio2RDF::Pharmgkb took 0.2951009273529053s
Verifiability | Publishers check for Bio2RDF::Pharmgkb took 0.3474583625793457s
Performance | Throughput check for Bio2RDF::Pharmgkb took 11.041202545166016s
Verifiability | Contribs. check for Bio2RDF::Pharmgkb took 0.6556668281555176s
Interlinking | sameAs chians check for Bio2RDF::Pharmgkb took 0.28592801094055176s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.6111979484558105s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.3951129913330078s
Timeliness | dataset update frequency check for Bio2RDF::Pharmgkb took 0.27843260765075684s
Currency | Creation date check for Bio2RDF::Pharmgkb took 0.364743709564209s
Currency | Modification date check for Bio2RDF::Pharmgkb took 0.24634432792663574s
Rep.Conc. | URIs length for Bio2RDF::Pharmgkb took 107.15629005432129s
Interoperability | New vocabularies check for Bio2RDF::Pharmgkb took 16.702858924865723s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pharmgkb took 0.4551982879638672s
Accuracy | Check Functional Property for Bio2RDF::Pharmgkb took 0.25955677032470703s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pharmgkb took 0.26569032669067383s
Accuracy | Check Empty annotation labels for Bio2RDF::Pharmgkb took 6.813776254653931s
Accuracy | Check White space in annotation for Bio2RDF::Pharmgkb took 0.8908624649047852s
Accuracy | Check Datatype consistency for Bio2RDF::Pharmgkb took 0.6579599380493164s
Consistency | Disjoint class check for Bio2RDF::Pharmgkb took 0.4185817241668701s
Consistency | Check Misplaced properties for Bio2RDF::Pharmgkb took 64.73114466667175s
Consistency | Misplaced classes for Bio2RDF::Pharmgkb took 2.4887073040008545s
Consistency | Check Ontology hijacking for Bio2RDF::Pharmgkb took 6.173275470733643s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pharmgkb took 1.305511713027954s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pharmgkb took 61.62086892127991s
Conciseness | Check Extensional conciseness for Bio2RDF::Pharmgkb took 0.74649977684021s
Conciseness | Check Intensional conciseness for Bio2RDF::Pharmgkb took 0.4826061725616455s
Security | Sign check for Bio2RDF::Pharmgkb took 0.269489049911499s
Availability | Check URIs Dereferenciability for Bio2RDF::Pharmgkb took 3.71889591217041s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 1.0961503982543945s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.020663022994995117s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 7.82012939453125e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pharmgkb took 23.306951761245728s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-pharmgkb took 1045.1020040512085s
Availability | SPARQL endpoint availability check for Bio2RDF::PharmGKB::BioPAX took 0.1390247344970703s
Availability | VoID file availability check for Bio2RDF::PharmGKB::BioPAX took 0.0009131431579589844s
Completeness | Calculation of interlinking completeness for Bio2RDF::PharmGKB::BioPAX took 0.9646501541137695s
Reputation | Calculation of the PageRank for Bio2RDF::PharmGKB::BioPAX took 0.02018451690673828s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PharmGKB::BioPAX took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::PharmGKB::BioPAX took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PharmGKB::BioPAX took 3.0279159545898438e-05s
Believability | Calculation of trust value for Bio2RDF::PharmGKB::BioPAX took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-pharmgkb-biopax took 7.687720775604248s
Availability | SPARQL endpoint availability check for Bio2RDF::PID took 0.13425350189208984s
Availability | VoID file availability check for Bio2RDF::PID took 0.0002231597900390625s
Completeness | Calculation of interlinking completeness for Bio2RDF::PID took 0.3033914566040039s
Reputation | Calculation of the PageRank for Bio2RDF::PID took 0.02139449119567871s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PID took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::PID took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PID took 3.147125244140625e-05s
Believability | Calculation of trust value for Bio2RDF::PID took 1.430511474609375e-05s
INFO | --- Analysis for bio2rdf-pid took 2.315450668334961s
Availability | SPARQL endpoint availability check for Bio2RDF::PubChem took 0.14205336570739746s
Availability | VoID file availability check for Bio2RDF::PubChem took 0.00020313262939453125s
Completeness | Calculation of interlinking completeness for Bio2RDF::PubChem took 0.4800443649291992s
Reputation | Calculation of the PageRank for Bio2RDF::PubChem took 0.020751953125s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PubChem took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::PubChem took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PubChem took 3.170967102050781e-05s
Believability | Calculation of trust value for Bio2RDF::PubChem took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-pubchem-2 took 3.27060604095459s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 0.4952704906463623s
Availability | VoID file availability check for Bio2RDF::Pubmed took 1.0371150970458984s
Extra | Recovery of all triples for Bio2RDF::Pubmed took 18.385794639587402s
Performance | Total latancy measurement for Bio2RDF::Pubmed took 1.3052680492401123s
Amount of data | Number of triples check for Bio2RDF::Pubmed took 45.13558769226074s
Interoperability | New terms check for Bio2RDF::Pubmed took 42.40353465080261s
Versatility | Languages check for Bio2RDF::Pubmed took 60.29930591583252s
Interpretability | Number of blank nodes check for Bio2RDF::Pubmed took 0.2704181671142578s
Security | Check HTTPS for Bio2RDF::Pubmed took 0.1744401454925537s
Interpretability | RDF structures check for Bio2RDF::Pubmed took 0.23257923126220703s
Versatility | Serialization formats check for Bio2RDF::Pubmed took 0.229630708694458s
Availability | RDF dump link check for Bio2RDF::Pubmed took 2.8246545791625977s
License | MR license check for Bio2RDF::Pubmed took 0.39354705810546875s
License | HR license check for Bio2RDF::Pubmed took 60.29982542991638s
Amount of data | Number of property check for Bio2RDF::Pubmed took 0.2506098747253418s
Understandability | Number of label check for Bio2RDF::Pubmed took 9.268432140350342s
Understandability | URI regex check for Bio2RDF::Pubmed took 0.6779885292053223s
Understandability | Vocabs check for Bio2RDF::Pubmed took 0.23067426681518555s
Verifiability | Authors check for Bio2RDF::Pubmed took 0.28881406784057617s
Verifiability | Publishers check for Bio2RDF::Pubmed took 0.3558833599090576s
Performance | Throughput check for Bio2RDF::Pubmed took 10.717839002609253s
Verifiability | Contribs. check for Bio2RDF::Pubmed took 0.6201796531677246s
Interlinking | sameAs chians check for Bio2RDF::Pubmed took 0.2815976142883301s
Interlinking | skos check for Bio2RDF::Pubmed took 0.7421412467956543s
Interlinking | skos check for Bio2RDF::Pubmed took 0.4558086395263672s
Timeliness | dataset update frequency check for Bio2RDF::Pubmed took 0.25507688522338867s
Currency | Creation date check for Bio2RDF::Pubmed took 0.3934593200683594s
Currency | Modification date check for Bio2RDF::Pubmed took 0.27254319190979004s
Rep.Conc. | URIs length for Bio2RDF::Pubmed took 106.57516956329346s
Interoperability | New vocabularies check for Bio2RDF::Pubmed took 17.998101472854614s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pubmed took 0.47881436347961426s
Accuracy | Check Functional Property for Bio2RDF::Pubmed took 0.254580020904541s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pubmed took 0.24498987197875977s
Accuracy | Check Empty annotation labels for Bio2RDF::Pubmed took 6.627385854721069s
Accuracy | Check White space in annotation for Bio2RDF::Pubmed took 0.8897414207458496s
Accuracy | Check Datatype consistency for Bio2RDF::Pubmed took 0.6595563888549805s
Consistency | Disjoint class check for Bio2RDF::Pubmed took 0.5341169834136963s
Consistency | Check Misplaced properties for Bio2RDF::Pubmed took 65.03726410865784s
Consistency | Misplaced classes for Bio2RDF::Pubmed took 2.3676810264587402s
Consistency | Check Ontology hijacking for Bio2RDF::Pubmed took 6.584655523300171s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pubmed took 1.3013005256652832s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pubmed took 61.657514333724976s
Conciseness | Check Extensional conciseness for Bio2RDF::Pubmed took 0.7341952323913574s
Conciseness | Check Intensional conciseness for Bio2RDF::Pubmed took 0.5214757919311523s
Security | Sign check for Bio2RDF::Pubmed took 0.31624507904052734s
Availability | Check URIs Dereferenciability for Bio2RDF::Pubmed took 3.7140400409698486s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 0.614539623260498s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.021173954010009766s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.00013971328735351562s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pubmed took 16.272536039352417s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 1.3828277587890625e-05s
INFO | --- Analysis for bio2rdf-pubmed took 1030.485880613327s
Availability | SPARQL endpoint availability check for Bio2RDF::Reactome took 0.13789892196655273s
Availability | VoID file availability check for Bio2RDF::Reactome took 0.00860738754272461s
Completeness | Calculation of interlinking completeness for Bio2RDF::Reactome took 0.4759206771850586s
Reputation | Calculation of the PageRank for Bio2RDF::Reactome took 0.020057201385498047s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Reactome took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Reactome took 0.0006880760192871094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Reactome took 6.771087646484375e-05s
Believability | Calculation of trust value for Bio2RDF::Reactome took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-reactome took 8.655268430709839s
Availability | SPARQL endpoint availability check for Bio2RDF::Rhea took 0.13917160034179688s
Availability | VoID file availability check for Bio2RDF::Rhea took 0.0002086162567138672s
Completeness | Calculation of interlinking completeness for Bio2RDF::Rhea took 0.30098748207092285s
Reputation | Calculation of the PageRank for Bio2RDF::Rhea took 0.021013498306274414s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Rhea took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Rhea took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Rhea took 5.555152893066406e-05s
Believability | Calculation of trust value for Bio2RDF::Rhea took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-rhea took 4.6983771324157715s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 0.1391458511352539s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0075795650482177734s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 1.0214149951934814s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.02078104019165039s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 7.677078247070312e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-sabiork took 10.54534101486206s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 0.48697757720947266s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.98958420753479s
Extra | Recovery of all triples for Bio2RDF::Sgd took 18.925952672958374s
Performance | Total latancy measurement for Bio2RDF::Sgd took 1.315629005432129s
Amount of data | Number of triples check for Bio2RDF::Sgd took 44.88753581047058s
Interoperability | New terms check for Bio2RDF::Sgd took 40.642937660217285s
Versatility | Languages check for Bio2RDF::Sgd took 60.27792191505432s
Interpretability | Number of blank nodes check for Bio2RDF::Sgd took 0.28710031509399414s
Security | Check HTTPS for Bio2RDF::Sgd took 0.17232108116149902s
Interpretability | RDF structures check for Bio2RDF::Sgd took 0.2676408290863037s
Versatility | Serialization formats check for Bio2RDF::Sgd took 0.24880218505859375s
Availability | RDF dump link check for Bio2RDF::Sgd took 3.0591018199920654s
License | MR license check for Bio2RDF::Sgd took 0.24900078773498535s
License | HR license check for Bio2RDF::Sgd took 60.29810976982117s
Amount of data | Number of property check for Bio2RDF::Sgd took 0.2698397636413574s
Understandability | Number of label check for Bio2RDF::Sgd took 9.162344932556152s
Understandability | URI regex check for Bio2RDF::Sgd took 0.5619657039642334s
Understandability | Vocabs check for Bio2RDF::Sgd took 0.2868928909301758s
Verifiability | Authors check for Bio2RDF::Sgd took 0.28992223739624023s
Verifiability | Publishers check for Bio2RDF::Sgd took 0.3427159786224365s
Performance | Throughput check for Bio2RDF::Sgd took 10.592803478240967s
Verifiability | Contribs. check for Bio2RDF::Sgd took 0.6088035106658936s
Interlinking | sameAs chians check for Bio2RDF::Sgd took 0.2750563621520996s
Interlinking | skos check for Bio2RDF::Sgd took 0.3684711456298828s
Interlinking | skos check for Bio2RDF::Sgd took 0.3586733341217041s
Timeliness | dataset update frequency check for Bio2RDF::Sgd took 0.2734360694885254s
Currency | Creation date check for Bio2RDF::Sgd took 0.3511514663696289s
Currency | Modification date check for Bio2RDF::Sgd took 0.2948770523071289s
Rep.Conc. | URIs length for Bio2RDF::Sgd took 106.82250928878784s
Interoperability | New vocabularies check for Bio2RDF::Sgd took 17.592532873153687s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sgd took 0.45063161849975586s
Accuracy | Check Functional Property for Bio2RDF::Sgd took 0.24333834648132324s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sgd took 0.2834751605987549s
Accuracy | Check Empty annotation labels for Bio2RDF::Sgd took 6.19982385635376s
Accuracy | Check White space in annotation for Bio2RDF::Sgd took 0.8890078067779541s
Accuracy | Check Datatype consistency for Bio2RDF::Sgd took 0.7003719806671143s
Consistency | Disjoint class check for Bio2RDF::Sgd took 0.2557361125946045s
Consistency | Check Misplaced properties for Bio2RDF::Sgd took 64.46832418441772s
Consistency | Misplaced classes for Bio2RDF::Sgd took 2.3859753608703613s
Consistency | Check Ontology hijacking for Bio2RDF::Sgd took 6.546241998672485s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sgd took 1.3523588180541992s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sgd took 61.546236991882324s
Conciseness | Check Extensional conciseness for Bio2RDF::Sgd took 0.726229190826416s
Conciseness | Check Intensional conciseness for Bio2RDF::Sgd took 0.5259425640106201s
Security | Sign check for Bio2RDF::Sgd took 0.2892279624938965s
Availability | Check URIs Dereferenciability for Bio2RDF::Sgd took 3.77148175239563s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 0.7266619205474854s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.020652294158935547s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00010776519775390625s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sgd took 18.1674325466156s
Believability | Calculation of trust value for Bio2RDF::Sgd took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-sgd took 1036.9556550979614s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 8.559226989746094e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.0008726119995117188s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 0.3812520503997803s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.020850181579589844s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 4.00543212890625e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 1.0728836059570312e-05s
INFO | --- Analysis for bio2rdf-sgd-resources took 2.356762170791626s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 1.3380126953125s
Availability | VoID file availability check for Bio2RDF::Sider took 1.132540225982666s
Extra | Recovery of all triples for Bio2RDF::Sider took 18.212153911590576s
Performance | Total latancy measurement for Bio2RDF::Sider took 1.2552392482757568s
Amount of data | Number of triples check for Bio2RDF::Sider took 44.96192741394043s
Interoperability | New terms check for Bio2RDF::Sider took 40.282604694366455s
Versatility | Languages check for Bio2RDF::Sider took 60.25422668457031s
Interpretability | Number of blank nodes check for Bio2RDF::Sider took 0.2857022285461426s
Security | Check HTTPS for Bio2RDF::Sider took 0.17031025886535645s
Interpretability | RDF structures check for Bio2RDF::Sider took 0.24341154098510742s
Versatility | Serialization formats check for Bio2RDF::Sider took 0.29307007789611816s
Availability | RDF dump link check for Bio2RDF::Sider took 2.9337964057922363s
License | MR license check for Bio2RDF::Sider took 0.2982449531555176s
License | HR license check for Bio2RDF::Sider took 60.24467325210571s
Amount of data | Number of property check for Bio2RDF::Sider took 0.3111386299133301s
Understandability | Number of label check for Bio2RDF::Sider took 9.128467798233032s
Understandability | URI regex check for Bio2RDF::Sider took 0.6726565361022949s
Understandability | Vocabs check for Bio2RDF::Sider took 0.26006388664245605s
Verifiability | Authors check for Bio2RDF::Sider took 0.2765083312988281s
Verifiability | Publishers check for Bio2RDF::Sider took 0.3485567569732666s
Performance | Throughput check for Bio2RDF::Sider took 10.622609615325928s
Verifiability | Contribs. check for Bio2RDF::Sider took 0.5842983722686768s
Interlinking | sameAs chians check for Bio2RDF::Sider took 0.2717723846435547s
Interlinking | skos check for Bio2RDF::Sider took 0.35599613189697266s
Interlinking | skos check for Bio2RDF::Sider took 0.38257503509521484s
Timeliness | dataset update frequency check for Bio2RDF::Sider took 0.292360782623291s
Currency | Creation date check for Bio2RDF::Sider took 0.36702823638916016s
Currency | Modification date check for Bio2RDF::Sider took 0.29402613639831543s
Rep.Conc. | URIs length for Bio2RDF::Sider took 108.86021041870117s
Interoperability | New vocabularies check for Bio2RDF::Sider took 18.772039651870728s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sider took 0.5031213760375977s
Accuracy | Check Functional Property for Bio2RDF::Sider took 0.28852295875549316s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sider took 0.27365684509277344s
Accuracy | Check Empty annotation labels for Bio2RDF::Sider took 6.521440744400024s
Accuracy | Check White space in annotation for Bio2RDF::Sider took 0.8901050090789795s
Accuracy | Check Datatype consistency for Bio2RDF::Sider took 0.647968053817749s
Consistency | Disjoint class check for Bio2RDF::Sider took 0.41967010498046875s
Consistency | Check Misplaced properties for Bio2RDF::Sider took 64.94589471817017s
Consistency | Misplaced classes for Bio2RDF::Sider took 2.382970094680786s
Consistency | Check Ontology hijacking for Bio2RDF::Sider took 6.042653799057007s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sider took 1.3416430950164795s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sider took 61.585959672927856s
Conciseness | Check Extensional conciseness for Bio2RDF::Sider took 0.7277860641479492s
Conciseness | Check Intensional conciseness for Bio2RDF::Sider took 0.4159541130065918s
Security | Sign check for Bio2RDF::Sider took 0.24885201454162598s
Availability | Check URIs Dereferenciability for Bio2RDF::Sider took 3.891716718673706s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 1.6554343700408936s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.020477771759033203s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 4.673004150390625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sider took 18.973268032073975s
Believability | Calculation of trust value for Bio2RDF::Sider took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-sider took 1045.3780629634857s
Availability | SPARQL endpoint availability check for Bio2RDF::SPIKE took 0.14124131202697754s
Availability | VoID file availability check for Bio2RDF::SPIKE took 0.0010046958923339844s
Completeness | Calculation of interlinking completeness for Bio2RDF::SPIKE took 5.135241746902466s
Reputation | Calculation of the PageRank for Bio2RDF::SPIKE took 0.02032947540283203s
Interlinking | Calculation of Degree of Connection for Bio2RDF::SPIKE took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Bio2RDF::SPIKE took 0.0006890296936035156s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::SPIKE took 2.8848648071289062e-05s
Believability | Calculation of trust value for Bio2RDF::SPIKE took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-spike took 52.177048444747925s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 4.172325134277344e-05s
Availability | VoID file availability check for bio2rdf-taxon took 0.0003650188446044922s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 14.786111831665039s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.020799636840820312s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 4.100799560546875e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-taxon took 87.57878232002258s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 0.569904088973999s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 1.020209789276123s
Extra | Recovery of all triples for Bio2RDF::Taxonomy took 19.028919458389282s
Performance | Total latancy measurement for Bio2RDF::Taxonomy took 1.2481846809387207s
Amount of data | Number of triples check for Bio2RDF::Taxonomy took 44.97682452201843s
Interoperability | New terms check for Bio2RDF::Taxonomy took 40.23140478134155s
Versatility | Languages check for Bio2RDF::Taxonomy took 60.31872749328613s
Interpretability | Number of blank nodes check for Bio2RDF::Taxonomy took 0.27934980392456055s
Security | Check HTTPS for Bio2RDF::Taxonomy took 0.18346166610717773s
Interpretability | RDF structures check for Bio2RDF::Taxonomy took 0.2679147720336914s
Versatility | Serialization formats check for Bio2RDF::Taxonomy took 0.30207204818725586s
Availability | RDF dump link check for Bio2RDF::Taxonomy took 2.815516233444214s
License | MR license check for Bio2RDF::Taxonomy took 0.40473270416259766s
License | HR license check for Bio2RDF::Taxonomy took 60.278099060058594s
Amount of data | Number of property check for Bio2RDF::Taxonomy took 0.2576792240142822s
Understandability | Number of label check for Bio2RDF::Taxonomy took 10.05063533782959s
Understandability | URI regex check for Bio2RDF::Taxonomy took 0.6137783527374268s
Understandability | Vocabs check for Bio2RDF::Taxonomy took 0.2741830348968506s
Verifiability | Authors check for Bio2RDF::Taxonomy took 0.2546858787536621s
Verifiability | Publishers check for Bio2RDF::Taxonomy took 0.4033036231994629s
Performance | Throughput check for Bio2RDF::Taxonomy took 10.55388355255127s
Verifiability | Contribs. check for Bio2RDF::Taxonomy took 0.6296896934509277s
Interlinking | sameAs chians check for Bio2RDF::Taxonomy took 0.28819704055786133s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.3790929317474365s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.33887648582458496s
Timeliness | dataset update frequency check for Bio2RDF::Taxonomy took 0.26009535789489746s
Currency | Creation date check for Bio2RDF::Taxonomy took 0.3442988395690918s
Currency | Modification date check for Bio2RDF::Taxonomy took 0.2460765838623047s
Rep.Conc. | URIs length for Bio2RDF::Taxonomy took 106.32837700843811s
Interoperability | New vocabularies check for Bio2RDF::Taxonomy took 17.170209407806396s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Taxonomy took 0.44030332565307617s
Accuracy | Check Functional Property for Bio2RDF::Taxonomy took 0.2608165740966797s
Accuracy | Check Inverse Functional Property for Bio2RDF::Taxonomy took 0.2970619201660156s
Accuracy | Check Empty annotation labels for Bio2RDF::Taxonomy took 6.709501504898071s
Accuracy | Check White space in annotation for Bio2RDF::Taxonomy took 0.8950800895690918s
Accuracy | Check Datatype consistency for Bio2RDF::Taxonomy took 0.6536834239959717s
Consistency | Disjoint class check for Bio2RDF::Taxonomy took 0.2712852954864502s
Consistency | Check Misplaced properties for Bio2RDF::Taxonomy took 64.71521520614624s
Consistency | Misplaced classes for Bio2RDF::Taxonomy took 2.4409680366516113s
Consistency | Check Ontology hijacking for Bio2RDF::Taxonomy took 6.052417755126953s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Taxonomy took 1.2950780391693115s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Taxonomy took 61.55533027648926s
Conciseness | Check Extensional conciseness for Bio2RDF::Taxonomy took 0.7313249111175537s
Conciseness | Check Intensional conciseness for Bio2RDF::Taxonomy took 0.4693434238433838s
Security | Sign check for Bio2RDF::Taxonomy took 0.2355637550354004s
Availability | Check URIs Dereferenciability for Bio2RDF::Taxonomy took 3.6373932361602783s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 0.7793128490447998s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.02088332176208496s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0006871223449707031s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 0.00010538101196289062s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Taxonomy took 17.883601188659668s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 1.3828277587890625e-05s
INFO | --- Analysis for bio2rdf-taxonomy took 1034.4252915382385s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 0.1519782543182373s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.00924372673034668s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 0.8884098529815674s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.02035832405090332s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 4.57763671875e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-wikipathways took 22.9166476726532s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 0.5107846260070801s
Availability | VoID file availability check for Bio2RDF::Wormbase took 1.0925829410552979s
Extra | Recovery of all triples for Bio2RDF::Wormbase took 17.824837923049927s
Performance | Total latancy measurement for Bio2RDF::Wormbase took 1.3827204704284668s
Amount of data | Number of triples check for Bio2RDF::Wormbase took 45.04433822631836s
Interoperability | New terms check for Bio2RDF::Wormbase took 40.83951163291931s
Versatility | Languages check for Bio2RDF::Wormbase took 60.269160985946655s
Interpretability | Number of blank nodes check for Bio2RDF::Wormbase took 0.3278968334197998s
Security | Check HTTPS for Bio2RDF::Wormbase took 0.16777706146240234s
Interpretability | RDF structures check for Bio2RDF::Wormbase took 0.2656269073486328s
Versatility | Serialization formats check for Bio2RDF::Wormbase took 0.2489175796508789s
Availability | RDF dump link check for Bio2RDF::Wormbase took 3.094653367996216s
License | MR license check for Bio2RDF::Wormbase took 0.2445390224456787s
License | HR license check for Bio2RDF::Wormbase took 60.263999223709106s
Amount of data | Number of property check for Bio2RDF::Wormbase took 0.22916293144226074s
Understandability | Number of label check for Bio2RDF::Wormbase took 10.219088315963745s
Understandability | URI regex check for Bio2RDF::Wormbase took 0.6029739379882812s
Understandability | Vocabs check for Bio2RDF::Wormbase took 0.285020112991333s
Verifiability | Authors check for Bio2RDF::Wormbase took 0.2821927070617676s
Verifiability | Publishers check for Bio2RDF::Wormbase took 0.3655402660369873s
Performance | Throughput check for Bio2RDF::Wormbase took 10.66063404083252s
Verifiability | Contribs. check for Bio2RDF::Wormbase took 0.68422532081604s
Interlinking | sameAs chians check for Bio2RDF::Wormbase took 0.3021402359008789s
Interlinking | skos check for Bio2RDF::Wormbase took 0.4381747245788574s
Interlinking | skos check for Bio2RDF::Wormbase took 0.38788747787475586s
Timeliness | dataset update frequency check for Bio2RDF::Wormbase took 0.27904772758483887s
Currency | Creation date check for Bio2RDF::Wormbase took 0.4001953601837158s
Currency | Modification date check for Bio2RDF::Wormbase took 0.28848838806152344s
Rep.Conc. | URIs length for Bio2RDF::Wormbase took 107.13142418861389s
Interoperability | New vocabularies check for Bio2RDF::Wormbase took 18.41552209854126s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Wormbase took 0.39883875846862793s
Accuracy | Check Functional Property for Bio2RDF::Wormbase took 0.23787260055541992s
Accuracy | Check Inverse Functional Property for Bio2RDF::Wormbase took 0.2597932815551758s
Accuracy | Check Empty annotation labels for Bio2RDF::Wormbase took 6.356006860733032s
Accuracy | Check White space in annotation for Bio2RDF::Wormbase took 0.8930239677429199s
Accuracy | Check Datatype consistency for Bio2RDF::Wormbase took 0.6647355556488037s
Consistency | Disjoint class check for Bio2RDF::Wormbase took 0.252701997756958s
Consistency | Check Misplaced properties for Bio2RDF::Wormbase took 65.0137403011322s
Consistency | Misplaced classes for Bio2RDF::Wormbase took 2.4145491123199463s
Consistency | Check Ontology hijacking for Bio2RDF::Wormbase took 6.145916223526001s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Wormbase took 1.3460712432861328s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Wormbase took 61.610231161117554s
Conciseness | Check Extensional conciseness for Bio2RDF::Wormbase took 0.7461321353912354s
Conciseness | Check Intensional conciseness for Bio2RDF::Wormbase took 0.5117321014404297s
Security | Sign check for Bio2RDF::Wormbase took 0.2591068744659424s
Availability | Check URIs Dereferenciability for Bio2RDF::Wormbase took 4.074422597885132s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 11.44248914718628s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.020992040634155273s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 9.083747863769531e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Wormbase took 16.95881700515747s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-wormbase took 1046.7602157592773s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 0.25330185890197754s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.21245574951171875s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 0.325176477432251s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.02052164077758789s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 8.344650268554688e-05s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 1.1444091796875e-05s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 3.4410176277160645s
Availability | SPARQL endpoint availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0826425552368164s
Availability | VoID file availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.009401321411132812s
Completeness | Calculation of interlinking completeness for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.37343311309814453s
Reputation | Calculation of the PageRank for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.021773338317871094s
Interlinking | Calculation of Degree of Connection for A Short Biographical Dictionary of English Literature (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for A Short Biographical Dictionary of English Literature (RKBExplorer) took 2.7418136596679688e-05s
Believability | Calculation of trust value for A Short Biographical Dictionary of English Literature (RKBExplorer) took 1.2636184692382812e-05s
INFO | --- Analysis for biolit took 3.4440464973449707s
Availability | SPARQL endpoint availability check for BioLOD for Protein Data Bank Japan took 8.702278137207031e-05s
Availability | VoID file availability check for BioLOD for Protein Data Bank Japan took 3.5503416061401367s
Completeness | Calculation of interlinking completeness for BioLOD for Protein Data Bank Japan took 1.0153563022613525s
Reputation | Calculation of the PageRank for BioLOD for Protein Data Bank Japan took 0.020842552185058594s
Interlinking | Calculation of Degree of Connection for BioLOD for Protein Data Bank Japan took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BioLOD for Protein Data Bank Japan took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for BioLOD for Protein Data Bank Japan took 4.029273986816406e-05s
Believability | Calculation of trust value for BioLOD for Protein Data Bank Japan took 1.2636184692382812e-05s
INFO | --- Analysis for biolod-pdb took 12.546416997909546s
Availability | SPARQL endpoint availability check for BioModels RDF took 0.8272838592529297s
Availability | VoID file availability check for BioModels RDF took 0.24184370040893555s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.4157414436340332s
Reputation | Calculation of the PageRank for BioModels RDF took 0.020730257034301758s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 3.981590270996094e-05s
Believability | Calculation of trust value for BioModels RDF took 1.2636184692382812e-05s
INFO | --- Analysis for biomodels-rdf took 5.6714088916778564s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.7804417610168457s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.5093173980712891s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.040621280670166s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.020529985427856445s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.790855407714844e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.1205673217773438e-05s
INFO | --- Analysis for Biop took 10.18335771560669s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 8.320808410644531e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.1857314109802246s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.30719828605651855s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.021023988723754883s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.4809112548828125e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.049041748046875e-05s
INFO | --- Analysis for Bioportal took 3.3506383895874023s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 8.392333984375e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 2.2324533462524414s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.46720123291015625s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.02087259292602539s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006432533264160156s
Believability | Calculation of trust value for Amphibian gross anatomy took 1.811981201171875e-05s
INFO | --- Analysis for bioportal-aao took 11.354442596435547s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 8.273124694824219e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 1.8456461429595947s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 0.43535566329956055s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.021949052810668945s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.0003132820129394531s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-aba took 10.889480113983154s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 8.416175842285156e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 2.0841968059539795s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.2870340347290039s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.02248096466064453s
Interlinking | Calculation of Degree of Connection for Cancer Research and Management ACGT Master Ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Cancer Research and Management ACGT Master Ontology took 0.0007913112640380859s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0015234947204589844s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-acgt took 9.115520000457764s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 8.440017700195312e-05s
Availability | VoID file availability check for Animal natural history and life history took 1.8195335865020752s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 1.2252368927001953s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.02046346664428711s
Interlinking | Calculation of Degree of Connection for Animal natural history and life history took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Animal natural history and life history took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.0003249645233154297s
Believability | Calculation of trust value for Animal natural history and life history took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-adw took 10.77439022064209s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 8.606910705566406e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 1.8883934020996094s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 0.3320186138153076s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.020775794982910156s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.00047850608825683594s
Believability | Calculation of trust value for Anatomical Entity Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-aeo took 10.687022924423218s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 8.726119995117188e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 1.991575002670288s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 0.4274415969848633s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.0202486515045166s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0009465217590332031s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-aero took 10.202537536621094s
Availability | SPARQL endpoint availability check for AI/RHEUM took 8.702278137207031e-05s
Availability | VoID file availability check for AI/RHEUM took 1.8813385963439941s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 0.44820284843444824s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.020688533782958984s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.0004088878631591797s
Believability | Calculation of trust value for AI/RHEUM took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-air took 15.658778190612793s
Availability | SPARQL endpoint availability check for Amino Acid took 8.606910705566406e-05s
Availability | VoID file availability check for Amino Acid took 1.803497552871704s
Completeness | Calculation of interlinking completeness for Amino Acid took 0.5118274688720703s
Reputation | Calculation of the PageRank for Amino Acid took 0.02071404457092285s
Interlinking | Calculation of Degree of Connection for Amino Acid took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Amino Acid took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.00025534629821777344s
Believability | Calculation of trust value for Amino Acid took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-amino-acid took 11.05101466178894s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 8.821487426757812e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 1.8247623443603516s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.33243894577026367s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.0206301212310791s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.0002918243408203125s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-apo took 10.899676084518433s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 8.487701416015625e-05s
Availability | VoID file availability check for African Traditional Medicine took 1.8129746913909912s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 1.086130142211914s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.020557403564453125s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.0002486705780029297s
Believability | Calculation of trust value for African Traditional Medicine took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-atmo took 10.552566528320312s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 0.00010418891906738281s
Availability | VoID file availability check for Amphibian taxonomy took 1.8250000476837158s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.3136942386627197s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.020427942276000977s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 0.00010061264038085938s
Believability | Calculation of trust value for Amphibian taxonomy took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ato took 11.652269124984741s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 8.797645568847656e-05s
Availability | VoID file availability check for BioAssay Ontology took 1.8556249141693115s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 2.331378221511841s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.02073073387145996s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.0013082027435302734s
Believability | Calculation of trust value for BioAssay Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-bao took 13.060993671417236s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 8.678436279296875e-05s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 1.8389596939086914s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 0.9806990623474121s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.020322322845458984s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.0003826618194580078s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 12.096836805343628s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 8.654594421386719e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 1.8495368957519531s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.6565837860107422s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.02045917510986328s
Interlinking | Calculation of Degree of Connection for Breast Cancer Grading Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Breast Cancer Grading Ontology took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.00033164024353027344s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-bcgo took 11.1361083984375s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 8.511543273925781e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 1.851762294769287s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.3336942195892334s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.020702838897705078s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.001415252685546875s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-bdo took 10.209335565567017s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 8.606910705566406e-05s
Availability | VoID file availability check for Basic Formal Ontology took 1.828728199005127s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.34017014503479004s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.02063584327697754s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0006496906280517578s
Believability | Calculation of trust value for Basic Formal Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-bfo took 11.42930793762207s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 4.172325134277344e-05s
Availability | VoID file availability check for Bleeding History Phenotype took 1.8698158264160156s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.37284326553344727s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.020971059799194336s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0007331371307373047s
Believability | Calculation of trust value for Bleeding History Phenotype took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-bho took 10.95563817024231s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 4.220008850097656e-05s
Availability | VoID file availability check for Bilateria anatomy took 1.7753076553344727s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.2852189540863037s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.02077794075012207s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.0004258155822753906s
Believability | Calculation of trust value for Bilateria anatomy took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-bila took 10.090612649917603s
Availability | SPARQL endpoint availability check for BIRNLex took 8.606910705566406e-05s
Availability | VoID file availability check for BIRNLex took 1.859189748764038s
Completeness | Calculation of interlinking completeness for BIRNLex took 1.973587989807129s
Reputation | Calculation of the PageRank for BIRNLex took 0.020435810089111328s
Interlinking | Calculation of Degree of Connection for BIRNLex took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for BIRNLex took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.0014684200286865234s
Believability | Calculation of trust value for BIRNLex took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-birnlex took 14.675963640213013s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 1.795576572418213s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.583327054977417s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.022105932235717773s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007522106170654297s
Believability | Calculation of trust value for Gene Regulation Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-bootstrep took 10.864460468292236s
Availability | SPARQL endpoint availability check for BioPAX took 9.846687316894531e-05s
Availability | VoID file availability check for BioPAX took 1.8309204578399658s
Completeness | Calculation of interlinking completeness for BioPAX took 1.0523757934570312s
Reputation | Calculation of the PageRank for BioPAX took 0.02055978775024414s
Interlinking | Calculation of Degree of Connection for BioPAX took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for BioPAX took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for BioPAX took 0.000102996826171875s
Believability | Calculation of trust value for BioPAX took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-bp took 11.235279560089111s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 8.559226989746094e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 2.0421557426452637s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.4175403118133545s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.02074456214904785s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.00032901763916015625s
Believability | Calculation of trust value for Biomedical Resource Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-bro_x1 took 13.873215436935425s
Availability | SPARQL endpoint availability check for Spatial Ontology took 9.799003601074219e-05s
Availability | VoID file availability check for Spatial Ontology took 1.8257770538330078s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 3.2135982513427734s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.02057814598083496s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.00022029876708984375s
Believability | Calculation of trust value for Spatial Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-bspo took 17.658998489379883s
Availability | SPARQL endpoint availability check for BioTop took 8.678436279296875e-05s
Availability | VoID file availability check for BioTop took 1.816258192062378s
Completeness | Calculation of interlinking completeness for BioTop took 4.43452787399292s
Reputation | Calculation of the PageRank for BioTop took 0.02172684669494629s
Interlinking | Calculation of Degree of Connection for BioTop took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BioTop took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.00064849853515625s
Believability | Calculation of trust value for BioTop took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-bt took 35.50681972503662s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 8.749961853027344e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 1.7808201313018799s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 2.284362554550171s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.020510435104370117s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for BRENDA tissue / enzyme source took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0008993148803710938s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-bto took 13.814328670501709s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 9.5367431640625e-05s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 1.819528341293335s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.3510768413543701s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.020366668701171875s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.0019009113311767578s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-canco took 9.467110395431519s
Availability | SPARQL endpoint availability check for CAO took 9.942054748535156e-05s
Availability | VoID file availability check for CAO took 5.1688737869262695s
Completeness | Calculation of interlinking completeness for CAO took 0.3596634864807129s
Reputation | Calculation of the PageRank for CAO took 0.020959854125976562s
Interlinking | Calculation of Degree of Connection for CAO took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CAO took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0006434917449951172s
Believability | Calculation of trust value for CAO took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-cao took 15.917177200317383s
Availability | SPARQL endpoint availability check for CareLex took 8.535385131835938e-05s
Availability | VoID file availability check for CareLex took 1.8703501224517822s
Completeness | Calculation of interlinking completeness for CareLex took 0.49904537200927734s
Reputation | Calculation of the PageRank for CareLex took 0.020934343338012695s
Interlinking | Calculation of Degree of Connection for CareLex took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CareLex took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for CareLex took 5.1975250244140625e-05s
Believability | Calculation of trust value for CareLex took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-carelex took 13.693180084228516s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 8.678436279296875e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 1.7976696491241455s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.48766517639160156s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.020397186279296875s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0008037090301513672s
Believability | Calculation of trust value for Cell Cycle Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-cco took 11.506751537322998s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 0.000133514404296875s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 1.7899198532104492s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.4622979164123535s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.02037525177001953s
Interlinking | Calculation of Degree of Connection for Comparative Data Analysis Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Comparative Data Analysis Ontology took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.0002560615539550781s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-cdao took 10.531766414642334s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 0.00011086463928222656s
Availability | VoID file availability check for Chemical entities of biological interest took 1.8520991802215576s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.5230450630187988s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.02052760124206543s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0007910728454589844s
Believability | Calculation of trust value for Chemical entities of biological interest took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-chebi took 10.360721349716187s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 8.58306884765625e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 1.8637239933013916s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.7296724319458008s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.020699262619018555s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.00024819374084472656s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-chem2bio2owl took 10.569404363632202s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 8.678436279296875e-05s
Availability | VoID file availability check for Chemical Information Ontology took 1.8373277187347412s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.3044557571411133s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.021497726440429688s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0008223056793212891s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0008530616760253906s
Believability | Calculation of trust value for Chemical Information Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-cheminf took 9.749675750732422s
Availability | SPARQL endpoint availability check for Cell type took 8.606910705566406e-05s
Availability | VoID file availability check for Cell type took 1.8339216709136963s
Completeness | Calculation of interlinking completeness for Cell type took 1.45857834815979s
Reputation | Calculation of the PageRank for Cell type took 0.02071833610534668s
Interlinking | Calculation of Degree of Connection for Cell type took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cell type took 0.0007939338684082031s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.00040602684020996094s
Believability | Calculation of trust value for Cell type took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-cl took 14.971636295318604s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 9.489059448242188e-05s
Availability | VoID file availability check for Cell Line Ontology took 1.8289759159088135s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.3510143756866455s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.02211451530456543s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0007963180541992188s
Believability | Calculation of trust value for Cell Line Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-clo took 15.644690752029419s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 8.487701416015625e-05s
Availability | VoID file availability check for Clinical Measurement Ontology took 2.003138303756714s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 1.3128867149353027s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.020883560180664062s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.00017333030700683594s
Believability | Calculation of trust value for Clinical Measurement Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-cmo took 11.287282943725586s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 8.463859558105469e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 1.9121885299682617s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 3.3593010902404785s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.021657466888427734s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.0002105236053466797s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-cno took 15.154479265213013s
Availability | SPARQL endpoint availability check for Wheat trait took 8.654594421386719e-05s
Availability | VoID file availability check for Wheat trait took 1.8337268829345703s
Completeness | Calculation of interlinking completeness for Wheat trait took 0.40982913970947266s
Reputation | Calculation of the PageRank for Wheat trait took 0.02080702781677246s
Interlinking | Calculation of Degree of Connection for Wheat trait took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Wheat trait took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 5.2928924560546875e-05s
Believability | Calculation of trust value for Wheat trait took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-co_wheat took 10.250479221343994s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 0.00010371208190917969s
Availability | VoID file availability check for Cognitive Atlas took 1.7992815971374512s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.3489818572998047s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.02036118507385254s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.0003528594970703125s
Believability | Calculation of trust value for Cognitive Atlas took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-cogat took 10.257069826126099s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 0.0001347064971923828s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 1.863271713256836s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.32424306869506836s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.020501136779785156s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0007534027099609375s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-cogpo took 10.117132186889648s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 8.440017700195312e-05s
Availability | VoID file availability check for Current Procedural Terminology took 1.804903507232666s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.3283240795135498s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.020585060119628906s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.0004279613494873047s
Believability | Calculation of trust value for Current Procedural Terminology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-cpt took 10.26974368095398s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 8.392333984375e-05s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 1.8816461563110352s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 1.4331586360931396s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.02102518081665039s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.0018396377563476562s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-csp took 14.8260657787323s
Availability | SPARQL endpoint availability check for COSTART took 8.654594421386719e-05s
Availability | VoID file availability check for COSTART took 1.8229339122772217s
Completeness | Calculation of interlinking completeness for COSTART took 0.35276174545288086s
Reputation | Calculation of the PageRank for COSTART took 0.021816253662109375s
Interlinking | Calculation of Degree of Connection for COSTART took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for COSTART took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0009894371032714844s
Believability | Calculation of trust value for COSTART took 6.0558319091796875e-05s
INFO | --- Analysis for bioportal-cst took 11.65660572052002s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 8.320808410644531e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 1.809920310974121s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.5143027305603027s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.020711660385131836s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.0005173683166503906s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ctcae took 12.20578122138977s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 8.726119995117188e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 1.7988896369934082s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.9232707023620605s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.022084951400756836s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.00045800209045410156s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-ctx took 11.735953092575073s
Availability | SPARQL endpoint availability check for Dendritic cell took 9.226799011230469e-05s
Availability | VoID file availability check for Dendritic cell took 2.363499164581299s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.9566895961761475s
Reputation | Calculation of the PageRank for Dendritic cell took 0.020440101623535156s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.0002808570861816406s
Believability | Calculation of trust value for Dendritic cell took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-dc_cl took 11.460424900054932s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 8.630752563476562e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 1.7760968208312988s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 1.080967664718628s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.02061319351196289s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 8.559226989746094e-05s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ddanat took 10.932700872421265s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 4.1961669921875e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 1.8250443935394287s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.3427093029022217s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.02038860321044922s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.0009834766387939453s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ddi took 11.81899118423462s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 9.298324584960938e-05s
Availability | VoID file availability check for Diagnostic Ontology took 1.8831524848937988s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.3165402412414551s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.02263474464416504s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 8.416175842285156e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-diagnosticont took 11.415802240371704s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 8.273124694824219e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 2.4359047412872314s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.5115401744842529s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.02265167236328125s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.00016045570373535156s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-dikb-evidence took 12.12867546081543s
Availability | SPARQL endpoint availability check for Human disease ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Human disease ontology took 2.011934280395508s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.33795714378356934s
Reputation | Calculation of the PageRank for Human disease ontology took 0.020511388778686523s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Human disease ontology took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0006210803985595703s
Believability | Calculation of trust value for Human disease ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-doid took 9.863995790481567s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 8.559226989746094e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 1.8070650100708008s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 1.170652151107788s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.02137446403503418s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0007731914520263672s
Believability | Calculation of trust value for Electrocardiography Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ecg took 13.947622776031494s
Availability | SPARQL endpoint availability check for Evidence codes took 8.630752563476562e-05s
Availability | VoID file availability check for Evidence codes took 1.9578287601470947s
Completeness | Calculation of interlinking completeness for Evidence codes took 1.8734633922576904s
Reputation | Calculation of the PageRank for Evidence codes took 0.02248072624206543s
Interlinking | Calculation of Degree of Connection for Evidence codes took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Evidence codes took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 2.8371810913085938e-05s
Believability | Calculation of trust value for Evidence codes took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-eco took 13.9191312789917s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 8.511543273925781e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 1.8374757766723633s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.4499471187591553s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.021145105361938477s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.0018019676208496094s
Believability | Calculation of trust value for Experimental Factor Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-efo took 9.957048177719116s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 8.392333984375e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 2.012598752975464s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 1.9492740631103516s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.021209239959716797s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.001180410385131836s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-ehda took 12.104281902313232s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 0.00010323524475097656s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 1.822981595993042s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.4218893051147461s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.020895719528198242s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007174015045166016s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ehdaa took 10.356042385101318s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 4.315376281738281e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 1.7932214736938477s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.4000682830810547s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.02078104019165039s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version, v2 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version, v2 took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0005254745483398438s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-ehdaa2 took 10.639504671096802s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 4.3392181396484375e-05s
Availability | VoID file availability check for Mouse gross anatomy and development took 1.791377067565918s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 2.399556875228882s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.020535707473754883s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 2.8848648071289062e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-emap took 13.204690933227539s
Availability | SPARQL endpoint availability check for Environment Ontology took 9.489059448242188e-05s
Availability | VoID file availability check for Environment Ontology took 1.8787858486175537s
Completeness | Calculation of interlinking completeness for Environment Ontology took 3.949084997177124s
Reputation | Calculation of the PageRank for Environment Ontology took 0.021480083465576172s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0007905960083007812s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.00044035911560058594s
Believability | Calculation of trust value for Environment Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-envo took 17.16865587234497s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 4.315376281738281e-05s
Availability | VoID file availability check for Plant environmental conditions took 1.8395705223083496s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 1.6279244422912598s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.02119755744934082s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.0002999305725097656s
Believability | Calculation of trust value for Plant environmental conditions took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-eo took 18.82379388809204s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 1.8570914268493652s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.44891834259033203s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.02130293846130371s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.0012302398681640625s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ep took 9.513002872467041s
Availability | SPARQL endpoint availability check for Epilepsy took 4.220008850097656e-05s
Availability | VoID file availability check for Epilepsy took 1.8123414516448975s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.3875386714935303s
Reputation | Calculation of the PageRank for Epilepsy took 0.022449254989624023s
Interlinking | Calculation of Degree of Connection for Epilepsy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Epilepsy took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.0001461505889892578s
Believability | Calculation of trust value for Epilepsy took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-epileponto took 14.033969402313232s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 4.410743713378906e-05s
Availability | VoID file availability check for eagle-i research resource ontology took 1.8383359909057617s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.39971065521240234s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.020916223526000977s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.0011489391326904297s
Believability | Calculation of trust value for eagle-i research resource ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ero took 12.540451765060425s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 4.744529724121094e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 1.88226318359375s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 1.9908332824707031s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.020943641662597656s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.001135110855102539s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ev took 12.047086954116821s
Availability | SPARQL endpoint availability check for ExO took 4.267692565917969e-05s
Availability | VoID file availability check for ExO took 1.8458993434906006s
Completeness | Calculation of interlinking completeness for ExO took 0.4965798854827881s
Reputation | Calculation of the PageRank for ExO took 0.02090907096862793s
Interlinking | Calculation of Degree of Connection for ExO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ExO took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for ExO took 0.0002529621124267578s
Believability | Calculation of trust value for ExO took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-exo took 11.210208177566528s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 0.0001010894775390625s
Availability | VoID file availability check for Fungal gross anatomy took 1.7996864318847656s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 1.6088743209838867s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.020279407501220703s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.00011348724365234375s
Believability | Calculation of trust value for Fungal gross anatomy took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-fao took 16.122647523880005s
Availability | SPARQL endpoint availability check for Biological imaging methods took 9.107589721679688e-05s
Availability | VoID file availability check for Biological imaging methods took 1.815802812576294s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 1.011652946472168s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.02232813835144043s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.00020575523376464844s
Believability | Calculation of trust value for Biological imaging methods took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-fbbi took 10.183181047439575s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 8.344650268554688e-05s
Availability | VoID file availability check for Drosophila gross anatomy took 1.8189568519592285s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 3.5614705085754395s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.02085423469543457s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0006732940673828125s
Believability | Calculation of trust value for Drosophila gross anatomy took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-fbbt took 18.779901027679443s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 8.296966552734375e-05s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 1.8022997379302979s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.2727639675140381s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.02074146270751953s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.0004565715789794922s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-fbcv took 14.292333841323853s
Availability | SPARQL endpoint availability check for Drosophila development took 9.632110595703125e-05s
Availability | VoID file availability check for Drosophila development took 1.8204879760742188s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.3108861446380615s
Reputation | Calculation of the PageRank for Drosophila development took 0.023106098175048828s
Interlinking | Calculation of Degree of Connection for Drosophila development took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Drosophila development took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.482269287109375e-05s
Believability | Calculation of trust value for Drosophila development took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-fbdv took 10.75299620628357s
Availability | SPARQL endpoint availability check for Fly taxonomy took 8.463859558105469e-05s
Availability | VoID file availability check for Fly taxonomy took 1.8445093631744385s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.5874810218811035s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.021029949188232422s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.0003795623779296875s
Believability | Calculation of trust value for Fly taxonomy took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-fbsp took 10.13097596168518s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 4.172325134277344e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 1.839137077331543s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.3405036926269531s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.020909547805786133s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.0002338886260986328s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-fda-meddevice took 17.297550439834595s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 8.96453857421875e-05s
Availability | VoID file availability check for Family Health History Ontology took 2.0409798622131348s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 0.32064270973205566s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.021043777465820312s
Interlinking | Calculation of Degree of Connection for Family Health History Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Family Health History Ontology took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.00045180320739746094s
Believability | Calculation of trust value for Family Health History Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-fhho took 15.166563749313354s
Availability | SPARQL endpoint availability check for Influenza Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Influenza Ontology took 1.835559606552124s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 1.0682122707366943s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.02079916000366211s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.0010712146759033203s
Believability | Calculation of trust value for Influenza Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-flu took 12.054886817932129s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 8.511543273925781e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 2.256183624267578s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.5991666316986084s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.021177291870117188s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 7.104873657226562e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-fma took 11.495710611343384s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 8.58306884765625e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 1.7944221496582031s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 1.5233960151672363s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.02109503746032715s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.00014328956604003906s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-fypo took 13.47274899482727s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 8.249282836914062e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 2.0122592449188232s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 2.1232945919036865s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.02104783058166504s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 0.00010609626770019531s
Believability | Calculation of trust value for GeoSpecies Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-geospecies took 15.382800340652466s
Availability | SPARQL endpoint availability check for General Formal Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for General Formal Ontology took 1.8071134090423584s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.5182254314422607s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.020500659942626953s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.0001614093780517578s
Believability | Calculation of trust value for General Formal Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-gfo took 10.95035982131958s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 9.107589721679688e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 1.8132953643798828s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.3295722007751465s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.020854711532592773s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.0006275177001953125s
Believability | Calculation of trust value for General Formal Ontology: Biology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-gfo-bio took 8.87847638130188s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 4.315376281738281e-05s
Availability | VoID file availability check for Gene Ontology Extension took 2.4575858116149902s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 2.084401845932007s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.020531177520751953s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0008985996246337891s
Believability | Calculation of trust value for Gene Ontology Extension took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-go_x1 took 16.806501626968384s
Availability | SPARQL endpoint availability check for Gene Ontology took 8.678436279296875e-05s
Availability | VoID file availability check for Gene Ontology took 1.8655340671539307s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.33796072006225586s
Reputation | Calculation of the PageRank for Gene Ontology took 0.021485567092895508s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0007927417755126953s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0008614063262939453s
Believability | Calculation of trust value for Gene Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-go_x2 took 13.293894529342651s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 4.863739013671875e-05s
Availability | VoID file availability check for Cereal Plant Development took 1.813218355178833s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 0.4973335266113281s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.020989179611206055s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 3.147125244140625e-05s
Believability | Calculation of trust value for Cereal Plant Development took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-gro took 12.97539472579956s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 0.00012373924255371094s
Availability | VoID file availability check for Cereal plant gross anatomy took 1.8659160137176514s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 0.6198036670684814s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.02055644989013672s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.00042939186096191406s
Believability | Calculation of trust value for Cereal plant gross anatomy took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-gro_x1 took 16.418526649475098s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 8.702278137207031e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 1.9189670085906982s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 2.7451038360595703s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020877599716186523s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007681846618652344s
Believability | Calculation of trust value for Gene Regulation Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-gro_x2 took 16.28697156906128s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 8.797645568847656e-05s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 1.8620717525482178s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.39017152786254883s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.020738840103149414s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0005548000335693359s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-hao took 12.330424070358276s
Availability | SPARQL endpoint availability check for HCPCS took 8.511543273925781e-05s
Availability | VoID file availability check for HCPCS took 1.8223090171813965s
Completeness | Calculation of interlinking completeness for HCPCS took 1.7465646266937256s
Reputation | Calculation of the PageRank for HCPCS took 0.022031307220458984s
Interlinking | Calculation of Degree of Connection for HCPCS took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for HCPCS took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.0002391338348388672s
Believability | Calculation of trust value for HCPCS took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-hcpcs took 12.232144594192505s
Availability | SPARQL endpoint availability check for Health Level Seven took 8.821487426757812e-05s
Availability | VoID file availability check for Health Level Seven took 2.6710572242736816s
Completeness | Calculation of interlinking completeness for Health Level Seven took 2.3614158630371094s
Reputation | Calculation of the PageRank for Health Level Seven took 0.02121710777282715s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.0013053417205810547s
Believability | Calculation of trust value for Health Level Seven took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-hl7 took 12.883253812789917s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 8.726119995117188e-05s
Availability | VoID file availability check for HEALTH_INDICATORS took 1.842210292816162s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.30832719802856445s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.02087235450744629s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.0004127025604248047s
Believability | Calculation of trust value for HEALTH_INDICATORS took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-hlth_indics took 13.891578674316406s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 8.463859558105469e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 2.0183732509613037s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.7989885807037354s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.020999670028686523s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 3.266334533691406e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-hom took 10.256183862686157s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 8.559226989746094e-05s
Availability | VoID file availability check for HOM-HARVARD took 1.840141773223877s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 0.4447636604309082s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.020880937576293945s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 2.9802322387695312e-05s
Believability | Calculation of trust value for HOM-HARVARD took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-hom_harvard took 11.58157467842102s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 8.440017700195312e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 1.8626723289489746s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.4356098175048828s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.02050614356994629s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.000659942626953125s
Believability | Calculation of trust value for Human Phenotype Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-hp_x1 took 14.600761651992798s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 8.511543273925781e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 1.8908569812774658s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 0.4283432960510254s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.02061629295349121s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.001016855239868164s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-hpio took 11.09619665145874s
Availability | SPARQL endpoint availability check for HUGO took 9.799003601074219e-05s
Availability | VoID file availability check for HUGO took 1.928908109664917s
Completeness | Calculation of interlinking completeness for HUGO took 0.8766686916351318s
Reputation | Calculation of the PageRank for HUGO took 0.022037506103515625s
Interlinking | Calculation of Degree of Connection for HUGO took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for HUGO took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for HUGO took 8.034706115722656e-05s
Believability | Calculation of trust value for HUGO took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-hugo took 10.935450553894043s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 8.7738037109375e-05s
Availability | VoID file availability check for Information Artifact Ontology took 1.8173246383666992s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 0.41869306564331055s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.02263665199279785s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0006821155548095703s
Believability | Calculation of trust value for Information Artifact Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-iao took 9.871137142181396s
Availability | SPARQL endpoint availability check for ICD10 took 8.511543273925781e-05s
Availability | VoID file availability check for ICD10 took 1.8767127990722656s
Completeness | Calculation of interlinking completeness for ICD10 took 1.0681383609771729s
Reputation | Calculation of the PageRank for ICD10 took 0.021031618118286133s
Interlinking | Calculation of Degree of Connection for ICD10 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ICD10 took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.000835418701171875s
Believability | Calculation of trust value for ICD10 took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-icd10 took 15.311746597290039s
Availability | SPARQL endpoint availability check for ICD10CM took 8.559226989746094e-05s
Availability | VoID file availability check for ICD10CM took 1.7953197956085205s
Completeness | Calculation of interlinking completeness for ICD10CM took 1.9814012050628662s
Reputation | Calculation of the PageRank for ICD10CM took 0.021297216415405273s
Interlinking | Calculation of Degree of Connection for ICD10CM took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ICD10CM took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0006508827209472656s
Believability | Calculation of trust value for ICD10CM took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-icd10cm took 10.448859691619873s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 0.00011873245239257812s
Availability | VoID file availability check for ICD-10-PCS took 1.893512487411499s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 2.216942310333252s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.021061420440673828s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.00015306472778320312s
Believability | Calculation of trust value for ICD-10-PCS took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-icd10pcs took 16.23026418685913s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 8.606910705566406e-05s
Availability | VoID file availability check for International Classification of Diseases took 1.843909740447998s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 1.0606539249420166s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.020633697509765625s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0006623268127441406s
Believability | Calculation of trust value for International Classification of Diseases took 1.52587890625e-05s
INFO | --- Analysis for bioportal-icd9cm took 12.849509954452515s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 9.751319885253906e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 1.8023130893707275s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.2921469211578369s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.020332813262939453s
Interlinking | Calculation of Degree of Connection for International Classification of Functioning, Disability and Health (ICF) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for International Classification of Functioning, Disability and Health (ICF) took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.00044608116149902344s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-icf_x1 took 10.034960269927979s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 0.00010371208190917969s
Availability | VoID file availability check for International Classification for Nursing Practice took 1.8234515190124512s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 0.33666157722473145s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.0216672420501709s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.001247406005859375s
Believability | Calculation of trust value for International Classification for Nursing Practice took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-icnp took 9.407942295074463s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 8.511543273925781e-05s
Availability | VoID file availability check for International Classification of Primary Care took 1.8857204914093018s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 0.6087415218353271s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.020613908767700195s
Interlinking | Calculation of Degree of Connection for International Classification of Primary Care took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for International Classification of Primary Care took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.00046062469482421875s
Believability | Calculation of trust value for International Classification of Primary Care took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-icpc took 10.96016240119934s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 8.869171142578125e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 1.831181287765503s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.4255218505859375s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.020679950714111328s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0008342266082763672s
Believability | Calculation of trust value for ICPC-2 PLUS took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-icpc2p took 13.578413248062134s
Availability | SPARQL endpoint availability check for ICPS Network took 9.131431579589844e-05s
Availability | VoID file availability check for ICPS Network took 1.8131937980651855s
Completeness | Calculation of interlinking completeness for ICPS Network took 1.6466777324676514s
Reputation | Calculation of the PageRank for ICPS Network took 0.02093505859375s
Interlinking | Calculation of Degree of Connection for ICPS Network took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ICPS Network took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.0002269744873046875s
Believability | Calculation of trust value for ICPS Network took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-icps took 11.415153503417969s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 9.655952453613281e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 1.852480411529541s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.36734509468078613s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.020537376403808594s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0009191036224365234s
Believability | Calculation of trust value for Infectious Disease Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-ido took 11.054661512374878s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 8.678436279296875e-05s
Availability | VoID file availability check for Brucellosis Ontology took 1.8259882926940918s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.4919309616088867s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.020923852920532227s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0011296272277832031s
Believability | Calculation of trust value for Brucellosis Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-idobru took 9.17494797706604s
Availability | SPARQL endpoint availability check for Malaria Ontology took 8.511543273925781e-05s
Availability | VoID file availability check for Malaria Ontology took 1.8455700874328613s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.3951702117919922s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.020790576934814453s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0007784366607666016s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.001313924789428711s
Believability | Calculation of trust value for Malaria Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-idomal took 9.611491441726685s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 0.0001163482666015625s
Availability | VoID file availability check for Event (INOH pathway ontology) took 1.7788236141204834s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 0.4559590816497803s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.02034902572631836s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.0003116130828857422s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-iev took 9.894675970077515s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 8.559226989746094e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 1.8129913806915283s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.3627438545227051s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.020731687545776367s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.00014638900756835938s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-imgt took 12.186681985855103s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 8.440017700195312e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 1.8430697917938232s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.3138773441314697s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.020343542098999023s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0005171298980712891s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-imr took 9.998430490493774s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 8.511543273925781e-05s
Availability | VoID file availability check for Interaction Network Ontology took 1.8050940036773682s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.8205215930938721s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.02144026756286621s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0008237361907958984s
Believability | Calculation of trust value for Interaction Network Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ino took 14.697391748428345s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 0.0001380443572998047s
Availability | VoID file availability check for Hewan Invertebrata took 1.827380657196045s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.5856740474700928s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.021178007125854492s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 3.1948089599609375e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-invertebrata took 11.244286060333252s
Availability | SPARQL endpoint availability check for IxnO took 4.38690185546875e-05s
Availability | VoID file availability check for IxnO took 1.9607272148132324s
Completeness | Calculation of interlinking completeness for IxnO took 0.3212614059448242s
Reputation | Calculation of the PageRank for IxnO took 0.020446300506591797s
Interlinking | Calculation of Degree of Connection for IxnO took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for IxnO took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.00018906593322753906s
Believability | Calculation of trust value for IxnO took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ixno took 9.731248378753662s
Availability | SPARQL endpoint availability check for SysMO-JERM took 8.440017700195312e-05s
Availability | VoID file availability check for SysMO-JERM took 1.8341648578643799s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 1.4100558757781982s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.0222165584564209s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.0003833770751953125s
Believability | Calculation of trust value for SysMO-JERM took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-jerm took 15.567655324935913s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 0.00011706352233886719s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 1.8303227424621582s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.3164856433868408s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.022184133529663086s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.0009253025054931641s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 4.7206878662109375e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-kisao took 10.796160221099854s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 8.821487426757812e-05s
Availability | VoID file availability check for Loggerhead nesting took 1.7948098182678223s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.3569817543029785s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.021544694900512695s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.00020885467529296875s
Believability | Calculation of trust value for Loggerhead nesting took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-lhn took 9.258970260620117s
Availability | SPARQL endpoint availability check for Lipid Ontology took 8.249282836914062e-05s
Availability | VoID file availability check for Lipid Ontology took 1.851874828338623s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 0.7061328887939453s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.020891189575195312s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.00021266937255859375s
Believability | Calculation of trust value for Lipid Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-lipro took 10.160032749176025s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 0.0001201629638671875s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 1.996936559677124s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.5422353744506836s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.020847797393798828s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.0019047260284423828s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-lnc took 10.4317467212677s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 8.559226989746094e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 2.414686679840088s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 1.9383060932159424s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.020817041397094727s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0006463527679443359s
Believability | Calculation of trust value for Mouse adult gross anatomy took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-ma took 16.07675290107727s
Availability | SPARQL endpoint availability check for Multiple alignment took 0.00012731552124023438s
Availability | VoID file availability check for Multiple alignment took 1.7905259132385254s
Completeness | Calculation of interlinking completeness for Multiple alignment took 1.2506930828094482s
Reputation | Calculation of the PageRank for Multiple alignment took 0.020711898803710938s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.0002048015594482422s
Believability | Calculation of trust value for Multiple alignment took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-mao took 14.554898738861084s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 8.20159912109375e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 1.825962781906128s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 1.406308889389038s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.020242691040039062s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0007314682006835938s
Believability | Calculation of trust value for Minimal anatomical terminology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-mat took 12.799898862838745s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 0.00011110305786132812s
Availability | VoID file availability check for Breast tissue cell lines took 1.8583481311798096s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.4811739921569824s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.020548582077026367s
Interlinking | Calculation of Degree of Connection for Breast tissue cell lines took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Breast tissue cell lines took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.000423431396484375s
Believability | Calculation of trust value for Breast tissue cell lines took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-mcbcc took 11.869433164596558s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Cell line ontology took 1.950392484664917s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.3504664897918701s
Reputation | Calculation of the PageRank for Cell line ontology took 0.020702362060546875s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0007538795471191406s
Believability | Calculation of trust value for Cell line ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mccl took 10.815148115158081s
Availability | SPARQL endpoint availability check for Cell line ontology took 8.487701416015625e-05s
Availability | VoID file availability check for Cell line ontology took 1.819786548614502s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.5010037422180176s
Reputation | Calculation of the PageRank for Cell line ontology took 0.02040886878967285s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0014190673828125s
Believability | Calculation of trust value for Cell line ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-mccl_x1 took 10.417306184768677s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 8.368492126464844e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 1.7837297916412354s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.4171934127807617s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.02057623863220215s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.0002491474151611328s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-mcv took 10.591236591339111s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 9.560585021972656e-05s
Availability | VoID file availability check for Master Drug Data Base took 2.1698989868164062s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 3.3425521850585938s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.020882368087768555s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.0001862049102783203s
Believability | Calculation of trust value for Master Drug Data Base took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-mddb took 26.01131772994995s
Availability | SPARQL endpoint availability check for MedDRA took 9.441375732421875e-05s
Availability | VoID file availability check for MedDRA took 1.7997760772705078s
Completeness | Calculation of interlinking completeness for MedDRA took 3.051199197769165s
Reputation | Calculation of the PageRank for MedDRA took 0.022531747817993164s
Interlinking | Calculation of Degree of Connection for MedDRA took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for MedDRA took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.0011181831359863281s
Believability | Calculation of trust value for MedDRA took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-mdr took 16.449265718460083s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 8.606910705566406e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 1.7944931983947754s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.4417252540588379s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.021112918853759766s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0009219646453857422s
Believability | Calculation of trust value for MedlinePlus Health Topics took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-medlineplus took 14.180905103683472s
Availability | SPARQL endpoint availability check for MeGO took 5.4836273193359375e-05s
Availability | VoID file availability check for MeGO took 1.7888004779815674s
Completeness | Calculation of interlinking completeness for MeGO took 0.7542080879211426s
Reputation | Calculation of the PageRank for MeGO took 0.02078723907470703s
Interlinking | Calculation of Degree of Connection for MeGO took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MeGO took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.0001499652862548828s
Believability | Calculation of trust value for MeGO took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-mego took 13.390692472457886s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 8.511543273925781e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 1.8231432437896729s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 0.3724827766418457s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.020909547805786133s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.0018792152404785156s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 1.4066696166992188e-05s
INFO | --- Analysis for bioportal-mesh-owl took 12.278769493103027s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 1.813084363937378s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 0.7397146224975586s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.0204465389251709s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0006182193756103516s
Believability | Calculation of trust value for Mental Functioning Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-mf took 9.681689023971558s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 8.296966552734375e-05s
Availability | VoID file availability check for Medaka fish anatomy and development took 2.9947924613952637s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 0.4947488307952881s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.020434141159057617s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0005540847778320312s
Believability | Calculation of trust value for Medaka fish anatomy and development took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mfo took 11.673555135726929s
Availability | SPARQL endpoint availability check for Emotion Ontology took 9.369850158691406e-05s
Availability | VoID file availability check for Emotion Ontology took 1.861680269241333s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 2.7528576850891113s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.020471572875976562s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0007500648498535156s
Believability | Calculation of trust value for Emotion Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mfoem took 16.454245567321777s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 8.463859558105469e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 1.8784127235412598s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 4.2906880378723145s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.02060532569885254s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 6.341934204101562e-05s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.00011348724365234375s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mhc took 18.260722398757935s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 4.2438507080078125e-05s
Availability | VoID file availability check for Protein-protein interaction took 1.847524642944336s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.29949164390563965s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.021021366119384766s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0006947517395019531s
Believability | Calculation of trust value for Protein-protein interaction took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mi took 10.97823166847229s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 0.00010347366333007812s
Availability | VoID file availability check for Mosquito insecticide resistance took 1.8617732524871826s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.52773118019104s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.020786762237548828s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0007197856903076172s
Believability | Calculation of trust value for Mosquito insecticide resistance took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-miro took 13.892394304275513s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 8.535385131835938e-05s
Availability | VoID file availability check for Measurement Method Ontology took 1.8013916015625s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.3502311706542969s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.021450042724609375s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.0001373291015625s
Believability | Calculation of trust value for Measurement Method Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-mmo took 13.686208009719849s
Availability | SPARQL endpoint availability check for MGED Ontology took 4.649162292480469e-05s
Availability | VoID file availability check for MGED Ontology took 1.8201031684875488s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.3939032554626465s
Reputation | Calculation of the PageRank for MGED Ontology took 0.020313024520874023s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.00038695335388183594s
Believability | Calculation of trust value for MGED Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-mo took 10.800869703292847s
Availability | SPARQL endpoint availability check for Protein modification took 8.845329284667969e-05s
Availability | VoID file availability check for Protein modification took 1.8416023254394531s
Completeness | Calculation of interlinking completeness for Protein modification took 0.3497343063354492s
Reputation | Calculation of the PageRank for Protein modification took 0.020592689514160156s
Interlinking | Calculation of Degree of Connection for Protein modification took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Protein modification took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.00022649765014648438s
Believability | Calculation of trust value for Protein modification took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mod took 9.9168062210083s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 8.511543273925781e-05s
Availability | VoID file availability check for Mammalian phenotype took 2.0292792320251465s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 0.9862096309661865s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.020523786544799805s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0006389617919921875s
Believability | Calculation of trust value for Mammalian phenotype took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-mp took 12.69678521156311s
Availability | SPARQL endpoint availability check for Mouse pathology took 8.320808410644531e-05s
Availability | VoID file availability check for Mouse pathology took 2.0141074657440186s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.2930457592010498s
Reputation | Calculation of the PageRank for Mouse pathology took 0.02041339874267578s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.00048613548278808594s
Believability | Calculation of trust value for Mouse pathology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-mpath took 13.484337091445923s
Availability | SPARQL endpoint availability check for Mass spectrometry took 8.702278137207031e-05s
Availability | VoID file availability check for Mass spectrometry took 1.7792656421661377s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.7553479671478271s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.021172761917114258s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0008172988891601562s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.0004162788391113281s
Believability | Calculation of trust value for Mass spectrometry took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-ms took 13.257591247558594s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 4.124641418457031e-05s
Availability | VoID file availability check for Medical Subject Headings took 1.8468575477600098s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.41217732429504395s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.020734310150146484s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.0018947124481201172s
Believability | Calculation of trust value for Medical Subject Headings took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-msh took 10.765767574310303s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 8.440017700195312e-05s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 2.260503053665161s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 3.375394582748413s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.02171492576599121s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.00017976760864257812s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mthch took 18.16611385345459s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 8.606910705566406e-05s
Availability | VoID file availability check for Natural Products Ontology took 1.7847437858581543s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 0.399517297744751s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.020846843719482422s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0007982254028320312s
Believability | Calculation of trust value for Natural Products Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-natpro took 11.881436109542847s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 8.392333984375e-05s
Availability | VoID file availability check for NCBI organismal classification took 1.887019157409668s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.8207862377166748s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.020411252975463867s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0008039474487304688s
Believability | Calculation of trust value for NCBI organismal classification took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-ncbitaxon took 10.655577182769775s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 4.172325134277344e-05s
Availability | VoID file availability check for NCI Thesaurus took 1.7988910675048828s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.48391079902648926s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.021596670150756836s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.00080108642578125s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.002114534378051758s
Believability | Calculation of trust value for NCI Thesaurus took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-ncit took 10.55663514137268s
Availability | SPARQL endpoint availability check for National Drug Data File took 8.606910705566406e-05s
Availability | VoID file availability check for National Drug Data File took 1.981187343597412s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.623633861541748s
Reputation | Calculation of the PageRank for National Drug Data File took 0.02065134048461914s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for National Drug Data File took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0006277561187744141s
Believability | Calculation of trust value for National Drug Data File took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-nddf took 11.315349578857422s
Availability | SPARQL endpoint availability check for National Drug File took 4.267692565917969e-05s
Availability | VoID file availability check for National Drug File took 1.981091022491455s
Completeness | Calculation of interlinking completeness for National Drug File took 0.31365513801574707s
Reputation | Calculation of the PageRank for National Drug File took 0.02104353904724121s
Interlinking | Calculation of Degree of Connection for National Drug File took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for National Drug File took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.001224517822265625s
Believability | Calculation of trust value for National Drug File took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ndfrt took 13.480120420455933s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 0.00010395050048828125s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 2.0106289386749268s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.3038899898529053s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.02053046226501465s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.0011494159698486328s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-nemo_x1 took 11.574113368988037s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 8.535385131835938e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 1.8391921520233154s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.5031232833862305s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.020412206649780273s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Neomark Oral Cancer Ontology took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0006525516510009766s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-neomark took 12.550741195678711s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 8.58306884765625e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 1.795933485031128s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 1.5033354759216309s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.02053546905517578s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.00012159347534179688s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-neomarkontology took 12.94722318649292s
Availability | SPARQL endpoint availability check for NIFSTD took 8.225440979003906e-05s
Availability | VoID file availability check for NIFSTD took 1.9946177005767822s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.34975171089172363s
Reputation | Calculation of the PageRank for NIFSTD took 0.020558834075927734s
Interlinking | Calculation of Degree of Connection for NIFSTD took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NIFSTD took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.0019230842590332031s
Believability | Calculation of trust value for NIFSTD took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-nif took 9.710673809051514s
Availability | SPARQL endpoint availability check for NIF Cell took 4.506111145019531e-05s
Availability | VoID file availability check for NIF Cell took 1.8384034633636475s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.6619694232940674s
Reputation | Calculation of the PageRank for NIF Cell took 0.020697593688964844s
Interlinking | Calculation of Degree of Connection for NIF Cell took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NIF Cell took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.0013511180877685547s
Believability | Calculation of trust value for NIF Cell took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-nif_cell took 14.203787565231323s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 8.797645568847656e-05s
Availability | VoID file availability check for NIF Dysfunction took 1.8735332489013672s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.507850170135498s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.020784378051757812s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.001375436782836914s
Believability | Calculation of trust value for NIF Dysfunction took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-nif_dysfunction took 32.68440866470337s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 8.130073547363281e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 1.865600824356079s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.31641578674316406s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.02076411247253418s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0005953311920166016s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-nigo took 24.08524227142334s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 9.846687316894531e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 1.815157175064087s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.4289264678955078s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.02044963836669922s
Interlinking | Calculation of Degree of Connection for NMR-instrument specific component of metabolomics investigations took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NMR-instrument specific component of metabolomics investigations took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0005762577056884766s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-nmr took 9.721830129623413s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 8.225440979003906e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 2.0336148738861084s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.8989307880401611s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.0211029052734375s
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.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.0001125335693359375s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-nonrctontology took 11.558348178863525s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 4.839897155761719e-05s
Availability | VoID file availability check for NanoParticle Ontology took 1.7948763370513916s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.3918731212615967s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.020563125610351562s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.001207590103149414s
Believability | Calculation of trust value for NanoParticle Ontology took 6.699562072753906e-05s
INFO | --- Analysis for bioportal-npo took 14.377821445465088s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 9.036064147949219e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 1.8176319599151611s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.5730559825897217s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.020279645919799805s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0007543563842773438s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-oae took 13.249287605285645s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 8.559226989746094e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 1.8360607624053955s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 1.6111788749694824s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.02155590057373047s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.0014472007751464844s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-obi took 11.760852098464966s
Availability | SPARQL endpoint availability check for OBOE took 8.463859558105469e-05s
Availability | VoID file availability check for OBOE took 1.7979187965393066s
Completeness | Calculation of interlinking completeness for OBOE took 2.3456149101257324s
Reputation | Calculation of the PageRank for OBOE took 0.021177053451538086s
Interlinking | Calculation of Degree of Connection for OBOE took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OBOE took 0.0007796287536621094s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.0001266002655029297s
Believability | Calculation of trust value for OBOE took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-oboe took 20.54747462272644s
Availability | SPARQL endpoint availability check for OBOE SBC took 8.58306884765625e-05s
Availability | VoID file availability check for OBOE SBC took 2.552537441253662s
Completeness | Calculation of interlinking completeness for OBOE SBC took 5.187157392501831s
Reputation | Calculation of the PageRank for OBOE SBC took 0.020815372467041016s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0007910728454589844s
Believability | Calculation of trust value for OBOE SBC took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-oboe-sbc took 17.807787895202637s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 9.942054748535156e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 1.851684808731079s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 2.1332943439483643s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.021306514739990234s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0005977153778076172s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-ocre took 22.357481956481934s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 8.344650268554688e-05s
Availability | VoID file availability check for Ontology for disease genetic investigation took 1.8075857162475586s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 4.238339185714722s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.02053236961364746s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0008313655853271484s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-odgi took 19.751799821853638s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 0.00012636184692382812s
Availability | VoID file availability check for Ontology for Genetic Interval took 2.4337635040283203s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 0.33657407760620117s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.02051544189453125s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0008807182312011719s
Believability | Calculation of trust value for Ontology for Genetic Interval took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-ogi took 18.60515022277832s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 8.654594421386719e-05s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 1.8574941158294678s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 0.448624849319458s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.020664453506469727s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.0003108978271484375s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-ogmd took 21.059426307678223s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 8.606910705566406e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 1.8009145259857178s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.27971529960632324s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.02027106285095215s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0006756782531738281s
Believability | Calculation of trust value for Ontology for General Medical Science took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-ogms took 9.320481538772583s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 4.506111145019531e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 1.854740858078003s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.3500254154205322s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.020414113998413086s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.001169443130493164s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-omim took 10.026149034500122s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 4.506111145019531e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 1.8402140140533447s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.3852555751800537s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.020963430404663086s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.0003800392150878906s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-omit took 10.296586275100708s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 4.1484832763671875e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 1.8268718719482422s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.3652167320251465s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.020886659622192383s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0006101131439208984s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-omrse took 9.37373661994934s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 4.2438507080078125e-05s
Availability | VoID file availability check for Ontology of Data Mining took 2.425863027572632s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.38650965690612793s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.021095991134643555s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.0007953643798828125s
Believability | Calculation of trust value for Ontology of Data Mining took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ontodm took 10.960486888885498s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 4.553794860839844e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 1.7953500747680664s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 0.3460705280303955s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.021518945693969727s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.0002455711364746094s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-ontodt took 12.84584665298462s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 4.220008850097656e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 1.8176867961883545s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.6952252388000488s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.020499467849731445s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.0006220340728759766s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ontoorpha took 11.134762048721313s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 8.726119995117188e-05s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 2.0582027435302734s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 1.33890700340271s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.020363569259643555s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0009257793426513672s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-opl took 12.705115795135498s
Availability | SPARQL endpoint availability check for Phenotypic quality took 8.726119995117188e-05s
Availability | VoID file availability check for Phenotypic quality took 1.958099603652954s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.32927799224853516s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.022280454635620117s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0008649826049804688s
Believability | Calculation of trust value for Phenotypic quality took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-pato took 10.853683948516846s
Availability | SPARQL endpoint availability check for Physician Data Query took 8.678436279296875e-05s
Availability | VoID file availability check for Physician Data Query took 1.8474516868591309s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.3196253776550293s
Reputation | Calculation of the PageRank for Physician Data Query took 0.0209197998046875s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Physician Data Query took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0008466243743896484s
Believability | Calculation of trust value for Physician Data Query took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-pdq took 12.913917064666748s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 8.893013000488281e-05s
Availability | VoID file availability check for Pediatric Terminology took 1.8575961589813232s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.6515889167785645s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.020763874053955078s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0007772445678710938s
Believability | Calculation of trust value for Pediatric Terminology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-pedterm took 11.394503355026245s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 8.96453857421875e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 1.8061044216156006s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 0.3137242794036865s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.020739078521728516s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.00020074844360351562s
Believability | Calculation of trust value for Parasite Experiment Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-peo took 10.252373695373535s
Availability | SPARQL endpoint availability check for PHARE took 4.553794860839844e-05s
Availability | VoID file availability check for PHARE took 2.0053162574768066s
Completeness | Calculation of interlinking completeness for PHARE took 0.44356346130371094s
Reputation | Calculation of the PageRank for PHARE took 0.020871639251708984s
Interlinking | Calculation of Degree of Connection for PHARE took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for PHARE took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006425380706787109s
Believability | Calculation of trust value for PHARE took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-phare took 10.351555585861206s
Availability | SPARQL endpoint availability check for PKO_Re took 4.482269287109375e-05s
Availability | VoID file availability check for PKO_Re took 1.8091545104980469s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.38382601737976074s
Reputation | Calculation of the PageRank for PKO_Re took 0.020802736282348633s
Interlinking | Calculation of Degree of Connection for PKO_Re took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for PKO_Re took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.00017690658569335938s
Believability | Calculation of trust value for PKO_Re took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-pko took 10.426716089248657s
Availability | SPARQL endpoint availability check for PMA 2010 took 8.463859558105469e-05s
Availability | VoID file availability check for PMA 2010 took 2.028862714767456s
Completeness | Calculation of interlinking completeness for PMA 2010 took 2.029762029647827s
Reputation | Calculation of the PageRank for PMA 2010 took 0.02059030532836914s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0008990764617919922s
Believability | Calculation of trust value for PMA 2010 took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-pma took 13.19774866104126s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 8.630752563476562e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 1.8120665550231934s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.3387877941131592s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.020830154418945312s
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.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.0001728534698486328s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-pmr took 14.2982497215271s
Availability | SPARQL endpoint availability check for Plant Anatomy took 8.96453857421875e-05s
Availability | VoID file availability check for Plant Anatomy took 1.8699250221252441s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.6328091621398926s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.020571470260620117s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.00039649009704589844s
Believability | Calculation of trust value for Plant Anatomy took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-po took 10.694772243499756s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 9.72747802734375e-05s
Availability | VoID file availability check for Plant Growth and Development Stage took 2.7099664211273193s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.6107356548309326s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.023198843002319336s
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.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 0.00010275840759277344s
Believability | Calculation of trust value for Plant Growth and Development Stage took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-po_x1 took 13.632700204849243s
Availability | SPARQL endpoint availability check for Plant Ontology took 9.059906005859375e-05s
Availability | VoID file availability check for Plant Ontology took 1.8401329517364502s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.6464691162109375s
Reputation | Calculation of the PageRank for Plant Ontology took 0.02068042755126953s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.00044655799865722656s
Believability | Calculation of trust value for Plant Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-po_x2 took 10.957260131835938s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 8.535385131835938e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 1.8182945251464844s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.8178057670593262s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.02079939842224121s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0006694793701171875s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-pr took 10.240250825881958s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 0.00016999244689941406s
Availability | VoID file availability check for Proteomics data and process provenance took 1.8161537647247314s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 0.40003347396850586s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.02175593376159668s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.0002684593200683594s
Believability | Calculation of trust value for Proteomics data and process provenance took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-propreo took 11.670448064804077s
Availability | SPARQL endpoint availability check for Pathway ontology took 8.940696716308594e-05s
Availability | VoID file availability check for Pathway ontology took 1.833437442779541s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.32242441177368164s
Reputation | Calculation of the PageRank for Pathway ontology took 0.021111011505126953s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Pathway ontology took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.0001285076141357422s
Believability | Calculation of trust value for Pathway ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-pw took 11.748401403427124s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 1.7980823516845703s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.32074570655822754s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.020730018615722656s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 3.147125244140625e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-qibo took 10.802521467208862s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 4.100799560546875e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 1.9857666492462158s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.3793635368347168s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.02078986167907715s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0017840862274169922s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-rcd took 13.21541976928711s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 8.392333984375e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 1.8484177589416504s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 2.2376835346221924s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.02139115333557129s
Interlinking | Calculation of Degree of Connection for Randomized Controlled Trials (RCT) Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Randomized Controlled Trials (RCT) Ontology took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.00013518333435058594s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-rctontology took 11.731091976165771s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 8.559226989746094e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 1.776548147201538s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 3.248563289642334s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.020655155181884766s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 9.489059448242188e-05s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-repo took 16.53477144241333s
Availability | SPARQL endpoint availability check for Physico-chemical process took 0.0001010894775390625s
Availability | VoID file availability check for Physico-chemical process took 1.826296329498291s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.68772292137146s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.02081584930419922s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.0001933574676513672s
Believability | Calculation of trust value for Physico-chemical process took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-rex took 11.952944040298462s
Availability | SPARQL endpoint availability check for RadLex took 8.606910705566406e-05s
Availability | VoID file availability check for RadLex took 1.8487648963928223s
Completeness | Calculation of interlinking completeness for RadLex took 1.2842614650726318s
Reputation | Calculation of the PageRank for RadLex took 0.020415782928466797s
Interlinking | Calculation of Degree of Connection for RadLex took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RadLex took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.0015130043029785156s
Believability | Calculation of trust value for RadLex took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-rid took 12.635124921798706s
Availability | SPARQL endpoint availability check for RNA ontology took 4.172325134277344e-05s
Availability | VoID file availability check for RNA ontology took 1.8663668632507324s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.45464420318603516s
Reputation | Calculation of the PageRank for RNA ontology took 0.02177572250366211s
Interlinking | Calculation of Degree of Connection for RNA ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RNA ontology took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0005712509155273438s
Believability | Calculation of trust value for RNA ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-rnao took 10.845953226089478s
Availability | SPARQL endpoint availability check for Role Ontology took 8.368492126464844e-05s
Availability | VoID file availability check for Role Ontology took 1.7956304550170898s
Completeness | Calculation of interlinking completeness for Role Ontology took 1.7079992294311523s
Reputation | Calculation of the PageRank for Role Ontology took 0.020970821380615234s
Interlinking | Calculation of Degree of Connection for Role Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Role Ontology took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.00022339820861816406s
Believability | Calculation of trust value for Role Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-roleo took 11.566143989562988s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 9.250640869140625e-05s
Availability | VoID file availability check for Rat Strain Ontology took 1.8569259643554688s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.7487502098083496s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.02110004425048828s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.00018930435180664062s
Believability | Calculation of trust value for Rat Strain Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-rs took 18.757558345794678s
Availability | SPARQL endpoint availability check for RxNORM took 8.559226989746094e-05s
Availability | VoID file availability check for RxNORM took 1.8002874851226807s
Completeness | Calculation of interlinking completeness for RxNORM took 0.28092265129089355s
Reputation | Calculation of the PageRank for RxNORM took 0.020389318466186523s
Interlinking | Calculation of Degree of Connection for RxNORM took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for RxNORM took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0006070137023925781s
Believability | Calculation of trust value for RxNORM took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-rxnorm took 11.51876974105835s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 9.560585021972656e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 1.847637414932251s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.32737112045288086s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.02066946029663086s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.0010833740234375s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-sao took 13.170606136322021s
Availability | SPARQL endpoint availability check for Systems Biology took 8.940696716308594e-05s
Availability | VoID file availability check for Systems Biology took 1.8198738098144531s
Completeness | Calculation of interlinking completeness for Systems Biology took 3.361072301864624s
Reputation | Calculation of the PageRank for Systems Biology took 0.02009439468383789s
Interlinking | Calculation of Degree of Connection for Systems Biology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Systems Biology took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.0004706382751464844s
Believability | Calculation of trust value for Systems Biology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-sbo took 16.51391625404358s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 0.00012183189392089844s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 1.8248322010040283s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.6690213680267334s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.02078843116760254s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.0001163482666015625s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-sbro took 11.724604368209839s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 8.678436279296875e-05s
Availability | VoID file availability check for Sleep Domain Ontology took 1.8304078578948975s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.3431878089904785s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.021023988723754883s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.0013270378112792969s
Believability | Calculation of trust value for Sleep Domain Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-sdo took 11.545301675796509s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 8.654594421386719e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 2.802381753921509s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 1.535499095916748s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.02055215835571289s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.00034618377685546875s
Believability | Calculation of trust value for Sample processing and separation techniques took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-sep took 13.118875741958618s
Availability | SPARQL endpoint availability check for Student Health Record took 8.559226989746094e-05s
Availability | VoID file availability check for Student Health Record took 1.9970474243164062s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.3036785125732422s
Reputation | Calculation of the PageRank for Student Health Record took 0.020857810974121094s
Interlinking | Calculation of Degree of Connection for Student Health Record took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Student Health Record took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.0004494190216064453s
Believability | Calculation of trust value for Student Health Record took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-shr took 9.007107973098755s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 8.749961853027344e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 1.8288657665252686s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 5.699988603591919s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.021086692810058594s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.0012564659118652344s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-sio took 15.155332803726196s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 0.0001304149627685547s
Availability | VoID file availability check for Situation-Based Access Control took 2.138913631439209s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 0.4458189010620117s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.020517349243164062s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.00020241737365722656s
Believability | Calculation of trust value for Situation-Based Access Control took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-sitbac took 15.251957178115845s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 8.606910705566406e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 1.8632619380950928s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 2.250974178314209s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.020398378372192383s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.0019669532775878906s
Believability | Calculation of trust value for SNOMED Clinical Terms took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-snomedct took 13.338409423828125s
Availability | SPARQL endpoint availability check for SNP-Ontology took 8.487701416015625e-05s
Availability | VoID file availability check for SNP-Ontology took 1.8008067607879639s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 2.796161651611328s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.02230215072631836s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.00066375732421875s
Believability | Calculation of trust value for SNP-Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-snpo took 15.275329113006592s
Availability | SPARQL endpoint availability check for Sequence types and features took 0.00012636184692382812s
Availability | VoID file availability check for Sequence types and features took 2.040471076965332s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.4444866180419922s
Reputation | Calculation of the PageRank for Sequence types and features took 0.020520448684692383s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Sequence types and features took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0005724430084228516s
Believability | Calculation of trust value for Sequence types and features took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-so_x1 took 15.056326627731323s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 8.678436279296875e-05s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 1.8308444023132324s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.3816521167755127s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.02048468589782715s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.0015954971313476562s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-sopharm took 11.632388830184937s
Availability | SPARQL endpoint availability check for SoyOntology took 8.559226989746094e-05s
Availability | VoID file availability check for SoyOntology took 1.8518099784851074s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.3344411849975586s
Reputation | Calculation of the PageRank for SoyOntology took 0.020888328552246094s
Interlinking | Calculation of Degree of Connection for SoyOntology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SoyOntology took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.0001316070556640625s
Believability | Calculation of trust value for SoyOntology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-soy took 10.74514651298523s
Availability | SPARQL endpoint availability check for Spider Ontology took 8.58306884765625e-05s
Availability | VoID file availability check for Spider Ontology took 1.8417177200317383s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.8527307510375977s
Reputation | Calculation of the PageRank for Spider Ontology took 0.02060866355895996s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.0003268718719482422s
Believability | Calculation of trust value for Spider Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-spd took 11.954418897628784s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 9.894371032714844e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 1.8769400119781494s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.31382155418395996s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.020763635635375977s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.00028228759765625s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-spto took 13.1645188331604s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 8.749961853027344e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 1.8362681865692139s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.3879997730255127s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.022599220275878906s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0008053779602050781s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.0004658699035644531s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-sso took 12.856788873672485s
Availability | SPARQL endpoint availability check for Software Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Software Ontology took 1.8617894649505615s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.3363335132598877s
Reputation | Calculation of the PageRank for Software Ontology took 0.020642757415771484s
Interlinking | Calculation of Degree of Connection for Software Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Software Ontology took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.0004222393035888672s
Believability | Calculation of trust value for Software Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-swo took 9.033158302307129s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 9.870529174804688e-05s
Availability | VoID file availability check for Tick gross anatomy took 1.8042263984680176s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.2954106330871582s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.020571231842041016s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.00023436546325683594s
Believability | Calculation of trust value for Tick gross anatomy took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-tads took 9.051010608673096s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 8.463859558105469e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 1.8701789379119873s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.32732343673706055s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.02053689956665039s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0008873939514160156s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-tao took 14.487690687179565s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 8.7738037109375e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 1.8152177333831787s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.3517012596130371s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.02060532569885254s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 9.489059448242188e-05s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-taxrank took 13.406700134277344s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 4.172325134277344e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 1.8213119506835938s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.32533907890319824s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.02072000503540039s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 7.271766662597656e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-teddy took 10.229645013809204s
Availability | SPARQL endpoint availability check for Time Event Ontology took 8.702278137207031e-05s
Availability | VoID file availability check for Time Event Ontology took 1.8672521114349365s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.3492398262023926s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.02045893669128418s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0008151531219482422s
Believability | Calculation of trust value for Time Event Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-teo took 13.319807291030884s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 8.630752563476562e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 2.4249472618103027s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.43436670303344727s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.021351337432861328s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.00040602684020996094s
Believability | Calculation of trust value for Mosquito gross anatomy took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-tgma took 12.317156791687012s
Availability | SPARQL endpoint availability check for thesaurus took 4.291534423828125e-05s
Availability | VoID file availability check for thesaurus took 1.8061258792877197s
Completeness | Calculation of interlinking completeness for thesaurus took 0.3346896171569824s
Reputation | Calculation of the PageRank for thesaurus took 0.02148580551147461s
Interlinking | Calculation of Degree of Connection for thesaurus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for thesaurus took 0.0007982254028320312s
Interlinking | Calculation of Clustering coefficient for thesaurus took 7.605552673339844e-05s
Believability | Calculation of trust value for thesaurus took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-thesaurus took 15.714593410491943s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 4.2438507080078125e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 1.997241497039795s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 2.297856330871582s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.02182912826538086s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.0003821849822998047s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 15.049401044845581s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for Translational Medicine Ontology took 2.0260798931121826s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.7284946441650391s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.020954132080078125s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0008482933044433594s
Believability | Calculation of trust value for Translational Medicine Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-tmo took 14.72054386138916s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Plant Trait Ontology took 1.9988377094268799s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 0.30740904808044434s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.020363807678222656s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.0001513957977294922s
Believability | Calculation of trust value for Plant Trait Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-to took 10.147154092788696s
Availability | SPARQL endpoint availability check for TOK_Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for TOK_Ontology took 5.135766983032227s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 1.6002933979034424s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.02132558822631836s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.00018286705017089844s
Believability | Calculation of trust value for TOK_Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-tok took 16.96302342414856s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 8.368492126464844e-05s
Availability | VoID file availability check for Teleost taxonomy took 1.8453011512756348s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 0.3315000534057617s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.020700693130493164s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.00019621849060058594s
Believability | Calculation of trust value for Teleost taxonomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-tto took 13.015766382217407s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Uber anatomy ontology took 1.784621000289917s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.36208605766296387s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.020970582962036133s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.0010342597961425781s
Believability | Calculation of trust value for Uber anatomy ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-uberon took 9.639789581298828s
Availability | SPARQL endpoint availability check for Units Ontology took 0.00012636184692382812s
Availability | VoID file availability check for Units Ontology took 1.8119843006134033s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.31053900718688965s
Reputation | Calculation of the PageRank for Units Ontology took 0.02113509178161621s
Interlinking | Calculation of Degree of Connection for Units Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Units Ontology took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.0002396106719970703s
Believability | Calculation of trust value for Units Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-unitsontology took 11.614682674407959s
Availability | SPARQL endpoint availability check for Units of measurement took 8.368492126464844e-05s
Availability | VoID file availability check for Units of measurement took 1.8298087120056152s
Completeness | Calculation of interlinking completeness for Units of measurement took 0.4537622928619385s
Reputation | Calculation of the PageRank for Units of measurement took 0.021099567413330078s
Interlinking | Calculation of Degree of Connection for Units of measurement took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Units of measurement took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.0003094673156738281s
Believability | Calculation of trust value for Units of measurement took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-uo took 11.918147563934326s
Availability | SPARQL endpoint availability check for VANDF took 8.58306884765625e-05s
Availability | VoID file availability check for VANDF took 2.1837940216064453s
Completeness | Calculation of interlinking completeness for VANDF took 0.36805057525634766s
Reputation | Calculation of the PageRank for VANDF took 0.020931005477905273s
Interlinking | Calculation of Degree of Connection for VANDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for VANDF took 0.0008180141448974609s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0007045269012451172s
Believability | Calculation of trust value for VANDF took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-vandf took 9.56214451789856s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 2.00705623626709s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 1.872614860534668s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.020808935165405273s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.00043964385986328125s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-vao took 12.831999778747559s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 4.2438507080078125e-05s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 1.990147590637207s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 0.6969687938690186s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.020426034927368164s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0006468296051025391s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-vhog took 11.434604406356812s
Availability | SPARQL endpoint availability check for VIVO took 8.678436279296875e-05s
Availability | VoID file availability check for VIVO took 1.8199560642242432s
Completeness | Calculation of interlinking completeness for VIVO took 0.3575892448425293s
Reputation | Calculation of the PageRank for VIVO took 0.020963668823242188s
Interlinking | Calculation of Degree of Connection for VIVO took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for VIVO took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.00037598609924316406s
Believability | Calculation of trust value for VIVO took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-vivo took 10.177513360977173s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 8.463859558105469e-05s
Availability | VoID file availability check for Vaccine Ontology took 1.832906723022461s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 1.0635292530059814s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.020684480667114258s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.0012576580047607422s
Believability | Calculation of trust value for Vaccine Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-vo took 11.901341676712036s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 8.726119995117188e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 2.998093843460083s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.30291032791137695s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.020929574966430664s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.00020813941955566406s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-vt took 14.691918849945068s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 4.410743713378906e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 1.7936105728149414s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.9248049259185791s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.020627737045288086s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.0005450248718261719s
Believability | Calculation of trust value for C. elegans gross anatomy took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-wbbt took 11.859161853790283s
Availability | SPARQL endpoint availability check for C. elegans development took 9.918212890625e-05s
Availability | VoID file availability check for C. elegans development took 1.8585054874420166s
Completeness | Calculation of interlinking completeness for C. elegans development took 2.043581247329712s
Reputation | Calculation of the PageRank for C. elegans development took 0.022582292556762695s
Interlinking | Calculation of Degree of Connection for C. elegans development took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for C. elegans development took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 5.3882598876953125e-05s
Believability | Calculation of trust value for C. elegans development took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-wbls took 16.548984050750732s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 9.34600830078125e-05s
Availability | VoID file availability check for C. elegans phenotype took 1.8285942077636719s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.3673086166381836s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.022179603576660156s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 8.7738037109375e-05s
Believability | Calculation of trust value for C. elegans phenotype took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-wbphenotype took 12.241206884384155s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 4.9114227294921875e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 1.8227992057800293s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.41486072540283203s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.020681381225585938s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0006124973297119141s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-who took 11.579771518707275s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 4.506111145019531e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 1.8191442489624023s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.5867912769317627s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.02060413360595703s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.0006949901580810547s
Believability | Calculation of trust value for Xenopus anatomy and development took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-xao took 10.569110870361328s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 8.630752563476562e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 1.7797389030456543s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.37953710556030273s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.020897626876831055s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.0002377033233642578s
Believability | Calculation of trust value for Experimental Conditions Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-xco took 12.938703060150146s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 8.225440979003906e-05s
Availability | VoID file availability check for Yeast phenotypes took 1.8097875118255615s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 0.29965829849243164s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.021364212036132812s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.0002999305725097656s
Believability | Calculation of trust value for Yeast phenotypes took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-ypo took 14.507793664932251s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 8.726119995117188e-05s
Availability | VoID file availability check for Zebrafish anatomy and development took 1.8047025203704834s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 0.3904573917388916s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.020364046096801758s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.0007653236389160156s
Believability | Calculation of trust value for Zebrafish anatomy and development took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-zfa took 14.357146501541138s
Availability | SPARQL endpoint availability check for Indian Terrorism Ontology (InTO) took 8.463859558105469e-05s
Availability | VoID file availability check for Indian Terrorism Ontology (InTO) took 1.2819817066192627s
Completeness | Calculation of interlinking completeness for Indian Terrorism Ontology (InTO) took 2.071564197540283s
Reputation | Calculation of the PageRank for Indian Terrorism Ontology (InTO) took 0.021609783172607422s
Interlinking | Calculation of Degree of Connection for Indian Terrorism Ontology (InTO) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Indian Terrorism Ontology (InTO) took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Indian Terrorism Ontology (InTO) took 3.337860107421875e-05s
Believability | Calculation of trust value for Indian Terrorism Ontology (InTO) took 1.1920928955078125e-05s
INFO | --- Analysis for Bioportal_link took 8.303611278533936s
Availability | SPARQL endpoint availability check for BioSamples RDF took 0.8446877002716064s
Availability | VoID file availability check for BioSamples RDF took 0.22952556610107422s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.42985010147094727s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.020634174346923828s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 3.4809112548828125e-05s
Believability | Calculation of trust value for BioSamples RDF took 1.2636184692382812e-05s
INFO | --- Analysis for biosamples-rdf took 5.2472100257873535s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 0.0975189208984375s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.0002205371856689453s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 0.43221449851989746s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.021384239196777344s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.0010344982147216797s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.00014138221740722656s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 1.2874603271484375e-05s
INFO | --- Analysis for bis-linked-data took 2.7001895904541016s
Availability | SPARQL endpoint availability check for Bitzi took 8.7738037109375e-05s
Availability | VoID file availability check for Bitzi took 0.2552008628845215s
Completeness | Calculation of interlinking completeness for Bitzi took 0.40834498405456543s
Reputation | Calculation of the PageRank for Bitzi took 0.022532939910888672s
Interlinking | Calculation of Degree of Connection for Bitzi took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bitzi took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Bitzi took 3.24249267578125e-05s
Believability | Calculation of trust value for Bitzi took 1.2874603271484375e-05s
INFO | --- Analysis for bitzi took 4.442468881607056s
Availability | SPARQL endpoint availability check for BizkaiSense took 0.2671184539794922s
Availability | VoID file availability check for BizkaiSense took 0.09521317481994629s
Completeness | Calculation of interlinking completeness for BizkaiSense took 1.533811330795288s
Reputation | Calculation of the PageRank for BizkaiSense took 0.02286553382873535s
Interlinking | Calculation of Degree of Connection for BizkaiSense took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BizkaiSense took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for BizkaiSense took 3.4809112548828125e-05s
Believability | Calculation of trust value for BizkaiSense took 5.1975250244140625e-05s
INFO | --- Analysis for bizkaisense took 3.737470865249634s
Availability | SPARQL endpoint availability check for blabla.itemlist took 0.00016736984252929688s
Availability | VoID file availability check for blabla.itemlist took 20.095811128616333s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.4223198890686035s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.020754098892211914s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 3.3855438232421875e-05s
Believability | Calculation of trust value for blabla.itemlist took 1.2874603271484375e-05s
INFO | --- Analysis for blabla-itemlist took 54.96389603614807s
Availability | SPARQL endpoint availability check for blabla.itemlist took 8.416175842285156e-05s
Availability | VoID file availability check for blabla.itemlist took 20.096462965011597s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 1.7575416564941406s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.022894620895385742s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 3.409385681152344e-05s
Believability | Calculation of trust value for blabla.itemlist took 1.1444091796875e-05s
INFO | --- Analysis for blabla_itemlist took 55.19378852844238s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.00016379356384277344s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.41805052757263184s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.5271327495574951s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.02142167091369629s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.1484832763671875e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for bll-thesaurus took 3.887019395828247s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 1.0317747592926025s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.09861087799072266s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 0.41637301445007324s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.020679712295532227s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 7.486343383789062e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 1.3589859008789062e-05s
INFO | --- Analysis for bluk-bnb took 11.429385662078857s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.2821023464202881s
Availability | VoID file availability check for Thesaurus BNCF took 0.18552756309509277s
Extra | Recovery of all triples for Thesaurus BNCF took 42.63161587715149s
Performance | Total latancy measurement for Thesaurus BNCF took 0.6368193626403809s
Amount of data | Number of triples check for Thesaurus BNCF took 0.6358664035797119s
Interoperability | New terms check for Thesaurus BNCF took 1.5120913982391357s
Versatility | Languages check for Thesaurus BNCF took 6.317535638809204s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 0.8422000408172607s
Security | Check HTTPS for Thesaurus BNCF took 0.09340548515319824s
Interpretability | RDF structures check for Thesaurus BNCF took 0.13465642929077148s
Versatility | Serialization formats check for Thesaurus BNCF took 0.1412041187286377s
Availability | RDF dump link check for Thesaurus BNCF took 0.10625052452087402s
License | MR license check for Thesaurus BNCF took 0.13829994201660156s
License | HR license check for Thesaurus BNCF took 0.19729924201965332s
Amount of data | Number of property check for Thesaurus BNCF took 0.13258934020996094s
Understandability | Number of label check for Thesaurus BNCF took 0.2956690788269043s
Understandability | URI regex check for Thesaurus BNCF took 0.2645742893218994s
Understandability | Vocabs check for Thesaurus BNCF took 0.1467435359954834s
Verifiability | Authors check for Thesaurus BNCF took 0.1251382827758789s
Verifiability | Publishers check for Thesaurus BNCF took 0.1429736614227295s
Performance | Throughput check for Thesaurus BNCF took 10.81052851676941s
Amount of data | Check the number of entities for Thesaurus BNCF took 8.344650268554688e-05s
Verifiability | Contribs. check for Thesaurus BNCF took 0.16277694702148438s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.12886333465576172s
Interlinking | skos check for Thesaurus BNCF took 0.184495210647583s
Interlinking | skos check for Thesaurus BNCF took 0.14154481887817383s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.12282085418701172s
Currency | Creation date check for Thesaurus BNCF took 0.12727069854736328s
Currency | Modification date check for Thesaurus BNCF took 0.2577338218688965s
Rep.Conc. | URIs length for Thesaurus BNCF took 24.455925941467285s
Interoperability | New vocabularies check for Thesaurus BNCF took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.12263107299804688s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.1537315845489502s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.11346793174743652s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 12.646257877349854s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.48128533363342285s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 3.8673648834228516s
Consistency | Disjoint class check for Thesaurus BNCF took 0.13904762268066406s
Consistency | Check Misplaced properties for Thesaurus BNCF took 0.8631994724273682s
Consistency | Misplaced classes for Thesaurus BNCF took 6.656501054763794s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 6.712049245834351s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.4164090156555176s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.1274468898773193s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.38193416595459s
Security | Sign check for Thesaurus BNCF took 0.14080500602722168s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 18.73973798751831s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.4819769859313965s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.02061939239501953s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 7.319450378417969e-05s
Interoperability | Check the re-using of existing vocabs for Thesaurus BNCF took 2.1457672119140625e-06s
Believability | Calculation of trust value for Thesaurus BNCF took 7.62939453125e-06s
INFO | --- Analysis for bncf-ns took 176.34635138511658s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.20591020584106445s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.00028252601623535156s
Extra | Recovery of all triples for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.3935973644256592s
Performance | Total latancy measurement for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.47734689712524414s
Amount of data | Number of triples check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.117326498031616s
Interoperability | New terms check for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.6642074584960938s
Versatility | Languages check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.10090184211731s
Interpretability | Number of blank nodes check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.9706416130065918s
Security | Check HTTPS for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.21045899391174316s
Interpretability | RDF structures check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.1607680320739746s
Versatility | Serialization formats check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.19224309921264648s
Availability | RDF dump link check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.1943190097808838s
License | MR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.27642822265625s
License | HR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.05942988395691s
Amount of data | Number of property check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.09585380554199219s
Understandability | Number of label check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6518237590789795s
Understandability | URI regex check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.16407060623168945s
Understandability | Vocabs check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.16431808471679688s
Verifiability | Authors check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3431830406188965s
Verifiability | Publishers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5757021903991699s
Performance | Throughput check for BPR ? Bibliography of the Italian Parliament and electoral studies took 10.639341354370117s
Amount of data | Check the number of entities for BPR ? Bibliography of the Italian Parliament and electoral studies took 8.606910705566406e-05s
Verifiability | Contribs. check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3348217010498047s
Interlinking | sameAs chians check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.1291816234588623s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.1313624382019043s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0917215347290039s
Timeliness | dataset update frequency check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.09816312789916992s
Currency | Creation date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.1833784580230713s
Currency | Modification date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.12254905700683594s
Rep.Conc. | URIs length for BPR ? Bibliography of the Italian Parliament and electoral studies took 15.658458948135376s
Interoperability | New vocabularies check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.10493707656860352s
Accuracy | Check Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.11178255081176758s
Accuracy | Check Inverse Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.09435725212097168s
Accuracy | Check Empty annotation labels for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5402650833129883s
Accuracy | Check White space in annotation for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.030401229858398438s
Accuracy | Check Datatype consistency for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.027387380599975586s
Consistency | Disjoint class check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.10805034637451172s
Consistency | Check Misplaced properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 11.470221042633057s
Consistency | Misplaced classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.21089935302734375s
Consistency | Check Ontology hijacking for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.3280019760131836s
Consistency | Check Invalid usage of undefined classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.8710682392120361s
Consistency | Check Invalid usage of undefined properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 13.309338092803955s
Conciseness | Check Extensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.032398223876953125s
Conciseness | Check Intensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.17749881744384766s
Security | Sign check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.08474373817443848s
Availability | Check URIs Dereferenciability for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.9506664276123047s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5783283710479736s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.02103424072265625s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 5.650520324707031e-05s
Interoperability | Check the re-using of existing vocabs for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.430511474609375e-06s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.0013580322265625e-05s
INFO | --- Analysis for bpr took 321.72920322418213s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 8.96453857421875e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.24037551879882812s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.43900322914123535s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.02116107940673828s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 6.604194641113281e-05s
Believability | Calculation of trust value for Brazilian Politicians took 8.106231689453125e-06s
INFO | --- Analysis for brazilian-politicians took 10.268534183502197s
Availability | SPARQL endpoint availability check for BrazilianCities took 254.80290865898132s
Availability | VoID file availability check for BrazilianCities took 0.00017023086547851562s
Completeness | Calculation of interlinking completeness for BrazilianCities took 1.1781458854675293s
Reputation | Calculation of the PageRank for BrazilianCities took 0.022528886795043945s
Interlinking | Calculation of Degree of Connection for BrazilianCities took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for BrazilianCities took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for BrazilianCities took 3.933906555175781e-05s
Believability | Calculation of trust value for BrazilianCities took 1.2159347534179688e-05s
INFO | --- Analysis for braziliancities took 515.5626456737518s
Availability | SPARQL endpoint availability check for Bricklink took 2.533398389816284s
Availability | VoID file availability check for Bricklink took 1.5420811176300049s
Completeness | Calculation of interlinking completeness for Bricklink took 0.8949851989746094s
Reputation | Calculation of the PageRank for Bricklink took 0.020808696746826172s
Interlinking | Calculation of Degree of Connection for Bricklink took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bricklink took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Bricklink took 6.937980651855469e-05s
Believability | Calculation of trust value for Bricklink took 1.4066696166992188e-05s
INFO | --- Analysis for bricklink took 27.810937643051147s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.147196531295776s
Availability | VoID file availability check for British Museum Collection took 20.1920166015625s
Completeness | Calculation of interlinking completeness for British Museum Collection took 0.43334460258483887s
Reputation | Calculation of the PageRank for British Museum Collection took 0.02041029930114746s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for British Museum Collection took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 3.409385681152344e-05s
Believability | Calculation of trust value for British Museum Collection took 1.2159347534179688e-05s
INFO | --- Analysis for british-museum-collection took 73.23117351531982s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 8.630752563476562e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.00010657310485839844s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.6963047981262207s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.02251434326171875s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 4.458427429199219e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 1.1920928955078125e-05s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 3.223163366317749s
Availability | SPARQL endpoint availability check for French Plant Health Bulletins took 60.066710233688354s
Availability | VoID file availability check for French Plant Health Bulletins took 35.452394247055054s
Completeness | Calculation of interlinking completeness for French Plant Health Bulletins took 0.33479881286621094s
Reputation | Calculation of the PageRank for French Plant Health Bulletins took 0.02181529998779297s
Interlinking | Calculation of Degree of Connection for French Plant Health Bulletins took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for French Plant Health Bulletins took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for French Plant Health Bulletins took 4.553794860839844e-05s
Believability | Calculation of trust value for French Plant Health Bulletins took 1.2636184692382812e-05s
INFO | --- Analysis for bsv took 117.75954246520996s
Availability | SPARQL endpoint availability check for Bund Offener Haushalt took 9.1552734375e-05s
Availability | VoID file availability check for Bund Offener Haushalt took 0.15722370147705078s
Completeness | Calculation of interlinking completeness for Bund Offener Haushalt took 2.6903955936431885s
Reputation | Calculation of the PageRank for Bund Offener Haushalt took 0.021051645278930664s
Interlinking | Calculation of Degree of Connection for Bund Offener Haushalt took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bund Offener Haushalt took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Bund Offener Haushalt took 3.075599670410156e-05s
Believability | Calculation of trust value for Bund Offener Haushalt took 1.239776611328125e-05s
INFO | --- Analysis for bund-offener-haushalt took 11.164816617965698s
Availability | SPARQL endpoint availability check for BundestagNebeneinkuenfte took 0.0567014217376709s
Availability | VoID file availability check for BundestagNebeneinkuenfte took 0.0011327266693115234s
Completeness | Calculation of interlinking completeness for BundestagNebeneinkuenfte took 0.5580387115478516s
Reputation | Calculation of the PageRank for BundestagNebeneinkuenfte took 0.0210568904876709s
Interlinking | Calculation of Degree of Connection for BundestagNebeneinkuenfte took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BundestagNebeneinkuenfte took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for BundestagNebeneinkuenfte took 3.147125244140625e-05s
Believability | Calculation of trust value for BundestagNebeneinkuenfte took 6.29425048828125e-05s
INFO | --- Analysis for bundestagnebeneinkuenfte took 6.245851039886475s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 0.27508020401000977s
Availability | VoID file availability check for business.data.gov.uk took 0.1611628532409668s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 1.4672176837921143s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.02077770233154297s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 5.53131103515625e-05s
Believability | Calculation of trust value for business.data.gov.uk took 9.059906005859375e-06s
INFO | --- Analysis for business-data-gov-uk took 3.9679677486419678s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 0.6590044498443604s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.7151072025299072s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 2.1514053344726562s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 1.7687788009643555s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 0.4372522830963135s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 1.7459721565246582s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 29.897959232330322s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 0.3425111770629883s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.24088788032531738s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 0.3879268169403076s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 0.40159082412719727s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 0.3661355972290039s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 0.40924072265625s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 11.811551570892334s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 0.3783247470855713s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 0.3931276798248291s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 0.7455344200134277s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.36610960960388184s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 0.4328885078430176s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.40041565895080566s
Performance | Throughput check for Biblioteca Virtual Miguel de Cervantes took 11.01285171508789s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 8.58306884765625e-05s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 0.34813380241394043s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 0.3721156120300293s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.37439918518066406s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.3961448669433594s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 0.3953571319580078s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 0.5090377330780029s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 0.3627448081970215s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 2.852313280105591s
Interoperability | New vocabularies check for Biblioteca Virtual Miguel de Cervantes took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Biblioteca Virtual Miguel de Cervantes took 0.36624789237976074s
Accuracy | Check Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.48096776008605957s
Accuracy | Check Inverse Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.48607301712036133s
Accuracy | Check Empty annotation labels for Biblioteca Virtual Miguel de Cervantes took 0.8229522705078125s
Accuracy | Check White space in annotation for Biblioteca Virtual Miguel de Cervantes took 0.031394243240356445s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.02778482437133789s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 1.1380178928375244s
Consistency | Check Misplaced properties for Biblioteca Virtual Miguel de Cervantes took 1.5648236274719238s
Consistency | Misplaced classes for Biblioteca Virtual Miguel de Cervantes took 0.4570634365081787s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 2.2252190113067627s
Consistency | Check Invalid usage of undefined classes for Biblioteca Virtual Miguel de Cervantes took 1.2801744937896729s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 2.405338764190674s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.03194737434387207s
Conciseness | Check Intensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.3436903953552246s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 0.3664069175720215s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 1563.9426639080048s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 0.7447366714477539s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.023339509963989258s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 5.9604644775390625e-05s
Interoperability | Check the re-using of existing vocabs for Biblioteca Virtual Miguel de Cervantes took 1.9073486328125e-06s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes took 1.0967254638671875e-05s
INFO | --- Analysis for BVMC took 1776.5165691375732s
Availability | SPARQL endpoint availability check for Price changes due to cabbage imports took 8.749961853027344e-05s
Availability | VoID file availability check for Price changes due to cabbage imports took 3.8118984699249268s
Completeness | Calculation of interlinking completeness for Price changes due to cabbage imports took 0.37676095962524414s
Reputation | Calculation of the PageRank for Price changes due to cabbage imports took 0.021860122680664062s
Interlinking | Calculation of Degree of Connection for Price changes due to cabbage imports took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Price changes due to cabbage imports took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Price changes due to cabbage imports took 3.504753112792969e-05s
Believability | Calculation of trust value for Price changes due to cabbage imports took 1.3113021850585938e-05s
INFO | --- Analysis for cabbage took 19.512558698654175s
Availability | SPARQL endpoint availability check for cablegate took 1.806147813796997s
Availability | VoID file availability check for cablegate took 1.6123929023742676s
Completeness | Calculation of interlinking completeness for cablegate took 0.295243501663208s
Reputation | Calculation of the PageRank for cablegate took 0.02060389518737793s
Interlinking | Calculation of Degree of Connection for cablegate took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for cablegate took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for cablegate took 6.67572021484375e-05s
Believability | Calculation of trust value for cablegate took 1.2159347534179688e-05s
INFO | --- Analysis for cablegate took 18.750863790512085s
Availability | SPARQL endpoint availability check for Calames took 8.320808410644531e-05s
Availability | VoID file availability check for Calames took 1.2202904224395752s
Completeness | Calculation of interlinking completeness for Calames took 0.9359438419342041s
Reputation | Calculation of the PageRank for Calames took 0.02039504051208496s
Interlinking | Calculation of Degree of Connection for Calames took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Calames took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Calames took 3.457069396972656e-05s
Believability | Calculation of trust value for Calames took 1.239776611328125e-05s
INFO | --- Analysis for calames took 8.159078121185303s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.20687580108642578s
Availability | VoID file availability check for CaLiGraph took 0.23208403587341309s
Extra | Recovery of all triples for CaLiGraph took 1.5359382629394531s
Performance | Total latancy measurement for CaLiGraph took 0.46766161918640137s
Amount of data | Number of triples check for CaLiGraph took 6.40750527381897s
Interoperability | New terms check for CaLiGraph took 1.9861366748809814s
Versatility | Languages check for CaLiGraph took 61.62382197380066s
Interpretability | Number of blank nodes check for CaLiGraph took 0.1266317367553711s
Interpretability | RDF structures check for CaLiGraph took 0.2717254161834717s
Versatility | Serialization formats check for CaLiGraph took 0.28014278411865234s
Availability | RDF dump link check for CaLiGraph took 0.16126108169555664s
License | MR license check for CaLiGraph took 0.6370184421539307s
License | HR license check for CaLiGraph took 60.2639844417572s
Amount of data | Number of property check for CaLiGraph took 0.14134931564331055s
Understandability | Number of label check for CaLiGraph took 3.0335800647735596s
Understandability | URI regex check for CaLiGraph took 0.3411848545074463s
Understandability | Vocabs check for CaLiGraph took 0.1456918716430664s
Verifiability | Authors check for CaLiGraph took 0.18628239631652832s
Verifiability | Publishers check for CaLiGraph took 0.17953777313232422s
Performance | Throughput check for CaLiGraph took 10.621219635009766s
Amount of data | Check the number of entities for CaLiGraph took 0.014194250106811523s
Verifiability | Contribs. check for CaLiGraph took 0.14818954467773438s
Interlinking | sameAs chians check for CaLiGraph took 0.4533214569091797s
Interlinking | skos check for CaLiGraph took 0.150848388671875s
Interlinking | skos check for CaLiGraph took 0.104400634765625s
Timeliness | dataset update frequency check for CaLiGraph took 0.23119115829467773s
Currency | Creation date check for CaLiGraph took 0.1922435760498047s
Currency | Modification date check for CaLiGraph took 0.14580821990966797s
Rep.Conc. | URIs length for CaLiGraph took 43.12274384498596s
Interoperability | New vocabularies check for CaLiGraph took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.1216583251953125s
Accuracy | Check Functional Property for CaLiGraph took 0.20986342430114746s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.2075824737548828s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.4903438091278076s
Accuracy | Check White space in annotation for CaLiGraph took 0.02762126922607422s
Accuracy | Check Datatype consistency for CaLiGraph took 0.028115034103393555s
Consistency | Disjoint class check for CaLiGraph took 0.13907432556152344s
Consistency | Check Misplaced properties for CaLiGraph took 42.974228858947754s
Consistency | Misplaced classes for CaLiGraph took 0.3753325939178467s
Consistency | Check Ontology hijacking for CaLiGraph took 1.9179022312164307s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.2797119617462158s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 43.32063007354736s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.03253889083862305s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.4195249080657959s
Security | Sign check for CaLiGraph took 0.13018584251403809s
Availability | Check URIs Dereferenciability for CaLiGraph took 3.6822144985198975s
Completeness | Calculation of interlinking completeness for CaLiGraph took 1.0504214763641357s
Reputation | Calculation of the PageRank for CaLiGraph took 0.020494699478149414s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 3.4332275390625e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.1920928955078125e-06s
Believability | Calculation of trust value for CaLiGraph took 1.3113021850585938e-05s
INFO | --- Analysis for CaLiGraph took 1462.2964968681335s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.14319849014282227s
Availability | VoID file availability check for CaLiGraph took 0.24628257751464844s
Extra | Recovery of all triples for CaLiGraph took 1.4488780498504639s
Performance | Total latancy measurement for CaLiGraph took 0.4914529323577881s
Amount of data | Number of triples check for CaLiGraph took 5.888235569000244s
Interoperability | New terms check for CaLiGraph took 1.9377222061157227s
Versatility | Languages check for CaLiGraph took 60.69058346748352s
Interpretability | Number of blank nodes check for CaLiGraph took 0.12708401679992676s
Interpretability | RDF structures check for CaLiGraph took 0.15175724029541016s
Versatility | Serialization formats check for CaLiGraph took 0.12775421142578125s
Availability | RDF dump link check for CaLiGraph took 0.1244204044342041s
License | MR license check for CaLiGraph took 0.24745941162109375s
License | HR license check for CaLiGraph took 61.03017520904541s
Amount of data | Number of property check for CaLiGraph took 0.13972854614257812s
Understandability | Number of label check for CaLiGraph took 2.3177037239074707s
Understandability | URI regex check for CaLiGraph took 0.237640380859375s
Understandability | Vocabs check for CaLiGraph took 0.09447932243347168s
Verifiability | Authors check for CaLiGraph took 0.134049654006958s
Verifiability | Publishers check for CaLiGraph took 0.11373424530029297s
Performance | Throughput check for CaLiGraph took 10.623677968978882s
Amount of data | Check the number of entities for CaLiGraph took 0.016875028610229492s
Verifiability | Contribs. check for CaLiGraph took 0.09379768371582031s
Interlinking | sameAs chians check for CaLiGraph took 0.4774913787841797s
Interlinking | skos check for CaLiGraph took 0.13623547554016113s
Interlinking | skos check for CaLiGraph took 0.08453154563903809s
Timeliness | dataset update frequency check for CaLiGraph took 0.11912941932678223s
Currency | Creation date check for CaLiGraph took 0.14354968070983887s
Currency | Modification date check for CaLiGraph took 0.14846324920654297s
Rep.Conc. | URIs length for CaLiGraph took 43.38496422767639s
Interoperability | New vocabularies check for CaLiGraph took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.15258407592773438s
Accuracy | Check Functional Property for CaLiGraph took 0.1154177188873291s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.0932321548461914s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.4687325954437256s
Accuracy | Check White space in annotation for CaLiGraph took 0.027938127517700195s
Accuracy | Check Datatype consistency for CaLiGraph took 0.029468774795532227s
Consistency | Disjoint class check for CaLiGraph took 0.13912105560302734s
Consistency | Check Misplaced properties for CaLiGraph took 42.961777448654175s
Consistency | Misplaced classes for CaLiGraph took 0.4573404788970947s
Consistency | Check Ontology hijacking for CaLiGraph took 1.9043185710906982s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.310448169708252s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 43.83709239959717s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.0358424186706543s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.40090107917785645s
Security | Sign check for CaLiGraph took 0.1247105598449707s
Availability | Check URIs Dereferenciability for CaLiGraph took 3.639540433883667s
Completeness | Calculation of interlinking completeness for CaLiGraph took 1.5809266567230225s
Reputation | Calculation of the PageRank for CaLiGraph took 0.020978450775146484s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 7.43865966796875e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.430511474609375e-06s
Believability | Calculation of trust value for CaLiGraph took 8.106231689453125e-06s
INFO | --- Analysis for caligraph took 1462.912343263626s
Availability | SPARQL endpoint availability check for can-link took 0.74835205078125s
Availability | VoID file availability check for can-link took 0.5134451389312744s
Completeness | Calculation of interlinking completeness for can-link took 1.613539218902588s
Reputation | Calculation of the PageRank for can-link took 0.02105545997619629s
Interlinking | Calculation of Degree of Connection for can-link took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for can-link took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for can-link took 2.8848648071289062e-05s
Believability | Calculation of trust value for can-link took 1.1444091796875e-05s
INFO | --- Analysis for can-link took 12.39866328239441s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 0.06877636909484863s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.0005826950073242188s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.33229637145996094s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.020740509033203125s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 2.8371810913085938e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 1.1205673217773438e-05s
INFO | --- Analysis for cap-italy-rdf took 2.923495054244995s
Availability | SPARQL endpoint availability check for person took 8.416175842285156e-05s
Availability | VoID file availability check for person took 0.38420677185058594s
Completeness | Calculation of interlinking completeness for person took 1.022627592086792s
Reputation | Calculation of the PageRank for person took 0.021210432052612305s
Interlinking | Calculation of Degree of Connection for person took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for person took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for person took 2.86102294921875e-05s
Believability | Calculation of trust value for person took 1.1205673217773438e-05s
INFO | --- Analysis for card took 3.3170855045318604s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 8.535385131835938e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 0.00031304359436035156s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 0.38960886001586914s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.021748781204223633s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 3.910064697265625e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 1.1205673217773438e-05s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 3.9110217094421387s
Availability | SPARQL endpoint availability check for Catalogus Professorum Lipsiensis took 0.29169607162475586s
Availability | VoID file availability check for Catalogus Professorum Lipsiensis took 0.11138296127319336s
Completeness | Calculation of interlinking completeness for Catalogus Professorum Lipsiensis took 0.7713072299957275s
Reputation | Calculation of the PageRank for Catalogus Professorum Lipsiensis took 0.020772457122802734s
Interlinking | Calculation of Degree of Connection for Catalogus Professorum Lipsiensis took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Catalogus Professorum Lipsiensis took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Catalogus Professorum Lipsiensis took 2.8848648071289062e-05s
Believability | Calculation of trust value for Catalogus Professorum Lipsiensis took 7.867813110351562e-06s
INFO | --- Analysis for catalogus-professorum-lipsiensis took 5.5755720138549805s
Availability | SPARQL endpoint availability check for Norway catch records dataset @PSNC took 0.1705155372619629s
Availability | VoID file availability check for Norway catch records dataset @PSNC took 0.024784326553344727s
Completeness | Calculation of interlinking completeness for Norway catch records dataset @PSNC took 2.7656607627868652s
Reputation | Calculation of the PageRank for Norway catch records dataset @PSNC took 0.02053999900817871s
Interlinking | Calculation of Degree of Connection for Norway catch records dataset @PSNC took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Norway catch records dataset @PSNC took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Norway catch records dataset @PSNC took 3.2901763916015625e-05s
Believability | Calculation of trust value for Norway catch records dataset @PSNC took 1.3113021850585938e-05s
INFO | --- Analysis for Catch_Record_(2014-_2019) took 12.92128849029541s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 8.487701416015625e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.1974320411682129s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 3.3857312202453613s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.02150416374206543s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0009007453918457031s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.00011754035949707031s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 7.62939453125e-06s
INFO | --- Analysis for ce4r took 40.257365703582764s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4103052616119385s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4705343246459961s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 1.3529376983642578s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 0.9379079341888428s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.874230146408081s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 2.0143659114837646s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 58.16102480888367s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1620783805847168s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 58.159292459487915s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2093195915222168s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1863844394683838s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3520071506500244s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.24056267738342285s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1757824420928955s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3028748035430908s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.39128994941711426s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2054438591003418s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.309406042098999s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2335374355316162s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 11.02834177017212s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 3.6716461181640625e-05s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.7641415596008301s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1564621925354004s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.5594308376312256s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2025609016418457s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1776103973388672s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.5446052551269531s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1820690631866455s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 3.8839285373687744s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4957129955291748s
Accuracy | Check Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.4673476219177246s
Accuracy | Check Inverse Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.6396558284759521s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 2.3572824001312256s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.02938532829284668s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.02914571762084961s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3019430637359619s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 0.47933459281921387s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 1.9463460445404053s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 2.2702770233154297s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.6189327239990234s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.03285932540893555s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.2638382911682129s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2110750675201416s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 2728.029340028763s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 1.0795433521270752s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.020593881607055664s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 5.14984130859375e-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 8.106231689453125e-06s
INFO | --- Analysis for ceo took 3060.4856877326965s
Availability | SPARQL endpoint availability check for Charging Stations took 4.315376281738281e-05s
Availability | VoID file availability check for Charging Stations took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for Charging Stations took 0.3663907051086426s
Reputation | Calculation of the PageRank for Charging Stations took 0.021374940872192383s
Interlinking | Calculation of Degree of Connection for Charging Stations took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Charging Stations took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Charging Stations took 3.2901763916015625e-05s
Believability | Calculation of trust value for Charging Stations took 1.430511474609375e-05s
INFO | --- Analysis for charging-stations took 2.83657169342041s
Availability | SPARQL endpoint availability check for Chat Game corpus took 7.009506225585938e-05s
Availability | VoID file availability check for Chat Game corpus took 0.00019693374633789062s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 1.514035940170288s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.021321773529052734s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 3.409385681152344e-05s
Believability | Calculation of trust value for Chat Game corpus took 1.2636184692382812e-05s
INFO | --- Analysis for chat-game-corpus took 22.84188961982727s
Availability | SPARQL endpoint availability check for Chemical Entities of Biological Interest (ChEBI) took 1.7201108932495117s
Availability | VoID file availability check for Chemical Entities of Biological Interest (ChEBI) took 0.6468057632446289s
Completeness | Calculation of interlinking completeness for Chemical Entities of Biological Interest (ChEBI) took 0.45198488235473633s
Reputation | Calculation of the PageRank for Chemical Entities of Biological Interest (ChEBI) took 0.02331829071044922s
Interlinking | Calculation of Degree of Connection for Chemical Entities of Biological Interest (ChEBI) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Chemical Entities of Biological Interest (ChEBI) took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Chemical Entities of Biological Interest (ChEBI) took 3.528594970703125e-05s
Believability | Calculation of trust value for Chemical Entities of Biological Interest (ChEBI) took 1.2636184692382812e-05s
INFO | --- Analysis for chebi took 6.0610949993133545s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 4.291534423828125e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.5062224864959717s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 1.3607690334320068s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.02132892608642578s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 5.412101745605469e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 1.2159347534179688e-05s
INFO | --- Analysis for chem2bio2rdf took 6.399475574493408s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 0.5940699577331543s
Availability | VoID file availability check for ChEMBL RDF took 0.2422482967376709s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.34731078147888184s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.021132707595825195s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 5.316734313964844e-05s
Believability | Calculation of trust value for ChEMBL RDF took 1.2874603271484375e-05s
INFO | --- Analysis for chembl-rdf took 8.345319509506226s
Availability | SPARQL endpoint availability check for chemdb  dataset took 0.7920699119567871s
Availability | VoID file availability check for chemdb  dataset took 1.2304461002349854s
Extra | Recovery of all triples for chemdb  dataset took 4.981766700744629s
Performance | Total latancy measurement for chemdb  dataset took 2.4526162147521973s
Amount of data | Number of triples check for chemdb  dataset took 0.5616414546966553s
Interoperability | New terms check for chemdb  dataset took 3.4747965335845947s
Versatility | Languages check for chemdb  dataset took 27.497665882110596s
Interpretability | Number of blank nodes check for chemdb  dataset took 0.5214800834655762s
Interpretability | RDF structures check for chemdb  dataset took 0.5280511379241943s
Versatility | Serialization formats check for chemdb  dataset took 0.5324718952178955s
Availability | RDF dump link check for chemdb  dataset took 0.5089221000671387s
License | MR license check for chemdb  dataset took 0.5197329521179199s
License | HR license check for chemdb  dataset took 3.646622896194458s
Amount of data | Number of property check for chemdb  dataset took 0.5257337093353271s
Understandability | Number of label check for chemdb  dataset took 0.593618631362915s
Understandability | URI regex check for chemdb  dataset took 0.9722752571105957s
Understandability | Vocabs check for chemdb  dataset took 0.4765045642852783s
Verifiability | Authors check for chemdb  dataset took 0.48969602584838867s
Verifiability | Publishers check for chemdb  dataset took 0.48208117485046387s
Performance | Throughput check for chemdb  dataset took 14.087744951248169s
Amount of data | Check the number of entities for chemdb  dataset took 3.600120544433594e-05s
Verifiability | Contribs. check for chemdb  dataset took 0.49877476692199707s
Interlinking | sameAs chians check for chemdb  dataset took 0.5301976203918457s
Interlinking | skos check for chemdb  dataset took 0.5990796089172363s
Interlinking | skos check for chemdb  dataset took 0.4847855567932129s
Timeliness | dataset update frequency check for chemdb  dataset took 0.4855320453643799s
Currency | Creation date check for chemdb  dataset took 0.5190424919128418s
Currency | Modification date check for chemdb  dataset took 0.5195095539093018s
Rep.Conc. | URIs length for chemdb  dataset took 2.9774105548858643s
Interoperability | New vocabularies check for chemdb  dataset took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for chemdb  dataset took 0.5266048908233643s
Accuracy | Check Functional Property for chemdb  dataset took 0.56740403175354s
Accuracy | Check Inverse Functional Property for chemdb  dataset took 0.5427210330963135s
Accuracy | Check Empty annotation labels for chemdb  dataset took 2.278169631958008s
Accuracy | Check White space in annotation for chemdb  dataset took 0.03126788139343262s
Accuracy | Check Datatype consistency for chemdb  dataset took 0.034262657165527344s
Consistency | Disjoint class check for chemdb  dataset took 0.494873046875s
Consistency | Check Misplaced properties for chemdb  dataset took 1.3425188064575195s
Consistency | Misplaced classes for chemdb  dataset took 0.6205539703369141s
Consistency | Check Ontology hijacking for chemdb  dataset took 3.4560766220092773s
Consistency | Check Invalid usage of undefined classes for chemdb  dataset took 1.3436851501464844s
Consistency | Check Invalid usage of undefined properties for chemdb  dataset took 2.1744608879089355s
Conciseness | Check Extensional conciseness for chemdb  dataset took 0.036391496658325195s
Conciseness | Check Intensional conciseness for chemdb  dataset took 0.5281870365142822s
Security | Sign check for chemdb  dataset took 0.5284519195556641s
Availability | Check URIs Dereferenciability for chemdb  dataset took 2658.187264442444s
Completeness | Calculation of interlinking completeness for chemdb  dataset took 0.7363021373748779s
Reputation | Calculation of the PageRank for chemdb  dataset took 0.022496938705444336s
Interlinking | Calculation of Degree of Connection for chemdb  dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for chemdb  dataset took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for chemdb  dataset took 6.961822509765625e-05s
Interoperability | Check the re-using of existing vocabs for chemdb  dataset took 1.1920928955078125e-06s
Believability | Calculation of trust value for chemdb  dataset took 1.621246337890625e-05s
INFO | --- Analysis for chemdb-basicInfo took 5575.815472364426s
Availability | SPARQL endpoint availability check for chemdb estimated properties dataset took 0.5858604907989502s
Availability | VoID file availability check for chemdb estimated properties dataset took 1.645599126815796s
Extra | Recovery of all triples for chemdb estimated properties dataset took 17.188652276992798s
Performance | Total latancy measurement for chemdb estimated properties dataset took 2.7853448390960693s
Amount of data | Number of triples check for chemdb estimated properties dataset took 0.6584649085998535s
Interoperability | New terms check for chemdb estimated properties dataset took 6.808064699172974s
Versatility | Languages check for chemdb estimated properties dataset took 28.04788565635681s
Interpretability | Number of blank nodes check for chemdb estimated properties dataset took 0.5618278980255127s
Interpretability | RDF structures check for chemdb estimated properties dataset took 0.5859735012054443s
Versatility | Serialization formats check for chemdb estimated properties dataset took 0.6174848079681396s
Availability | RDF dump link check for chemdb estimated properties dataset took 0.5657939910888672s
License | MR license check for chemdb estimated properties dataset took 0.6052627563476562s
License | HR license check for chemdb estimated properties dataset took 3.660322427749634s
Amount of data | Number of property check for chemdb estimated properties dataset took 0.6025080680847168s
Understandability | Number of label check for chemdb estimated properties dataset took 0.6501798629760742s
Understandability | URI regex check for chemdb estimated properties dataset took 1.1466877460479736s
Understandability | Vocabs check for chemdb estimated properties dataset took 0.58154296875s
Verifiability | Authors check for chemdb estimated properties dataset took 0.623523473739624s
Verifiability | Publishers check for chemdb estimated properties dataset took 0.6215360164642334s
Performance | Throughput check for chemdb estimated properties dataset took 11.983448266983032s
Amount of data | Check the number of entities for chemdb estimated properties dataset took 0.00012636184692382812s
Verifiability | Contribs. check for chemdb estimated properties dataset took 0.5412940979003906s
Interlinking | sameAs chians check for chemdb estimated properties dataset took 0.5317990779876709s
Interlinking | skos check for chemdb estimated properties dataset took 0.6567187309265137s
Interlinking | skos check for chemdb estimated properties dataset took 0.49524521827697754s
Timeliness | dataset update frequency check for chemdb estimated properties dataset took 0.5392868518829346s
Currency | Creation date check for chemdb estimated properties dataset took 0.5862233638763428s
Currency | Modification date check for chemdb estimated properties dataset took 0.5667581558227539s
Rep.Conc. | URIs length for chemdb estimated properties dataset took 5.894015073776245s
Interoperability | New vocabularies check for chemdb estimated properties dataset took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for chemdb estimated properties dataset took 0.648608922958374s
Accuracy | Check Functional Property for chemdb estimated properties dataset took 0.7897698879241943s
Accuracy | Check Inverse Functional Property for chemdb estimated properties dataset took 0.7442545890808105s
Accuracy | Check Empty annotation labels for chemdb estimated properties dataset took 5.690651893615723s
Accuracy | Check White space in annotation for chemdb estimated properties dataset took 0.03140974044799805s
Accuracy | Check Datatype consistency for chemdb estimated properties dataset took 0.03295135498046875s
Consistency | Disjoint class check for chemdb estimated properties dataset took 0.5359892845153809s
Consistency | Check Misplaced properties for chemdb estimated properties dataset took 1.5211358070373535s
Consistency | Misplaced classes for chemdb estimated properties dataset took 0.6481833457946777s
Consistency | Check Ontology hijacking for chemdb estimated properties dataset took 6.9046711921691895s
Consistency | Check Invalid usage of undefined classes for chemdb estimated properties dataset took 1.2824416160583496s
Consistency | Check Invalid usage of undefined properties for chemdb estimated properties dataset took 2.2733466625213623s
Conciseness | Check Extensional conciseness for chemdb estimated properties dataset took 0.03344273567199707s
Conciseness | Check Intensional conciseness for chemdb estimated properties dataset took 0.7346374988555908s
Security | Sign check for chemdb estimated properties dataset took 0.6143589019775391s
Availability | Check URIs Dereferenciability for chemdb estimated properties dataset took 3004.8565258979797s
Completeness | Calculation of interlinking completeness for chemdb estimated properties dataset took 0.8059725761413574s
Reputation | Calculation of the PageRank for chemdb estimated properties dataset took 0.02132272720336914s
Interlinking | Calculation of Degree of Connection for chemdb estimated properties dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for chemdb estimated properties dataset took 0.0008242130279541016s
Interlinking | Calculation of Clustering coefficient for chemdb estimated properties dataset took 5.078315734863281e-05s
Interoperability | Check the re-using of existing vocabs for chemdb estimated properties dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for chemdb estimated properties dataset took 1.2636184692382812e-05s
INFO | --- Analysis for chemdb-estimatedProperties took 5953.045385837555s
Availability | SPARQL endpoint availability check for chemdb phase transition dataset took 0.5249345302581787s
Availability | VoID file availability check for chemdb phase transition dataset took 1.3660292625427246s
Extra | Recovery of all triples for chemdb phase transition dataset took 13.36490511894226s
Performance | Total latancy measurement for chemdb phase transition dataset took 2.532935857772827s
Amount of data | Number of triples check for chemdb phase transition dataset took 0.570913553237915s
Interoperability | New terms check for chemdb phase transition dataset took 3.997575283050537s
Versatility | Languages check for chemdb phase transition dataset took 27.78932213783264s
Interpretability | Number of blank nodes check for chemdb phase transition dataset took 0.5162415504455566s
Interpretability | RDF structures check for chemdb phase transition dataset took 0.5289998054504395s
Versatility | Serialization formats check for chemdb phase transition dataset took 0.5350651741027832s
Availability | RDF dump link check for chemdb phase transition dataset took 0.5089435577392578s
License | MR license check for chemdb phase transition dataset took 0.5213661193847656s
License | HR license check for chemdb phase transition dataset took 3.649536609649658s
Amount of data | Number of property check for chemdb phase transition dataset took 0.5345525741577148s
Understandability | Number of label check for chemdb phase transition dataset took 0.592266321182251s
Understandability | URI regex check for chemdb phase transition dataset took 1.0214011669158936s
Understandability | Vocabs check for chemdb phase transition dataset took 0.49498534202575684s
Verifiability | Authors check for chemdb phase transition dataset took 0.5157058238983154s
Verifiability | Publishers check for chemdb phase transition dataset took 0.5062553882598877s
Performance | Throughput check for chemdb phase transition dataset took 14.295547246932983s
Amount of data | Check the number of entities for chemdb phase transition dataset took 8.20159912109375e-05s
Verifiability | Contribs. check for chemdb phase transition dataset took 0.506563663482666s
Interlinking | sameAs chians check for chemdb phase transition dataset took 0.5321669578552246s
Interlinking | skos check for chemdb phase transition dataset took 0.6234879493713379s
Interlinking | skos check for chemdb phase transition dataset took 0.47907090187072754s
Timeliness | dataset update frequency check for chemdb phase transition dataset took 0.4857447147369385s
Currency | Creation date check for chemdb phase transition dataset took 0.5310802459716797s
Currency | Modification date check for chemdb phase transition dataset took 0.5085489749908447s
Rep.Conc. | URIs length for chemdb phase transition dataset took 3.70652174949646s
Interoperability | New vocabularies check for chemdb phase transition dataset took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for chemdb phase transition dataset took 0.508087158203125s
Accuracy | Check Functional Property for chemdb phase transition dataset took 0.6277332305908203s
Accuracy | Check Inverse Functional Property for chemdb phase transition dataset took 0.5977964401245117s
Accuracy | Check Empty annotation labels for chemdb phase transition dataset took 3.1165895462036133s
Accuracy | Check White space in annotation for chemdb phase transition dataset took 0.031112194061279297s
Accuracy | Check Datatype consistency for chemdb phase transition dataset took 0.034001827239990234s
Consistency | Disjoint class check for chemdb phase transition dataset took 0.5069961547851562s
Consistency | Check Misplaced properties for chemdb phase transition dataset took 1.342010498046875s
Consistency | Misplaced classes for chemdb phase transition dataset took 0.6088752746582031s
Consistency | Check Ontology hijacking for chemdb phase transition dataset took 3.8882720470428467s
Consistency | Check Invalid usage of undefined classes for chemdb phase transition dataset took 1.309804916381836s
Consistency | Check Invalid usage of undefined properties for chemdb phase transition dataset took 2.1463241577148438s
Conciseness | Check Extensional conciseness for chemdb phase transition dataset took 0.03309750556945801s
Conciseness | Check Intensional conciseness for chemdb phase transition dataset took 0.5325214862823486s
Security | Sign check for chemdb phase transition dataset took 0.5164608955383301s
Availability | Check URIs Dereferenciability for chemdb phase transition dataset took 2670.6573281288147s
Completeness | Calculation of interlinking completeness for chemdb phase transition dataset took 1.0396389961242676s
Reputation | Calculation of the PageRank for chemdb phase transition dataset took 0.02284407615661621s
Interlinking | Calculation of Degree of Connection for chemdb phase transition dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for chemdb phase transition dataset took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for chemdb phase transition dataset took 4.7206878662109375e-05s
Interoperability | Check the re-using of existing vocabs for chemdb phase transition dataset took 1.1920928955078125e-06s
Believability | Calculation of trust value for chemdb phase transition dataset took 1.1920928955078125e-05s
INFO | --- Analysis for chemdb-phaseTransition took 5589.99236869812s
Availability | SPARQL endpoint availability check for chemdb thermochemistry dataset took 0.5144288539886475s
Availability | VoID file availability check for chemdb thermochemistry dataset took 1.425809383392334s
Extra | Recovery of all triples for chemdb thermochemistry dataset took 13.325284481048584s
Performance | Total latancy measurement for chemdb thermochemistry dataset took 2.461249351501465s
Amount of data | Number of triples check for chemdb thermochemistry dataset took 0.5689055919647217s
Interoperability | New terms check for chemdb thermochemistry dataset took 3.9122564792633057s
Versatility | Languages check for chemdb thermochemistry dataset took 27.964296102523804s
Interpretability | Number of blank nodes check for chemdb thermochemistry dataset took 0.5142190456390381s
Interpretability | RDF structures check for chemdb thermochemistry dataset took 0.5343055725097656s
Versatility | Serialization formats check for chemdb thermochemistry dataset took 0.5309202671051025s
Availability | RDF dump link check for chemdb thermochemistry dataset took 0.4986846446990967s
License | MR license check for chemdb thermochemistry dataset took 0.5219423770904541s
License | HR license check for chemdb thermochemistry dataset took 3.5952608585357666s
Amount of data | Number of property check for chemdb thermochemistry dataset took 0.5225157737731934s
Understandability | Number of label check for chemdb thermochemistry dataset took 0.5746088027954102s
Understandability | URI regex check for chemdb thermochemistry dataset took 1.0160102844238281s
Understandability | Vocabs check for chemdb thermochemistry dataset took 0.4893336296081543s
Verifiability | Authors check for chemdb thermochemistry dataset took 0.5087506771087646s
Verifiability | Publishers check for chemdb thermochemistry dataset took 0.5030043125152588s
Performance | Throughput check for chemdb thermochemistry dataset took 14.564470529556274s
Amount of data | Check the number of entities for chemdb thermochemistry dataset took 7.963180541992188e-05s
Verifiability | Contribs. check for chemdb thermochemistry dataset took 0.47925686836242676s
Interlinking | sameAs chians check for chemdb thermochemistry dataset took 0.5202150344848633s
Interlinking | skos check for chemdb thermochemistry dataset took 0.6176676750183105s
Interlinking | skos check for chemdb thermochemistry dataset took 0.49213337898254395s
Timeliness | dataset update frequency check for chemdb thermochemistry dataset took 0.5028693675994873s
Currency | Creation date check for chemdb thermochemistry dataset took 0.5289425849914551s
Currency | Modification date check for chemdb thermochemistry dataset took 0.5278074741363525s
Rep.Conc. | URIs length for chemdb thermochemistry dataset took 3.8511998653411865s
Interoperability | New vocabularies check for chemdb thermochemistry dataset took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for chemdb thermochemistry dataset took 0.5262291431427002s
Accuracy | Check Functional Property for chemdb thermochemistry dataset took 0.6004533767700195s
Accuracy | Check Inverse Functional Property for chemdb thermochemistry dataset took 0.5692243576049805s
Accuracy | Check Empty annotation labels for chemdb thermochemistry dataset took 2.8194491863250732s
Accuracy | Check White space in annotation for chemdb thermochemistry dataset took 0.03170204162597656s
Accuracy | Check Datatype consistency for chemdb thermochemistry dataset took 0.03508758544921875s
Consistency | Disjoint class check for chemdb thermochemistry dataset took 0.5156309604644775s
Consistency | Check Misplaced properties for chemdb thermochemistry dataset took 1.7850399017333984s
Consistency | Misplaced classes for chemdb thermochemistry dataset took 0.6129212379455566s
Consistency | Check Ontology hijacking for chemdb thermochemistry dataset took 4.08429741859436s
Consistency | Check Invalid usage of undefined classes for chemdb thermochemistry dataset took 1.2748606204986572s
Consistency | Check Invalid usage of undefined properties for chemdb thermochemistry dataset took 2.1313483715057373s
Conciseness | Check Extensional conciseness for chemdb thermochemistry dataset took 0.033480167388916016s
Conciseness | Check Intensional conciseness for chemdb thermochemistry dataset took 0.5268635749816895s
Security | Sign check for chemdb thermochemistry dataset took 0.527442216873169s
Availability | Check URIs Dereferenciability for chemdb thermochemistry dataset took 2652.0669276714325s
Completeness | Calculation of interlinking completeness for chemdb thermochemistry dataset took 0.6816563606262207s
Reputation | Calculation of the PageRank for chemdb thermochemistry dataset took 0.021548032760620117s
Interlinking | Calculation of Degree of Connection for chemdb thermochemistry dataset took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for chemdb thermochemistry dataset took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for chemdb thermochemistry dataset took 7.200241088867188e-05s
Interoperability | Check the re-using of existing vocabs for chemdb thermochemistry dataset took 1.1920928955078125e-06s
Believability | Calculation of trust value for chemdb thermochemistry dataset took 1.1682510375976562e-05s
INFO | --- Analysis for chemdb-thermochemistry took 5600.518673419952s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 4.0531158447265625e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.8861072063446045s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 1.0052745342254639s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.021178483963012695s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0007951259613037109s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 4.458427429199219e-05s
Believability | Calculation of trust value for ChemPedia RDF took 1.2159347534179688e-05s
INFO | --- Analysis for chempedia-rdf took 11.614720582962036s
Availability | SPARQL endpoint availability check for Chiman Maru took 4.291534423828125e-05s
Availability | VoID file availability check for Chiman Maru took 0.055097103118896484s
Completeness | Calculation of interlinking completeness for Chiman Maru took 0.38013219833374023s
Reputation | Calculation of the PageRank for Chiman Maru took 0.021654367446899414s
Interlinking | Calculation of Degree of Connection for Chiman Maru took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Chiman Maru took 0.0007946491241455078s
Interlinking | Calculation of Clustering coefficient for Chiman Maru took 3.147125244140625e-05s
Believability | Calculation of trust value for Chiman Maru took 1.1682510375976562e-05s
INFO | --- Analysis for ChimanMaru_Entrepreneur took 4.981211423873901s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 392.6754128932953s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 261.30422711372375s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 0.7937266826629639s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.022600173950195312s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0010223388671875s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 5.1975250244140625e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 7.867813110351562e-06s
INFO | --- Analysis for Chinese_Red_Classic_Song_Linked_Data_Dataset took 795.2314772605896s
Availability | SPARQL endpoint availability check for Chronicling America took 8.654594421386719e-05s
Availability | VoID file availability check for Chronicling America took 0.9048149585723877s
Completeness | Calculation of interlinking completeness for Chronicling America took 1.0497910976409912s
Reputation | Calculation of the PageRank for Chronicling America took 0.020822525024414062s
Interlinking | Calculation of Degree of Connection for Chronicling America took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Chronicling America took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 0.00010037422180175781s
Believability | Calculation of trust value for Chronicling America took 1.2159347534179688e-05s
INFO | --- Analysis for chronicling-america took 128.32339334487915s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.7079062461853027s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 1.1886446475982666s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 79.480477809906s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.5718960762023926s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 1.2905519008636475s
Interoperability | New terms check for Cultural Heritage Thesaurus took 1.7351369857788086s
Versatility | Languages check for Cultural Heritage Thesaurus took 2.1705076694488525s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 1.060361623764038s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.2900404930114746s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.2679166793823242s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 7.633063554763794s
License | MR license check for Cultural Heritage Thesaurus took 0.3571314811706543s
License | HR license check for Cultural Heritage Thesaurus took 0.4413337707519531s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.3255596160888672s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.42906904220581055s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.5754456520080566s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.2936725616455078s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.4617140293121338s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.3048529624938965s
Performance | Throughput check for Cultural Heritage Thesaurus took 11.961888074874878s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 9.679794311523438e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.30801892280578613s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.2688167095184326s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.2972397804260254s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.29715991020202637s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.3205718994140625s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.3500082492828369s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.29402661323547363s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 23.029461145401s
Interoperability | New vocabularies check for Cultural Heritage Thesaurus took 0.9130284786224365s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.27446651458740234s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.3079524040222168s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.2863123416900635s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 5.806249618530273s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.21855926513671875s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.3179333209991455s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 1.6138222217559814s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.28398704528808594s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 6.15109658241272s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 2.8549599647521973s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.0001704692840576172s
Security | Sign check for Cultural Heritage Thesaurus took 0.39873838424682617s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 1.3046975135803223s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.02163529396057129s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 8.988380432128906e-05s
Interoperability | Check the re-using of existing vocabs for Cultural Heritage Thesaurus took 0.48917150497436523s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 1.1920928955078125e-05s
INFO | --- Analysis for cht took 202.1173393726349s
Availability | SPARQL endpoint availability check for ciard-ring took 8.678436279296875e-05s
Availability | VoID file availability check for ciard-ring took 0.0006954669952392578s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.30806422233581543s
Reputation | Calculation of the PageRank for ciard-ring took 0.022069692611694336s
Interlinking | Calculation of Degree of Connection for ciard-ring took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for ciard-ring took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 5.269050598144531e-05s
Believability | Calculation of trust value for ciard-ring took 1.239776611328125e-05s
INFO | --- Analysis for ciard-ring took 13.090424299240112s
Availability | SPARQL endpoint availability check for Cine Figure took 8.487701416015625e-05s
Availability | VoID file availability check for Cine Figure took 0.8705291748046875s
Completeness | Calculation of interlinking completeness for Cine Figure took 1.3860089778900146s
Reputation | Calculation of the PageRank for Cine Figure took 0.02064824104309082s
Interlinking | Calculation of Degree of Connection for Cine Figure took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cine Figure took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Cine Figure took 4.601478576660156e-05s
Believability | Calculation of trust value for Cine Figure took 7.176399230957031e-05s
INFO | --- Analysis for Cine_Figure took 12.789127826690674s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 0.46549153327941895s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.2385411262512207s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.32423830032348633s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.020622730255126953s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 4.267692565917969e-05s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 1.2159347534179688e-05s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 8.61768102645874s
Availability | SPARQL endpoint availability check for CIPFA took 0.000125885009765625s
Availability | VoID file availability check for CIPFA took 0.11146235466003418s
Completeness | Calculation of interlinking completeness for CIPFA took 1.1533808708190918s
Reputation | Calculation of the PageRank for CIPFA took 0.021424293518066406s
Interlinking | Calculation of Degree of Connection for CIPFA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CIPFA took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for CIPFA took 3.7670135498046875e-05s
Believability | Calculation of trust value for CIPFA took 9.059906005859375e-06s
INFO | --- Analysis for cipfa took 5.982285737991333s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 60.04992890357971s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 40.03327250480652s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.6371862888336182s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.0266115665435791s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 3.147125244140625e-05s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.0012083053588867188s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.0004677772521972656s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 1.1920928955078125e-05s
INFO | --- Analysis for ckan took 263.4761915206909s
Availability | SPARQL endpoint availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.6573548316955566s
Availability | VoID file availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.2515449523925781s
Completeness | Calculation of interlinking completeness for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.47339344024658203s
Reputation | Calculation of the PageRank for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.020879030227661133s
Interlinking | Calculation of Degree of Connection for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 3.838539123535156e-05s
Interoperability | Check the re-using of existing vocabs for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 3.814697265625e-06s
Believability | Calculation of trust value for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.1920928955078125e-05s
INFO | --- Analysis for CLaSSES took 4.435100555419922s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 8.416175842285156e-05s
Availability | VoID file availability check for Temples of the Classical World took 7.014323949813843s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 0.8188490867614746s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.02113652229309082s
Interlinking | Calculation of Degree of Connection for Temples of the Classical World took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Temples of the Classical World took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 2.9087066650390625e-05s
Believability | Calculation of trust value for Temples of the Classical World took 5.9604644775390625e-06s
INFO | --- Analysis for classical_temples took 12.30815052986145s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 1.0449185371398926s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.30180954933166504s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 0.36063265800476074s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.021226167678833008s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 8.20159912109375e-05s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 8.344650268554688e-06s
INFO | --- Analysis for clean-energy-data-reegle took 4.9549241065979s
Availability | SPARQL endpoint availability check for CLLD-afbo took 8.463859558105469e-05s
Availability | VoID file availability check for CLLD-afbo took 0.28782081604003906s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.34264564514160156s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.022356510162353516s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 7.605552673339844e-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.1920928955078125e-05s
INFO | --- Analysis for clld-afbo took 4.502193450927734s
Availability | SPARQL endpoint availability check for CLLD-APICS took 8.749961853027344e-05s
Availability | VoID file availability check for CLLD-APICS took 0.34778738021850586s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 0.3163163661956787s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.023648500442504883s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.001226186752319336s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 0.00010323524475097656s
Interoperability | Check the re-using of existing vocabs for CLLD-APICS took 2.384185791015625e-06s
Believability | Calculation of trust value for CLLD-APICS took 1.239776611328125e-05s
INFO | --- Analysis for clld-apics took 4.741770267486572s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 8.463859558105469e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.28107619285583496s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.41901135444641113s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.020933866500854492s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 3.695487976074219e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-EWAVE took 2.1457672119140625e-06s
Believability | Calculation of trust value for CLLD-EWAVE took 1.1682510375976562e-05s
INFO | --- Analysis for clld-ewave took 4.00426983833313s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 8.96453857421875e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.29184961318969727s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 1.1741454601287842s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.02068781852722168s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 0.00010037422180175781s
Interoperability | Check the re-using of existing vocabs for CLLD-GLOTTOLOG took 2.384185791015625e-06s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 1.1444091796875e-05s
INFO | --- Analysis for clld-glottolog took 4.7510621547698975s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 8.487701416015625e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.3023378849029541s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.31078338623046875s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.020441770553588867s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 7.700920104980469e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-PHOIBLE took 2.1457672119140625e-06s
Believability | Calculation of trust value for CLLD-PHOIBLE took 1.2159347534179688e-05s
INFO | --- Analysis for clld-phoible took 3.95261812210083s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 8.130073547363281e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.27516746520996094s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 0.4005157947540283s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.020447254180908203s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 7.534027099609375e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-SAILS took 2.1457672119140625e-06s
Believability | Calculation of trust value for CLLD-SAILS took 1.1205673217773438e-05s
INFO | --- Analysis for clld-sails took 4.379768371582031s
Availability | SPARQL endpoint availability check for CLLD-WALS took 4.00543212890625e-05s
Availability | VoID file availability check for CLLD-WALS took 0.32538771629333496s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.29489970207214355s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.020841121673583984s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 8.20159912109375e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-WALS took 2.1457672119140625e-06s
Believability | Calculation of trust value for CLLD-WALS took 1.1920928955078125e-05s
INFO | --- Analysis for clld-wals took 5.159504652023315s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 4.291534423828125e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.5689718723297119s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 0.3650999069213867s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.021656036376953125s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 7.748603820800781e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-WOLD took 2.86102294921875e-06s
Believability | Calculation of trust value for CLLD-WOLD took 1.0728836059570312e-05s
INFO | --- Analysis for clld-wold took 4.394078493118286s
Availability | SPARQL endpoint availability check for COD inventory took 0.27879786491394043s
Availability | VoID file availability check for COD inventory took 0.00020122528076171875s
Completeness | Calculation of interlinking completeness for COD inventory took 0.7654554843902588s
Reputation | Calculation of the PageRank for COD inventory took 0.020525455474853516s
Interlinking | Calculation of Degree of Connection for COD inventory took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for COD inventory took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for COD inventory took 3.218650817871094e-05s
Believability | Calculation of trust value for COD inventory took 1.1444091796875e-05s
INFO | --- Analysis for cod-inventory took 3.2777347564697266s
Availability | SPARQL endpoint availability check for Cooperation Databank took 0.1652669906616211s
Availability | VoID file availability check for Cooperation Databank took 0.0064716339111328125s
Completeness | Calculation of interlinking completeness for Cooperation Databank took 1.545173168182373s
Reputation | Calculation of the PageRank for Cooperation Databank took 0.023180484771728516s
Interlinking | Calculation of Degree of Connection for Cooperation Databank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cooperation Databank took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Cooperation Databank took 3.552436828613281e-05s
Believability | Calculation of trust value for Cooperation Databank took 1.1205673217773438e-05s
INFO | --- Analysis for CoDa took 4.260855436325073s
Availability | SPARQL endpoint availability check for CODE Endpoint took 261.72701239585876s
Availability | VoID file availability check for CODE Endpoint took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for CODE Endpoint took 0.613344669342041s
Reputation | Calculation of the PageRank for CODE Endpoint took 0.021322965621948242s
Interlinking | Calculation of Degree of Connection for CODE Endpoint took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for CODE Endpoint took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for CODE Endpoint took 4.6253204345703125e-05s
Believability | Calculation of trust value for CODE Endpoint took 1.1682510375976562e-05s
INFO | --- Analysis for code-endpoint took 395.3239850997925s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 0.9502592086791992s
Availability | VoID file availability check for OpenUpLabs COINS took 0.9621586799621582s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.33181118965148926s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.02399444580078125s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0011370182037353516s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 4.172325134277344e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 8.58306884765625e-06s
INFO | --- Analysis for coins-openuplabs took 4.608962297439575s
Availability | SPARQL endpoint availability check for Catalogue of Life in China 2003 Edition took 3.511216163635254s
Availability | VoID file availability check for Catalogue of Life in China 2003 Edition took 0.966742992401123s
Completeness | Calculation of interlinking completeness for Catalogue of Life in China 2003 Edition took 0.36371302604675293s
Reputation | Calculation of the PageRank for Catalogue of Life in China 2003 Edition took 0.020905494689941406s
Interlinking | Calculation of Degree of Connection for Catalogue of Life in China 2003 Edition took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Catalogue of Life in China 2003 Edition took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Catalogue of Life in China 2003 Edition took 8.368492126464844e-05s
Believability | Calculation of trust value for Catalogue of Life in China 2003 Edition took 1.1444091796875e-05s
INFO | --- Analysis for CoLChina_sp2000 took 7.373687744140625s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 0.0706644058227539s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.014817476272583008s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 0.32161474227905273s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.02098989486694336s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 3.695487976074219e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 1.0967254638671875e-05s
INFO | --- Analysis for colinda took 1.918328046798706s
Availability | SPARQL endpoint availability check for CN  2012 took 29.55703639984131s
Availability | VoID file availability check for CN  2012 took 2.2914280891418457s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.6476106643676758s
Reputation | Calculation of the PageRank for CN  2012 took 0.022333621978759766s
Interlinking | Calculation of Degree of Connection for CN  2012 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CN  2012 took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 4.458427429199219e-05s
Believability | Calculation of trust value for CN  2012 took 9.059906005859375e-06s
INFO | --- Analysis for combined-nomenclature-2012 took 106.66158819198608s
Availability | SPARQL endpoint availability check for Comments on Literature in Literature (CoLiL) took 2.5763304233551025s
Availability | VoID file availability check for Comments on Literature in Literature (CoLiL) took 0.0003376007080078125s
Extra | Recovery of all triples for Comments on Literature in Literature (CoLiL) took 136.55508756637573s
Performance | Total latancy measurement for Comments on Literature in Literature (CoLiL) took 8.36320161819458s
Amount of data | Number of triples check for Comments on Literature in Literature (CoLiL) took 301.4635741710663s
Interoperability | New terms check for Comments on Literature in Literature (CoLiL) took 132.37100791931152s
Versatility | Languages check for Comments on Literature in Literature (CoLiL) took 301.4491639137268s
Interpretability | Number of blank nodes check for Comments on Literature in Literature (CoLiL) took 111.02068448066711s
Security | Check HTTPS for Comments on Literature in Literature (CoLiL) took 1.130706787109375s
Interpretability | RDF structures check for Comments on Literature in Literature (CoLiL) took 1.8311893939971924s
Versatility | Serialization formats check for Comments on Literature in Literature (CoLiL) took 1.700878381729126s
Availability | RDF dump link check for Comments on Literature in Literature (CoLiL) took 1.6989860534667969s
License | MR license check for Comments on Literature in Literature (CoLiL) took 1.734649658203125s
License | HR license check for Comments on Literature in Literature (CoLiL) took 1.8411402702331543s
Amount of data | Number of property check for Comments on Literature in Literature (CoLiL) took 1.693532943725586s
Understandability | Number of label check for Comments on Literature in Literature (CoLiL) took 2.0393896102905273s
Understandability | URI regex check for Comments on Literature in Literature (CoLiL) took 3.547020673751831s
Understandability | Vocabs check for Comments on Literature in Literature (CoLiL) took 1.721604585647583s
Verifiability | Authors check for Comments on Literature in Literature (CoLiL) took 1.745384931564331s
Verifiability | Publishers check for Comments on Literature in Literature (CoLiL) took 1.7459611892700195s
Performance | Throughput check for Comments on Literature in Literature (CoLiL) took 17.555092334747314s
Amount of data | Check the number of entities for Comments on Literature in Literature (CoLiL) took 0.0006182193756103516s
Verifiability | Contribs. check for Comments on Literature in Literature (CoLiL) took 1.83042311668396s
Interlinking | sameAs chians check for Comments on Literature in Literature (CoLiL) took 1.6652460098266602s
Interlinking | skos check for Comments on Literature in Literature (CoLiL) took 1.9540154933929443s
Interlinking | skos check for Comments on Literature in Literature (CoLiL) took 1.6857550144195557s
Timeliness | dataset update frequency check for Comments on Literature in Literature (CoLiL) took 1.7114999294281006s
Currency | Creation date check for Comments on Literature in Literature (CoLiL) took 1.8886449337005615s
Currency | Modification date check for Comments on Literature in Literature (CoLiL) took 1.695556402206421s
Rep.Conc. | URIs length for Comments on Literature in Literature (CoLiL) took 471.70361828804016s
Interoperability | New vocabularies check for Comments on Literature in Literature (CoLiL) took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for Comments on Literature in Literature (CoLiL) took 1.6901752948760986s
Accuracy | Check Empty annotation labels for Comments on Literature in Literature (CoLiL) took 3.4084489345550537s
Accuracy | Check White space in annotation for Comments on Literature in Literature (CoLiL) took 0.0021326541900634766s
Accuracy | Check Datatype consistency for Comments on Literature in Literature (CoLiL) took 2.6719300746917725s
Consistency | Disjoint class check for Comments on Literature in Literature (CoLiL) took 1.6860413551330566s
Consistency | Check Misplaced properties for Comments on Literature in Literature (CoLiL) took 303.1634154319763s
Consistency | Misplaced classes for Comments on Literature in Literature (CoLiL) took 10.766076803207397s
Consistency | Check Ontology hijacking for Comments on Literature in Literature (CoLiL) took 34.273223876953125s
Consistency | Check Invalid usage of undefined classes for Comments on Literature in Literature (CoLiL) took 1.541107177734375s
Consistency | Check Invalid usage of undefined properties for Comments on Literature in Literature (CoLiL) took 302.75009775161743s
Conciseness | Check Extensional conciseness for Comments on Literature in Literature (CoLiL) took 2.8004188537597656s
Conciseness | Check Intensional conciseness for Comments on Literature in Literature (CoLiL) took 1.9961724281311035s
Security | Sign check for Comments on Literature in Literature (CoLiL) took 1.669445514678955s
Availability | Check URIs Dereferenciability for Comments on Literature in Literature (CoLiL) took 3.779332160949707s
Completeness | Calculation of interlinking completeness for Comments on Literature in Literature (CoLiL) took 1.5365793704986572s
Reputation | Calculation of the PageRank for Comments on Literature in Literature (CoLiL) took 0.02336883544921875s
Interlinking | Calculation of Degree of Connection for Comments on Literature in Literature (CoLiL) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Comments on Literature in Literature (CoLiL) took 0.000682830810546875s
Interlinking | Calculation of Clustering coefficient for Comments on Literature in Literature (CoLiL) took 4.100799560546875e-05s
Interoperability | Check the re-using of existing vocabs for Comments on Literature in Literature (CoLiL) took 1.1920928955078125e-06s
Believability | Calculation of trust value for Comments on Literature in Literature (CoLiL) took 1.1444091796875e-05s
INFO | --- Analysis for comments-on-literature-in-literature took 3563.103211402893s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of strawberry by period took 4.982948303222656e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of strawberry by period took 3.871929883956909s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of strawberry by period took 0.2810962200164795s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of strawberry by period took 0.021123647689819336s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of strawberry by period took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of strawberry by period took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of strawberry by period took 3.2901763916015625e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of strawberry by period took 1.1920928955078125e-05s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-strawberry-by-period took 86.64927768707275s
Availability | SPARQL endpoint availability check for Price competitiveness of pear by region took 8.559226989746094e-05s
Availability | VoID file availability check for Price competitiveness of pear by region took 3.166369676589966s
Completeness | Calculation of interlinking completeness for Price competitiveness of pear by region took 2.1028597354888916s
Reputation | Calculation of the PageRank for Price competitiveness of pear by region took 0.020980119705200195s
Interlinking | Calculation of Degree of Connection for Price competitiveness of pear by region took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Price competitiveness of pear by region took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of pear by region took 2.8848648071289062e-05s
Believability | Calculation of trust value for Price competitiveness of pear by region took 1.1205673217773438e-05s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period took 29.811628580093384s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of watermelon by period took 8.368492126464844e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of watermelon by period took 3.139455795288086s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of watermelon by period took 1.3474409580230713s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of watermelon by period took 0.021215438842773438s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of watermelon by period took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of watermelon by period took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of watermelon by period took 3.147125244140625e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of watermelon by period took 8.821487426757812e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period-2 took 73.17870831489563s
Availability | SPARQL endpoint availability check for Price competitiveness of grape by region took 4.220008850097656e-05s
Availability | VoID file availability check for Price competitiveness of grape by region took 3.2714388370513916s
Completeness | Calculation of interlinking completeness for Price competitiveness of grape by region took 4.958340644836426s
Reputation | Calculation of the PageRank for Price competitiveness of grape by region took 0.02267622947692871s
Interlinking | Calculation of Degree of Connection for Price competitiveness of grape by region took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Price competitiveness of grape by region took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of grape by region took 3.695487976074219e-05s
Believability | Calculation of trust value for Price competitiveness of grape by region took 1.2159347534179688e-05s
INFO | --- Analysis for comparison-of-price-competitiveness-of-grape-by-region took 51.423691749572754s
Availability | SPARQL endpoint availability check for Computational Historical Semantics in LiLa took 0.6373715400695801s
Availability | VoID file availability check for Computational Historical Semantics in LiLa took 0.24576687812805176s
Completeness | Calculation of interlinking completeness for Computational Historical Semantics in LiLa took 1.4641072750091553s
Reputation | Calculation of the PageRank for Computational Historical Semantics in LiLa took 0.02060675621032715s
Interlinking | Calculation of Degree of Connection for Computational Historical Semantics in LiLa took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Computational Historical Semantics in LiLa took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Computational Historical Semantics in LiLa took 3.4809112548828125e-05s
Interoperability | Check the re-using of existing vocabs for Computational Historical Semantics in LiLa took 3.337860107421875e-06s
Believability | Calculation of trust value for Computational Historical Semantics in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for CompHistSem took 12.290093898773193s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 0.23481082916259766s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.012869596481323242s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 4.007941722869873s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.021300077438354492s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 6.365776062011719e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 1.1682510375976562e-05s
INFO | --- Analysis for comsode-d3-2 took 14.763708591461182s
Availability | SPARQL endpoint availability check for ConceptNet took 8.225440979003906e-05s
Availability | VoID file availability check for ConceptNet took 1.8421978950500488s
Completeness | Calculation of interlinking completeness for ConceptNet took 0.469545841217041s
Reputation | Calculation of the PageRank for ConceptNet took 0.020556211471557617s
Interlinking | Calculation of Degree of Connection for ConceptNet took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ConceptNet took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for ConceptNet took 2.8848648071289062e-05s
Believability | Calculation of trust value for ConceptNet took 1.1205673217773438e-05s
INFO | --- Analysis for conceptnet took 13.381348133087158s
Availability | SPARQL endpoint availability check for 2011 US Congress People took 4.649162292480469e-05s
Availability | VoID file availability check for 2011 US Congress People took 3.1262247562408447s
Completeness | Calculation of interlinking completeness for 2011 US Congress People took 0.9317107200622559s
Reputation | Calculation of the PageRank for 2011 US Congress People took 0.02291727066040039s
Interlinking | Calculation of Degree of Connection for 2011 US Congress People took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for 2011 US Congress People took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for 2011 US Congress People took 8.392333984375e-05s
Believability | Calculation of trust value for 2011 US Congress People took 8.106231689453125e-06s
INFO | --- Analysis for congresspeople took 12.411521673202515s
Availability | SPARQL endpoint availability check for LODsyndesis Dataset took 1.9733247756958008s
Availability | VoID file availability check for LODsyndesis Dataset took 0.017888545989990234s
Completeness | Calculation of interlinking completeness for LODsyndesis Dataset took 1.3079638481140137s
Reputation | Calculation of the PageRank for LODsyndesis Dataset took 0.020586013793945312s
Interlinking | Calculation of Degree of Connection for LODsyndesis Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LODsyndesis Dataset took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for LODsyndesis Dataset took 2.8371810913085938e-05s
Believability | Calculation of trust value for LODsyndesis Dataset took 1.0967254638671875e-05s
INFO | --- Analysis for connectivity-of-lod-datasets took 52.79391527175903s
Availability | SPARQL endpoint availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.11276650428771973s
Availability | VoID file availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.014731407165527344s
Completeness | Calculation of interlinking completeness for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.3523709774017334s
Reputation | Calculation of the PageRank for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.021204710006713867s
Interlinking | Calculation of Degree of Connection for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 3.170967102050781e-05s
Believability | Calculation of trust value for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 1.239776611328125e-05s
INFO | --- Analysis for copac-library-catalogue took 10.19240951538086s
Availability | SPARQL endpoint availability check for Copyright Free Music took 8.368492126464844e-05s
Availability | VoID file availability check for Copyright Free Music took 0.602423906326294s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 0.527106523513794s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.022240877151489258s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 2.765655517578125e-05s
Believability | Calculation of trust value for Copyright Free Music took 1.1205673217773438e-05s
INFO | --- Analysis for Copyright_Free_Music took 8.241469860076904s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 8.606910705566406e-05s
Availability | VoID file availability check for CopyrightTermBank took 0.0005908012390136719s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 1.9468510150909424s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.020395278930664062s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 7.581710815429688e-05s
Believability | Calculation of trust value for CopyrightTermBank took 6.699562072753906e-05s
INFO | --- Analysis for copyrighttermbank took 42.79509735107422s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 9.81093144416809s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.4209580421447754s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.8028290271759033s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.021010875701904297s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 5.745887756347656e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 8.58306884765625e-06s
INFO | --- Analysis for core took 46.58465814590454s
Availability | SPARQL endpoint availability check for Corine linked dataset @PSNC took 0.6630618572235107s
Availability | VoID file availability check for Corine linked dataset @PSNC took 0.36840176582336426s
Extra | Recovery of all triples for Corine linked dataset @PSNC took 116.29155683517456s
Performance | Total latancy measurement for Corine linked dataset @PSNC took 1.0734729766845703s
Amount of data | Number of triples check for Corine linked dataset @PSNC took 9.672368288040161s
Interoperability | New terms check for Corine linked dataset @PSNC took 14.216899633407593s
Versatility | Languages check for Corine linked dataset @PSNC took 300.21508526802063s
Interpretability | Number of blank nodes check for Corine linked dataset @PSNC took 2.072969436645508s
Interpretability | RDF structures check for Corine linked dataset @PSNC took 0.300386905670166s
Versatility | Serialization formats check for Corine linked dataset @PSNC took 0.816605806350708s
Availability | RDF dump link check for Corine linked dataset @PSNC took 0.3720252513885498s
License | MR license check for Corine linked dataset @PSNC took 0.804793119430542s
License | HR license check for Corine linked dataset @PSNC took 300.1655683517456s
Amount of data | Number of property check for Corine linked dataset @PSNC took 0.22870492935180664s
Understandability | Number of label check for Corine linked dataset @PSNC took 2.597715139389038s
Understandability | URI regex check for Corine linked dataset @PSNC took 1.348128080368042s
Understandability | Vocabs check for Corine linked dataset @PSNC took 0.5277080535888672s
Verifiability | Authors check for Corine linked dataset @PSNC took 0.24128293991088867s
Verifiability | Publishers check for Corine linked dataset @PSNC took 2.9127705097198486s
Performance | Throughput check for Corine linked dataset @PSNC took 11.04836893081665s
Amount of data | Check the number of entities for Corine linked dataset @PSNC took 8.130073547363281e-05s
Verifiability | Contribs. check for Corine linked dataset @PSNC took 0.20180296897888184s
Interlinking | sameAs chians check for Corine linked dataset @PSNC took 0.19926738739013672s
Interlinking | skos check for Corine linked dataset @PSNC took 0.5293271541595459s
Interlinking | skos check for Corine linked dataset @PSNC took 0.42922019958496094s
Timeliness | dataset update frequency check for Corine linked dataset @PSNC took 0.6739089488983154s
Currency | Creation date check for Corine linked dataset @PSNC took 1.189866065979004s
Currency | Modification date check for Corine linked dataset @PSNC took 0.29717230796813965s
Rep.Conc. | URIs length for Corine linked dataset @PSNC took 154.12798142433167s
Interoperability | New vocabularies check for Corine linked dataset @PSNC took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Corine linked dataset @PSNC took 0.1795668601989746s
Accuracy | Check Functional Property for Corine linked dataset @PSNC took 0.3966982364654541s
Accuracy | Check Inverse Functional Property for Corine linked dataset @PSNC took 0.4699723720550537s
Accuracy | Check Empty annotation labels for Corine linked dataset @PSNC took 41.81398057937622s
Accuracy | Check White space in annotation for Corine linked dataset @PSNC took 2.6961333751678467s
Accuracy | Check Datatype consistency for Corine linked dataset @PSNC took 2.7397353649139404s
Consistency | Disjoint class check for Corine linked dataset @PSNC took 0.23855042457580566s
Consistency | Check Misplaced properties for Corine linked dataset @PSNC took 85.5844087600708s
Consistency | Misplaced classes for Corine linked dataset @PSNC took 8.350127458572388s
Consistency | Check Ontology hijacking for Corine linked dataset @PSNC took 33.716795921325684s
Consistency | Check Invalid usage of undefined classes for Corine linked dataset @PSNC took 1.5356299877166748s
Consistency | Check Invalid usage of undefined properties for Corine linked dataset @PSNC took 86.71772718429565s
Conciseness | Check Extensional conciseness for Corine linked dataset @PSNC took 2.858942747116089s
Conciseness | Check Intensional conciseness for Corine linked dataset @PSNC took 0.4925382137298584s
Security | Sign check for Corine linked dataset @PSNC took 1.5160856246948242s
Availability | Check URIs Dereferenciability for Corine linked dataset @PSNC took 3.641655206680298s
Completeness | Calculation of interlinking completeness for Corine linked dataset @PSNC took 0.6357831954956055s
Reputation | Calculation of the PageRank for Corine linked dataset @PSNC took 0.021512985229492188s
Interlinking | Calculation of Degree of Connection for Corine linked dataset @PSNC took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Corine linked dataset @PSNC took 0.0007939338684082031s
Interlinking | Calculation of Clustering coefficient for Corine linked dataset @PSNC took 3.910064697265625e-05s
Interoperability | Check the re-using of existing vocabs for Corine linked dataset @PSNC took 2.6226043701171875e-06s
Believability | Calculation of trust value for Corine linked dataset @PSNC took 1.1682510375976562e-05s
INFO | --- Analysis for Corine_linked_dataset took 2275.7231266498566s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 4.2438507080078125e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 3.703275442123413s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.6195757389068604s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.021001577377319336s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Hongcheon) Environmental Status took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Hongcheon) Environmental Status took 2.9087066650390625e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Hongcheon) Environmental Status took 8.106231689453125e-06s
INFO | --- Analysis for corn took 100.9483916759491s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 4.863739013671875e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 3.770012140274048s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Goesan) Environmental Status took 2.490952253341675s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Goesan) Environmental Status took 0.020922183990478516s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Goesan) Environmental Status took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Goesan) Environmental Status took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Goesan) Environmental Status took 3.0279159545898438e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Goesan) Environmental Status took 1.1205673217773438e-05s
INFO | --- Analysis for corn-s-famous-mountainous-district-goesan-environmental-status took 41.35960340499878s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 8.320808410644531e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 3.1503939628601074s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.316882848739624s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.02108931541442871s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Jeongseon) Environmental Status took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Jeongseon) Environmental Status took 3.743171691894531e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Jeongseon) Environmental Status took 1.1682510375976562e-05s
INFO | --- Analysis for corn-s-famous-mountainous-district-jeongseon-environmental-status took 33.27852511405945s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 8.511543273925781e-05s
Availability | VoID file availability check for Cornetto1.2 took 1.1020143032073975s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.4300875663757324s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.02064990997314453s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 5.7697296142578125e-05s
Believability | Calculation of trust value for Cornetto1.2 took 6.67572021484375e-06s
INFO | --- Analysis for cornetto took 14.05780029296875s
Availability | SPARQL endpoint availability check for Corporate Body Named Authority List  took 0.1960463523864746s
Availability | VoID file availability check for Corporate Body Named Authority List  took 4.806830406188965s
Extra | Recovery of all triples for Corporate Body Named Authority List  took 172.1993863582611s
Performance | Total latancy measurement for Corporate Body Named Authority List  took 0.6149685382843018s
Amount of data | Number of triples check for Corporate Body Named Authority List  took 42.156879901885986s
Interoperability | New terms check for Corporate Body Named Authority List  took 38.01710796356201s
Versatility | Languages check for Corporate Body Named Authority List  took 300.1337990760803s
Interpretability | Number of blank nodes check for Corporate Body Named Authority List  took 14.441717386245728s
Security | Check HTTPS for Corporate Body Named Authority List  took 0.33933115005493164s
Interpretability | RDF structures check for Corporate Body Named Authority List  took 0.471665620803833s
Versatility | Serialization formats check for Corporate Body Named Authority List  took 0.2502024173736572s
Availability | RDF dump link check for Corporate Body Named Authority List  took 0.28318142890930176s
License | MR license check for Corporate Body Named Authority List  took 0.3100299835205078s
License | HR license check for Corporate Body Named Authority List  took 83.51304936408997s
Amount of data | Number of property check for Corporate Body Named Authority List  took 0.1775047779083252s
Understandability | Number of label check for Corporate Body Named Authority List  took 2.763922691345215s
Understandability | URI regex check for Corporate Body Named Authority List  took 0.3119685649871826s
Understandability | Vocabs check for Corporate Body Named Authority List  took 0.09522271156311035s
Verifiability | Authors check for Corporate Body Named Authority List  took 0.20726585388183594s
Verifiability | Publishers check for Corporate Body Named Authority List  took 0.23126506805419922s
Performance | Throughput check for Corporate Body Named Authority List  took 10.575364351272583s
Amount of data | Check the number of entities for Corporate Body Named Authority List  took 5.412101745605469e-05s
Verifiability | Contribs. check for Corporate Body Named Authority List  took 0.1721513271331787s
Interlinking | sameAs chians check for Corporate Body Named Authority List  took 6.556915760040283s
Interlinking | skos check for Corporate Body Named Authority List  took 0.3529510498046875s
Interlinking | skos check for Corporate Body Named Authority List  took 0.31180763244628906s
Timeliness | dataset update frequency check for Corporate Body Named Authority List  took 0.1954038143157959s
Currency | Creation date check for Corporate Body Named Authority List  took 1.0770549774169922s
Currency | Modification date check for Corporate Body Named Authority List  took 0.2576887607574463s
Rep.Conc. | URIs length for Corporate Body Named Authority List  took 342.27704071998596s
Interoperability | New vocabularies check for Corporate Body Named Authority List  took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Corporate Body Named Authority List  took 0.1847374439239502s
Accuracy | Check Functional Property for Corporate Body Named Authority List  took 0.19015741348266602s
Accuracy | Check Inverse Functional Property for Corporate Body Named Authority List  took 0.16640353202819824s
Accuracy | Check Empty annotation labels for Corporate Body Named Authority List  took 41.322081565856934s
Accuracy | Check White space in annotation for Corporate Body Named Authority List  took 3.297661304473877s
Accuracy | Check Datatype consistency for Corporate Body Named Authority List  took 2.6951396465301514s
Consistency | Disjoint class check for Corporate Body Named Authority List  took 0.13827991485595703s
Consistency | Check Misplaced properties for Corporate Body Named Authority List  took 234.39290022850037s
Consistency | Misplaced classes for Corporate Body Named Authority List  took 8.715333223342896s
Consistency | Check Ontology hijacking for Corporate Body Named Authority List  took 88.39528751373291s
Consistency | Check Invalid usage of undefined classes for Corporate Body Named Authority List  took 1.8115088939666748s
Consistency | Check Invalid usage of undefined properties for Corporate Body Named Authority List  took 234.96864581108093s
Conciseness | Check Extensional conciseness for Corporate Body Named Authority List  took 3.199418306350708s
Conciseness | Check Intensional conciseness for Corporate Body Named Authority List  took 0.4222559928894043s
Security | Sign check for Corporate Body Named Authority List  took 0.1463940143585205s
Availability | Check URIs Dereferenciability for Corporate Body Named Authority List  took 3.845947265625s
Completeness | Calculation of interlinking completeness for Corporate Body Named Authority List  took 2.33652400970459s
Reputation | Calculation of the PageRank for Corporate Body Named Authority List  took 0.020763397216796875s
Interlinking | Calculation of Degree of Connection for Corporate Body Named Authority List  took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Corporate Body Named Authority List  took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Corporate Body Named Authority List  took 4.863739013671875e-05s
Interoperability | Check the re-using of existing vocabs for Corporate Body Named Authority List  took 1.430511474609375e-06s
Believability | Calculation of trust value for Corporate Body Named Authority List  took 1.1444091796875e-05s
INFO | --- Analysis for corporate-body took 9791.234855413437s
Availability | SPARQL endpoint availability check for Corpus Fibonacci in LiLa took 0.6439511775970459s
Availability | VoID file availability check for Corpus Fibonacci in LiLa took 0.2403724193572998s
Completeness | Calculation of interlinking completeness for Corpus Fibonacci in LiLa took 2.5040621757507324s
Reputation | Calculation of the PageRank for Corpus Fibonacci in LiLa took 0.02071237564086914s
Interlinking | Calculation of Degree of Connection for Corpus Fibonacci in LiLa took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Corpus Fibonacci in LiLa took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Corpus Fibonacci in LiLa took 3.552436828613281e-05s
Interoperability | Check the re-using of existing vocabs for Corpus Fibonacci in LiLa took 4.0531158447265625e-06s
Believability | Calculation of trust value for Corpus Fibonacci in LiLa took 1.5497207641601562e-05s
INFO | --- Analysis for CorpusFibonacci took 11.693540334701538s
Availability | SPARQL endpoint availability check for CORS Check - HTTP Header Logs for Linked Open Data took 0.12668251991271973s
Availability | VoID file availability check for CORS Check - HTTP Header Logs for Linked Open Data took 0.014700174331665039s
Completeness | Calculation of interlinking completeness for CORS Check - HTTP Header Logs for Linked Open Data took 0.3022270202636719s
Reputation | Calculation of the PageRank for CORS Check - HTTP Header Logs for Linked Open Data took 0.020508289337158203s
Interlinking | Calculation of Degree of Connection for CORS Check - HTTP Header Logs for Linked Open Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CORS Check - HTTP Header Logs for Linked Open Data took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for CORS Check - HTTP Header Logs for Linked Open Data took 2.7179718017578125e-05s
Believability | Calculation of trust value for CORS Check - HTTP Header Logs for Linked Open Data took 1.1205673217773438e-05s
INFO | --- Analysis for corscheck took 8.390681743621826s
Availability | SPARQL endpoint availability check for Country Name Authority List took 0.22369122505187988s
Availability | VoID file availability check for Country Name Authority List took 4.503344774246216s
Extra | Recovery of all triples for Country Name Authority List took 187.08331847190857s
Performance | Total latancy measurement for Country Name Authority List took 0.6586654186248779s
Amount of data | Number of triples check for Country Name Authority List took 30.22928762435913s
Interoperability | New terms check for Country Name Authority List took 38.52559494972229s
Versatility | Languages check for Country Name Authority List took 300.118061542511s
Interpretability | Number of blank nodes check for Country Name Authority List took 37.66696763038635s
Security | Check HTTPS for Country Name Authority List took 0.4005751609802246s
Interpretability | RDF structures check for Country Name Authority List took 0.42165350914001465s
Versatility | Serialization formats check for Country Name Authority List took 0.3102095127105713s
Availability | RDF dump link check for Country Name Authority List took 0.2272779941558838s
License | MR license check for Country Name Authority List took 0.2059309482574463s
License | HR license check for Country Name Authority List took 82.45192694664001s
Amount of data | Number of property check for Country Name Authority List took 0.19332098960876465s
Understandability | Number of label check for Country Name Authority List took 1.0674450397491455s
Understandability | URI regex check for Country Name Authority List took 0.4174020290374756s
Understandability | Vocabs check for Country Name Authority List took 0.1232302188873291s
Verifiability | Authors check for Country Name Authority List took 0.2590758800506592s
Verifiability | Publishers check for Country Name Authority List took 0.2067553997039795s
Performance | Throughput check for Country Name Authority List took 10.488898754119873s
Amount of data | Check the number of entities for Country Name Authority List took 0.0004398822784423828s
Verifiability | Contribs. check for Country Name Authority List took 0.2349536418914795s
Interlinking | sameAs chians check for Country Name Authority List took 6.825122356414795s
Interlinking | skos check for Country Name Authority List took 0.197983980178833s
Interlinking | skos check for Country Name Authority List took 0.14021611213684082s
Timeliness | dataset update frequency check for Country Name Authority List took 0.22312164306640625s
Currency | Creation date check for Country Name Authority List took 0.9351766109466553s
Currency | Modification date check for Country Name Authority List took 0.13583707809448242s
Rep.Conc. | URIs length for Country Name Authority List took 321.1960678100586s
Interoperability | New vocabularies check for Country Name Authority List took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Country Name Authority List took 0.20015954971313477s
Accuracy | Check Functional Property for Country Name Authority List took 0.20675420761108398s
Accuracy | Check Inverse Functional Property for Country Name Authority List took 0.15199542045593262s
Accuracy | Check Empty annotation labels for Country Name Authority List took 40.51981973648071s
Accuracy | Check White space in annotation for Country Name Authority List took 3.2777154445648193s
Accuracy | Check Datatype consistency for Country Name Authority List took 2.7323176860809326s
Consistency | Disjoint class check for Country Name Authority List took 0.15998387336730957s
Consistency | Check Misplaced properties for Country Name Authority List took 231.95443892478943s
Consistency | Misplaced classes for Country Name Authority List took 8.803380250930786s
Consistency | Check Ontology hijacking for Country Name Authority List took 36.600191593170166s
Consistency | Check Invalid usage of undefined classes for Country Name Authority List took 1.8126277923583984s
Consistency | Check Invalid usage of undefined properties for Country Name Authority List took 13.785876512527466s
Conciseness | Check Extensional conciseness for Country Name Authority List took 3.1462900638580322s
Conciseness | Check Intensional conciseness for Country Name Authority List took 0.4491546154022217s
Security | Sign check for Country Name Authority List took 0.17522978782653809s
Availability | Check URIs Dereferenciability for Country Name Authority List took 4.043694257736206s
Completeness | Calculation of interlinking completeness for Country Name Authority List took 0.8410446643829346s
Reputation | Calculation of the PageRank for Country Name Authority List took 0.027463912963867188s
Interlinking | Calculation of Degree of Connection for Country Name Authority List took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Country Name Authority List took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Country Name Authority List took 6.031990051269531e-05s
Interoperability | Check the re-using of existing vocabs for Country Name Authority List took 1.6689300537109375e-06s
Believability | Calculation of trust value for Country Name Authority List took 1.4781951904296875e-05s
INFO | --- Analysis for country-authority-list took 9530.85478067398s
Availability | SPARQL endpoint availability check for Courts thesaurus took 0.09912276268005371s
Availability | VoID file availability check for Courts thesaurus took 0.013628005981445312s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 0.452411413192749s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.021548748016357422s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 7.796287536621094e-05s
Believability | Calculation of trust value for Courts thesaurus took 1.6689300537109375e-05s
INFO | --- Analysis for courts-thesaurus took 5.019162178039551s
Availability | SPARQL endpoint availability check for Covid-on-the-Web Dataset took 0.37613344192504883s
Availability | VoID file availability check for Covid-on-the-Web Dataset took 0.38912105560302734s
Extra | Recovery of all triples for Covid-on-the-Web Dataset took 2.4858598709106445s
Performance | Total latancy measurement for Covid-on-the-Web Dataset took 0.6742901802062988s
Amount of data | Number of triples check for Covid-on-the-Web Dataset took 17.775620460510254s
Interoperability | New terms check for Covid-on-the-Web Dataset took 14.851067543029785s
Versatility | Languages check for Covid-on-the-Web Dataset took 300.17378997802734s
Interpretability | Number of blank nodes check for Covid-on-the-Web Dataset took 69.3619236946106s
Interpretability | RDF structures check for Covid-on-the-Web Dataset took 0.12407493591308594s
Versatility | Serialization formats check for Covid-on-the-Web Dataset took 0.3043203353881836s
Availability | RDF dump link check for Covid-on-the-Web Dataset took 3.5155935287475586s
License | MR license check for Covid-on-the-Web Dataset took 0.43009400367736816s
License | HR license check for Covid-on-the-Web Dataset took 300.1792998313904s
Amount of data | Number of property check for Covid-on-the-Web Dataset took 0.15002965927124023s
Understandability | Number of label check for Covid-on-the-Web Dataset took 1.0433554649353027s
Understandability | URI regex check for Covid-on-the-Web Dataset took 0.4601454734802246s
Understandability | Vocabs check for Covid-on-the-Web Dataset took 0.1210637092590332s
Verifiability | Authors check for Covid-on-the-Web Dataset took 2.3562252521514893s
Verifiability | Publishers check for Covid-on-the-Web Dataset took 0.2525007724761963s
Performance | Throughput check for Covid-on-the-Web Dataset took 10.794755697250366s
Amount of data | Check the number of entities for Covid-on-the-Web Dataset took 0.1012411117553711s
Verifiability | Contribs. check for Covid-on-the-Web Dataset took 0.19824004173278809s
Interlinking | sameAs chians check for Covid-on-the-Web Dataset took 0.1642313003540039s
Interlinking | skos check for Covid-on-the-Web Dataset took 0.12939023971557617s
Interlinking | skos check for Covid-on-the-Web Dataset took 0.12230372428894043s
Timeliness | dataset update frequency check for Covid-on-the-Web Dataset took 0.8483719825744629s
Currency | Creation date check for Covid-on-the-Web Dataset took 0.13431477546691895s
Currency | Modification date check for Covid-on-the-Web Dataset took 0.14893269538879395s
Rep.Conc. | URIs length for Covid-on-the-Web Dataset took 45.67754769325256s
Interoperability | New vocabularies check for Covid-on-the-Web Dataset took 10.697640657424927s
Consistency | Deprecated classes/propertiers check for Covid-on-the-Web Dataset took 0.15350937843322754s
Accuracy | Check Functional Property for Covid-on-the-Web Dataset took 0.328655481338501s
Accuracy | Check Inverse Functional Property for Covid-on-the-Web Dataset took 0.31679248809814453s
Accuracy | Check Empty annotation labels for Covid-on-the-Web Dataset took 1.6199305057525635s
Accuracy | Check White space in annotation for Covid-on-the-Web Dataset took 0.0626976490020752s
Accuracy | Check Datatype consistency for Covid-on-the-Web Dataset took 0.08492469787597656s
Consistency | Disjoint class check for Covid-on-the-Web Dataset took 0.1329052448272705s
Consistency | Check Misplaced properties for Covid-on-the-Web Dataset took 46.98216652870178s
Consistency | Misplaced classes for Covid-on-the-Web Dataset took 1.8723194599151611s
Consistency | Check Ontology hijacking for Covid-on-the-Web Dataset took 2.7201273441314697s
Consistency | Check Invalid usage of undefined classes for Covid-on-the-Web Dataset took 1.3260219097137451s
Consistency | Check Invalid usage of undefined properties for Covid-on-the-Web Dataset took 29.828142642974854s
Conciseness | Check Extensional conciseness for Covid-on-the-Web Dataset took 0.09087085723876953s
Conciseness | Check Intensional conciseness for Covid-on-the-Web Dataset took 1.980776071548462s
Security | Sign check for Covid-on-the-Web Dataset took 0.8945455551147461s
Availability | Check URIs Dereferenciability for Covid-on-the-Web Dataset took 3.7439658641815186s
Completeness | Calculation of interlinking completeness for Covid-on-the-Web Dataset took 0.4738645553588867s
Reputation | Calculation of the PageRank for Covid-on-the-Web Dataset took 0.17770123481750488s
Interlinking | Calculation of Degree of Connection for Covid-on-the-Web Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Covid-on-the-Web Dataset took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Covid-on-the-Web Dataset took 8.678436279296875e-05s
Interoperability | Check the re-using of existing vocabs for Covid-on-the-Web Dataset took 10.979502201080322s
Believability | Calculation of trust value for Covid-on-the-Web Dataset took 1.1444091796875e-05s
INFO | --- Analysis for Covid-on-the-Web took 5469.433725833893s
Availability | SPARQL endpoint availability check for CPA 2008 took 24.69796061515808s
Availability | VoID file availability check for CPA 2008 took 1.599701166152954s
Completeness | Calculation of interlinking completeness for CPA 2008 took 0.46860384941101074s
Reputation | Calculation of the PageRank for CPA 2008 took 0.02120685577392578s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 4.172325134277344e-05s
Believability | Calculation of trust value for CPA 2008 took 1.239776611328125e-05s
INFO | --- Analysis for cpa-2008 took 106.42654466629028s
Availability | SPARQL endpoint availability check for Cooperative Patent Classification took 0.42350125312805176s
Availability | VoID file availability check for Cooperative Patent Classification took 0.3177046775817871s
Extra | Recovery of all triples for Cooperative Patent Classification took 22.98761558532715s
Performance | Total latancy measurement for Cooperative Patent Classification took 0.7812769412994385s
Amount of data | Number of triples check for Cooperative Patent Classification took 90.09225583076477s
Versatility | Languages check for Cooperative Patent Classification took 120.13656330108643s
Interpretability | Number of blank nodes check for Cooperative Patent Classification took 90.1744875907898s
Interpretability | RDF structures check for Cooperative Patent Classification took 0.21798181533813477s
Versatility | Serialization formats check for Cooperative Patent Classification took 0.20439529418945312s
Availability | RDF dump link check for Cooperative Patent Classification took 0.17275047302246094s
License | MR license check for Cooperative Patent Classification took 0.23411798477172852s
License | HR license check for Cooperative Patent Classification took 90.13995814323425s
Amount of data | Number of property check for Cooperative Patent Classification took 0.13981103897094727s
Understandability | Number of label check for Cooperative Patent Classification took 90.14559483528137s
Understandability | URI regex check for Cooperative Patent Classification took 0.36039304733276367s
Understandability | Vocabs check for Cooperative Patent Classification took 0.13868141174316406s
Verifiability | Authors check for Cooperative Patent Classification took 0.16919183731079102s
Verifiability | Publishers check for Cooperative Patent Classification took 0.2005908489227295s
Performance | Throughput check for Cooperative Patent Classification took 10.788896083831787s
Amount of data | Check the number of entities for Cooperative Patent Classification took 0.00014638900756835938s
Verifiability | Contribs. check for Cooperative Patent Classification took 0.16272568702697754s
Interlinking | sameAs chians check for Cooperative Patent Classification took 0.12632083892822266s
Interlinking | skos check for Cooperative Patent Classification took 0.11940670013427734s
Interlinking | skos check for Cooperative Patent Classification took 0.11102700233459473s
Timeliness | dataset update frequency check for Cooperative Patent Classification took 0.11035895347595215s
Currency | Creation date check for Cooperative Patent Classification took 0.09764719009399414s
Currency | Modification date check for Cooperative Patent Classification took 0.6554522514343262s
Rep.Conc. | URIs length for Cooperative Patent Classification took 149.5080122947693s
Interoperability | New vocabularies check for Cooperative Patent Classification took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for Cooperative Patent Classification took 0.17692947387695312s
Accuracy | Check Empty annotation labels for Cooperative Patent Classification took 14.237953424453735s
Accuracy | Check White space in annotation for Cooperative Patent Classification took 3.0006604194641113s
Accuracy | Check Datatype consistency for Cooperative Patent Classification took 4.804506301879883s
Consistency | Disjoint class check for Cooperative Patent Classification took 0.17658019065856934s
Consistency | Check Misplaced properties for Cooperative Patent Classification took 120.31259322166443s
Consistency | Check Ontology hijacking for Cooperative Patent Classification took 17.29834794998169s
Consistency | Check Invalid usage of undefined classes for Cooperative Patent Classification took 1.6085398197174072s
Consistency | Check Invalid usage of undefined properties for Cooperative Patent Classification took 121.63808631896973s
Conciseness | Check Extensional conciseness for Cooperative Patent Classification took 2.9697072505950928s
Conciseness | Check Intensional conciseness for Cooperative Patent Classification took 0.1968986988067627s
Security | Sign check for Cooperative Patent Classification took 0.17917585372924805s
Availability | Check URIs Dereferenciability for Cooperative Patent Classification took 0.9975886344909668s
Completeness | Calculation of interlinking completeness for Cooperative Patent Classification took 0.6160032749176025s
Reputation | Calculation of the PageRank for Cooperative Patent Classification took 0.02144479751586914s
Interlinking | Calculation of Degree of Connection for Cooperative Patent Classification took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Cooperative Patent Classification took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Cooperative Patent Classification took 4.9114227294921875e-05s
Interoperability | Check the re-using of existing vocabs for Cooperative Patent Classification took 1.9073486328125e-06s
Believability | Calculation of trust value for Cooperative Patent Classification took 1.1682510375976562e-05s
INFO | --- Analysis for CPC took 1313.4255051612854s
Availability | SPARQL endpoint availability check for CPC 2008 took 25.320630073547363s
Availability | VoID file availability check for CPC 2008 took 2.027416944503784s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.28972864151000977s
Reputation | Calculation of the PageRank for CPC 2008 took 0.020763158798217773s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0006847381591796875s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 3.814697265625e-05s
Believability | Calculation of trust value for CPC 2008 took 9.775161743164062e-06s
INFO | --- Analysis for cpc-2008 took 101.3411295413971s
Availability | SPARQL endpoint availability check for CPV  2003 took 20.927490711212158s
Availability | VoID file availability check for CPV  2003 took 1.9170374870300293s
Completeness | Calculation of interlinking completeness for CPV  2003 took 0.38149309158325195s
Reputation | Calculation of the PageRank for CPV  2003 took 0.022443532943725586s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 4.8160552978515625e-05s
Believability | Calculation of trust value for CPV  2003 took 1.0251998901367188e-05s
INFO | --- Analysis for cpv-2003 took 95.9388632774353s
Availability | SPARQL endpoint availability check for CPV 2008 took 23.921042919158936s
Availability | VoID file availability check for CPV 2008 took 2.289186954498291s
Completeness | Calculation of interlinking completeness for CPV 2008 took 1.835101842880249s
Reputation | Calculation of the PageRank for CPV 2008 took 0.021065711975097656s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 4.8160552978515625e-05s
Believability | Calculation of trust value for CPV 2008 took 9.775161743164062e-06s
INFO | --- Analysis for cpv-2008 took 108.1042833328247s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 260.97876715660095s
Availability | VoID file availability check for crowdsourcing-fb took 0.0002875328063964844s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 0.4970400333404541s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.020906925201416016s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 4.3392181396484375e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 1.1682510375976562e-05s
INFO | --- Analysis for crowdsourcing-fb took 394.7171814441681s
Availability | SPARQL endpoint availability check for CRTM took 20.388333082199097s
Availability | VoID file availability check for CRTM took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for CRTM took 0.7595932483673096s
Reputation | Calculation of the PageRank for CRTM took 0.021299362182617188s
Interlinking | Calculation of Degree of Connection for CRTM took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for CRTM took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for CRTM took 2.9325485229492188e-05s
Believability | Calculation of trust value for CRTM took 1.0967254638671875e-05s
INFO | --- Analysis for crtm took 43.11701202392578s
Availability | SPARQL endpoint availability check for Crystal Eye: Aggregated Crystallographic Data took 0.3365938663482666s
Availability | VoID file availability check for Crystal Eye: Aggregated Crystallographic Data took 0.21492958068847656s
Completeness | Calculation of interlinking completeness for Crystal Eye: Aggregated Crystallographic Data took 0.3683016300201416s
Reputation | Calculation of the PageRank for Crystal Eye: Aggregated Crystallographic Data took 0.02423548698425293s
Interlinking | Calculation of Degree of Connection for Crystal Eye: Aggregated Crystallographic Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Crystal Eye: Aggregated Crystallographic Data took 0.0011327266693115234s
Interlinking | Calculation of Clustering coefficient for Crystal Eye: Aggregated Crystallographic Data took 4.029273986816406e-05s
Believability | Calculation of trust value for Crystal Eye: Aggregated Crystallographic Data took 1.2874603271484375e-05s
INFO | --- Analysis for crystal-eye took 3.590526819229126s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 6.795648813247681s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.20294618606567383s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 0.31172704696655273s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.02200913429260254s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 4.4345855712890625e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 9.298324584960938e-06s
INFO | --- Analysis for ctic-public-dataset took 39.2041916847229s
Availability | SPARQL endpoint availability check for Cultivation status of GMO crops took 8.678436279296875e-05s
Availability | VoID file availability check for Cultivation status of GMO crops took 3.783754348754883s
Completeness | Calculation of interlinking completeness for Cultivation status of GMO crops took 0.44749021530151367s
Reputation | Calculation of the PageRank for Cultivation status of GMO crops took 0.022565126419067383s
Interlinking | Calculation of Degree of Connection for Cultivation status of GMO crops took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cultivation status of GMO crops took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Cultivation status of GMO crops took 2.8371810913085938e-05s
Believability | Calculation of trust value for Cultivation status of GMO crops took 1.1682510375976562e-05s
INFO | --- Analysis for cultivation-status-of-gmo-crops took 40.51970291137695s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 0.47584962844848633s
Availability | VoID file availability check for CulturaLinkedData took 0.18114256858825684s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 0.4255995750427246s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.020563364028930664s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 2.7418136596679688e-05s
Believability | Calculation of trust value for CulturaLinkedData took 1.2159347534179688e-05s
INFO | --- Analysis for culturalinkeddata took 6.019671201705933s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.2374269962310791s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.08450555801391602s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.7232179641723633s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.021509408950805664s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 3.62396240234375e-05s
Believability | Calculation of trust value for Data about business entities from the ARES system - business registry of the Czech Republic took 8.821487426757812e-06s
INFO | --- Analysis for cz-ares-or took 2.9726760387420654s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.12900733947753906s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.09243631362915039s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.3367500305175781s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.02217245101928711s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 3.337860107421875e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 5.7220458984375e-06s
INFO | --- Analysis for cz-ares-rzp took 2.9281692504882812s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 0.12945175170898438s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.08784198760986328s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.6438319683074951s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.020668983459472656s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 3.123283386230469e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 1.2874603271484375e-05s
INFO | --- Analysis for cz-cenia-irz-chemicals took 4.598633766174316s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 0.11716961860656738s
Availability | VoID file availability check for Integrated pollution registry took 0.07601547241210938s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 1.0397403240203857s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.021043062210083008s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 3.981590270996094e-05s
Believability | Calculation of trust value for Integrated pollution registry took 1.1205673217773438e-05s
INFO | --- Analysis for cz-cenia-pollution took 7.715192556381226s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 0.11903071403503418s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.08499264717102051s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.40578484535217285s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.021495819091796875s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Contracts took 3.504753112792969e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Contracts took 8.58306884765625e-06s
INFO | --- Analysis for cz-contracts took 2.5190093517303467s
Availability | SPARQL endpoint availability check for List of courts of the Czech Republic took 0.08111047744750977s
Availability | VoID file availability check for List of courts of the Czech Republic took 0.00021195411682128906s
Completeness | Calculation of interlinking completeness for List of courts of the Czech Republic took 0.34031128883361816s
Reputation | Calculation of the PageRank for List of courts of the Czech Republic took 0.021013498306274414s
Interlinking | Calculation of Degree of Connection for List of courts of the Czech Republic took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for List of courts of the Czech Republic took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for List of courts of the Czech Republic took 2.7418136596679688e-05s
Believability | Calculation of trust value for List of courts of the Czech Republic took 1.1920928955078125e-05s
INFO | --- Analysis for cz-courts took 3.3553178310394287s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 0.11505365371704102s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.0749363899230957s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.4110729694366455s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.0210111141204834s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 4.3392181396484375e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 9.059906005859375e-06s
INFO | --- Analysis for cz-ctia-bans took 7.5106706619262695s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 0.12929534912109375s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.08795595169067383s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 0.6235496997833252s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.020775318145751953s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 3.5762786865234375e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 9.059906005859375e-06s
INFO | --- Analysis for cz-ctia-confiscations took 4.463886737823486s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.11869668960571289s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.07900071144104004s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.48294615745544434s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.02224564552307129s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 3.9577484130859375e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 8.821487426757812e-06s
INFO | --- Analysis for cz-ctia-focus took 2.4248745441436768s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 0.10543560981750488s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.08424782752990723s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 1.371016502380371s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.02196955680847168s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 4.172325134277344e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 8.344650268554688e-06s
INFO | --- Analysis for cz-ctia-inspections took 3.448601245880127s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 0.12703537940979004s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.07572245597839355s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.29796862602233887s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.021403074264526367s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 3.528594970703125e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 9.059906005859375e-06s
INFO | --- Analysis for cz-ctia-sanctions took 6.471445083618164s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 0.22984838485717773s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.08540606498718262s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.8579568862915039s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.020842313766479492s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 3.6716461181640625e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 8.821487426757812e-06s
INFO | --- Analysis for cz-cuzk-cadastre-offices took 6.6462461948394775s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 0.11617851257324219s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.06501102447509766s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 1.0051546096801758s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.02042675018310547s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 3.075599670410156e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 9.775161743164062e-06s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 3.4113945960998535s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 0.5816996097564697s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.5204010009765625s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.4727468490600586s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.020401477813720703s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 3.695487976074219e-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 4.756005048751831s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 0.40958738327026367s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.5195951461791992s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 0.36319613456726074s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.020803451538085938s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 3.838539123535156e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 9.059906005859375e-06s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 4.867304086685181s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.4232463836669922s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.6131789684295654s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.30564260482788086s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.020712614059448242s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 3.504753112792969e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 9.5367431640625e-06s
INFO | --- Analysis for cz-czso-demography-in-regions-czech-republic-age-categories took 3.8247463703155518s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 0.3807682991027832s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.5682570934295654s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 1.0812578201293945s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.021348953247070312s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 4.38690185546875e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 9.298324584960938e-06s
INFO | --- Analysis for cz-czso-job-applicants took 5.33332896232605s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.3969886302947998s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.5689990520477295s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 1.7796850204467773s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.02111649513244629s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 3.9577484130859375e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 9.775161743164062e-06s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 5.309859752655029s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.42133450508117676s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.5284328460693359s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.3531012535095215s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.020822763442993164s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 3.695487976074219e-05s
Believability | Calculation of trust value for Structure of regions of Czech Republic according to Czech Statistical Office took 9.298324584960938e-06s
INFO | --- Analysis for cz-czso-regions took 3.728292465209961s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 0.41245436668395996s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.5723326206207275s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 0.440157413482666s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.020492076873779297s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 3.5762786865234375e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 8.821487426757812e-06s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 5.409286022186279s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 0.4354972839355469s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.5836489200592041s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 1.6994295120239258s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.02054142951965332s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 3.552436828613281e-05s
Believability | Calculation of trust value for Social service facilities and nursing in districts of Czech republic took 8.344650268554688e-06s
INFO | --- Analysis for cz-czso-social-service-facilities took 17.941327571868896s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 0.41393065452575684s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.5217139720916748s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 3.0783889293670654s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.020860910415649414s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 4.1961669921875e-05s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 9.059906005859375e-06s
INFO | --- Analysis for cz-czso-unemployment-rate took 47.83486557006836s
Availability | SPARQL endpoint availability check for ATC groups took 0.14183926582336426s
Availability | VoID file availability check for ATC groups took 0.09015893936157227s
Completeness | Calculation of interlinking completeness for ATC groups took 0.34711718559265137s
Reputation | Calculation of the PageRank for ATC groups took 0.023879528045654297s
Interlinking | Calculation of Degree of Connection for ATC groups took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.0012400150299072266s
Interlinking | Calculation of Clustering coefficient for ATC groups took 9.131431579589844e-05s
Believability | Calculation of trust value for ATC groups took 1.239776611328125e-05s
INFO | --- Analysis for cz-eh-1-atc took 6.05541205406189s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.13190531730651855s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.07698416709899902s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.7951011657714844s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.021615266799926758s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Financial fulfillments took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0010712146759033203s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 4.291534423828125e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 9.775161743164062e-06s
INFO | --- Analysis for cz-fulfillments took 6.3384904861450195s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 0.030230998992919922s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.0029556751251220703s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 2.0335755348205566s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.020970582962036133s
Interlinking | Calculation of Degree of Connection for Czech Business Entity identification numbers and names took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Czech Business Entity identification numbers and names took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 4.6253204345703125e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 8.821487426757812e-06s
INFO | --- Analysis for cz-ic took 8.171849250793457s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 0.12665700912475586s
Availability | VoID file availability check for List of Czech data boxes took 0.13756060600280762s
Extra | Recovery of all triples for List of Czech data boxes took 165.81193089485168s
Performance | Total latancy measurement for List of Czech data boxes took 0.6556382179260254s
Amount of data | Number of triples check for List of Czech data boxes took 11.91795539855957s
Interoperability | New terms check for List of Czech data boxes took 11.97962212562561s
Versatility | Languages check for List of Czech data boxes took 300.172376871109s
Interpretability | Number of blank nodes check for List of Czech data boxes took 1.5582270622253418s
Interpretability | RDF structures check for List of Czech data boxes took 0.17438364028930664s
Versatility | Serialization formats check for List of Czech data boxes took 0.14433717727661133s
Availability | RDF dump link check for List of Czech data boxes took 16.205869913101196s
License | MR license check for List of Czech data boxes took 0.6142072677612305s
License | HR license check for List of Czech data boxes took 64.18450474739075s
Amount of data | Number of property check for List of Czech data boxes took 0.12866592407226562s
Understandability | Number of label check for List of Czech data boxes took 2.0104005336761475s
Understandability | URI regex check for List of Czech data boxes took 0.6903743743896484s
Understandability | Vocabs check for List of Czech data boxes took 0.12122702598571777s
Verifiability | Authors check for List of Czech data boxes took 5.5365917682647705s
Verifiability | Publishers check for List of Czech data boxes took 0.8677432537078857s
Performance | Throughput check for List of Czech data boxes took 10.682169437408447s
Amount of data | Check the number of entities for List of Czech data boxes took 3.132208824157715s
Verifiability | Contribs. check for List of Czech data boxes took 0.16762161254882812s
Interlinking | sameAs chians check for List of Czech data boxes took 0.28510522842407227s
Interlinking | skos check for List of Czech data boxes took 0.3443481922149658s
Interlinking | skos check for List of Czech data boxes took 0.14563894271850586s
Timeliness | dataset update frequency check for List of Czech data boxes took 0.3949904441833496s
Currency | Creation date check for List of Czech data boxes took 0.22350645065307617s
Currency | Modification date check for List of Czech data boxes took 0.12078619003295898s
Rep.Conc. | URIs length for List of Czech data boxes took 128.4311683177948s
Interoperability | New vocabularies check for List of Czech data boxes took 10.340994596481323s
Consistency | Deprecated classes/propertiers check for List of Czech data boxes took 0.3858330249786377s
Accuracy | Check Functional Property for List of Czech data boxes took 0.32544636726379395s
Accuracy | Check Inverse Functional Property for List of Czech data boxes took 0.3262491226196289s
Accuracy | Check Empty annotation labels for List of Czech data boxes took 35.52485251426697s
Accuracy | Check White space in annotation for List of Czech data boxes took 3.0947461128234863s
Accuracy | Check Datatype consistency for List of Czech data boxes took 2.6556649208068848s
Consistency | Disjoint class check for List of Czech data boxes took 0.12383055686950684s
Consistency | Check Misplaced properties for List of Czech data boxes took 78.4807550907135s
Consistency | Misplaced classes for List of Czech data boxes took 7.598024606704712s
Consistency | Check Ontology hijacking for List of Czech data boxes took 35.23669624328613s
Consistency | Check Invalid usage of undefined classes for List of Czech data boxes took 1.4227869510650635s
Consistency | Check Invalid usage of undefined properties for List of Czech data boxes took 72.20544791221619s
Conciseness | Check Extensional conciseness for List of Czech data boxes took 2.7076072692871094s
Conciseness | Check Intensional conciseness for List of Czech data boxes took 0.3477518558502197s
Security | Sign check for List of Czech data boxes took 0.2174358367919922s
Availability | Check URIs Dereferenciability for List of Czech data boxes took 418.0369806289673s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 0.7830042839050293s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.02398538589477539s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 2.574920654296875e-05s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0010540485382080078s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 5.1975250244140625e-05s
Interoperability | Check the re-using of existing vocabs for List of Czech data boxes took 9.254789590835571s
Believability | Calculation of trust value for List of Czech data boxes took 1.0013580322265625e-05s
INFO | --- Analysis for cz-list-of-databoxes took 2207.763213157654s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.14854168891906738s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.13205599784851074s
Extra | Recovery of all triples for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 163.49892616271973s
Performance | Total latancy measurement for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.6434762477874756s
Amount of data | Number of triples check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 11.096016645431519s
Interoperability | New terms check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 12.036903858184814s
Versatility | Languages check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 300.2133228778839s
Interpretability | Number of blank nodes check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.3173208236694336s
Interpretability | RDF structures check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.17714238166809082s
Versatility | Serialization formats check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12578845024108887s
Availability | RDF dump link check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 15.764198303222656s
License | MR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.8982458114624023s
License | HR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 61.106505155563354s
Amount of data | Number of property check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1568617820739746s
Understandability | Number of label check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.0809874534606934s
Understandability | URI regex check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.8242964744567871s
Understandability | Vocabs check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1409621238708496s
Verifiability | Authors check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 5.438622951507568s
Verifiability | Publishers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.8394155502319336s
Performance | Throughput check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.569198846817017s
Amount of data | Check the number of entities for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.3516619205474854s
Verifiability | Contribs. check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.13169169425964355s
Interlinking | sameAs chians check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.2900538444519043s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.33620238304138184s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12043905258178711s
Timeliness | dataset update frequency check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.3323841094970703s
Currency | Creation date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.21477699279785156s
Currency | Modification date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.16730427742004395s
Rep.Conc. | URIs length for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 127.71561431884766s
Interoperability | New vocabularies check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 9.336130380630493s
Consistency | Deprecated classes/propertiers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.6207828521728516s
Accuracy | Check Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.30643200874328613s
Accuracy | Check Inverse Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12102556228637695s
Accuracy | Check Empty annotation labels for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 36.4253191947937s
Accuracy | Check White space in annotation for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.095015287399292s
Accuracy | Check Datatype consistency for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.6345198154449463s
Consistency | Disjoint class check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12135958671569824s
Consistency | Check Misplaced properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 77.07043957710266s
Consistency | Misplaced classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 7.780415296554565s
Consistency | Check Ontology hijacking for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 36.143953800201416s
Consistency | Check Invalid usage of undefined classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.5140478610992432s
Consistency | Check Invalid usage of undefined properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 71.2115638256073s
Conciseness | Check Extensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.8034164905548096s
Conciseness | Check Intensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.35369277000427246s
Security | Sign check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1851212978363037s
Availability | Check URIs Dereferenciability for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 422.7219703197479s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.7881512641906738s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.02355480194091797s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 4.9591064453125e-05s
Interoperability | Check the re-using of existing vocabs for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 9.231561660766602s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 9.298324584960938e-06s
INFO | --- Analysis for cz-nace took 2202.3709902763367s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.37812066078186035s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.002576589584350586s
Extra | Recovery of all triples for Czech National Open Data Catalog in DCAT-AP v1.2 took 420.26574444770813s
Performance | Total latancy measurement for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.947596549987793s
Amount of data | Number of triples check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.9145054817199707s
Interoperability | New terms check for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.8846168518066406s
Versatility | Languages check for Czech National Open Data Catalog in DCAT-AP v1.2 took 300.20137333869934s
Interpretability | Number of blank nodes check for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.4614696502685547s
Interpretability | RDF structures check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.6722631454467773s
Versatility | Serialization formats check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2173910140991211s
