Availability | SPARQL endpoint availability check for Korespondencja Emila Szramka z Janem Kuderą took 4.2438507080078125e-05s
Availability | VoID file availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.0005986690521240234s
Completeness | Calculation of interlinking completeness for Korespondencja Emila Szramka z Janem Kuderą took 0.3100707530975342s
Reputation | Calculation of the PageRank for Korespondencja Emila Szramka z Janem Kuderą took 0.5247104167938232s
Interlinking | Calculation of Degree of Connection for Korespondencja Emila Szramka z Janem Kuderą took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Korespondencja Emila Szramka z Janem Kuderą took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Korespondencja Emila Szramka z Janem Kuderą took 0.00032830238342285156s
Believability | Calculation of trust value for Korespondencja Emila Szramka z Janem Kuderą took 5.9604644775390625e-06s
INFO | --- Analysis for 0080-3626 took 6.2463531494140625s
Availability | SPARQL endpoint availability check for 土地利用图 took 4.220008850097656e-05s
Availability | VoID file availability check for 土地利用图 took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for 土地利用图 took 0.24852204322814941s
Reputation | Calculation of the PageRank for 土地利用图 took 0.01986241340637207s
Interlinking | Calculation of Degree of Connection for 土地利用图 took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for 土地利用图 took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for 土地利用图 took 2.6941299438476562e-05s
Believability | Calculation of trust value for 土地利用图 took 6.4373016357421875e-06s
INFO | --- Analysis for 10.12041geodata.290864223.ver1.db_ took 3.7707290649414062s
Availability | SPARQL endpoint availability check for 113322 took 4.124641418457031e-05s
Availability | VoID file availability check for 113322 took 0.0006330013275146484s
Completeness | Calculation of interlinking completeness for 113322 took 0.9661612510681152s
Reputation | Calculation of the PageRank for 113322 took 0.019872426986694336s
Interlinking | Calculation of Degree of Connection for 113322 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for 113322 took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for 113322 took 2.6226043701171875e-05s
Believability | Calculation of trust value for 113322 took 7.62939453125e-06s
INFO | --- Analysis for 11 took 5.621174097061157s
Availability | SPARQL endpoint availability check for Korepetycje Buki took 4.100799560546875e-05s
Availability | VoID file availability check for Korepetycje Buki took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for Korepetycje Buki took 0.970726728439331s
Reputation | Calculation of the PageRank for Korepetycje Buki took 0.019876480102539062s
Interlinking | Calculation of Degree of Connection for Korepetycje Buki took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Korepetycje Buki took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Korepetycje Buki took 2.6464462280273438e-05s
Believability | Calculation of trust value for Korepetycje Buki took 7.867813110351562e-06s
INFO | --- Analysis for 12323 took 3.480010986328125s
Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 2.967775821685791s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.0005550384521484375s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.3104057312011719s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.020015478134155273s
Interlinking | Calculation of Degree of Connection for 2000 U.S. Census in RDF (rdfabout.com) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for 2000 U.S. Census in RDF (rdfabout.com) took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 8.726119995117188e-05s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 6.4373016357421875e-06s
INFO | --- Analysis for 2000-us-census-rdf took 14.653423070907593s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 2.334925889968872s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.31691670417785645s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.020045042037963867s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 3.6716461181640625e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 4.5299530029296875e-06s
INFO | --- Analysis for 2001-spanish-census-to-rdf took 7.326908349990845s
Availability | SPARQL endpoint availability check for Open Data Web took 0.28888416290283203s
Availability | VoID file availability check for Open Data Web took 0.0002396106719970703s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.3036320209503174s
Reputation | Calculation of the PageRank for Open Data Web took 0.02019810676574707s
Interlinking | Calculation of Degree of Connection for Open Data Web took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.0040740966796875e-05s
Believability | Calculation of trust value for Open Data Web took 6.9141387939453125e-06s
INFO | --- Analysis for _data.odw.tw took 4.773632287979126s
Availability | SPARQL endpoint availability check for 土地利用 took 4.1961669921875e-05s
Availability | VoID file availability check for 土地利用 took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for 土地利用 took 0.5732266902923584s
Reputation | Calculation of the PageRank for 土地利用 took 0.01995682716369629s
Interlinking | Calculation of Degree of Connection for 土地利用 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for 土地利用 took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for 土地利用 took 2.6941299438476562e-05s
Believability | Calculation of trust value for 土地利用 took 7.62939453125e-06s
INFO | --- Analysis for _data1.odw.tw took 6.24685001373291s
Availability | SPARQL endpoint availability check for 土地利用模型 took 4.267692565917969e-05s
Availability | VoID file availability check for 土地利用模型 took 0.0003516674041748047s
Completeness | Calculation of interlinking completeness for 土地利用模型 took 0.2966630458831787s
Reputation | Calculation of the PageRank for 土地利用模型 took 0.020475149154663086s
Interlinking | Calculation of Degree of Connection for 土地利用模型 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for 土地利用模型 took 0.0007910728454589844s
Interlinking | Calculation of Clustering coefficient for 土地利用模型 took 3.0279159545898438e-05s
Believability | Calculation of trust value for 土地利用模型 took 1.3113021850585938e-05s
INFO | --- Analysis for _data2.odw.tw took 6.2956788539886475s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 8.940696716308594e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.00038504600524902344s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2925112247467041s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02054882049560547s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.0279159545898438e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.3909759521484375e-06s
INFO | --- Analysis for _https:data.bioontology.orgontologiesBOFdownloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb&download_format=rdf took 6.1754162311553955s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 4.220008850097656e-05s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.0005273818969726562s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.31504201889038086s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.020403623580932617s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 2.8848648071289062e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 7.867813110351562e-06s
INFO | --- Analysis for a-collection-of-papers-for-lrec2014-and-related-workshops took 5.394567966461182s
Availability | SPARQL endpoint availability check for ITS TEST DATASET took 4.1961669921875e-05s
Availability | VoID file availability check for ITS TEST DATASET took 0.0006878376007080078s
Completeness | Calculation of interlinking completeness for ITS TEST DATASET took 0.30211877822875977s
Reputation | Calculation of the PageRank for ITS TEST DATASET took 0.020232200622558594s
Interlinking | Calculation of Degree of Connection for ITS TEST DATASET took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ITS TEST DATASET took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for ITS TEST DATASET took 3.0040740966796875e-05s
Believability | Calculation of trust value for ITS TEST DATASET took 4.76837158203125e-06s
INFO | --- Analysis for A1 took 9.000982522964478s
Availability | SPARQL endpoint availability check for SummerOlympics took 11.183066844940186s
Availability | VoID file availability check for SummerOlympics took 0.0007216930389404297s
Completeness | Calculation of interlinking completeness for SummerOlympics took 0.3147554397583008s
Reputation | Calculation of the PageRank for SummerOlympics took 0.019990921020507812s
Interlinking | Calculation of Degree of Connection for SummerOlympics took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SummerOlympics took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for SummerOlympics took 6.246566772460938e-05s
Believability | Calculation of trust value for SummerOlympics took 7.3909759521484375e-06s
INFO | --- Analysis for abc took 18.353609800338745s
Availability | SPARQL endpoint availability check for Test_m took 4.172325134277344e-05s
Availability | VoID file availability check for Test_m took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for Test_m took 0.4315612316131592s
Reputation | Calculation of the PageRank for Test_m took 0.020340442657470703s
Interlinking | Calculation of Degree of Connection for Test_m took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Test_m took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Test_m took 3.0517578125e-05s
Believability | Calculation of trust value for Test_m took 7.3909759521484375e-06s
INFO | --- Analysis for ABC took 3.9188899993896484s
Availability | SPARQL endpoint availability check for my intro took 4.076957702636719e-05s
Availability | VoID file availability check for my intro took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for my intro took 0.30406665802001953s
Reputation | Calculation of the PageRank for my intro took 0.02009892463684082s
Interlinking | Calculation of Degree of Connection for my intro took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for my intro took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for my intro took 2.8133392333984375e-05s
Believability | Calculation of trust value for my intro took 7.152557373046875e-06s
INFO | --- Analysis for abhay_intro took 3.040245771408081s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.6565237045288086s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.0005283355712890625s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.30252814292907715s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.020278215408325195s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 0.00010275840759277344s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 8.106231689453125e-06s
INFO | --- Analysis for abs-linked-data took 4.713598728179932s
Availability | SPARQL endpoint availability check for Academic Offer of UNL took 3.981590270996094e-05s
Availability | VoID file availability check for Academic Offer of UNL took 0.00028014183044433594s
Completeness | Calculation of interlinking completeness for Academic Offer of UNL took 0.31176090240478516s
Reputation | Calculation of the PageRank for Academic Offer of UNL took 0.020432233810424805s
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.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Academic Offer of UNL took 3.2901763916015625e-05s
Believability | Calculation of trust value for Academic Offer of UNL took 8.106231689453125e-06s
INFO | --- Analysis for academic-offer-of-unl took 3.4488048553466797s
Availability | SPARQL endpoint availability check for AcadOnto took 4.076957702636719e-05s
Availability | VoID file availability check for AcadOnto took 0.0005714893341064453s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.9406716823577881s
Reputation | Calculation of the PageRank for AcadOnto took 0.02010035514831543s
Interlinking | Calculation of Degree of Connection for AcadOnto took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for AcadOnto took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 2.9087066650390625e-05s
Believability | Calculation of trust value for AcadOnto took 7.3909759521484375e-06s
INFO | --- Analysis for acadonto took 5.196605205535889s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 12.174281120300293s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0007719993591308594s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.3144373893737793s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.02000570297241211s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 3.552436828613281e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 5.0067901611328125e-06s
INFO | --- Analysis for acorn-sat took 45.520774841308594s
Availability | SPARQL endpoint availability check for Addgene took 4.076957702636719e-05s
Availability | VoID file availability check for Addgene took 0.0008232593536376953s
Completeness | Calculation of interlinking completeness for Addgene took 0.7186543941497803s
Reputation | Calculation of the PageRank for Addgene took 0.02007746696472168s
Interlinking | Calculation of Degree of Connection for Addgene took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Addgene took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Addgene took 3.2901763916015625e-05s
Believability | Calculation of trust value for Addgene took 6.67572021484375e-06s
INFO | --- Analysis for addgene took 16.195616245269775s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 4.1484832763671875e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.28453493118286133s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.020437002182006836s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 9.393692016601562e-05s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 6.4373016357421875e-06s
INFO | --- Analysis for aegp-spanish-textile-and-clothing-association took 2.9747612476348877s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 30.445749759674072s
Availability | VoID file availability check for AEMET metereological dataset took 0.0007460117340087891s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.38169384002685547s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.02057623863220215s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 3.3855438232421875e-05s
Believability | Calculation of trust value for AEMET metereological dataset took 7.3909759521484375e-06s
INFO | --- Analysis for aemet took 144.06362676620483s
Availability | SPARQL endpoint availability check for Agenda de Zaragoza took 4.076957702636719e-05s
Availability | VoID file availability check for Agenda de Zaragoza took 0.0002269744873046875s
Completeness | Calculation of interlinking completeness for Agenda de Zaragoza took 0.25615668296813965s
Reputation | Calculation of the PageRank for Agenda de Zaragoza took 0.02008223533630371s
Interlinking | Calculation of Degree of Connection for Agenda de Zaragoza took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Agenda de Zaragoza took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Agenda de Zaragoza took 2.8133392333984375e-05s
Believability | Calculation of trust value for Agenda de Zaragoza took 7.3909759521484375e-06s
INFO | --- Analysis for agenda-de-zaragoza took 3.406158685684204s
Availability | SPARQL endpoint availability check for AgriNepalData took 0.032636165618896484s
Availability | VoID file availability check for AgriNepalData took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for AgriNepalData took 0.2629082202911377s
Reputation | Calculation of the PageRank for AgriNepalData took 0.02005171775817871s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 6.890296936035156e-05s
Believability | Calculation of trust value for AgriNepalData took 9.059906005859375e-06s
INFO | --- Analysis for agrinepaldata took 2.3974380493164062s
Availability | SPARQL endpoint availability check for AGRIS took 261.1169595718384s
Availability | VoID file availability check for AGRIS took 0.0006794929504394531s
Completeness | Calculation of interlinking completeness for AGRIS took 0.3207254409790039s
Reputation | Calculation of the PageRank for AGRIS took 0.020556926727294922s
Interlinking | Calculation of Degree of Connection for AGRIS took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for AGRIS took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for AGRIS took 7.390975952148438e-05s
Believability | Calculation of trust value for AGRIS took 7.62939453125e-06s
INFO | --- Analysis for agris took 556.2550973892212s
Availability | SPARQL endpoint availability check for AGROVOC took 0.2090601921081543s
Availability | VoID file availability check for AGROVOC took 0.0005342960357666016s
Extra | Recovery of all triples for AGROVOC took 32.75910687446594s
Performance | Total latancy measurement for AGROVOC took 0.4974048137664795s
Amount of data | Number of triples check for AGROVOC took 12.93303108215332s
Interoperability | New terms check for AGROVOC took 3.6174051761627197s
Versatility | Languages check for AGROVOC took 30.08399748802185s
Interpretability | Number of blank nodes check for AGROVOC took 11.096253633499146s
Interpretability | RDF structures check for AGROVOC took 0.07929396629333496s
Versatility | Serialization formats check for AGROVOC took 0.1011354923248291s
Availability | RDF dump link check for AGROVOC took 0.07816123962402344s
License | MR license check for AGROVOC took 0.12823820114135742s
License | HR license check for AGROVOC took 0.3700430393218994s
Amount of data | Number of property check for AGROVOC took 0.10210275650024414s
Understandability | Number of label check for AGROVOC took 28.42980647087097s
Understandability | URI regex check for AGROVOC took 0.19056010246276855s
Understandability | Vocabs check for AGROVOC took 0.07832551002502441s
Verifiability | Authors check for AGROVOC took 0.08786773681640625s
Verifiability | Publishers check for AGROVOC took 0.07676935195922852s
Performance | Throughput check for AGROVOC took 10.511097431182861s
Amount of data | Check the number of entities for AGROVOC took 6.985664367675781e-05s
Verifiability | Contribs. check for AGROVOC took 0.19757342338562012s
Interlinking | sameAs chians check for AGROVOC took 0.1857292652130127s
Interlinking | skos check for AGROVOC took 0.20050644874572754s
Interlinking | skos check for AGROVOC took 0.19559454917907715s
Timeliness | dataset update frequency check for AGROVOC took 0.1848607063293457s
Currency | Creation date check for AGROVOC took 0.16654229164123535s
Currency | Modification date check for AGROVOC took 0.1658320426940918s
Rep.Conc. | URIs length for AGROVOC took 34.47310495376587s
Interoperability | New vocabularies check for AGROVOC took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for AGROVOC took 0.10400533676147461s
Accuracy | Check Functional Property for AGROVOC took 0.08912849426269531s
Accuracy | Check Inverse Functional Property for AGROVOC took 0.07623744010925293s
Accuracy | Check Empty annotation labels for AGROVOC took 19.272640466690063s
Accuracy | Check White space in annotation for AGROVOC took 2.9592039585113525s
Accuracy | Check Datatype consistency for AGROVOC took 4.362416505813599s
Consistency | Disjoint class check for AGROVOC took 0.08716750144958496s
Consistency | Check Misplaced properties for AGROVOC took 10.721758604049683s
Consistency | Check Ontology hijacking for AGROVOC took 19.226835250854492s
Consistency | Check Invalid usage of undefined classes for AGROVOC took 1.5062482357025146s
Consistency | Check Invalid usage of undefined properties for AGROVOC took 13.2755286693573s
Conciseness | Check Extensional conciseness for AGROVOC took 2.7734501361846924s
Conciseness | Check Intensional conciseness for AGROVOC took 0.11793875694274902s
Security | Sign check for AGROVOC took 0.1007840633392334s
Availability | Check URIs Dereferenciability for AGROVOC took 2.8918631076812744s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.8085527420043945s
Reputation | Calculation of the PageRank for AGROVOC took 0.02026677131652832s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 0.00011372566223144531s
Interoperability | Check the re-using of existing vocabs for AGROVOC took 1.9073486328125e-06s
Believability | Calculation of trust value for AGROVOC took 7.62939453125e-06s
INFO | --- Analysis for agrovoc took 309.02343249320984s
Availability | SPARQL endpoint availability check for AGROVOC took 4.00543212890625e-05s
Availability | VoID file availability check for AGROVOC took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.26114916801452637s
Reputation | Calculation of the PageRank for AGROVOC took 0.020783662796020508s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 7.009506225585938e-05s
Believability | Calculation of trust value for AGROVOC took 8.344650268554688e-06s
INFO | --- Analysis for agrovoc-skos took 4.273156404495239s
Availability | SPARQL endpoint availability check for Analytics India Magazine took 8.58306884765625e-05s
Availability | VoID file availability check for Analytics India Magazine took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for Analytics India Magazine took 0.24711179733276367s
Reputation | Calculation of the PageRank for Analytics India Magazine took 0.0200653076171875s
Interlinking | Calculation of Degree of Connection for Analytics India Magazine took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Analytics India Magazine took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for Analytics India Magazine took 3.1948089599609375e-05s
Believability | Calculation of trust value for Analytics India Magazine took 7.152557373046875e-06s
INFO | --- Analysis for AIM took 2.743260622024536s
Availability | SPARQL endpoint availability check for All India Survey of Higher Education took 4.100799560546875e-05s
Availability | VoID file availability check for All India Survey of Higher Education took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for All India Survey of Higher Education took 0.2543368339538574s
Reputation | Calculation of the PageRank for All India Survey of Higher Education took 0.02009272575378418s
Interlinking | Calculation of Degree of Connection for All India Survey of Higher Education took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for All India Survey of Higher Education took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for All India Survey of Higher Education took 3.0994415283203125e-05s
Believability | Calculation of trust value for All India Survey of Higher Education took 6.198883056640625e-06s
INFO | --- Analysis for AISHE took 2.346292018890381s
Availability | SPARQL endpoint availability check for  equipment ontology took 4.100799560546875e-05s
Availability | VoID file availability check for  equipment ontology took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for  equipment ontology took 0.25043344497680664s
Reputation | Calculation of the PageRank for  equipment ontology took 0.02007007598876953s
Interlinking | Calculation of Degree of Connection for  equipment ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for  equipment ontology took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for  equipment ontology took 3.075599670410156e-05s
Believability | Calculation of trust value for  equipment ontology took 5.9604644775390625e-06s
INFO | --- Analysis for akash took 2.3852620124816895s
Availability | SPARQL endpoint availability check for aksw.org Research Group dataset took 3.838539123535156e-05s
Availability | VoID file availability check for aksw.org Research Group dataset took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for aksw.org Research Group dataset took 0.2510831356048584s
Reputation | Calculation of the PageRank for aksw.org Research Group dataset took 0.020189762115478516s
Interlinking | Calculation of Degree of Connection for aksw.org Research Group dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for aksw.org Research Group dataset took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for aksw.org Research Group dataset took 3.075599670410156e-05s
Believability | Calculation of trust value for aksw.org Research Group dataset took 6.9141387939453125e-06s
INFO | --- Analysis for aksworg took 2.9111135005950928s
Availability | SPARQL endpoint availability check for AlchemyAPI took 3.8623809814453125e-05s
Availability | VoID file availability check for AlchemyAPI took 0.00023102760314941406s
Completeness | Calculation of interlinking completeness for AlchemyAPI took 0.26454925537109375s
Reputation | Calculation of the PageRank for AlchemyAPI took 0.020144939422607422s
Interlinking | Calculation of Degree of Connection for AlchemyAPI took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for AlchemyAPI took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for AlchemyAPI took 3.0040740966796875e-05s
Believability | Calculation of trust value for AlchemyAPI took 6.67572021484375e-06s
INFO | --- Analysis for alchemyapi took 3.317009449005127s
Availability | SPARQL endpoint availability check for Alexandria Digital Library (ADL) Gazetteer took 3.886222839355469e-05s
Availability | VoID file availability check for Alexandria Digital Library (ADL) Gazetteer took 0.00027823448181152344s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library (ADL) Gazetteer took 0.26961660385131836s
Reputation | Calculation of the PageRank for Alexandria Digital Library (ADL) Gazetteer took 0.020135164260864258s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library (ADL) Gazetteer took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Alexandria Digital Library (ADL) Gazetteer took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library (ADL) Gazetteer took 3.0994415283203125e-05s
Believability | Calculation of trust value for Alexandria Digital Library (ADL) Gazetteer took 6.67572021484375e-06s
INFO | --- Analysis for alexandria-digital-library-adl-gazetteer took 2.8789002895355225s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 1.764885663986206s
Availability | VoID file availability check for aliada-scanbit-net took 0.00038504600524902344s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 0.2533142566680908s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.019963741302490234s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.00013184547424316406s
Believability | Calculation of trust value for aliada-scanbit-net took 6.67572021484375e-06s
INFO | --- Analysis for aliada-scanbit-net took 4.459248304367065s
Availability | SPARQL endpoint availability check for Allen Brain Atlas took 3.933906555175781e-05s
Availability | VoID file availability check for Allen Brain Atlas took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for Allen Brain Atlas took 0.25774717330932617s
Reputation | Calculation of the PageRank for Allen Brain Atlas took 0.020505666732788086s
Interlinking | Calculation of Degree of Connection for Allen Brain Atlas took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Allen Brain Atlas took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Allen Brain Atlas took 2.9802322387695312e-05s
Believability | Calculation of trust value for Allen Brain Atlas took 6.198883056640625e-06s
INFO | --- Analysis for allen-brain-atlas took 2.892045021057129s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 4.67297101020813s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.0006544589996337891s
Extra | Recovery of all triples for Allie Abbreviation And Long Form Database in Life Science took 10.094310998916626s
Amount of data | Number of triples check for Allie Abbreviation And Long Form Database in Life Science took 10.096683740615845s
Versatility | Languages check for Allie Abbreviation And Long Form Database in Life Science took 10.096877336502075s
Interpretability | Number of blank nodes check for Allie Abbreviation And Long Form Database in Life Science took 10.095851421356201s
Interpretability | RDF structures check for Allie Abbreviation And Long Form Database in Life Science took 10.0003342628479s
Versatility | Serialization formats check for Allie Abbreviation And Long Form Database in Life Science took 10.006397485733032s
Availability | RDF dump link check for Allie Abbreviation And Long Form Database in Life Science took 10.098307609558105s
License | MR license check for Allie Abbreviation And Long Form Database in Life Science took 10.102324485778809s
License | HR license check for Allie Abbreviation And Long Form Database in Life Science took 10.092264890670776s
Amount of data | Number of property check for Allie Abbreviation And Long Form Database in Life Science took 10.005290269851685s
Understandability | Number of label check for Allie Abbreviation And Long Form Database in Life Science took 10.097000122070312s
Understandability | URI regex check for Allie Abbreviation And Long Form Database in Life Science took 20.0983784198761s
Understandability | Vocabs check for Allie Abbreviation And Long Form Database in Life Science took 0.6923983097076416s
Verifiability | Authors check for Allie Abbreviation And Long Form Database in Life Science took 10.010576725006104s
Verifiability | Publishers check for Allie Abbreviation And Long Form Database in Life Science took 9.997905492782593s
Amount of data | Check the number of entities for Allie Abbreviation And Long Form Database in Life Science took 8.249282836914062e-05s
Verifiability | Contribs. check for Allie Abbreviation And Long Form Database in Life Science took 10.100399494171143s
Interlinking | sameAs chians check for Allie Abbreviation And Long Form Database in Life Science took 10.095168352127075s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 10.003349304199219s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 10.095403671264648s
Timeliness | dataset update frequency check for Allie Abbreviation And Long Form Database in Life Science took 9.999140977859497s
Currency | Creation date check for Allie Abbreviation And Long Form Database in Life Science took 20.007838487625122s
Currency | Modification date check for Allie Abbreviation And Long Form Database in Life Science took 20.19154644012451s
Rep.Conc. | URIs length for Allie Abbreviation And Long Form Database in Life Science took 20.10601568222046s
Interoperability | New vocabularies check for Allie Abbreviation And Long Form Database in Life Science took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for Allie Abbreviation And Long Form Database in Life Science took 10.09461236000061s
Consistency | Disjoint class check for Allie Abbreviation And Long Form Database in Life Science took 10.008438348770142s
Consistency | Check Ontology hijacking for Allie Abbreviation And Long Form Database in Life Science took 10.004887580871582s
Consistency | Check Invalid usage of undefined properties for Allie Abbreviation And Long Form Database in Life Science took 11.619428396224976s
Conciseness | Check Extensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 0.00013589859008789062s
Security | Sign check for Allie Abbreviation And Long Form Database in Life Science took 1.898923397064209s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 0.3717002868652344s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.02211904525756836s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0009279251098632812s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 9.274482727050781e-05s
Interoperability | Check the re-using of existing vocabs for Allie Abbreviation And Long Form Database in Life Science took 1.9073486328125e-06s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 7.3909759521484375e-06s
INFO | --- Analysis for allie-abbreviation-and-long-form-database-in-life-science took 601.1577997207642s
Availability | SPARQL endpoint availability check for Alojamientos took 4.982948303222656e-05s
Availability | VoID file availability check for Alojamientos took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for Alojamientos took 0.7281005382537842s
Reputation | Calculation of the PageRank for Alojamientos took 0.02739238739013672s
Interlinking | Calculation of Degree of Connection for Alojamientos took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Alojamientos took 0.0014193058013916016s
Interlinking | Calculation of Clustering coefficient for Alojamientos took 5.8650970458984375e-05s
Believability | Calculation of trust value for Alojamientos took 1.1444091796875e-05s
INFO | --- Analysis for alojamientos-zaragoza took 3.8061206340789795s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 0.3144195079803467s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.001184225082397461s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 0.70926833152771s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.020219802856445312s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 3.790855407714844e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 1.5735626220703125e-05s
INFO | --- Analysis for alpino-rdf took 5.4210944175720215s
Availability | SPARQL endpoint availability check for AAT-atawil took 4.172325134277344e-05s
Availability | VoID file availability check for AAT-atawil took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for AAT-atawil took 0.2592775821685791s
Reputation | Calculation of the PageRank for AAT-atawil took 0.020170211791992188s
Interlinking | Calculation of Degree of Connection for AAT-atawil took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for AAT-atawil took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for AAT-atawil took 2.9802322387695312e-05s
Believability | Calculation of trust value for AAT-atawil took 6.4373016357421875e-06s
INFO | --- Analysis for Altawil took 2.4088287353515625s
Availability | SPARQL endpoint availability check for Auckland Museum Collections Online took 3.981590270996094e-05s
Availability | VoID file availability check for Auckland Museum Collections Online took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for Auckland Museum Collections Online took 0.25908827781677246s
Reputation | Calculation of the PageRank for Auckland Museum Collections Online took 0.020446062088012695s
Interlinking | Calculation of Degree of Connection for Auckland Museum Collections Online took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Auckland Museum Collections Online took 0.0007402896881103516s
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 7.152557373046875e-06s
INFO | --- Analysis for am-collections-online took 2.9456770420074463s
Availability | SPARQL endpoint availability check for Amer Nejma took 4.267692565917969e-05s
Availability | VoID file availability check for Amer Nejma took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for Amer Nejma took 0.30216526985168457s
Reputation | Calculation of the PageRank for Amer Nejma took 0.02058696746826172s
Interlinking | Calculation of Degree of Connection for Amer Nejma took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Amer Nejma took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Amer Nejma took 3.123283386230469e-05s
Believability | Calculation of trust value for Amer Nejma took 7.62939453125e-06s
INFO | --- Analysis for Amer_Nejma took 2.8819520473480225s
Availability | SPARQL endpoint availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.27434253692626953s
Reputation | Calculation of the PageRank for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.020235776901245117s
Interlinking | Calculation of Degree of Connection for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 3.075599670410156e-05s
Believability | Calculation of trust value for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for amon took 2.9509778022766113s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.6335890293121338s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.26577234268188477s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.020382404327392578s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0007276535034179688s
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 6.4373016357421875e-06s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 3.797254800796509s
Availability | SPARQL endpoint availability check for Analisi del blog http://www.beppegrillo.it/ took 3.933906555175781e-05s
Availability | VoID file availability check for Analisi del blog http://www.beppegrillo.it/ took 0.0002353191375732422s
Completeness | Calculation of interlinking completeness for Analisi del blog http://www.beppegrillo.it/ took 0.2831394672393799s
Reputation | Calculation of the PageRank for Analisi del blog http://www.beppegrillo.it/ took 0.02007269859313965s
Interlinking | Calculation of Degree of Connection for Analisi del blog http://www.beppegrillo.it/ took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Analisi del blog http://www.beppegrillo.it/ took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Analisi del blog http://www.beppegrillo.it/ took 3.0994415283203125e-05s
Believability | Calculation of trust value for Analisi del blog http://www.beppegrillo.it/ took 7.62939453125e-06s
INFO | --- Analysis for analisi-del-blog-http-www-beppegrillo-it took 2.976414680480957s
Availability | SPARQL endpoint availability check for Animal Diversity Web took 4.029273986816406e-05s
Availability | VoID file availability check for Animal Diversity Web took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for Animal Diversity Web took 0.2729313373565674s
Reputation | Calculation of the PageRank for Animal Diversity Web took 0.020172834396362305s
Interlinking | Calculation of Degree of Connection for Animal Diversity Web took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Animal Diversity Web took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Animal Diversity Web took 3.123283386230469e-05s
Believability | Calculation of trust value for Animal Diversity Web took 1.6689300537109375e-05s
INFO | --- Analysis for animal-diversity-web took 3.0095531940460205s
Availability | SPARQL endpoint availability check for Anime Dataset took 4.220008850097656e-05s
Availability | VoID file availability check for Anime Dataset took 0.001192331314086914s
Completeness | Calculation of interlinking completeness for Anime Dataset took 0.28284645080566406s
Reputation | Calculation of the PageRank for Anime Dataset took 0.020259618759155273s
Interlinking | Calculation of Degree of Connection for Anime Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Anime Dataset took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Anime Dataset took 2.9802322387695312e-05s
Believability | Calculation of trust value for Anime Dataset took 6.9141387939453125e-06s
INFO | --- Analysis for Anime took 3.9757583141326904s
Availability | SPARQL endpoint availability check for ANNO took 7.653236389160156e-05s
Availability | VoID file availability check for ANNO took 0.0006172657012939453s
Completeness | Calculation of interlinking completeness for ANNO took 0.29056477546691895s
Reputation | Calculation of the PageRank for ANNO took 0.02026534080505371s
Interlinking | Calculation of Degree of Connection for ANNO took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ANNO took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for ANNO took 3.314018249511719e-05s
Believability | Calculation of trust value for ANNO took 7.62939453125e-06s
INFO | --- Analysis for anno took 8.343955755233765s
Availability | SPARQL endpoint availability check for Antique Cars Collection (Linked Cars) took 4.315376281738281e-05s
Availability | VoID file availability check for Antique Cars Collection (Linked Cars) took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for Antique Cars Collection (Linked Cars) took 0.2744617462158203s
Reputation | Calculation of the PageRank for Antique Cars Collection (Linked Cars) took 0.020146846771240234s
Interlinking | Calculation of Degree of Connection for Antique Cars Collection (Linked Cars) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Antique Cars Collection (Linked Cars) took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Antique Cars Collection (Linked Cars) took 7.843971252441406e-05s
Believability | Calculation of trust value for Antique Cars Collection (Linked Cars) took 6.9141387939453125e-06s
INFO | --- Analysis for AntiqueCarsCollection took 2.9581360816955566s
Availability | SPARQL endpoint availability check for apache took 4.267692565917969e-05s
Availability | VoID file availability check for apache took 0.0006723403930664062s
Completeness | Calculation of interlinking completeness for apache took 0.26756954193115234s
Reputation | Calculation of the PageRank for apache took 0.020151615142822266s
Interlinking | Calculation of Degree of Connection for apache took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for apache took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for apache took 5.626678466796875e-05s
Believability | Calculation of trust value for apache took 7.152557373046875e-06s
INFO | --- Analysis for apache took 3.3549611568450928s
Availability | SPARQL endpoint availability check for Apertium RDF took 4.124641418457031e-05s
Availability | VoID file availability check for Apertium RDF took 0.0006058216094970703s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.26543092727661133s
Reputation | Calculation of the PageRank for Apertium RDF took 0.020173072814941406s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 4.4345855712890625e-05s
Believability | Calculation of trust value for Apertium RDF took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf took 4.918978691101074s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 4.1484832763671875e-05s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.0007219314575195312s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.2557978630065918s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.01999187469482422s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 4.3392181396484375e-05s
Believability | Calculation of trust value for Apertium RDF CA-IT took 6.4373016357421875e-06s
INFO | --- Analysis for apertium-rdf-ca-it took 5.686060190200806s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 4.7206878662109375e-05s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.0012373924255371094s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.2768990993499756s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.02010202407836914s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 4.482269287109375e-05s
Believability | Calculation of trust value for Apertium RDF EN-CA took 7.867813110351562e-06s
INFO | --- Analysis for apertium-rdf-en-ca took 5.768671751022339s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 4.1961669921875e-05s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.0006082057952880859s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.28591299057006836s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.020671844482421875s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 4.38690185546875e-05s
Believability | Calculation of trust value for Apertium RDF EN-ES took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-en-es took 5.601513385772705s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 4.363059997558594e-05s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.0006268024444580078s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.2684478759765625s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.02048015594482422s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-GL took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF EN-GL took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 4.410743713378906e-05s
Believability | Calculation of trust value for Apertium RDF EN-GL took 8.106231689453125e-06s
INFO | --- Analysis for apertium-rdf-en-gl took 5.688086271286011s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 4.1961669921875e-05s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.0006005764007568359s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 0.27912211418151855s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.020283222198486328s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 4.363059997558594e-05s
Believability | Calculation of trust value for Apertium RDF EO-CA took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-eo-ca took 5.63006854057312s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 4.2438507080078125e-05s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.0014491081237792969s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.26546764373779297s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.02066636085510254s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-EN took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-EN took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 4.506111145019531e-05s
Believability | Calculation of trust value for Apertium RDF EO-EN took 1.1682510375976562e-05s
INFO | --- Analysis for apertium-rdf-eo-en took 5.549124479293823s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 4.3392181396484375e-05s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.0011446475982666016s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.2643470764160156s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.020506858825683594s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 4.57763671875e-05s
Believability | Calculation of trust value for Apertium RDF EO-ES took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-eo-es took 5.535031080245972s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 4.315376281738281e-05s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.0005784034729003906s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.25691962242126465s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.020853281021118164s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 4.76837158203125e-05s
Believability | Calculation of trust value for Apertium RDF EO-FR took 8.58306884765625e-06s
INFO | --- Analysis for apertium-rdf-eo-fr took 5.540476560592651s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 4.38690185546875e-05s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.0003180503845214844s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.27622199058532715s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.021220684051513672s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 4.9114227294921875e-05s
Believability | Calculation of trust value for Apertium RDF ES-AN took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-es-an took 5.527689456939697s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 4.1484832763671875e-05s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0009396076202392578s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.24471521377563477s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.020699501037597656s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 4.792213439941406e-05s
Believability | Calculation of trust value for Apertium RDF ES-AST took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-es-ast took 5.510290622711182s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 4.124641418457031e-05s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 0.291628360748291s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.020986557006835938s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 5.3882598876953125e-05s
Believability | Calculation of trust value for Apertium RDF ES-CA took 8.106231689453125e-06s
INFO | --- Analysis for apertium-rdf-es-ca took 24.876147747039795s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 4.5299530029296875e-05s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.0009024143218994141s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.23507237434387207s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.02089524269104004s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 4.982948303222656e-05s
Believability | Calculation of trust value for Apertium RDF ES-GL took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-es-gl took 5.426370620727539s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 4.4345855712890625e-05s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.0005588531494140625s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.26215386390686035s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.0206148624420166s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 4.744529724121094e-05s
Believability | Calculation of trust value for Apertium RDF ES-PT took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-es-pt took 5.648249387741089s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 4.673004150390625e-05s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.0005393028259277344s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.27866101264953613s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.02039813995361328s
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.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 4.601478576660156e-05s
Believability | Calculation of trust value for Apertium RDF ES-RO took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-es-ro took 5.523896932601929s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 4.744529724121094e-05s
Availability | VoID file availability check for Apertium RDF EU-EN took 0.0005881786346435547s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.2769467830657959s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.020626544952392578s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 4.6253204345703125e-05s
Believability | Calculation of trust value for Apertium RDF EU-EN took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-eu-en took 5.632330656051636s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 4.172325134277344e-05s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.0011458396911621094s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.2748072147369385s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.021328449249267578s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0009598731994628906s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 4.839897155761719e-05s
Believability | Calculation of trust value for Apertium RDF EU-ES took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-eu-es took 5.6762449741363525s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 4.315376281738281e-05s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.0012924671173095703s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.2636375427246094s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.020641803741455078s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 7.033348083496094e-05s
Believability | Calculation of trust value for Apertium RDF FR-CA took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-fr-ca took 5.479773044586182s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 4.3392181396484375e-05s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.0002911090850830078s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.2569539546966553s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.02049541473388672s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 4.696846008300781e-05s
Believability | Calculation of trust value for Apertium RDF FR-ES took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-fr-es took 5.51982307434082s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 7.557868957519531e-05s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0006635189056396484s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 0.26415324211120605s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.020472049713134766s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 4.744529724121094e-05s
Believability | Calculation of trust value for Apertium RDF OC-CA took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-oc-ca took 5.517893314361572s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 4.863739013671875e-05s
Availability | VoID file availability check for Apertium RDF OC-ES took 0.0006356239318847656s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 0.26109743118286133s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.02049088478088379s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 5.340576171875e-05s
Believability | Calculation of trust value for Apertium RDF OC-ES took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-oc-es took 5.681720495223999s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 4.6253204345703125e-05s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.0003788471221923828s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 0.26079726219177246s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.02072000503540039s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 4.863739013671875e-05s
Believability | Calculation of trust value for Apertium RDF PT-CA took 1.5020370483398438e-05s
INFO | --- Analysis for apertium-rdf-pt-ca took 5.904594659805298s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 4.887580871582031e-05s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.0006470680236816406s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.27105045318603516s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.020476341247558594s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 4.9114227294921875e-05s
Believability | Calculation of trust value for Apertium RDF PT-GL took 8.344650268554688e-06s
INFO | --- Analysis for apertium-rdf-pt-gl took 6.3130059242248535s
Availability | SPARQL endpoint availability check for AragoDBPedia took 0.8532884120941162s
Availability | VoID file availability check for AragoDBPedia took 0.0006642341613769531s
Extra | Recovery of all triples for AragoDBPedia took 3.5159525871276855s
Performance | Total latancy measurement for AragoDBPedia took 1.9611611366271973s
Amount of data | Number of triples check for AragoDBPedia took 0.9122312068939209s
Interoperability | New terms check for AragoDBPedia took 2.294538736343384s
Versatility | Languages check for AragoDBPedia took 60.492889165878296s
Interpretability | Number of blank nodes check for AragoDBPedia took 5.106242895126343s
Security | Check HTTPS for AragoDBPedia took 0.3021829128265381s
Interpretability | RDF structures check for AragoDBPedia took 0.8361313343048096s
Versatility | Serialization formats check for AragoDBPedia took 0.9142329692840576s
Availability | RDF dump link check for AragoDBPedia took 0.43143153190612793s
License | MR license check for AragoDBPedia took 0.7213141918182373s
License | HR license check for AragoDBPedia took 6.67190146446228s
Amount of data | Number of property check for AragoDBPedia took 0.41851282119750977s
Understandability | Number of label check for AragoDBPedia took 0.5759403705596924s
Understandability | URI regex check for AragoDBPedia took 0.9469234943389893s
Understandability | Vocabs check for AragoDBPedia took 0.43111705780029297s
Verifiability | Authors check for AragoDBPedia took 0.5204606056213379s
Verifiability | Publishers check for AragoDBPedia took 0.44896697998046875s
Performance | Throughput check for AragoDBPedia took 12.083610534667969s
Amount of data | Check the number of entities for AragoDBPedia took 3.218650817871094e-05s
Verifiability | Contribs. check for AragoDBPedia took 0.48520660400390625s
Interlinking | sameAs chians check for AragoDBPedia took 0.46253323554992676s
Interlinking | skos check for AragoDBPedia took 0.5372889041900635s
Interlinking | skos check for AragoDBPedia took 0.3667120933532715s
Timeliness | dataset update frequency check for AragoDBPedia took 0.5148470401763916s
Currency | Creation date check for AragoDBPedia took 2.0247743129730225s
Currency | Modification date check for AragoDBPedia took 0.46187520027160645s
Rep.Conc. | URIs length for AragoDBPedia took 5.847527027130127s
Interoperability | New vocabularies check for AragoDBPedia took 4.76837158203125e-06s
Consistency | Deprecated classes/propertiers check for AragoDBPedia took 0.4411463737487793s
Accuracy | Check Functional Property for AragoDBPedia took 0.5338945388793945s
Accuracy | Check Inverse Functional Property for AragoDBPedia took 0.49806690216064453s
Accuracy | Check Empty annotation labels for AragoDBPedia took 1.5177712440490723s
Accuracy | Check White space in annotation for AragoDBPedia took 0.030773639678955078s
Accuracy | Check Datatype consistency for AragoDBPedia took 0.030278682708740234s
Consistency | Disjoint class check for AragoDBPedia took 0.5024371147155762s
Consistency | Check Misplaced properties for AragoDBPedia took 4.775920391082764s
Consistency | Misplaced classes for AragoDBPedia took 0.7285511493682861s
Consistency | Check Ontology hijacking for AragoDBPedia took 2.670498847961426s
Consistency | Check Invalid usage of undefined classes for AragoDBPedia took 1.3789358139038086s
Consistency | Check Invalid usage of undefined properties for AragoDBPedia took 5.58600115776062s
Conciseness | Check Extensional conciseness for AragoDBPedia took 0.03373217582702637s
Conciseness | Check Intensional conciseness for AragoDBPedia took 0.6450610160827637s
Security | Sign check for AragoDBPedia took 0.5557360649108887s
Availability | Check URIs Dereferenciability for AragoDBPedia took 3350.503623485565s
Completeness | Calculation of interlinking completeness for AragoDBPedia took 1.4726297855377197s
Reputation | Calculation of the PageRank for AragoDBPedia took 0.025304555892944336s
Interlinking | Calculation of Degree of Connection for AragoDBPedia took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for AragoDBPedia took 0.0012540817260742188s
Interlinking | Calculation of Clustering coefficient for AragoDBPedia took 0.00013709068298339844s
Interoperability | Check the re-using of existing vocabs for AragoDBPedia took 3.337860107421875e-06s
Believability | Calculation of trust value for AragoDBPedia took 6.198883056640625e-06s
INFO | --- Analysis for aragodbpedia took 39402.278710365295s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 30.480422258377075s
Availability | VoID file availability check for Archives Hub Linked Data took 0.0006806850433349609s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.7198724746704102s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.0202789306640625s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 5.602836608886719e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for archiveshub-linkeddata took 86.12449622154236s
Availability | SPARQL endpoint availability check for Archivi ISMA took 4.172325134277344e-05s
Availability | VoID file availability check for Archivi ISMA took 0.00035452842712402344s
Completeness | Calculation of interlinking completeness for Archivi ISMA took 0.2837843894958496s
Reputation | Calculation of the PageRank for Archivi ISMA took 0.023959636688232422s
Interlinking | Calculation of Degree of Connection for Archivi ISMA took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Archivi ISMA took 0.001222372055053711s
Interlinking | Calculation of Clustering coefficient for Archivi ISMA took 4.363059997558594e-05s
Believability | Calculation of trust value for Archivi ISMA took 9.298324584960938e-06s
INFO | --- Analysis for archivio-isma took 4.724622011184692s
Availability | SPARQL endpoint availability check for ARIADNE took 6.556510925292969e-05s
Availability | VoID file availability check for ARIADNE took 0.00041937828063964844s
Completeness | Calculation of interlinking completeness for ARIADNE took 0.2644639015197754s
Reputation | Calculation of the PageRank for ARIADNE took 0.02485036849975586s
Interlinking | Calculation of Degree of Connection for ARIADNE took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for ARIADNE took 0.0012068748474121094s
Interlinking | Calculation of Clustering coefficient for ARIADNE took 4.6253204345703125e-05s
Believability | Calculation of trust value for ARIADNE took 9.059906005859375e-06s
INFO | --- Analysis for ariadne took 3.3967058658599854s
Availability | SPARQL endpoint availability check for Aristotle University took 4.100799560546875e-05s
Availability | VoID file availability check for Aristotle University took 0.0003514289855957031s
Completeness | Calculation of interlinking completeness for Aristotle University took 0.24537897109985352s
Reputation | Calculation of the PageRank for Aristotle University took 0.024003267288208008s
Interlinking | Calculation of Degree of Connection for Aristotle University took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Aristotle University took 0.0012331008911132812s
Interlinking | Calculation of Clustering coefficient for Aristotle University took 6.4849853515625e-05s
Believability | Calculation of trust value for Aristotle University took 8.344650268554688e-06s
INFO | --- Analysis for aristotle-university took 3.4228808879852295s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 4.362664461135864s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.0006754398345947266s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 0.2654235363006592s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.024245023727416992s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0012042522430419922s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 4.363059997558594e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 9.5367431640625e-06s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 18.040636777877808s
Availability | SPARQL endpoint availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 4.172325134277344e-05s
Availability | VoID file availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.00035691261291503906s
Completeness | Calculation of interlinking completeness for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.26827073097229004s
Reputation | Calculation of the PageRank for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.02419281005859375s
Interlinking | Calculation of Degree of Connection for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0012640953063964844s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 4.458427429199219e-05s
Believability | Calculation of trust value for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 8.106231689453125e-06s
INFO | --- Analysis for arrayexpress_e-afmx-4 took 3.8795578479766846s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 2.943183422088623s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0006914138793945312s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.26844263076782227s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.020590782165527344s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 4.00543212890625e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 6.198883056640625e-06s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 14.844067573547363s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 4.172325134277344e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0006639957427978516s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.2640054225921631s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.020266056060791016s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.000102996826171875s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 7.3909759521484375e-06s
INFO | --- Analysis for artenuevosmedios-gnoss took 8.197184562683105s
Availability | SPARQL endpoint availability check for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 7.867813110351562e-05s
Availability | VoID file availability check for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.260481595993042s
Reputation | Calculation of the PageRank for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.020601272583007812s
Interlinking | Calculation of Degree of Connection for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 1.4066696166992188e-05s
Believability | Calculation of trust value for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 7.3909759521484375e-06s
INFO | --- Analysis for Arthron took 2.4005513191223145s
Availability | SPARQL endpoint availability check for Arthroscopy community took 4.076957702636719e-05s
Availability | VoID file availability check for Arthroscopy community took 0.0006070137023925781s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 0.2872316837310791s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.020327091217041016s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 0.00010085105895996094s
Believability | Calculation of trust value for Arthroscopy community took 7.152557373046875e-06s
INFO | --- Analysis for arthroscopy took 2.9840919971466064s
Availability | SPARQL endpoint availability check for Wikidata entry for Art × Science International took 33.224419593811035s
Availability | VoID file availability check for Wikidata entry for Art × Science International took 0.0006320476531982422s
Extra | Recovery of all triples for Wikidata entry for Art × Science International took 0.13475751876831055s
Amount of data | Number of triples check for Wikidata entry for Art × Science International took 0.14246869087219238s
Versatility | Languages check for Wikidata entry for Art × Science International took 0.14726686477661133s
Interpretability | Number of blank nodes check for Wikidata entry for Art × Science International took 0.1478133201599121s
Interpretability | RDF structures check for Wikidata entry for Art × Science International took 0.1364591121673584s
Versatility | Serialization formats check for Wikidata entry for Art × Science International took 0.12910056114196777s
Availability | RDF dump link check for Wikidata entry for Art × Science International took 0.13552045822143555s
License | MR license check for Wikidata entry for Art × Science International took 0.1267693042755127s
License | HR license check for Wikidata entry for Art × Science International took 0.1354222297668457s
Amount of data | Number of property check for Wikidata entry for Art × Science International took 0.13625621795654297s
Understandability | Number of label check for Wikidata entry for Art × Science International took 0.13653349876403809s
Understandability | URI regex check for Wikidata entry for Art × Science International took 0.2721407413482666s
Understandability | Vocabs check for Wikidata entry for Art × Science International took 0.1373119354248047s
Verifiability | Authors check for Wikidata entry for Art × Science International took 0.13695216178894043s
Verifiability | Publishers check for Wikidata entry for Art × Science International took 0.12757301330566406s
Amount of data | Check the number of entities for Wikidata entry for Art × Science International took 0.0001361370086669922s
Verifiability | Contribs. check for Wikidata entry for Art × Science International took 0.13599228858947754s
Interlinking | sameAs chians check for Wikidata entry for Art × Science International took 0.14900875091552734s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.13616013526916504s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.14014363288879395s
Timeliness | dataset update frequency check for Wikidata entry for Art × Science International took 0.15361356735229492s
Currency | Creation date check for Wikidata entry for Art × Science International took 0.2843739986419678s
Currency | Modification date check for Wikidata entry for Art × Science International took 0.2550187110900879s
Rep.Conc. | URIs length for Wikidata entry for Art × Science International took 0.2780933380126953s
Interoperability | New vocabularies check for Wikidata entry for Art × Science International took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for Wikidata entry for Art × Science International took 0.12804555892944336s
Consistency | Disjoint class check for Wikidata entry for Art × Science International took 0.13799238204956055s
Consistency | Check Ontology hijacking for Wikidata entry for Art × Science International took 0.13669538497924805s
Consistency | Check Invalid usage of undefined properties for Wikidata entry for Art × Science International took 1.5357425212860107s
Conciseness | Check Extensional conciseness for Wikidata entry for Art × Science International took 0.0006008148193359375s
Security | Sign check for Wikidata entry for Art × Science International took 0.13863444328308105s
Completeness | Calculation of interlinking completeness for Wikidata entry for Art × Science International took 0.2767972946166992s
Reputation | Calculation of the PageRank for Wikidata entry for Art × Science International took 0.020183563232421875s
Interlinking | Calculation of Degree of Connection for Wikidata entry for Art × Science International took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Wikidata entry for Art × Science International took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Wikidata entry for Art × Science International took 1.2874603271484375e-05s
Interoperability | Check the re-using of existing vocabs for Wikidata entry for Art × Science International took 4.76837158203125e-07s
Believability | Calculation of trust value for Wikidata entry for Art × Science International took 8.58306884765625e-06s
INFO | --- Analysis for artxscienceinternational-wikidata took 56.375109910964966s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 2.3617560863494873s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0006527900695800781s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.2787497043609619s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.020177841186523438s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 7.534027099609375e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 6.9141387939453125e-06s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 10.148482084274292s
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 1.7692654132843018s
Availability | VoID file availability check for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 0.26146697998046875s
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.020417213439941406s
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.1920928955078125e-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.0007474422454833984s
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.534027099609375e-05s
Believability | Calculation of trust value for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 8.344650268554688e-06s
INFO | --- Analysis for ASCDC-AS-NTUE-School-Art-Textbooks took 9.141727924346924s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.0138583183288574s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0007202625274658203s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.28813958168029785s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.020207643508911133s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 8.821487426757812e-05s
Believability | Calculation of trust value for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 7.3909759521484375e-06s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 8.401195526123047s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 1.3990726470947266s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.0006115436553955078s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 0.3777921199798584s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.020150184631347656s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 4.00543212890625e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 6.67572021484375e-06s
INFO | --- Analysis for ASCDC-CRB took 10.29298734664917s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.8740310668945312s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0006482601165771484s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.2531266212463379s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.02008795738220215s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.00010418891906738281s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 8.344650268554688e-06s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 8.048550605773926s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 0.9548044204711914s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.0006103515625s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 0.2747001647949219s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.020064115524291992s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 3.4332275390625e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 7.62939453125e-06s
INFO | --- Analysis for ASCDC-DQOT took 8.545982360839844s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.9372644424438477s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0007169246673583984s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.2790799140930176s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.02039170265197754s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0008661746978759766s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 8.606910705566406e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 7.3909759521484375e-06s
INFO | --- Analysis for ASCDC-IHP-WCD took 7.594923496246338s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 2.2508184909820557s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.000682830810546875s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 0.27754712104797363s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.020377635955810547s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 8.20159912109375e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 7.152557373046875e-06s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 10.94640851020813s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.8926055431365967s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0006778240203857422s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.2654130458831787s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0204160213470459s
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.0967254638671875e-05s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 5.3882598876953125e-05s
Believability | Calculation of trust value for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 7.867813110351562e-06s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 8.502161979675293s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.8893046379089355s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0006921291351318359s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.2689783573150635s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.025339603424072266s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 3.933906555175781e-05s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0012593269348144531s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 7.43865966796875e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 8.821487426757812e-06s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 7.259929656982422s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 7.107495307922363s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.00035071372985839844s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.26938438415527344s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.024223804473876953s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0012345314025878906s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 6.175041198730469e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 7.867813110351562e-06s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 9.895591020584106s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.9011349678039551s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0006024837493896484s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.28732752799987793s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.024793624877929688s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0012516975402832031s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.00010347366333007812s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 8.106231689453125e-06s
INFO | --- Analysis for ASCDC-Tibetan-Audio-Archive took 7.605395317077637s
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 0.9924838542938232s
Availability | VoID file availability check for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 0.0006415843963623047s
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.26570725440979004s
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.024320125579833984s
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.7881393432617188e-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.0013973712921142578s
Interlinking | Calculation of Clustering coefficient for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 0.00010824203491210938s
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.3909759521484375e-06s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 8.606177806854248s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 0.8469038009643555s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.00063323974609375s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 0.264784574508667s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.025016069412231445s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0012371540069580078s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 6.389617919921875e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 9.298324584960938e-06s
INFO | --- Analysis for ASCDC_-_DNB took 6.281318426132202s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 4.363059997558594e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 0.0005888938903808594s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 0.2758634090423584s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.025270938873291016s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.001220703125s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 8.916854858398438e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 9.059906005859375e-06s
INFO | --- Analysis for asit took 6.614442348480225s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 6.0558319091796875e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.0007243156433105469s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.2613856792449951s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.025205135345458984s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0012822151184082031s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 5.650520324707031e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 8.58306884765625e-06s
INFO | --- Analysis for asjp took 4.887530326843262s
Availability | SPARQL endpoint availability check for ASN:US took 524.5648169517517s
Availability | VoID file availability check for ASN:US took 0.0009441375732421875s
Completeness | Calculation of interlinking completeness for ASN:US took 0.7099506855010986s
Reputation | Calculation of the PageRank for ASN:US took 0.026740074157714844s
Interlinking | Calculation of Degree of Connection for ASN:US took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for ASN:US took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for ASN:US took 7.343292236328125e-05s
Believability | Calculation of trust value for ASN:US took 1.3589859008789062e-05s
INFO | --- Analysis for asn-us took 1341.8206112384796s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 4.315376281738281e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.0006301403045654297s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.26404571533203125s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.020874977111816406s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 3.218650817871094e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 5.7220458984375e-06s
INFO | --- Analysis for aspire-mmu took 8.719780683517456s
Availability | SPARQL endpoint availability check for associations took 4.172325134277344e-05s
Availability | VoID file availability check for associations took 0.0006582736968994141s
Completeness | Calculation of interlinking completeness for associations took 0.7024564743041992s
Reputation | Calculation of the PageRank for associations took 0.02025318145751953s
Interlinking | Calculation of Degree of Connection for associations took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for associations took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for associations took 6.937980651855469e-05s
Believability | Calculation of trust value for associations took 6.9141387939453125e-06s
INFO | --- Analysis for associations took 9.659734964370728s
Availability | SPARQL endpoint availability check for ATC publikovaná SÚKL took 7.176399230957031e-05s
Availability | VoID file availability check for ATC publikovaná SÚKL took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for ATC publikovaná SÚKL took 0.2579689025878906s
Reputation | Calculation of the PageRank for ATC publikovaná SÚKL took 0.020212411880493164s
Interlinking | Calculation of Degree of Connection for ATC publikovaná SÚKL took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ATC publikovaná SÚKL took 0.0009407997131347656s
Interlinking | Calculation of Clustering coefficient for ATC publikovaná SÚKL took 3.2901763916015625e-05s
Believability | Calculation of trust value for ATC publikovaná SÚKL took 6.9141387939453125e-06s
INFO | --- Analysis for atc-publikovan--s-kl took 3.3514304161071777s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 4.220008850097656e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.0005614757537841797s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 0.24866843223571777s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.020190715789794922s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0009217262268066406s
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 6.9141387939453125e-06s
INFO | --- Analysis for athelia-rfid took 4.9752631187438965s
Availability | SPARQL endpoint availability check for AuditSocials Social Media Advertising Compliance Glossary took 7.128715515136719e-05s
Availability | VoID file availability check for AuditSocials Social Media Advertising Compliance Glossary took 0.0006325244903564453s
Completeness | Calculation of interlinking completeness for AuditSocials Social Media Advertising Compliance Glossary took 0.2612597942352295s
Reputation | Calculation of the PageRank for AuditSocials Social Media Advertising Compliance Glossary took 0.020012617111206055s
Interlinking | Calculation of Degree of Connection for AuditSocials Social Media Advertising Compliance Glossary took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for AuditSocials Social Media Advertising Compliance Glossary took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for AuditSocials Social Media Advertising Compliance Glossary took 1.1682510375976562e-05s
Believability | Calculation of trust value for AuditSocials Social Media Advertising Compliance Glossary took 7.152557373046875e-06s
INFO | --- Analysis for auditsocials-glossary took 4.981912612915039s
Availability | SPARQL endpoint availability check for AUEB Linked Open Data took 4.100799560546875e-05s
Availability | VoID file availability check for AUEB Linked Open Data took 0.00028967857360839844s
Completeness | Calculation of interlinking completeness for AUEB Linked Open Data took 0.24173307418823242s
Reputation | Calculation of the PageRank for AUEB Linked Open Data took 0.020273685455322266s
Interlinking | Calculation of Degree of Connection for AUEB Linked Open Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for AUEB Linked Open Data took 0.0009090900421142578s
Interlinking | Calculation of Clustering coefficient for AUEB Linked Open Data took 3.314018249511719e-05s
Believability | Calculation of trust value for AUEB Linked Open Data took 6.67572021484375e-06s
INFO | --- Analysis for aueb-linked-open-data took 2.941671371459961s
Availability | SPARQL endpoint availability check for Augustini Confessiones in LiLa took 0.5626442432403564s
Availability | VoID file availability check for Augustini Confessiones in LiLa took 0.0007040500640869141s
Completeness | Calculation of interlinking completeness for Augustini Confessiones in LiLa took 0.271625280380249s
Reputation | Calculation of the PageRank for Augustini Confessiones in LiLa took 0.020000696182250977s
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.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for Augustini Confessiones in LiLa took 4.696846008300781e-05s
Believability | Calculation of trust value for Augustini Confessiones in LiLa took 6.9141387939453125e-06s
INFO | --- Analysis for AugustiniConfessiones took 3.9169936180114746s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 0.6388494968414307s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.2753112316131592s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.020427465438842773s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Alpine Ski Racers of Austria took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 8.821487426757812e-05s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 6.9141387939453125e-06s
INFO | --- Analysis for austrian_ski_racers took 4.2102861404418945s
Availability | SPARQL endpoint availability check for AVsOnto took 4.124641418457031e-05s
Availability | VoID file availability check for AVsOnto took 0.0006062984466552734s
Completeness | Calculation of interlinking completeness for AVsOnto took 0.280989408493042s
Reputation | Calculation of the PageRank for AVsOnto took 0.020040273666381836s
Interlinking | Calculation of Degree of Connection for AVsOnto took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for AVsOnto took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for AVsOnto took 2.8371810913085938e-05s
Believability | Calculation of trust value for AVsOnto took 6.9141387939453125e-06s
INFO | --- Analysis for AVsOnto took 3.804083824157715s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.34221696853637695s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0005288124084472656s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 170.81026577949524s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.5436270236968994s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.10390734672546s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.04517245292663574s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.04552721977233887s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.04569435119628906s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.04954385757446289s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0490117073059082s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.04889869689941406s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.045397043228149414s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0416874885559082s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.045798301696777344s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.08637499809265137s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.04509115219116211s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.045318603515625s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.04886794090270996s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.00011706352233886719s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.045334815979003906s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.04945087432861328s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.04618501663208008s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.04913520812988281s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.04547381401062012s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.7162680625915527s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.34050989151000977s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 681.5073165893555s
Interoperability | New vocabularies check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2313089370727539s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 31.273959159851074s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.20857310295105s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.892214059829712s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.13524317741394043s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.2208106517792s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 60.46455216407776s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.6999497413635254s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 301.50180745124817s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.8517158031463623s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.14915108680725098s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.0766754150390625s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.258378028869629s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.026495695114135742s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.271766662597656e-05s
Interoperability | Check the re-using of existing vocabs for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.152557373046875e-07s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 5.4836273193359375e-06s
INFO | --- Analysis for b3kat took 2535.6863412857056s
Availability | SPARQL endpoint availability check for BabelNet took 0.6253681182861328s
Availability | VoID file availability check for BabelNet took 0.0007050037384033203s
Completeness | Calculation of interlinking completeness for BabelNet took 0.7192320823669434s
Reputation | Calculation of the PageRank for BabelNet took 0.02136397361755371s
Interlinking | Calculation of Degree of Connection for BabelNet took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for BabelNet took 0.0021805763244628906s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.00019693374633789062s
Believability | Calculation of trust value for BabelNet took 7.62939453125e-06s
INFO | --- Analysis for babelnet took 6.768915414810181s
Availability | SPARQL endpoint availability check for Bacevicius.lt took 4.172325134277344e-05s
Availability | VoID file availability check for Bacevicius.lt took 0.0003972053527832031s
Completeness | Calculation of interlinking completeness for Bacevicius.lt took 0.24729394912719727s
Reputation | Calculation of the PageRank for Bacevicius.lt took 0.02032947540283203s
Interlinking | Calculation of Degree of Connection for Bacevicius.lt took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bacevicius.lt took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Bacevicius.lt took 3.0517578125e-05s
Believability | Calculation of trust value for Bacevicius.lt took 6.9141387939453125e-06s
INFO | --- Analysis for Bacevicius.lt took 4.161616802215576s
Availability | SPARQL endpoint availability check for Basisregistratie Adressen en Gebouwen took 0.5939383506774902s
Availability | VoID file availability check for Basisregistratie Adressen en Gebouwen took 0.0005402565002441406s
Completeness | Calculation of interlinking completeness for Basisregistratie Adressen en Gebouwen took 0.2727794647216797s
Reputation | Calculation of the PageRank for Basisregistratie Adressen en Gebouwen took 0.020356416702270508s
Interlinking | Calculation of Degree of Connection for Basisregistratie Adressen en Gebouwen took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Basisregistratie Adressen en Gebouwen took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Basisregistratie Adressen en Gebouwen took 4.363059997558594e-05s
Believability | Calculation of trust value for Basisregistratie Adressen en Gebouwen took 1.3589859008789062e-05s
INFO | --- Analysis for bag took 4.485836029052734s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 0.88802170753479s
Availability | VoID file availability check for 红色经典歌曲 took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.259554386138916s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020487308502197266s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.075599670410156e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 8.821487426757812e-06s
INFO | --- Analysis for baixue took 3.35233211517334s
Availability | SPARQL endpoint availability check for baixue composer took 4.1961669921875e-05s
Availability | VoID file availability check for baixue composer took 0.0006878376007080078s
Completeness | Calculation of interlinking completeness for baixue composer took 0.28156352043151855s
Reputation | Calculation of the PageRank for baixue composer took 0.020909547805786133s
Interlinking | Calculation of Degree of Connection for baixue composer took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for baixue composer took 0.0008814334869384766s
Interlinking | Calculation of Clustering coefficient for baixue composer took 3.6716461181640625e-05s
Believability | Calculation of trust value for baixue composer took 8.106231689453125e-06s
INFO | --- Analysis for baixue_composer took 2.9187769889831543s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 7.128715515136719e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0006146430969238281s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.28624916076660156s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020404577255249023s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.218650817871094e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 7.3909759521484375e-06s
INFO | --- Analysis for baixue_imagery took 3.164851188659668s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 4.458427429199219e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0006396770477294922s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.2764394283294678s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020235061645507812s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.0517578125e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 7.152557373046875e-06s
INFO | --- Analysis for baixue_imagery1 took 3.6371235847473145s
Availability | SPARQL endpoint availability check for BAMS took 3.886222839355469e-05s
Availability | VoID file availability check for BAMS took 0.0003833770751953125s
Completeness | Calculation of interlinking completeness for BAMS took 0.27483558654785156s
Reputation | Calculation of the PageRank for BAMS took 0.020278453826904297s
Interlinking | Calculation of Degree of Connection for BAMS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BAMS took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for BAMS took 3.170967102050781e-05s
Believability | Calculation of trust value for BAMS took 8.106231689453125e-06s
INFO | --- Analysis for bams took 2.933284282684326s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 4.410743713378906e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.0006098747253417969s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 0.2605414390563965s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.02422499656677246s
Interlinking | Calculation of Degree of Connection for Basque EuroWordNet-lemon lexicon (3.0) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Basque EuroWordNet-lemon lexicon (3.0) took 0.0008127689361572266s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 4.696846008300781e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 7.867813110351562e-06s
INFO | --- Analysis for basque-eurowordnet-lemon-lexicon-3-0 took 3.127764940261841s
Availability | SPARQL endpoint availability check for BBC Music took 0.31935715675354004s
Availability | VoID file availability check for BBC Music took 0.0014383792877197266s
Completeness | Calculation of interlinking completeness for BBC Music took 0.24489474296569824s
Reputation | Calculation of the PageRank for BBC Music took 0.020276308059692383s
Interlinking | Calculation of Degree of Connection for BBC Music took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BBC Music took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.0001239776611328125s
Believability | Calculation of trust value for BBC Music took 7.62939453125e-06s
INFO | --- Analysis for bbc-music took 3.3605709075927734s
Availability | SPARQL endpoint availability check for BBC Programmes took 0.24434661865234375s
Availability | VoID file availability check for BBC Programmes took 0.0006096363067626953s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.69577956199646s
Reputation | Calculation of the PageRank for BBC Programmes took 0.020184040069580078s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 0.00010156631469726562s
Believability | Calculation of trust value for BBC Programmes took 7.62939453125e-06s
INFO | --- Analysis for bbc-programmes took 10.957424402236938s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.3719961643218994s
Availability | VoID file availability check for BBC Wildlife Finder took 0.0006480216979980469s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 0.280519962310791s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.0202333927154541s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 0.00011205673217773438s
Believability | Calculation of trust value for BBC Wildlife Finder took 7.62939453125e-06s
INFO | --- Analysis for bbc-wildlife-finder took 8.6645987033844s
Availability | SPARQL endpoint availability check for BBOP took 5.435943603515625e-05s
Availability | VoID file availability check for BBOP took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for BBOP took 0.251300573348999s
Reputation | Calculation of the PageRank for BBOP took 0.020132780075073242s
Interlinking | Calculation of Degree of Connection for BBOP took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for BBOP took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for BBOP took 2.8848648071289062e-05s
Believability | Calculation of trust value for BBOP took 6.67572021484375e-06s
INFO | --- Analysis for bbop took 2.9045066833496094s
Availability | SPARQL endpoint availability check for BBOP took 4.076957702636719e-05s
Availability | VoID file availability check for BBOP took 0.0009286403656005859s
Completeness | Calculation of interlinking completeness for BBOP took 0.27232956886291504s
Reputation | Calculation of the PageRank for BBOP took 0.020177602767944336s
Interlinking | Calculation of Degree of Connection for BBOP took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BBOP took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for BBOP took 2.86102294921875e-05s
Believability | Calculation of trust value for BBOP took 6.67572021484375e-06s
INFO | --- Analysis for bbop-selected took 19.45577359199524s
Availability | SPARQL endpoint availability check for Bdgp took 1.6183757781982422s
Availability | VoID file availability check for Bdgp took 0.0005140304565429688s
Completeness | Calculation of interlinking completeness for Bdgp took 0.2618262767791748s
Reputation | Calculation of the PageRank for Bdgp took 0.020453929901123047s
Interlinking | Calculation of Degree of Connection for Bdgp took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bdgp took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Bdgp took 2.86102294921875e-05s
Believability | Calculation of trust value for Bdgp took 6.9141387939453125e-06s
INFO | --- Analysis for bdgp took 8.437558889389038s
Availability | SPARQL endpoint availability check for Bendev Junior took 4.0531158447265625e-05s
Availability | VoID file availability check for Bendev Junior took 0.0005488395690917969s
Completeness | Calculation of interlinking completeness for Bendev Junior took 0.29871487617492676s
Reputation | Calculation of the PageRank for Bendev Junior took 0.020157575607299805s
Interlinking | Calculation of Degree of Connection for Bendev Junior took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Bendev Junior took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Bendev Junior took 3.0040740966796875e-05s
Believability | Calculation of trust value for Bendev Junior took 6.9141387939453125e-06s
INFO | --- Analysis for bendevoficial took 5.436323881149292s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 4.518123149871826s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.0006246566772460938s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.2807178497314453s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.02033853530883789s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 6.651878356933594e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 4.76837158203125e-06s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 12.493497371673584s
Availability | SPARQL endpoint availability check for Berlin Offener Haushalt took 3.8623809814453125e-05s
Availability | VoID file availability check for Berlin Offener Haushalt took 0.00022745132446289062s
Completeness | Calculation of interlinking completeness for Berlin Offener Haushalt took 0.2735590934753418s
Reputation | Calculation of the PageRank for Berlin Offener Haushalt took 0.02043437957763672s
Interlinking | Calculation of Degree of Connection for Berlin Offener Haushalt took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Berlin Offener Haushalt took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Berlin Offener Haushalt took 2.86102294921875e-05s
Believability | Calculation of trust value for Berlin Offener Haushalt took 6.4373016357421875e-06s
INFO | --- Analysis for berlin-offener-haushalt took 3.3642635345458984s
Availability | SPARQL endpoint availability check for berlios took 4.076957702636719e-05s
Availability | VoID file availability check for berlios took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for berlios took 0.255842924118042s
Reputation | Calculation of the PageRank for berlios took 0.020169496536254883s
Interlinking | Calculation of Degree of Connection for berlios took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for berlios took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for berlios took 8.58306884765625e-05s
Believability | Calculation of trust value for berlios took 6.67572021484375e-06s
INFO | --- Analysis for berlios took 2.6164658069610596s
Availability | SPARQL endpoint availability check for Between Our Worlds took 4.124641418457031e-05s
Availability | VoID file availability check for Between Our Worlds took 0.0006074905395507812s
Completeness | Calculation of interlinking completeness for Between Our Worlds took 0.3278496265411377s
Reputation | Calculation of the PageRank for Between Our Worlds took 0.020336389541625977s
Interlinking | Calculation of Degree of Connection for Between Our Worlds took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Between Our Worlds took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for Between Our Worlds took 7.009506225585938e-05s
Believability | Calculation of trust value for Between Our Worlds took 8.344650268554688e-06s
INFO | --- Analysis for betweenourworlds took 9.146004915237427s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.3448355197906494s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.2755398750305176s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.020270824432373047s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 8.749961853027344e-05s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 4.76837158203125e-06s
INFO | --- Analysis for bfs-linked-data took 2.9110279083251953s
Availability | SPARQL endpoint availability check for BibBase took 0.08892703056335449s
Availability | VoID file availability check for BibBase took 0.00045371055603027344s
Completeness | Calculation of interlinking completeness for BibBase took 0.26278018951416016s
Reputation | Calculation of the PageRank for BibBase took 0.020388126373291016s
Interlinking | Calculation of Degree of Connection for BibBase took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BibBase took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for BibBase took 9.489059448242188e-05s
Believability | Calculation of trust value for BibBase took 6.9141387939453125e-06s
INFO | --- Analysis for bibbase took 2.536724805831909s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 4.029273986816406e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.2793600559234619s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.020288705825805664s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 0.00011467933654785156s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 6.4373016357421875e-06s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 6.515296936035156s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 4.00543212890625e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.25319576263427734s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.020221471786499023s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 9.679794311523438e-05s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 6.9141387939453125e-06s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 3.076047658920288s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 4.00543212890625e-05s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.2985103130340576s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.020261764526367188s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 3.0279159545898438e-05s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 3.504753112792969e-05s
INFO | --- Analysis for biblioteca-virtual-miguel-de-cervantes-bvmc-linked-open-data took 2.9519684314727783s
Availability | SPARQL endpoint availability check for BibSonomy - The blue social bookmark and publication sharing system. took 4.1484832763671875e-05s
Availability | VoID file availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.0006361007690429688s
Completeness | Calculation of interlinking completeness for BibSonomy - The blue social bookmark and publication sharing system. took 0.2765953540802002s
Reputation | Calculation of the PageRank for BibSonomy - The blue social bookmark and publication sharing system. took 0.020195484161376953s
Interlinking | Calculation of Degree of Connection for BibSonomy - The blue social bookmark and publication sharing system. took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for BibSonomy - The blue social bookmark and publication sharing system. took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for BibSonomy - The blue social bookmark and publication sharing system. took 3.552436828613281e-05s
Believability | Calculation of trust value for BibSonomy - The blue social bookmark and publication sharing system. took 6.67572021484375e-06s
INFO | --- Analysis for BibSonomy took 7.981821060180664s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 4.1484832763671875e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.0005562305450439453s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.2714214324951172s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.020267248153686523s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 2.956390380859375e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 6.67572021484375e-06s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 5.112379789352417s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 5.2928924560546875e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.0005619525909423828s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 0.2587568759918213s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.02030205726623535s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2010 took 3.123283386230469e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2010 took 6.4373016357421875e-06s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 2.6666853427886963s
Availability | SPARQL endpoint availability check for Bio2RDF::ACFSID took 6.365776062011719e-05s
Availability | VoID file availability check for Bio2RDF::ACFSID took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for Bio2RDF::ACFSID took 0.2528359889984131s
Reputation | Calculation of the PageRank for Bio2RDF::ACFSID took 0.020406723022460938s
Interlinking | Calculation of Degree of Connection for Bio2RDF::ACFSID took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::ACFSID took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::ACFSID took 2.8848648071289062e-05s
Believability | Calculation of trust value for Bio2RDF::ACFSID took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-acfsid took 2.940112590789795s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 60.04936766624451s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.0006716251373291016s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 0.3623805046081543s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.020543575286865234s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 9.584426879882812e-05s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-affymetrix took 242.7288703918457s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 60.05579209327698s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.0007216930389404297s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 0.3399522304534912s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.020468950271606445s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.00011372566223144531s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-biomodels took 264.1263508796692s
Availability | SPARQL endpoint availability check for Bio2RDF::BioModels::BioPAX took 4.029273986816406e-05s
Availability | VoID file availability check for Bio2RDF::BioModels::BioPAX took 0.0003094673156738281s
Completeness | Calculation of interlinking completeness for Bio2RDF::BioModels::BioPAX took 0.7303416728973389s
Reputation | Calculation of the PageRank for Bio2RDF::BioModels::BioPAX took 0.020661592483520508s
Interlinking | Calculation of Degree of Connection for Bio2RDF::BioModels::BioPAX took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::BioModels::BioPAX took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::BioModels::BioPAX took 3.123283386230469e-05s
Believability | Calculation of trust value for Bio2RDF::BioModels::BioPAX took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-biomodels-biopax took 4.4873151779174805s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 60.05721592903137s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.0007205009460449219s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 0.8878991603851318s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.025452852249145508s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 3.933906555175781e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.0012755393981933594s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.0005118846893310547s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 9.059906005859375e-06s
INFO | --- Analysis for bio2rdf-bioportal took 447.9675211906433s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 60.059746980667114s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.0007369518280029297s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 0.8902266025543213s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.020886659622192383s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 5.936622619628906e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-chembl took 446.1272482872009s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 60.06135296821594s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.0006732940673828125s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 0.6763031482696533s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.020861148834228516s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 2.47955322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0009489059448242188s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 4.982948303222656e-05s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-clinicaltrials took 265.8943364620209s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 60.04994821548462s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.0007541179656982422s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 1.2387218475341797s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.021728515625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 3.4332275390625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 6.222724914550781e-05s
Believability | Calculation of trust value for Bio2RDF::Ctd took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-ctd took 446.8292946815491s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 4.124641418457031e-05s
Availability | VoID file availability check for bio2rdf-dataset took 0.0006153583526611328s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 0.2589547634124756s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.02020549774169922s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 4.482269287109375e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 6.67572021484375e-06s
INFO | --- Analysis for bio2rdf-dataset took 24.12520933151245s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 60.053765296936035s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.0007476806640625s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 0.749016284942627s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.020769596099853516s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 7.319450378417969e-05s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-dbsnp took 265.6711027622223s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 60.04624819755554s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.0006623268127441406s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 0.7026453018188477s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.020743846893310547s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.00011444091796875s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-drugbank took 285.14884209632874s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 60.04231858253479s
Availability | VoID file availability check for Bio2RDF::Genage took 0.0006961822509765625s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 0.2659757137298584s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.02585744857788086s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0009572505950927734s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 7.700920104980469e-05s
Believability | Calculation of trust value for Bio2RDF::Genage took 8.821487426757812e-06s
INFO | --- Analysis for bio2rdf-genage took 285.8025572299957s
Availability | SPARQL endpoint availability check for Bio2RDF::GenBank took 5.173683166503906e-05s
Availability | VoID file availability check for Bio2RDF::GenBank took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Bio2RDF::GenBank took 0.7187774181365967s
Reputation | Calculation of the PageRank for Bio2RDF::GenBank took 0.020267486572265625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::GenBank took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bio2RDF::GenBank took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::GenBank took 6.270408630371094e-05s
Believability | Calculation of trust value for Bio2RDF::GenBank took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-genbank took 4.7240376472473145s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 60.05218529701233s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.0007064342498779297s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 0.9102873802185059s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.020440101623535156s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 6.031990051269531e-05s
Believability | Calculation of trust value for Bio2RDF::Gendr took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-gendr took 287.10563373565674s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 60.04904317855835s
Availability | VoID file availability check for Bio2RDF::Goa took 0.0007727146148681641s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 0.7393574714660645s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.020982027053833008s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0008103847503662109s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 5.8650970458984375e-05s
Believability | Calculation of trust value for Bio2RDF::Goa took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-goa took 445.3199679851532s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 60.054264307022095s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.0007777214050292969s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 1.1953184604644775s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.024892091751098633s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 3.8623809814453125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.0012166500091552734s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.00017452239990234375s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-hgnc took 266.649533033371s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 60.05152654647827s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.0007567405700683594s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 0.3038454055786133s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.020923137664794922s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 5.936622619628906e-05s
Believability | Calculation of trust value for Bio2RDF::Homologene took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-homologene took 264.836124420166s
Availability | SPARQL endpoint availability check for Bio2RDF::INOH took 4.0531158447265625e-05s
Availability | VoID file availability check for Bio2RDF::INOH took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for Bio2RDF::INOH took 0.7607457637786865s
Reputation | Calculation of the PageRank for Bio2RDF::INOH took 0.020344018936157227s
Interlinking | Calculation of Degree of Connection for Bio2RDF::INOH took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::INOH took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::INOH took 3.218650817871094e-05s
Believability | Calculation of trust value for Bio2RDF::INOH took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-inoh took 3.959697961807251s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 60.054158210754395s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.0007359981536865234s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 0.31656813621520996s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.02060842514038086s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 0.00010657310485839844s
Believability | Calculation of trust value for Bio2RDF::Interpro took 6.67572021484375e-06s
INFO | --- Analysis for bio2rdf-interpro took 265.2276542186737s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 60.06136870384216s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.0007338523864746094s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 0.7517049312591553s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.020680904388427734s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 7.271766662597656e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-iproclass took 447.35601449012756s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 60.06140732765198s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.0007016658782958984s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 0.7570064067840576s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.020606517791748047s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 8.177757263183594e-05s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-irefindex took 265.170697927475s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG took 4.363059997558594e-05s
Availability | VoID file availability check for Bio2RDF::KEGG took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG took 0.2699732780456543s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG took 0.020292997360229492s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG took 6.079673767089844e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG took 9.298324584960938e-06s
INFO | --- Analysis for bio2rdf-kegg took 4.868200302124023s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG::BioPAX took 3.838539123535156e-05s
Availability | VoID file availability check for Bio2RDF::KEGG::BioPAX took 0.00023555755615234375s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG::BioPAX took 0.260861873626709s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG::BioPAX took 0.02025294303894043s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG::BioPAX took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG::BioPAX took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG::BioPAX took 3.337860107421875e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG::BioPAX took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-kegg-biopax took 3.4004852771759033s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 60.06119108200073s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.0007431507110595703s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 0.28975820541381836s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.020705223083496094s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 4.553794860839844e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-linkedspl took 266.0329806804657s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 60.060792446136475s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.0006971359252929688s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 0.7094664573669434s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.020639896392822266s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 4.839897155761719e-05s
Believability | Calculation of trust value for Bio2RDF::Lsr took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-lsr took 265.6354684829712s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 60.06132626533508s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.0004115104675292969s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 0.7465188503265381s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.020853042602539062s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 7.987022399902344e-05s
Believability | Calculation of trust value for Bio2RDF::Mesh took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-mesh took 305.2172055244446s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 60.051384687423706s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.0007417201995849609s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 0.7714247703552246s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.02096724510192871s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 9.5367431640625e-05s
Believability | Calculation of trust value for Bio2RDF::Mgi took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-mgi took 326.86141705513s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 60.06265211105347s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.0008199214935302734s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 0.7505054473876953s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.025531291961669922s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.00012493133544921875s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 5.7220458984375e-06s
INFO | --- Analysis for bio2rdf-ncbigene took 405.79573130607605s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 60.05936002731323s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.0006546974182128906s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 0.7400307655334473s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.020595312118530273s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 4.410743713378906e-05s
Believability | Calculation of trust value for Bio2RDF::Ndc took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-ndc took 265.0997910499573s
Availability | SPARQL endpoint availability check for Bio2RDF::NetPath took 3.9577484130859375e-05s
Availability | VoID file availability check for Bio2RDF::NetPath took 0.00028014183044433594s
Completeness | Calculation of interlinking completeness for Bio2RDF::NetPath took 0.2591078281402588s
Reputation | Calculation of the PageRank for Bio2RDF::NetPath took 0.020272016525268555s
Interlinking | Calculation of Degree of Connection for Bio2RDF::NetPath took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::NetPath took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::NetPath took 2.9802322387695312e-05s
Believability | Calculation of trust value for Bio2RDF::NetPath took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-netpath took 4.801419496536255s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 40.03913688659668s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.0005509853363037109s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.24368715286254883s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.02018117904663086s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 2.9087066650390625e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-nextprot took 122.86953902244568s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 60.05809950828552s
Availability | VoID file availability check for Bio2RDF::Omim took 0.0007634162902832031s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 0.7666268348693848s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.02037215232849121s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.00014066696166992188s
Believability | Calculation of trust value for Bio2RDF::Omim took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-omim took 265.6987705230713s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 4.00543212890625e-05s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.00039196014404296875s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.27432680130004883s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.020804643630981445s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 3.838539123535156e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-omim-resources took 22.452534675598145s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 60.05100774765015s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 0.7310185432434082s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.020756244659423828s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0008237361907958984s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 0.00010323524475097656s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-orphanet took 344.7604146003723s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 60.04650545120239s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.0007383823394775391s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 0.7373089790344238s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.020726919174194336s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 3.981590270996094e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-pathwaycommons took 267.31049609184265s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 60.05342149734497s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.0004036426544189453s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 1.2428045272827148s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.02490997314453125s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0007872581481933594s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 6.818771362304688e-05s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 1.0728836059570312e-05s
INFO | --- Analysis for bio2rdf-pharmgkb took 367.5749969482422s
Availability | SPARQL endpoint availability check for Bio2RDF::PharmGKB::BioPAX took 4.076957702636719e-05s
Availability | VoID file availability check for Bio2RDF::PharmGKB::BioPAX took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for Bio2RDF::PharmGKB::BioPAX took 0.28217625617980957s
Reputation | Calculation of the PageRank for Bio2RDF::PharmGKB::BioPAX took 0.02028179168701172s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PharmGKB::BioPAX took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PharmGKB::BioPAX took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PharmGKB::BioPAX took 3.337860107421875e-05s
Believability | Calculation of trust value for Bio2RDF::PharmGKB::BioPAX took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-pharmgkb-biopax took 4.3041160106658936s
Availability | SPARQL endpoint availability check for Bio2RDF::PID took 4.5299530029296875e-05s
Availability | VoID file availability check for Bio2RDF::PID took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Bio2RDF::PID took 0.6861681938171387s
Reputation | Calculation of the PageRank for Bio2RDF::PID took 0.020555734634399414s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PID took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PID took 0.000985860824584961s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PID took 3.933906555175781e-05s
Believability | Calculation of trust value for Bio2RDF::PID took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-pid took 5.6218650341033936s
Availability | SPARQL endpoint availability check for Bio2RDF::PubChem took 4.0531158447265625e-05s
Availability | VoID file availability check for Bio2RDF::PubChem took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for Bio2RDF::PubChem took 0.2503845691680908s
Reputation | Calculation of the PageRank for Bio2RDF::PubChem took 0.02078413963317871s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PubChem took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PubChem took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PubChem took 3.528594970703125e-05s
Believability | Calculation of trust value for Bio2RDF::PubChem took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-pubchem-2 took 3.7857730388641357s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 60.05952525138855s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.0008366107940673828s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 0.7136197090148926s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.020781517028808594s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.00014495849609375s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-pubmed took 245.7837679386139s
Availability | SPARQL endpoint availability check for Bio2RDF::Reactome took 3.981590270996094e-05s
Availability | VoID file availability check for Bio2RDF::Reactome took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for Bio2RDF::Reactome took 0.7271022796630859s
Reputation | Calculation of the PageRank for Bio2RDF::Reactome took 0.020441532135009766s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Reactome took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Reactome took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Reactome took 7.176399230957031e-05s
Believability | Calculation of trust value for Bio2RDF::Reactome took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-reactome took 5.777240991592407s
Availability | SPARQL endpoint availability check for Bio2RDF::Rhea took 4.100799560546875e-05s
Availability | VoID file availability check for Bio2RDF::Rhea took 0.0003132820129394531s
Completeness | Calculation of interlinking completeness for Bio2RDF::Rhea took 0.274489164352417s
Reputation | Calculation of the PageRank for Bio2RDF::Rhea took 0.020498991012573242s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Rhea took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Rhea took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Rhea took 5.4836273193359375e-05s
Believability | Calculation of trust value for Bio2RDF::Rhea took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-rhea took 3.4622485637664795s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 60.04764699935913s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0007297992706298828s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 0.29032087326049805s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.02078866958618164s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 8.702278137207031e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-sabiork took 264.30395770072937s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 60.05514407157898s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.0007967948913574219s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 0.766270637512207s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.02085137367248535s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00011920928955078125s
Believability | Calculation of trust value for Bio2RDF::Sgd took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-sgd took 265.47410321235657s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 4.100799560546875e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.0006489753723144531s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 0.7157042026519775s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.02020263671875s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 3.24249267578125e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-sgd-resources took 23.726855993270874s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 60.060868978500366s
Availability | VoID file availability check for Bio2RDF::Sider took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 0.26755857467651367s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.020667552947998047s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 5.3882598876953125e-05s
Believability | Calculation of trust value for Bio2RDF::Sider took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-sider took 325.9860637187958s
Availability | SPARQL endpoint availability check for Bio2RDF::SPIKE took 3.8623809814453125e-05s
Availability | VoID file availability check for Bio2RDF::SPIKE took 0.00023102760314941406s
Completeness | Calculation of interlinking completeness for Bio2RDF::SPIKE took 0.7110753059387207s
Reputation | Calculation of the PageRank for Bio2RDF::SPIKE took 0.020122766494750977s
Interlinking | Calculation of Degree of Connection for Bio2RDF::SPIKE took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bio2RDF::SPIKE took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::SPIKE took 2.9087066650390625e-05s
Believability | Calculation of trust value for Bio2RDF::SPIKE took 6.67572021484375e-06s
INFO | --- Analysis for bio2rdf-spike took 5.039074897766113s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 4.267692565917969e-05s
Availability | VoID file availability check for bio2rdf-taxon took 0.0006444454193115234s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 0.27936649322509766s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.020300626754760742s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 4.076957702636719e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-taxon took 22.82810068130493s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 60.064146757125854s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.0007207393646240234s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 0.42445874214172363s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.020767688751220703s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 0.00011205673217773438s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 9.775161743164062e-06s
INFO | --- Analysis for bio2rdf-taxonomy took 345.38222908973694s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 60.05237555503845s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.0007658004760742188s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 0.28622984886169434s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.02053046226501465s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 3.695487976074219e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-wikipathways took 446.6196126937866s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 60.055874824523926s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.00063323974609375s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 0.3199455738067627s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.02060985565185547s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 8.678436279296875e-05s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-wormbase took 345.58084654808044s
Availability | SPARQL endpoint availability check for Biografías y Vidas took 4.1484832763671875e-05s
Availability | VoID file availability check for Biografías y Vidas took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for Biografías y Vidas took 0.7001919746398926s
Reputation | Calculation of the PageRank for Biografías y Vidas took 0.020197629928588867s
Interlinking | Calculation of Degree of Connection for Biografías y Vidas took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Biografías y Vidas took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Biografías y Vidas took 1.2159347534179688e-05s
Believability | Calculation of trust value for Biografías y Vidas took 7.152557373046875e-06s
INFO | --- Analysis for biografiasyvidas took 4.6028711795806885s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 0.27382445335388184s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.0004496574401855469s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 0.6913490295410156s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.020366907119750977s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 8.082389831542969e-05s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 4.5299530029296875e-06s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 4.010901212692261s
Availability | SPARQL endpoint availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 4.100799560546875e-05s
Availability | VoID file availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.25907182693481445s
Reputation | Calculation of the PageRank for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.02013373374938965s
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.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for A Short Biographical Dictionary of English Literature (RKBExplorer) took 3.0040740966796875e-05s
Believability | Calculation of trust value for A Short Biographical Dictionary of English Literature (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for biolit took 2.9896562099456787s
Availability | SPARQL endpoint availability check for BioLOD for Protein Data Bank Japan took 4.029273986816406e-05s
Availability | VoID file availability check for BioLOD for Protein Data Bank Japan took 0.0005781650543212891s
Completeness | Calculation of interlinking completeness for BioLOD for Protein Data Bank Japan took 0.27822160720825195s
Reputation | Calculation of the PageRank for BioLOD for Protein Data Bank Japan took 0.020374774932861328s
Interlinking | Calculation of Degree of Connection for BioLOD for Protein Data Bank Japan took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BioLOD for Protein Data Bank Japan took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for BioLOD for Protein Data Bank Japan took 3.9577484130859375e-05s
Believability | Calculation of trust value for BioLOD for Protein Data Bank Japan took 6.198883056640625e-06s
INFO | --- Analysis for biolod-pdb took 8.836259126663208s
Availability | SPARQL endpoint availability check for BioModels RDF took 1.0332446098327637s
Availability | VoID file availability check for BioModels RDF took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.2770094871520996s
Reputation | Calculation of the PageRank for BioModels RDF took 0.020583629608154297s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 4.00543212890625e-05s
Believability | Calculation of trust value for BioModels RDF took 5.9604644775390625e-06s
INFO | --- Analysis for biomodels-rdf took 4.288247346878052s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.4069268703460693s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007565021514892578s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.27737855911254883s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.02057623863220215s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.0994415283203125e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 7.3909759521484375e-06s
INFO | --- Analysis for Biop took 6.9774627685546875s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.172325134277344e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0005567073822021484s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.6882567405700684s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.020432710647583008s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.528594970703125e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 6.9141387939453125e-06s
INFO | --- Analysis for Bioportal took 2.9691786766052246s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 4.124641418457031e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.3038296699523926s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.020238161087036133s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006330013275146484s
Believability | Calculation of trust value for Amphibian gross anatomy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-aao took 2.9021759033203125s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 3.9577484130859375e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.0005965232849121094s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 0.2786545753479004s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.020279884338378906s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.0002982616424560547s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-aba took 2.731289863586426s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.2716255187988281s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.02065300941467285s
Interlinking | Calculation of Degree of Connection for Cancer Research and Management ACGT Master Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cancer Research and Management ACGT Master Ontology took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0016274452209472656s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-acgt took 2.7879934310913086s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 4.1484832763671875e-05s
Availability | VoID file availability check for Animal natural history and life history took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 0.29029345512390137s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.02017998695373535s
Interlinking | Calculation of Degree of Connection for Animal natural history and life history took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Animal natural history and life history took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.0003237724304199219s
Believability | Calculation of trust value for Animal natural history and life history took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-adw took 2.753971815109253s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.0006844997406005859s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 0.27513790130615234s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.020188331604003906s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.00047850608825683594s
Believability | Calculation of trust value for Anatomical Entity Ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-aeo took 3.1411476135253906s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 3.933906555175781e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 0.0005548000335693359s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 0.2711300849914551s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.0203704833984375s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0009653568267822266s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-aero took 2.675602436065674s
Availability | SPARQL endpoint availability check for AI/RHEUM took 3.981590270996094e-05s
Availability | VoID file availability check for AI/RHEUM took 0.00055694580078125s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 0.27597594261169434s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.02041935920715332s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.0004048347473144531s
Believability | Calculation of trust value for AI/RHEUM took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-air took 2.776898145675659s
Availability | SPARQL endpoint availability check for Amino Acid took 4.172325134277344e-05s
Availability | VoID file availability check for Amino Acid took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for Amino Acid took 0.28977036476135254s
Reputation | Calculation of the PageRank for Amino Acid took 0.020349740982055664s
Interlinking | Calculation of Degree of Connection for Amino Acid took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Amino Acid took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.0002562999725341797s
Believability | Calculation of trust value for Amino Acid took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-amino-acid took 2.7659835815429688s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.27611351013183594s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.020153284072875977s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.0002803802490234375s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-apo took 2.7119224071502686s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 4.0531158447265625e-05s
Availability | VoID file availability check for African Traditional Medicine took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 0.2841064929962158s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.020455121994018555s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.0002372264862060547s
Believability | Calculation of trust value for African Traditional Medicine took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-atmo took 2.776088237762451s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 4.124641418457031e-05s
Availability | VoID file availability check for Amphibian taxonomy took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.2617065906524658s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.02071833610534668s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 9.846687316894531e-05s
Believability | Calculation of trust value for Amphibian taxonomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ato took 2.725529432296753s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 3.981590270996094e-05s
Availability | VoID file availability check for BioAssay Ontology took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 0.2885098457336426s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.020278215408325195s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.001312255859375s
Believability | Calculation of trust value for BioAssay Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-bao took 2.6596081256866455s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 3.981590270996094e-05s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 0.2658517360687256s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.020383596420288086s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.00037026405334472656s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 2.632007122039795s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.2685103416442871s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.0203707218170166s
Interlinking | Calculation of Degree of Connection for Breast Cancer Grading Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Breast Cancer Grading Ontology took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.0003325939178466797s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-bcgo took 2.72296404838562s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.29204511642456055s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.020115137100219727s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.0013625621795654297s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-bdo took 2.734713554382324s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Basic Formal Ontology took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.2679574489593506s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.020411968231201172s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0005056858062744141s
Believability | Calculation of trust value for Basic Formal Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-bfo took 2.6741557121276855s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 4.076957702636719e-05s
Availability | VoID file availability check for Bleeding History Phenotype took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.2714066505432129s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.020113468170166016s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0007114410400390625s
Believability | Calculation of trust value for Bleeding History Phenotype took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-bho took 2.7086400985717773s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 4.124641418457031e-05s
Availability | VoID file availability check for Bilateria anatomy took 0.000560760498046875s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.25998449325561523s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.020549535751342773s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.00044274330139160156s
Believability | Calculation of trust value for Bilateria anatomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-bila took 2.657895088195801s
Availability | SPARQL endpoint availability check for BIRNLex took 4.3392181396484375e-05s
Availability | VoID file availability check for BIRNLex took 0.0003807544708251953s
Completeness | Calculation of interlinking completeness for BIRNLex took 0.24859976768493652s
Reputation | Calculation of the PageRank for BIRNLex took 0.020808696746826172s
Interlinking | Calculation of Degree of Connection for BIRNLex took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BIRNLex took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.0015366077423095703s
Believability | Calculation of trust value for BIRNLex took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-birnlex took 2.678100347518921s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.696846008300781e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0004124641418457031s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.2366955280303955s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020171403884887695s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007460117340087891s
Believability | Calculation of trust value for Gene Regulation Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-bootstrep took 2.5949325561523438s
Availability | SPARQL endpoint availability check for BioPAX took 4.1484832763671875e-05s
Availability | VoID file availability check for BioPAX took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for BioPAX took 0.27269554138183594s
Reputation | Calculation of the PageRank for BioPAX took 0.020276546478271484s
Interlinking | Calculation of Degree of Connection for BioPAX took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BioPAX took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for BioPAX took 9.965896606445312e-05s
Believability | Calculation of trust value for BioPAX took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-bp took 2.5852110385894775s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.24457621574401855s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.020278453826904297s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0007925033569335938s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.00035262107849121094s
Believability | Calculation of trust value for Biomedical Resource Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-bro_x1 took 2.5614264011383057s
Availability | SPARQL endpoint availability check for Spatial Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Spatial Ontology took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 0.2920207977294922s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.02043914794921875s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0007932186126708984s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.0002276897430419922s
Believability | Calculation of trust value for Spatial Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-bspo took 2.722982883453369s
Availability | SPARQL endpoint availability check for BioTop took 4.124641418457031e-05s
Availability | VoID file availability check for BioTop took 0.0005393028259277344s
Completeness | Calculation of interlinking completeness for BioTop took 0.28342294692993164s
Reputation | Calculation of the PageRank for BioTop took 0.020059585571289062s
Interlinking | Calculation of Degree of Connection for BioTop took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BioTop took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006866455078125s
Believability | Calculation of trust value for BioTop took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-bt took 2.6221961975097656s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 8.20159912109375e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.0005950927734375s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.2917492389678955s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.020301342010498047s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for BRENDA tissue / enzyme source took 0.0007765293121337891s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0008728504180908203s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-bto took 2.7353832721710205s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 5.340576171875e-05s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.000576019287109375s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.31034183502197266s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.02120494842529297s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.0018837451934814453s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-canco took 3.078202486038208s
Availability | SPARQL endpoint availability check for CAO took 3.981590270996094e-05s
Availability | VoID file availability check for CAO took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for CAO took 0.2867600917816162s
Reputation | Calculation of the PageRank for CAO took 0.020055294036865234s
Interlinking | Calculation of Degree of Connection for CAO took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CAO took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0005862712860107422s
Believability | Calculation of trust value for CAO took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-cao took 2.7172937393188477s
Availability | SPARQL endpoint availability check for CareLex took 3.910064697265625e-05s
Availability | VoID file availability check for CareLex took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for CareLex took 0.2673637866973877s
Reputation | Calculation of the PageRank for CareLex took 0.020224571228027344s
Interlinking | Calculation of Degree of Connection for CareLex took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for CareLex took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for CareLex took 4.8160552978515625e-05s
Believability | Calculation of trust value for CareLex took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-carelex took 2.6638619899749756s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 3.981590270996094e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.2736673355102539s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.020013093948364258s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0007765293121337891s
Believability | Calculation of trust value for Cell Cycle Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-cco took 2.7515015602111816s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.2751779556274414s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.02021932601928711s
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.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.00025272369384765625s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-cdao took 2.6460459232330322s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 4.124641418457031e-05s
Availability | VoID file availability check for Chemical entities of biological interest took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.2574474811553955s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.020456790924072266s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0008101463317871094s
Believability | Calculation of trust value for Chemical entities of biological interest took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-chebi took 2.637199640274048s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 4.100799560546875e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.0005214214324951172s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.2726011276245117s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.020301103591918945s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.00025725364685058594s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-chem2bio2owl took 2.7707858085632324s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 6.127357482910156e-05s
Availability | VoID file availability check for Chemical Information Ontology took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.28112220764160156s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.020056486129760742s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0007739067077636719s
Believability | Calculation of trust value for Chemical Information Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-cheminf took 2.6818931102752686s
Availability | SPARQL endpoint availability check for Cell type took 4.0531158447265625e-05s
Availability | VoID file availability check for Cell type took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for Cell type took 0.2535982131958008s
Reputation | Calculation of the PageRank for Cell type took 0.020040273666381836s
Interlinking | Calculation of Degree of Connection for Cell type took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Cell type took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.0003745555877685547s
Believability | Calculation of trust value for Cell type took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-cl took 2.6518867015838623s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Cell Line Ontology took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.30151844024658203s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.020247459411621094s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0007925033569335938s
Believability | Calculation of trust value for Cell Line Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-clo took 2.763868808746338s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 0.2554299831390381s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.02045726776123047s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0008599758148193359s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.00020074844360351562s
Believability | Calculation of trust value for Clinical Measurement Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-cmo took 2.5614843368530273s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.0005400180816650391s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 0.2450268268585205s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.020160675048828125s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.0002090930938720703s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-cno took 2.5663225650787354s
Availability | SPARQL endpoint availability check for Wheat trait took 4.076957702636719e-05s
Availability | VoID file availability check for Wheat trait took 0.0005278587341308594s
Completeness | Calculation of interlinking completeness for Wheat trait took 0.25220775604248047s
Reputation | Calculation of the PageRank for Wheat trait took 0.020299196243286133s
Interlinking | Calculation of Degree of Connection for Wheat trait took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Wheat trait took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 5.221366882324219e-05s
Believability | Calculation of trust value for Wheat trait took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-co_wheat took 2.659919261932373s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 4.100799560546875e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.264697790145874s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.020274639129638672s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.00033354759216308594s
Believability | Calculation of trust value for Cognitive Atlas took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-cogat took 2.5786068439483643s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.277571439743042s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.020256519317626953s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0007963180541992188s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0007278919219970703s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-cogpo took 2.7272391319274902s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 4.9591064453125e-05s
Availability | VoID file availability check for Current Procedural Terminology took 0.0003600120544433594s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.25387120246887207s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.02024698257446289s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.00040650367736816406s
Believability | Calculation of trust value for Current Procedural Terminology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-cpt took 2.6272661685943604s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 4.100799560546875e-05s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 0.29810309410095215s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.020236730575561523s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.0017426013946533203s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-csp took 3.1529877185821533s
Availability | SPARQL endpoint availability check for COSTART took 4.0531158447265625e-05s
Availability | VoID file availability check for COSTART took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for COSTART took 0.2578396797180176s
Reputation | Calculation of the PageRank for COSTART took 0.019971132278442383s
Interlinking | Calculation of Degree of Connection for COSTART took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for COSTART took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0009610652923583984s
Believability | Calculation of trust value for COSTART took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-cst took 2.6652936935424805s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 4.124641418457031e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.28010034561157227s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.02042865753173828s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.0005421638488769531s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ctcae took 2.6186389923095703s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 4.0531158447265625e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.27838778495788574s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.020250797271728516s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.00045609474182128906s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ctx took 2.6204280853271484s
Availability | SPARQL endpoint availability check for Dendritic cell took 4.124641418457031e-05s
Availability | VoID file availability check for Dendritic cell took 0.0005474090576171875s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.2540106773376465s
Reputation | Calculation of the PageRank for Dendritic cell took 0.020452022552490234s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.00029730796813964844s
Believability | Calculation of trust value for Dendritic cell took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-dc_cl took 2.6627445220947266s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 4.00543212890625e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 0.2549405097961426s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.02025437355041504s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 8.678436279296875e-05s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ddanat took 2.565117835998535s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 4.1484832763671875e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.2536313533782959s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.019992351531982422s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.00096893310546875s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ddi took 2.6871964931488037s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 5.269050598144531e-05s
Availability | VoID file availability check for Diagnostic Ontology took 0.0006432533264160156s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.25141191482543945s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.020569562911987305s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 8.630752563476562e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-diagnosticont took 2.673616886138916s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 4.887580871582031e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.2746739387512207s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.020572662353515625s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.00016188621520996094s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-dikb-evidence took 2.66021990776062s
Availability | SPARQL endpoint availability check for Human disease ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Human disease ontology took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.2877800464630127s
Reputation | Calculation of the PageRank for Human disease ontology took 0.020176172256469727s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Human disease ontology took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0006134510040283203s
Believability | Calculation of trust value for Human disease ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-doid took 2.6651618480682373s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 0.2698402404785156s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.02026653289794922s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0007872581481933594s
Believability | Calculation of trust value for Electrocardiography Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ecg took 2.6315789222717285s
Availability | SPARQL endpoint availability check for Evidence codes took 4.3392181396484375e-05s
Availability | VoID file availability check for Evidence codes took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for Evidence codes took 0.2670454978942871s
Reputation | Calculation of the PageRank for Evidence codes took 0.020444631576538086s
Interlinking | Calculation of Degree of Connection for Evidence codes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Evidence codes took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 3.266334533691406e-05s
Believability | Calculation of trust value for Evidence codes took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-eco took 2.5544705390930176s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.32833266258239746s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.020364761352539062s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.0017025470733642578s
Believability | Calculation of trust value for Experimental Factor Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-efo took 3.053142786026001s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 4.3392181396484375e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 0.2763955593109131s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.021406888961791992s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.0011889934539794922s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ehda took 2.586544990539551s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 4.0531158447265625e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.27534985542297363s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.019986867904663086s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007102489471435547s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-ehdaa took 2.620012044906616s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 3.981590270996094e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.28669285774230957s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.020140409469604492s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version, v2 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version, v2 took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0005309581756591797s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ehdaa2 took 2.5866000652313232s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 3.9577484130859375e-05s
Availability | VoID file availability check for Mouse gross anatomy and development took 0.0003521442413330078s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 0.2713582515716553s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.02007126808166504s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 3.1948089599609375e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-emap took 2.6350951194763184s
Availability | SPARQL endpoint availability check for Environment Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Environment Ontology took 0.0004334449768066406s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.29236483573913574s
Reputation | Calculation of the PageRank for Environment Ontology took 0.020275115966796875s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.0004208087921142578s
Believability | Calculation of trust value for Environment Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-envo took 2.6614840030670166s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 4.458427429199219e-05s
Availability | VoID file availability check for Plant environmental conditions took 0.00028967857360839844s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.2472705841064453s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.02031397819519043s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.0003044605255126953s
Believability | Calculation of trust value for Plant environmental conditions took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-eo took 2.526221752166748s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.2562570571899414s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.020468950271606445s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.001199960708618164s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ep took 2.754110813140869s
Availability | SPARQL endpoint availability check for Epilepsy took 6.651878356933594e-05s
Availability | VoID file availability check for Epilepsy took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.2606964111328125s
Reputation | Calculation of the PageRank for Epilepsy took 0.02055215835571289s
Interlinking | Calculation of Degree of Connection for Epilepsy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Epilepsy took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.00013375282287597656s
Believability | Calculation of trust value for Epilepsy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-epileponto took 2.608417272567749s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 5.364418029785156e-05s
Availability | VoID file availability check for eagle-i research resource ontology took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.2747828960418701s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.020251750946044922s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0007951259613037109s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.0012063980102539062s
Believability | Calculation of trust value for eagle-i research resource ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ero took 2.654426336288452s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 4.076957702636719e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.0005545616149902344s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 0.2829933166503906s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.020076274871826172s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.0012183189392089844s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ev took 2.639554738998413s
Availability | SPARQL endpoint availability check for ExO took 4.076957702636719e-05s
Availability | VoID file availability check for ExO took 0.0005590915679931641s
Completeness | Calculation of interlinking completeness for ExO took 0.28415441513061523s
Reputation | Calculation of the PageRank for ExO took 0.02017354965209961s
Interlinking | Calculation of Degree of Connection for ExO took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ExO took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for ExO took 0.00025010108947753906s
Believability | Calculation of trust value for ExO took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-exo took 2.690796136856079s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 4.076957702636719e-05s
Availability | VoID file availability check for Fungal gross anatomy took 0.0005338191986083984s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 0.29660582542419434s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.020142316818237305s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.00010609626770019531s
Believability | Calculation of trust value for Fungal gross anatomy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-fao took 2.651562452316284s
Availability | SPARQL endpoint availability check for Biological imaging methods took 4.1484832763671875e-05s
Availability | VoID file availability check for Biological imaging methods took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.26378369331359863s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.020076751708984375s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.00018596649169921875s
Believability | Calculation of trust value for Biological imaging methods took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-fbbi took 2.707578420639038s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 4.1961669921875e-05s
Availability | VoID file availability check for Drosophila gross anatomy took 0.00043511390686035156s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 0.2528712749481201s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.020344257354736328s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0006241798400878906s
Believability | Calculation of trust value for Drosophila gross anatomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-fbbt took 2.525019884109497s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 4.029273986816406e-05s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.27009081840515137s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.019942283630371094s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.00041675567626953125s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-fbcv took 2.656113386154175s
Availability | SPARQL endpoint availability check for Drosophila development took 4.076957702636719e-05s
Availability | VoID file availability check for Drosophila development took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.2779097557067871s
Reputation | Calculation of the PageRank for Drosophila development took 0.020167112350463867s
Interlinking | Calculation of Degree of Connection for Drosophila development took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Drosophila development took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.124641418457031e-05s
Believability | Calculation of trust value for Drosophila development took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-fbdv took 2.633866548538208s
Availability | SPARQL endpoint availability check for Fly taxonomy took 3.910064697265625e-05s
Availability | VoID file availability check for Fly taxonomy took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.2972531318664551s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.019992589950561523s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.0003528594970703125s
Believability | Calculation of trust value for Fly taxonomy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-fbsp took 3.258086919784546s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 4.38690185546875e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.2917308807373047s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.020186662673950195s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.00022101402282714844s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-fda-meddevice took 2.7200024127960205s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 5.364418029785156e-05s
Availability | VoID file availability check for Family Health History Ontology took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 0.287459135055542s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.019993305206298828s
Interlinking | Calculation of Degree of Connection for Family Health History Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Family Health History Ontology took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.0003871917724609375s
Believability | Calculation of trust value for Family Health History Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-fhho took 2.648495674133301s
Availability | SPARQL endpoint availability check for Influenza Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Influenza Ontology took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.2666008472442627s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.020422697067260742s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.001033782958984375s
Believability | Calculation of trust value for Influenza Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-flu took 2.7169153690338135s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 3.9577484130859375e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.0005860328674316406s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.26258134841918945s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.02049851417541504s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 3.647804260253906e-05s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 6.318092346191406e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-fma took 2.681612014770508s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 8.20159912109375e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 0.2919328212738037s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.0204007625579834s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.00012922286987304688s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-fypo took 2.676623582839966s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.29179883003234863s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.021413564682006836s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 9.179115295410156e-05s
Believability | Calculation of trust value for GeoSpecies Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-geospecies took 2.67423415184021s
Availability | SPARQL endpoint availability check for General Formal Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for General Formal Ontology took 0.0002970695495605469s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.24251842498779297s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.020073413848876953s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.00015783309936523438s
Believability | Calculation of trust value for General Formal Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-gfo took 2.6032886505126953s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 4.100799560546875e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.2689852714538574s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.02009296417236328s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.0005877017974853516s
Believability | Calculation of trust value for General Formal Ontology: Biology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-gfo-bio took 2.718336343765259s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 4.1484832763671875e-05s
Availability | VoID file availability check for Gene Ontology Extension took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 0.2874336242675781s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.0199282169342041s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0008776187896728516s
Believability | Calculation of trust value for Gene Ontology Extension took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-go_x1 took 2.687098503112793s
Availability | SPARQL endpoint availability check for Gene Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Gene Ontology took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.2571909427642822s
Reputation | Calculation of the PageRank for Gene Ontology took 0.01999831199645996s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0008573532104492188s
Believability | Calculation of trust value for Gene Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-go_x2 took 2.574138879776001s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 4.029273986816406e-05s
Availability | VoID file availability check for Cereal Plant Development took 0.0005657672882080078s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 0.2665383815765381s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.02028059959411621s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 2.7894973754882812e-05s
Believability | Calculation of trust value for Cereal Plant Development took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-gro took 2.646308183670044s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 4.124641418457031e-05s
Availability | VoID file availability check for Cereal plant gross anatomy took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 0.25841307640075684s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.020129680633544922s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.00043463706970214844s
Believability | Calculation of trust value for Cereal plant gross anatomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-gro_x1 took 2.621028423309326s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.00055694580078125s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.2856919765472412s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020143747329711914s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007402896881103516s
Believability | Calculation of trust value for Gene Regulation Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-gro_x2 took 2.6563615798950195s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 4.5299530029296875e-05s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.0006635189056396484s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.2625541687011719s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.02040696144104004s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0005629062652587891s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-hao took 2.632030725479126s
Availability | SPARQL endpoint availability check for HCPCS took 4.1961669921875e-05s
Availability | VoID file availability check for HCPCS took 0.0004572868347167969s
Completeness | Calculation of interlinking completeness for HCPCS took 0.2643439769744873s
Reputation | Calculation of the PageRank for HCPCS took 0.020231246948242188s
Interlinking | Calculation of Degree of Connection for HCPCS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for HCPCS took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.00022745132446289062s
Believability | Calculation of trust value for HCPCS took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-hcpcs took 2.5890424251556396s
Availability | SPARQL endpoint availability check for Health Level Seven took 4.1484832763671875e-05s
Availability | VoID file availability check for Health Level Seven took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for Health Level Seven took 0.2993812561035156s
Reputation | Calculation of the PageRank for Health Level Seven took 0.020144224166870117s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.0012574195861816406s
Believability | Calculation of trust value for Health Level Seven took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-hl7 took 2.7742106914520264s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 4.029273986816406e-05s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.2865936756134033s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.020123004913330078s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.00033092498779296875s
Believability | Calculation of trust value for HEALTH_INDICATORS took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-hlth_indics took 2.708324909210205s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 4.220008850097656e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.2670769691467285s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.020478010177612305s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 2.86102294921875e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-hom took 2.713803768157959s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 4.076957702636719e-05s
Availability | VoID file availability check for HOM-HARVARD took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 0.3058147430419922s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.01999068260192871s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 2.9325485229492188e-05s
Believability | Calculation of trust value for HOM-HARVARD took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-hom_harvard took 2.6793527603149414s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.27831435203552246s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.020447492599487305s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0007169246673583984s
Believability | Calculation of trust value for Human Phenotype Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-hp_x1 took 2.600377321243286s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 0.26520442962646484s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.020325183868408203s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.0010411739349365234s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-hpio took 2.692826271057129s
Availability | SPARQL endpoint availability check for HUGO took 4.1484832763671875e-05s
Availability | VoID file availability check for HUGO took 0.0005195140838623047s
Completeness | Calculation of interlinking completeness for HUGO took 0.2611515522003174s
Reputation | Calculation of the PageRank for HUGO took 0.02033853530883789s
Interlinking | Calculation of Degree of Connection for HUGO took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for HUGO took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for HUGO took 7.486343383789062e-05s
Believability | Calculation of trust value for HUGO took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-hugo took 2.684584617614746s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 4.57763671875e-05s
Availability | VoID file availability check for Information Artifact Ontology took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 0.24453377723693848s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.020119905471801758s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0006413459777832031s
Believability | Calculation of trust value for Information Artifact Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-iao took 2.6410653591156006s
Availability | SPARQL endpoint availability check for ICD10 took 4.029273986816406e-05s
Availability | VoID file availability check for ICD10 took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for ICD10 took 0.24699759483337402s
Reputation | Calculation of the PageRank for ICD10 took 0.020012378692626953s
Interlinking | Calculation of Degree of Connection for ICD10 took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for ICD10 took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.0008089542388916016s
Believability | Calculation of trust value for ICD10 took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-icd10 took 2.594686508178711s
Availability | SPARQL endpoint availability check for ICD10CM took 4.363059997558594e-05s
Availability | VoID file availability check for ICD10CM took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.26347875595092773s
Reputation | Calculation of the PageRank for ICD10CM took 0.02048039436340332s
Interlinking | Calculation of Degree of Connection for ICD10CM took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for ICD10CM took 0.0009024143218994141s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0006911754608154297s
Believability | Calculation of trust value for ICD10CM took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-icd10cm took 2.577268600463867s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 4.124641418457031e-05s
Availability | VoID file availability check for ICD-10-PCS took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 0.2587428092956543s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.02028036117553711s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.00015354156494140625s
Believability | Calculation of trust value for ICD-10-PCS took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-icd10pcs took 2.631985902786255s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 4.076957702636719e-05s
Availability | VoID file availability check for International Classification of Diseases took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 0.28597593307495117s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.020051956176757812s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0006253719329833984s
Believability | Calculation of trust value for International Classification of Diseases took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-icd9cm took 2.662614107131958s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 5.435943603515625e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.25096940994262695s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.020118236541748047s
Interlinking | Calculation of Degree of Connection for International Classification of Functioning, Disability and Health (ICF) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for International Classification of Functioning, Disability and Health (ICF) took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.0004456043243408203s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-icf_x1 took 2.6765217781066895s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 4.100799560546875e-05s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.0004658699035644531s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 0.26648950576782227s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.020111799240112305s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.0012242794036865234s
Believability | Calculation of trust value for International Classification for Nursing Practice took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-icnp took 2.6448841094970703s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 4.124641418457031e-05s
Availability | VoID file availability check for International Classification of Primary Care took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 0.2638280391693115s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.020337343215942383s
Interlinking | Calculation of Degree of Connection for International Classification of Primary Care took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for International Classification of Primary Care took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.0004413127899169922s
Believability | Calculation of trust value for International Classification of Primary Care took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-icpc took 2.760239362716675s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 4.124641418457031e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 0.00024271011352539062s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.2753899097442627s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.01995086669921875s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0008327960968017578s
Believability | Calculation of trust value for ICPC-2 PLUS took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-icpc2p took 2.5952627658843994s
Availability | SPARQL endpoint availability check for ICPS Network took 5.125999450683594e-05s
Availability | VoID file availability check for ICPS Network took 0.0004286766052246094s
Completeness | Calculation of interlinking completeness for ICPS Network took 0.24678611755371094s
Reputation | Calculation of the PageRank for ICPS Network took 0.020694494247436523s
Interlinking | Calculation of Degree of Connection for ICPS Network took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ICPS Network took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.0002281665802001953s
Believability | Calculation of trust value for ICPS Network took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-icps took 2.60229229927063s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.256028413772583s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.020012617111206055s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0008540153503417969s
Believability | Calculation of trust value for Infectious Disease Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ido took 2.613746166229248s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Brucellosis Ontology took 0.0005846023559570312s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.2945137023925781s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.020809650421142578s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0011587142944335938s
Believability | Calculation of trust value for Brucellosis Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-idobru took 2.7239060401916504s
Availability | SPARQL endpoint availability check for Malaria Ontology took 8.273124694824219e-05s
Availability | VoID file availability check for Malaria Ontology took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.2610478401184082s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.02033710479736328s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.0013129711151123047s
Believability | Calculation of trust value for Malaria Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-idomal took 2.654792308807373s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 4.029273986816406e-05s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.0005586147308349609s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 0.30098915100097656s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.020151615142822266s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.00032210350036621094s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-iev took 2.8797190189361572s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 4.076957702636719e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.0004639625549316406s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.26263904571533203s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.020331144332885742s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.00014495849609375s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-imgt took 2.7080166339874268s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 4.100799560546875e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.23866987228393555s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.019891977310180664s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0005681514739990234s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-imr took 2.639789581298828s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Interaction Network Ontology took 0.0005428791046142578s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.2626805305480957s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.020066022872924805s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0007786750793457031s
Believability | Calculation of trust value for Interaction Network Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-ino took 2.6268560886383057s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 4.100799560546875e-05s
Availability | VoID file availability check for Hewan Invertebrata took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.2710893154144287s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.02019214630126953s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 3.314018249511719e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-invertebrata took 2.6774046421051025s
Availability | SPARQL endpoint availability check for IxnO took 3.981590270996094e-05s
Availability | VoID file availability check for IxnO took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for IxnO took 0.2503933906555176s
Reputation | Calculation of the PageRank for IxnO took 0.020220279693603516s
Interlinking | Calculation of Degree of Connection for IxnO took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IxnO took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.00018978118896484375s
Believability | Calculation of trust value for IxnO took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ixno took 3.0461575984954834s
Availability | SPARQL endpoint availability check for SysMO-JERM took 4.1484832763671875e-05s
Availability | VoID file availability check for SysMO-JERM took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 0.2645711898803711s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.021236896514892578s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.0004596710205078125s
Believability | Calculation of trust value for SysMO-JERM took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-jerm took 2.675200939178467s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.2619514465332031s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.020208120346069336s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 3.5762786865234375e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-kisao took 2.7275822162628174s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 4.124641418457031e-05s
Availability | VoID file availability check for Loggerhead nesting took 0.0005640983581542969s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.267991304397583s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.020411014556884766s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.0002231597900390625s
Believability | Calculation of trust value for Loggerhead nesting took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-lhn took 2.63254976272583s
Availability | SPARQL endpoint availability check for Lipid Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Lipid Ontology took 0.0005552768707275391s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 0.2829151153564453s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.020121335983276367s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.0002033710479736328s
Believability | Calculation of trust value for Lipid Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-lipro took 2.675799608230591s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 4.124641418457031e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.0005273818969726562s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.3011457920074463s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.02013230323791504s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.0018091201782226562s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-lnc took 3.0974080562591553s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 4.029273986816406e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 0.26594066619873047s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.020166635513305664s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.000652313232421875s
Believability | Calculation of trust value for Mouse adult gross anatomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ma took 2.605048179626465s
Availability | SPARQL endpoint availability check for Multiple alignment took 4.506111145019531e-05s
Availability | VoID file availability check for Multiple alignment took 0.000518798828125s
Completeness | Calculation of interlinking completeness for Multiple alignment took 0.29196786880493164s
Reputation | Calculation of the PageRank for Multiple alignment took 0.020083189010620117s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.00019550323486328125s
Believability | Calculation of trust value for Multiple alignment took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mao took 2.581745147705078s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 4.4345855712890625e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 0.2669973373413086s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.02018451690673828s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0006852149963378906s
Believability | Calculation of trust value for Minimal anatomical terminology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mat took 2.654613494873047s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 3.981590270996094e-05s
Availability | VoID file availability check for Breast tissue cell lines took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.25351953506469727s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.01997089385986328s
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.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.00042247772216796875s
Believability | Calculation of trust value for Breast tissue cell lines took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mcbcc took 2.6373393535614014s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Cell line ontology took 0.0005323886871337891s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.2937595844268799s
Reputation | Calculation of the PageRank for Cell line ontology took 0.020159482955932617s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007874965667724609s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0008103847503662109s
Believability | Calculation of trust value for Cell line ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mccl took 2.7465455532073975s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Cell line ontology took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.30104637145996094s
Reputation | Calculation of the PageRank for Cell line ontology took 0.020591259002685547s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007843971252441406s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0014481544494628906s
Believability | Calculation of trust value for Cell line ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mccl_x1 took 2.684602975845337s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 3.981590270996094e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.29082560539245605s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.020047664642333984s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.000232696533203125s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mcv took 2.7215075492858887s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 3.981590270996094e-05s
Availability | VoID file availability check for Master Drug Data Base took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 0.262631893157959s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.020426034927368164s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.00017452239990234375s
Believability | Calculation of trust value for Master Drug Data Base took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mddb took 2.5995686054229736s
Availability | SPARQL endpoint availability check for MedDRA took 4.1484832763671875e-05s
Availability | VoID file availability check for MedDRA took 0.0005075931549072266s
Completeness | Calculation of interlinking completeness for MedDRA took 0.27676892280578613s
Reputation | Calculation of the PageRank for MedDRA took 0.020226478576660156s
Interlinking | Calculation of Degree of Connection for MedDRA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MedDRA took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.001111745834350586s
Believability | Calculation of trust value for MedDRA took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mdr took 2.7045626640319824s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 4.00543212890625e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.0005228519439697266s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.24881744384765625s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.02019500732421875s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0008649826049804688s
Believability | Calculation of trust value for MedlinePlus Health Topics took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-medlineplus took 2.614591360092163s
Availability | SPARQL endpoint availability check for MeGO took 4.124641418457031e-05s
Availability | VoID file availability check for MeGO took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for MeGO took 0.25904226303100586s
Reputation | Calculation of the PageRank for MeGO took 0.020308732986450195s
Interlinking | Calculation of Degree of Connection for MeGO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MeGO took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.0001552104949951172s
Believability | Calculation of trust value for MeGO took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mego took 2.605545997619629s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 4.076957702636719e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 0.0005559921264648438s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 0.2937946319580078s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.020186185836791992s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.0018110275268554688s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-mesh-owl took 3.120631456375122s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 0.25710368156433105s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.020183324813842773s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0006246566772460938s
Believability | Calculation of trust value for Mental Functioning Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mf took 2.6118228435516357s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 4.4345855712890625e-05s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 0.25893640518188477s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.020159244537353516s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0006041526794433594s
Believability | Calculation of trust value for Medaka fish anatomy and development took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mfo took 2.7508044242858887s
Availability | SPARQL endpoint availability check for Emotion Ontology took 5.173683166503906e-05s
Availability | VoID file availability check for Emotion Ontology took 0.0005035400390625s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 0.2537667751312256s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.020205974578857422s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0007736682891845703s
Believability | Calculation of trust value for Emotion Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mfoem took 2.7014217376708984s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.2759280204772949s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.020171165466308594s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.00010561943054199219s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mhc took 2.6774163246154785s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 4.100799560546875e-05s
Availability | VoID file availability check for Protein-protein interaction took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.2897799015045166s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.020250320434570312s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0006937980651855469s
Believability | Calculation of trust value for Protein-protein interaction took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mi took 2.6522765159606934s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 4.315376281738281e-05s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.0005533695220947266s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.2678678035736084s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.020242929458618164s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0008215904235839844s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0007052421569824219s
Believability | Calculation of trust value for Mosquito insecticide resistance took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-miro took 2.591815948486328s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Measurement Method Ontology took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.24890637397766113s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.02020406723022461s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0008425712585449219s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.00015616416931152344s
Believability | Calculation of trust value for Measurement Method Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mmo took 2.722139358520508s
Availability | SPARQL endpoint availability check for MGED Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for MGED Ontology took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.26840734481811523s
Reputation | Calculation of the PageRank for MGED Ontology took 0.020069122314453125s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.0003724098205566406s
Believability | Calculation of trust value for MGED Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mo took 2.6351325511932373s
Availability | SPARQL endpoint availability check for Protein modification took 4.0531158447265625e-05s
Availability | VoID file availability check for Protein modification took 0.0005362033843994141s
Completeness | Calculation of interlinking completeness for Protein modification took 0.26242709159851074s
Reputation | Calculation of the PageRank for Protein modification took 0.020542621612548828s
Interlinking | Calculation of Degree of Connection for Protein modification took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Protein modification took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.000232696533203125s
Believability | Calculation of trust value for Protein modification took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-mod took 2.699314594268799s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 4.4345855712890625e-05s
Availability | VoID file availability check for Mammalian phenotype took 0.0005517005920410156s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 0.2631845474243164s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.020663022994995117s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0006704330444335938s
Believability | Calculation of trust value for Mammalian phenotype took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mp took 2.687518835067749s
Availability | SPARQL endpoint availability check for Mouse pathology took 4.506111145019531e-05s
Availability | VoID file availability check for Mouse pathology took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.26416826248168945s
Reputation | Calculation of the PageRank for Mouse pathology took 0.02032017707824707s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mouse pathology took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.00048279762268066406s
Believability | Calculation of trust value for Mouse pathology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mpath took 2.691843271255493s
Availability | SPARQL endpoint availability check for Mass spectrometry took 4.100799560546875e-05s
Availability | VoID file availability check for Mass spectrometry took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.26246213912963867s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.020457983016967773s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.0003635883331298828s
Believability | Calculation of trust value for Mass spectrometry took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ms took 2.7356863021850586s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 4.0531158447265625e-05s
Availability | VoID file availability check for Medical Subject Headings took 0.0005702972412109375s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.29309868812561035s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.020245075225830078s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.0018296241760253906s
Believability | Calculation of trust value for Medical Subject Headings took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-msh took 3.1716320514678955s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 4.1961669921875e-05s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.25606369972229004s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.0201263427734375s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.00016760826110839844s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mthch took 2.5534281730651855s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.0005822181701660156s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 0.3118562698364258s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.020233631134033203s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0007982254028320312s
Believability | Calculation of trust value for Natural Products Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-natpro took 2.7106881141662598s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 4.506111145019531e-05s
Availability | VoID file availability check for NCBI organismal classification took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.2807497978210449s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.020322561264038086s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0008373260498046875s
Believability | Calculation of trust value for NCBI organismal classification took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ncbitaxon took 2.6975486278533936s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 4.076957702636719e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.3364858627319336s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.02053236961364746s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.002014636993408203s
Believability | Calculation of trust value for NCI Thesaurus took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ncit took 3.1319212913513184s
Availability | SPARQL endpoint availability check for National Drug Data File took 4.076957702636719e-05s
Availability | VoID file availability check for National Drug Data File took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.2521789073944092s
Reputation | Calculation of the PageRank for National Drug Data File took 0.02025008201599121s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for National Drug Data File took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0006337165832519531s
Believability | Calculation of trust value for National Drug Data File took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-nddf took 2.512073516845703s
Availability | SPARQL endpoint availability check for National Drug File took 3.838539123535156e-05s
Availability | VoID file availability check for National Drug File took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for National Drug File took 0.26346898078918457s
Reputation | Calculation of the PageRank for National Drug File took 0.020078420639038086s
Interlinking | Calculation of Degree of Connection for National Drug File took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for National Drug File took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.0012576580047607422s
Believability | Calculation of trust value for National Drug File took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ndfrt took 2.614335298538208s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 4.00543212890625e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.000438690185546875s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.26628756523132324s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.020182371139526367s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.0011763572692871094s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-nemo_x1 took 2.6640913486480713s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.0005471706390380859s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.26259493827819824s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.020129919052124023s
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.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0006701946258544922s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-neomark took 2.6265742778778076s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 0.0004646778106689453s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 0.25273966789245605s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.02013564109802246s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.0001201629638671875s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-neomarkontology took 2.6979663372039795s
Availability | SPARQL endpoint availability check for NIFSTD took 3.933906555175781e-05s
Availability | VoID file availability check for NIFSTD took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.30746030807495117s
Reputation | Calculation of the PageRank for NIFSTD took 0.020258665084838867s
Interlinking | Calculation of Degree of Connection for NIFSTD took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NIFSTD took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.0019230842590332031s
Believability | Calculation of trust value for NIFSTD took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-nif took 3.1058096885681152s
Availability | SPARQL endpoint availability check for NIF Cell took 4.00543212890625e-05s
Availability | VoID file availability check for NIF Cell took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.2912294864654541s
Reputation | Calculation of the PageRank for NIF Cell took 0.02022576332092285s
Interlinking | Calculation of Degree of Connection for NIF Cell took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NIF Cell took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.0013203620910644531s
Believability | Calculation of trust value for NIF Cell took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-nif_cell took 2.7341971397399902s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 4.1484832763671875e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.29039907455444336s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.020343303680419922s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.0014166831970214844s
Believability | Calculation of trust value for NIF Dysfunction took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-nif_dysfunction took 2.661092758178711s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 3.933906555175781e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.2915656566619873s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.020160675048828125s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0005841255187988281s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-nigo took 2.7562055587768555s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 4.0531158447265625e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 0.00047397613525390625s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.26178717613220215s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.020092487335205078s
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.0007891654968261719s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0006108283996582031s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-nmr took 2.5581400394439697s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 0.0004584789276123047s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.2832973003387451s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.02060866355895996s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.0001087188720703125s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-nonrctontology took 2.7006945610046387s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for NanoParticle Ontology took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.2757914066314697s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.020365476608276367s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.0011985301971435547s
Believability | Calculation of trust value for NanoParticle Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-npo took 2.7660880088806152s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 4.2438507080078125e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.2823042869567871s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.0203859806060791s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0007920265197753906s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-oae took 2.5626041889190674s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 4.100799560546875e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 0.0012612342834472656s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 0.285510778427124s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.02012801170349121s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.0014667510986328125s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-obi took 2.6962428092956543s
Availability | SPARQL endpoint availability check for OBOE took 4.0531158447265625e-05s
Availability | VoID file availability check for OBOE took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for OBOE took 0.2515435218811035s
Reputation | Calculation of the PageRank for OBOE took 0.02023458480834961s
Interlinking | Calculation of Degree of Connection for OBOE took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for OBOE took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.00011014938354492188s
Believability | Calculation of trust value for OBOE took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-oboe took 2.633610248565674s
Availability | SPARQL endpoint availability check for OBOE SBC took 3.981590270996094e-05s
Availability | VoID file availability check for OBOE SBC took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for OBOE SBC took 0.261476993560791s
Reputation | Calculation of the PageRank for OBOE SBC took 0.020112276077270508s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0007805824279785156s
Believability | Calculation of trust value for OBOE SBC took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-oboe-sbc took 2.625502824783325s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 4.172325134277344e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 0.2702927589416504s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.02047252655029297s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0005860328674316406s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ocre took 2.6226234436035156s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 7.557868957519531e-05s
Availability | VoID file availability check for Ontology for disease genetic investigation took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 0.25885653495788574s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.020668983459472656s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0008561611175537109s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-odgi took 2.6905832290649414s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 5.14984130859375e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 0.26700425148010254s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.020112037658691406s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0008821487426757812s
Believability | Calculation of trust value for Ontology for Genetic Interval took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ogi took 2.634463310241699s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 4.100799560546875e-05s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 0.26660752296447754s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.019913911819458008s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.00028395652770996094s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ogmd took 2.617964744567871s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 4.1484832763671875e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.29164576530456543s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.020052671432495117s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0006685256958007812s
Believability | Calculation of trust value for Ontology for General Medical Science took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ogms took 2.731114387512207s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 4.482269287109375e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.0005893707275390625s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.25382113456726074s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.020415544509887695s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.001130819320678711s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-omim took 2.6759636402130127s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 4.482269287109375e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.26598167419433594s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.020288944244384766s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.0003674030303955078s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-omit took 2.7123823165893555s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 4.029273986816406e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.00021839141845703125s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.2747316360473633s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.02049708366394043s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0006041526794433594s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-omrse took 2.4317500591278076s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 6.341934204101562e-05s
Availability | VoID file availability check for Ontology of Data Mining took 0.0005757808685302734s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.2666962146759033s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.020223379135131836s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.0007691383361816406s
Believability | Calculation of trust value for Ontology of Data Mining took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ontodm took 2.7101638317108154s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 3.910064697265625e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 0.25528645515441895s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.020284175872802734s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.0002484321594238281s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ontodt took 2.6158037185668945s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 4.00543212890625e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.24659466743469238s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.020446062088012695s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.000591278076171875s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ontoorpha took 2.65913724899292s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 3.9577484130859375e-05s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 0.0004267692565917969s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 0.2727665901184082s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.020199060440063477s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0009186267852783203s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-opl took 2.5978658199310303s
Availability | SPARQL endpoint availability check for Phenotypic quality took 4.029273986816406e-05s
Availability | VoID file availability check for Phenotypic quality took 0.0005228519439697266s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.24979853630065918s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.020199060440063477s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0008649826049804688s
Believability | Calculation of trust value for Phenotypic quality took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-pato took 2.6284992694854736s
Availability | SPARQL endpoint availability check for Physician Data Query took 3.933906555175781e-05s
Availability | VoID file availability check for Physician Data Query took 0.00044655799865722656s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.27919816970825195s
Reputation | Calculation of the PageRank for Physician Data Query took 0.020291805267333984s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Physician Data Query took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0007965564727783203s
Believability | Calculation of trust value for Physician Data Query took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-pdq took 2.671100616455078s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 3.910064697265625e-05s
Availability | VoID file availability check for Pediatric Terminology took 0.0004787445068359375s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.2747960090637207s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.02020430564880371s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0007932186126708984s
Believability | Calculation of trust value for Pediatric Terminology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-pedterm took 2.702867031097412s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 0.28698134422302246s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.020374536514282227s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.0001976490020751953s
Believability | Calculation of trust value for Parasite Experiment Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-peo took 2.8567447662353516s
Availability | SPARQL endpoint availability check for PHARE took 7.176399230957031e-05s
Availability | VoID file availability check for PHARE took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for PHARE took 0.2721436023712158s
Reputation | Calculation of the PageRank for PHARE took 0.02032160758972168s
Interlinking | Calculation of Degree of Connection for PHARE took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PHARE took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006277561187744141s
Believability | Calculation of trust value for PHARE took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-phare took 2.647343397140503s
Availability | SPARQL endpoint availability check for PKO_Re took 4.00543212890625e-05s
Availability | VoID file availability check for PKO_Re took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.25679707527160645s
Reputation | Calculation of the PageRank for PKO_Re took 0.020452022552490234s
Interlinking | Calculation of Degree of Connection for PKO_Re took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PKO_Re took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.000171661376953125s
Believability | Calculation of trust value for PKO_Re took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-pko took 2.644157648086548s
Availability | SPARQL endpoint availability check for PMA 2010 took 4.00543212890625e-05s
Availability | VoID file availability check for PMA 2010 took 0.0004527568817138672s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.2969648838043213s
Reputation | Calculation of the PageRank for PMA 2010 took 0.02022695541381836s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PMA 2010 took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0008974075317382812s
Believability | Calculation of trust value for PMA 2010 took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-pma took 2.725771188735962s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 3.981590270996094e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.2847774028778076s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.02033686637878418s
Interlinking | Calculation of Degree of Connection for Physical Medicine and Rehabilitation took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Physical Medicine and Rehabilitation took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.0001652240753173828s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-pmr took 2.624238967895508s
Availability | SPARQL endpoint availability check for Plant Anatomy took 4.6253204345703125e-05s
Availability | VoID file availability check for Plant Anatomy took 0.0006000995635986328s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.25887632369995117s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.020602941513061523s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.0003902912139892578s
Believability | Calculation of trust value for Plant Anatomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-po took 2.6242640018463135s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 3.9577484130859375e-05s
Availability | VoID file availability check for Plant Growth and Development Stage took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.2991962432861328s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.02051854133605957s
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.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 6.699562072753906e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-po_x1 took 2.6872146129608154s
Availability | SPARQL endpoint availability check for Plant Ontology took 4.00543212890625e-05s
Availability | VoID file availability check for Plant Ontology took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.28870391845703125s
Reputation | Calculation of the PageRank for Plant Ontology took 0.0202791690826416s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.00043463706970214844s
Believability | Calculation of trust value for Plant Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-po_x2 took 2.601287603378296s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 3.933906555175781e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.2764098644256592s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.020328283309936523s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0006651878356933594s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-pr took 2.5637946128845215s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 4.100799560546875e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 0.2931380271911621s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.020484447479248047s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.00025653839111328125s
Believability | Calculation of trust value for Proteomics data and process provenance took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-propreo took 2.7193665504455566s
Availability | SPARQL endpoint availability check for Pathway ontology took 3.9577484130859375e-05s
Availability | VoID file availability check for Pathway ontology took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.2725398540496826s
Reputation | Calculation of the PageRank for Pathway ontology took 0.020275354385375977s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Pathway ontology took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.00012254714965820312s
Believability | Calculation of trust value for Pathway ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-pw took 2.657545566558838s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 5.269050598144531e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.26085686683654785s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.020316600799560547s
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.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 3.0517578125e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-qibo took 2.724017858505249s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 4.0531158447265625e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.00045371055603027344s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.3549692630767822s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.02052783966064453s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.001737356185913086s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-rcd took 3.101012945175171s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.2771759033203125s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.02048492431640625s
Interlinking | Calculation of Degree of Connection for Randomized Controlled Trials (RCT) Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Randomized Controlled Trials (RCT) Ontology took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.00012946128845214844s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-rctontology took 2.729326009750366s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.263141393661499s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.020451068878173828s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 9.72747802734375e-05s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-repo took 2.707517623901367s
Availability | SPARQL endpoint availability check for Physico-chemical process took 3.933906555175781e-05s
Availability | VoID file availability check for Physico-chemical process took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.2526850700378418s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.020475387573242188s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.00019121170043945312s
Believability | Calculation of trust value for Physico-chemical process took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-rex took 2.6351466178894043s
Availability | SPARQL endpoint availability check for RadLex took 4.363059997558594e-05s
Availability | VoID file availability check for RadLex took 0.0005970001220703125s
Completeness | Calculation of interlinking completeness for RadLex took 0.26737189292907715s
Reputation | Calculation of the PageRank for RadLex took 0.020630359649658203s
Interlinking | Calculation of Degree of Connection for RadLex took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RadLex took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.0015158653259277344s
Believability | Calculation of trust value for RadLex took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-rid took 2.6293742656707764s
Availability | SPARQL endpoint availability check for RNA ontology took 4.363059997558594e-05s
Availability | VoID file availability check for RNA ontology took 0.00034332275390625s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.26071977615356445s
Reputation | Calculation of the PageRank for RNA ontology took 0.020107030868530273s
Interlinking | Calculation of Degree of Connection for RNA ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for RNA ontology took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0005459785461425781s
Believability | Calculation of trust value for RNA ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-rnao took 2.4774692058563232s
Availability | SPARQL endpoint availability check for Role Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Role Ontology took 0.0005338191986083984s
Completeness | Calculation of interlinking completeness for Role Ontology took 0.288654088973999s
Reputation | Calculation of the PageRank for Role Ontology took 0.0310819149017334s
Interlinking | Calculation of Degree of Connection for Role Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Role Ontology took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.0002281665802001953s
Believability | Calculation of trust value for Role Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-roleo took 2.6819117069244385s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 3.981590270996094e-05s
Availability | VoID file availability check for Rat Strain Ontology took 0.0005433559417724609s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.2742729187011719s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.020640134811401367s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.00018525123596191406s
Believability | Calculation of trust value for Rat Strain Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-rs took 2.712294816970825s
Availability | SPARQL endpoint availability check for RxNORM took 6.604194641113281e-05s
Availability | VoID file availability check for RxNORM took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for RxNORM took 0.2624397277832031s
Reputation | Calculation of the PageRank for RxNORM took 0.020633220672607422s
Interlinking | Calculation of Degree of Connection for RxNORM took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for RxNORM took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0006124973297119141s
Believability | Calculation of trust value for RxNORM took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-rxnorm took 2.627558708190918s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 4.839897155761719e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.0005536079406738281s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.251126766204834s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.020244121551513672s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.0010523796081542969s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-sao took 2.595993757247925s
Availability | SPARQL endpoint availability check for Systems Biology took 3.838539123535156e-05s
Availability | VoID file availability check for Systems Biology took 0.0004916191101074219s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.25533199310302734s
Reputation | Calculation of the PageRank for Systems Biology took 0.020377159118652344s
Interlinking | Calculation of Degree of Connection for Systems Biology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Systems Biology took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.00046133995056152344s
Believability | Calculation of trust value for Systems Biology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-sbo took 2.718273639678955s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 8.606910705566406e-05s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.0005314350128173828s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.25917577743530273s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.020499706268310547s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0008127689361572266s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.00011706352233886719s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-sbro took 2.9271671772003174s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Sleep Domain Ontology took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.29030323028564453s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.02072882652282715s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.0013284683227539062s
Believability | Calculation of trust value for Sleep Domain Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-sdo took 2.7195611000061035s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 4.0531158447265625e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.26285862922668457s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.0200650691986084s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.00034046173095703125s
Believability | Calculation of trust value for Sample processing and separation techniques took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-sep took 2.690831184387207s
Availability | SPARQL endpoint availability check for Student Health Record took 4.076957702636719e-05s
Availability | VoID file availability check for Student Health Record took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.2731020450592041s
Reputation | Calculation of the PageRank for Student Health Record took 0.02003931999206543s
Interlinking | Calculation of Degree of Connection for Student Health Record took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Student Health Record took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.0004372596740722656s
Believability | Calculation of trust value for Student Health Record took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-shr took 2.6667892932891846s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.0007376670837402344s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 0.27770304679870605s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.02001214027404785s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.0012278556823730469s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-sio took 3.5833914279937744s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 4.076957702636719e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 0.26816701889038086s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.020097970962524414s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.0002014636993408203s
Believability | Calculation of trust value for Situation-Based Access Control took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-sitbac took 2.6527674198150635s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 4.029273986816406e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.3091859817504883s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.026530027389526367s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.002013683319091797s
Believability | Calculation of trust value for SNOMED Clinical Terms took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-snomedct took 3.036278486251831s
Availability | SPARQL endpoint availability check for SNP-Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for SNP-Ontology took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.27435803413391113s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.020412683486938477s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0006754398345947266s
Believability | Calculation of trust value for SNP-Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-snpo took 2.6244659423828125s
Availability | SPARQL endpoint availability check for Sequence types and features took 4.410743713378906e-05s
Availability | VoID file availability check for Sequence types and features took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.2762131690979004s
Reputation | Calculation of the PageRank for Sequence types and features took 0.020336389541625977s
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.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0006070137023925781s
Believability | Calculation of trust value for Sequence types and features took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-so_x1 took 2.660435438156128s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 4.124641418457031e-05s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 0.00054931640625s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.32230210304260254s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.020924091339111328s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.001596212387084961s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-sopharm took 3.057636260986328s
Availability | SPARQL endpoint availability check for SoyOntology took 3.9577484130859375e-05s
Availability | VoID file availability check for SoyOntology took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.28122615814208984s
Reputation | Calculation of the PageRank for SoyOntology took 0.020390748977661133s
Interlinking | Calculation of Degree of Connection for SoyOntology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SoyOntology took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.00012803077697753906s
Believability | Calculation of trust value for SoyOntology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-soy took 2.639028549194336s
Availability | SPARQL endpoint availability check for Spider Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Spider Ontology took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.26741814613342285s
Reputation | Calculation of the PageRank for Spider Ontology took 0.020339250564575195s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0007913112640380859s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.00034046173095703125s
Believability | Calculation of trust value for Spider Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-spd took 2.7349469661712646s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.2495260238647461s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.019908666610717773s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.00027370452880859375s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-spto took 2.7240419387817383s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.00029850006103515625s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.25977587699890137s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.020146608352661133s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.00043702125549316406s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-sso took 2.676593542098999s
Availability | SPARQL endpoint availability check for Software Ontology took 5.316734313964844e-05s
Availability | VoID file availability check for Software Ontology took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.2723078727722168s
Reputation | Calculation of the PageRank for Software Ontology took 0.019956111907958984s
Interlinking | Calculation of Degree of Connection for Software Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Software Ontology took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.00042176246643066406s
Believability | Calculation of trust value for Software Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-swo took 2.671992778778076s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 4.00543212890625e-05s
Availability | VoID file availability check for Tick gross anatomy took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.2431960105895996s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.0205078125s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.00023746490478515625s
Believability | Calculation of trust value for Tick gross anatomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-tads took 2.584686756134033s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 3.933906555175781e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.28830885887145996s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.019971609115600586s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0008742809295654297s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-tao took 2.685365676879883s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 4.029273986816406e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.28167080879211426s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.020074129104614258s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 8.249282836914062e-05s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-taxrank took 2.656550168991089s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 4.0531158447265625e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.28508949279785156s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.020074129104614258s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 6.985664367675781e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-teddy took 2.7040822505950928s
Availability | SPARQL endpoint availability check for Time Event Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Time Event Ontology took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.28548383712768555s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.020368337631225586s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0008053779602050781s
Believability | Calculation of trust value for Time Event Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-teo took 2.683156967163086s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 3.9577484130859375e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.2661440372467041s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.02028632164001465s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.0004024505615234375s
Believability | Calculation of trust value for Mosquito gross anatomy took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-tgma took 2.6662087440490723s
Availability | SPARQL endpoint availability check for thesaurus took 3.981590270996094e-05s
Availability | VoID file availability check for thesaurus took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for thesaurus took 0.2931694984436035s
Reputation | Calculation of the PageRank for thesaurus took 0.02002716064453125s
Interlinking | Calculation of Degree of Connection for thesaurus took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for thesaurus took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for thesaurus took 6.4849853515625e-05s
Believability | Calculation of trust value for thesaurus took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-thesaurus took 2.642416000366211s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 4.076957702636719e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.26554441452026367s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.019991159439086914s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.0003533363342285156s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 3.147125244140625e-05s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 2.5744354724884033s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Translational Medicine Ontology took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.2765681743621826s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.019879579544067383s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0008394718170166016s
Believability | Calculation of trust value for Translational Medicine Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-tmo took 2.637449026107788s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Plant Trait Ontology took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 0.278200626373291s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.020781755447387695s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.00015974044799804688s
Believability | Calculation of trust value for Plant Trait Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-to took 2.6613447666168213s
Availability | SPARQL endpoint availability check for TOK_Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for TOK_Ontology took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 0.2624497413635254s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.020537376403808594s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.00018405914306640625s
Believability | Calculation of trust value for TOK_Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-tok took 2.63010311126709s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 4.076957702636719e-05s
Availability | VoID file availability check for Teleost taxonomy took 0.0010845661163330078s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 0.27538299560546875s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.020195484161376953s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.00019168853759765625s
Believability | Calculation of trust value for Teleost taxonomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-tto took 2.6228463649749756s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Uber anatomy ontology took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.27466702461242676s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.020031213760375977s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.0010521411895751953s
Believability | Calculation of trust value for Uber anatomy ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-uberon took 2.6597378253936768s
Availability | SPARQL endpoint availability check for Units Ontology took 4.553794860839844e-05s
Availability | VoID file availability check for Units Ontology took 0.0005583763122558594s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.264695405960083s
Reputation | Calculation of the PageRank for Units Ontology took 0.020735979080200195s
Interlinking | Calculation of Degree of Connection for Units Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Units Ontology took 0.0009622573852539062s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.0002620220184326172s
Believability | Calculation of trust value for Units Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-unitsontology took 2.626150131225586s
Availability | SPARQL endpoint availability check for Units of measurement took 4.00543212890625e-05s
Availability | VoID file availability check for Units of measurement took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for Units of measurement took 0.2588667869567871s
Reputation | Calculation of the PageRank for Units of measurement took 0.02006053924560547s
Interlinking | Calculation of Degree of Connection for Units of measurement took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Units of measurement took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.0002796649932861328s
Believability | Calculation of trust value for Units of measurement took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-uo took 2.6883633136749268s
Availability | SPARQL endpoint availability check for VANDF took 5.507469177246094e-05s
Availability | VoID file availability check for VANDF took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for VANDF took 0.2773468494415283s
Reputation | Calculation of the PageRank for VANDF took 0.020428895950317383s
Interlinking | Calculation of Degree of Connection for VANDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for VANDF took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0007359981536865234s
Believability | Calculation of trust value for VANDF took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-vandf took 2.7001490592956543s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 3.9577484130859375e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.0004677772521972656s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 0.28647947311401367s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.020026683807373047s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.0004172325134277344s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-vao took 2.686833620071411s
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 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 0.2624950408935547s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.020151615142822266s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0006203651428222656s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-vhog took 2.6366398334503174s
Availability | SPARQL endpoint availability check for VIVO took 4.00543212890625e-05s
Availability | VoID file availability check for VIVO took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for VIVO took 0.26625728607177734s
Reputation | Calculation of the PageRank for VIVO took 0.020254850387573242s
Interlinking | Calculation of Degree of Connection for VIVO took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for VIVO took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.0003390312194824219s
Believability | Calculation of trust value for VIVO took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-vivo took 2.731823682785034s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Vaccine Ontology took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.24436688423156738s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.020406246185302734s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.0012612342834472656s
Believability | Calculation of trust value for Vaccine Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-vo took 2.6730098724365234s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.28881287574768066s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.020293235778808594s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0008172988891601562s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.00021195411682128906s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-vt took 2.628694772720337s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 4.363059997558594e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.26521730422973633s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.020485401153564453s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.0005297660827636719s
Believability | Calculation of trust value for C. elegans gross anatomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-wbbt took 2.580036163330078s
Availability | SPARQL endpoint availability check for C. elegans development took 4.076957702636719e-05s
Availability | VoID file availability check for C. elegans development took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.29085779190063477s
Reputation | Calculation of the PageRank for C. elegans development took 0.020405054092407227s
Interlinking | Calculation of Degree of Connection for C. elegans development took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for C. elegans development took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 4.649162292480469e-05s
Believability | Calculation of trust value for C. elegans development took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-wbls took 2.6966183185577393s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 4.2438507080078125e-05s
Availability | VoID file availability check for C. elegans phenotype took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.2758979797363281s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.02018141746520996s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 8.654594421386719e-05s
Believability | Calculation of trust value for C. elegans phenotype took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-wbphenotype took 2.6868393421173096s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 4.029273986816406e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.2684197425842285s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.0203704833984375s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0006070137023925781s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-who took 2.7169711589813232s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 4.172325134277344e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.28597164154052734s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.020174264907836914s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.0006978511810302734s
Believability | Calculation of trust value for Xenopus anatomy and development took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-xao took 2.7092385292053223s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.2703869342803955s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.02033853530883789s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0007932186126708984s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.00023865699768066406s
Believability | Calculation of trust value for Experimental Conditions Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-xco took 2.5848052501678467s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 4.124641418457031e-05s
Availability | VoID file availability check for Yeast phenotypes took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 0.28593921661376953s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.020595788955688477s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0010302066802978516s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.0002696514129638672s
Believability | Calculation of trust value for Yeast phenotypes took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ypo took 2.769951105117798s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 4.00543212890625e-05s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 0.26752328872680664s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.020093917846679688s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.0007646083831787109s
Believability | Calculation of trust value for Zebrafish anatomy and development took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-zfa took 2.676467180252075s
Availability | SPARQL endpoint availability check for Indian Terrorism Ontology (InTO) took 4.076957702636719e-05s
Availability | VoID file availability check for Indian Terrorism Ontology (InTO) took 0.0005998611450195312s
Completeness | Calculation of interlinking completeness for Indian Terrorism Ontology (InTO) took 0.2753136157989502s
Reputation | Calculation of the PageRank for Indian Terrorism Ontology (InTO) took 0.020026445388793945s
Interlinking | Calculation of Degree of Connection for Indian Terrorism Ontology (InTO) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Indian Terrorism Ontology (InTO) took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Indian Terrorism Ontology (InTO) took 2.6702880859375e-05s
Believability | Calculation of trust value for Indian Terrorism Ontology (InTO) took 6.9141387939453125e-06s
INFO | --- Analysis for Bioportal_link took 3.3787834644317627s
Availability | SPARQL endpoint availability check for BioSamples RDF took 0.45623111724853516s
Availability | VoID file availability check for BioSamples RDF took 0.0004551410675048828s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.27546238899230957s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.02040576934814453s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 3.314018249511719e-05s
Believability | Calculation of trust value for BioSamples RDF took 7.152557373046875e-06s
INFO | --- Analysis for biosamples-rdf took 4.504912853240967s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 0.5529818534851074s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 0.26326417922973633s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.019918441772460938s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.00011277198791503906s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for bis-linked-data took 3.0211782455444336s
Availability | SPARQL endpoint availability check for Bitzi took 4.076957702636719e-05s
Availability | VoID file availability check for Bitzi took 0.00023818016052246094s
Completeness | Calculation of interlinking completeness for Bitzi took 0.25968217849731445s
Reputation | Calculation of the PageRank for Bitzi took 0.0204010009765625s
Interlinking | Calculation of Degree of Connection for Bitzi took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bitzi took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Bitzi took 2.9325485229492188e-05s
Believability | Calculation of trust value for Bitzi took 7.62939453125e-06s
INFO | --- Analysis for bitzi took 2.946234703063965s
Availability | SPARQL endpoint availability check for BizkaiSense took 4.00543212890625e-05s
Availability | VoID file availability check for BizkaiSense took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for BizkaiSense took 0.26541686058044434s
Reputation | Calculation of the PageRank for BizkaiSense took 0.020761728286743164s
Interlinking | Calculation of Degree of Connection for BizkaiSense took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BizkaiSense took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for BizkaiSense took 3.218650817871094e-05s
Believability | Calculation of trust value for BizkaiSense took 8.106231689453125e-06s
INFO | --- Analysis for bizkaisense took 2.860593795776367s
Availability | SPARQL endpoint availability check for blabla.itemlist took 4.124641418457031e-05s
Availability | VoID file availability check for blabla.itemlist took 0.00022530555725097656s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.278444766998291s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.02070474624633789s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 3.0279159545898438e-05s
Believability | Calculation of trust value for blabla.itemlist took 7.152557373046875e-06s
INFO | --- Analysis for blabla-itemlist took 2.8788397312164307s
Availability | SPARQL endpoint availability check for blabla.itemlist took 3.910064697265625e-05s
Availability | VoID file availability check for blabla.itemlist took 0.00023102760314941406s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.25861239433288574s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.020598888397216797s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 2.8848648071289062e-05s
Believability | Calculation of trust value for blabla.itemlist took 6.9141387939453125e-06s
INFO | --- Analysis for blabla_itemlist took 2.911168098449707s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.0531158447265625e-05s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0003597736358642578s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.2585909366607666s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.020284652709960938s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 3.743171691894531e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for bll-thesaurus took 3.6719279289245605s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 0.49344563484191895s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.0006659030914306641s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 0.272418737411499s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.020493030548095703s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 6.270408630371094e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 7.152557373046875e-06s
INFO | --- Analysis for bluk-bnb took 10.31224513053894s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.343555212020874s
Availability | VoID file availability check for Thesaurus BNCF took 0.0006000995635986328s
Extra | Recovery of all triples for Thesaurus BNCF took 47.505112648010254s
Performance | Total latancy measurement for Thesaurus BNCF took 0.6826884746551514s
Amount of data | Number of triples check for Thesaurus BNCF took 0.6700701713562012s
Interoperability | New terms check for Thesaurus BNCF took 1.51011323928833s
Versatility | Languages check for Thesaurus BNCF took 6.8734002113342285s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 0.918419361114502s
Security | Check HTTPS for Thesaurus BNCF took 0.09558343887329102s
Interpretability | RDF structures check for Thesaurus BNCF took 0.1365365982055664s
Versatility | Serialization formats check for Thesaurus BNCF took 0.13208699226379395s
Availability | RDF dump link check for Thesaurus BNCF took 0.12254643440246582s
License | MR license check for Thesaurus BNCF took 0.12894487380981445s
License | HR license check for Thesaurus BNCF took 0.20763826370239258s
Amount of data | Number of property check for Thesaurus BNCF took 0.2369077205657959s
Understandability | Number of label check for Thesaurus BNCF took 0.2592000961303711s
Understandability | URI regex check for Thesaurus BNCF took 0.2541968822479248s
Understandability | Vocabs check for Thesaurus BNCF took 0.13454961776733398s
Verifiability | Authors check for Thesaurus BNCF took 0.1313467025756836s
Verifiability | Publishers check for Thesaurus BNCF took 0.1351470947265625s
Performance | Throughput check for Thesaurus BNCF took 10.81076431274414s
Amount of data | Check the number of entities for Thesaurus BNCF took 3.123283386230469e-05s
Verifiability | Contribs. check for Thesaurus BNCF took 0.12006759643554688s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.12279939651489258s
Interlinking | skos check for Thesaurus BNCF took 0.17060041427612305s
Interlinking | skos check for Thesaurus BNCF took 0.15306782722473145s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.12286829948425293s
Currency | Creation date check for Thesaurus BNCF took 0.2409050464630127s
Currency | Modification date check for Thesaurus BNCF took 0.2357020378112793s
Rep.Conc. | URIs length for Thesaurus BNCF took 24.14484190940857s
Interoperability | New vocabularies check for Thesaurus BNCF took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.1298825740814209s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.11702680587768555s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.11985921859741211s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 11.064520120620728s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.5111467838287354s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 3.9452080726623535s
Consistency | Disjoint class check for Thesaurus BNCF took 0.12473917007446289s
Consistency | Check Misplaced properties for Thesaurus BNCF took 0.9686064720153809s
Consistency | Misplaced classes for Thesaurus BNCF took 6.75659966468811s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 7.8076677322387695s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.397179126739502s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.178943157196045s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.439553737640381s
Security | Sign check for Thesaurus BNCF took 0.1277613639831543s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 19.47400450706482s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.37817931175231934s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.02040719985961914s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 7.62939453125e-05s
Interoperability | Check the re-using of existing vocabs for Thesaurus BNCF took 2.384185791015625e-06s
Believability | Calculation of trust value for Thesaurus BNCF took 6.4373016357421875e-06s
INFO | --- Analysis for bncf-ns took 184.73611760139465s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4503805637359619s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0006885528564453125s
Extra | Recovery of all triples for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.7635884284973145s
Performance | Total latancy measurement for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.4736030101776123s
Amount of data | Number of triples check for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.3239452838897705s
Interoperability | New terms check for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.153475046157837s
Versatility | Languages check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.292723178863525s
Interpretability | Number of blank nodes check for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.9025559425354004s
Security | Check HTTPS for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.21674466133117676s
Interpretability | RDF structures check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.33439064025878906s
Versatility | Serialization formats check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5533294677734375s
Availability | RDF dump link check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.47524571418762207s
License | MR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6104681491851807s
License | HR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.28813099861145s
Amount of data | Number of property check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.2703406810760498s
Understandability | Number of label check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.0949172973632812s
Understandability | URI regex check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6016592979431152s
Understandability | Vocabs check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.42816901206970215s
Verifiability | Authors check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4221611022949219s
Verifiability | Publishers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3218858242034912s
Performance | Throughput check for BPR ? Bibliography of the Italian Parliament and electoral studies took 11.163448572158813s
Amount of data | Check the number of entities for BPR ? Bibliography of the Italian Parliament and electoral studies took 6.985664367675781e-05s
Verifiability | Contribs. check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.32031702995300293s
Interlinking | sameAs chians check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.2997303009033203s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3078453540802002s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.31500768661499023s
Timeliness | dataset update frequency check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.40581464767456055s
Currency | Creation date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6446597576141357s
Currency | Modification date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.31938886642456055s
Rep.Conc. | URIs length for BPR ? Bibliography of the Italian Parliament and electoral studies took 18.182989597320557s
Interoperability | New vocabularies check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3082735538482666s
Accuracy | Check Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.26921796798706055s
Accuracy | Check Inverse Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.31049060821533203s
Accuracy | Check Empty annotation labels for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.9729287624359131s
Accuracy | Check White space in annotation for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.030475378036499023s
Accuracy | Check Datatype consistency for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.02911090850830078s
Consistency | Disjoint class check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.25866079330444336s
Consistency | Check Misplaced properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 13.745574951171875s
Consistency | Misplaced classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.360595703125s
Consistency | Check Ontology hijacking for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.412550926208496s
Consistency | Check Invalid usage of undefined classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.6817927360534668s
Consistency | Check Invalid usage of undefined properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 15.05156135559082s
Conciseness | Check Extensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.03160595893859863s
Conciseness | Check Intensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.34284353256225586s
Security | Sign check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.32839250564575195s
Availability | Check URIs Dereferenciability for BPR ? Bibliography of the Italian Parliament and electoral studies took 6.220026969909668s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.793776273727417s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.020649433135986328s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.935264587402344e-05s
Interoperability | Check the re-using of existing vocabs for BPR ? Bibliography of the Italian Parliament and electoral studies took 9.5367431640625e-07s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 7.152557373046875e-06s
INFO | --- Analysis for bpr took 390.5405604839325s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 5.316734313964844e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.2670779228210449s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.02088451385498047s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 7.271766662597656e-05s
Believability | Calculation of trust value for Brazilian Politicians took 4.76837158203125e-06s
INFO | --- Analysis for brazilian-politicians took 2.9411256313323975s
Availability | SPARQL endpoint availability check for BrazilianCities took 5.245208740234375e-05s
Availability | VoID file availability check for BrazilianCities took 0.00029778480529785156s
Completeness | Calculation of interlinking completeness for BrazilianCities took 0.28089284896850586s
Reputation | Calculation of the PageRank for BrazilianCities took 0.020490407943725586s
Interlinking | Calculation of Degree of Connection for BrazilianCities took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BrazilianCities took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for BrazilianCities took 3.1948089599609375e-05s
Believability | Calculation of trust value for BrazilianCities took 7.62939453125e-06s
INFO | --- Analysis for braziliancities took 4.81470513343811s
Availability | SPARQL endpoint availability check for Bricklink took 1.7847232818603516s
Availability | VoID file availability check for Bricklink took 0.0007495880126953125s
Completeness | Calculation of interlinking completeness for Bricklink took 0.2700841426849365s
Reputation | Calculation of the PageRank for Bricklink took 0.020398378372192383s
Interlinking | Calculation of Degree of Connection for Bricklink took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bricklink took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Bricklink took 6.532669067382812e-05s
Believability | Calculation of trust value for Bricklink took 3.337860107421875e-05s
INFO | --- Analysis for bricklink took 13.65616774559021s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.154375076293945s
Availability | VoID file availability check for British Museum Collection took 0.0006382465362548828s
Completeness | Calculation of interlinking completeness for British Museum Collection took 0.27614545822143555s
Reputation | Calculation of the PageRank for British Museum Collection took 0.02004694938659668s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for British Museum Collection took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 3.1948089599609375e-05s
Believability | Calculation of trust value for British Museum Collection took 6.67572021484375e-06s
INFO | --- Analysis for british-museum-collection took 73.50937676429749s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 4.029273986816406e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.0004355907440185547s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.259685754776001s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.020645856857299805s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 3.814697265625e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 7.152557373046875e-06s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 3.261681079864502s
Availability | SPARQL endpoint availability check for French Plant Health Bulletins took 3.933906555175781e-05s
Availability | VoID file availability check for French Plant Health Bulletins took 0.0002219676971435547s
Completeness | Calculation of interlinking completeness for French Plant Health Bulletins took 0.26810288429260254s
Reputation | Calculation of the PageRank for French Plant Health Bulletins took 0.020155668258666992s
Interlinking | Calculation of Degree of Connection for French Plant Health Bulletins took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for French Plant Health Bulletins took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for French Plant Health Bulletins took 2.7894973754882812e-05s
Believability | Calculation of trust value for French Plant Health Bulletins took 7.152557373046875e-06s
INFO | --- Analysis for bsv took 2.9847092628479004s
Availability | SPARQL endpoint availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.8449277877807617s
Availability | VoID file availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0006914138793945312s
Completeness | Calculation of interlinking completeness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.2746002674102783s
Reputation | Calculation of the PageRank for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.020439863204956055s
Interlinking | Calculation of Degree of Connection for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.430511474609375e-05s
Believability | Calculation of trust value for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 6.9141387939453125e-06s
INFO | --- Analysis for bulgarian_admissions_to_correctional_facilities took 7.492960691452026s
Availability | SPARQL endpoint availability check for Bund Offener Haushalt took 4.076957702636719e-05s
Availability | VoID file availability check for Bund Offener Haushalt took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for Bund Offener Haushalt took 0.24684381484985352s
Reputation | Calculation of the PageRank for Bund Offener Haushalt took 0.020328760147094727s
Interlinking | Calculation of Degree of Connection for Bund Offener Haushalt took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bund Offener Haushalt took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for Bund Offener Haushalt took 3.24249267578125e-05s
Believability | Calculation of trust value for Bund Offener Haushalt took 6.67572021484375e-06s
INFO | --- Analysis for bund-offener-haushalt took 2.878204822540283s
Availability | SPARQL endpoint availability check for BundestagNebeneinkuenfte took 4.2438507080078125e-05s
Availability | VoID file availability check for BundestagNebeneinkuenfte took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for BundestagNebeneinkuenfte took 0.24729275703430176s
Reputation | Calculation of the PageRank for BundestagNebeneinkuenfte took 0.020662307739257812s
Interlinking | Calculation of Degree of Connection for BundestagNebeneinkuenfte took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BundestagNebeneinkuenfte took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for BundestagNebeneinkuenfte took 3.4332275390625e-05s
Believability | Calculation of trust value for BundestagNebeneinkuenfte took 6.67572021484375e-06s
INFO | --- Analysis for bundestagnebeneinkuenfte took 2.898407220840454s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 0.3488895893096924s
Availability | VoID file availability check for business.data.gov.uk took 0.0006256103515625s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 0.273012638092041s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.020545005798339844s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 0.00015497207641601562s
Believability | Calculation of trust value for business.data.gov.uk took 5.4836273193359375e-06s
INFO | --- Analysis for business-data-gov-uk took 2.996053695678711s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 0.4945824146270752s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.0006582736968994141s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 1.540386438369751s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 1.4286139011383057s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 0.4445962905883789s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 1.574272632598877s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 30.263735055923462s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 0.29828405380249023s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.1368241310119629s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 0.5187954902648926s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 0.4129016399383545s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 0.4089198112487793s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 0.3545677661895752s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 20.166632413864136s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 0.4167020320892334s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 0.7533073425292969s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 0.8306186199188232s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.4552116394042969s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 0.3906893730163574s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.295764684677124s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 7.152557373046875e-05s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 0.23026371002197266s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 0.1867680549621582s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.2384035587310791s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.2428879737854004s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 0.24659299850463867s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 0.47252964973449707s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 0.51816725730896s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 0.3754868507385254s
Interoperability | New vocabularies check for Biblioteca Virtual Miguel de Cervantes took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for Biblioteca Virtual Miguel de Cervantes took 0.14832115173339844s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.03214907646179199s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 0.1349482536315918s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 0.13078975677490234s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 1.409010887145996s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.0343480110168457s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 0.1357128620147705s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 5.923891067504883s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 0.3719499111175537s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.0198671817779541s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 5.53131103515625e-05s
Interoperability | Check the re-using of existing vocabs for Biblioteca Virtual Miguel de Cervantes took 1.430511474609375e-06s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes took 8.344650268554688e-06s
INFO | --- Analysis for BVMC took 92.68500995635986s
Availability | SPARQL endpoint availability check for Price changes due to cabbage imports took 5.8650970458984375e-05s
Availability | VoID file availability check for Price changes due to cabbage imports took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Price changes due to cabbage imports took 0.2508695125579834s
Reputation | Calculation of the PageRank for Price changes due to cabbage imports took 0.019833803176879883s
Interlinking | Calculation of Degree of Connection for Price changes due to cabbage imports took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Price changes due to cabbage imports took 0.0006866455078125s
Interlinking | Calculation of Clustering coefficient for Price changes due to cabbage imports took 3.218650817871094e-05s
Believability | Calculation of trust value for Price changes due to cabbage imports took 7.867813110351562e-06s
INFO | --- Analysis for cabbage took 4.633290529251099s
Availability | SPARQL endpoint availability check for cablegate took 1.5885441303253174s
Availability | VoID file availability check for cablegate took 0.0003066062927246094s
Completeness | Calculation of interlinking completeness for cablegate took 0.2595252990722656s
Reputation | Calculation of the PageRank for cablegate took 0.020241260528564453s
Interlinking | Calculation of Degree of Connection for cablegate took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for cablegate took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for cablegate took 6.723403930664062e-05s
Believability | Calculation of trust value for cablegate took 7.3909759521484375e-06s
INFO | --- Analysis for cablegate took 7.170074701309204s
Availability | SPARQL endpoint availability check for Calames took 4.100799560546875e-05s
Availability | VoID file availability check for Calames took 0.0007481575012207031s
Completeness | Calculation of interlinking completeness for Calames took 0.25109004974365234s
Reputation | Calculation of the PageRank for Calames took 0.0205233097076416s
Interlinking | Calculation of Degree of Connection for Calames took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Calames took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Calames took 3.504753112792969e-05s
Believability | Calculation of trust value for Calames took 7.3909759521484375e-06s
INFO | --- Analysis for calames took 4.664625406265259s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.47719645500183105s
Availability | VoID file availability check for CaLiGraph took 0.0002598762512207031s
Extra | Recovery of all triples for CaLiGraph took 1.6556243896484375s
Performance | Total latancy measurement for CaLiGraph took 1.175297498703003s
Amount of data | Number of triples check for CaLiGraph took 12.615275144577026s
Interoperability | New terms check for CaLiGraph took 2.094853401184082s
Versatility | Languages check for CaLiGraph took 60.308308124542236s
Interpretability | Number of blank nodes check for CaLiGraph took 0.27878832817077637s
Security | Check HTTPS for CaLiGraph took 0.12726998329162598s
Interpretability | RDF structures check for CaLiGraph took 0.5726566314697266s
Versatility | Serialization formats check for CaLiGraph took 0.34574294090270996s
Availability | RDF dump link check for CaLiGraph took 0.2960984706878662s
License | MR license check for CaLiGraph took 0.47275614738464355s
License | HR license check for CaLiGraph took 60.326839447021484s
Amount of data | Number of property check for CaLiGraph took 0.26613616943359375s
Understandability | Number of label check for CaLiGraph took 5.387420654296875s
Understandability | URI regex check for CaLiGraph took 0.5631740093231201s
Understandability | Vocabs check for CaLiGraph took 0.27402734756469727s
Verifiability | Authors check for CaLiGraph took 0.28887057304382324s
Verifiability | Publishers check for CaLiGraph took 0.2531421184539795s
Performance | Throughput check for CaLiGraph took 11.446149349212646s
Amount of data | Check the number of entities for CaLiGraph took 0.017783164978027344s
Verifiability | Contribs. check for CaLiGraph took 0.26653027534484863s
Interlinking | sameAs chians check for CaLiGraph took 0.677361011505127s
Interlinking | skos check for CaLiGraph took 0.38266897201538086s
Interlinking | skos check for CaLiGraph took 0.23577499389648438s
Timeliness | dataset update frequency check for CaLiGraph took 0.30037951469421387s
Currency | Creation date check for CaLiGraph took 0.5874760150909424s
Currency | Modification date check for CaLiGraph took 0.5452570915222168s
Rep.Conc. | URIs length for CaLiGraph took 62.53620004653931s
Interoperability | New vocabularies check for CaLiGraph took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.26680922508239746s
Accuracy | Check Functional Property for CaLiGraph took 0.29381537437438965s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.2972712516784668s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.6186890602111816s
Accuracy | Check White space in annotation for CaLiGraph took 0.026838064193725586s
Accuracy | Check Datatype consistency for CaLiGraph took 0.02851247787475586s
Consistency | Disjoint class check for CaLiGraph took 0.26700687408447266s
Consistency | Check Misplaced properties for CaLiGraph took 61.03443264961243s
Consistency | Misplaced classes for CaLiGraph took 0.4660377502441406s
Consistency | Check Ontology hijacking for CaLiGraph took 2.006723642349243s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.2329041957855225s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.49679398536682s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.03281903266906738s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.48241472244262695s
Security | Sign check for CaLiGraph took 0.3761603832244873s
Availability | Check URIs Dereferenciability for CaLiGraph took 5.6627113819122314s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.92669677734375s
Reputation | Calculation of the PageRank for CaLiGraph took 0.02047419548034668s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 3.7670135498046875e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.430511474609375e-06s
Believability | Calculation of trust value for CaLiGraph took 7.62939453125e-06s
INFO | --- Analysis for CaLiGraph took 1447.550345659256s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.2519519329071045s
Availability | VoID file availability check for CaLiGraph took 0.0005955696105957031s
Extra | Recovery of all triples for CaLiGraph took 1.6356923580169678s
Performance | Total latancy measurement for CaLiGraph took 1.1308550834655762s
Amount of data | Number of triples check for CaLiGraph took 12.308356761932373s
Interoperability | New terms check for CaLiGraph took 2.0295586585998535s
Versatility | Languages check for CaLiGraph took 60.293426513671875s
Interpretability | Number of blank nodes check for CaLiGraph took 0.25809192657470703s
Security | Check HTTPS for CaLiGraph took 0.14089465141296387s
Interpretability | RDF structures check for CaLiGraph took 0.26230883598327637s
Versatility | Serialization formats check for CaLiGraph took 0.24369049072265625s
Availability | RDF dump link check for CaLiGraph took 0.2586033344268799s
License | MR license check for CaLiGraph took 0.29694437980651855s
License | HR license check for CaLiGraph took 60.296566009521484s
Amount of data | Number of property check for CaLiGraph took 0.2659134864807129s
Understandability | Number of label check for CaLiGraph took 3.077223777770996s
Understandability | URI regex check for CaLiGraph took 0.5092465877532959s
Understandability | Vocabs check for CaLiGraph took 0.25470590591430664s
Verifiability | Authors check for CaLiGraph took 0.26503992080688477s
Verifiability | Publishers check for CaLiGraph took 0.25758886337280273s
Performance | Throughput check for CaLiGraph took 11.705832719802856s
Amount of data | Check the number of entities for CaLiGraph took 0.010467290878295898s
Verifiability | Contribs. check for CaLiGraph took 0.2627100944519043s
Interlinking | sameAs chians check for CaLiGraph took 0.6547186374664307s
Interlinking | skos check for CaLiGraph took 0.26693105697631836s
Interlinking | skos check for CaLiGraph took 0.24302196502685547s
Timeliness | dataset update frequency check for CaLiGraph took 0.2387096881866455s
Currency | Creation date check for CaLiGraph took 0.4946177005767822s
Currency | Modification date check for CaLiGraph took 0.5199635028839111s
Rep.Conc. | URIs length for CaLiGraph took 62.65615940093994s
Interoperability | New vocabularies check for CaLiGraph took 4.76837158203125e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.24997591972351074s
Accuracy | Check Functional Property for CaLiGraph took 0.264819860458374s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.25890469551086426s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.566896915435791s
Accuracy | Check White space in annotation for CaLiGraph took 0.02655506134033203s
Accuracy | Check Datatype consistency for CaLiGraph took 0.02720475196838379s
Consistency | Disjoint class check for CaLiGraph took 0.2519402503967285s
Consistency | Check Misplaced properties for CaLiGraph took 60.987603425979614s
Consistency | Misplaced classes for CaLiGraph took 0.5362427234649658s
Consistency | Check Ontology hijacking for CaLiGraph took 2.1524202823638916s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.313554286956787s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.58358073234558s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.029886245727539062s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.44164252281188965s
Security | Sign check for CaLiGraph took 0.2563185691833496s
Availability | Check URIs Dereferenciability for CaLiGraph took 6.095861911773682s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.36489009857177734s
Reputation | Calculation of the PageRank for CaLiGraph took 0.02080845832824707s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 7.295608520507812e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.6689300537109375e-06s
Believability | Calculation of trust value for CaLiGraph took 7.152557373046875e-06s
INFO | --- Analysis for caligraph took 1442.726613998413s
Availability | SPARQL endpoint availability check for can-link took 4.100799560546875e-05s
Availability | VoID file availability check for can-link took 0.0002734661102294922s
Completeness | Calculation of interlinking completeness for can-link took 0.2900114059448242s
Reputation | Calculation of the PageRank for can-link took 0.020292282104492188s
Interlinking | Calculation of Degree of Connection for can-link took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for can-link took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for can-link took 3.123283386230469e-05s
Believability | Calculation of trust value for can-link took 8.344650268554688e-06s
INFO | --- Analysis for can-link took 4.23383092880249s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 0.06577801704406738s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.00046563148498535156s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.2877175807952881s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.0202639102935791s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 2.9325485229492188e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 7.152557373046875e-06s
INFO | --- Analysis for cap-italy-rdf took 3.5083680152893066s
Availability | SPARQL endpoint availability check for person took 4.076957702636719e-05s
Availability | VoID file availability check for person took 0.000286102294921875s
Completeness | Calculation of interlinking completeness for person took 0.2787613868713379s
Reputation | Calculation of the PageRank for person took 0.020412683486938477s
Interlinking | Calculation of Degree of Connection for person took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for person took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for person took 3.24249267578125e-05s
Believability | Calculation of trust value for person took 7.867813110351562e-06s
INFO | --- Analysis for card took 3.7668139934539795s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 4.0531158447265625e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0005970001220703125s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 0.2778027057647705s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.020374536514282227s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 4.649162292480469e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 6.4373016357421875e-06s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 4.27489161491394s
Availability | SPARQL endpoint availability check for Catalogus Professorum Lipsiensis took 5.6743621826171875e-05s
Availability | VoID file availability check for Catalogus Professorum Lipsiensis took 0.00021409988403320312s
Completeness | Calculation of interlinking completeness for Catalogus Professorum Lipsiensis took 0.2799811363220215s
Reputation | Calculation of the PageRank for Catalogus Professorum Lipsiensis took 0.02122044563293457s
Interlinking | Calculation of Degree of Connection for Catalogus Professorum Lipsiensis took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Catalogus Professorum Lipsiensis took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Catalogus Professorum Lipsiensis took 3.504753112792969e-05s
Believability | Calculation of trust value for Catalogus Professorum Lipsiensis took 7.62939453125e-06s
INFO | --- Analysis for catalogus-professorum-lipsiensis took 3.020387887954712s
Availability | SPARQL endpoint availability check for Norway catch records dataset @PSNC took 0.7787106037139893s
Availability | VoID file availability check for Norway catch records dataset @PSNC took 0.00025272369384765625s
Extra | Recovery of all triples for Norway catch records dataset @PSNC took 117.02980780601501s
Performance | Total latancy measurement for Norway catch records dataset @PSNC took 0.9271824359893799s
Amount of data | Number of triples check for Norway catch records dataset @PSNC took 9.076115846633911s
Interoperability | New terms check for Norway catch records dataset @PSNC took 14.2525794506073s
Versatility | Languages check for Norway catch records dataset @PSNC took 300.21579933166504s
Interpretability | Number of blank nodes check for Norway catch records dataset @PSNC took 3.2867612838745117s
Interpretability | RDF structures check for Norway catch records dataset @PSNC took 0.26917386054992676s
Versatility | Serialization formats check for Norway catch records dataset @PSNC took 9.691024541854858s
Availability | RDF dump link check for Norway catch records dataset @PSNC took 0.2892613410949707s
License | MR license check for Norway catch records dataset @PSNC took 0.649160623550415s
License | HR license check for Norway catch records dataset @PSNC took 300.1674826145172s
Amount of data | Number of property check for Norway catch records dataset @PSNC took 0.5001518726348877s
Understandability | Number of label check for Norway catch records dataset @PSNC took 2.54819917678833s
Understandability | URI regex check for Norway catch records dataset @PSNC took 0.6019771099090576s
Understandability | Vocabs check for Norway catch records dataset @PSNC took 0.3493664264678955s
Verifiability | Authors check for Norway catch records dataset @PSNC took 0.20733642578125s
Verifiability | Publishers check for Norway catch records dataset @PSNC took 0.25797414779663086s
Performance | Throughput check for Norway catch records dataset @PSNC took 11.581111431121826s
Amount of data | Check the number of entities for Norway catch records dataset @PSNC took 7.748603820800781e-05s
Verifiability | Contribs. check for Norway catch records dataset @PSNC took 0.18573904037475586s
Interlinking | sameAs chians check for Norway catch records dataset @PSNC took 0.19824528694152832s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.46773195266723633s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.4610726833343506s
Timeliness | dataset update frequency check for Norway catch records dataset @PSNC took 5.619623422622681s
Currency | Creation date check for Norway catch records dataset @PSNC took 0.49126696586608887s
Currency | Modification date check for Norway catch records dataset @PSNC took 0.24303746223449707s
Rep.Conc. | URIs length for Norway catch records dataset @PSNC took 158.4782464504242s
Interoperability | New vocabularies check for Norway catch records dataset @PSNC took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Norway catch records dataset @PSNC took 0.19166851043701172s
Accuracy | Check Functional Property for Norway catch records dataset @PSNC took 0.3284294605255127s
Accuracy | Check Inverse Functional Property for Norway catch records dataset @PSNC took 0.3279151916503906s
Accuracy | Check Empty annotation labels for Norway catch records dataset @PSNC took 37.14693260192871s
Accuracy | Check White space in annotation for Norway catch records dataset @PSNC took 2.6337740421295166s
Accuracy | Check Datatype consistency for Norway catch records dataset @PSNC took 2.64540696144104s
Consistency | Disjoint class check for Norway catch records dataset @PSNC took 0.210404634475708s
Consistency | Check Misplaced properties for Norway catch records dataset @PSNC took 83.47784948348999s
Consistency | Misplaced classes for Norway catch records dataset @PSNC took 8.288883686065674s
Consistency | Check Ontology hijacking for Norway catch records dataset @PSNC took 37.06731200218201s
Consistency | Check Invalid usage of undefined classes for Norway catch records dataset @PSNC took 1.376695156097412s
Consistency | Check Invalid usage of undefined properties for Norway catch records dataset @PSNC took 87.63825678825378s
Conciseness | Check Extensional conciseness for Norway catch records dataset @PSNC took 2.749130964279175s
Conciseness | Check Intensional conciseness for Norway catch records dataset @PSNC took 0.6054649353027344s
Security | Sign check for Norway catch records dataset @PSNC took 0.48401474952697754s
Availability | Check URIs Dereferenciability for Norway catch records dataset @PSNC took 5.416904449462891s
Completeness | Calculation of interlinking completeness for Norway catch records dataset @PSNC took 0.34941625595092773s
Reputation | Calculation of the PageRank for Norway catch records dataset @PSNC took 0.020457983016967773s
Interlinking | Calculation of Degree of Connection for Norway catch records dataset @PSNC took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Norway catch records dataset @PSNC took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Norway catch records dataset @PSNC took 3.790855407714844e-05s
Interoperability | Check the re-using of existing vocabs for Norway catch records dataset @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Norway catch records dataset @PSNC took 6.67572021484375e-06s
INFO | --- Analysis for Catch_Record_(2014-_2019) took 2271.592069387436s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 5.5789947509765625e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0006716251373291016s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.7039961814880371s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.020652294158935547s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.00011587142944335938s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 7.62939453125e-06s
INFO | --- Analysis for ce4r took 8.027644634246826s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.37146902084350586s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.0002779960632324219s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 1.7349867820739746s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 0.7607147693634033s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2768983840942383s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 1.7076692581176758s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 58.123833894729614s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17987656593322754s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2656998634338379s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.14026880264282227s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1544179916381836s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.27884745597839355s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4138977527618408s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15057373046875s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2984797954559326s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.30344152450561523s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16917729377746582s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2125406265258789s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.295241117477417s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 10.602368831634521s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 6.937980651855469e-05s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.24149513244628906s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1588900089263916s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 1.0045182704925537s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.12696623802185059s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3103170394897461s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.5942707061767578s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4340202808380127s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 2.080543041229248s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.13668465614318848s
Accuracy | Check Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.2934889793395996s
Accuracy | Check Inverse Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.291532039642334s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 0.5944011211395264s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.030858278274536133s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.028215408325195312s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.37143921852111816s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.2120921611785889s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 2.107539176940918s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 1.317323923110962s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.440211296081543s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.0300750732421875s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.19684195518493652s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15637683868408203s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 1810.0436902046204s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 0.5366764068603516s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.020933151245117188s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 3.5762786865234375e-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 7.62939453125e-06s
INFO | --- Analysis for ceo took 1945.6448602676392s
Availability | SPARQL endpoint availability check for Charging Stations took 3.933906555175781e-05s
Availability | VoID file availability check for Charging Stations took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for Charging Stations took 0.7180690765380859s
Reputation | Calculation of the PageRank for Charging Stations took 0.0204312801361084s
Interlinking | Calculation of Degree of Connection for Charging Stations took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Charging Stations took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for Charging Stations took 3.075599670410156e-05s
Believability | Calculation of trust value for Charging Stations took 6.9141387939453125e-06s
INFO | --- Analysis for charging-stations took 6.041823863983154s
Availability | SPARQL endpoint availability check for Chat Game corpus took 4.124641418457031e-05s
Availability | VoID file availability check for Chat Game corpus took 0.0006949901580810547s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 0.2781069278717041s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.020021915435791016s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 3.218650817871094e-05s
Believability | Calculation of trust value for Chat Game corpus took 6.198883056640625e-06s
INFO | --- Analysis for chat-game-corpus took 13.113943815231323s
Availability | SPARQL endpoint availability check for Chemical Entities of Biological Interest (ChEBI) took 4.2438507080078125e-05s
Availability | VoID file availability check for Chemical Entities of Biological Interest (ChEBI) took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for Chemical Entities of Biological Interest (ChEBI) took 0.2587907314300537s
Reputation | Calculation of the PageRank for Chemical Entities of Biological Interest (ChEBI) took 0.019969463348388672s
Interlinking | Calculation of Degree of Connection for Chemical Entities of Biological Interest (ChEBI) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Chemical Entities of Biological Interest (ChEBI) took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Chemical Entities of Biological Interest (ChEBI) took 3.0994415283203125e-05s
Believability | Calculation of trust value for Chemical Entities of Biological Interest (ChEBI) took 6.198883056640625e-06s
INFO | --- Analysis for chebi took 3.8586997985839844s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 4.076957702636719e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.0005195140838623047s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 0.27939939498901367s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.02052140235900879s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0009002685546875s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 6.175041198730469e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 6.9141387939453125e-06s
INFO | --- Analysis for chem2bio2rdf took 138.021977186203s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 0.7893078327178955s
Availability | VoID file availability check for ChEMBL RDF took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.27964162826538086s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.020099401473999023s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 5.030632019042969e-05s
Believability | Calculation of trust value for ChEMBL RDF took 7.3909759521484375e-06s
INFO | --- Analysis for chembl-rdf took 4.402373552322388s
Availability | SPARQL endpoint availability check for chemdb  dataset took 1.6581971645355225s
Availability | VoID file availability check for chemdb  dataset took 0.0002892017364501953s
Extra | Recovery of all triples for chemdb  dataset took 7.972052335739136s
Performance | Total latancy measurement for chemdb  dataset took 2.4900355339050293s
Amount of data | Number of triples check for chemdb  dataset took 0.5297763347625732s
Interoperability | New terms check for chemdb  dataset took 1.8575470447540283s
Versatility | Languages check for chemdb  dataset took 0.5281851291656494s
Interpretability | Number of blank nodes check for chemdb  dataset took 0.5163071155548096s
Interpretability | RDF structures check for chemdb  dataset took 0.5546262264251709s
Versatility | Serialization formats check for chemdb  dataset took 0.5566437244415283s
Availability | RDF dump link check for chemdb  dataset took 0.4970979690551758s
License | MR license check for chemdb  dataset took 0.5086727142333984s
License | HR license check for chemdb  dataset took 0.5057883262634277s
Amount of data | Number of property check for chemdb  dataset took 0.5158207416534424s
Understandability | Number of label check for chemdb  dataset took 0.5582594871520996s
Understandability | URI regex check for chemdb  dataset took 1.0031664371490479s
Understandability | Vocabs check for chemdb  dataset took 0.49239134788513184s
Verifiability | Authors check for chemdb  dataset took 0.524498462677002s
Verifiability | Publishers check for chemdb  dataset took 0.5210287570953369s
Performance | Throughput check for chemdb  dataset took 12.515381336212158s
Amount of data | Check the number of entities for chemdb  dataset took 3.314018249511719e-05s
Verifiability | Contribs. check for chemdb  dataset took 0.4898250102996826s
Interlinking | sameAs chians check for chemdb  dataset took 0.5396263599395752s
Interlinking | skos check for chemdb  dataset took 0.5042128562927246s
Interlinking | skos check for chemdb  dataset took 0.49450230598449707s
Timeliness | dataset update frequency check for chemdb  dataset took 0.5021634101867676s
Currency | Creation date check for chemdb  dataset took 1.036048412322998s
Currency | Modification date check for chemdb  dataset took 1.0499496459960938s
Rep.Conc. | URIs length for chemdb  dataset took 1.8611881732940674s
Interoperability | New vocabularies check for chemdb  dataset took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for chemdb  dataset took 0.5365724563598633s
Accuracy | Check Functional Property for chemdb  dataset took 0.5196073055267334s
Accuracy | Check Inverse Functional Property for chemdb  dataset took 0.4934248924255371s
Accuracy | Check Empty annotation labels for chemdb  dataset took 0.5329694747924805s
Accuracy | Check White space in annotation for chemdb  dataset took 0.00013875961303710938s
Accuracy | Check Datatype consistency for chemdb  dataset took 0.03220796585083008s
Consistency | Disjoint class check for chemdb  dataset took 0.504540205001831s
Consistency | Check Misplaced properties for chemdb  dataset took 1.0339179039001465s
Consistency | Misplaced classes for chemdb  dataset took 0.5906686782836914s
Consistency | Check Ontology hijacking for chemdb  dataset took 2.341630220413208s
Consistency | Check Invalid usage of undefined classes for chemdb  dataset took 1.3207015991210938s
Consistency | Check Invalid usage of undefined properties for chemdb  dataset took 1.8613967895507812s
Conciseness | Check Extensional conciseness for chemdb  dataset took 0.021458148956298828s
Conciseness | Check Intensional conciseness for chemdb  dataset took 0.5471205711364746s
Security | Sign check for chemdb  dataset took 0.5109996795654297s
Availability | Check URIs Dereferenciability for chemdb  dataset took 170.64595365524292s
Completeness | Calculation of interlinking completeness for chemdb  dataset took 0.34289026260375977s
Reputation | Calculation of the PageRank for chemdb  dataset took 0.020632505416870117s
Interlinking | Calculation of Degree of Connection for chemdb  dataset took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for chemdb  dataset took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for chemdb  dataset took 8.20159912109375e-05s
Interoperability | Check the re-using of existing vocabs for chemdb  dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for chemdb  dataset took 7.152557373046875e-06s
INFO | --- Analysis for chemdb-basicInfo took 257.3466942310333s
Availability | SPARQL endpoint availability check for chemdb estimated properties dataset took 0.5058064460754395s
Availability | VoID file availability check for chemdb estimated properties dataset took 0.00025844573974609375s
Extra | Recovery of all triples for chemdb estimated properties dataset took 7.241901636123657s
Performance | Total latancy measurement for chemdb estimated properties dataset took 2.5068163871765137s
Amount of data | Number of triples check for chemdb estimated properties dataset took 0.5005655288696289s
Interoperability | New terms check for chemdb estimated properties dataset took 1.7921507358551025s
Versatility | Languages check for chemdb estimated properties dataset took 0.5071806907653809s
Interpretability | Number of blank nodes check for chemdb estimated properties dataset took 0.49224352836608887s
Interpretability | RDF structures check for chemdb estimated properties dataset took 0.5100002288818359s
Versatility | Serialization formats check for chemdb estimated properties dataset took 0.5047416687011719s
Availability | RDF dump link check for chemdb estimated properties dataset took 0.5028517246246338s
License | MR license check for chemdb estimated properties dataset took 0.5005209445953369s
License | HR license check for chemdb estimated properties dataset took 0.4985635280609131s
Amount of data | Number of property check for chemdb estimated properties dataset took 0.5020637512207031s
Understandability | Number of label check for chemdb estimated properties dataset took 0.5066516399383545s
Understandability | URI regex check for chemdb estimated properties dataset took 0.9905056953430176s
Understandability | Vocabs check for chemdb estimated properties dataset took 0.4927670955657959s
Verifiability | Authors check for chemdb estimated properties dataset took 0.4971158504486084s
Verifiability | Publishers check for chemdb estimated properties dataset took 0.48900580406188965s
Performance | Throughput check for chemdb estimated properties dataset took 12.93811821937561s
Amount of data | Check the number of entities for chemdb estimated properties dataset took 7.033348083496094e-05s
Verifiability | Contribs. check for chemdb estimated properties dataset took 0.48997020721435547s
Interlinking | sameAs chians check for chemdb estimated properties dataset took 0.4958195686340332s
Interlinking | skos check for chemdb estimated properties dataset took 0.5084402561187744s
Interlinking | skos check for chemdb estimated properties dataset took 0.5120344161987305s
Timeliness | dataset update frequency check for chemdb estimated properties dataset took 0.5107827186584473s
Currency | Creation date check for chemdb estimated properties dataset took 0.9955344200134277s
Currency | Modification date check for chemdb estimated properties dataset took 1.000077247619629s
Rep.Conc. | URIs length for chemdb estimated properties dataset took 1.7937588691711426s
Interoperability | New vocabularies check for chemdb estimated properties dataset took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for chemdb estimated properties dataset took 0.4938070774078369s
Accuracy | Check Functional Property for chemdb estimated properties dataset took 0.4995417594909668s
Accuracy | Check Inverse Functional Property for chemdb estimated properties dataset took 0.5023040771484375s
Accuracy | Check Empty annotation labels for chemdb estimated properties dataset took 0.5130813121795654s
Accuracy | Check White space in annotation for chemdb estimated properties dataset took 0.00030159950256347656s
Accuracy | Check Datatype consistency for chemdb estimated properties dataset took 0.03600716590881348s
Consistency | Disjoint class check for chemdb estimated properties dataset took 0.4961717128753662s
Consistency | Check Misplaced properties for chemdb estimated properties dataset took 0.9912934303283691s
Consistency | Misplaced classes for chemdb estimated properties dataset took 0.5602364540100098s
Consistency | Check Ontology hijacking for chemdb estimated properties dataset took 2.0933420658111572s
Consistency | Check Invalid usage of undefined classes for chemdb estimated properties dataset took 1.3608663082122803s
Consistency | Check Invalid usage of undefined properties for chemdb estimated properties dataset took 1.8628106117248535s
Conciseness | Check Extensional conciseness for chemdb estimated properties dataset took 0.022182941436767578s
Conciseness | Check Intensional conciseness for chemdb estimated properties dataset took 0.4950418472290039s
Security | Sign check for chemdb estimated properties dataset took 0.493147611618042s
Availability | Check URIs Dereferenciability for chemdb estimated properties dataset took 167.4046733379364s
Completeness | Calculation of interlinking completeness for chemdb estimated properties dataset took 0.449521541595459s
Reputation | Calculation of the PageRank for chemdb estimated properties dataset took 0.020521163940429688s
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.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for chemdb estimated properties dataset took 5.245208740234375e-05s
Interoperability | Check the re-using of existing vocabs for chemdb estimated properties dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for chemdb estimated properties dataset took 1.049041748046875e-05s
INFO | --- Analysis for chemdb-estimatedProperties took 251.34302163124084s
Availability | SPARQL endpoint availability check for chemdb phase transition dataset took 0.4990098476409912s
Availability | VoID file availability check for chemdb phase transition dataset took 0.0003752708435058594s
Extra | Recovery of all triples for chemdb phase transition dataset took 7.587145566940308s
Performance | Total latancy measurement for chemdb phase transition dataset took 2.526862382888794s
Amount of data | Number of triples check for chemdb phase transition dataset took 0.522777795791626s
Interoperability | New terms check for chemdb phase transition dataset took 1.8525612354278564s
Versatility | Languages check for chemdb phase transition dataset took 1.5316307544708252s
Interpretability | Number of blank nodes check for chemdb phase transition dataset took 0.5207433700561523s
Interpretability | RDF structures check for chemdb phase transition dataset took 0.5276155471801758s
Versatility | Serialization formats check for chemdb phase transition dataset took 0.5250306129455566s
Availability | RDF dump link check for chemdb phase transition dataset took 0.5027999877929688s
License | MR license check for chemdb phase transition dataset took 0.49748945236206055s
License | HR license check for chemdb phase transition dataset took 0.49569272994995117s
Amount of data | Number of property check for chemdb phase transition dataset took 0.5439183712005615s
Understandability | Number of label check for chemdb phase transition dataset took 0.539254903793335s
Understandability | URI regex check for chemdb phase transition dataset took 1.0054435729980469s
Understandability | Vocabs check for chemdb phase transition dataset took 0.505671501159668s
Verifiability | Authors check for chemdb phase transition dataset took 0.50319504737854s
Verifiability | Publishers check for chemdb phase transition dataset took 0.5087337493896484s
Performance | Throughput check for chemdb phase transition dataset took 13.536200523376465s
Amount of data | Check the number of entities for chemdb phase transition dataset took 6.604194641113281e-05s
Verifiability | Contribs. check for chemdb phase transition dataset took 0.5013694763183594s
Interlinking | sameAs chians check for chemdb phase transition dataset took 0.5166091918945312s
Interlinking | skos check for chemdb phase transition dataset took 0.5052957534790039s
Interlinking | skos check for chemdb phase transition dataset took 0.5081148147583008s
Timeliness | dataset update frequency check for chemdb phase transition dataset took 0.4976158142089844s
Currency | Creation date check for chemdb phase transition dataset took 1.029374122619629s
Currency | Modification date check for chemdb phase transition dataset took 1.0208251476287842s
Rep.Conc. | URIs length for chemdb phase transition dataset took 1.8200557231903076s
Interoperability | New vocabularies check for chemdb phase transition dataset took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for chemdb phase transition dataset took 0.504479169845581s
Accuracy | Check Functional Property for chemdb phase transition dataset took 0.5210144519805908s
Accuracy | Check Inverse Functional Property for chemdb phase transition dataset took 0.5127286911010742s
Accuracy | Check Empty annotation labels for chemdb phase transition dataset took 0.5480527877807617s
Accuracy | Check White space in annotation for chemdb phase transition dataset took 0.0003077983856201172s
Accuracy | Check Datatype consistency for chemdb phase transition dataset took 0.0323941707611084s
Consistency | Disjoint class check for chemdb phase transition dataset took 0.5168063640594482s
Consistency | Check Misplaced properties for chemdb phase transition dataset took 1.0484790802001953s
Consistency | Misplaced classes for chemdb phase transition dataset took 0.5708370208740234s
Consistency | Check Ontology hijacking for chemdb phase transition dataset took 2.1335597038269043s
Consistency | Check Invalid usage of undefined classes for chemdb phase transition dataset took 1.3371198177337646s
Consistency | Check Invalid usage of undefined properties for chemdb phase transition dataset took 1.8489665985107422s
Conciseness | Check Extensional conciseness for chemdb phase transition dataset took 0.02206897735595703s
Conciseness | Check Intensional conciseness for chemdb phase transition dataset took 0.5192339420318604s
Security | Sign check for chemdb phase transition dataset took 0.5046513080596924s
Availability | Check URIs Dereferenciability for chemdb phase transition dataset took 167.21612858772278s
Completeness | Calculation of interlinking completeness for chemdb phase transition dataset took 0.8130497932434082s
Reputation | Calculation of the PageRank for chemdb phase transition dataset took 0.020643234252929688s
Interlinking | Calculation of Degree of Connection for chemdb phase transition dataset took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for chemdb phase transition dataset took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for chemdb phase transition dataset took 4.673004150390625e-05s
Interoperability | Check the re-using of existing vocabs for chemdb phase transition dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for chemdb phase transition dataset took 6.9141387939453125e-06s
INFO | --- Analysis for chemdb-phaseTransition took 256.3141043186188s
Availability | SPARQL endpoint availability check for chemdb thermochemistry dataset took 0.4906163215637207s
Availability | VoID file availability check for chemdb thermochemistry dataset took 0.00026726722717285156s
Extra | Recovery of all triples for chemdb thermochemistry dataset took 7.260178565979004s
Performance | Total latancy measurement for chemdb thermochemistry dataset took 2.524447202682495s
Amount of data | Number of triples check for chemdb thermochemistry dataset took 0.5112204551696777s
Interoperability | New terms check for chemdb thermochemistry dataset took 1.8804752826690674s
Versatility | Languages check for chemdb thermochemistry dataset took 0.4918692111968994s
Interpretability | Number of blank nodes check for chemdb thermochemistry dataset took 0.4969630241394043s
Interpretability | RDF structures check for chemdb thermochemistry dataset took 0.5070641040802002s
Versatility | Serialization formats check for chemdb thermochemistry dataset took 0.500469446182251s
Availability | RDF dump link check for chemdb thermochemistry dataset took 0.501866340637207s
License | MR license check for chemdb thermochemistry dataset took 0.5048208236694336s
License | HR license check for chemdb thermochemistry dataset took 0.5144298076629639s
Amount of data | Number of property check for chemdb thermochemistry dataset took 0.5031630992889404s
Understandability | Number of label check for chemdb thermochemistry dataset took 0.5149576663970947s
Understandability | URI regex check for chemdb thermochemistry dataset took 0.9981708526611328s
Understandability | Vocabs check for chemdb thermochemistry dataset took 0.498607873916626s
Verifiability | Authors check for chemdb thermochemistry dataset took 0.520641565322876s
Verifiability | Publishers check for chemdb thermochemistry dataset took 0.4965097904205322s
Performance | Throughput check for chemdb thermochemistry dataset took 12.997095584869385s
Amount of data | Check the number of entities for chemdb thermochemistry dataset took 7.414817810058594e-05s
Verifiability | Contribs. check for chemdb thermochemistry dataset took 0.4866013526916504s
Interlinking | sameAs chians check for chemdb thermochemistry dataset took 0.5048801898956299s
Interlinking | skos check for chemdb thermochemistry dataset took 0.5028398036956787s
Interlinking | skos check for chemdb thermochemistry dataset took 0.513676643371582s
Timeliness | dataset update frequency check for chemdb thermochemistry dataset took 0.5002965927124023s
Currency | Creation date check for chemdb thermochemistry dataset took 0.9999654293060303s
Currency | Modification date check for chemdb thermochemistry dataset took 1.0175457000732422s
Rep.Conc. | URIs length for chemdb thermochemistry dataset took 1.8438401222229004s
Interoperability | New vocabularies check for chemdb thermochemistry dataset took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for chemdb thermochemistry dataset took 0.530341625213623s
Accuracy | Check Functional Property for chemdb thermochemistry dataset took 0.4880087375640869s
Accuracy | Check Inverse Functional Property for chemdb thermochemistry dataset took 0.4868931770324707s
Accuracy | Check Empty annotation labels for chemdb thermochemistry dataset took 0.5060997009277344s
Accuracy | Check White space in annotation for chemdb thermochemistry dataset took 0.00030303001403808594s
Accuracy | Check Datatype consistency for chemdb thermochemistry dataset took 0.03430438041687012s
Consistency | Disjoint class check for chemdb thermochemistry dataset took 0.5041849613189697s
Consistency | Check Misplaced properties for chemdb thermochemistry dataset took 0.9978363513946533s
Consistency | Misplaced classes for chemdb thermochemistry dataset took 0.5515575408935547s
Consistency | Check Ontology hijacking for chemdb thermochemistry dataset took 2.0917787551879883s
Consistency | Check Invalid usage of undefined classes for chemdb thermochemistry dataset took 1.338346242904663s
Consistency | Check Invalid usage of undefined properties for chemdb thermochemistry dataset took 1.8618037700653076s
Conciseness | Check Extensional conciseness for chemdb thermochemistry dataset took 0.02228713035583496s
Conciseness | Check Intensional conciseness for chemdb thermochemistry dataset took 0.4975886344909668s
Security | Sign check for chemdb thermochemistry dataset took 0.48629117012023926s
Availability | Check URIs Dereferenciability for chemdb thermochemistry dataset took 163.1446988582611s
Completeness | Calculation of interlinking completeness for chemdb thermochemistry dataset took 0.7538318634033203s
Reputation | Calculation of the PageRank for chemdb thermochemistry dataset took 0.020234107971191406s
Interlinking | Calculation of Degree of Connection for chemdb thermochemistry dataset took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for chemdb thermochemistry dataset took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for chemdb thermochemistry dataset took 5.793571472167969e-05s
Interoperability | Check the re-using of existing vocabs for chemdb thermochemistry dataset took 1.9073486328125e-06s
Believability | Calculation of trust value for chemdb thermochemistry dataset took 6.67572021484375e-06s
INFO | --- Analysis for chemdb-thermochemistry took 248.8696002960205s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 4.291534423828125e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.0005974769592285156s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 0.7161955833435059s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.020142555236816406s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 2.6464462280273438e-05s
Believability | Calculation of trust value for ChemPedia RDF took 6.198883056640625e-06s
INFO | --- Analysis for chempedia-rdf took 8.729283094406128s
Availability | SPARQL endpoint availability check for Chiman Maru took 4.124641418457031e-05s
Availability | VoID file availability check for Chiman Maru took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for Chiman Maru took 0.26914310455322266s
Reputation | Calculation of the PageRank for Chiman Maru took 0.02048015594482422s
Interlinking | Calculation of Degree of Connection for Chiman Maru took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Chiman Maru took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Chiman Maru took 2.8371810913085938e-05s
Believability | Calculation of trust value for Chiman Maru took 6.9141387939453125e-06s
INFO | --- Analysis for ChimanMaru_Entrepreneur took 4.176067352294922s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 393.2041277885437s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.0007088184356689453s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 0.7127175331115723s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.02052927017211914s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 4.4345855712890625e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 7.152557373046875e-06s
INFO | --- Analysis for Chinese_Red_Classic_Song_Linked_Data_Dataset took 801.7349374294281s
Availability | SPARQL endpoint availability check for Chronicling America took 4.220008850097656e-05s
Availability | VoID file availability check for Chronicling America took 0.000553131103515625s
Completeness | Calculation of interlinking completeness for Chronicling America took 0.6935074329376221s
Reputation | Calculation of the PageRank for Chronicling America took 0.021279573440551758s
Interlinking | Calculation of Degree of Connection for Chronicling America took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Chronicling America took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 0.00010347366333007812s
Believability | Calculation of trust value for Chronicling America took 7.3909759521484375e-06s
INFO | --- Analysis for chronicling-america took 6.740917444229126s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.7530722618103027s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.0006153583526611328s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 123.67095637321472s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.6969537734985352s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 0.6249608993530273s
Interoperability | New terms check for Cultural Heritage Thesaurus took 2.0149378776550293s
Versatility | Languages check for Cultural Heritage Thesaurus took 1.2850229740142822s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 0.5239508152008057s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.3372995853424072s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.32391810417175293s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 10.501734495162964s
License | MR license check for Cultural Heritage Thesaurus took 0.3188655376434326s
License | HR license check for Cultural Heritage Thesaurus took 0.36411523818969727s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.3210594654083252s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.3702378273010254s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.7652933597564697s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.3074781894683838s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.3289802074432373s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.3363020420074463s
Performance | Throughput check for Cultural Heritage Thesaurus took 11.766579151153564s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 7.009506225585938e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.37016940116882324s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.33351993560791016s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.384052038192749s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.3711860179901123s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.362274169921875s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.6477687358856201s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.676964521408081s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 14.36963963508606s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.3706486225128174s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.31203770637512207s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.35837864875793457s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 3.5935211181640625s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.22318315505981445s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.4217402935028076s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 1.0748791694641113s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.3330066204071045s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 6.765133619308472s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 2.292012929916382s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.0001461505889892578s
Security | Sign check for Cultural Heritage Thesaurus took 0.3572084903717041s
Availability | Check URIs Dereferenciability for Cultural Heritage Thesaurus took 325.8583731651306s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 1.5251641273498535s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.2046973705291748s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0008962154388427734s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 0.0001227855682373047s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 8.344650268554688e-06s
INFO | --- Analysis for cht took 544.749801158905s
Availability | SPARQL endpoint availability check for ciard-ring took 9.393692016601562e-05s
Availability | VoID file availability check for ciard-ring took 0.0006616115570068359s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.7084269523620605s
Reputation | Calculation of the PageRank for ciard-ring took 0.06152606010437012s
Interlinking | Calculation of Degree of Connection for ciard-ring took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ciard-ring took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 4.553794860839844e-05s
Believability | Calculation of trust value for ciard-ring took 6.9141387939453125e-06s
INFO | --- Analysis for ciard-ring took 6.033626079559326s
Availability | SPARQL endpoint availability check for Cine Figure took 4.0531158447265625e-05s
Availability | VoID file availability check for Cine Figure took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for Cine Figure took 0.2984347343444824s
Reputation | Calculation of the PageRank for Cine Figure took 0.020264625549316406s
Interlinking | Calculation of Degree of Connection for Cine Figure took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cine Figure took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Cine Figure took 4.38690185546875e-05s
Believability | Calculation of trust value for Cine Figure took 7.3909759521484375e-06s
INFO | --- Analysis for Cine_Figure took 3.748809337615967s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 21.334912300109863s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.0007989406585693359s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.7456488609313965s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.021087169647216797s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 5.316734313964844e-05s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 7.62939453125e-06s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 177.4863543510437s
Availability | SPARQL endpoint availability check for CIPFA took 3.9577484130859375e-05s
Availability | VoID file availability check for CIPFA took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for CIPFA took 0.24878168106079102s
Reputation | Calculation of the PageRank for CIPFA took 0.020574331283569336s
Interlinking | Calculation of Degree of Connection for CIPFA took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CIPFA took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for CIPFA took 3.504753112792969e-05s
Believability | Calculation of trust value for CIPFA took 5.0067901611328125e-06s
INFO | --- Analysis for cipfa took 3.2191896438598633s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 60.05879807472229s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.7033581733703613s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.02072930335998535s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.0004017353057861328s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 7.867813110351562e-06s
INFO | --- Analysis for ckan took 263.9904234409332s
Availability | SPARQL endpoint availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.5985827445983887s
Availability | VoID file availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.7075791358947754s
Reputation | Calculation of the PageRank for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.02071523666381836s
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.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 3.814697265625e-05s
Believability | Calculation of trust value for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 7.3909759521484375e-06s
INFO | --- Analysis for CLaSSES took 4.932310104370117s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 4.124641418457031e-05s
Availability | VoID file availability check for Temples of the Classical World took 0.0005772113800048828s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 0.2734096050262451s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.02080059051513672s
Interlinking | Calculation of Degree of Connection for Temples of the Classical World took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Temples of the Classical World took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 3.0040740966796875e-05s
Believability | Calculation of trust value for Temples of the Classical World took 5.4836273193359375e-06s
INFO | --- Analysis for classical_temples took 4.571427345275879s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 1.8733558654785156s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.0006103515625s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 0.2685098648071289s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.020206451416015625s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 0.00014662742614746094s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 4.291534423828125e-06s
INFO | --- Analysis for clean-energy-data-reegle took 8.463689088821411s
Availability | SPARQL endpoint availability check for CLLD-afbo took 5.2928924560546875e-05s
Availability | VoID file availability check for CLLD-afbo took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.2929863929748535s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.02028942108154297s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 7.867813110351562e-05s
Believability | Calculation of trust value for CLLD-afbo took 6.67572021484375e-06s
INFO | --- Analysis for clld-afbo took 4.8931920528411865s
Availability | SPARQL endpoint availability check for CLLD-APICS took 3.9577484130859375e-05s
Availability | VoID file availability check for CLLD-APICS took 0.000835418701171875s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 0.7028443813323975s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.02028036117553711s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.000789642333984375s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 7.653236389160156e-05s
Believability | Calculation of trust value for CLLD-APICS took 6.4373016357421875e-06s
INFO | --- Analysis for clld-apics took 4.932257890701294s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 4.00543212890625e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.0007872581481933594s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.2887256145477295s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.0203855037689209s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 3.886222839355469e-05s
Believability | Calculation of trust value for CLLD-EWAVE took 6.4373016357421875e-06s
INFO | --- Analysis for clld-ewave took 3.6095213890075684s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 4.1484832763671875e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.0006265640258789062s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 0.27700018882751465s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.020171403884887695s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 9.703636169433594e-05s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 6.9141387939453125e-06s
INFO | --- Analysis for clld-glottolog took 3.5130884647369385s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 4.00543212890625e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.2694211006164551s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.02024245262145996s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 7.653236389160156e-05s
Believability | Calculation of trust value for CLLD-PHOIBLE took 6.9141387939453125e-06s
INFO | --- Analysis for clld-phoible took 3.447760581970215s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 4.9591064453125e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.0005619525909423828s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 0.25525665283203125s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.020320892333984375s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 7.557868957519531e-05s
Believability | Calculation of trust value for CLLD-SAILS took 6.67572021484375e-06s
INFO | --- Analysis for clld-sails took 3.5651462078094482s
Availability | SPARQL endpoint availability check for CLLD-WALS took 4.482269287109375e-05s
Availability | VoID file availability check for CLLD-WALS took 0.0005323886871337891s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.2484731674194336s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.020125627517700195s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 8.153915405273438e-05s
Believability | Calculation of trust value for CLLD-WALS took 6.9141387939453125e-06s
INFO | --- Analysis for clld-wals took 3.5816009044647217s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 3.886222839355469e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 0.25429630279541016s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.02029275894165039s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 7.581710815429688e-05s
Believability | Calculation of trust value for CLLD-WOLD took 6.4373016357421875e-06s
INFO | --- Analysis for clld-wold took 3.496187448501587s
Availability | SPARQL endpoint availability check for COD inventory took 3.886222839355469e-05s
Availability | VoID file availability check for COD inventory took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for COD inventory took 0.2691171169281006s
Reputation | Calculation of the PageRank for COD inventory took 0.020072221755981445s
Interlinking | Calculation of Degree of Connection for COD inventory took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for COD inventory took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for COD inventory took 2.86102294921875e-05s
Believability | Calculation of trust value for COD inventory took 7.152557373046875e-06s
INFO | --- Analysis for cod-inventory took 2.9326913356781006s
Availability | SPARQL endpoint availability check for Cooperation Databank took 0.13274121284484863s
Availability | VoID file availability check for Cooperation Databank took 0.0005428791046142578s
Completeness | Calculation of interlinking completeness for Cooperation Databank took 0.262117862701416s
Reputation | Calculation of the PageRank for Cooperation Databank took 0.020401954650878906s
Interlinking | Calculation of Degree of Connection for Cooperation Databank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cooperation Databank took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Cooperation Databank took 3.719329833984375e-05s
Believability | Calculation of trust value for Cooperation Databank took 7.62939453125e-06s
INFO | --- Analysis for CoDa took 2.54703950881958s
Availability | SPARQL endpoint availability check for CODE Endpoint took 3.9577484130859375e-05s
Availability | VoID file availability check for CODE Endpoint took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for CODE Endpoint took 0.2692854404449463s
Reputation | Calculation of the PageRank for CODE Endpoint took 0.020154237747192383s
Interlinking | Calculation of Degree of Connection for CODE Endpoint took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CODE Endpoint took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for CODE Endpoint took 2.8848648071289062e-05s
Believability | Calculation of trust value for CODE Endpoint took 6.9141387939453125e-06s
INFO | --- Analysis for code-endpoint took 2.886528253555298s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 0.7157697677612305s
Availability | VoID file availability check for OpenUpLabs COINS took 0.00048089027404785156s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.270601749420166s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.0202939510345459s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 2.7894973754882812e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 4.76837158203125e-06s
INFO | --- Analysis for coins-openuplabs took 3.1964495182037354s
Availability | SPARQL endpoint availability check for Catalogue of Life in China 2003 Edition took 3.4126312732696533s
Availability | VoID file availability check for Catalogue of Life in China 2003 Edition took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for Catalogue of Life in China 2003 Edition took 0.2597939968109131s
Reputation | Calculation of the PageRank for Catalogue of Life in China 2003 Edition took 0.02006077766418457s
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.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Catalogue of Life in China 2003 Edition took 7.987022399902344e-05s
Believability | Calculation of trust value for Catalogue of Life in China 2003 Edition took 6.67572021484375e-06s
INFO | --- Analysis for CoLChina_sp2000 took 7.081528663635254s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 0.04612421989440918s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 0.2645385265350342s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.020321369171142578s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 4.38690185546875e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 6.9141387939453125e-06s
INFO | --- Analysis for colinda took 2.5084493160247803s
Availability | SPARQL endpoint availability check for CN  2012 took 26.60906481742859s
Availability | VoID file availability check for CN  2012 took 0.0007874965667724609s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.7566909790039062s
Reputation | Calculation of the PageRank for CN  2012 took 0.02073073387145996s
Interlinking | Calculation of Degree of Connection for CN  2012 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CN  2012 took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 4.100799560546875e-05s
Believability | Calculation of trust value for CN  2012 took 5.0067901611328125e-06s
INFO | --- Analysis for combined-nomenclature-2012 took 124.67995500564575s
Availability | SPARQL endpoint availability check for Comments on Literature in Literature (CoLiL) took 3.7670135498046875e-05s
Availability | VoID file availability check for Comments on Literature in Literature (CoLiL) took 0.0003795623779296875s
Completeness | Calculation of interlinking completeness for Comments on Literature in Literature (CoLiL) took 0.6887507438659668s
Reputation | Calculation of the PageRank for Comments on Literature in Literature (CoLiL) took 0.020334959030151367s
Interlinking | Calculation of Degree of Connection for Comments on Literature in Literature (CoLiL) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Comments on Literature in Literature (CoLiL) took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Comments on Literature in Literature (CoLiL) took 3.0994415283203125e-05s
Believability | Calculation of trust value for Comments on Literature in Literature (CoLiL) took 7.152557373046875e-06s
INFO | --- Analysis for comments-on-literature-in-literature took 4.199984312057495s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of strawberry by period took 3.981590270996094e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of strawberry by period took 0.00023221969604492188s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of strawberry by period took 0.2793292999267578s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of strawberry by period took 0.020505428314208984s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of strawberry by period took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of strawberry by period took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of strawberry by period took 3.1948089599609375e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of strawberry by period took 7.3909759521484375e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-strawberry-by-period took 4.22003436088562s
Availability | SPARQL endpoint availability check for Price competitiveness of pear by region took 3.933906555175781e-05s
Availability | VoID file availability check for Price competitiveness of pear by region took 0.0002739429473876953s
Completeness | Calculation of interlinking completeness for Price competitiveness of pear by region took 0.26935315132141113s
Reputation | Calculation of the PageRank for Price competitiveness of pear by region took 0.02010655403137207s
Interlinking | Calculation of Degree of Connection for Price competitiveness of pear by region took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Price competitiveness of pear by region took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of pear by region took 2.8133392333984375e-05s
Believability | Calculation of trust value for Price competitiveness of pear by region took 6.4373016357421875e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period took 2.9672658443450928s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of watermelon by period took 4.00543212890625e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of watermelon by period took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of watermelon by period took 0.28235745429992676s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of watermelon by period took 0.020201444625854492s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of watermelon by period took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of watermelon by period took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of watermelon by period took 2.8848648071289062e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of watermelon by period took 6.9141387939453125e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period-2 took 2.989919900894165s
Availability | SPARQL endpoint availability check for Price competitiveness of grape by region took 5.412101745605469e-05s
Availability | VoID file availability check for Price competitiveness of grape by region took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for Price competitiveness of grape by region took 0.24722838401794434s
Reputation | Calculation of the PageRank for Price competitiveness of grape by region took 0.02072310447692871s
Interlinking | Calculation of Degree of Connection for Price competitiveness of grape by region took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Price competitiveness of grape by region took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of grape by region took 3.075599670410156e-05s
Believability | Calculation of trust value for Price competitiveness of grape by region took 7.3909759521484375e-06s
INFO | --- Analysis for comparison-of-price-competitiveness-of-grape-by-region took 2.8721821308135986s
Availability | SPARQL endpoint availability check for Computational Historical Semantics in LiLa took 0.4055509567260742s
Availability | VoID file availability check for Computational Historical Semantics in LiLa took 0.0006072521209716797s
Completeness | Calculation of interlinking completeness for Computational Historical Semantics in LiLa took 0.2702200412750244s
Reputation | Calculation of the PageRank for Computational Historical Semantics in LiLa took 0.020450353622436523s
Interlinking | Calculation of Degree of Connection for Computational Historical Semantics in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Computational Historical Semantics in LiLa took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Computational Historical Semantics in LiLa took 3.8623809814453125e-05s
Believability | Calculation of trust value for Computational Historical Semantics in LiLa took 6.9141387939453125e-06s
INFO | --- Analysis for CompHistSem took 3.7086081504821777s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 22.689096450805664s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.0006554126739501953s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 0.26103949546813965s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.02042388916015625s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 3.62396240234375e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 7.62939453125e-06s
INFO | --- Analysis for comsode-d3-2 took 119.15984725952148s
Availability | SPARQL endpoint availability check for ConceptNet took 4.9114227294921875e-05s
Availability | VoID file availability check for ConceptNet took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for ConceptNet took 0.2798495292663574s
Reputation | Calculation of the PageRank for ConceptNet took 0.020277023315429688s
Interlinking | Calculation of Degree of Connection for ConceptNet took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ConceptNet took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for ConceptNet took 2.9087066650390625e-05s
Believability | Calculation of trust value for ConceptNet took 6.9141387939453125e-06s
INFO | --- Analysis for conceptnet took 3.346325397491455s
Availability | SPARQL endpoint availability check for 2011 US Congress People took 4.220008850097656e-05s
Availability | VoID file availability check for 2011 US Congress People took 0.0006661415100097656s
Completeness | Calculation of interlinking completeness for 2011 US Congress People took 0.2805190086364746s
Reputation | Calculation of the PageRank for 2011 US Congress People took 0.020473003387451172s
Interlinking | Calculation of Degree of Connection for 2011 US Congress People took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for 2011 US Congress People took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for 2011 US Congress People took 8.606910705566406e-05s
Believability | Calculation of trust value for 2011 US Congress People took 5.0067901611328125e-06s
INFO | --- Analysis for congresspeople took 3.10646653175354s
Availability | SPARQL endpoint availability check for MIMO took 0.3278777599334717s
Availability | VoID file availability check for MIMO took 0.0006768703460693359s
Completeness | Calculation of interlinking completeness for MIMO took 0.26583218574523926s
Reputation | Calculation of the PageRank for MIMO took 0.020311594009399414s
Interlinking | Calculation of Degree of Connection for MIMO took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for MIMO took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for MIMO took 1.1205673217773438e-05s
Believability | Calculation of trust value for MIMO took 7.3909759521484375e-06s
INFO | --- Analysis for CONNECTED took 3.887397289276123s
Availability | SPARQL endpoint availability check for LODsyndesis Dataset took 5.53131103515625e-05s
Availability | VoID file availability check for LODsyndesis Dataset took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for LODsyndesis Dataset took 0.25986456871032715s
Reputation | Calculation of the PageRank for LODsyndesis Dataset took 0.02051711082458496s
Interlinking | Calculation of Degree of Connection for LODsyndesis Dataset took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for LODsyndesis Dataset took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for LODsyndesis Dataset took 2.9325485229492188e-05s
Believability | Calculation of trust value for LODsyndesis Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for connectivity-of-lod-datasets took 2.8844375610351562s
Availability | SPARQL endpoint availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 7.534027099609375e-05s
Availability | VoID file availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.29270458221435547s
Reputation | Calculation of the PageRank for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.020279884338378906s
Interlinking | Calculation of Degree of Connection for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 2.8371810913085938e-05s
Believability | Calculation of trust value for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 8.58306884765625e-06s
INFO | --- Analysis for copac-library-catalogue took 2.9479048252105713s
Availability | SPARQL endpoint availability check for Copyright Free Music took 5.412101745605469e-05s
Availability | VoID file availability check for Copyright Free Music took 0.0006506443023681641s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 0.27550506591796875s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.02021503448486328s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 2.8133392333984375e-05s
Believability | Calculation of trust value for Copyright Free Music took 6.67572021484375e-06s
INFO | --- Analysis for Copyright_Free_Music took 3.423311710357666s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 4.00543212890625e-05s
Availability | VoID file availability check for CopyrightTermBank took 0.0006568431854248047s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 0.25397491455078125s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.0202481746673584s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 6.794929504394531e-05s
Believability | Calculation of trust value for CopyrightTermBank took 7.152557373046875e-06s
INFO | --- Analysis for copyrighttermbank took 34.89412569999695s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 1.9527366161346436s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.0003147125244140625s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.2471916675567627s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.020202159881591797s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 3.743171691894531e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 6.67572021484375e-06s
INFO | --- Analysis for core took 7.543036460876465s
Availability | SPARQL endpoint availability check for Corine linked dataset @PSNC took 0.5202078819274902s
Availability | VoID file availability check for Corine linked dataset @PSNC took 0.0002605915069580078s
Extra | Recovery of all triples for Corine linked dataset @PSNC took 122.02245283126831s
Performance | Total latancy measurement for Corine linked dataset @PSNC took 1.044154167175293s
Amount of data | Number of triples check for Corine linked dataset @PSNC took 8.799623250961304s
Interoperability | New terms check for Corine linked dataset @PSNC took 15.365938186645508s
Versatility | Languages check for Corine linked dataset @PSNC took 300.20337104797363s
Interpretability | Number of blank nodes check for Corine linked dataset @PSNC took 2.8451499938964844s
Interpretability | RDF structures check for Corine linked dataset @PSNC took 0.29080677032470703s
Versatility | Serialization formats check for Corine linked dataset @PSNC took 13.237338542938232s
Availability | RDF dump link check for Corine linked dataset @PSNC took 0.33657336235046387s
License | MR license check for Corine linked dataset @PSNC took 0.7801554203033447s
License | HR license check for Corine linked dataset @PSNC took 300.1699936389923s
Amount of data | Number of property check for Corine linked dataset @PSNC took 0.28265833854675293s
Understandability | Number of label check for Corine linked dataset @PSNC took 2.772914171218872s
Understandability | URI regex check for Corine linked dataset @PSNC took 0.8044614791870117s
Understandability | Vocabs check for Corine linked dataset @PSNC took 0.464569091796875s
Verifiability | Authors check for Corine linked dataset @PSNC took 0.2017688751220703s
Verifiability | Publishers check for Corine linked dataset @PSNC took 0.2613544464111328s
Performance | Throughput check for Corine linked dataset @PSNC took 11.228656530380249s
Amount of data | Check the number of entities for Corine linked dataset @PSNC took 7.128715515136719e-05s
Verifiability | Contribs. check for Corine linked dataset @PSNC took 0.18207263946533203s
Interlinking | sameAs chians check for Corine linked dataset @PSNC took 0.22294878959655762s
Interlinking | skos check for Corine linked dataset @PSNC took 0.4463672637939453s
Interlinking | skos check for Corine linked dataset @PSNC took 0.43766355514526367s
Timeliness | dataset update frequency check for Corine linked dataset @PSNC took 5.354434490203857s
Currency | Creation date check for Corine linked dataset @PSNC took 0.5408313274383545s
Currency | Modification date check for Corine linked dataset @PSNC took 0.22185921669006348s
Rep.Conc. | URIs length for Corine linked dataset @PSNC took 160.92857384681702s
Interoperability | New vocabularies check for Corine linked dataset @PSNC took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Corine linked dataset @PSNC took 0.20114612579345703s
Accuracy | Check Functional Property for Corine linked dataset @PSNC took 0.34522533416748047s
Accuracy | Check Inverse Functional Property for Corine linked dataset @PSNC took 0.3364830017089844s
Accuracy | Check Empty annotation labels for Corine linked dataset @PSNC took 40.991562843322754s
Accuracy | Check White space in annotation for Corine linked dataset @PSNC took 2.6770265102386475s
Accuracy | Check Datatype consistency for Corine linked dataset @PSNC took 2.6173181533813477s
Consistency | Disjoint class check for Corine linked dataset @PSNC took 0.19738531112670898s
Consistency | Check Misplaced properties for Corine linked dataset @PSNC took 83.66150569915771s
Consistency | Misplaced classes for Corine linked dataset @PSNC took 8.359046459197998s
Consistency | Check Ontology hijacking for Corine linked dataset @PSNC took 39.442301511764526s
Consistency | Check Invalid usage of undefined classes for Corine linked dataset @PSNC took 1.612363576889038s
Consistency | Check Invalid usage of undefined properties for Corine linked dataset @PSNC took 96.00831532478333s
Conciseness | Check Extensional conciseness for Corine linked dataset @PSNC took 2.7742838859558105s
Conciseness | Check Intensional conciseness for Corine linked dataset @PSNC took 0.5591208934783936s
Security | Sign check for Corine linked dataset @PSNC took 1.0132782459259033s
Availability | Check URIs Dereferenciability for Corine linked dataset @PSNC took 5.283813953399658s
Completeness | Calculation of interlinking completeness for Corine linked dataset @PSNC took 1.4728341102600098s
Reputation | Calculation of the PageRank for Corine linked dataset @PSNC took 0.021019458770751953s
Interlinking | Calculation of Degree of Connection for Corine linked dataset @PSNC took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Corine linked dataset @PSNC took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Corine linked dataset @PSNC took 3.7670135498046875e-05s
Interoperability | Check the re-using of existing vocabs for Corine linked dataset @PSNC took 2.1457672119140625e-06s
Believability | Calculation of trust value for Corine linked dataset @PSNC took 8.344650268554688e-06s
INFO | --- Analysis for Corine_linked_dataset took 2302.7125852108s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 8.058547973632812e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.705214262008667s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.02061748504638672s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Hongcheon) Environmental Status took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Hongcheon) Environmental Status took 3.266334533691406e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Hongcheon) Environmental Status took 7.3909759521484375e-06s
INFO | --- Analysis for corn took 4.980428695678711s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 5.078315734863281e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Goesan) Environmental Status took 0.7036683559417725s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Goesan) Environmental Status took 0.020537137985229492s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Goesan) Environmental Status took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Goesan) Environmental Status took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Goesan) Environmental Status took 3.0994415283203125e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Goesan) Environmental Status took 8.344650268554688e-06s
INFO | --- Analysis for corn-s-famous-mountainous-district-goesan-environmental-status took 4.401405334472656s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 3.933906555175781e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.25755834579467773s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0207364559173584s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Jeongseon) Environmental Status took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0009038448333740234s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Jeongseon) Environmental Status took 3.337860107421875e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Jeongseon) Environmental Status took 7.62939453125e-06s
INFO | --- Analysis for corn-s-famous-mountainous-district-jeongseon-environmental-status took 3.9587018489837646s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 4.124641418457031e-05s
Availability | VoID file availability check for Cornetto1.2 took 0.0005495548248291016s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.2811458110809326s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.02009439468383789s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 5.745887756347656e-05s
Believability | Calculation of trust value for Cornetto1.2 took 7.62939453125e-06s
INFO | --- Analysis for cornetto took 14.851489782333374s
Availability | SPARQL endpoint availability check for Corporate Body Named Authority List  took 0.1657261848449707s
Availability | VoID file availability check for Corporate Body Named Authority List  took 0.0005381107330322266s
Extra | Recovery of all triples for Corporate Body Named Authority List  took 300.1041522026062s
Performance | Total latancy measurement for Corporate Body Named Authority List  took 0.6377508640289307s
Amount of data | Number of triples check for Corporate Body Named Authority List  took 170.8506908416748s
Interoperability | New terms check for Corporate Body Named Authority List  took 113.31554770469666s
Versatility | Languages check for Corporate Body Named Authority List  took 300.0726878643036s
Interpretability | Number of blank nodes check for Corporate Body Named Authority List  took 12.3607919216156s
Security | Check HTTPS for Corporate Body Named Authority List  took 0.34763646125793457s
Interpretability | RDF structures check for Corporate Body Named Authority List  took 0.7404332160949707s
Versatility | Serialization formats check for Corporate Body Named Authority List  took 19.43988037109375s
Availability | RDF dump link check for Corporate Body Named Authority List  took 0.2617912292480469s
License | MR license check for Corporate Body Named Authority List  took 0.3061070442199707s
License | HR license check for Corporate Body Named Authority List  took 300.045033454895s
Amount of data | Number of property check for Corporate Body Named Authority List  took 0.22453665733337402s
Understandability | Number of label check for Corporate Body Named Authority List  took 8.912477016448975s
Understandability | URI regex check for Corporate Body Named Authority List  took 0.3955974578857422s
Understandability | Vocabs check for Corporate Body Named Authority List  took 0.1572420597076416s
Verifiability | Authors check for Corporate Body Named Authority List  took 0.20766019821166992s
Verifiability | Publishers check for Corporate Body Named Authority List  took 0.23729729652404785s
Performance | Throughput check for Corporate Body Named Authority List  took 10.60254430770874s
Amount of data | Check the number of entities for Corporate Body Named Authority List  took 7.05718994140625e-05s
Verifiability | Contribs. check for Corporate Body Named Authority List  took 0.18086719512939453s
Interlinking | sameAs chians check for Corporate Body Named Authority List  took 12.148613214492798s
Interlinking | skos check for Corporate Body Named Authority List  took 0.4589416980743408s
Interlinking | skos check for Corporate Body Named Authority List  took 0.47930097579956055s
Timeliness | dataset update frequency check for Corporate Body Named Authority List  took 0.3699777126312256s
Currency | Creation date check for Corporate Body Named Authority List  took 0.8881018161773682s
Currency | Modification date check for Corporate Body Named Authority List  took 0.32451462745666504s
Rep.Conc. | URIs length for Corporate Body Named Authority List  took 623.5743410587311s
Interoperability | New vocabularies check for Corporate Body Named Authority List  took 6.9141387939453125e-06s
Consistency | Deprecated classes/propertiers check for Corporate Body Named Authority List  took 0.16423368453979492s
Accuracy | Check Functional Property for Corporate Body Named Authority List  took 0.18585562705993652s
Accuracy | Check Inverse Functional Property for Corporate Body Named Authority List  took 0.130720853805542s
Accuracy | Check Empty annotation labels for Corporate Body Named Authority List  took 122.84818887710571s
Accuracy | Check White space in annotation for Corporate Body Named Authority List  took 3.1456997394561768s
Consistency | Disjoint class check for Corporate Body Named Authority List  took 0.20167994499206543s
Consistency | Check Misplaced properties for Corporate Body Named Authority List  took 300.86634254455566s
Consistency | Misplaced classes for Corporate Body Named Authority List  took 0.4664647579193115s
Consistency | Check Ontology hijacking for Corporate Body Named Authority List  took 130.95040345191956s
Consistency | Check Invalid usage of undefined properties for Corporate Body Named Authority List  took 301.51443886756897s
Conciseness | Check Extensional conciseness for Corporate Body Named Authority List  took 0.00019788742065429688s
Conciseness | Check Intensional conciseness for Corporate Body Named Authority List  took 0.6978580951690674s
Security | Sign check for Corporate Body Named Authority List  took 0.19866704940795898s
Completeness | Calculation of interlinking completeness for Corporate Body Named Authority List  took 1.6131198406219482s
Reputation | Calculation of the PageRank for Corporate Body Named Authority List  took 0.02551722526550293s
Interlinking | Calculation of Degree of Connection for Corporate Body Named Authority List  took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for Corporate Body Named Authority List  took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Corporate Body Named Authority List  took 5.984306335449219e-05s
Interoperability | Check the re-using of existing vocabs for Corporate Body Named Authority List  took 1.6689300537109375e-06s
Believability | Calculation of trust value for Corporate Body Named Authority List  took 7.152557373046875e-06s
INFO | --- Analysis for corporate-body took 16275.900395154953s
Availability | SPARQL endpoint availability check for Corpus Fibonacci in LiLa took 0.5831983089447021s
Availability | VoID file availability check for Corpus Fibonacci in LiLa took 0.0006663799285888672s
Completeness | Calculation of interlinking completeness for Corpus Fibonacci in LiLa took 0.2784914970397949s
Reputation | Calculation of the PageRank for Corpus Fibonacci in LiLa took 0.020339250564575195s
Interlinking | Calculation of Degree of Connection for Corpus Fibonacci in LiLa took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Corpus Fibonacci in LiLa took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Corpus Fibonacci in LiLa took 3.7670135498046875e-05s
Believability | Calculation of trust value for Corpus Fibonacci in LiLa took 7.152557373046875e-06s
INFO | --- Analysis for CorpusFibonacci took 5.330454587936401s
Availability | SPARQL endpoint availability check for CORS Check - HTTP Header Logs for Linked Open Data took 0.000118255615234375s
Availability | VoID file availability check for CORS Check - HTTP Header Logs for Linked Open Data took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for CORS Check - HTTP Header Logs for Linked Open Data took 0.25832200050354004s
Reputation | Calculation of the PageRank for CORS Check - HTTP Header Logs for Linked Open Data took 0.02009439468383789s
Interlinking | Calculation of Degree of Connection for CORS Check - HTTP Header Logs for Linked Open Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CORS Check - HTTP Header Logs for Linked Open Data took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for CORS Check - HTTP Header Logs for Linked Open Data took 2.9087066650390625e-05s
Believability | Calculation of trust value for CORS Check - HTTP Header Logs for Linked Open Data took 1.1682510375976562e-05s
INFO | --- Analysis for corscheck took 4.659626722335815s
Availability | SPARQL endpoint availability check for Country Name Authority List took 0.127061128616333s
Availability | VoID file availability check for Country Name Authority List took 0.0006966590881347656s
Extra | Recovery of all triples for Country Name Authority List took 300.0375328063965s
Performance | Total latancy measurement for Country Name Authority List took 0.7421376705169678s
Amount of data | Number of triples check for Country Name Authority List took 171.4625449180603s
Interoperability | New terms check for Country Name Authority List took 139.27214360237122s
Versatility | Languages check for Country Name Authority List took 300.1513423919678s
Interpretability | Number of blank nodes check for Country Name Authority List took 8.564911365509033s
Security | Check HTTPS for Country Name Authority List took 0.3245384693145752s
Interpretability | RDF structures check for Country Name Authority List took 0.2542135715484619s
Versatility | Serialization formats check for Country Name Authority List took 17.043509483337402s
Availability | RDF dump link check for Country Name Authority List took 0.21892213821411133s
License | MR license check for Country Name Authority List took 0.6097774505615234s
License | HR license check for Country Name Authority List took 300.1049454212189s
Amount of data | Number of property check for Country Name Authority List took 0.1652679443359375s
Understandability | Number of label check for Country Name Authority List took 10.089125633239746s
Understandability | URI regex check for Country Name Authority List took 0.4286201000213623s
Understandability | Vocabs check for Country Name Authority List took 0.11148190498352051s
Verifiability | Authors check for Country Name Authority List took 0.12071490287780762s
Verifiability | Publishers check for Country Name Authority List took 0.23986196517944336s
Performance | Throughput check for Country Name Authority List took 10.61680555343628s
Amount of data | Check the number of entities for Country Name Authority List took 7.104873657226562e-05s
Verifiability | Contribs. check for Country Name Authority List took 0.1403636932373047s
Interlinking | sameAs chians check for Country Name Authority List took 11.635719060897827s
Interlinking | skos check for Country Name Authority List took 0.33951449394226074s
Interlinking | skos check for Country Name Authority List took 0.32304835319519043s
Timeliness | dataset update frequency check for Country Name Authority List took 0.221754789352417s
Currency | Creation date check for Country Name Authority List took 0.762775182723999s
Currency | Modification date check for Country Name Authority List took 0.35815858840942383s
Rep.Conc. | URIs length for Country Name Authority List took 600.2100286483765s
Interoperability | New vocabularies check for Country Name Authority List took 5.0067901611328125e-06s
Consistency | Deprecated classes/propertiers check for Country Name Authority List took 0.22136449813842773s
Accuracy | Check Functional Property for Country Name Authority List took 0.18669843673706055s
Accuracy | Check Inverse Functional Property for Country Name Authority List took 0.11405420303344727s
Accuracy | Check Empty annotation labels for Country Name Authority List took 156.36398649215698s
Accuracy | Check White space in annotation for Country Name Authority List took 3.13374662399292s
Consistency | Disjoint class check for Country Name Authority List took 0.20840001106262207s
Consistency | Check Misplaced properties for Country Name Authority List took 300.95921087265015s
Consistency | Misplaced classes for Country Name Authority List took 0.6511437892913818s
Consistency | Check Ontology hijacking for Country Name Authority List took 204.13237524032593s
Consistency | Check Invalid usage of undefined properties for Country Name Authority List took 301.45432901382446s
Conciseness | Check Extensional conciseness for Country Name Authority List took 0.00019478797912597656s
Conciseness | Check Intensional conciseness for Country Name Authority List took 0.6690263748168945s
Security | Sign check for Country Name Authority List took 0.22840166091918945s
Completeness | Calculation of interlinking completeness for Country Name Authority List took 1.5579781532287598s
Reputation | Calculation of the PageRank for Country Name Authority List took 0.02104783058166504s
Interlinking | Calculation of Degree of Connection for Country Name Authority List took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Country Name Authority List took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Country Name Authority List took 5.364418029785156e-05s
Interoperability | Check the re-using of existing vocabs for Country Name Authority List took 1.1920928955078125e-06s
Believability | Calculation of trust value for Country Name Authority List took 7.152557373046875e-06s
INFO | --- Analysis for country-authority-list took 16555.3539686203s
Availability | SPARQL endpoint availability check for Courts thesaurus took 0.18598508834838867s
Availability | VoID file availability check for Courts thesaurus took 0.0004298686981201172s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 0.2805502414703369s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.02031564712524414s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 6.389617919921875e-05s
Believability | Calculation of trust value for Courts thesaurus took 6.4373016357421875e-06s
INFO | --- Analysis for courts-thesaurus took 4.858325004577637s
Availability | SPARQL endpoint availability check for Covid-on-the-Web Dataset took 20.50129771232605s
Availability | VoID file availability check for Covid-on-the-Web Dataset took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for Covid-on-the-Web Dataset took 0.27002525329589844s
Reputation | Calculation of the PageRank for Covid-on-the-Web Dataset took 0.020146608352661133s
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.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Covid-on-the-Web Dataset took 8.034706115722656e-05s
Believability | Calculation of trust value for Covid-on-the-Web Dataset took 7.152557373046875e-06s
INFO | --- Analysis for Covid-on-the-Web took 71.93319153785706s
Availability | SPARQL endpoint availability check for CPA 2008 took 25.851590871810913s
Availability | VoID file availability check for CPA 2008 took 0.0006203651428222656s
Completeness | Calculation of interlinking completeness for CPA 2008 took 0.26574182510375977s
Reputation | Calculation of the PageRank for CPA 2008 took 0.02082037925720215s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 4.649162292480469e-05s
Believability | Calculation of trust value for CPA 2008 took 5.9604644775390625e-06s
INFO | --- Analysis for cpa-2008 took 123.4314112663269s
Availability | SPARQL endpoint availability check for Cooperative Patent Classification took 0.5126450061798096s
Availability | VoID file availability check for Cooperative Patent Classification took 0.0006191730499267578s
Extra | Recovery of all triples for Cooperative Patent Classification took 60.51298260688782s
Performance | Total latancy measurement for Cooperative Patent Classification took 1.3055498600006104s
Amount of data | Number of triples check for Cooperative Patent Classification took 90.19348621368408s
Versatility | Languages check for Cooperative Patent Classification took 120.30309247970581s
Interpretability | Number of blank nodes check for Cooperative Patent Classification took 90.77246427536011s
Interpretability | RDF structures check for Cooperative Patent Classification took 2.176165819168091s
Versatility | Serialization formats check for Cooperative Patent Classification took 1.6668338775634766s
Availability | RDF dump link check for Cooperative Patent Classification took 1.5871119499206543s
License | MR license check for Cooperative Patent Classification took 1.972487449645996s
License | HR license check for Cooperative Patent Classification took 92.90838527679443s
Amount of data | Number of property check for Cooperative Patent Classification took 11.826177835464478s
Understandability | Number of label check for Cooperative Patent Classification took 93.73139190673828s
Understandability | URI regex check for Cooperative Patent Classification took 0.4615180492401123s
Understandability | Vocabs check for Cooperative Patent Classification took 0.18241047859191895s
Verifiability | Authors check for Cooperative Patent Classification took 0.23427033424377441s
Verifiability | Publishers check for Cooperative Patent Classification took 0.2548859119415283s
Performance | Throughput check for Cooperative Patent Classification took 10.8868567943573s
Amount of data | Check the number of entities for Cooperative Patent Classification took 7.390975952148438e-05s
Verifiability | Contribs. check for Cooperative Patent Classification took 0.210829496383667s
Interlinking | sameAs chians check for Cooperative Patent Classification took 0.18442654609680176s
Interlinking | skos check for Cooperative Patent Classification took 0.19306039810180664s
Interlinking | skos check for Cooperative Patent Classification took 0.24427580833435059s
Timeliness | dataset update frequency check for Cooperative Patent Classification took 0.1833176612854004s
Currency | Creation date check for Cooperative Patent Classification took 0.46941637992858887s
Currency | Modification date check for Cooperative Patent Classification took 0.5001275539398193s
Rep.Conc. | URIs length for Cooperative Patent Classification took 197.61712408065796s
Interoperability | New vocabularies check for Cooperative Patent Classification took 4.5299530029296875e-06s
Consistency | Deprecated classes/propertiers check for Cooperative Patent Classification took 0.2364039421081543s
Accuracy | Check Empty annotation labels for Cooperative Patent Classification took 88.61698770523071s
Accuracy | Check White space in annotation for Cooperative Patent Classification took 2.93611741065979s
Accuracy | Check Datatype consistency for Cooperative Patent Classification took 10.411323308944702s
Consistency | Disjoint class check for Cooperative Patent Classification took 0.22023558616638184s
Consistency | Check Misplaced properties for Cooperative Patent Classification took 120.49478220939636s
Consistency | Check Ontology hijacking for Cooperative Patent Classification took 138.8397753238678s
Consistency | Check Invalid usage of undefined properties for Cooperative Patent Classification took 122.18928623199463s
Conciseness | Check Extensional conciseness for Cooperative Patent Classification took 2.890488386154175s
Conciseness | Check Intensional conciseness for Cooperative Patent Classification took 27.186007499694824s
Security | Sign check for Cooperative Patent Classification took 0.2264385223388672s
Availability | Check URIs Dereferenciability for Cooperative Patent Classification took 1.9636116027832031s
Completeness | Calculation of interlinking completeness for Cooperative Patent Classification took 1.1174697875976562s
Reputation | Calculation of the PageRank for Cooperative Patent Classification took 0.0920712947845459s
Interlinking | Calculation of Degree of Connection for Cooperative Patent Classification took 2.4080276489257812e-05s
Interlinking | Calculation of Centrality for Cooperative Patent Classification took 0.0012564659118652344s
Interlinking | Calculation of Clustering coefficient for Cooperative Patent Classification took 4.482269287109375e-05s
Interoperability | Check the re-using of existing vocabs for Cooperative Patent Classification took 1.6689300537109375e-06s
Believability | Calculation of trust value for Cooperative Patent Classification took 7.3909759521484375e-06s
INFO | --- Analysis for CPC took 1648.058541059494s
Availability | SPARQL endpoint availability check for CPC 2008 took 23.927854537963867s
Availability | VoID file availability check for CPC 2008 took 0.0008482933044433594s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.9143359661102295s
Reputation | Calculation of the PageRank for CPC 2008 took 0.020404815673828125s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 3.4332275390625e-05s
Believability | Calculation of trust value for CPC 2008 took 4.76837158203125e-06s
INFO | --- Analysis for cpc-2008 took 122.68755650520325s
Availability | SPARQL endpoint availability check for CPV  2003 took 20.63029146194458s
Availability | VoID file availability check for CPV  2003 took 0.00096893310546875s
Completeness | Calculation of interlinking completeness for CPV  2003 took 0.8039398193359375s
Reputation | Calculation of the PageRank for CPV  2003 took 0.02031540870666504s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 3.409385681152344e-05s
Believability | Calculation of trust value for CPV  2003 took 5.4836273193359375e-06s
INFO | --- Analysis for cpv-2003 took 114.29646420478821s
Availability | SPARQL endpoint availability check for CPV 2008 took 23.227121353149414s
Availability | VoID file availability check for CPV 2008 took 0.0008070468902587891s
Completeness | Calculation of interlinking completeness for CPV 2008 took 0.25128626823425293s
Reputation | Calculation of the PageRank for CPV 2008 took 0.020589113235473633s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 4.839897155761719e-05s
Believability | Calculation of trust value for CPV 2008 took 4.0531158447265625e-06s
INFO | --- Analysis for cpv-2008 took 121.42215871810913s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 261.2367670536041s
Availability | VoID file availability check for crowdsourcing-fb took 0.00034332275390625s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 0.7299809455871582s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.02065110206604004s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 3.981590270996094e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 6.67572021484375e-06s
INFO | --- Analysis for crowdsourcing-fb took 537.1068379878998s
Availability | SPARQL endpoint availability check for CRTM took 6.127357482910156e-05s
Availability | VoID file availability check for CRTM took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for CRTM took 0.2658073902130127s
Reputation | Calculation of the PageRank for CRTM took 0.021579980850219727s
Interlinking | Calculation of Degree of Connection for CRTM took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CRTM took 0.0010268688201904297s
Interlinking | Calculation of Clustering coefficient for CRTM took 3.7670135498046875e-05s
Believability | Calculation of trust value for CRTM took 6.67572021484375e-06s
INFO | --- Analysis for crtm took 4.894036293029785s
Availability | SPARQL endpoint availability check for Crystal Eye: Aggregated Crystallographic Data took 4.0531158447265625e-05s
Availability | VoID file availability check for Crystal Eye: Aggregated Crystallographic Data took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for Crystal Eye: Aggregated Crystallographic Data took 0.2613670825958252s
Reputation | Calculation of the PageRank for Crystal Eye: Aggregated Crystallographic Data took 0.02017354965209961s
Interlinking | Calculation of Degree of Connection for Crystal Eye: Aggregated Crystallographic Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Crystal Eye: Aggregated Crystallographic Data took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Crystal Eye: Aggregated Crystallographic Data took 2.8848648071289062e-05s
Believability | Calculation of trust value for Crystal Eye: Aggregated Crystallographic Data took 5.4836273193359375e-06s
INFO | --- Analysis for crystal-eye took 3.3339598178863525s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 6.93284010887146s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.0005664825439453125s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 0.34877634048461914s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.020084857940673828s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 4.38690185546875e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 4.291534423828125e-06s
INFO | --- Analysis for ctic-public-dataset took 45.07463312149048s
Availability | SPARQL endpoint availability check for Cultivation status of GMO crops took 4.0531158447265625e-05s
Availability | VoID file availability check for Cultivation status of GMO crops took 0.00023651123046875s
Completeness | Calculation of interlinking completeness for Cultivation status of GMO crops took 0.25996899604797363s
Reputation | Calculation of the PageRank for Cultivation status of GMO crops took 0.019977331161499023s
Interlinking | Calculation of Degree of Connection for Cultivation status of GMO crops took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cultivation status of GMO crops took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Cultivation status of GMO crops took 2.7894973754882812e-05s
Believability | Calculation of trust value for Cultivation status of GMO crops took 7.62939453125e-06s
INFO | --- Analysis for cultivation-status-of-gmo-crops took 2.95294189453125s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 10.813279867172241s
Availability | VoID file availability check for CulturaLinkedData took 0.0006566047668457031s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 0.27426791191101074s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.02004241943359375s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 2.956390380859375e-05s
Believability | Calculation of trust value for CulturaLinkedData took 7.152557373046875e-06s
INFO | --- Analysis for culturalinkeddata took 24.518158435821533s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 30.69670343399048s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0008416175842285156s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.29043078422546387s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.020265579223632812s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 4.076957702636719e-05s
Believability | Calculation of trust value for Data about business entities from the ARES system - business registry of the Czech Republic took 5.0067901611328125e-06s
INFO | --- Analysis for cz-ares-or took 104.12730956077576s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 30.192299842834473s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0010652542114257812s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.26541781425476074s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.021245241165161133s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0008413791656494141s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 4.9114227294921875e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 4.291534423828125e-06s
INFO | --- Analysis for cz-ares-rzp took 103.74845910072327s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 30.19815731048584s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.0006947517395019531s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.7302348613739014s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.020467519760131836s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 3.266334533691406e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 4.76837158203125e-06s
INFO | --- Analysis for cz-cenia-irz-chemicals took 134.24480724334717s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 30.286579847335815s
Availability | VoID file availability check for Integrated pollution registry took 0.0007233619689941406s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.2726311683654785s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.02065420150756836s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 4.887580871582031e-05s
Believability | Calculation of trust value for Integrated pollution registry took 5.0067901611328125e-06s
INFO | --- Analysis for cz-cenia-pollution took 123.55075240135193s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 30.14221978187561s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.0007319450378417969s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.26878929138183594s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.020566940307617188s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Contracts took 4.100799560546875e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Contracts took 4.0531158447265625e-06s
INFO | --- Analysis for cz-contracts took 103.05413746833801s
Availability | SPARQL endpoint availability check for List of courts of the Czech Republic took 4.100799560546875e-05s
Availability | VoID file availability check for List of courts of the Czech Republic took 0.0002865791320800781s
Completeness | Calculation of interlinking completeness for List of courts of the Czech Republic took 0.27614808082580566s
Reputation | Calculation of the PageRank for List of courts of the Czech Republic took 0.020209550857543945s
Interlinking | Calculation of Degree of Connection for List of courts of the Czech Republic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for List of courts of the Czech Republic took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for List of courts of the Czech Republic took 3.0994415283203125e-05s
Believability | Calculation of trust value for List of courts of the Czech Republic took 5.9604644775390625e-06s
INFO | --- Analysis for cz-courts took 4.43501091003418s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 30.28536891937256s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.0007658004760742188s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.33150815963745117s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.02036261558532715s
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.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 3.337860107421875e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 5.0067901611328125e-06s
INFO | --- Analysis for cz-ctia-bans took 106.35894632339478s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 30.094111680984497s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.0010068416595458984s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 0.7952747344970703s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.020402193069458008s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 3.814697265625e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 4.0531158447265625e-06s
INFO | --- Analysis for cz-ctia-confiscations took 104.45288896560669s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 30.053474187850952s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.0006494522094726562s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.33150768280029297s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.02032470703125s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 3.552436828613281e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 4.291534423828125e-06s
INFO | --- Analysis for cz-ctia-focus took 104.06619501113892s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 30.096116304397583s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.0007281303405761719s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 0.3241903781890869s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.0205843448638916s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 4.839897155761719e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 4.76837158203125e-06s
INFO | --- Analysis for cz-ctia-inspections took 103.65901589393616s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 30.098117351531982s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.0006680488586425781s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.7608840465545654s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.020221948623657227s
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.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 3.4332275390625e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 5.7220458984375e-06s
INFO | --- Analysis for cz-ctia-sanctions took 106.74172043800354s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 20.147942304611206s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.0005993843078613281s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.2979128360748291s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.020082473754882812s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 4.4345855712890625e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 4.5299530029296875e-06s
INFO | --- Analysis for cz-cuzk-cadastre-offices took 94.35048222541809s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 20.2620792388916s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.0005383491516113281s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.3942859172821045s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.020214080810546875s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 3.123283386230469e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 5.4836273193359375e-06s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 96.66035056114197s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 20.91412377357483s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.27816343307495117s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.020577430725097656s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 4.673004150390625e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 4.5299530029296875e-06s
INFO | --- Analysis for cz-czso-average-salaries took 95.17327880859375s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 20.370882511138916s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 0.6837966442108154s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.020307302474975586s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 3.504753112792969e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 5.0067901611328125e-06s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 94.96465706825256s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 20.356910228729248s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0002963542938232422s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.7006173133850098s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.021012544631958008s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 4.744529724121094e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 5.0067901611328125e-06s
INFO | --- Analysis for cz-czso-demography-in-regions-czech-republic-age-categories took 95.82596826553345s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 20.37140202522278s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.737633228302002s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.02010178565979004s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 4.506111145019531e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 5.0067901611328125e-06s
INFO | --- Analysis for cz-czso-job-applicants took 95.28398513793945s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 20.353573083877563s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.00055694580078125s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.7038204669952393s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.020575523376464844s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 4.696846008300781e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 5.7220458984375e-06s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 94.42001795768738s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 20.239763021469116s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0006725788116455078s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.3032722473144531s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.02032303810119629s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 3.337860107421875e-05s
Believability | Calculation of trust value for Structure of regions of Czech Republic according to Czech Statistical Office took 5.245208740234375e-06s
INFO | --- Analysis for cz-czso-regions took 93.75157761573792s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 20.29106903076172s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.0005652904510498047s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 0.2744157314300537s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.02054142951965332s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 4.0531158447265625e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 6.67572021484375e-06s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 93.97001791000366s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 20.315138339996338s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.0003039836883544922s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.6849880218505859s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.02047419548034668s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 4.410743713378906e-05s
Believability | Calculation of trust value for Social service facilities and nursing in districts of Czech republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-czso-social-service-facilities took 95.26779508590698s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 20.324954748153687s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.00028061866760253906s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.2906315326690674s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.020172119140625s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 5.14984130859375e-05s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 4.5299530029296875e-06s
INFO | --- Analysis for cz-czso-unemployment-rate took 93.97831010818481s
Availability | SPARQL endpoint availability check for ATC groups took 30.027043342590332s
Availability | VoID file availability check for ATC groups took 0.0007278919219970703s
Completeness | Calculation of interlinking completeness for ATC groups took 0.7888267040252686s
Reputation | Calculation of the PageRank for ATC groups took 0.020424365997314453s
Interlinking | Calculation of Degree of Connection for ATC groups took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for ATC groups took 6.842613220214844e-05s
Believability | Calculation of trust value for ATC groups took 7.152557373046875e-06s
INFO | --- Analysis for cz-eh-1-atc took 104.84761929512024s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 30.034990549087524s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0007300376892089844s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.2782421112060547s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.020330190658569336s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Financial fulfillments took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 4.935264587402344e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 4.76837158203125e-06s
INFO | --- Analysis for cz-fulfillments took 103.13865613937378s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 0.036801815032958984s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.0007855892181396484s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.2721378803253174s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.020654916763305664s
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.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 4.839897155761719e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 5.0067901611328125e-06s
INFO | --- Analysis for cz-ic took 22.965787649154663s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 20.057194471359253s
Availability | VoID file availability check for List of Czech data boxes took 0.0007534027099609375s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 0.7304935455322266s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.020514726638793945s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 4.029273986816406e-05s
Believability | Calculation of trust value for List of Czech data boxes took 5.0067901611328125e-06s
INFO | --- Analysis for cz-list-of-databoxes took 93.48211359977722s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 20.18909192085266s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0008726119995117188s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.2186081409454346s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.020984649658203125s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.9577484130859375e-05s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 5.245208740234375e-06s
INFO | --- Analysis for cz-nace took 95.02432298660278s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.620495080947876s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0005424022674560547s
Extra | Recovery of all triples for Czech National Open Data Catalog in DCAT-AP v1.2 took 143.9099576473236s
Performance | Total latancy measurement for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.8012979030609131s
Amount of data | Number of triples check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5199863910675049s
Interoperability | New terms check for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.6746978759765625s
Versatility | Languages check for Czech National Open Data Catalog in DCAT-AP v1.2 took 55.67520880699158s
Interpretability | Number of blank nodes check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.4951896667480469s
Interpretability | RDF structures check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.17794036865234375s
Versatility | Serialization formats check for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.780198335647583s
Availability | RDF dump link check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2548646926879883s
License | MR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3596804141998291s
License | HR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.532332181930542s
Amount of data | Number of property check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.15222907066345215s
Understandability | Number of label check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.4541018009185791s
Understandability | URI regex check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3062913417816162s
Understandability | Vocabs check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.18205523490905762s
Verifiability | Authors check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.15598678588867188s
Verifiability | Publishers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2387375831604004s
Performance | Throughput check for Czech National Open Data Catalog in DCAT-AP v1.2 took 10.990220308303833s
Amount of data | Check the number of entities for Czech National Open Data Catalog in DCAT-AP v1.2 took 9.059906005859375e-05s
Verifiability | Contribs. check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.14953398704528809s
Interlinking | sameAs chians check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.1998310089111328s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2794318199157715s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.17708992958068848s
Timeliness | dataset update frequency check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.7112932205200195s
Currency | Creation date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3982422351837158s
Currency | Modification date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3165583610534668s
Rep.Conc. | URIs length for Czech National Open Data Catalog in DCAT-AP v1.2 took 55.3949511051178s
Interoperability | New vocabularies check for Czech National Open Data Catalog in DCAT-AP v1.2 took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.15172600746154785s
Accuracy | Check Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.15752720832824707s
Accuracy | Check Inverse Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.15854835510253906s
Accuracy | Check Empty annotation labels for Czech National Open Data Catalog in DCAT-AP v1.2 took 40.80411720275879s
Accuracy | Check White space in annotation for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.363348960876465s
Accuracy | Check Datatype consistency for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.5532219409942627s
Consistency | Disjoint class check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.1792290210723877s
Consistency | Check Misplaced properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.379352331161499s
Consistency | Misplaced classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 8.279195785522461s
Consistency | Check Ontology hijacking for Czech National Open Data Catalog in DCAT-AP v1.2 took 96.20863127708435s
Consistency | Check Invalid usage of undefined classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.8030929565429688s
Consistency | Check Invalid usage of undefined properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.6491858959198s
Conciseness | Check Extensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.087035655975342s
Conciseness | Check Intensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.20354509353637695s
Security | Sign check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.4514429569244385s
Availability | Check URIs Dereferenciability for Czech National Open Data Catalog in DCAT-AP v1.2 took 879.0204117298126s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.6733229160308838s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.054743051528930664s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.2 took 6.961822509765625e-05s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.2 took 8.344650268554688e-05s
Interoperability | Check the re-using of existing vocabs for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.1457672119140625e-06s
Believability | Calculation of trust value for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.3828277587890625e-05s
INFO | --- Analysis for cz-nkod took 41666.44315171242s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 30.1419734954834s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.0006926059722900391s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 0.7261707782745361s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.020424604415893555s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Orders took 4.839897155761719e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Orders took 5.7220458984375e-06s
INFO | --- Analysis for cz-orders took 104.70248627662659s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 20.1303870677948s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.0009503364562988281s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 0.730339527130127s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.020989656448364258s
Interlinking | Calculation of Degree of Connection for Institutions of public power of the Czech Republic took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Institutions of public power of the Czech Republic took 0.000835418701171875s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 4.57763671875e-05s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 4.76837158203125e-06s
INFO | --- Analysis for cz-ovm took 95.38455390930176s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 30.263097286224365s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.0007026195526123047s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 0.8091938495635986s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.021190643310546875s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0008001327514648438s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 4.124641418457031e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-ovm-agendas took 104.94079899787903s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.3504056930541992s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0006110668182373047s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.24617910385131836s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.020415067672729492s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 7.295608520507812e-05s
Believability | Calculation of trust value for Registry of territorial identification, addresses and real estate of the Czech Republic took 5.0067901611328125e-06s
INFO | --- Analysis for cz-ruian took 5.07110071182251s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 20.87380313873291s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.00028967857360839844s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.25267839431762695s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.022635459899902344s
Interlinking | Calculation of Degree of Connection for Audited subjects of Supreme Audit Office of the Czech Republic took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0012736320495605469s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 9.965896606445312e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 5.245208740234375e-06s
INFO | --- Analysis for cz-sao-audited-subjects took 95.42784237861633s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 20.400763034820557s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.0003082752227783203s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 0.6793086528778076s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.02080368995666504s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 3.981590270996094e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 4.76837158203125e-06s
INFO | --- Analysis for cz-sao-check-actions took 94.45651125907898s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 20.361342906951904s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 0.6855885982513428s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.020464420318603516s
Interlinking | Calculation of Degree of Connection for List of laws used in inspection reports of SAO took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for List of laws used in inspection reports of SAO took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for List of laws used in inspection reports of SAO took 4.00543212890625e-05s
Believability | Calculation of trust value for List of laws used in inspection reports of SAO took 5.0067901611328125e-06s
INFO | --- Analysis for cz-sao-check-actions-law took 94.02410173416138s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 30.125859022140503s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.0007150173187255859s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 0.3332087993621826s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.02051091194152832s
Interlinking | Calculation of Degree of Connection for Active ingredients of medicinal products available in Czech Republic took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Active ingredients of medicinal products available in Czech Republic took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 3.361701965332031e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 6.9141387939453125e-06s
INFO | --- Analysis for cz-sidc-drug-ingredients took 103.02997756004333s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 30.17311429977417s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0011584758758544922s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 0.26955080032348633s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.02081155776977539s
Interlinking | Calculation of Degree of Connection for List of prices of reimbursed medicinal products marketed in Czech republic took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 3.528594970703125e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 4.76837158203125e-06s
INFO | --- Analysis for cz-sidc-drug-prices took 104.532390832901s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 30.10275888442993s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.0008139610290527344s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 0.39600563049316406s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.0207672119140625s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 3.528594970703125e-05s
Believability | Calculation of trust value for Medicinal products marketed in Czech Republic took 7.62939453125e-06s
INFO | --- Analysis for cz-sidc-drugs took 133.5181999206543s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 20.06221079826355s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.0008223056793212891s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 0.2472822666168213s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.02061009407043457s
Interlinking | Calculation of Degree of Connection for Summary types of Czech institutions of public power took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Summary types of Czech institutions of public power took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 4.172325134277344e-05s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 4.76837158203125e-06s
INFO | --- Analysis for cz-souhrnne-typy-ovm took 113.93306541442871s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 30.045850038528442s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.0007448196411132812s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 0.2003490924835205s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.02086162567138672s
Interlinking | Calculation of Degree of Connection for Evaluation of VaVaI results for 2013 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Evaluation of VaVaI results for 2013 took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 4.267692565917969e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 5.4836273193359375e-06s
INFO | --- Analysis for cz-vavai-evaluation-2013 took 113.2184956073761s
Availability | SPARQL endpoint availability check for State funding providers took 30.23920440673828s
Availability | VoID file availability check for State funding providers took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for State funding providers took 0.6755037307739258s
Reputation | Calculation of the PageRank for State funding providers took 0.020623207092285156s
Interlinking | Calculation of Degree of Connection for State funding providers took 1.52587890625e-05s
Interlinking | Calculation of Centrality for State funding providers took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for State funding providers took 3.6716461181640625e-05s
Believability | Calculation of trust value for State funding providers took 4.5299530029296875e-06s
INFO | --- Analysis for cz-vavai-funding-providers took 114.65593314170837s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 30.036043405532837s
Availability | VoID file availability check for Organizations active in R&D took 0.0006575584411621094s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 0.25423097610473633s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.021860361099243164s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.001531362533569336s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 7.43865966796875e-05s
Believability | Calculation of trust value for Organizations active in R&D took 5.0067901611328125e-06s
INFO | --- Analysis for cz-vavai-organizations took 153.86218881607056s
Availability | SPARQL endpoint availability check for R&D Programmes took 30.250274896621704s
Availability | VoID file availability check for R&D Programmes took 0.0010268688201904297s
Completeness | Calculation of interlinking completeness for R&D Programmes took 0.7441315650939941s
Reputation | Calculation of the PageRank for R&D Programmes took 0.025685548782348633s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for R&D Programmes took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 3.886222839355469e-05s
Believability | Calculation of trust value for R&D Programmes took 5.245208740234375e-06s
INFO | --- Analysis for cz-vavai-programmes took 115.06891870498657s
Availability | SPARQL endpoint availability check for R&D Projects took 30.14847755432129s
Availability | VoID file availability check for R&D Projects took 0.0007264614105224609s
Completeness | Calculation of interlinking completeness for R&D Projects took 0.7096221446990967s
Reputation | Calculation of the PageRank for R&D Projects took 0.020192861557006836s
Interlinking | Calculation of Degree of Connection for R&D Projects took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for R&D Projects took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 4.601478576660156e-05s
Believability | Calculation of trust value for R&D Projects took 5.0067901611328125e-06s
INFO | --- Analysis for cz-vavai-projects took 113.97009801864624s
Availability | SPARQL endpoint availability check for Institutional research plans took 30.047428131103516s
Availability | VoID file availability check for Institutional research plans took 0.0006873607635498047s
Completeness | Calculation of interlinking completeness for Institutional research plans took 0.27236032485961914s
Reputation | Calculation of the PageRank for Institutional research plans took 0.020621776580810547s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Institutional research plans took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 3.9577484130859375e-05s
Believability | Calculation of trust value for Institutional research plans took 4.291534423828125e-06s
INFO | --- Analysis for cz-vavai-research-plans took 114.87234807014465s
Availability | SPARQL endpoint availability check for Results of R&D took 30.27836537361145s
Availability | VoID file availability check for Results of R&D took 0.0009672641754150391s
Completeness | Calculation of interlinking completeness for Results of R&D took 0.7886621952056885s
Reputation | Calculation of the PageRank for Results of R&D took 0.02040553092956543s
Interlinking | Calculation of Degree of Connection for Results of R&D took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Results of R&D took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 5.054473876953125e-05s
Believability | Calculation of trust value for Results of R&D took 5.245208740234375e-06s
INFO | --- Analysis for cz-vavai-results took 114.96912217140198s
Availability | SPARQL endpoint availability check for Tenders in R&D took 30.155388355255127s
Availability | VoID file availability check for Tenders in R&D took 0.0006887912750244141s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.25415563583374023s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.020526647567749023s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for Tenders in R&D took 5.841255187988281e-05s
Believability | Calculation of trust value for Tenders in R&D took 5.4836273193359375e-06s
INFO | --- Analysis for cz-vavai-tenders took 114.64746880531311s
Availability | SPARQL endpoint availability check for Czech addresses – Adresy v České republice took 4.1961669921875e-05s
Availability | VoID file availability check for Czech addresses – Adresy v České republice took 0.0005633831024169922s
Completeness | Calculation of interlinking completeness for Czech addresses – Adresy v České republice took 0.2479548454284668s
Reputation | Calculation of the PageRank for Czech addresses – Adresy v České republice took 0.02012038230895996s
Interlinking | Calculation of Degree of Connection for Czech addresses – Adresy v České republice took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Czech addresses – Adresy v České republice took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Czech addresses – Adresy v České republice took 3.24249267578125e-05s
Believability | Calculation of trust value for Czech addresses – Adresy v České republice took 7.62939453125e-06s
INFO | --- Analysis for czech_addresses took 5.8587706089019775s
Availability | SPARQL endpoint availability check for Dante Latin Loanwords in LiLa took 0.5881412029266357s
Availability | VoID file availability check for Dante Latin Loanwords in LiLa took 0.0006012916564941406s
Completeness | Calculation of interlinking completeness for Dante Latin Loanwords in LiLa took 0.2505631446838379s
Reputation | Calculation of the PageRank for Dante Latin Loanwords in LiLa took 0.020112037658691406s
Interlinking | Calculation of Degree of Connection for Dante Latin Loanwords in LiLa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Dante Latin Loanwords in LiLa took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Dante Latin Loanwords in LiLa took 3.5762786865234375e-05s
Believability | Calculation of trust value for Dante Latin Loanwords in LiLa took 5.4836273193359375e-06s
INFO | --- Analysis for DanteLatinLoanwords took 4.7878923416137695s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.35093045234680176s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.0006656646728515625s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 112.58226609230042s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 0.9059960842132568s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 8.82418704032898s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 2.500969409942627s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 120.30462050437927s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 0.445514440536499s
Security | Check HTTPS for data.bnf.fr - Bibliothèque nationale de France took 0.43776416778564453s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 0.5695290565490723s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 0.32410573959350586s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.3489725589752197s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 0.9228477478027344s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 40.29030179977417s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.20547866821289062s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 0.6952059268951416s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 0.42344093322753906s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.2113950252532959s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 0.2132570743560791s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 0.1997826099395752s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 10.513357639312744s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 7.05718994140625e-05s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 0.19992828369140625s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 0.40130114555358887s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.6804931163787842s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.21678900718688965s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.2299196720123291s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 0.41843461990356445s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 1.2669663429260254s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 58.78195285797119s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.2098522186279297s
Accuracy | Check Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.31967830657958984s
Accuracy | Check Inverse Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.36026811599731445s
Accuracy | Check Empty annotation labels for data.bnf.fr - Bibliothèque nationale de France took 36.16325807571411s
Accuracy | Check White space in annotation for data.bnf.fr - Bibliothèque nationale de France took 3.1642444133758545s
Accuracy | Check Datatype consistency for data.bnf.fr - Bibliothèque nationale de France took 2.666736364364624s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 0.2854280471801758s
Consistency | Check Misplaced properties for data.bnf.fr - Bibliothèque nationale de France took 7.743546724319458s
Consistency | Misplaced classes for data.bnf.fr - Bibliothèque nationale de France took 8.760991096496582s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 38.50584554672241s
Consistency | Check Invalid usage of undefined classes for data.bnf.fr - Bibliothèque nationale de France took 1.4930431842803955s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 8.852736711502075s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 2.7939791679382324s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.21280574798583984s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 0.2330946922302246s
Availability | Check URIs Dereferenciability for data.bnf.fr - Bibliothèque nationale de France took 8.638370752334595s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 1.2532286643981934s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.027055978775024414s
Interlinking | Calculation of Degree of Connection for data.bnf.fr - Bibliothèque nationale de France took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for data.bnf.fr - Bibliothèque nationale de France took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.00015091896057128906s
Interoperability | Check the re-using of existing vocabs for data.bnf.fr - Bibliothèque nationale de France took 1.430511474609375e-06s
Believability | Calculation of trust value for data.bnf.fr - Bibliothèque nationale de France took 7.152557373046875e-06s
INFO | --- Analysis for data-bnf-fr took 643.5940742492676s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 0.12972164154052734s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.0005784034729003906s
Extra | Recovery of all triples for Open Data from the Italian National Research Council took 0.8383898735046387s
Performance | Total latancy measurement for Open Data from the Italian National Research Council took 0.3050215244293213s
Amount of data | Number of triples check for Open Data from the Italian National Research Council took 4.16401481628418s
Interoperability | New terms check for Open Data from the Italian National Research Council took 2.3093512058258057s
Versatility | Languages check for Open Data from the Italian National Research Council took 0.0783698558807373s
Interpretability | Number of blank nodes check for Open Data from the Italian National Research Council took 0.578765869140625s
Security | Check HTTPS for Open Data from the Italian National Research Council took 0.03955721855163574s
Interpretability | RDF structures check for Open Data from the Italian National Research Council took 0.1010899543762207s
Versatility | Serialization formats check for Open Data from the Italian National Research Council took 0.09672355651855469s
Availability | RDF dump link check for Open Data from the Italian National Research Council took 0.0803983211517334s
License | MR license check for Open Data from the Italian National Research Council took 0.09583139419555664s
License | HR license check for Open Data from the Italian National Research Council took 12.027566909790039s
Amount of data | Number of property check for Open Data from the Italian National Research Council took 0.09083271026611328s
Understandability | Number of label check for Open Data from the Italian National Research Council took 3.8952322006225586s
Understandability | URI regex check for Open Data from the Italian National Research Council took 0.1659097671508789s
Understandability | Vocabs check for Open Data from the Italian National Research Council took 0.08368921279907227s
Verifiability | Authors check for Open Data from the Italian National Research Council took 0.0868978500366211s
Verifiability | Publishers check for Open Data from the Italian National Research Council took 0.08088302612304688s
Performance | Throughput check for Open Data from the Italian National Research Council took 10.388769149780273s
Amount of data | Check the number of entities for Open Data from the Italian National Research Council took 8.416175842285156e-05s
Verifiability | Contribs. check for Open Data from the Italian National Research Council took 0.08140134811401367s
Interlinking | sameAs chians check for Open Data from the Italian National Research Council took 0.08782362937927246s
Interlinking | skos check for Open Data from the Italian National Research Council took 0.08146023750305176s
Interlinking | skos check for Open Data from the Italian National Research Council took 0.05649709701538086s
Timeliness | dataset update frequency check for Open Data from the Italian National Research Council took 0.08467960357666016s
Currency | Creation date check for Open Data from the Italian National Research Council took 0.17026591300964355s
Currency | Modification date check for Open Data from the Italian National Research Council took 0.17557549476623535s
Rep.Conc. | URIs length for Open Data from the Italian National Research Council took 12.038856983184814s
Consistency | Deprecated classes/propertiers check for Open Data from the Italian National Research Council took 0.08429121971130371s
Accuracy | Check Functional Property for Open Data from the Italian National Research Council took 0.08245658874511719s
Accuracy | Check Inverse Functional Property for Open Data from the Italian National Research Council took 0.08217096328735352s
Accuracy | Check Empty annotation labels for Open Data from the Italian National Research Council took 0.4023866653442383s
Accuracy | Check White space in annotation for Open Data from the Italian National Research Council took 0.03307390213012695s
Accuracy | Check Datatype consistency for Open Data from the Italian National Research Council took 0.027926921844482422s
Consistency | Disjoint class check for Open Data from the Italian National Research Council took 0.08217763900756836s
Consistency | Check Misplaced properties for Open Data from the Italian National Research Council took 10.2266526222229s
Consistency | Misplaced classes for Open Data from the Italian National Research Council took 0.18797945976257324s
Consistency | Check Ontology hijacking for Open Data from the Italian National Research Council took 1.624277114868164s
Consistency | Check Invalid usage of undefined classes for Open Data from the Italian National Research Council took 1.3459961414337158s
Consistency | Check Invalid usage of undefined properties for Open Data from the Italian National Research Council took 11.54908037185669s
Conciseness | Check Extensional conciseness for Open Data from the Italian National Research Council took 0.03242826461791992s
Conciseness | Check Intensional conciseness for Open Data from the Italian National Research Council took 0.10321259498596191s
Security | Sign check for Open Data from the Italian National Research Council took 0.08258795738220215s
Availability | Check URIs Dereferenciability for Open Data from the Italian National Research Council took 575.6356430053711s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 0.799013614654541s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.021663427352905273s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 8.463859558105469e-05s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 6.9141387939453125e-06s
INFO | --- Analysis for data-cnr-it took 679.8370134830475s
Availability | SPARQL endpoint availability check for Data.gov took 1.6241841316223145s
Availability | VoID file availability check for Data.gov took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for Data.gov took 0.7590899467468262s
Reputation | Calculation of the PageRank for Data.gov took 0.020511388778686523s
Interlinking | Calculation of Degree of Connection for Data.gov took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Data.gov took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Data.gov took 3.266334533691406e-05s
Believability | Calculation of trust value for Data.gov took 1.0013580322265625e-05s
INFO | --- Analysis for data-gov took 19.973926305770874s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 0.8907885551452637s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.0004558563232421875s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 0.6821708679199219s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.020086050033569336s
Interlinking | Calculation of Degree of Connection for DataGovIE - Irish Government Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DataGovIE - Irish Government Data took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 7.033348083496094e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 4.5299530029296875e-06s
INFO | --- Analysis for data-gov-ie took 4.606244087219238s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 4.1961669921875e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 0.2447059154510498s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.020136356353759766s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for data.gov.uk Time Intervals took 6.866455078125e-05s
Believability | Calculation of trust value for data.gov.uk Time Intervals took 5.0067901611328125e-06s
INFO | --- Analysis for data-gov-uk-time-intervals took 3.7278292179107666s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 21.857154607772827s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.0008521080017089844s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 0.6892468929290771s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.020678281784057617s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 5.745887756347656e-05s
Believability | Calculation of trust value for data-hnm-hu - Hungarian National Museum Datasets took 7.62939453125e-06s
INFO | --- Analysis for data-hnm-hu took 163.29431462287903s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.22014307975769043s
Availability | VoID file availability check for Climb Dataincubator took 0.00042057037353515625s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.24380993843078613s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.020694494247436523s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 8.416175842285156e-05s
Believability | Calculation of trust value for Climb Dataincubator took 6.4373016357421875e-06s
INFO | --- Analysis for data-incubator-climb took 3.357966899871826s
Availability | SPARQL endpoint availability check for Discogs in RDF took 4.482269287109375e-05s
Availability | VoID file availability check for Discogs in RDF took 0.0006854534149169922s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.2500011920928955s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.02023601531982422s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 9.179115295410156e-05s
Believability | Calculation of trust value for Discogs in RDF took 5.0067901611328125e-06s
INFO | --- Analysis for data-incubator-discogs took 6.997026205062866s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 0.052590370178222656s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.0007181167602539062s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 0.2543168067932129s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.02042865753173828s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 5.364418029785156e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 5.0067901611328125e-06s
INFO | --- Analysis for data-incubator-metoffice took 5.537656545639038s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.05899524688720703s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.0007658004760742188s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 0.274503231048584s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.02029871940612793s
Interlinking | Calculation of Degree of Connection for Moseley Folk Festival Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Moseley Folk Festival Data took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 8.559226989746094e-05s
Believability | Calculation of trust value for Moseley Folk Festival Data took 5.245208740234375e-06s
INFO | --- Analysis for data-incubator-moseley took 8.938573122024536s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.052063703536987305s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.00044345855712890625s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 0.2506070137023926s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.02025008201599121s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.0008113384246826172s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 8.749961853027344e-05s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 8.106231689453125e-06s
INFO | --- Analysis for data-incubator-musicbrainz took 2.7916061878204346s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 1.8859984874725342s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.000690460205078125s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 0.24454307556152344s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.02027297019958496s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for NASA Space Flight & Astronaut data in RDF took 8.940696716308594e-05s
Believability | Calculation of trust value for NASA Space Flight & Astronaut data in RDF took 4.291534423828125e-06s
INFO | --- Analysis for data-incubator-nasa took 7.700233459472656s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 0.06675362586975098s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.00020432472229003906s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 0.25044703483581543s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.020476818084716797s
Interlinking | Calculation of Degree of Connection for Airport data from Our Airports published as RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Airport data from Our Airports published as RDF took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 7.677078247070312e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 5.0067901611328125e-06s
INFO | --- Analysis for data-incubator-our-airports took 2.4469449520111084s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 0.05539894104003906s
Availability | VoID file availability check for Pokedex data in RDF took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 0.34988903999328613s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.02045416831970215s
Interlinking | Calculation of Degree of Connection for Pokedex data in RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Pokedex data in RDF took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 9.107589721679688e-05s
Believability | Calculation of trust value for Pokedex data in RDF took 4.5299530029296875e-06s
INFO | --- Analysis for data-incubator-pokedex took 4.950845241546631s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.05253911018371582s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 0.2823057174682617s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.020726680755615234s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 9.34600830078125e-05s
Believability | Calculation of trust value for Scottish Mountaineering Council Journals Issues 1-36 took 7.62939453125e-06s
INFO | --- Analysis for data-incubator-smcjournals took 2.402311325073242s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 0.6024432182312012s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.0005500316619873047s
Extra | Recovery of all triples for data.open.ac.uk, Linked Data from the Open University took 67.01379084587097s
Performance | Total latancy measurement for data.open.ac.uk, Linked Data from the Open University took 1.2045559883117676s
Amount of data | Number of triples check for data.open.ac.uk, Linked Data from the Open University took 0.2635610103607178s
Interoperability | New terms check for data.open.ac.uk, Linked Data from the Open University took 1.470526933670044s
Versatility | Languages check for data.open.ac.uk, Linked Data from the Open University took 12.704200267791748s
Interpretability | Number of blank nodes check for data.open.ac.uk, Linked Data from the Open University took 0.2581517696380615s
Security | Check HTTPS for data.open.ac.uk, Linked Data from the Open University took 0.13654589653015137s
Interpretability | RDF structures check for data.open.ac.uk, Linked Data from the Open University took 0.28558921813964844s
Versatility | Serialization formats check for data.open.ac.uk, Linked Data from the Open University took 0.30553507804870605s
Availability | RDF dump link check for data.open.ac.uk, Linked Data from the Open University took 0.25800037384033203s
License | MR license check for data.open.ac.uk, Linked Data from the Open University took 0.2856101989746094s
License | HR license check for data.open.ac.uk, Linked Data from the Open University took 3.286166191101074s
Amount of data | Number of property check for data.open.ac.uk, Linked Data from the Open University took 0.26553797721862793s
Understandability | Number of label check for data.open.ac.uk, Linked Data from the Open University took 0.43919849395751953s
Understandability | URI regex check for data.open.ac.uk, Linked Data from the Open University took 0.5567586421966553s
Understandability | Vocabs check for data.open.ac.uk, Linked Data from the Open University took 0.28617334365844727s
Verifiability | Authors check for data.open.ac.uk, Linked Data from the Open University took 0.3020017147064209s
Verifiability | Publishers check for data.open.ac.uk, Linked Data from the Open University took 0.27170491218566895s
Performance | Throughput check for data.open.ac.uk, Linked Data from the Open University took 11.709332466125488s
Amount of data | Check the number of entities for data.open.ac.uk, Linked Data from the Open University took 7.033348083496094e-05s
Verifiability | Contribs. check for data.open.ac.uk, Linked Data from the Open University took 0.274738073348999s
Interlinking | sameAs chians check for data.open.ac.uk, Linked Data from the Open University took 0.26753687858581543s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.3104369640350342s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.2847931385040283s
Timeliness | dataset update frequency check for data.open.ac.uk, Linked Data from the Open University took 0.28107166290283203s
Currency | Creation date check for data.open.ac.uk, Linked Data from the Open University took 0.5801398754119873s
Currency | Modification date check for data.open.ac.uk, Linked Data from the Open University took 0.5508232116699219s
Rep.Conc. | URIs length for data.open.ac.uk, Linked Data from the Open University took 51.014360189437866s
Interoperability | New vocabularies check for data.open.ac.uk, Linked Data from the Open University took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for data.open.ac.uk, Linked Data from the Open University took 0.2686479091644287s
Accuracy | Check Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.2589850425720215s
Accuracy | Check Inverse Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.2592761516571045s
Accuracy | Check Empty annotation labels for data.open.ac.uk, Linked Data from the Open University took 32.962406158447266s
Accuracy | Check White space in annotation for data.open.ac.uk, Linked Data from the Open University took 3.201389789581299s
Consistency | Disjoint class check for data.open.ac.uk, Linked Data from the Open University took 0.2574727535247803s
Consistency | Check Misplaced properties for data.open.ac.uk, Linked Data from the Open University took 0.7243382930755615s
Consistency | Check Ontology hijacking for data.open.ac.uk, Linked Data from the Open University took 18.46109676361084s
Consistency | Check Invalid usage of undefined properties for data.open.ac.uk, Linked Data from the Open University took 1.5828101634979248s
Conciseness | Check Extensional conciseness for data.open.ac.uk, Linked Data from the Open University took 0.0001437664031982422s
Conciseness | Check Intensional conciseness for data.open.ac.uk, Linked Data from the Open University took 0.4016909599304199s
Security | Sign check for data.open.ac.uk, Linked Data from the Open University took 0.271803617477417s
Availability | Check URIs Dereferenciability for data.open.ac.uk, Linked Data from the Open University took 1537.979960680008s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 1.2111411094665527s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.021466970443725586s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 8.130073547363281e-05s
Interoperability | Check the re-using of existing vocabs for data.open.ac.uk, Linked Data from the Open University took 1.9073486328125e-06s
Believability | Calculation of trust value for data.open.ac.uk, Linked Data from the Open University took 6.67572021484375e-06s
INFO | --- Analysis for data-open-ac-uk took 1827.8546242713928s
Availability | SPARQL endpoint availability check for Persée in RDF took 0.717540979385376s
Availability | VoID file availability check for Persée in RDF took 0.0007281303405761719s
Extra | Recovery of all triples for Persée in RDF took 1.7766695022583008s
Performance | Total latancy measurement for Persée in RDF took 0.5765633583068848s
Amount of data | Number of triples check for Persée in RDF took 1.9633409976959229s
Interoperability | New terms check for Persée in RDF took 1.7106049060821533s
Versatility | Languages check for Persée in RDF took 120.89351773262024s
Interpretability | Number of blank nodes check for Persée in RDF took 0.4544839859008789s
Interpretability | RDF structures check for Persée in RDF took 1.2381539344787598s
Versatility | Serialization formats check for Persée in RDF took 0.9244575500488281s
Availability | RDF dump link check for Persée in RDF took 0.28040289878845215s
License | MR license check for Persée in RDF took 1.7719531059265137s
License | HR license check for Persée in RDF took 38.89634442329407s
Amount of data | Number of property check for Persée in RDF took 0.12226986885070801s
Understandability | Number of label check for Persée in RDF took 1.9069182872772217s
Understandability | URI regex check for Persée in RDF took 0.8501362800598145s
Understandability | Vocabs check for Persée in RDF took 0.404982328414917s
Verifiability | Authors check for Persée in RDF took 0.12471818923950195s
Verifiability | Publishers check for Persée in RDF took 0.21940112113952637s
Performance | Throughput check for Persée in RDF took 10.560937881469727s
Amount of data | Check the number of entities for Persée in RDF took 8.249282836914062e-05s
Verifiability | Contribs. check for Persée in RDF took 0.22889232635498047s
Interlinking | sameAs chians check for Persée in RDF took 0.17727327346801758s
Interlinking | skos check for Persée in RDF took 0.7128269672393799s
Interlinking | skos check for Persée in RDF took 0.11624574661254883s
Timeliness | dataset update frequency check for Persée in RDF took 0.6740067005157471s
Currency | Creation date check for Persée in RDF took 0.42180728912353516s
Currency | Modification date check for Persée in RDF took 0.9953866004943848s
Rep.Conc. | URIs length for Persée in RDF took 3.5061614513397217s
Interoperability | New vocabularies check for Persée in RDF took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Persée in RDF took 0.11823487281799316s
Accuracy | Check Functional Property for Persée in RDF took 0.13147687911987305s
Accuracy | Check Inverse Functional Property for Persée in RDF took 0.13418817520141602s
Accuracy | Check Empty annotation labels for Persée in RDF took 0.9883687496185303s
Accuracy | Check White space in annotation for Persée in RDF took 0.040138959884643555s
Accuracy | Check Datatype consistency for Persée in RDF took 0.027519941329956055s
Consistency | Disjoint class check for Persée in RDF took 0.27925705909729004s
Consistency | Check Misplaced properties for Persée in RDF took 2.598757266998291s
Consistency | Misplaced classes for Persée in RDF took 0.21225428581237793s
Consistency | Check Ontology hijacking for Persée in RDF took 1.6948962211608887s
Consistency | Check Invalid usage of undefined classes for Persée in RDF took 1.1417856216430664s
Consistency | Check Invalid usage of undefined properties for Persée in RDF took 3.6426141262054443s
Conciseness | Check Extensional conciseness for Persée in RDF took 0.031807661056518555s
Conciseness | Check Intensional conciseness for Persée in RDF took 0.12668800354003906s
Security | Sign check for Persée in RDF took 0.6533098220825195s
Availability | Check URIs Dereferenciability for Persée in RDF took 1184.808571100235s
Completeness | Calculation of interlinking completeness for Persée in RDF took 1.257392406463623s
Reputation | Calculation of the PageRank for Persée in RDF took 0.020965576171875s
Interlinking | Calculation of Degree of Connection for Persée in RDF took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Persée in RDF took 0.0006785392761230469s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 0.00011181831359863281s
Interoperability | Check the re-using of existing vocabs for Persée in RDF took 1.6689300537109375e-06s
Believability | Calculation of trust value for Persée in RDF took 7.62939453125e-06s
INFO | --- Analysis for data-persee-fr took 1425.8643653392792s
Availability | SPARQL endpoint availability check for data.southampton.ac.uk with SPARQL endpoint took 4.458427429199219e-05s
Availability | VoID file availability check for data.southampton.ac.uk with SPARQL endpoint took 0.000225067138671875s
Completeness | Calculation of interlinking completeness for data.southampton.ac.uk with SPARQL endpoint took 0.267894983291626s
Reputation | Calculation of the PageRank for data.southampton.ac.uk with SPARQL endpoint took 0.020551443099975586s
Interlinking | Calculation of Degree of Connection for data.southampton.ac.uk with SPARQL endpoint took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for data.southampton.ac.uk with SPARQL endpoint took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for data.southampton.ac.uk with SPARQL endpoint took 3.0279159545898438e-05s
Believability | Calculation of trust value for data.southampton.ac.uk with SPARQL endpoint took 8.106231689453125e-06s
INFO | --- Analysis for data-southampton-ac-uk took 4.5091776847839355s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 0.7224414348602295s
Availability | VoID file availability check for data-szepmuveszeti-hu took 0.0003159046173095703s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 0.2673189640045166s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.020412683486938477s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.0001266002655029297s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 7.3909759521484375e-06s
INFO | --- Analysis for data-szepmuveszeti-hu took 8.249232530593872s
Availability | SPARQL endpoint availability check for Open Data Web took 0.2583770751953125s
Availability | VoID file availability check for Open Data Web took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.2789497375488281s
Reputation | Calculation of the PageRank for Open Data Web took 0.020478248596191406s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.0994415283203125e-05s
Believability | Calculation of trust value for Open Data Web took 7.62939453125e-06s
INFO | --- Analysis for data.odw.tw took 3.46274471282959s
Availability | SPARQL endpoint availability check for DataFAQs took 4.029273986816406e-05s
Availability | VoID file availability check for DataFAQs took 0.00022482872009277344s
Completeness | Calculation of interlinking completeness for DataFAQs took 0.2794506549835205s
Reputation | Calculation of the PageRank for DataFAQs took 0.020482540130615234s
Interlinking | Calculation of Degree of Connection for DataFAQs took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DataFAQs took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for DataFAQs took 3.147125244140625e-05s
Believability | Calculation of trust value for DataFAQs took 8.344650268554688e-06s
INFO | --- Analysis for datafaqs took 3.2751755714416504s
Availability | SPARQL endpoint availability check for datahub took 4.124641418457031e-05s
Availability | VoID file availability check for datahub took 0.000690460205078125s
Completeness | Calculation of interlinking completeness for datahub took 0.26378321647644043s
Reputation | Calculation of the PageRank for datahub took 0.020616769790649414s
Interlinking | Calculation of Degree of Connection for datahub took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for datahub took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for datahub took 4.8160552978515625e-05s
Believability | Calculation of trust value for datahub took 6.9141387939453125e-06s
INFO | --- Analysis for datahub took 3.0721442699432373s
Availability | SPARQL endpoint availability check for Open Datasets in South Korea took 5.360042333602905s
Availability | VoID file availability check for Open Datasets in South Korea took 0.0006318092346191406s
Completeness | Calculation of interlinking completeness for Open Datasets in South Korea took 0.2696044445037842s
Reputation | Calculation of the PageRank for Open Datasets in South Korea took 0.020524978637695312s
Interlinking | Calculation of Degree of Connection for Open Datasets in South Korea took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open Datasets in South Korea took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Open Datasets in South Korea took 3.0994415283203125e-05s
Believability | Calculation of trust value for Open Datasets in South Korea took 6.4373016357421875e-06s
INFO | --- Analysis for datahub-kr-datamap took 15.38507080078125s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.41399216651916504s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0006084442138671875s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.2824134826660156s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.02051568031311035s
Interlinking | Calculation of Degree of Connection for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 7.343292236328125e-05s
Believability | Calculation of trust value for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 7.3909759521484375e-06s
INFO | --- Analysis for dataturcyl-lod-for-tourists-in-castilla-y-leon-spain took 5.31609034538269s
Availability | SPARQL endpoint availability check for datos-artium-org took 21.261126041412354s
Availability | VoID file availability check for datos-artium-org took 0.0007550716400146484s
Completeness | Calculation of interlinking completeness for datos-artium-org took 0.6962034702301025s
Reputation | Calculation of the PageRank for datos-artium-org took 0.02094745635986328s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for datos-artium-org took 0.0008151531219482422s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.00013446807861328125s
Believability | Calculation of trust value for datos-artium-org took 1.52587890625e-05s
INFO | --- Analysis for datos-artium-org took 165.25492405891418s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 1.7864189147949219s
Availability | VoID file availability check for Datos.bcn.cl took 0.0006554126739501953s
Extra | Recovery of all triples for Datos.bcn.cl took 99.90793108940125s
Performance | Total latancy measurement for Datos.bcn.cl took 25.409963607788086s
Amount of data | Number of triples check for Datos.bcn.cl took 13.85129714012146s
Interoperability | New terms check for Datos.bcn.cl took 3.9153518676757812s
Versatility | Languages check for Datos.bcn.cl took 301.1739401817322s
Interpretability | Number of blank nodes check for Datos.bcn.cl took 12.584325790405273s
Security | Check HTTPS for Datos.bcn.cl took 0.7362992763519287s
Interpretability | RDF structures check for Datos.bcn.cl took 6.327572345733643s
Versatility | Serialization formats check for Datos.bcn.cl took 5.760645389556885s
Availability | RDF dump link check for Datos.bcn.cl took 6.027946949005127s
License | MR license check for Datos.bcn.cl took 6.036676406860352s
License | HR license check for Datos.bcn.cl took 52.32049608230591s
Amount of data | Number of property check for Datos.bcn.cl took 1.1885125637054443s
Understandability | Number of label check for Datos.bcn.cl took 6.826850414276123s
Understandability | URI regex check for Datos.bcn.cl took 11.249031066894531s
Understandability | Vocabs check for Datos.bcn.cl took 6.0217931270599365s
Verifiability | Authors check for Datos.bcn.cl took 6.050066947937012s
Verifiability | Publishers check for Datos.bcn.cl took 6.005116939544678s
Performance | Throughput check for Datos.bcn.cl took 60.29077458381653s
Amount of data | Check the number of entities for Datos.bcn.cl took 6.651878356933594e-05s
Verifiability | Contribs. check for Datos.bcn.cl took 6.034074306488037s
Interlinking | sameAs chians check for Datos.bcn.cl took 6.032675266265869s
Interlinking | skos check for Datos.bcn.cl took 6.057596206665039s
Interlinking | skos check for Datos.bcn.cl took 5.990541458129883s
Timeliness | dataset update frequency check for Datos.bcn.cl took 6.038633108139038s
Currency | Creation date check for Datos.bcn.cl took 12.071546077728271s
Currency | Modification date check for Datos.bcn.cl took 5.996556282043457s
Rep.Conc. | URIs length for Datos.bcn.cl took 53.57610321044922s
Interoperability | New vocabularies check for Datos.bcn.cl took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Datos.bcn.cl took 1.1853902339935303s
Accuracy | Check Functional Property for Datos.bcn.cl took 6.027583599090576s
Accuracy | Check Inverse Functional Property for Datos.bcn.cl took 6.024667501449585s
Accuracy | Check Empty annotation labels for Datos.bcn.cl took 26.310551404953003s
Accuracy | Check White space in annotation for Datos.bcn.cl took 0.2409200668334961s
Accuracy | Check Datatype consistency for Datos.bcn.cl took 0.2653656005859375s
Consistency | Disjoint class check for Datos.bcn.cl took 1.1665470600128174s
Consistency | Check Misplaced properties for Datos.bcn.cl took 15.762141942977905s
Consistency | Misplaced classes for Datos.bcn.cl took 3.1893911361694336s
Consistency | Check Ontology hijacking for Datos.bcn.cl took 30.398927688598633s
Consistency | Check Invalid usage of undefined classes for Datos.bcn.cl took 1.2235181331634521s
Consistency | Check Invalid usage of undefined properties for Datos.bcn.cl took 6.098015546798706s
Conciseness | Check Extensional conciseness for Datos.bcn.cl took 0.2954113483428955s
Conciseness | Check Intensional conciseness for Datos.bcn.cl took 1.4308593273162842s
Security | Sign check for Datos.bcn.cl took 5.80142617225647s
Availability | Check URIs Dereferenciability for Datos.bcn.cl took 8710.406895160675s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 1.346766471862793s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.02160501480102539s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 0.00010013580322265625s
Interoperability | Check the re-using of existing vocabs for Datos.bcn.cl took 1.430511474609375e-06s
Believability | Calculation of trust value for Datos.bcn.cl took 5.4836273193359375e-06s
INFO | --- Analysis for datos-bcn-cl took 9989.635930299759s
Availability | SPARQL endpoint availability check for datos.bne.es took 0.9910717010498047s
Availability | VoID file availability check for datos.bne.es took 0.0005006790161132812s
Completeness | Calculation of interlinking completeness for datos.bne.es took 0.7039375305175781s
Reputation | Calculation of the PageRank for datos.bne.es took 0.020453453063964844s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for datos.bne.es took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.00011968612670898438s
Believability | Calculation of trust value for datos.bne.es took 6.67572021484375e-06s
INFO | --- Analysis for datos-bne-es took 6.101276159286499s
Availability | SPARQL endpoint availability check for dbacademic took 0.04000520706176758s
Availability | VoID file availability check for dbacademic took 0.0003662109375s
Completeness | Calculation of interlinking completeness for dbacademic took 0.7123696804046631s
Reputation | Calculation of the PageRank for dbacademic took 0.02022552490234375s
Interlinking | Calculation of Degree of Connection for dbacademic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for dbacademic took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for dbacademic took 3.0040740966796875e-05s
Believability | Calculation of trust value for dbacademic took 5.0067901611328125e-06s
INFO | --- Analysis for dbacademic took 4.105745553970337s
Availability | SPARQL endpoint availability check for DBkWik took 216.89100289344788s
Availability | VoID file availability check for DBkWik took 0.0009491443634033203s
Completeness | Calculation of interlinking completeness for DBkWik took 0.28098559379577637s
Reputation | Calculation of the PageRank for DBkWik took 0.02058100700378418s
Interlinking | Calculation of Degree of Connection for DBkWik took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for DBkWik took 7.43865966796875e-05s
Believability | Calculation of trust value for DBkWik took 8.344650268554688e-06s
INFO | --- Analysis for dbkwik took 466.3877823352814s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 4.7206878662109375e-05s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.0006396770477294922s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 0.24838924407958984s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.02013993263244629s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.0001087188720703125s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 6.9141387939453125e-06s
INFO | --- Analysis for dblp-deusto-gnoss took 44.05453634262085s
Availability | SPARQL endpoint availability check for dblp Knowledge Graph took 0.3316037654876709s
Availability | VoID file availability check for dblp Knowledge Graph took 0.00032806396484375s
Extra | Recovery of all triples for dblp Knowledge Graph took 56.350592851638794s
Performance | Total latancy measurement for dblp Knowledge Graph took 0.7513034343719482s
Amount of data | Number of triples check for dblp Knowledge Graph took 0.12258601188659668s
Interoperability | New terms check for dblp Knowledge Graph took 2.4206302165985107s
Versatility | Languages check for dblp Knowledge Graph took 32.983909606933594s
Interpretability | Number of blank nodes check for dblp Knowledge Graph took 3.2592287063598633s
Interpretability | RDF structures check for dblp Knowledge Graph took 0.15248370170593262s
Versatility | Serialization formats check for dblp Knowledge Graph took 0.1562333106994629s
Availability | RDF dump link check for dblp Knowledge Graph took 0.13898444175720215s
License | MR license check for dblp Knowledge Graph took 0.1831226348876953s
License | HR license check for dblp Knowledge Graph took 30.145959615707397s
Amount of data | Number of property check for dblp Knowledge Graph took 0.187363862991333s
Understandability | Number of label check for dblp Knowledge Graph took 1.2885527610778809s
Understandability | URI regex check for dblp Knowledge Graph took 0.30019569396972656s
Understandability | Vocabs check for dblp Knowledge Graph took 0.18627381324768066s
Verifiability | Authors check for dblp Knowledge Graph took 0.1882157325744629s
Verifiability | Publishers check for dblp Knowledge Graph took 0.19268345832824707s
Performance | Throughput check for dblp Knowledge Graph took 11.320676803588867s
Amount of data | Check the number of entities for dblp Knowledge Graph took 7.557868957519531e-05s
Verifiability | Contribs. check for dblp Knowledge Graph took 0.17626523971557617s
Interlinking | sameAs chians check for dblp Knowledge Graph took 0.2202928066253662s
Interlinking | skos check for dblp Knowledge Graph took 0.17776918411254883s
Interlinking | skos check for dblp Knowledge Graph took 0.15290141105651855s
Timeliness | dataset update frequency check for dblp Knowledge Graph took 0.1387782096862793s
Currency | Creation date check for dblp Knowledge Graph took 0.290208101272583s
Currency | Modification date check for dblp Knowledge Graph took 0.29558491706848145s
Rep.Conc. | URIs length for dblp Knowledge Graph took 38.26551938056946s
Interoperability | New vocabularies check for dblp Knowledge Graph took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for dblp Knowledge Graph took 0.15772128105163574s
Accuracy | Check Functional Property for dblp Knowledge Graph took 0.12786436080932617s
Accuracy | Check Inverse Functional Property for dblp Knowledge Graph took 0.14897418022155762s
Accuracy | Check Empty annotation labels for dblp Knowledge Graph took 19.43474555015564s
Accuracy | Check White space in annotation for dblp Knowledge Graph took 3.1268434524536133s
Accuracy | Check Datatype consistency for dblp Knowledge Graph took 6.091745853424072s
Consistency | Disjoint class check for dblp Knowledge Graph took 0.1502852439880371s
Consistency | Check Misplaced properties for dblp Knowledge Graph took 0.2838454246520996s
Consistency | Check Ontology hijacking for dblp Knowledge Graph took 18.364433765411377s
Consistency | Check Invalid usage of undefined classes for dblp Knowledge Graph took 17150.79744887352s
Consistency | Check Invalid usage of undefined properties for dblp Knowledge Graph took 10.574688196182251s
Conciseness | Check Extensional conciseness for dblp Knowledge Graph took 2.6892850399017334s
Conciseness | Check Intensional conciseness for dblp Knowledge Graph took 0.17960286140441895s
Security | Sign check for dblp Knowledge Graph took 0.14316320419311523s
Availability | Check URIs Dereferenciability for dblp Knowledge Graph took 1.763460636138916s
Completeness | Calculation of interlinking completeness for dblp Knowledge Graph took 1.9618422985076904s
Reputation | Calculation of the PageRank for dblp Knowledge Graph took 0.021006107330322266s
Interlinking | Calculation of Degree of Connection for dblp Knowledge Graph took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for dblp Knowledge Graph took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for dblp Knowledge Graph took 4.2438507080078125e-05s
Interoperability | Check the re-using of existing vocabs for dblp Knowledge Graph took 1.9073486328125e-06s
Believability | Calculation of trust value for dblp Knowledge Graph took 7.152557373046875e-06s
INFO | --- Analysis for dblp-kg took 17453.366618156433s
Availability | SPARQL endpoint availability check for dbnary took 0.30159568786621094s
Availability | VoID file availability check for dbnary took 0.0005645751953125s
Extra | Recovery of all triples for dbnary took 2.323049783706665s
Performance | Total latancy measurement for dbnary took 0.3891732692718506s
Amount of data | Number of triples check for dbnary took 1.2531137466430664s
Interoperability | New terms check for dbnary took 3.6566550731658936s
Versatility | Languages check for dbnary took 61.20466637611389s
Interpretability | Number of blank nodes check for dbnary took 4.787197828292847s
Security | Check HTTPS for dbnary took 0.19061803817749023s
Interpretability | RDF structures check for dbnary took 0.1488475799560547s
Versatility | Serialization formats check for dbnary took 0.2598085403442383s
Availability | RDF dump link check for dbnary took 0.1042623519897461s
License | MR license check for dbnary took 0.1020517349243164s
License | HR license check for dbnary took 60.427703857421875s
Amount of data | Number of property check for dbnary took 0.09644198417663574s
Understandability | Number of label check for dbnary took 1.053971767425537s
Understandability | URI regex check for dbnary took 0.18509650230407715s
Understandability | Vocabs check for dbnary took 0.3199284076690674s
Verifiability | Authors check for dbnary took 0.07148456573486328s
Verifiability | Publishers check for dbnary took 0.06970667839050293s
Performance | Throughput check for dbnary took 10.44706678390503s
Amount of data | Check the number of entities for dbnary took 0.00015664100646972656s
Verifiability | Contribs. check for dbnary took 0.06585407257080078s
Interlinking | sameAs chians check for dbnary took 0.10025978088378906s
Interlinking | skos check for dbnary took 0.4889984130859375s
Interlinking | skos check for dbnary took 0.06695342063903809s
Timeliness | dataset update frequency check for dbnary took 0.4015688896179199s
Currency | Creation date check for dbnary took 0.15883994102478027s
Currency | Modification date check for dbnary took 0.16254186630249023s
Rep.Conc. | URIs length for dbnary took 12.31015944480896s
Interoperability | New vocabularies check for dbnary took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for dbnary took 0.1555478572845459s
Accuracy | Check Functional Property for dbnary took 0.13770532608032227s
Accuracy | Check Inverse Functional Property for dbnary took 0.12379765510559082s
Accuracy | Check Empty annotation labels for dbnary took 0.6561193466186523s
Accuracy | Check White space in annotation for dbnary took 0.030709028244018555s
Accuracy | Check Datatype consistency for dbnary took 0.027915477752685547s
Consistency | Disjoint class check for dbnary took 0.10066080093383789s
Consistency | Check Misplaced properties for dbnary took 9.131901264190674s
Consistency | Misplaced classes for dbnary took 0.23363447189331055s
Consistency | Check Ontology hijacking for dbnary took 1.8092103004455566s
Consistency | Check Invalid usage of undefined classes for dbnary took 1.3432912826538086s
Consistency | Check Invalid usage of undefined properties for dbnary took 10.312431573867798s
Conciseness | Check Extensional conciseness for dbnary took 0.03737449645996094s
Conciseness | Check Intensional conciseness for dbnary took 0.18068456649780273s
Security | Sign check for dbnary took 0.1083364486694336s
Availability | Check URIs Dereferenciability for dbnary took 5.509713888168335s
Completeness | Calculation of interlinking completeness for dbnary took 0.683110237121582s
Reputation | Calculation of the PageRank for dbnary took 0.021178245544433594s
Interlinking | Calculation of Degree of Connection for dbnary took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for dbnary took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for dbnary took 5.626678466796875e-05s
Interoperability | Check the re-using of existing vocabs for dbnary took 1.430511474609375e-06s
Believability | Calculation of trust value for dbnary took 8.106231689453125e-06s
INFO | --- Analysis for dbnary took 305.2039885520935s
Availability | SPARQL endpoint availability check for DBpedia took 0.673938512802124s
Availability | VoID file availability check for DBpedia took 0.0006020069122314453s
Extra | Recovery of all triples for DBpedia took 7.561211347579956s
Performance | Total latancy measurement for DBpedia took 1.0876038074493408s
Amount of data | Number of triples check for DBpedia took 1.4356472492218018s
Interoperability | New terms check for DBpedia took 8.110818147659302s
Versatility | Languages check for DBpedia took 32.14376139640808s
Interpretability | Number of blank nodes check for DBpedia took 0.19242620468139648s
Security | Check HTTPS for DBpedia took 0.13233399391174316s
Interpretability | RDF structures check for DBpedia took 0.30255746841430664s
Versatility | Serialization formats check for DBpedia took 0.25403451919555664s
Availability | RDF dump link check for DBpedia took 0.34426379203796387s
License | MR license check for DBpedia took 1.1607420444488525s
License | HR license check for DBpedia took 30.637775897979736s
Amount of data | Number of property check for DBpedia took 0.2427971363067627s
Understandability | Number of label check for DBpedia took 3.0422730445861816s
Understandability | URI regex check for DBpedia took 0.6878478527069092s
Understandability | Vocabs check for DBpedia took 0.3212153911590576s
Verifiability | Authors check for DBpedia took 0.2222142219543457s
Verifiability | Publishers check for DBpedia took 0.2682831287384033s
Performance | Throughput check for DBpedia took 10.42497730255127s
Amount of data | Check the number of entities for DBpedia took 3.170967102050781e-05s
Verifiability | Contribs. check for DBpedia took 0.47547459602355957s
Interlinking | sameAs chians check for DBpedia took 2.976029396057129s
Interlinking | skos check for DBpedia took 0.4159221649169922s
Interlinking | skos check for DBpedia took 0.19077658653259277s
Timeliness | dataset update frequency check for DBpedia took 0.20569872856140137s
Currency | Creation date check for DBpedia took 0.45229458808898926s
Currency | Modification date check for DBpedia took 0.4625117778778076s
Rep.Conc. | URIs length for DBpedia took 41.471657276153564s
Interoperability | New vocabularies check for DBpedia took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for DBpedia took 0.2299654483795166s
Accuracy | Check Functional Property for DBpedia took 0.23665547370910645s
Accuracy | Check Inverse Functional Property for DBpedia took 0.21222519874572754s
Accuracy | Check Empty annotation labels for DBpedia took 1.3957819938659668s
Accuracy | Check White space in annotation for DBpedia took 0.03137803077697754s
Accuracy | Check Datatype consistency for DBpedia took 0.02889084815979004s
Consistency | Disjoint class check for DBpedia took 0.2138063907623291s
Consistency | Check Misplaced properties for DBpedia took 34.30725860595703s
Consistency | Misplaced classes for DBpedia took 0.7879698276519775s
Consistency | Check Ontology hijacking for DBpedia took 4.2706499099731445s
Consistency | Check Invalid usage of undefined classes for DBpedia took 1.1749393939971924s
Consistency | Check Invalid usage of undefined properties for DBpedia took 1.7880642414093018s
Conciseness | Check Extensional conciseness for DBpedia took 0.03112626075744629s
Conciseness | Check Intensional conciseness for DBpedia took 4.770241022109985s
Security | Sign check for DBpedia took 0.21651816368103027s
Availability | Check URIs Dereferenciability for DBpedia took 5949.939060211182s
Completeness | Calculation of interlinking completeness for DBpedia took 1.521641731262207s
Reputation | Calculation of the PageRank for DBpedia took 0.021790742874145508s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.0009329319000244141s
Interoperability | Check the re-using of existing vocabs for DBpedia took 1.1920928955078125e-06s
Believability | Calculation of trust value for DBpedia took 5.9604644775390625e-06s
INFO | --- Analysis for dbpedia took 6340.1984078884125s
Availability | SPARQL endpoint availability check for DBpedia abstract corpus took 4.1961669921875e-05s
Availability | VoID file availability check for DBpedia abstract corpus took 0.0007154941558837891s
Completeness | Calculation of interlinking completeness for DBpedia abstract corpus took 0.25035524368286133s
Reputation | Calculation of the PageRank for DBpedia abstract corpus took 0.02077770233154297s
Interlinking | Calculation of Degree of Connection for DBpedia abstract corpus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBpedia abstract corpus took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for DBpedia abstract corpus took 6.961822509765625e-05s
Believability | Calculation of trust value for DBpedia abstract corpus took 1.0967254638671875e-05s
INFO | --- Analysis for dbpedia-abstract-corpus took 8.475765705108643s
Availability | SPARQL endpoint availability check for DBpedia Commons took 20.084856510162354s
Availability | VoID file availability check for DBpedia Commons took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.768362283706665s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.020026445388793945s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 0.0004715919494628906s
Believability | Calculation of trust value for DBpedia Commons took 5.9604644775390625e-06s
INFO | --- Analysis for dbpedia-commons took 53.792049407958984s
Availability | SPARQL endpoint availability check for DBpedia in German took 3.981590270996094e-05s
Availability | VoID file availability check for DBpedia in German took 0.00028395652770996094s
Completeness | Calculation of interlinking completeness for DBpedia in German took 0.2489168643951416s
Reputation | Calculation of the PageRank for DBpedia in German took 0.020278215408325195s
Interlinking | Calculation of Degree of Connection for DBpedia in German took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia in German took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for DBpedia in German took 6.198883056640625e-05s
Believability | Calculation of trust value for DBpedia in German took 6.67572021484375e-06s
INFO | --- Analysis for dbpedia-de took 4.1130690574646s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 10.540335178375244s
Availability | VoID file availability check for DBpedia in Greek took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 0.26531457901000977s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.020402193069458008s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.00019168853759765625s
Believability | Calculation of trust value for DBpedia in Greek took 5.245208740234375e-06s
INFO | --- Analysis for dbpedia-el took 44.428128480911255s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 8.409932851791382s
Availability | VoID file availability check for DBpedia in Spanish took 0.0003540515899658203s
Extra | Recovery of all triples for DBpedia in Spanish took 12.999730825424194s
Performance | Total latancy measurement for DBpedia in Spanish took 10.778813600540161s
Amount of data | Number of triples check for DBpedia in Spanish took 3.807025671005249s
Interoperability | New terms check for DBpedia in Spanish took 5.415579080581665s
Versatility | Languages check for DBpedia in Spanish took 31.517533779144287s
Interpretability | Number of blank nodes check for DBpedia in Spanish took 0.4251558780670166s
Security | Check HTTPS for DBpedia in Spanish took 0.18568086624145508s
Interpretability | RDF structures check for DBpedia in Spanish took 1.2267000675201416s
Versatility | Serialization formats check for DBpedia in Spanish took 0.6696815490722656s
Availability | RDF dump link check for DBpedia in Spanish took 0.4295470714569092s
License | MR license check for DBpedia in Spanish took 1.14097261428833s
License | HR license check for DBpedia in Spanish took 30.383278369903564s
Amount of data | Number of property check for DBpedia in Spanish took 0.5091617107391357s
Understandability | Number of label check for DBpedia in Spanish took 2.330029249191284s
Understandability | URI regex check for DBpedia in Spanish took 0.8151776790618896s
Understandability | Vocabs check for DBpedia in Spanish took 0.550626277923584s
Verifiability | Authors check for DBpedia in Spanish took 0.3305530548095703s
Verifiability | Publishers check for DBpedia in Spanish took 0.334397554397583s
Performance | Throughput check for DBpedia in Spanish took 11.13913869857788s
Amount of data | Check the number of entities for DBpedia in Spanish took 7.128715515136719e-05s
Verifiability | Contribs. check for DBpedia in Spanish took 0.33684539794921875s
Interlinking | sameAs chians check for DBpedia in Spanish took 1.5119967460632324s
Interlinking | skos check for DBpedia in Spanish took 0.5255954265594482s
Interlinking | skos check for DBpedia in Spanish took 0.27410459518432617s
Timeliness | dataset update frequency check for DBpedia in Spanish took 0.4919929504394531s
Currency | Creation date check for DBpedia in Spanish took 0.6811501979827881s
Currency | Modification date check for DBpedia in Spanish took 0.6783578395843506s
Rep.Conc. | URIs length for DBpedia in Spanish took 8.227159976959229s
Interoperability | New vocabularies check for DBpedia in Spanish took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Spanish took 0.35387635231018066s
Accuracy | Check Functional Property for DBpedia in Spanish took 0.5661101341247559s
Accuracy | Check Inverse Functional Property for DBpedia in Spanish took 0.5187623500823975s
Accuracy | Check Empty annotation labels for DBpedia in Spanish took 1.3851332664489746s
Accuracy | Check White space in annotation for DBpedia in Spanish took 0.03119182586669922s
Accuracy | Check Datatype consistency for DBpedia in Spanish took 0.027178287506103516s
Consistency | Disjoint class check for DBpedia in Spanish took 0.3371012210845947s
Consistency | Check Misplaced properties for DBpedia in Spanish took 8.713496446609497s
Consistency | Misplaced classes for DBpedia in Spanish took 1.3290624618530273s
Consistency | Check Ontology hijacking for DBpedia in Spanish took 2.4065065383911133s
Consistency | Check Invalid usage of undefined classes for DBpedia in Spanish took 1.1369802951812744s
Consistency | Check Invalid usage of undefined properties for DBpedia in Spanish took 7.064001560211182s
Conciseness | Check Extensional conciseness for DBpedia in Spanish took 0.03306746482849121s
Conciseness | Check Intensional conciseness for DBpedia in Spanish took 1.702751636505127s
Security | Sign check for DBpedia in Spanish took 0.4343695640563965s
Availability | Check URIs Dereferenciability for DBpedia in Spanish took 6.267076015472412s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 0.33976221084594727s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.02056717872619629s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 9.679794311523438e-05s
Interoperability | Check the re-using of existing vocabs for DBpedia in Spanish took 9.5367431640625e-07s
Believability | Calculation of trust value for DBpedia in Spanish took 5.245208740234375e-06s
INFO | --- Analysis for dbpedia-es took 660.304544210434s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 1.1932573318481445s
Availability | VoID file availability check for DBpedia in Basque took 0.00054931640625s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.2391657829284668s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.019902467727661133s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 2.8848648071289062e-05s
Believability | Calculation of trust value for DBpedia in Basque took 4.76837158203125e-06s
INFO | --- Analysis for dbpedia-eu took 8.480352878570557s
Availability | SPARQL endpoint availability check for DBpedia in French took 30.666715621948242s
Availability | VoID file availability check for DBpedia in French took 0.0009670257568359375s
Completeness | Calculation of interlinking completeness for DBpedia in French took 0.7925369739532471s
Reputation | Calculation of the PageRank for DBpedia in French took 0.021249771118164062s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 0.00010061264038085938s
Believability | Calculation of trust value for DBpedia in French took 9.5367431640625e-06s
INFO | --- Analysis for dbpedia-fr took 707.9989449977875s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 4.529552698135376s
Availability | VoID file availability check for DBpedia in Japanese took 4.031728267669678s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 0.24338507652282715s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.025065183639526367s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 0.00010371208190917969s
Interoperability | Check the re-using of existing vocabs for DBpedia in Japanese took 1.430511474609375e-06s
Believability | Calculation of trust value for DBpedia in Japanese took 5.245208740234375e-06s
INFO | --- Analysis for dbpedia-ja took 38.03133535385132s
Availability | SPARQL endpoint availability check for dbpedia lite took 4.3392181396484375e-05s
Availability | VoID file availability check for dbpedia lite took 0.0006566047668457031s
Completeness | Calculation of interlinking completeness for dbpedia lite took 0.24651265144348145s
Reputation | Calculation of the PageRank for dbpedia lite took 0.020865917205810547s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for dbpedia lite took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 0.00010204315185546875s
Believability | Calculation of trust value for dbpedia lite took 3.814697265625e-06s
INFO | --- Analysis for dbpedia-lite took 22.739644527435303s
Availability | SPARQL endpoint availability check for DBpedia-Live took 3.8623809814453125e-05s
Availability | VoID file availability check for DBpedia-Live took 0.0002269744873046875s
Completeness | Calculation of interlinking completeness for DBpedia-Live took 0.6896247863769531s
Reputation | Calculation of the PageRank for DBpedia-Live took 0.02056574821472168s
Interlinking | Calculation of Degree of Connection for DBpedia-Live took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia-Live took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for DBpedia-Live took 3.123283386230469e-05s
Believability | Calculation of trust value for DBpedia-Live took 7.62939453125e-06s
INFO | --- Analysis for dbpedia-live took 4.140063762664795s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 0.2579350471496582s
Availability | VoID file availability check for DBpedia in Dutch took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 0.6861872673034668s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.022003650665283203s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.00017261505126953125s
Believability | Calculation of trust value for DBpedia in Dutch took 5.7220458984375e-06s
INFO | --- Analysis for dbpedia-nl took 3.468679904937744s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 30.147720098495483s
Availability | VoID file availability check for DBpedia in Portuguese took 0.0006852149963378906s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 0.25507569313049316s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.020525455474853516s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 8.130073547363281e-05s
Believability | Calculation of trust value for DBpedia in Portuguese took 5.4836273193359375e-06s
INFO | --- Analysis for dbpedia-pt took 72.51259660720825s
Availability | SPARQL endpoint availability check for DBpedia Spotlight took 3.933906555175781e-05s
Availability | VoID file availability check for DBpedia Spotlight took 0.0002799034118652344s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight took 0.24970602989196777s
Reputation | Calculation of the PageRank for DBpedia Spotlight took 0.020636796951293945s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight took 3.2901763916015625e-05s
Believability | Calculation of trust value for DBpedia Spotlight took 6.4373016357421875e-06s
INFO | --- Analysis for dbpedia-spotlight took 3.237630844116211s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 4.220008850097656e-05s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 0.0006422996520996094s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 0.25160694122314453s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.02810192108154297s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight NIF NER Corpus took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight NIF NER Corpus took 0.0011382102966308594s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight NIF NER Corpus took 8.082389831542969e-05s
Believability | Calculation of trust value for DBpedia Spotlight NIF NER Corpus took 8.106231689453125e-06s
INFO | --- Analysis for dbpedia-spotlight-nif-ner-corpus took 13.66193699836731s
Availability | SPARQL endpoint availability check for DBpedia Wikidata took 4.4345855712890625e-05s
Availability | VoID file availability check for DBpedia Wikidata took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for DBpedia Wikidata took 0.24959301948547363s
Reputation | Calculation of the PageRank for DBpedia Wikidata took 0.02014923095703125s
Interlinking | Calculation of Degree of Connection for DBpedia Wikidata took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for DBpedia Wikidata took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for DBpedia Wikidata took 2.9087066650390625e-05s
Believability | Calculation of trust value for DBpedia Wikidata took 6.9141387939453125e-06s
INFO | --- Analysis for dbpedia-wikidata took 3.624178171157837s
Availability | SPARQL endpoint availability check for DBpedia took 4.029273986816406e-05s
Availability | VoID file availability check for DBpedia took 0.00022077560424804688s
Completeness | Calculation of interlinking completeness for DBpedia took 0.2500324249267578s
Reputation | Calculation of the PageRank for DBpedia took 0.020411252975463867s
Interlinking | Calculation of Degree of Connection for DBpedia took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for DBpedia took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for DBpedia took 2.765655517578125e-05s
Believability | Calculation of trust value for DBpedia took 5.7220458984375e-06s
INFO | --- Analysis for dbpedia_ took 2.8049356937408447s
Availability | SPARQL endpoint availability check for DBTropes took 4.3392181396484375e-05s
Availability | VoID file availability check for DBTropes took 0.0005791187286376953s
Completeness | Calculation of interlinking completeness for DBTropes took 0.24657893180847168s
Reputation | Calculation of the PageRank for DBTropes took 0.02043008804321289s
Interlinking | Calculation of Degree of Connection for DBTropes took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for DBTropes took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for DBTropes took 9.322166442871094e-05s
Believability | Calculation of trust value for DBTropes took 6.4373016357421875e-06s
INFO | --- Analysis for dbtropes took 3.2371327877044678s
Availability | SPARQL endpoint availability check for DBTune – Music-Related RDF took 4.029273986816406e-05s
Availability | VoID file availability check for DBTune – Music-Related RDF took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for DBTune – Music-Related RDF took 0.2704606056213379s
Reputation | Calculation of the PageRank for DBTune – Music-Related RDF took 0.020519018173217773s
Interlinking | Calculation of Degree of Connection for DBTune – Music-Related RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DBTune – Music-Related RDF took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for DBTune – Music-Related RDF took 3.743171691894531e-05s
Believability | Calculation of trust value for DBTune – Music-Related RDF took 1.71661376953125e-05s
INFO | --- Analysis for dbtune took 2.826650619506836s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 4.38690185546875e-05s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.0006644725799560547s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 0.24718832969665527s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.020417451858520508s
Interlinking | Calculation of Degree of Connection for DBTune.org Artists: Last.fm took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DBTune.org Artists: Last.fm took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 5.9604644775390625e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 6.9141387939453125e-06s
INFO | --- Analysis for dbtune-artists-last-fm took 8.525060892105103s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 4.172325134277344e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.0006937980651855469s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 0.40384674072265625s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.020121335983276367s
Interlinking | Calculation of Degree of Connection for DBTune.org AudioScrobbler RDF Service took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBTune.org AudioScrobbler RDF Service took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for DBTune.org AudioScrobbler RDF Service took 3.218650817871094e-05s
Believability | Calculation of trust value for DBTune.org AudioScrobbler RDF Service took 7.152557373046875e-06s
INFO | --- Analysis for dbtune-audioscrobbler took 6.235239744186401s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 6.718206405639648s
Availability | VoID file availability check for DBTune.org/classical took 0.0006954669952392578s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.8510382175445557s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.02199268341064453s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.000980377197265625s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 9.5367431640625e-05s
Believability | Calculation of trust value for DBTune.org/classical took 6.9141387939453125e-06s
INFO | --- Analysis for dbtune-classical took 22.589208602905273s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 8.148452758789062s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.0006468296051025391s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.4591391086578369s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.020969390869140625s
Interlinking | Calculation of Degree of Connection for DBTune.org John Peel sessions RDF server took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DBTune.org John Peel sessions RDF server took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 7.462501525878906e-05s
Believability | Calculation of trust value for DBTune.org John Peel sessions RDF server took 6.198883056640625e-06s
INFO | --- Analysis for dbtune-john-peel-sessions took 29.90382671356201s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 7.3830084800720215s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.0006387233734130859s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.8333451747894287s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.020676374435424805s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 6.818771362304688e-05s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 7.62939453125e-06s
INFO | --- Analysis for dbtune-magnatune took 27.296637296676636s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 7.649142026901245s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.0006799697875976562s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 0.4927644729614258s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.020708084106445312s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.00011324882507324219s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 7.867813110351562e-06s
INFO | --- Analysis for dbtune-musicbrainz took 24.683786392211914s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 7.957977533340454s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 0.40694332122802734s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.02070331573486328s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.0008060932159423828s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 5.364418029785156e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 7.152557373046875e-06s
INFO | --- Analysis for dbtune-myspace took 20.85402750968933s
Availability | SPARQL endpoint availability check for OpenUpLabs DCLG took 4.38690185546875e-05s
Availability | VoID file availability check for OpenUpLabs DCLG took 0.00032067298889160156s
Completeness | Calculation of interlinking completeness for OpenUpLabs DCLG took 0.2720341682434082s
Reputation | Calculation of the PageRank for OpenUpLabs DCLG took 0.02031731605529785s
Interlinking | Calculation of Degree of Connection for OpenUpLabs DCLG took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OpenUpLabs DCLG took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs DCLG took 2.9802322387695312e-05s
Believability | Calculation of trust value for OpenUpLabs DCLG took 6.9141387939453125e-06s
INFO | --- Analysis for dclg-openuplabs took 3.8582921028137207s
Availability | SPARQL endpoint availability check for data.dcs took 4.076957702636719e-05s
Availability | VoID file availability check for data.dcs took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for data.dcs took 0.26404881477355957s
Reputation | Calculation of the PageRank for data.dcs took 0.020253896713256836s
Interlinking | Calculation of Degree of Connection for data.dcs took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for data.dcs took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for data.dcs took 6.389617919921875e-05s
Believability | Calculation of trust value for data.dcs took 5.4836273193359375e-06s
INFO | --- Analysis for dcs-sheffield took 3.1590468883514404s
Availability | SPARQL endpoint availability check for Germany - Bundesministerium der Finanzen - Budget took 3.981590270996094e-05s
Availability | VoID file availability check for Germany - Bundesministerium der Finanzen - Budget took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for Germany - Bundesministerium der Finanzen - Budget took 0.3905770778656006s
Reputation | Calculation of the PageRank for Germany - Bundesministerium der Finanzen - Budget took 0.020447969436645508s
Interlinking | Calculation of Degree of Connection for Germany - Bundesministerium der Finanzen - Budget took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Germany - Bundesministerium der Finanzen - Budget took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Germany - Bundesministerium der Finanzen - Budget took 3.0279159545898438e-05s
Believability | Calculation of trust value for Germany - Bundesministerium der Finanzen - Budget took 6.9141387939453125e-06s
INFO | --- Analysis for de-budget took 3.4926247596740723s
Availability | SPARQL endpoint availability check for de-gaap-ontology-lexicon took 4.2438507080078125e-05s
Availability | VoID file availability check for de-gaap-ontology-lexicon took 0.0005509853363037109s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 0.2765498161315918s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.020411968231201172s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 3.790855407714844e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 6.9141387939453125e-06s
INFO | --- Analysis for de-gaap-ontology-lexicon took 4.307485580444336s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 4.220008850097656e-05s
Availability | VoID file availability check for Debian Package Tracking System took 0.0006320476531982422s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 0.2676992416381836s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.020627975463867188s
Interlinking | Calculation of Degree of Connection for Debian Package Tracking System took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Debian Package Tracking System took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 4.5299530029296875e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 6.9141387939453125e-06s
INFO | --- Analysis for debian-package-tracking-system took 4.446488380432129s
Availability | SPARQL endpoint availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 3.9577484130859375e-05s
Availability | VoID file availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.00023317337036132812s
Completeness | Calculation of interlinking completeness for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.28000903129577637s
Reputation | Calculation of the PageRank for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.020598649978637695s
Interlinking | Calculation of Degree of Connection for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 3.075599670410156e-05s
Believability | Calculation of trust value for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 6.198883056640625e-06s
INFO | --- Analysis for delimitacion-territorial-juntas-administrativas-zaragoza took 2.905057191848755s
Availability | SPARQL endpoint availability check for Demografie took 3.886222839355469e-05s
Availability | VoID file availability check for Demografie took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for Demografie took 0.260939359664917s
Reputation | Calculation of the PageRank for Demografie took 0.020516633987426758s
Interlinking | Calculation of Degree of Connection for Demografie took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Demografie took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Demografie took 2.9802322387695312e-05s
Believability | Calculation of trust value for Demografie took 5.7220458984375e-06s
INFO | --- Analysis for demografie took 2.81919527053833s
Availability | SPARQL endpoint availability check for Projeto Desaparecidos took 4.2438507080078125e-05s
Availability | VoID file availability check for Projeto Desaparecidos took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for Projeto Desaparecidos took 0.2614939212799072s
Reputation | Calculation of the PageRank for Projeto Desaparecidos took 0.02184748649597168s
Interlinking | Calculation of Degree of Connection for Projeto Desaparecidos took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Projeto Desaparecidos took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Projeto Desaparecidos took 3.528594970703125e-05s
Believability | Calculation of trust value for Projeto Desaparecidos took 5.4836273193359375e-06s
INFO | --- Analysis for desaparecidos took 3.0766794681549072s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 4.506111145019531e-05s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 0.26102471351623535s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.02195262908935547s
Interlinking | Calculation of Degree of Connection for Deusto Entrepreneurship: sharing business knowledge took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Deusto Entrepreneurship: sharing business knowledge took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 0.00010824203491210938s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 7.62939453125e-06s
INFO | --- Analysis for deustoentrepreneurship took 3.7020223140716553s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 4.172325134277344e-05s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 0.244981050491333s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.020478010177612305s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.00010156631469726562s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 6.67572021484375e-06s
INFO | --- Analysis for deustotech took 3.4153685569763184s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 1.5376818180084229s
Availability | VoID file availability check for Deutsche Biographie took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 0.2763042449951172s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.02069258689880371s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.0010097026824951172s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 4.792213439941406e-05s
Believability | Calculation of trust value for Deutsche Biographie took 6.67572021484375e-06s
INFO | --- Analysis for deutsche-biographie took 4.347918510437012s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 4.172325134277344e-05s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.00054931640625s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 0.2523937225341797s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.021080493927001953s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 5.459785461425781e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 5.9604644775390625e-06s
INFO | --- Analysis for deutsche-nationalbibliografie-dnb took 6.209819555282593s
Availability | SPARQL endpoint availability check for dev8d took 4.0531158447265625e-05s
Availability | VoID file availability check for dev8d took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for dev8d took 0.23916339874267578s
Reputation | Calculation of the PageRank for dev8d took 0.0203707218170166s
Interlinking | Calculation of Degree of Connection for dev8d took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for dev8d took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for dev8d took 6.532669067382812e-05s
Believability | Calculation of trust value for dev8d took 6.9141387939453125e-06s
INFO | --- Analysis for dev8d took 2.5872414112091064s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 30.27578616142273s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 0.0007307529449462891s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 0.2747151851654053s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.020311832427978516s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Dewey Decimal Classification (DDC) took 4.982948303222656e-05s
Believability | Calculation of trust value for Dewey Decimal Classification (DDC) took 9.5367431640625e-06s
INFO | --- Analysis for dewey_decimal_classification took 93.32887005805969s
Availability | SPARQL endpoint availability check for Distributed Hydrology Soil Vegetation Model took 4.291534423828125e-05s
Availability | VoID file availability check for Distributed Hydrology Soil Vegetation Model took 0.0007090568542480469s
Completeness | Calculation of interlinking completeness for Distributed Hydrology Soil Vegetation Model took 0.24077391624450684s
Reputation | Calculation of the PageRank for Distributed Hydrology Soil Vegetation Model took 0.023278236389160156s
Interlinking | Calculation of Degree of Connection for Distributed Hydrology Soil Vegetation Model took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Distributed Hydrology Soil Vegetation Model took 0.0011000633239746094s
Interlinking | Calculation of Clustering coefficient for Distributed Hydrology Soil Vegetation Model took 5.412101745605469e-05s
Believability | Calculation of trust value for Distributed Hydrology Soil Vegetation Model took 7.152557373046875e-06s
INFO | --- Analysis for DHSVM took 13.735625505447388s
Availability | SPARQL endpoint availability check for Diachronic Ontologies from People's Daily took 3.981590270996094e-05s
Availability | VoID file availability check for Diachronic Ontologies from People's Daily took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for Diachronic Ontologies from People's Daily took 0.24724149703979492s
Reputation | Calculation of the PageRank for Diachronic Ontologies from People's Daily took 0.020489215850830078s
Interlinking | Calculation of Degree of Connection for Diachronic Ontologies from People's Daily took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Diachronic Ontologies from People's Daily took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Diachronic Ontologies from People's Daily took 3.170967102050781e-05s
Believability | Calculation of trust value for Diachronic Ontologies from People's Daily took 5.4836273193359375e-06s
INFO | --- Analysis for diachronic-ontologies-peoples-daily took 2.7522428035736084s
Availability | SPARQL endpoint availability check for Diavgeia took 4.100799560546875e-05s
Availability | VoID file availability check for Diavgeia took 0.0006098747253417969s
Completeness | Calculation of interlinking completeness for Diavgeia took 0.29832959175109863s
Reputation | Calculation of the PageRank for Diavgeia took 0.020340442657470703s
Interlinking | Calculation of Degree of Connection for Diavgeia took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Diavgeia took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 8.440017700195312e-05s
Believability | Calculation of trust value for Diavgeia took 4.291534423828125e-06s
INFO | --- Analysis for diavgeia took 5.2787370681762695s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 4.172325134277344e-05s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.24621796607971191s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.02033233642578125s
Interlinking | Calculation of Degree of Connection for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00011157989501953125s
Believability | Calculation of trust value for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 5.9604644775390625e-06s
INFO | --- Analysis for didactalia took 2.7852160930633545s
Availability | SPARQL endpoint availability check for diigo.feed took 3.981590270996094e-05s
Availability | VoID file availability check for diigo.feed took 0.0002262592315673828s
Completeness | Calculation of interlinking completeness for diigo.feed took 0.24874234199523926s
Reputation | Calculation of the PageRank for diigo.feed took 0.020494461059570312s
Interlinking | Calculation of Degree of Connection for diigo.feed took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for diigo.feed took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for diigo.feed took 2.86102294921875e-05s
Believability | Calculation of trust value for diigo.feed took 6.198883056640625e-06s
INFO | --- Analysis for diigo-feed took 2.7898776531219482s
Availability | SPARQL endpoint availability check for DisGeNET took 0.8481228351593018s
Availability | VoID file availability check for DisGeNET took 0.0005710124969482422s
Completeness | Calculation of interlinking completeness for DisGeNET took 0.2534189224243164s
Reputation | Calculation of the PageRank for DisGeNET took 0.020543813705444336s
Interlinking | Calculation of Degree of Connection for DisGeNET took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DisGeNET took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.00015425682067871094s
Believability | Calculation of trust value for DisGeNET took 1.5497207641601562e-05s
INFO | --- Analysis for disgenet took 8.023590564727783s
Availability | SPARQL endpoint availability check for CAP Italia in RDF took 3.9577484130859375e-05s
Availability | VoID file availability check for CAP Italia in RDF took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for CAP Italia in RDF took 0.25014638900756836s
Reputation | Calculation of the PageRank for CAP Italia in RDF took 0.02046656608581543s
Interlinking | Calculation of Degree of Connection for CAP Italia in RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CAP Italia in RDF took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for CAP Italia in RDF took 3.170967102050781e-05s
Believability | Calculation of trust value for CAP Italia in RDF took 7.152557373046875e-06s
INFO | --- Analysis for disk took 2.9157724380493164s
Availability | SPARQL endpoint availability check for Distritos de Zaragoza took 3.886222839355469e-05s
Availability | VoID file availability check for Distritos de Zaragoza took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for Distritos de Zaragoza took 0.24968171119689941s
Reputation | Calculation of the PageRank for Distritos de Zaragoza took 0.023416996002197266s
Interlinking | Calculation of Degree of Connection for Distritos de Zaragoza took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Distritos de Zaragoza took 0.0014090538024902344s
Interlinking | Calculation of Clustering coefficient for Distritos de Zaragoza took 4.57763671875e-05s
Believability | Calculation of trust value for Distritos de Zaragoza took 7.62939453125e-06s
INFO | --- Analysis for distritos-zaragoza took 3.0111372470855713s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 4.7206878662109375e-05s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 0.0007562637329101562s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 0.25928544998168945s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.020438671112060547s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.0007863044738769531s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 3.8623809814453125e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 7.62939453125e-06s
INFO | --- Analysis for dkh-deusto-knowledge-hub took 6.540245056152344s
Availability | SPARQL endpoint availability check for DM2E took 4.291534423828125e-05s
Availability | VoID file availability check for DM2E took 0.000644683837890625s
Completeness | Calculation of interlinking completeness for DM2E took 0.2580404281616211s
Reputation | Calculation of the PageRank for DM2E took 0.020543813705444336s
Interlinking | Calculation of Degree of Connection for DM2E took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for DM2E took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.000110626220703125s
Believability | Calculation of trust value for DM2E took 9.298324584960938e-06s
INFO | --- Analysis for dm2e took 2.937863349914551s
Availability | SPARQL endpoint availability check for DMOZ RDF Dump took 4.076957702636719e-05s
Availability | VoID file availability check for DMOZ RDF Dump took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for DMOZ RDF Dump took 0.250016450881958s
Reputation | Calculation of the PageRank for DMOZ RDF Dump took 0.020326614379882812s
Interlinking | Calculation of Degree of Connection for DMOZ RDF Dump took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DMOZ RDF Dump took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for DMOZ RDF Dump took 3.075599670410156e-05s
Believability | Calculation of trust value for DMOZ RDF Dump took 7.3909759521484375e-06s
INFO | --- Analysis for dmoz_rdf_dump took 2.9090118408203125s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 1.7578630447387695s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.0005538463592529297s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 0.31015634536743164s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.020528316497802734s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.0001544952392578125s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 6.67572021484375e-06s
INFO | --- Analysis for dnb-gemeinsame-normdatei took 10.789482116699219s
Availability | SPARQL endpoint availability check for DOAP Store took 3.9577484130859375e-05s
Availability | VoID file availability check for DOAP Store took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for DOAP Store took 0.2807044982910156s
Reputation | Calculation of the PageRank for DOAP Store took 0.02036905288696289s
Interlinking | Calculation of Degree of Connection for DOAP Store took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DOAP Store took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for DOAP Store took 2.9325485229492188e-05s
Believability | Calculation of trust value for DOAP Store took 5.245208740234375e-06s
INFO | --- Analysis for doap_store took 2.960920572280884s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 4.458427429199219e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 0.0007011890411376953s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 0.30092597007751465s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.020411968231201172s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 6.270408630371094e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 3.814697265625e-06s
INFO | --- Analysis for doi took 8.218996286392212s
Availability | SPARQL endpoint availability check for Driggu Florentino took 4.00543212890625e-05s
Availability | VoID file availability check for Driggu Florentino took 0.0005431175231933594s
Completeness | Calculation of interlinking completeness for Driggu Florentino took 0.2785162925720215s
Reputation | Calculation of the PageRank for Driggu Florentino took 0.0203092098236084s
Interlinking | Calculation of Degree of Connection for Driggu Florentino took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Driggu Florentino took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Driggu Florentino took 3.0279159545898438e-05s
Believability | Calculation of trust value for Driggu Florentino took 5.9604644775390625e-06s
INFO | --- Analysis for Driggu took 3.6279561519622803s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 7.460410118103027s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.0007503032684326172s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 0.42559123039245605s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.020664453506469727s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 3.647804260253906e-05s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 8.344650268554688e-06s
INFO | --- Analysis for drug-data-hifm took 37.94335126876831s
Availability | SPARQL endpoint availability check for dspace took 4.00543212890625e-05s
Availability | VoID file availability check for dspace took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for dspace took 0.3327016830444336s
Reputation | Calculation of the PageRank for dspace took 0.02025747299194336s
Interlinking | Calculation of Degree of Connection for dspace took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for dspace took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for dspace took 2.9802322387695312e-05s
Believability | Calculation of trust value for dspace took 7.152557373046875e-06s
INFO | --- Analysis for dspace took 3.5776333808898926s
Availability | SPARQL endpoint availability check for DURAARK - Linked Building Data took 4.458427429199219e-05s
Availability | VoID file availability check for DURAARK - Linked Building Data took 0.0002903938293457031s
Completeness | Calculation of interlinking completeness for DURAARK - Linked Building Data took 0.28391265869140625s
Reputation | Calculation of the PageRank for DURAARK - Linked Building Data took 0.020691394805908203s
Interlinking | Calculation of Degree of Connection for DURAARK - Linked Building Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DURAARK - Linked Building Data took 0.0008463859558105469s
Interlinking | Calculation of Clustering coefficient for DURAARK - Linked Building Data took 3.0279159545898438e-05s
Believability | Calculation of trust value for DURAARK - Linked Building Data took 7.3909759521484375e-06s
INFO | --- Analysis for duraark-linked-building-data took 3.118997812271118s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 272.09959292411804s
Availability | VoID file availability check for MetaLex Document Server took 0.0006859302520751953s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.2509634494781494s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.020946979522705078s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 4.482269287109375e-05s
Believability | Calculation of trust value for MetaLex Document Server took 6.9141387939453125e-06s
INFO | --- Analysis for dutch-national-regulations-metalex took 557.5363273620605s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 1.5918269157409668s
Availability | VoID file availability check for Dutch Ships and Sailors took 0.0006585121154785156s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 0.6785931587219238s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.020867586135864258s
Interlinking | Calculation of Degree of Connection for Dutch Ships and Sailors took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Dutch Ships and Sailors took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 3.9577484130859375e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 7.3909759521484375e-06s
INFO | --- Analysis for dutch-ships-and-sailors took 13.621899127960205s
Availability | SPARQL endpoint availability check for DWS-Group took 4.3392181396484375e-05s
Availability | VoID file availability check for DWS-Group took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for DWS-Group took 0.6708307266235352s
Reputation | Calculation of the PageRank for DWS-Group took 0.020647525787353516s
Interlinking | Calculation of Degree of Connection for DWS-Group took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DWS-Group took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 0.00010371208190917969s
Believability | Calculation of trust value for DWS-Group took 7.152557373046875e-06s
INFO | --- Analysis for dws-group took 4.525719404220581s
Availability | SPARQL endpoint availability check for E1 - Nuvem dados took 4.291534423828125e-05s
Availability | VoID file availability check for E1 - Nuvem dados took 0.0006184577941894531s
Completeness | Calculation of interlinking completeness for E1 - Nuvem dados took 0.6852302551269531s
Reputation | Calculation of the PageRank for E1 - Nuvem dados took 0.021267414093017578s
Interlinking | Calculation of Degree of Connection for E1 - Nuvem dados took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for E1 - Nuvem dados took 0.0009944438934326172s
Interlinking | Calculation of Clustering coefficient for E1 - Nuvem dados took 4.839897155761719e-05s
Believability | Calculation of trust value for E1 - Nuvem dados took 7.152557373046875e-06s
INFO | --- Analysis for E1 took 5.3845274448394775s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 0.0765678882598877s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 0.6962149143218994s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.02184915542602539s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Alaska Fairbanks took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Alaska Fairbanks took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.00011754035949707031s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i-alaska took 3.3440120220184326s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 0.06290197372436523s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 0.0004401206970214844s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 0.28247714042663574s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.020746469497680664s
Interlinking | Calculation of Degree of Connection for eagle-i @ Clark Atlanta University took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ Clark Atlanta University took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 5.459785461425781e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-cau took 2.4094483852386475s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 0.051412343978881836s
Availability | VoID file availability check for eagle-i @ The City College of New York took 0.00022149085998535156s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.25092101097106934s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.020294904708862305s
Interlinking | Calculation of Degree of Connection for eagle-i @ The City College of New York took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ The City College of New York took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 6.175041198730469e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-ccny-cuny took 2.319584608078003s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 0.058774709701538086s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 0.6801643371582031s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.02039647102355957s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 9.489059448242188e-05s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-cdrewu took 2.724470853805542s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 0.04063010215759277s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 0.000560760498046875s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.24320769309997559s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.02065420150756836s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.0001366138458251953s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 6.67572021484375e-06s
INFO | --- Analysis for eagle-i-dartmouth took 2.377617835998535s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.04140901565551758s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 0.24506402015686035s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.020618677139282227s
Interlinking | Calculation of Degree of Connection for eagle-i @ Florida Agricultural and Mechanical University took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for eagle-i @ Florida Agricultural and Mechanical University took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 8.368492126464844e-05s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-famu took 2.376336097717285s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 0.041002750396728516s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.0004374980926513672s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.24682855606079102s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.020766019821166992s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.00013589859008789062s
Believability | Calculation of trust value for eagle-i @ Harvard University took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i-harvard took 2.3262312412261963s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 0.04023313522338867s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 0.2409987449645996s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.020787954330444336s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Hawai’i at Mānoa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Hawai’i at Mānoa took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.00012612342834472656s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-hawaii took 2.2941203117370605s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 0.04615449905395508s
Availability | VoID file availability check for eagle-i @ Howard University took 0.0006856918334960938s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 0.24371886253356934s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.020714282989501953s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 6.651878356933594e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 5.4836273193359375e-06s
INFO | --- Analysis for eagle-i-howard took 2.365321397781372s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 0.039441585540771484s
Availability | VoID file availability check for eagle-i @ Hunter College took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 0.2621891498565674s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.02055215835571289s
Interlinking | Calculation of Degree of Connection for eagle-i @ Hunter College took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Hunter College took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 6.341934204101562e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-hunter-cuny took 2.34836483001709s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 0.04173111915588379s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 0.28245043754577637s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.020472049713134766s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.00011444091796875s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-jsu took 2.430128574371338s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 0.033286333084106445s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 0.26380133628845215s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.020632505416870117s
Interlinking | Calculation of Degree of Connection for eagle-i @ Meharry Medical College took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Meharry Medical College took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 3.886222839355469e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 8.106231689453125e-06s
INFO | --- Analysis for eagle-i-meharry took 2.4054625034332275s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 0.03910470008850098s
Availability | VoID file availability check for eagle-i @ Montana State University took 0.00043845176696777344s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 0.2427833080291748s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.020737171173095703s
Interlinking | Calculation of Degree of Connection for eagle-i @ Montana State University took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Montana State University took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 9.965896606445312e-05s
Believability | Calculation of trust value for eagle-i @ Montana State University took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-montana took 2.330442190170288s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 0.0393528938293457s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.00042819976806640625s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 0.2437913417816162s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.020230531692504883s
Interlinking | Calculation of Degree of Connection for eagle-i @ Morehouse School of Medicine took 2.9325485229492188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Morehouse School of Medicine took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 9.489059448242188e-05s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 6.67572021484375e-06s
INFO | --- Analysis for eagle-i-msm took 2.3481955528259277s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 0.04022336006164551s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 0.2437593936920166s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.020236968994140625s
Interlinking | Calculation of Degree of Connection for eagle-i @ Oregon Health and Science University took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Oregon Health and Science University took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.00012350082397460938s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 8.344650268554688e-06s
INFO | --- Analysis for eagle-i-ohsu took 2.4056599140167236s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 0.04557538032531738s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.0004284381866455078s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 0.25208258628845215s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.020633935928344727s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 6.413459777832031e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 6.4373016357421875e-06s
INFO | --- Analysis for eagle-i-psm took 2.418287515640259s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 0.046561241149902344s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.0004143714904785156s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 0.24482989311218262s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.020708799362182617s
Interlinking | Calculation of Degree of Connection for eagle-i @ Texas Southern University took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ Texas Southern University took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Texas Southern University took 6.318092346191406e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 5.9604644775390625e-06s
INFO | --- Analysis for eagle-i-tsu took 2.3911197185516357s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 0.0542294979095459s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.00033664703369140625s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 0.24670624732971191s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.02047419548034668s
Interlinking | Calculation of Degree of Connection for eagle-i @ Tuskegee University took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Tuskegee University took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 6.198883056640625e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-tuskegee took 2.417644739151001s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 0.03304648399353027s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 0.24217772483825684s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.02052783966064453s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 9.751319885253906e-05s
Believability | Calculation of trust value for eagle-i @ Universidad Central del Caribe took 5.7220458984375e-06s
INFO | --- Analysis for eagle-i-uccaribe took 2.4247119426727295s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.04141545295715332s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.28871774673461914s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.020504474639892578s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0001232624053955078s
Believability | Calculation of trust value for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.2636184692382812e-05s
INFO | --- Analysis for eagle-i-upr took 2.3911428451538086s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 0.040368080139160156s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 0.28042054176330566s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.020552635192871094s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at El Paso took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at El Paso took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 6.151199340820312e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 8.821487426757812e-06s
INFO | --- Analysis for eagle-i-utep took 2.4160845279693604s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 0.04558992385864258s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 0.0003409385681152344s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 0.2779848575592041s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.020592451095581055s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 6.747245788574219e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 5.4836273193359375e-06s
INFO | --- Analysis for eagle-i-utsa took 2.409151792526245s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 0.17151904106140137s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.0004353523254394531s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 0.24429631233215332s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.02052021026611328s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 9.059906005859375e-05s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 5.4836273193359375e-06s
INFO | --- Analysis for eagle-i-vanderbilt took 2.5279486179351807s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 0.03951215744018555s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.0004620552062988281s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 0.26181507110595703s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.02045607566833496s
Interlinking | Calculation of Degree of Connection for eagle-i @ Xavier University of Louisiana took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Xavier University of Louisiana took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 7.414817810058594e-05s
Believability | Calculation of trust value for eagle-i @ Xavier University of Louisiana took 4.76837158203125e-06s
INFO | --- Analysis for eagle-i-xula took 2.3928987979888916s
Availability | SPARQL endpoint availability check for Emergency situation took 0.788933515548706s
Availability | VoID file availability check for Emergency situation took 0.0005595684051513672s
Completeness | Calculation of interlinking completeness for Emergency situation took 0.2663915157318115s
Reputation | Calculation of the PageRank for Emergency situation took 0.020407915115356445s
Interlinking | Calculation of Degree of Connection for Emergency situation took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Emergency situation took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Emergency situation took 4.744529724121094e-05s
Believability | Calculation of trust value for Emergency situation took 5.9604644775390625e-06s
INFO | --- Analysis for Earthquake took 3.62719988822937s
Availability | SPARQL endpoint availability check for ESO took 0.6076490879058838s
Availability | VoID file availability check for ESO took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for ESO took 0.28258347511291504s
Reputation | Calculation of the PageRank for ESO took 0.02044367790222168s
Interlinking | Calculation of Degree of Connection for ESO took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ESO took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for ESO took 8.106231689453125e-05s
Believability | Calculation of trust value for ESO took 5.7220458984375e-06s
INFO | --- Analysis for Earthquake_case took 3.961984634399414s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 0.3128795623779297s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.00043320655822753906s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 0.24770832061767578s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.020541667938232422s
Interlinking | Calculation of Degree of Connection for European Central Bank (ECB) Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for European Central Bank (ECB) Linked Data took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 0.00010251998901367188s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 3.814697265625e-06s
INFO | --- Analysis for ecb-linked-data took 2.6327176094055176s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 4.4875383377075195s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 0.0006628036499023438s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 0.25704193115234375s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.020633935928344727s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 3.7670135498046875e-05s
Believability | Calculation of trust value for European Central Bank Statistics (PublicData.eu) took 4.5299530029296875e-06s
INFO | --- Analysis for ecb-statistics-linked-data took 10.54110336303711s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 1.8530793190002441s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 0.24927735328674316s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.02059006690979004s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 6.961822509765625e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 6.198883056640625e-06s
INFO | --- Analysis for ecco-tcp-linked-data took 5.943176507949829s
Availability | SPARQL endpoint availability check for ECLAP took 20.627939224243164s
Availability | VoID file availability check for ECLAP took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for ECLAP took 0.2792937755584717s
Reputation | Calculation of the PageRank for ECLAP took 0.020610332489013672s
Interlinking | Calculation of Degree of Connection for ECLAP took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for ECLAP took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for ECLAP took 3.838539123535156e-05s
Believability | Calculation of trust value for ECLAP took 5.4836273193359375e-06s
INFO | --- Analysis for eclap took 53.06682276725769s
Availability | SPARQL endpoint availability check for 《老子》译本传播知识图谱 took 5.459785461425781e-05s
Availability | VoID file availability check for 《老子》译本传播知识图谱 took 0.0005838871002197266s
Completeness | Calculation of interlinking completeness for 《老子》译本传播知识图谱 took 0.2489171028137207s
Reputation | Calculation of the PageRank for 《老子》译本传播知识图谱 took 0.02089238166809082s
Interlinking | Calculation of Degree of Connection for 《老子》译本传播知识图谱 took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for 《老子》译本传播知识图谱 took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for 《老子》译本传播知识图谱 took 1.33514404296875e-05s
Believability | Calculation of trust value for 《老子》译本传播知识图谱 took 5.9604644775390625e-06s
INFO | --- Analysis for ECNU-GISer took 4.140412330627441s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 4.3392181396484375e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.26395702362060547s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.02042245864868164s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 5.3882598876953125e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 6.198883056640625e-06s
INFO | --- Analysis for ecs took 2.590583086013794s
Availability | SPARQL endpoint availability check for Edificios Históricos en Zaragoza took 4.1961669921875e-05s
Availability | VoID file availability check for Edificios Históricos en Zaragoza took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for Edificios Históricos en Zaragoza took 0.2793095111846924s
Reputation | Calculation of the PageRank for Edificios Históricos en Zaragoza took 0.0206146240234375s
Interlinking | Calculation of Degree of Connection for Edificios Históricos en Zaragoza took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Edificios Históricos en Zaragoza took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Edificios Históricos en Zaragoza took 3.147125244140625e-05s
Believability | Calculation of trust value for Edificios Históricos en Zaragoza took 5.7220458984375e-06s
INFO | --- Analysis for edificios-historicos-zaragoza took 2.9206719398498535s
Availability | SPARQL endpoint availability check for Edublogs took 4.100799560546875e-05s
Availability | VoID file availability check for Edublogs took 0.0006098747253417969s
Completeness | Calculation of interlinking completeness for Edublogs took 0.254605770111084s
Reputation | Calculation of the PageRank for Edublogs took 0.02098989486694336s
Interlinking | Calculation of Degree of Connection for Edublogs took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Edublogs took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Edublogs took 0.00010323524475097656s
Believability | Calculation of trust value for Edublogs took 5.245208740234375e-06s
INFO | --- Analysis for edublogs took 3.2705323696136475s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 0.43037891387939453s
Availability | VoID file availability check for education.data.gov.uk took 0.0005941390991210938s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 0.2438962459564209s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.0207369327545166s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 8.893013000488281e-05s
Believability | Calculation of trust value for education.data.gov.uk took 4.76837158203125e-06s
INFO | --- Analysis for education-data-gov-uk took 4.1472578048706055s
Availability | SPARQL endpoint availability check for OpenUpLabs Education took 4.100799560546875e-05s
Availability | VoID file availability check for OpenUpLabs Education took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for OpenUpLabs Education took 0.257735013961792s
Reputation | Calculation of the PageRank for OpenUpLabs Education took 0.02074742317199707s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Education took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Education took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Education took 3.361701965332031e-05s
Believability | Calculation of trust value for OpenUpLabs Education took 7.867813110351562e-06s
INFO | --- Analysis for education-openuplabs took 2.7730770111083984s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 392.75854229927063s
Availability | VoID file availability check for Educational programs - SISVU took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 1.4920845031738281s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.021579265594482422s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 6.318092346191406e-05s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 5.602836608886719e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 7.152557373046875e-06s
INFO | --- Analysis for educationalprograms_sisvu took 1325.1427628993988s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 0.9115054607391357s
Availability | VoID file availability check for European Environment Agency Published Products took 0.0005929470062255859s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 0.6815602779388428s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.02096724510192871s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 4.982948303222656e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 5.4836273193359375e-06s
INFO | --- Analysis for eea took 9.90341854095459s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 0.5225274562835693s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 0.6797072887420654s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.020599365234375s
Interlinking | Calculation of Degree of Connection for EEA Reporting Obligations Database took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EEA Reporting Obligations Database took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 5.3882598876953125e-05s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 5.0067901611328125e-06s
INFO | --- Analysis for eea-rod took 7.295568227767944s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 0.16542744636535645s
Availability | VoID file availability check for EEA Vocabularies took 0.0005922317504882812s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 0.24413847923278809s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.02059197425842285s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 8.249282836914062e-05s
Believability | Calculation of trust value for EEA Vocabularies took 7.867813110351562e-06s
INFO | --- Analysis for eea-vocabularies took 7.227594614028931s
Availability | SPARQL endpoint availability check for Ege University Linked Open Data took 4.0531158447265625e-05s
Availability | VoID file availability check for Ege University Linked Open Data took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for Ege University Linked Open Data took 0.2996189594268799s
Reputation | Calculation of the PageRank for Ege University Linked Open Data took 0.020528078079223633s
Interlinking | Calculation of Degree of Connection for Ege University Linked Open Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ege University Linked Open Data took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Ege University Linked Open Data took 3.147125244140625e-05s
Believability | Calculation of trust value for Ege University Linked Open Data took 5.9604644775390625e-06s
INFO | --- Analysis for ege-university-linked-open-data took 2.836334228515625s
Availability | SPARQL endpoint availability check for E-Government Ontology took 0.4574117660522461s
Availability | VoID file availability check for E-Government Ontology took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for E-Government Ontology took 0.25785374641418457s
Reputation | Calculation of the PageRank for E-Government Ontology took 0.020711183547973633s
Interlinking | Calculation of Degree of Connection for E-Government Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for E-Government Ontology took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for E-Government Ontology took 3.1948089599609375e-05s
Believability | Calculation of trust value for E-Government Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for EGovOntology took 3.9828367233276367s
Availability | SPARQL endpoint availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5508139133453369s
Availability | VoID file availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0005679130554199219s
Extra | Recovery of all triples for Aragon Interoperable Information Structure EI2A - aragon open data took 2.9549708366394043s
Performance | Total latancy measurement for Aragon Interoperable Information Structure EI2A - aragon open data took 1.3492169380187988s
Amount of data | Number of triples check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.7932744026184082s
Interoperability | New terms check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.9115016460418701s
Versatility | Languages check for Aragon Interoperable Information Structure EI2A - aragon open data took 60.36896896362305s
Interpretability | Number of blank nodes check for Aragon Interoperable Information Structure EI2A - aragon open data took 4.4626145362854s
Interpretability | RDF structures check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.41077733039855957s
Versatility | Serialization formats check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.0798008441925049s
Availability | RDF dump link check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3241090774536133s
License | MR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4057295322418213s
License | HR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 7.040821313858032s
Amount of data | Number of property check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.25247883796691895s
Understandability | Number of label check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4081602096557617s
Understandability | URI regex check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6571002006530762s
Understandability | Vocabs check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.28316760063171387s
Verifiability | Authors check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2582883834838867s
Verifiability | Publishers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.270251989364624s
Performance | Throughput check for Aragon Interoperable Information Structure EI2A - aragon open data took 10.969178438186646s
Amount of data | Check the number of entities for Aragon Interoperable Information Structure EI2A - aragon open data took 8.559226989746094e-05s
Verifiability | Contribs. check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3633894920349121s
Interlinking | sameAs chians check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3059535026550293s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.40186190605163574s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.24332094192504883s
Timeliness | dataset update frequency check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.33167195320129395s
Currency | Creation date check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.6809098720550537s
Currency | Modification date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.26212430000305176s
Rep.Conc. | URIs length for Aragon Interoperable Information Structure EI2A - aragon open data took 6.445594072341919s
Interoperability | New vocabularies check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.28647804260253906s
Accuracy | Check Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.36368727684020996s
Accuracy | Check Inverse Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.34369778633117676s
Accuracy | Check Empty annotation labels for Aragon Interoperable Information Structure EI2A - aragon open data took 1.1505217552185059s
Accuracy | Check White space in annotation for Aragon Interoperable Information Structure EI2A - aragon open data took 0.031166791915893555s
Accuracy | Check Datatype consistency for Aragon Interoperable Information Structure EI2A - aragon open data took 0.028108835220336914s
Consistency | Disjoint class check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2797679901123047s
Consistency | Check Misplaced properties for Aragon Interoperable Information Structure EI2A - aragon open data took 4.707103967666626s
Consistency | Misplaced classes for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5394220352172852s
Consistency | Check Ontology hijacking for Aragon Interoperable Information Structure EI2A - aragon open data took 2.6739180088043213s
Consistency | Check Invalid usage of undefined classes for Aragon Interoperable Information Structure EI2A - aragon open data took 1.1342089176177979s
Consistency | Check Invalid usage of undefined properties for Aragon Interoperable Information Structure EI2A - aragon open data took 5.241614103317261s
Conciseness | Check Extensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.03295278549194336s
Conciseness | Check Intensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4785163402557373s
Security | Sign check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4893512725830078s
Availability | Check URIs Dereferenciability for Aragon Interoperable Information Structure EI2A - aragon open data took 3441.7956483364105s
Completeness | Calculation of interlinking completeness for Aragon Interoperable Information Structure EI2A - aragon open data took 1.385446548461914s
Reputation | Calculation of the PageRank for Aragon Interoperable Information Structure EI2A - aragon open data took 0.021078824996948242s
Interlinking | Calculation of Degree of Connection for Aragon Interoperable Information Structure EI2A - aragon open data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Aragon Interoperable Information Structure EI2A - aragon open data took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Aragon Interoperable Information Structure EI2A - aragon open data took 5.364418029785156e-05s
Interoperability | Check the re-using of existing vocabs for Aragon Interoperable Information Structure EI2A - aragon open data took 1.1920928955078125e-06s
Believability | Calculation of trust value for Aragon Interoperable Information Structure EI2A - aragon open data took 6.4373016357421875e-06s
INFO | --- Analysis for ei2a took 16121.671344518661s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 4.172325134277344e-05s
Availability | VoID file availability check for EIONET RDF Data took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 0.254378080368042s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.019968271255493164s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.00010466575622558594s
Believability | Calculation of trust value for EIONET RDF Data took 4.0531158447265625e-06s
INFO | --- Analysis for eionet-rdf took 3.1716039180755615s
Availability | SPARQL endpoint availability check for Google’s Easter Egg i took 4.267692565917969e-05s
Availability | VoID file availability check for Google’s Easter Egg i took 0.000232696533203125s
Completeness | Calculation of interlinking completeness for Google’s Easter Egg i took 0.2514324188232422s
Reputation | Calculation of the PageRank for Google’s Easter Egg i took 0.02044081687927246s
Interlinking | Calculation of Degree of Connection for Google’s Easter Egg i took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Google’s Easter Egg i took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Google’s Easter Egg i took 3.2901763916015625e-05s
Believability | Calculation of trust value for Google’s Easter Egg i took 5.7220458984375e-06s
INFO | --- Analysis for ElgooG_ took 2.399322509765625s
Availability | SPARQL endpoint availability check for ELTE Digital Institutional Repository (EDIT) took 3.933906555175781e-05s
Availability | VoID file availability check for ELTE Digital Institutional Repository (EDIT) took 0.00023818016052246094s
Completeness | Calculation of interlinking completeness for ELTE Digital Institutional Repository (EDIT) took 0.2711052894592285s
Reputation | Calculation of the PageRank for ELTE Digital Institutional Repository (EDIT) took 0.0203092098236084s
Interlinking | Calculation of Degree of Connection for ELTE Digital Institutional Repository (EDIT) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ELTE Digital Institutional Repository (EDIT) took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for ELTE Digital Institutional Repository (EDIT) took 2.9087066650390625e-05s
Believability | Calculation of trust value for ELTE Digital Institutional Repository (EDIT) took 8.106231689453125e-06s
INFO | --- Analysis for elte-digital-institutional-repository-edit took 2.9160447120666504s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 30.583471536636353s
Availability | VoID file availability check for El Viajero's tourism dataset took 0.0008068084716796875s
Completeness | Calculation of interlinking completeness for El Viajero's tourism dataset took 0.26923108100891113s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.020391464233398438s
Interlinking | Calculation of Degree of Connection for El Viajero's tourism dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for El Viajero's tourism dataset took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 6.985664367675781e-05s
Believability | Calculation of trust value for El Viajero's tourism dataset took 5.4836273193359375e-06s
INFO | --- Analysis for elviajero took 154.60471487045288s
Availability | SPARQL endpoint availability check for EMN took 4.124641418457031e-05s
Availability | VoID file availability check for EMN took 0.00047397613525390625s
Completeness | Calculation of interlinking completeness for EMN took 0.26476478576660156s
Reputation | Calculation of the PageRank for EMN took 0.02045273780822754s
Interlinking | Calculation of Degree of Connection for EMN took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EMN took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for EMN took 3.838539123535156e-05s
Believability | Calculation of trust value for EMN took 5.9604644775390625e-06s
INFO | --- Analysis for emn took 2.4989140033721924s
Availability | SPARQL endpoint availability check for EnAKTing CO2 Emission Dataset took 4.1484832763671875e-05s
Availability | VoID file availability check for EnAKTing CO2 Emission Dataset took 0.0006136894226074219s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 0.287311315536499s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.020379304885864258s
Interlinking | Calculation of Degree of Connection for EnAKTing CO2 Emission Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EnAKTing CO2 Emission Dataset took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 5.1975250244140625e-05s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 5.245208740234375e-06s
INFO | --- Analysis for enakting-co2emission took 2.5217158794403076s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 5.435943603515625e-05s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.00046443939208984375s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 0.24277138710021973s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.020313739776611328s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 3.981590270996094e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 4.5299530029296875e-06s
INFO | --- Analysis for enakting-crime took 2.373936891555786s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 4.0531158447265625e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.0004570484161376953s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 0.27254319190979004s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.020288467407226562s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 3.790855407714844e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 5.0067901611328125e-06s
INFO | --- Analysis for enakting-energy took 2.496645927429199s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 4.076957702636719e-05s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.00044345855712890625s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 0.27555251121520996s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.02088785171508789s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 9.250640869140625e-05s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 5.245208740234375e-06s
INFO | --- Analysis for enakting-mortality took 2.4263696670532227s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 4.315376281738281e-05s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 0.29863715171813965s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.020595312118530273s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 3.743171691894531e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 5.0067901611328125e-06s
INFO | --- Analysis for enakting-nhs took 2.492844343185425s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 4.291534423828125e-05s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.00021839141845703125s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 0.2856159210205078s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.020704030990600586s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 5.412101745605469e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 4.76837158203125e-06s
INFO | --- Analysis for enakting-population took 2.4935498237609863s
Availability | SPARQL endpoint availability check for Enel Shops took 7.176399230957031e-05s
Availability | VoID file availability check for Enel Shops took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for Enel Shops took 0.2690715789794922s
Reputation | Calculation of the PageRank for Enel Shops took 0.020664691925048828s
Interlinking | Calculation of Degree of Connection for Enel Shops took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Enel Shops took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Enel Shops took 3.0517578125e-05s
Believability | Calculation of trust value for Enel Shops took 8.344650268554688e-06s
INFO | --- Analysis for enel-shops took 2.9522523880004883s
Availability | SPARQL endpoint availability check for Energy efficiency assessments and improvements took 4.029273986816406e-05s
Availability | VoID file availability check for Energy efficiency assessments and improvements took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for Energy efficiency assessments and improvements took 0.2562260627746582s
Reputation | Calculation of the PageRank for Energy efficiency assessments and improvements took 0.020468473434448242s
Interlinking | Calculation of Degree of Connection for Energy efficiency assessments and improvements took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Energy efficiency assessments and improvements took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Energy efficiency assessments and improvements took 2.9325485229492188e-05s
Believability | Calculation of trust value for Energy efficiency assessments and improvements took 5.1021575927734375e-05s
INFO | --- Analysis for energy-efficiency took 2.9326283931732178s
Availability | SPARQL endpoint availability check for English Heritage Archaeological Sciences Thesaurus took 3.933906555175781e-05s
Availability | VoID file availability check for English Heritage Archaeological Sciences Thesaurus took 0.00023293495178222656s
Completeness | Calculation of interlinking completeness for English Heritage Archaeological Sciences Thesaurus took 0.2663588523864746s
Reputation | Calculation of the PageRank for English Heritage Archaeological Sciences Thesaurus took 0.020326852798461914s
Interlinking | Calculation of Degree of Connection for English Heritage Archaeological Sciences Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for English Heritage Archaeological Sciences Thesaurus took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for English Heritage Archaeological Sciences Thesaurus took 2.7179718017578125e-05s
Believability | Calculation of trust value for English Heritage Archaeological Sciences Thesaurus took 5.4836273193359375e-06s
INFO | --- Analysis for english-heritage-archaeological-sciences-thesaurus took 2.958037853240967s
Availability | SPARQL endpoint availability check for English Heritage Building Materials Thesaurus took 4.172325134277344e-05s
Availability | VoID file availability check for English Heritage Building Materials Thesaurus took 0.00023102760314941406s
Completeness | Calculation of interlinking completeness for English Heritage Building Materials Thesaurus took 0.2777061462402344s
Reputation | Calculation of the PageRank for English Heritage Building Materials Thesaurus took 0.020476102828979492s
Interlinking | Calculation of Degree of Connection for English Heritage Building Materials Thesaurus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for English Heritage Building Materials Thesaurus took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for English Heritage Building Materials Thesaurus took 2.86102294921875e-05s
Believability | Calculation of trust value for English Heritage Building Materials Thesaurus took 6.198883056640625e-06s
INFO | --- Analysis for english-heritage-building-materials-thesaurus took 2.9833405017852783s
Availability | SPARQL endpoint availability check for English Heritage Components Thesaurus took 3.838539123535156e-05s
Availability | VoID file availability check for English Heritage Components Thesaurus took 0.0002281665802001953s
Completeness | Calculation of interlinking completeness for English Heritage Components Thesaurus took 0.25894927978515625s
Reputation | Calculation of the PageRank for English Heritage Components Thesaurus took 0.02019643783569336s
Interlinking | Calculation of Degree of Connection for English Heritage Components Thesaurus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for English Heritage Components Thesaurus took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for English Heritage Components Thesaurus took 2.9087066650390625e-05s
Believability | Calculation of trust value for English Heritage Components Thesaurus took 5.7220458984375e-06s
INFO | --- Analysis for english-heritage-components-thesaurus took 3.015373945236206s
Availability | SPARQL endpoint availability check for English Heritage Event Types Thesaurus took 3.910064697265625e-05s
Availability | VoID file availability check for English Heritage Event Types Thesaurus took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for English Heritage Event Types Thesaurus took 0.2894108295440674s
Reputation | Calculation of the PageRank for English Heritage Event Types Thesaurus took 0.020308256149291992s
Interlinking | Calculation of Degree of Connection for English Heritage Event Types Thesaurus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for English Heritage Event Types Thesaurus took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for English Heritage Event Types Thesaurus took 2.8371810913085938e-05s
Believability | Calculation of trust value for English Heritage Event Types Thesaurus took 5.7220458984375e-06s
INFO | --- Analysis for english-heritage-event-types-thesaurus took 2.9447269439697266s
Availability | SPARQL endpoint availability check for English Heritage Evidence Thesaurus took 3.910064697265625e-05s
Availability | VoID file availability check for English Heritage Evidence Thesaurus took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for English Heritage Evidence Thesaurus took 0.27221059799194336s
Reputation | Calculation of the PageRank for English Heritage Evidence Thesaurus took 0.020451068878173828s
Interlinking | Calculation of Degree of Connection for English Heritage Evidence Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for English Heritage Evidence Thesaurus took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for English Heritage Evidence Thesaurus took 3.0040740966796875e-05s
Believability | Calculation of trust value for English Heritage Evidence Thesaurus took 6.4373016357421875e-06s
INFO | --- Analysis for english-heritage-evidence-thesaurus took 3.03344988822937s
Availability | SPARQL endpoint availability check for English Heritage Maritime Craft Thesaurus took 3.933906555175781e-05s
Availability | VoID file availability check for English Heritage Maritime Craft Thesaurus took 0.0002269744873046875s
Completeness | Calculation of interlinking completeness for English Heritage Maritime Craft Thesaurus took 0.2747213840484619s
Reputation | Calculation of the PageRank for English Heritage Maritime Craft Thesaurus took 0.020292282104492188s
Interlinking | Calculation of Degree of Connection for English Heritage Maritime Craft Thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for English Heritage Maritime Craft Thesaurus took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for English Heritage Maritime Craft Thesaurus took 2.8133392333984375e-05s
Believability | Calculation of trust value for English Heritage Maritime Craft Thesaurus took 5.7220458984375e-06s
INFO | --- Analysis for english-heritage-maritime-craft-thesaurus took 2.9746885299682617s
Availability | SPARQL endpoint availability check for English Heritage Monument Types Thesaurus took 3.886222839355469e-05s
Availability | VoID file availability check for English Heritage Monument Types Thesaurus took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for English Heritage Monument Types Thesaurus took 0.2567563056945801s
Reputation | Calculation of the PageRank for English Heritage Monument Types Thesaurus took 0.020404338836669922s
Interlinking | Calculation of Degree of Connection for English Heritage Monument Types Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for English Heritage Monument Types Thesaurus took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for English Heritage Monument Types Thesaurus took 2.9087066650390625e-05s
Believability | Calculation of trust value for English Heritage Monument Types Thesaurus took 8.344650268554688e-06s
INFO | --- Analysis for english-heritage-monument-types-thesaurus took 2.963399648666382s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 1.527949571609497s
Availability | VoID file availability check for English Heritage Periods List took 0.0008244514465332031s
Extra | Recovery of all triples for English Heritage Periods List took 1.043107509613037s
Amount of data | Number of triples check for English Heritage Periods List took 1.510857105255127s
Versatility | Languages check for English Heritage Periods List took 0.5167183876037598s
Interpretability | Number of blank nodes check for English Heritage Periods List took 10.231897592544556s
Security | Check HTTPS for English Heritage Periods List took 15.540288925170898s
Interpretability | RDF structures check for English Heritage Periods List took 0.6572046279907227s
Versatility | Serialization formats check for English Heritage Periods List took 68.7803680896759s
Availability | RDF dump link check for English Heritage Periods List took 86.60248947143555s
License | MR license check for English Heritage Periods List took 10.198007106781006s
License | HR license check for English Heritage Periods List took 10.836300373077393s
Amount of data | Number of property check for English Heritage Periods List took 55.80466437339783s
Understandability | Number of label check for English Heritage Periods List took 35.05521535873413s
Understandability | URI regex check for English Heritage Periods List took 1.3100075721740723s
Understandability | Vocabs check for English Heritage Periods List took 0.7800467014312744s
Verifiability | Authors check for English Heritage Periods List took 0.509270191192627s
Verifiability | Publishers check for English Heritage Periods List took 41.082741498947144s
Performance | Throughput check for English Heritage Periods List took 217.13209295272827s
Amount of data | Check the number of entities for English Heritage Periods List took 6.937980651855469e-05s
Verifiability | Contribs. check for English Heritage Periods List took 0.49248671531677246s
Interlinking | sameAs chians check for English Heritage Periods List took 0.41147589683532715s
Interlinking | skos check for English Heritage Periods List took 0.4479975700378418s
Interlinking | skos check for English Heritage Periods List took 0.42777299880981445s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.44553494453430176s
Currency | Creation date check for English Heritage Periods List took 0.9096505641937256s
Currency | Modification date check for English Heritage Periods List took 0.9450671672821045s
Rep.Conc. | URIs length for English Heritage Periods List took 0.8996107578277588s
Interoperability | New vocabularies check for English Heritage Periods List took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Periods List took 0.5072391033172607s
Accuracy | Check Functional Property for English Heritage Periods List took 0.5794363021850586s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.40224242210388184s
Consistency | Disjoint class check for English Heritage Periods List took 1.2800424098968506s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.4623715877532959s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.5676019191741943s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.00014257431030273438s
Security | Sign check for English Heritage Periods List took 53.416114807128906s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 0.5012972354888916s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.020487546920776367s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 3.814697265625e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Periods List took 1.1920928955078125e-06s
Believability | Calculation of trust value for English Heritage Periods List took 6.67572021484375e-06s
INFO | --- Analysis for english-heritage-periods-list took 911.8438727855682s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 0.3026754856109619s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.0005345344543457031s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 0.27220892906188965s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.029513120651245117s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 3.6716461181640625e-05s
Believability | Calculation of trust value for English Index of Multiple Deprivation Ranking 2010 took 4.76837158203125e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-ranking-2010 took 4.093571186065674s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Score 2010 took 0.2303483486175537s
Availability | VoID file availability check for English Index of Multiple Deprivation Score 2010 took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Score 2010 took 0.2807741165161133s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Score 2010 took 0.020531892776489258s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Score 2010 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Score 2010 took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Score 2010 took 3.552436828613281e-05s
Believability | Calculation of trust value for English Index of Multiple Deprivation Score 2010 took 5.7220458984375e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-score-2010 took 5.610858917236328s
Availability | SPARQL endpoint availability check for English Indices of Multiple Deprivation took 4.1484832763671875e-05s
Availability | VoID file availability check for English Indices of Multiple Deprivation took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for English Indices of Multiple Deprivation took 0.2764430046081543s
Reputation | Calculation of the PageRank for English Indices of Multiple Deprivation took 0.02161693572998047s
Interlinking | Calculation of Degree of Connection for English Indices of Multiple Deprivation took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for English Indices of Multiple Deprivation took 0.0007865428924560547s
Interlinking | Calculation of Clustering coefficient for English Indices of Multiple Deprivation took 3.886222839355469e-05s
Believability | Calculation of trust value for English Indices of Multiple Deprivation took 5.4836273193359375e-06s
INFO | --- Analysis for english-indices-of-multiple-deprivation took 2.994931697845459s
Availability | SPARQL endpoint availability check for English WordNet took 4.291534423828125e-05s
Availability | VoID file availability check for English WordNet took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for English WordNet took 0.2584104537963867s
Reputation | Calculation of the PageRank for English WordNet took 0.0202789306640625s
Interlinking | Calculation of Degree of Connection for English WordNet took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for English WordNet took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for English WordNet took 3.2901763916015625e-05s
Believability | Calculation of trust value for English WordNet took 5.245208740234375e-06s
INFO | --- Analysis for english-wordnet took 3.641483783721924s
Availability | SPARQL endpoint availability check for English Heritage Places took 3.886222839355469e-05s
Availability | VoID file availability check for English Heritage Places took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for English Heritage Places took 0.26949596405029297s
Reputation | Calculation of the PageRank for English Heritage Places took 0.020206451416015625s
Interlinking | Calculation of Degree of Connection for English Heritage Places took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for English Heritage Places took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for English Heritage Places took 3.147125244140625e-05s
Believability | Calculation of trust value for English Heritage Places took 6.4373016357421875e-06s
INFO | --- Analysis for englishheritage_places took 2.950296640396118s
Availability | SPARQL endpoint availability check for Enipedia - Energy Industry Data took 0.18567562103271484s
Availability | VoID file availability check for Enipedia - Energy Industry Data took 0.00048041343688964844s
Completeness | Calculation of interlinking completeness for Enipedia - Energy Industry Data took 0.26090455055236816s
Reputation | Calculation of the PageRank for Enipedia - Energy Industry Data took 0.02337360382080078s
Interlinking | Calculation of Degree of Connection for Enipedia - Energy Industry Data took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Enipedia - Energy Industry Data took 0.0007884502410888672s
Interlinking | Calculation of Clustering coefficient for Enipedia - Energy Industry Data took 0.00010061264038085938s
Believability | Calculation of trust value for Enipedia - Energy Industry Data took 7.867813110351562e-06s
INFO | --- Analysis for enipedia took 3.0817861557006836s
Availability | SPARQL endpoint availability check for Enslaved.org took 4.2438507080078125e-05s
Availability | VoID file availability check for Enslaved.org took 0.0006251335144042969s
Completeness | Calculation of interlinking completeness for Enslaved.org took 0.2653675079345703s
Reputation | Calculation of the PageRank for Enslaved.org took 0.020830631256103516s
Interlinking | Calculation of Degree of Connection for Enslaved.org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Enslaved.org took 0.0007920265197753906s
Interlinking | Calculation of Clustering coefficient for Enslaved.org took 3.528594970703125e-05s
Believability | Calculation of trust value for Enslaved.org took 7.3909759521484375e-06s
INFO | --- Analysis for enslaved.org took 5.209477186203003s
Availability | SPARQL endpoint availability check for ENTICE Educational Episodes Knowledge Graph took 60.0490517616272s
Availability | VoID file availability check for ENTICE Educational Episodes Knowledge Graph took 0.0007343292236328125s
Completeness | Calculation of interlinking completeness for ENTICE Educational Episodes Knowledge Graph took 0.26334714889526367s
Reputation | Calculation of the PageRank for ENTICE Educational Episodes Knowledge Graph took 0.020322322845458984s
Interlinking | Calculation of Degree of Connection for ENTICE Educational Episodes Knowledge Graph took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for ENTICE Educational Episodes Knowledge Graph took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for ENTICE Educational Episodes Knowledge Graph took 5.53131103515625e-05s
Believability | Calculation of trust value for ENTICE Educational Episodes Knowledge Graph took 7.867813110351562e-06s
INFO | --- Analysis for entice-graph took 143.82235431671143s
Availability | SPARQL endpoint availability check for Entrez Gene took 4.3392181396484375e-05s
Availability | VoID file availability check for Entrez Gene took 0.0007843971252441406s
Completeness | Calculation of interlinking completeness for Entrez Gene took 0.2734639644622803s
Reputation | Calculation of the PageRank for Entrez Gene took 0.020061731338500977s
Interlinking | Calculation of Degree of Connection for Entrez Gene took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Entrez Gene took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Entrez Gene took 3.218650817871094e-05s
Believability | Calculation of trust value for Entrez Gene took 6.9141387939453125e-06s
INFO | --- Analysis for entrez_gene took 27.955700874328613s
Availability | SPARQL endpoint availability check for Entrez Gene Extract took 3.933906555175781e-05s
Availability | VoID file availability check for Entrez Gene Extract took 0.00023221969604492188s
Completeness | Calculation of interlinking completeness for Entrez Gene Extract took 0.2597494125366211s
Reputation | Calculation of the PageRank for Entrez Gene Extract took 0.0209047794342041s
Interlinking | Calculation of Degree of Connection for Entrez Gene Extract took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Entrez Gene Extract took 0.0008876323699951172s
Interlinking | Calculation of Clustering coefficient for Entrez Gene Extract took 3.1948089599609375e-05s
Believability | Calculation of trust value for Entrez Gene Extract took 6.198883056640625e-06s
INFO | --- Analysis for entrez_gene_extract took 3.343416929244995s
Availability | SPARQL endpoint availability check for Environment Agency Bathing Water Quality took 1.0688631534576416s
Availability | VoID file availability check for Environment Agency Bathing Water Quality took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for Environment Agency Bathing Water Quality took 0.7300443649291992s
Reputation | Calculation of the PageRank for Environment Agency Bathing Water Quality took 0.020141124725341797s
Interlinking | Calculation of Degree of Connection for Environment Agency Bathing Water Quality took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Environment Agency Bathing Water Quality took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Environment Agency Bathing Water Quality took 4.649162292480469e-05s
Believability | Calculation of trust value for Environment Agency Bathing Water Quality took 4.5299530029296875e-06s
INFO | --- Analysis for environment-agency-bathing-water-quality took 13.32795524597168s
Availability | SPARQL endpoint availability check for environment.data.gov.uk took 0.36292338371276855s
Availability | VoID file availability check for environment.data.gov.uk took 0.0005803108215332031s
Completeness | Calculation of interlinking completeness for environment.data.gov.uk took 0.26291871070861816s
Reputation | Calculation of the PageRank for environment.data.gov.uk took 0.020227909088134766s
Interlinking | Calculation of Degree of Connection for environment.data.gov.uk took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for environment.data.gov.uk took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for environment.data.gov.uk took 4.291534423828125e-05s
Believability | Calculation of trust value for environment.data.gov.uk took 4.5299530029296875e-06s
INFO | --- Analysis for environment-data-gov-uk took 9.644562482833862s
Availability | SPARQL endpoint availability check for EARTh took 272.0529725551605s
Availability | VoID file availability check for EARTh took 0.0008416175842285156s
Completeness | Calculation of interlinking completeness for EARTh took 0.2771768569946289s
Reputation | Calculation of the PageRank for EARTh took 0.02074575424194336s
Interlinking | Calculation of Degree of Connection for EARTh took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for EARTh took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for EARTh took 0.00010251998901367188s
Believability | Calculation of trust value for EARTh took 5.7220458984375e-06s
INFO | --- Analysis for environmental-applications-reference-thesaurus took 566.0375957489014s
Availability | SPARQL endpoint availability check for Micka (EO metadata) @PSNC took 0.48528409004211426s
Availability | VoID file availability check for Micka (EO metadata) @PSNC took 0.00025200843811035156s
Extra | Recovery of all triples for Micka (EO metadata) @PSNC took 107.83243799209595s
Performance | Total latancy measurement for Micka (EO metadata) @PSNC took 1.0075318813323975s
Amount of data | Number of triples check for Micka (EO metadata) @PSNC took 9.22127389907837s
Interoperability | New terms check for Micka (EO metadata) @PSNC took 14.245585680007935s
Versatility | Languages check for Micka (EO metadata) @PSNC took 300.25197529792786s
Interpretability | Number of blank nodes check for Micka (EO metadata) @PSNC took 2.409677028656006s
Interpretability | RDF structures check for Micka (EO metadata) @PSNC took 0.2617156505584717s
Versatility | Serialization formats check for Micka (EO metadata) @PSNC took 9.008320569992065s
Availability | RDF dump link check for Micka (EO metadata) @PSNC took 0.292205810546875s
License | MR license check for Micka (EO metadata) @PSNC took 0.5966393947601318s
License | HR license check for Micka (EO metadata) @PSNC took 300.25129890441895s
Amount of data | Number of property check for Micka (EO metadata) @PSNC took 0.3367283344268799s
Understandability | Number of label check for Micka (EO metadata) @PSNC took 2.5442090034484863s
Understandability | URI regex check for Micka (EO metadata) @PSNC took 0.9403340816497803s
Understandability | Vocabs check for Micka (EO metadata) @PSNC took 0.5223946571350098s
Verifiability | Authors check for Micka (EO metadata) @PSNC took 0.2128007411956787s
Verifiability | Publishers check for Micka (EO metadata) @PSNC took 0.2497255802154541s
Performance | Throughput check for Micka (EO metadata) @PSNC took 11.575290203094482s
Amount of data | Check the number of entities for Micka (EO metadata) @PSNC took 7.2479248046875e-05s
Verifiability | Contribs. check for Micka (EO metadata) @PSNC took 0.2119762897491455s
Interlinking | sameAs chians check for Micka (EO metadata) @PSNC took 0.2038722038269043s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.5079779624938965s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.468245267868042s
Timeliness | dataset update frequency check for Micka (EO metadata) @PSNC took 5.7138025760650635s
Currency | Creation date check for Micka (EO metadata) @PSNC took 0.5068306922912598s
Currency | Modification date check for Micka (EO metadata) @PSNC took 0.25681281089782715s
Rep.Conc. | URIs length for Micka (EO metadata) @PSNC took 153.88545083999634s
Interoperability | New vocabularies check for Micka (EO metadata) @PSNC took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Micka (EO metadata) @PSNC took 0.18870139122009277s
Accuracy | Check Functional Property for Micka (EO metadata) @PSNC took 0.3930537700653076s
Accuracy | Check Inverse Functional Property for Micka (EO metadata) @PSNC took 0.35650110244750977s
Accuracy | Check Empty annotation labels for Micka (EO metadata) @PSNC took 37.14203929901123s
Accuracy | Check White space in annotation for Micka (EO metadata) @PSNC took 2.725083351135254s
Accuracy | Check Datatype consistency for Micka (EO metadata) @PSNC took 2.632647752761841s
Consistency | Disjoint class check for Micka (EO metadata) @PSNC took 0.19353604316711426s
Consistency | Check Misplaced properties for Micka (EO metadata) @PSNC took 102.81278848648071s
Consistency | Misplaced classes for Micka (EO metadata) @PSNC took 8.612634181976318s
Consistency | Check Ontology hijacking for Micka (EO metadata) @PSNC took 35.9708890914917s
Consistency | Check Invalid usage of undefined classes for Micka (EO metadata) @PSNC took 1.2203161716461182s
Consistency | Check Invalid usage of undefined properties for Micka (EO metadata) @PSNC took 96.99640417098999s
Conciseness | Check Extensional conciseness for Micka (EO metadata) @PSNC took 2.717000961303711s
Conciseness | Check Intensional conciseness for Micka (EO metadata) @PSNC took 0.5712018013000488s
Security | Sign check for Micka (EO metadata) @PSNC took 0.9184601306915283s
Availability | Check URIs Dereferenciability for Micka (EO metadata) @PSNC took 5.799839735031128s
Completeness | Calculation of interlinking completeness for Micka (EO metadata) @PSNC took 1.3868398666381836s
Reputation | Calculation of the PageRank for Micka (EO metadata) @PSNC took 0.020903825759887695s
Interlinking | Calculation of Degree of Connection for Micka (EO metadata) @PSNC took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Micka (EO metadata) @PSNC took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Micka (EO metadata) @PSNC took 4.410743713378906e-05s
Interoperability | Check the re-using of existing vocabs for Micka (EO metadata) @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Micka (EO metadata) @PSNC took 7.152557373046875e-06s
INFO | --- Analysis for EO_metadata took 2284.797307729721s
Availability | SPARQL endpoint availability check for Earth Observation Knowledge Packages took 4.315376281738281e-05s
Availability | VoID file availability check for Earth Observation Knowledge Packages took 0.000667572021484375s
Completeness | Calculation of interlinking completeness for Earth Observation Knowledge Packages took 0.3074500560760498s
Reputation | Calculation of the PageRank for Earth Observation Knowledge Packages took 0.020453453063964844s
Interlinking | Calculation of Degree of Connection for Earth Observation Knowledge Packages took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Earth Observation Knowledge Packages took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Earth Observation Knowledge Packages took 3.0517578125e-05s
Believability | Calculation of trust value for Earth Observation Knowledge Packages took 7.62939453125e-06s
INFO | --- Analysis for EOKP-Datasets took 4.169087648391724s
Availability | SPARQL endpoint availability check for EPA-CDR took 9.5367431640625e-05s
Availability | VoID file availability check for EPA-CDR took 0.0006594657897949219s
Completeness | Calculation of interlinking completeness for EPA-CDR took 0.6881592273712158s
Reputation | Calculation of the PageRank for EPA-CDR took 0.02079916000366211s
Interlinking | Calculation of Degree of Connection for EPA-CDR took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EPA-CDR took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for EPA-CDR took 4.291534423828125e-05s
Believability | Calculation of trust value for EPA-CDR took 4.291534423828125e-06s
INFO | --- Analysis for epa-cdr took 7.4219725131988525s
Availability | SPARQL endpoint availability check for EPA-FRS took 4.315376281738281e-05s
Availability | VoID file availability check for EPA-FRS took 0.0007121562957763672s
Completeness | Calculation of interlinking completeness for EPA-FRS took 0.2747924327850342s
Reputation | Calculation of the PageRank for EPA-FRS took 0.020425796508789062s
Interlinking | Calculation of Degree of Connection for EPA-FRS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EPA-FRS took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for EPA-FRS took 6.985664367675781e-05s
Believability | Calculation of trust value for EPA-FRS took 4.0531158447265625e-06s
INFO | --- Analysis for epa-frs took 7.083787202835083s
Availability | SPARQL endpoint availability check for EPA-RCRA took 4.3392181396484375e-05s
Availability | VoID file availability check for EPA-RCRA took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for EPA-RCRA took 0.26487040519714355s
Reputation | Calculation of the PageRank for EPA-RCRA took 0.020269155502319336s
Interlinking | Calculation of Degree of Connection for EPA-RCRA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EPA-RCRA took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for EPA-RCRA took 3.218650817871094e-05s
Believability | Calculation of trust value for EPA-RCRA took 4.5299530029296875e-06s
INFO | --- Analysis for epa-rcra took 6.276543617248535s
Availability | SPARQL endpoint availability check for EPA-SRS took 4.38690185546875e-05s
Availability | VoID file availability check for EPA-SRS took 0.00061798095703125s
Completeness | Calculation of interlinking completeness for EPA-SRS took 0.705385684967041s
Reputation | Calculation of the PageRank for EPA-SRS took 0.020293235778808594s
Interlinking | Calculation of Degree of Connection for EPA-SRS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EPA-SRS took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for EPA-SRS took 7.343292236328125e-05s
Believability | Calculation of trust value for EPA-SRS took 4.76837158203125e-06s
INFO | --- Analysis for epa-srs took 6.607115745544434s
Availability | SPARQL endpoint availability check for EPA-TRI took 4.100799560546875e-05s
Availability | VoID file availability check for EPA-TRI took 0.0006351470947265625s
Completeness | Calculation of interlinking completeness for EPA-TRI took 0.2669374942779541s
Reputation | Calculation of the PageRank for EPA-TRI took 0.020394325256347656s
Interlinking | Calculation of Degree of Connection for EPA-TRI took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EPA-TRI took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for EPA-TRI took 3.0994415283203125e-05s
Believability | Calculation of trust value for EPA-TRI took 4.5299530029296875e-06s
INFO | --- Analysis for epa-tri took 5.759097337722778s
Availability | SPARQL endpoint availability check for European Patent Office (EPO) took 3.838539123535156e-05s
Availability | VoID file availability check for European Patent Office (EPO) took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for European Patent Office (EPO) took 0.28748011589050293s
Reputation | Calculation of the PageRank for European Patent Office (EPO) took 0.020287752151489258s
Interlinking | Calculation of Degree of Connection for European Patent Office (EPO) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for European Patent Office (EPO) took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for European Patent Office (EPO) took 7.295608520507812e-05s
Believability | Calculation of trust value for European Patent Office (EPO) took 6.4373016357421875e-06s
INFO | --- Analysis for epo took 2.9784164428710938s
Availability | SPARQL endpoint availability check for ePrints Harvest (RKBExplorer) took 0.039949655532836914s
Availability | VoID file availability check for ePrints Harvest (RKBExplorer) took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for ePrints Harvest (RKBExplorer) took 0.2779254913330078s
Reputation | Calculation of the PageRank for ePrints Harvest (RKBExplorer) took 0.02012801170349121s
Interlinking | Calculation of Degree of Connection for ePrints Harvest (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ePrints Harvest (RKBExplorer) took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for ePrints Harvest (RKBExplorer) took 0.0001251697540283203s
Believability | Calculation of trust value for ePrints Harvest (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for eprints-harvest-rkbexplorer took 2.571195363998413s
Availability | SPARQL endpoint availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.4102182388305664s
Availability | VoID file availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for European Pollutant Release and Transfer Register (E-PRTR) took 0.27852916717529297s
Reputation | Calculation of the PageRank for European Pollutant Release and Transfer Register (E-PRTR) took 0.021439790725708008s
Interlinking | Calculation of Degree of Connection for European Pollutant Release and Transfer Register (E-PRTR) took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for European Pollutant Release and Transfer Register (E-PRTR) took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for European Pollutant Release and Transfer Register (E-PRTR) took 8.249282836914062e-05s
Believability | Calculation of trust value for European Pollutant Release and Transfer Register (E-PRTR) took 7.3909759521484375e-06s
INFO | --- Analysis for eprtr took 3.7381432056427s
Availability | SPARQL endpoint availability check for Railway Infrastructure KG took 0.1348860263824463s
Availability | VoID file availability check for Railway Infrastructure KG took 0.0004334449768066406s
Completeness | Calculation of interlinking completeness for Railway Infrastructure KG took 0.2599306106567383s
Reputation | Calculation of the PageRank for Railway Infrastructure KG took 0.02069711685180664s
Interlinking | Calculation of Degree of Connection for Railway Infrastructure KG took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Railway Infrastructure KG took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Railway Infrastructure KG took 3.24249267578125e-05s
Believability | Calculation of trust value for Railway Infrastructure KG took 7.152557373046875e-06s
INFO | --- Analysis for ERAKG took 2.5550458431243896s
Availability | SPARQL endpoint availability check for reg took 4.267692565917969e-05s
Availability | VoID file availability check for reg took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for reg took 0.26471948623657227s
Reputation | Calculation of the PageRank for reg took 0.02064990997314453s
Interlinking | Calculation of Degree of Connection for reg took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for reg took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for reg took 1.1920928955078125e-05s
Believability | Calculation of trust value for reg took 7.3909759521484375e-06s
INFO | --- Analysis for erg took 2.393373966217041s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Kingdom of Spain took 30.235220909118652s
Availability | VoID file availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.0007615089416503906s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Kingdom of Spain took 0.2685277462005615s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Kingdom of Spain took 0.020882606506347656s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Kingdom of Spain took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Kingdom of Spain took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Kingdom of Spain took 3.0040740966796875e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Kingdom of Spain took 5.245208740234375e-06s
INFO | --- Analysis for es-msssi-drug-prices took 102.89306879043579s
Availability | SPARQL endpoint availability check for ESD Standards: Controlled lists for the UK public sector took 4.172325134277344e-05s
Availability | VoID file availability check for ESD Standards: Controlled lists for the UK public sector took 0.0007319450378417969s
Completeness | Calculation of interlinking completeness for ESD Standards: Controlled lists for the UK public sector took 0.26181626319885254s
Reputation | Calculation of the PageRank for ESD Standards: Controlled lists for the UK public sector took 0.02040553092956543s
Interlinking | Calculation of Degree of Connection for ESD Standards: Controlled lists for the UK public sector took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ESD Standards: Controlled lists for the UK public sector took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for ESD Standards: Controlled lists for the UK public sector took 8.726119995117188e-05s
Believability | Calculation of trust value for ESD Standards: Controlled lists for the UK public sector took 5.0067901611328125e-06s
INFO | --- Analysis for esd-standards took 4.700144052505493s
Availability | SPARQL endpoint availability check for ESD-Toolkit took 7.748603820800781e-05s
Availability | VoID file availability check for ESD-Toolkit took 0.0006830692291259766s
Completeness | Calculation of interlinking completeness for ESD-Toolkit took 0.27448487281799316s
Reputation | Calculation of the PageRank for ESD-Toolkit took 0.020372390747070312s
Interlinking | Calculation of Degree of Connection for ESD-Toolkit took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ESD-Toolkit took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for ESD-Toolkit took 7.295608520507812e-05s
Believability | Calculation of trust value for ESD-Toolkit took 5.7220458984375e-06s
INFO | --- Analysis for esd-toolkit took 4.297135829925537s
Availability | SPARQL endpoint availability check for Dataset Esis took 4.4345855712890625e-05s
Availability | VoID file availability check for Dataset Esis took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for Dataset Esis took 0.2543067932128906s
Reputation | Calculation of the PageRank for Dataset Esis took 0.020227909088134766s
Interlinking | Calculation of Degree of Connection for Dataset Esis took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Dataset Esis took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Dataset Esis took 3.147125244140625e-05s
Believability | Calculation of trust value for Dataset Esis took 7.152557373046875e-06s
INFO | --- Analysis for esislearning took 2.890145778656006s
Availability | SPARQL endpoint availability check for The European Science Vocabulary (EuroSciVoc) took 4.0531158447265625e-05s
Availability | VoID file availability check for The European Science Vocabulary (EuroSciVoc) took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for The European Science Vocabulary (EuroSciVoc) took 0.2610299587249756s
Reputation | Calculation of the PageRank for The European Science Vocabulary (EuroSciVoc) took 0.020336389541625977s
Interlinking | Calculation of Degree of Connection for The European Science Vocabulary (EuroSciVoc) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The European Science Vocabulary (EuroSciVoc) took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for The European Science Vocabulary (EuroSciVoc) took 2.7894973754882812e-05s
Believability | Calculation of trust value for The European Science Vocabulary (EuroSciVoc) took 5.4836273193359375e-06s
INFO | --- Analysis for ESV took 3.504382371902466s
Availability | SPARQL endpoint availability check for Etymological Dictionary of Latin in LiLa took 0.5580356121063232s
Availability | VoID file availability check for Etymological Dictionary of Latin in LiLa took 0.0003046989440917969s
Completeness | Calculation of interlinking completeness for Etymological Dictionary of Latin in LiLa took 0.2642490863800049s
Reputation | Calculation of the PageRank for Etymological Dictionary of Latin in LiLa took 0.020195722579956055s
Interlinking | Calculation of Degree of Connection for Etymological Dictionary of Latin in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Etymological Dictionary of Latin in LiLa took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Etymological Dictionary of Latin in LiLa took 3.695487976074219e-05s
Believability | Calculation of trust value for Etymological Dictionary of Latin in LiLa took 7.152557373046875e-06s
INFO | --- Analysis for EtymologicalDictionaryofLatin took 4.139394998550415s
Availability | SPARQL endpoint availability check for EU Agencies and decentralized bodies (Agencies) took 5.845411777496338s
Availability | VoID file availability check for EU Agencies and decentralized bodies (Agencies) took 0.0008702278137207031s
Completeness | Calculation of interlinking completeness for EU Agencies and decentralized bodies (Agencies) took 0.2701854705810547s
Reputation | Calculation of the PageRank for EU Agencies and decentralized bodies (Agencies) took 0.021753311157226562s
Interlinking | Calculation of Degree of Connection for EU Agencies and decentralized bodies (Agencies) took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for EU Agencies and decentralized bodies (Agencies) took 0.0009624958038330078s
Interlinking | Calculation of Clustering coefficient for EU Agencies and decentralized bodies (Agencies) took 8.487701416015625e-05s
Believability | Calculation of trust value for EU Agencies and decentralized bodies (Agencies) took 7.62939453125e-06s
INFO | --- Analysis for eu-agencies-bodies took 16.27235245704651s
Availability | SPARQL endpoint availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 4.172325134277344e-05s
Availability | VoID file availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.0003402233123779297s
Completeness | Calculation of interlinking completeness for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.24897003173828125s
Reputation | Calculation of the PageRank for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.020354032516479492s
Interlinking | Calculation of Degree of Connection for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 3.123283386230469e-05s
Believability | Calculation of trust value for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 5.9604644775390625e-06s
INFO | --- Analysis for eu-dgt-tm took 2.876333713531494s
Availability | SPARQL endpoint availability check for Institutions and Bodies of the European Union took 4.2438507080078125e-05s
Availability | VoID file availability check for Institutions and Bodies of the European Union took 0.000701904296875s
Completeness | Calculation of interlinking completeness for Institutions and Bodies of the European Union took 0.2645251750946045s
Reputation | Calculation of the PageRank for Institutions and Bodies of the European Union took 0.020119190216064453s
Interlinking | Calculation of Degree of Connection for Institutions and Bodies of the European Union took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Institutions and Bodies of the European Union took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Institutions and Bodies of the European Union took 7.081031799316406e-05s
Believability | Calculation of trust value for Institutions and Bodies of the European Union took 9.775161743164062e-06s
INFO | --- Analysis for eu-institutions took 11.366820335388184s
Availability | SPARQL endpoint availability check for EU Parliament Media Library took 1.0803911685943604s
Availability | VoID file availability check for EU Parliament Media Library took 0.0007538795471191406s
Completeness | Calculation of interlinking completeness for EU Parliament Media Library took 0.2780625820159912s
Reputation | Calculation of the PageRank for EU Parliament Media Library took 0.020408153533935547s
Interlinking | Calculation of Degree of Connection for EU Parliament Media Library took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EU Parliament Media Library took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for EU Parliament Media Library took 3.361701965332031e-05s
Believability | Calculation of trust value for EU Parliament Media Library took 5.245208740234375e-06s
INFO | --- Analysis for eu-parliament-media took 7.969568252563477s
Availability | SPARQL endpoint availability check for EU Who Is Who took 0.9372115135192871s
Availability | VoID file availability check for EU Who Is Who took 0.0006606578826904297s
Completeness | Calculation of interlinking completeness for EU Who Is Who took 0.2658677101135254s
Reputation | Calculation of the PageRank for EU Who Is Who took 0.020470380783081055s
Interlinking | Calculation of Degree of Connection for EU Who Is Who took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EU Who Is Who took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for EU Who Is Who took 3.409385681152344e-05s
Believability | Calculation of trust value for EU Who Is Who took 4.291534423828125e-06s
INFO | --- Analysis for eu-who-is-who took 10.110368251800537s
Availability | SPARQL endpoint availability check for EUMIDA as Linked Data took 0.895578145980835s
Availability | VoID file availability check for EUMIDA as Linked Data took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for EUMIDA as Linked Data took 0.2723357677459717s
Reputation | Calculation of the PageRank for EUMIDA as Linked Data took 0.020377397537231445s
Interlinking | Calculation of Degree of Connection for EUMIDA as Linked Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EUMIDA as Linked Data took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for EUMIDA as Linked Data took 3.981590270996094e-05s
Believability | Calculation of trust value for EUMIDA as Linked Data took 4.76837158203125e-06s
INFO | --- Analysis for eumida-linked-data took 8.168454647064209s
Availability | SPARQL endpoint availability check for European Nature Information System took 0.3724534511566162s
Availability | VoID file availability check for European Nature Information System took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for European Nature Information System took 0.2872648239135742s
Reputation | Calculation of the PageRank for European Nature Information System took 0.020428895950317383s
Interlinking | Calculation of Degree of Connection for European Nature Information System took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for European Nature Information System took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for European Nature Information System took 0.00010442733764648438s
Believability | Calculation of trust value for European Nature Information System took 5.7220458984375e-06s
INFO | --- Analysis for eunis took 4.100737571716309s
Availability | SPARQL endpoint availability check for EUR-Lex as Linked Data took 3603.588835954666s
Availability | VoID file availability check for EUR-Lex as Linked Data took 0.0006620883941650391s
Completeness | Calculation of interlinking completeness for EUR-Lex as Linked Data took 0.2770519256591797s
Reputation | Calculation of the PageRank for EUR-Lex as Linked Data took 0.02140069007873535s
Interlinking | Calculation of Degree of Connection for EUR-Lex as Linked Data took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for EUR-Lex as Linked Data took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for EUR-Lex as Linked Data took 7.724761962890625e-05s
Believability | Calculation of trust value for EUR-Lex as Linked Data took 6.198883056640625e-06s
INFO | --- Analysis for eur-lex-rdf took 3612.8635823726654s
Availability | SPARQL endpoint availability check for Standard Eurobarometer took 1.023362636566162s
Availability | VoID file availability check for Standard Eurobarometer took 0.0005855560302734375s
Completeness | Calculation of interlinking completeness for Standard Eurobarometer took 0.3030531406402588s
Reputation | Calculation of the PageRank for Standard Eurobarometer took 0.020389795303344727s
Interlinking | Calculation of Degree of Connection for Standard Eurobarometer took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Standard Eurobarometer took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Standard Eurobarometer took 4.0531158447265625e-05s
Believability | Calculation of trust value for Standard Eurobarometer took 4.5299530029296875e-06s
INFO | --- Analysis for eurobarometer-standard took 8.383895874023438s
Availability | SPARQL endpoint availability check for European Election Results took 0.9312119483947754s
Availability | VoID file availability check for European Election Results took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for European Election Results took 0.281400203704834s
Reputation | Calculation of the PageRank for European Election Results took 0.020502328872680664s
Interlinking | Calculation of Degree of Connection for European Election Results took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for European Election Results took 0.0008771419525146484s
Interlinking | Calculation of Clustering coefficient for European Election Results took 3.886222839355469e-05s
Believability | Calculation of trust value for European Election Results took 5.245208740234375e-06s
INFO | --- Analysis for european-election-results took 8.57676887512207s
Availability | SPARQL endpoint availability check for EPO patents took 0.4499082565307617s
Availability | VoID file availability check for EPO patents took 0.0005583763122558594s
Extra | Recovery of all triples for EPO patents took 45.353209495544434s
Performance | Total latancy measurement for EPO patents took 1.0767803192138672s
Amount of data | Number of triples check for EPO patents took 90.21425342559814s
Versatility | Languages check for EPO patents took 120.11940288543701s
Interpretability | Number of blank nodes check for EPO patents took 90.27495193481445s
Interpretability | RDF structures check for EPO patents took 0.21121883392333984s
Versatility | Serialization formats check for EPO patents took 0.23245716094970703s
Availability | RDF dump link check for EPO patents took 0.19887661933898926s
License | MR license check for EPO patents took 0.18858051300048828s
License | HR license check for EPO patents took 90.18274188041687s
Amount of data | Number of property check for EPO patents took 0.25179505348205566s
Understandability | Number of label check for EPO patents took 90.16961765289307s
Understandability | URI regex check for EPO patents took 0.3855125904083252s
Understandability | Vocabs check for EPO patents took 0.21091198921203613s
Verifiability | Authors check for EPO patents took 0.1828906536102295s
Verifiability | Publishers check for EPO patents took 0.22913122177124023s
Performance | Throughput check for EPO patents took 11.313805341720581s
Amount of data | Check the number of entities for EPO patents took 8.654594421386719e-05s
Verifiability | Contribs. check for EPO patents took 0.21737933158874512s
Interlinking | sameAs chians check for EPO patents took 0.21961641311645508s
Interlinking | skos check for EPO patents took 0.26337099075317383s
Interlinking | skos check for EPO patents took 0.18806791305541992s
Timeliness | dataset update frequency check for EPO patents took 0.20730066299438477s
Currency | Creation date check for EPO patents took 0.4760465621948242s
Currency | Modification date check for EPO patents took 0.4158933162689209s
Rep.Conc. | URIs length for EPO patents took 182.1975073814392s
Interoperability | New vocabularies check for EPO patents took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for EPO patents took 0.2758519649505615s
Accuracy | Check Empty annotation labels for EPO patents took 40.25065612792969s
Accuracy | Check White space in annotation for EPO patents took 3.047913074493408s
Accuracy | Check Datatype consistency for EPO patents took 4.937923431396484s
Consistency | Disjoint class check for EPO patents took 0.21596574783325195s
Consistency | Check Misplaced properties for EPO patents took 120.39683222770691s
Consistency | Check Ontology hijacking for EPO patents took 57.05905556678772s
Consistency | Check Invalid usage of undefined classes for EPO patents took 1.44162917137146s
Consistency | Check Invalid usage of undefined properties for EPO patents took 121.52510833740234s
Conciseness | Check Extensional conciseness for EPO patents took 2.8182458877563477s
Conciseness | Check Intensional conciseness for EPO patents took 0.35340332984924316s
Security | Sign check for EPO patents took 0.29265594482421875s
Availability | Check URIs Dereferenciability for EPO patents took 2.1145896911621094s
Completeness | Calculation of interlinking completeness for EPO patents took 0.8270046710968018s
Reputation | Calculation of the PageRank for EPO patents took 0.021286964416503906s
Interlinking | Calculation of Degree of Connection for EPO patents took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for EPO patents took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for EPO patents took 4.220008850097656e-05s
Interoperability | Check the re-using of existing vocabs for EPO patents took 2.1457672119140625e-06s
Believability | Calculation of trust value for EPO patents took 6.9141387939453125e-06s
INFO | --- Analysis for European_Patent_Information took 1397.7860407829285s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data took 4.76837158203125e-05s
Availability | VoID file availability check for Europeana Linked Open Data took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data took 0.27022838592529297s
Reputation | Calculation of the PageRank for Europeana Linked Open Data took 0.022601842880249023s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data took 0.0012938976287841797s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data took 4.458427429199219e-05s
Believability | Calculation of trust value for Europeana Linked Open Data took 6.9141387939453125e-06s
INFO | --- Analysis for europeana-lod took 4.298807144165039s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data V1.0 took 4.220008850097656e-05s
Availability | VoID file availability check for Europeana Linked Open Data V1.0 took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data V1.0 took 0.3132283687591553s
Reputation | Calculation of the PageRank for Europeana Linked Open Data V1.0 took 0.020255327224731445s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data V1.0 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data V1.0 took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data V1.0 took 9.250640869140625e-05s
Believability | Calculation of trust value for Europeana Linked Open Data V1.0 took 7.152557373046875e-06s
INFO | --- Analysis for europeana-lod-v1 took 9.388511180877686s
Availability | SPARQL endpoint availability check for Europeana SPARQL took 0.04026341438293457s
Availability | VoID file availability check for Europeana SPARQL took 0.0003757476806640625s
Completeness | Calculation of interlinking completeness for Europeana SPARQL took 0.2672083377838135s
Reputation | Calculation of the PageRank for Europeana SPARQL took 0.020818710327148438s
Interlinking | Calculation of Degree of Connection for Europeana SPARQL took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Europeana SPARQL took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Europeana SPARQL took 4.792213439941406e-05s
Believability | Calculation of trust value for Europeana SPARQL took 6.9141387939453125e-06s
INFO | --- Analysis for europeana-sparql took 4.083274602890015s
Availability | SPARQL endpoint availability check for EuroSentiment took 0.08310365676879883s
Availability | VoID file availability check for EuroSentiment took 0.0003726482391357422s
Completeness | Calculation of interlinking completeness for EuroSentiment took 0.29726743698120117s
Reputation | Calculation of the PageRank for EuroSentiment took 0.02085399627685547s
Interlinking | Calculation of Degree of Connection for EuroSentiment took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for EuroSentiment took 0.0007848739624023438s
Interlinking | Calculation of Clustering coefficient for EuroSentiment took 4.076957702636719e-05s
Believability | Calculation of trust value for EuroSentiment took 7.152557373046875e-06s
INFO | --- Analysis for eurosentiment took 3.180345296859741s
Availability | SPARQL endpoint availability check for Eurostat RDF datasets took 4.76837158203125e-05s
Availability | VoID file availability check for Eurostat RDF datasets took 0.0005557537078857422s
Completeness | Calculation of interlinking completeness for Eurostat RDF datasets took 0.695932149887085s
Reputation | Calculation of the PageRank for Eurostat RDF datasets took 0.020247697830200195s
Interlinking | Calculation of Degree of Connection for Eurostat RDF datasets took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Eurostat RDF datasets took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Eurostat RDF datasets took 7.724761962890625e-05s
Believability | Calculation of trust value for Eurostat RDF datasets took 4.291534423828125e-06s
INFO | --- Analysis for eurostat-rdf took 12.28708267211914s
Availability | SPARQL endpoint availability check for EuroVoc took 0.20376873016357422s
Availability | VoID file availability check for EuroVoc took 0.0006725788116455078s
Extra | Recovery of all triples for EuroVoc took 300.0828900337219s
Performance | Total latancy measurement for EuroVoc took 0.6168820858001709s
Amount of data | Number of triples check for EuroVoc took 169.53013467788696s
Interoperability | New terms check for EuroVoc took 197.74510979652405s
Versatility | Languages check for EuroVoc took 300.1369740962982s
Interpretability | Number of blank nodes check for EuroVoc took 6.225809097290039s
Security | Check HTTPS for EuroVoc took 0.3534255027770996s
Interpretability | RDF structures check for EuroVoc took 1.0999019145965576s
Versatility | Serialization formats check for EuroVoc took 30.534615516662598s
Availability | RDF dump link check for EuroVoc took 0.20136308670043945s
License | MR license check for EuroVoc took 0.26468372344970703s
License | HR license check for EuroVoc took 300.0916838645935s
Amount of data | Number of property check for EuroVoc took 0.18344497680664062s
Understandability | Number of label check for EuroVoc took 6.7642130851745605s
Understandability | URI regex check for EuroVoc took 0.27599072456359863s
Understandability | Vocabs check for EuroVoc took 0.15447354316711426s
Verifiability | Authors check for EuroVoc took 0.24242115020751953s
Verifiability | Publishers check for EuroVoc took 0.33163976669311523s
Performance | Throughput check for EuroVoc took 12.264523267745972s
Amount of data | Check the number of entities for EuroVoc took 7.462501525878906e-05s
Verifiability | Contribs. check for EuroVoc took 0.15599775314331055s
Interlinking | sameAs chians check for EuroVoc took 18.065726280212402s
Interlinking | skos check for EuroVoc took 0.6550867557525635s
Interlinking | skos check for EuroVoc took 0.49199771881103516s
Timeliness | dataset update frequency check for EuroVoc took 0.26218080520629883s
Currency | Creation date check for EuroVoc took 0.3142068386077881s
Currency | Modification date check for EuroVoc took 0.22382497787475586s
Rep.Conc. | URIs length for EuroVoc took 600.1836311817169s
Interoperability | New vocabularies check for EuroVoc took 4.76837158203125e-06s
Consistency | Deprecated classes/propertiers check for EuroVoc took 0.18128681182861328s
Accuracy | Check Functional Property for EuroVoc took 0.18263936042785645s
Accuracy | Check Inverse Functional Property for EuroVoc took 0.1374804973602295s
Accuracy | Check Empty annotation labels for EuroVoc took 142.77271437644958s
Accuracy | Check White space in annotation for EuroVoc took 3.1948909759521484s
Consistency | Disjoint class check for EuroVoc took 0.18959569931030273s
Consistency | Check Misplaced properties for EuroVoc took 300.9890887737274s
Consistency | Misplaced classes for EuroVoc took 0.6595077514648438s
Consistency | Check Ontology hijacking for EuroVoc took 185.73380780220032s
Consistency | Check Invalid usage of undefined properties for EuroVoc took 301.3111710548401s
Conciseness | Check Extensional conciseness for EuroVoc took 0.0002276897430419922s
Conciseness | Check Intensional conciseness for EuroVoc took 2.6697006225585938s
Security | Sign check for EuroVoc took 0.20905089378356934s
Completeness | Calculation of interlinking completeness for EuroVoc took 1.5931601524353027s
Reputation | Calculation of the PageRank for EuroVoc took 0.02089691162109375s
Interlinking | Calculation of Degree of Connection for EuroVoc took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EuroVoc took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for EuroVoc took 9.322166442871094e-05s
Interoperability | Check the re-using of existing vocabs for EuroVoc took 1.6689300537109375e-06s
Believability | Calculation of trust value for EuroVoc took 6.4373016357421875e-06s
INFO | --- Analysis for eurovoc took 16842.260281085968s
Availability | SPARQL endpoint availability check for EUROVOC in SKOS took 4.0531158447265625e-05s
Availability | VoID file availability check for EUROVOC in SKOS took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for EUROVOC in SKOS took 0.27810168266296387s
Reputation | Calculation of the PageRank for EUROVOC in SKOS took 0.020754098892211914s
Interlinking | Calculation of Degree of Connection for EUROVOC in SKOS took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for EUROVOC in SKOS took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for EUROVOC in SKOS took 4.553794860839844e-05s
Believability | Calculation of trust value for EUROVOC in SKOS took 6.9141387939453125e-06s
INFO | --- Analysis for eurovoc-in-skos took 6.144756078720093s
Availability | SPARQL endpoint availability check for European Television Heritage took 3.981590270996094e-05s
Availability | VoID file availability check for European Television Heritage took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for European Television Heritage took 0.24894332885742188s
Reputation | Calculation of the PageRank for European Television Heritage took 0.020249605178833008s
Interlinking | Calculation of Degree of Connection for European Television Heritage took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for European Television Heritage took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for European Television Heritage took 2.9087066650390625e-05s
Believability | Calculation of trust value for European Television Heritage took 6.4373016357421875e-06s
INFO | --- Analysis for euscreen took 5.1717729568481445s
Availability | SPARQL endpoint availability check for Farmacias en Euskadi took 4.220008850097656e-05s
Availability | VoID file availability check for Farmacias en Euskadi took 0.0006165504455566406s
Completeness | Calculation of interlinking completeness for Farmacias en Euskadi took 0.7309389114379883s
Reputation | Calculation of the PageRank for Farmacias en Euskadi took 0.02051568031311035s
Interlinking | Calculation of Degree of Connection for Farmacias en Euskadi took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Farmacias en Euskadi took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Farmacias en Euskadi took 5.8650970458984375e-05s
Believability | Calculation of trust value for Farmacias en Euskadi took 4.76837158203125e-06s
INFO | --- Analysis for euskadi-farmacias took 8.800658226013184s
Availability | SPARQL endpoint availability check for Research outputs of Eastern University Sri Lanka took 0.7733652591705322s
Availability | VoID file availability check for Research outputs of Eastern University Sri Lanka took 0.0005576610565185547s
Completeness | Calculation of interlinking completeness for Research outputs of Eastern University Sri Lanka took 0.2606542110443115s
Reputation | Calculation of the PageRank for Research outputs of Eastern University Sri Lanka took 0.020377397537231445s
Interlinking | Calculation of Degree of Connection for Research outputs of Eastern University Sri Lanka took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Research outputs of Eastern University Sri Lanka took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Research outputs of Eastern University Sri Lanka took 2.9087066650390625e-05s
Believability | Calculation of trust value for Research outputs of Eastern University Sri Lanka took 6.9141387939453125e-06s
INFO | --- Analysis for EUSL-Research-Data-Sri_Lanka took 5.755147218704224s
Availability | SPARQL endpoint availability check for Edinburgh University Theatre Company Productions took 0.41356444358825684s
Availability | VoID file availability check for Edinburgh University Theatre Company Productions took 0.0006432533264160156s
Completeness | Calculation of interlinking completeness for Edinburgh University Theatre Company Productions took 0.27710604667663574s
Reputation | Calculation of the PageRank for Edinburgh University Theatre Company Productions took 0.02031993865966797s
Interlinking | Calculation of Degree of Connection for Edinburgh University Theatre Company Productions took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Edinburgh University Theatre Company Productions took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Edinburgh University Theatre Company Productions took 6.914138793945312e-05s
Believability | Calculation of trust value for Edinburgh University Theatre Company Productions took 6.67572021484375e-06s
INFO | --- Analysis for eutc-productions took 5.875256299972534s
Availability | SPARQL endpoint availability check for EventMedia took 0.4020516872406006s
Availability | VoID file availability check for EventMedia took 0.0006771087646484375s
Completeness | Calculation of interlinking completeness for EventMedia took 0.70339035987854s
Reputation | Calculation of the PageRank for EventMedia took 0.02023792266845703s
Interlinking | Calculation of Degree of Connection for EventMedia took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EventMedia took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for EventMedia took 0.0001049041748046875s
Believability | Calculation of trust value for EventMedia took 5.9604644775390625e-06s
INFO | --- Analysis for event-media took 10.908226728439331s
Availability | SPARQL endpoint availability check for EventKG took 4.315376281738281e-05s
Availability | VoID file availability check for EventKG took 0.0005586147308349609s
Completeness | Calculation of interlinking completeness for EventKG took 0.2527928352355957s
Reputation | Calculation of the PageRank for EventKG took 0.020289897918701172s
Interlinking | Calculation of Degree of Connection for EventKG took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EventKG took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for EventKG took 8.273124694824219e-05s
Believability | Calculation of trust value for EventKG took 5.245208740234375e-06s
INFO | --- Analysis for eventkg took 4.7113494873046875s
Availability | SPARQL endpoint availability check for Eventseer took 0.8461427688598633s
Availability | VoID file availability check for Eventseer took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for Eventseer took 0.26859283447265625s
Reputation | Calculation of the PageRank for Eventseer took 0.02041006088256836s
Interlinking | Calculation of Degree of Connection for Eventseer took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Eventseer took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Eventseer took 4.458427429199219e-05s
Believability | Calculation of trust value for Eventseer took 6.4373016357421875e-06s
INFO | --- Analysis for eventseer took 3.3084495067596436s
Availability | SPARQL endpoint availability check for Face Link took 4.124641418457031e-05s
Availability | VoID file availability check for Face Link took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for Face Link took 0.24538397789001465s
Reputation | Calculation of the PageRank for Face Link took 0.02047872543334961s
Interlinking | Calculation of Degree of Connection for Face Link took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Face Link took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Face Link took 3.2901763916015625e-05s
Believability | Calculation of trust value for Face Link took 6.4373016357421875e-06s
INFO | --- Analysis for Face_Link took 2.3216702938079834s
Availability | SPARQL endpoint availability check for Facebook Linked Data Service took 3.8623809814453125e-05s
Availability | VoID file availability check for Facebook Linked Data Service took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for Facebook Linked Data Service took 0.2701728343963623s
Reputation | Calculation of the PageRank for Facebook Linked Data Service took 0.020296096801757812s
Interlinking | Calculation of Degree of Connection for Facebook Linked Data Service took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Facebook Linked Data Service took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Facebook Linked Data Service took 2.8371810913085938e-05s
Believability | Calculation of trust value for Facebook Linked Data Service took 6.67572021484375e-06s
INFO | --- Analysis for facebook-lids took 2.9962596893310547s
Availability | SPARQL endpoint availability check for Fact Forge took 4.029273986816406e-05s
Availability | VoID file availability check for Fact Forge took 0.00023937225341796875s
Completeness | Calculation of interlinking completeness for Fact Forge took 0.24334335327148438s
Reputation | Calculation of the PageRank for Fact Forge took 0.02045273780822754s
Interlinking | Calculation of Degree of Connection for Fact Forge took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Fact Forge took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Fact Forge took 2.9325485229492188e-05s
Believability | Calculation of trust value for Fact Forge took 7.62939453125e-06s
INFO | --- Analysis for fact-forge took 2.8872475624084473s
Availability | SPARQL endpoint availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.49047017097473145s
Availability | VoID file availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.00024580955505371094s
Extra | Recovery of all triples for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 111.61822938919067s
Performance | Total latancy measurement for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.1496877670288086s
Amount of data | Number of triples check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.192750215530396s
Interoperability | New terms check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 15.129695415496826s
Versatility | Languages check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.22145891189575s
Interpretability | Number of blank nodes check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 3.2136459350585938s
Interpretability | RDF structures check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.28217577934265137s
Versatility | Serialization formats check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 11.125923871994019s
Availability | RDF dump link check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.30327868461608887s
License | MR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5960509777069092s
License | HR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.15448212623596s
Amount of data | Number of property check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.29550671577453613s
Understandability | Number of label check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.8871171474456787s
Understandability | URI regex check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.8521251678466797s
Understandability | Vocabs check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.45081090927124023s
Verifiability | Authors check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.1956479549407959s
Verifiability | Publishers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.2616240978240967s
Performance | Throughput check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 11.062110662460327s
Amount of data | Check the number of entities for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 7.939338684082031e-05s
Verifiability | Contribs. check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.187058687210083s
Interlinking | sameAs chians check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.18593931198120117s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4637148380279541s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.43885207176208496s
Timeliness | dataset update frequency check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 6.06675124168396s
Currency | Creation date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5062668323516846s
Currency | Modification date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.24431920051574707s
Rep.Conc. | URIs length for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 171.45969414710999s
Interoperability | New vocabularies check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.21457552909851074s
Accuracy | Check Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.3862168788909912s
Accuracy | Check Inverse Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.3965930938720703s
Accuracy | Check Empty annotation labels for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 39.047460079193115s
Accuracy | Check White space in annotation for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.7126376628875732s
Accuracy | Check Datatype consistency for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.6470720767974854s
Consistency | Disjoint class check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.1975419521331787s
Consistency | Check Misplaced properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 92.39218187332153s
Consistency | Misplaced classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.557965278625488s
Consistency | Check Ontology hijacking for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 33.57167410850525s
Consistency | Check Invalid usage of undefined classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.2102930545806885s
Consistency | Check Invalid usage of undefined properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 95.69044756889343s
Conciseness | Check Extensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.7325360774993896s
Conciseness | Check Intensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5299069881439209s
Security | Sign check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.8471543788909912s
Availability | Check URIs Dereferenciability for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 5.908529043197632s
Completeness | Calculation of interlinking completeness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.9592025279998779s
Reputation | Calculation of the PageRank for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.020890235900878906s
Interlinking | Calculation of Degree of Connection for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 5.269050598144531e-05s
Interoperability | Check the re-using of existing vocabs for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 6.9141387939453125e-06s
INFO | --- Analysis for FADN_(2019) took 2306.0849413871765s
Availability | SPARQL endpoint availability check for FAMEData took 7.700920104980469e-05s
Availability | VoID file availability check for FAMEData took 0.0007631778717041016s
Completeness | Calculation of interlinking completeness for FAMEData took 0.7133140563964844s
Reputation | Calculation of the PageRank for FAMEData took 0.020816326141357422s
Interlinking | Calculation of Degree of Connection for FAMEData took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FAMEData took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for FAMEData took 2.956390380859375e-05s
Believability | Calculation of trust value for FAMEData took 5.9604644775390625e-06s
INFO | --- Analysis for famedata took 65.20591402053833s
Availability | SPARQL endpoint availability check for FAO geopolitical ontology took 5.4836273193359375e-05s
Availability | VoID file availability check for FAO geopolitical ontology took 0.0006809234619140625s
Completeness | Calculation of interlinking completeness for FAO geopolitical ontology took 0.7011196613311768s
Reputation | Calculation of the PageRank for FAO geopolitical ontology took 0.02042675018310547s
Interlinking | Calculation of Degree of Connection for FAO geopolitical ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FAO geopolitical ontology took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for FAO geopolitical ontology took 9.274482727050781e-05s
Believability | Calculation of trust value for FAO geopolitical ontology took 3.814697265625e-06s
INFO | --- Analysis for fao-geopolitical-ontology took 11.556682825088501s
Availability | SPARQL endpoint availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.5068373680114746s
Availability | VoID file availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0004639625549316406s
Completeness | Calculation of interlinking completeness for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.27686381340026855s
Reputation | Calculation of the PageRank for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.020818233489990234s
Interlinking | Calculation of Degree of Connection for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0001010894775390625s
Believability | Calculation of trust value for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 5.0067901611328125e-06s
INFO | --- Analysis for fao-linked-data took 3.87127685546875s
Availability | SPARQL endpoint availability check for FAO ASFIS classification of biological entities @PSNC took 4.3392181396484375e-05s
Availability | VoID file availability check for FAO ASFIS classification of biological entities @PSNC took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for FAO ASFIS classification of biological entities @PSNC took 0.6972627639770508s
Reputation | Calculation of the PageRank for FAO ASFIS classification of biological entities @PSNC took 0.020466327667236328s
Interlinking | Calculation of Degree of Connection for FAO ASFIS classification of biological entities @PSNC took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FAO ASFIS classification of biological entities @PSNC took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for FAO ASFIS classification of biological entities @PSNC took 3.170967102050781e-05s
Believability | Calculation of trust value for FAO ASFIS classification of biological entities @PSNC took 6.9141387939453125e-06s
INFO | --- Analysis for FAO_species took 3.703382968902588s
Availability | SPARQL endpoint availability check for ChEMBL-RDF (@ Uppsala University) took 20.622809410095215s
Availability | VoID file availability check for ChEMBL-RDF (@ Uppsala University) took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for ChEMBL-RDF (@ Uppsala University) took 0.276456356048584s
Reputation | Calculation of the PageRank for ChEMBL-RDF (@ Uppsala University) took 0.02107858657836914s
Interlinking | Calculation of Degree of Connection for ChEMBL-RDF (@ Uppsala University) took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for ChEMBL-RDF (@ Uppsala University) took 0.0008580684661865234s
Interlinking | Calculation of Clustering coefficient for ChEMBL-RDF (@ Uppsala University) took 4.887580871582031e-05s
Believability | Calculation of trust value for ChEMBL-RDF (@ Uppsala University) took 7.152557373046875e-06s
INFO | --- Analysis for farmbio-chembl took 66.5112738609314s
Availability | SPARQL endpoint availability check for Farmers Markets Geographic Data (United States) took 4.076957702636719e-05s
Availability | VoID file availability check for Farmers Markets Geographic Data (United States) took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for Farmers Markets Geographic Data (United States) took 0.6918723583221436s
Reputation | Calculation of the PageRank for Farmers Markets Geographic Data (United States) took 0.020462751388549805s
Interlinking | Calculation of Degree of Connection for Farmers Markets Geographic Data (United States) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Farmers Markets Geographic Data (United States) took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Farmers Markets Geographic Data (United States) took 3.0040740966796875e-05s
Believability | Calculation of trust value for Farmers Markets Geographic Data (United States) took 5.4836273193359375e-06s
INFO | --- Analysis for farmers-markets-geographic-data-united-states took 4.7941296100616455s
Availability | SPARQL endpoint availability check for FarolApp Streetlight Dataset took 4.029273986816406e-05s
Availability | VoID file availability check for FarolApp Streetlight Dataset took 0.0002262592315673828s
Completeness | Calculation of interlinking completeness for FarolApp Streetlight Dataset took 0.2608940601348877s
Reputation | Calculation of the PageRank for FarolApp Streetlight Dataset took 0.020381689071655273s
Interlinking | Calculation of Degree of Connection for FarolApp Streetlight Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FarolApp Streetlight Dataset took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for FarolApp Streetlight Dataset took 2.956390380859375e-05s
Believability | Calculation of trust value for FarolApp Streetlight Dataset took 5.4836273193359375e-06s
INFO | --- Analysis for farolapp-dataset took 3.3516666889190674s
Availability | SPARQL endpoint availability check for Fatal Traffic Accidents in greek roads took 3.981590270996094e-05s
Availability | VoID file availability check for Fatal Traffic Accidents in greek roads took 0.00022363662719726562s
Completeness | Calculation of interlinking completeness for Fatal Traffic Accidents in greek roads took 0.2764708995819092s
Reputation | Calculation of the PageRank for Fatal Traffic Accidents in greek roads took 0.020254850387573242s
Interlinking | Calculation of Degree of Connection for Fatal Traffic Accidents in greek roads took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Fatal Traffic Accidents in greek roads took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Fatal Traffic Accidents in greek roads took 2.8848648071289062e-05s
Believability | Calculation of trust value for Fatal Traffic Accidents in greek roads took 5.245208740234375e-06s
INFO | --- Analysis for fatal-traffic-accidents-in-greek-roads took 2.940429449081421s
Availability | SPARQL endpoint availability check for I4.0-Onto took 4.267692565917969e-05s
Availability | VoID file availability check for I4.0-Onto took 0.00023245811462402344s
Completeness | Calculation of interlinking completeness for I4.0-Onto took 0.2577946186065674s
Reputation | Calculation of the PageRank for I4.0-Onto took 0.020478010177612305s
Interlinking | Calculation of Degree of Connection for I4.0-Onto took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for I4.0-Onto took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for I4.0-Onto took 2.956390380859375e-05s
Believability | Calculation of trust value for I4.0-Onto took 5.4836273193359375e-06s
INFO | --- Analysis for fatimazahra took 2.810119390487671s
Availability | SPARQL endpoint availability check for Federal Reserve Economic Data RDF took 3.981590270996094e-05s
Availability | VoID file availability check for Federal Reserve Economic Data RDF took 0.00021576881408691406s
Completeness | Calculation of interlinking completeness for Federal Reserve Economic Data RDF took 0.2579991817474365s
Reputation | Calculation of the PageRank for Federal Reserve Economic Data RDF took 0.020637035369873047s
Interlinking | Calculation of Degree of Connection for Federal Reserve Economic Data RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Federal Reserve Economic Data RDF took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Economic Data RDF took 3.409385681152344e-05s
Believability | Calculation of trust value for Federal Reserve Economic Data RDF took 1.0728836059570312e-05s
INFO | --- Analysis for federal-economic-rdf took 3.432424306869507s
Availability | SPARQL endpoint availability check for Feed Wrapper took 3.910064697265625e-05s
Availability | VoID file availability check for Feed Wrapper took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for Feed Wrapper took 0.2590796947479248s
Reputation | Calculation of the PageRank for Feed Wrapper took 0.02048802375793457s
Interlinking | Calculation of Degree of Connection for Feed Wrapper took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Feed Wrapper took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Feed Wrapper took 3.0040740966796875e-05s
Believability | Calculation of trust value for Feed Wrapper took 5.4836273193359375e-06s
INFO | --- Analysis for feedwrapper-lids took 2.981029510498047s
Availability | SPARQL endpoint availability check for FHIR STU3 took 4.6253204345703125e-05s
Availability | VoID file availability check for FHIR STU3 took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for FHIR STU3 took 0.28636956214904785s
Reputation | Calculation of the PageRank for FHIR STU3 took 0.020352602005004883s
Interlinking | Calculation of Degree of Connection for FHIR STU3 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for FHIR STU3 took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for FHIR STU3 took 2.86102294921875e-05s
Believability | Calculation of trust value for FHIR STU3 took 5.7220458984375e-06s
INFO | --- Analysis for FHIR_STU3 took 2.7510807514190674s
Availability | SPARQL endpoint availability check for FiESTA took 4.3392181396484375e-05s
Availability | VoID file availability check for FiESTA took 0.0006704330444335938s
Completeness | Calculation of interlinking completeness for FiESTA took 0.26145482063293457s
Reputation | Calculation of the PageRank for FiESTA took 0.020288467407226562s
Interlinking | Calculation of Degree of Connection for FiESTA took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for FiESTA took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for FiESTA took 3.814697265625e-05s
Believability | Calculation of trust value for FiESTA took 6.198883056640625e-06s
INFO | --- Analysis for fiesta took 13.022531986236572s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 4.3392181396484375e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.25963330268859863s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.020226478576660156s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 2.9325485229492188e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 7.152557373046875e-06s
INFO | --- Analysis for file:C:UsersaDesktopurn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976.owl took 2.7159268856048584s
Availability | SPARQL endpoint availability check for Finnish municipalities and regional classifications took 4.100799560546875e-05s
Availability | VoID file availability check for Finnish municipalities and regional classifications took 0.0005872249603271484s
Completeness | Calculation of interlinking completeness for Finnish municipalities and regional classifications took 0.2511909008026123s
Reputation | Calculation of the PageRank for Finnish municipalities and regional classifications took 0.0203244686126709s
Interlinking | Calculation of Degree of Connection for Finnish municipalities and regional classifications took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Finnish municipalities and regional classifications took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Finnish municipalities and regional classifications took 6.747245788574219e-05s
Believability | Calculation of trust value for Finnish municipalities and regional classifications took 4.291534423828125e-06s
INFO | --- Analysis for finnish-municipalities took 3.3824212551116943s
Availability | SPARQL endpoint availability check for firmao took 4.100799560546875e-05s
Availability | VoID file availability check for firmao took 0.0003662109375s
Completeness | Calculation of interlinking completeness for firmao took 0.2872598171234131s
Reputation | Calculation of the PageRank for firmao took 0.02064061164855957s
Interlinking | Calculation of Degree of Connection for firmao took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for firmao took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for firmao took 3.1948089599609375e-05s
Believability | Calculation of trust value for firmao took 6.198883056640625e-06s
INFO | --- Analysis for firmao took 2.8792290687561035s
Availability | SPARQL endpoint availability check for FISH Archaeological Objects Thesaurus took 4.00543212890625e-05s
Availability | VoID file availability check for FISH Archaeological Objects Thesaurus took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for FISH Archaeological Objects Thesaurus took 0.2611367702484131s
Reputation | Calculation of the PageRank for FISH Archaeological Objects Thesaurus took 0.02028179168701172s
Interlinking | Calculation of Degree of Connection for FISH Archaeological Objects Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FISH Archaeological Objects Thesaurus took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for FISH Archaeological Objects Thesaurus took 2.9325485229492188e-05s
Believability | Calculation of trust value for FISH Archaeological Objects Thesaurus took 6.4373016357421875e-06s
INFO | --- Analysis for fish-archaeological-objects-thesaurus took 2.8578875064849854s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset @PSNC took 0.21316051483154297s
Availability | VoID file availability check for Norway fishery stocks dataset @PSNC took 0.0002608299255371094s
Extra | Recovery of all triples for Norway fishery stocks dataset @PSNC took 114.96759629249573s
Performance | Total latancy measurement for Norway fishery stocks dataset @PSNC took 0.988616943359375s
Amount of data | Number of triples check for Norway fishery stocks dataset @PSNC took 9.35892391204834s
Interoperability | New terms check for Norway fishery stocks dataset @PSNC took 13.776122331619263s
Versatility | Languages check for Norway fishery stocks dataset @PSNC took 300.203462600708s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset @PSNC took 3.0863685607910156s
Interpretability | RDF structures check for Norway fishery stocks dataset @PSNC took 0.26885318756103516s
Versatility | Serialization formats check for Norway fishery stocks dataset @PSNC took 9.94185757637024s
Availability | RDF dump link check for Norway fishery stocks dataset @PSNC took 0.3057372570037842s
License | MR license check for Norway fishery stocks dataset @PSNC took 0.6614203453063965s
License | HR license check for Norway fishery stocks dataset @PSNC took 300.2585051059723s
Amount of data | Number of property check for Norway fishery stocks dataset @PSNC took 0.19938445091247559s
Understandability | Number of label check for Norway fishery stocks dataset @PSNC took 2.5476832389831543s
Understandability | URI regex check for Norway fishery stocks dataset @PSNC took 0.7590253353118896s
Understandability | Vocabs check for Norway fishery stocks dataset @PSNC took 0.4967679977416992s
Verifiability | Authors check for Norway fishery stocks dataset @PSNC took 0.1865377426147461s
Verifiability | Publishers check for Norway fishery stocks dataset @PSNC took 0.24033570289611816s
Performance | Throughput check for Norway fishery stocks dataset @PSNC took 11.519413948059082s
Amount of data | Check the number of entities for Norway fishery stocks dataset @PSNC took 0.00010800361633300781s
Verifiability | Contribs. check for Norway fishery stocks dataset @PSNC took 0.18361902236938477s
Interlinking | sameAs chians check for Norway fishery stocks dataset @PSNC took 0.2012312412261963s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.5656123161315918s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.446108341217041s
Timeliness | dataset update frequency check for Norway fishery stocks dataset @PSNC took 7.4404637813568115s
Currency | Creation date check for Norway fishery stocks dataset @PSNC took 0.5129756927490234s
Currency | Modification date check for Norway fishery stocks dataset @PSNC took 0.234574556350708s
Rep.Conc. | URIs length for Norway fishery stocks dataset @PSNC took 152.35802102088928s
Interoperability | New vocabularies check for Norway fishery stocks dataset @PSNC took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset @PSNC took 0.19655084609985352s
Accuracy | Check Functional Property for Norway fishery stocks dataset @PSNC took 0.34888672828674316s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset @PSNC took 0.3429694175720215s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset @PSNC took 38.02895998954773s
Accuracy | Check White space in annotation for Norway fishery stocks dataset @PSNC took 2.71053409576416s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset @PSNC took 2.6065571308135986s
Consistency | Disjoint class check for Norway fishery stocks dataset @PSNC took 0.1803445816040039s
Consistency | Check Misplaced properties for Norway fishery stocks dataset @PSNC took 90.22609829902649s
Consistency | Misplaced classes for Norway fishery stocks dataset @PSNC took 8.884324550628662s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset @PSNC took 36.02248930931091s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset @PSNC took 1.287785530090332s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset @PSNC took 91.32820677757263s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset @PSNC took 2.6771671772003174s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset @PSNC took 0.5638673305511475s
Security | Sign check for Norway fishery stocks dataset @PSNC took 0.1952369213104248s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset @PSNC took 5.590301275253296s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset @PSNC took 0.5253341197967529s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset @PSNC took 0.020579814910888672s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset @PSNC took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset @PSNC took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset @PSNC took 5.91278076171875e-05s
Interoperability | Check the re-using of existing vocabs for Norway fishery stocks dataset @PSNC took 1.1920928955078125e-06s
Believability | Calculation of trust value for Norway fishery stocks dataset @PSNC took 6.67572021484375e-06s
INFO | --- Analysis for Fishery_Stock_Dataset took 2269.8059542179108s
Availability | SPARQL endpoint availability check for Fishes of Texas took 4.863739013671875e-05s
Availability | VoID file availability check for Fishes of Texas took 0.0007073879241943359s
Completeness | Calculation of interlinking completeness for Fishes of Texas took 0.2702631950378418s
Reputation | Calculation of the PageRank for Fishes of Texas took 0.02111053466796875s
Interlinking | Calculation of Degree of Connection for Fishes of Texas took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Fishes of Texas took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Fishes of Texas took 8.630752563476562e-05s
Believability | Calculation of trust value for Fishes of Texas took 6.4373016357421875e-06s
INFO | --- Analysis for fishes-of-texas took 2.8879168033599854s
Availability | SPARQL endpoint availability check for flickr? wrappr took 4.1961669921875e-05s
Availability | VoID file availability check for flickr? wrappr took 0.0005426406860351562s
Completeness | Calculation of interlinking completeness for flickr? wrappr took 0.2607266902923584s
Reputation | Calculation of the PageRank for flickr? wrappr took 0.020496129989624023s
Interlinking | Calculation of Degree of Connection for flickr? wrappr took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for flickr? wrappr took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for flickr? wrappr took 9.560585021972656e-05s
Believability | Calculation of trust value for flickr? wrappr took 6.9141387939453125e-06s
INFO | --- Analysis for flickr-wrappr took 3.934595823287964s
Availability | SPARQL endpoint availability check for flickr.person took 4.172325134277344e-05s
Availability | VoID file availability check for flickr.person took 0.0002262592315673828s
Completeness | Calculation of interlinking completeness for flickr.person took 0.25940465927124023s
Reputation | Calculation of the PageRank for flickr.person took 0.02411818504333496s
Interlinking | Calculation of Degree of Connection for flickr.person took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for flickr.person took 0.001718282699584961s
Interlinking | Calculation of Clustering coefficient for flickr.person took 5.316734313964844e-05s
Believability | Calculation of trust value for flickr.person took 8.106231689453125e-06s
INFO | --- Analysis for flickr_person took 3.0656721591949463s
Availability | SPARQL endpoint availability check for flickr.videoobject took 4.00543212890625e-05s
Availability | VoID file availability check for flickr.videoobject took 0.00027823448181152344s
Completeness | Calculation of interlinking completeness for flickr.videoobject took 0.28472018241882324s
Reputation | Calculation of the PageRank for flickr.videoobject took 0.020399093627929688s
Interlinking | Calculation of Degree of Connection for flickr.videoobject took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for flickr.videoobject took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for flickr.videoobject took 2.9325485229492188e-05s
Believability | Calculation of trust value for flickr.videoobject took 5.7220458984375e-06s
INFO | --- Analysis for flickr_videoobject took 3.0588536262512207s
Availability | SPARQL endpoint availability check for Future land use simulation model took 4.267692565917969e-05s
Availability | VoID file availability check for Future land use simulation model took 0.0006511211395263672s
Completeness | Calculation of interlinking completeness for Future land use simulation model took 0.27233052253723145s
Reputation | Calculation of the PageRank for Future land use simulation model took 0.02069854736328125s
Interlinking | Calculation of Degree of Connection for Future land use simulation model took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Future land use simulation model took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Future land use simulation model took 3.0994415283203125e-05s
Believability | Calculation of trust value for Future land use simulation model took 8.106231689453125e-06s
INFO | --- Analysis for FLUS took 8.945282220840454s
Availability | SPARQL endpoint availability check for Fly-TED took 4.38690185546875e-05s
Availability | VoID file availability check for Fly-TED took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for Fly-TED took 0.2643899917602539s
Reputation | Calculation of the PageRank for Fly-TED took 0.020158052444458008s
Interlinking | Calculation of Degree of Connection for Fly-TED took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Fly-TED took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Fly-TED took 3.0279159545898438e-05s
Believability | Calculation of trust value for Fly-TED took 5.4836273193359375e-06s
INFO | --- Analysis for fly-ted took 2.9601187705993652s
Availability | SPARQL endpoint availability check for FlyAtlas took 3.886222839355469e-05s
Availability | VoID file availability check for FlyAtlas took 0.00023245811462402344s
Completeness | Calculation of interlinking completeness for FlyAtlas took 0.26021289825439453s
Reputation | Calculation of the PageRank for FlyAtlas took 0.020497798919677734s
Interlinking | Calculation of Degree of Connection for FlyAtlas took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for FlyAtlas took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for FlyAtlas took 3.0994415283203125e-05s
Believability | Calculation of trust value for FlyAtlas took 5.9604644775390625e-06s
INFO | --- Analysis for flyatlas took 2.9163694381713867s
Availability | SPARQL endpoint availability check for Flybase took 1.824599266052246s
Availability | VoID file availability check for Flybase took 0.0007145404815673828s
Completeness | Calculation of interlinking completeness for Flybase took 0.2809464931488037s
Reputation | Calculation of the PageRank for Flybase took 0.020497560501098633s
Interlinking | Calculation of Degree of Connection for Flybase took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Flybase took 0.0007855892181396484s
Interlinking | Calculation of Clustering coefficient for Flybase took 3.457069396972656e-05s
Believability | Calculation of trust value for Flybase took 7.3909759521484375e-06s
INFO | --- Analysis for flybase took 10.329118728637695s
Availability | SPARQL endpoint availability check for Flyted took 1.228694200515747s
Availability | VoID file availability check for Flyted took 0.0013298988342285156s
Completeness | Calculation of interlinking completeness for Flyted took 0.2828524112701416s
Reputation | Calculation of the PageRank for Flyted took 0.020377397537231445s
Interlinking | Calculation of Degree of Connection for Flyted took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Flyted took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Flyted took 2.765655517578125e-05s
Believability | Calculation of trust value for Flyted took 5.4836273193359375e-06s
INFO | --- Analysis for flyted took 11.293753385543823s
Availability | SPARQL endpoint availability check for Foodista took 0.9532372951507568s
Availability | VoID file availability check for Foodista took 0.00043582916259765625s
Completeness | Calculation of interlinking completeness for Foodista took 0.25939035415649414s
Reputation | Calculation of the PageRank for Foodista took 0.020299911499023438s
Interlinking | Calculation of Degree of Connection for Foodista took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Foodista took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Foodista took 2.7894973754882812e-05s
Believability | Calculation of trust value for Foodista took 6.67572021484375e-06s
INFO | --- Analysis for foodista took 9.826821327209473s
Availability | SPARQL endpoint availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.17872953414916992s
Availability | VoID file availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0003573894500732422s
Completeness | Calculation of interlinking completeness for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.25720739364624023s
Reputation | Calculation of the PageRank for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.02015995979309082s
Interlinking | Calculation of Degree of Connection for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.009506225585938e-05s
Believability | Calculation of trust value for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.62939453125e-06s
INFO | --- Analysis for foodpedia took 2.637812376022339s
Availability | SPARQL endpoint availability check for FORGE Course information took 4.649162292480469e-05s
Availability | VoID file availability check for FORGE Course information took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for FORGE Course information took 0.26060009002685547s
Reputation | Calculation of the PageRank for FORGE Course information took 0.021049976348876953s
Interlinking | Calculation of Degree of Connection for FORGE Course information took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for FORGE Course information took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for FORGE Course information took 3.24249267578125e-05s
Believability | Calculation of trust value for FORGE Course information took 7.3909759521484375e-06s
INFO | --- Analysis for forge-course-information took 2.9605259895324707s
Availability | SPARQL endpoint availability check for FrameBase schema took 4.1961669921875e-05s
Availability | VoID file availability check for FrameBase schema took 0.0006847381591796875s
Completeness | Calculation of interlinking completeness for FrameBase schema took 0.30005693435668945s
Reputation | Calculation of the PageRank for FrameBase schema took 0.02062082290649414s
Interlinking | Calculation of Degree of Connection for FrameBase schema took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for FrameBase schema took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for FrameBase schema took 4.458427429199219e-05s
Believability | Calculation of trust value for FrameBase schema took 6.4373016357421875e-06s
INFO | --- Analysis for framebase-schema took 3.0235605239868164s
Availability | SPARQL endpoint availability check for FrameNet took 3.981590270996094e-05s
Availability | VoID file availability check for FrameNet took 0.0002238750457763672s
Completeness | Calculation of interlinking completeness for FrameNet took 0.25838613510131836s
Reputation | Calculation of the PageRank for FrameNet took 0.020597457885742188s
Interlinking | Calculation of Degree of Connection for FrameNet took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FrameNet took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for FrameNet took 3.0279159545898438e-05s
Believability | Calculation of trust value for FrameNet took 6.4373016357421875e-06s
INFO | --- Analysis for framenet took 2.9067537784576416s
Availability | SPARQL endpoint availability check for Framester took 4.3392181396484375e-05s
Availability | VoID file availability check for Framester took 0.0005636215209960938s
Completeness | Calculation of interlinking completeness for Framester took 0.2591390609741211s
Reputation | Calculation of the PageRank for Framester took 0.021071910858154297s
Interlinking | Calculation of Degree of Connection for Framester took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Framester took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Framester took 8.0108642578125e-05s
Believability | Calculation of trust value for Framester took 6.198883056640625e-06s
INFO | --- Analysis for framester took 52.999526023864746s
Availability | SPARQL endpoint availability check for Federal Reserve Board (FRB) Linked Data took 0.15428686141967773s
Availability | VoID file availability check for Federal Reserve Board (FRB) Linked Data took 0.00022673606872558594s
Completeness | Calculation of interlinking completeness for Federal Reserve Board (FRB) Linked Data took 0.2779209613800049s
Reputation | Calculation of the PageRank for Federal Reserve Board (FRB) Linked Data took 0.02057051658630371s
Interlinking | Calculation of Degree of Connection for Federal Reserve Board (FRB) Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Federal Reserve Board (FRB) Linked Data took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Board (FRB) Linked Data took 9.036064147949219e-05s
Believability | Calculation of trust value for Federal Reserve Board (FRB) Linked Data took 5.9604644775390625e-06s
INFO | --- Analysis for frb-linked-data took 2.593794345855713s
Availability | SPARQL endpoint availability check for Freebase took 4.57763671875e-05s
Availability | VoID file availability check for Freebase took 0.0004277229309082031s
Completeness | Calculation of interlinking completeness for Freebase took 0.2644691467285156s
Reputation | Calculation of the PageRank for Freebase took 0.020390748977661133s
Interlinking | Calculation of Degree of Connection for Freebase took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Freebase took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Freebase took 0.00026917457580566406s
Believability | Calculation of trust value for Freebase took 5.7220458984375e-06s
INFO | --- Analysis for freebase took 4.306342601776123s
Availability | SPARQL endpoint availability check for Freeyork took 4.029273986816406e-05s
Availability | VoID file availability check for Freeyork took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for Freeyork took 0.2648015022277832s
Reputation | Calculation of the PageRank for Freeyork took 0.020435810089111328s
Interlinking | Calculation of Degree of Connection for Freeyork took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Freeyork took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Freeyork took 0.00010538101196289062s
Believability | Calculation of trust value for Freeyork took 7.152557373046875e-06s
INFO | --- Analysis for freeyork-org took 5.000874757766724s
Availability | SPARQL endpoint availability check for French School Program took 4.00543212890625e-05s
Availability | VoID file availability check for French School Program took 0.000274658203125s
Completeness | Calculation of interlinking completeness for French School Program took 0.27927303314208984s
Reputation | Calculation of the PageRank for French School Program took 0.020554065704345703s
Interlinking | Calculation of Degree of Connection for French School Program took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for French School Program took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for French School Program took 3.075599670410156e-05s
Believability | Calculation of trust value for French School Program took 6.198883056640625e-06s
INFO | --- Analysis for french-school-program took 3.0612335205078125s
Availability | SPARQL endpoint availability check for French School System took 4.029273986816406e-05s
Availability | VoID file availability check for French School System took 0.00027823448181152344s
Completeness | Calculation of interlinking completeness for French School System took 0.26059699058532715s
Reputation | Calculation of the PageRank for French School System took 0.0204770565032959s
Interlinking | Calculation of Degree of Connection for French School System took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for French School System took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for French School System took 3.0040740966796875e-05s
Believability | Calculation of trust value for French School System took 6.9141387939453125e-06s
INFO | --- Analysis for french-school-system took 2.9254727363586426s
Availability | SPARQL endpoint availability check for French TimeBank took 4.100799560546875e-05s
Availability | VoID file availability check for French TimeBank took 0.0002799034118652344s
Completeness | Calculation of interlinking completeness for French TimeBank took 0.2620658874511719s
Reputation | Calculation of the PageRank for French TimeBank took 0.02069711685180664s
Interlinking | Calculation of Degree of Connection for French TimeBank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for French TimeBank took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for French TimeBank took 3.147125244140625e-05s
Believability | Calculation of trust value for French TimeBank took 7.62939453125e-06s
INFO | --- Analysis for french-timebank took 2.9596059322357178s
Availability | SPARQL endpoint availability check for Community Research and Development Information Service (CORDIS) took 0.7106571197509766s
Availability | VoID file availability check for Community Research and Development Information Service (CORDIS) took 0.0005695819854736328s
Completeness | Calculation of interlinking completeness for Community Research and Development Information Service (CORDIS) took 0.28070998191833496s
Reputation | Calculation of the PageRank for Community Research and Development Information Service (CORDIS) took 0.028812170028686523s
Interlinking | Calculation of Degree of Connection for Community Research and Development Information Service (CORDIS) took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Community Research and Development Information Service (CORDIS) took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Community Research and Development Information Service (CORDIS) took 9.298324584960938e-05s
Believability | Calculation of trust value for Community Research and Development Information Service (CORDIS) took 5.7220458984375e-06s
INFO | --- Analysis for fu-berlin-cordis took 4.354112386703491s
Availability | SPARQL endpoint availability check for DailyMed took 0.6846773624420166s
Availability | VoID file availability check for DailyMed took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for DailyMed took 0.2770259380340576s
Reputation | Calculation of the PageRank for DailyMed took 0.02061176300048828s
Interlinking | Calculation of Degree of Connection for DailyMed took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DailyMed took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for DailyMed took 9.870529174804688e-05s
Believability | Calculation of trust value for DailyMed took 6.4373016357421875e-06s
INFO | --- Analysis for fu-berlin-dailymed took 5.5678932666778564s
Availability | SPARQL endpoint availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.689638614654541s
Availability | VoID file availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.0005578994750976562s
Completeness | Calculation of interlinking completeness for DBLP Bibliography Database in RDF (FU Berlin) took 0.28630900382995605s
Reputation | Calculation of the PageRank for DBLP Bibliography Database in RDF (FU Berlin) took 0.020596742630004883s
Interlinking | Calculation of Degree of Connection for DBLP Bibliography Database in RDF (FU Berlin) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DBLP Bibliography Database in RDF (FU Berlin) took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for DBLP Bibliography Database in RDF (FU Berlin) took 8.416175842285156e-05s
Believability | Calculation of trust value for DBLP Bibliography Database in RDF (FU Berlin) took 6.198883056640625e-06s
INFO | --- Analysis for fu-berlin-dblp took 4.364706516265869s
Availability | SPARQL endpoint availability check for Diseasome took 0.7086522579193115s
Availability | VoID file availability check for Diseasome took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for Diseasome took 0.26949477195739746s
Reputation | Calculation of the PageRank for Diseasome took 0.02039361000061035s
Interlinking | Calculation of Degree of Connection for Diseasome took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Diseasome took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Diseasome took 0.00011014938354492188s
Believability | Calculation of trust value for Diseasome took 6.198883056640625e-06s
INFO | --- Analysis for fu-berlin-diseasome took 5.569630146026611s
Availability | SPARQL endpoint availability check for DrugBank took 0.6892859935760498s
Availability | VoID file availability check for DrugBank took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for DrugBank took 0.2705838680267334s
Reputation | Calculation of the PageRank for DrugBank took 0.020608901977539062s
Interlinking | Calculation of Degree of Connection for DrugBank took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DrugBank took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for DrugBank took 0.00011324882507324219s
Believability | Calculation of trust value for DrugBank took 5.0067901611328125e-06s
INFO | --- Analysis for fu-berlin-drugbank took 5.462096691131592s
Availability | SPARQL endpoint availability check for European Commission Competition data set (FU Berlin) took 0.6958975791931152s
Availability | VoID file availability check for European Commission Competition data set (FU Berlin) took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for European Commission Competition data set (FU Berlin) took 0.2733430862426758s
Reputation | Calculation of the PageRank for European Commission Competition data set (FU Berlin) took 0.020351171493530273s
Interlinking | Calculation of Degree of Connection for European Commission Competition data set (FU Berlin) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for European Commission Competition data set (FU Berlin) took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for European Commission Competition data set (FU Berlin) took 3.0279159545898438e-05s
Believability | Calculation of trust value for European Commission Competition data set (FU Berlin) took 6.198883056640625e-06s
INFO | --- Analysis for fu-berlin-ec-competition took 4.383059978485107s
Availability | SPARQL endpoint availability check for EURAXESS - Researchers in Motion took 0.7071502208709717s
Availability | VoID file availability check for EURAXESS - Researchers in Motion took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for EURAXESS - Researchers in Motion took 0.2538912296295166s
Reputation | Calculation of the PageRank for EURAXESS - Researchers in Motion took 0.02048778533935547s
Interlinking | Calculation of Degree of Connection for EURAXESS - Researchers in Motion took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EURAXESS - Researchers in Motion took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for EURAXESS - Researchers in Motion took 7.271766662597656e-05s
Believability | Calculation of trust value for EURAXESS - Researchers in Motion took 5.4836273193359375e-06s
INFO | --- Analysis for fu-berlin-euraxess took 4.346514940261841s
Availability | SPARQL endpoint availability check for European Employment Services (EURES) took 0.9193248748779297s
Availability | VoID file availability check for European Employment Services (EURES) took 0.0005741119384765625s
Completeness | Calculation of interlinking completeness for European Employment Services (EURES) took 0.2887897491455078s
Reputation | Calculation of the PageRank for European Employment Services (EURES) took 0.020235300064086914s
Interlinking | Calculation of Degree of Connection for European Employment Services (EURES) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for European Employment Services (EURES) took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for European Employment Services (EURES) took 7.581710815429688e-05s
Believability | Calculation of trust value for European Employment Services (EURES) took 5.0067901611328125e-06s
INFO | --- Analysis for fu-berlin-eures took 4.604963064193726s
Availability | SPARQL endpoint availability check for Eurostat in RDF (FU Berlin) took 0.7169835567474365s
Availability | VoID file availability check for Eurostat in RDF (FU Berlin) took 0.0005669593811035156s
Completeness | Calculation of interlinking completeness for Eurostat in RDF (FU Berlin) took 0.2932088375091553s
Reputation | Calculation of the PageRank for Eurostat in RDF (FU Berlin) took 0.020114660263061523s
Interlinking | Calculation of Degree of Connection for Eurostat in RDF (FU Berlin) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Eurostat in RDF (FU Berlin) took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Eurostat in RDF (FU Berlin) took 9.584426879882812e-05s
Believability | Calculation of trust value for Eurostat in RDF (FU Berlin) took 5.7220458984375e-06s
INFO | --- Analysis for fu-berlin-eurostat took 5.110102653503418s
Availability | SPARQL endpoint availability check for MediCare took 0.6792862415313721s
Availability | VoID file availability check for MediCare took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for MediCare took 0.26383328437805176s
Reputation | Calculation of the PageRank for MediCare took 0.02022838592529297s
Interlinking | Calculation of Degree of Connection for MediCare took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MediCare took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for MediCare took 4.100799560546875e-05s
Believability | Calculation of trust value for MediCare took 7.3909759521484375e-06s
INFO | --- Analysis for fu-berlin-medicare took 4.903364896774292s
Availability | SPARQL endpoint availability check for Project Gutenberg in RDF (FU Berlin) took 0.695544958114624s
Availability | VoID file availability check for Project Gutenberg in RDF (FU Berlin) took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for Project Gutenberg in RDF (FU Berlin) took 0.2619650363922119s
Reputation | Calculation of the PageRank for Project Gutenberg in RDF (FU Berlin) took 0.020106792449951172s
Interlinking | Calculation of Degree of Connection for Project Gutenberg in RDF (FU Berlin) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Project Gutenberg in RDF (FU Berlin) took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg in RDF (FU Berlin) took 6.985664367675781e-05s
Believability | Calculation of trust value for Project Gutenberg in RDF (FU Berlin) took 6.67572021484375e-06s
INFO | --- Analysis for fu-berlin-project-gutenberg took 4.324387550354004s
Availability | SPARQL endpoint availability check for SIDER: Side Effect Resource took 0.6936752796173096s
Availability | VoID file availability check for SIDER: Side Effect Resource took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for SIDER: Side Effect Resource took 0.25339436531066895s
Reputation | Calculation of the PageRank for SIDER: Side Effect Resource took 0.02052903175354004s
Interlinking | Calculation of Degree of Connection for SIDER: Side Effect Resource took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for SIDER: Side Effect Resource took 0.0009262561798095703s
Interlinking | Calculation of Clustering coefficient for SIDER: Side Effect Resource took 0.00010609626770019531s
Believability | Calculation of trust value for SIDER: Side Effect Resource took 7.3909759521484375e-06s
INFO | --- Analysis for fu-berlin-sider took 4.970492839813232s
Availability | SPARQL endpoint availability check for STITCH: Chemical-Protein Interactions took 0.7156822681427002s
Availability | VoID file availability check for STITCH: Chemical-Protein Interactions took 0.00048828125s
Completeness | Calculation of interlinking completeness for STITCH: Chemical-Protein Interactions took 0.2407526969909668s
Reputation | Calculation of the PageRank for STITCH: Chemical-Protein Interactions took 0.020017385482788086s
Interlinking | Calculation of Degree of Connection for STITCH: Chemical-Protein Interactions took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for STITCH: Chemical-Protein Interactions took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for STITCH: Chemical-Protein Interactions took 7.319450378417969e-05s
Believability | Calculation of trust value for STITCH: Chemical-Protein Interactions took 5.7220458984375e-06s
INFO | --- Analysis for fu-berlin-stitch took 4.378767728805542s
Availability | SPARQL endpoint availability check for fvdb took 4.076957702636719e-05s
Availability | VoID file availability check for fvdb took 0.0005693435668945312s
Completeness | Calculation of interlinking completeness for fvdb took 0.2671632766723633s
Reputation | Calculation of the PageRank for fvdb took 0.020535707473754883s
Interlinking | Calculation of Degree of Connection for fvdb took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for fvdb took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for fvdb took 3.0517578125e-05s
Believability | Calculation of trust value for fvdb took 5.245208740234375e-06s
INFO | --- Analysis for fv took 12.515787363052368s
Availability | SPARQL endpoint availability check for Global Agricultural Concept Space took 4.1961669921875e-05s
Availability | VoID file availability check for Global Agricultural Concept Space took 0.0006554126739501953s
Completeness | Calculation of interlinking completeness for Global Agricultural Concept Space took 0.28432703018188477s
Reputation | Calculation of the PageRank for Global Agricultural Concept Space took 0.020183563232421875s
Interlinking | Calculation of Degree of Connection for Global Agricultural Concept Space took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Global Agricultural Concept Space took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Global Agricultural Concept Space took 2.7418136596679688e-05s
Believability | Calculation of trust value for Global Agricultural Concept Space took 7.3909759521484375e-06s
INFO | --- Analysis for GACS took 3.163081645965576s
Availability | SPARQL endpoint availability check for Galen from co-ode.org took 3.910064697265625e-05s
Availability | VoID file availability check for Galen from co-ode.org took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for Galen from co-ode.org took 0.266711950302124s
Reputation | Calculation of the PageRank for Galen from co-ode.org took 0.020338773727416992s
Interlinking | Calculation of Degree of Connection for Galen from co-ode.org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Galen from co-ode.org took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Galen from co-ode.org took 2.8371810913085938e-05s
Believability | Calculation of trust value for Galen from co-ode.org took 6.4373016357421875e-06s
INFO | --- Analysis for galen_from_co-odeorg took 2.9497482776641846s
Availability | SPARQL endpoint availability check for Galician EuroWordNet-lemon lexicon (3.0) took 4.38690185546875e-05s
Availability | VoID file availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Galician EuroWordNet-lemon lexicon (3.0) took 0.24662041664123535s
Reputation | Calculation of the PageRank for Galician EuroWordNet-lemon lexicon (3.0) took 0.020562171936035156s
Interlinking | Calculation of Degree of Connection for Galician EuroWordNet-lemon lexicon (3.0) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Galician EuroWordNet-lemon lexicon (3.0) took 0.0008184909820556641s
Interlinking | Calculation of Clustering coefficient for Galician EuroWordNet-lemon lexicon (3.0) took 4.553794860839844e-05s
Believability | Calculation of trust value for Galician EuroWordNet-lemon lexicon (3.0) took 8.58306884765625e-06s
INFO | --- Analysis for galician-eurowordnet-lemon-lexicon-3-0 took 5.535787105560303s
Availability | SPARQL endpoint availability check for Garnica Plywood Catalogue took 4.124641418457031e-05s
Availability | VoID file availability check for Garnica Plywood Catalogue took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for Garnica Plywood Catalogue took 0.30135416984558105s
Reputation | Calculation of the PageRank for Garnica Plywood Catalogue took 0.020531177520751953s
Interlinking | Calculation of Degree of Connection for Garnica Plywood Catalogue took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Garnica Plywood Catalogue took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Garnica Plywood Catalogue took 9.751319885253906e-05s
Believability | Calculation of trust value for Garnica Plywood Catalogue took 6.9141387939453125e-06s
INFO | --- Analysis for garnicaplywood took 2.6606063842773438s
Availability | SPARQL endpoint availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 4.267692565917969e-05s
Availability | VoID file availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.3158881664276123s
Reputation | Calculation of the PageRank for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.02082061767578125s
Interlinking | Calculation of Degree of Connection for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.00010275840759277344s
Believability | Calculation of trust value for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 7.867813110351562e-06s
INFO | --- Analysis for gemeenschappelijke-thesaurus-audiovisuele-archieven took 63.27166962623596s
Availability | SPARQL endpoint availability check for GEneral Multilingual Environmental Thesaurus took 0.2936534881591797s
Availability | VoID file availability check for GEneral Multilingual Environmental Thesaurus took 0.0005853176116943359s
Completeness | Calculation of interlinking completeness for GEneral Multilingual Environmental Thesaurus took 0.2758920192718506s
Reputation | Calculation of the PageRank for GEneral Multilingual Environmental Thesaurus took 0.020119667053222656s
Interlinking | Calculation of Degree of Connection for GEneral Multilingual Environmental Thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for GEneral Multilingual Environmental Thesaurus took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for GEneral Multilingual Environmental Thesaurus took 0.00010585784912109375s
Believability | Calculation of trust value for GEneral Multilingual Environmental Thesaurus took 8.344650268554688e-06s
INFO | --- Analysis for gemet took 20.280295610427856s
Availability | SPARQL endpoint availability check for gemet-annotated took 4.124641418457031e-05s
Availability | VoID file availability check for gemet-annotated took 0.0006678104400634766s
Completeness | Calculation of interlinking completeness for gemet-annotated took 0.2919487953186035s
Reputation | Calculation of the PageRank for gemet-annotated took 0.020420312881469727s
Interlinking | Calculation of Degree of Connection for gemet-annotated took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for gemet-annotated took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for gemet-annotated took 3.838539123535156e-05s
Believability | Calculation of trust value for gemet-annotated took 7.152557373046875e-06s
INFO | --- Analysis for gemet-annotated took 3.0185067653656006s
Availability | SPARQL endpoint availability check for Gene Expression Atlas RDF took 0.9291877746582031s
Availability | VoID file availability check for Gene Expression Atlas RDF took 0.0008533000946044922s
Completeness | Calculation of interlinking completeness for Gene Expression Atlas RDF took 0.2678089141845703s
Reputation | Calculation of the PageRank for Gene Expression Atlas RDF took 0.020255088806152344s
Interlinking | Calculation of Degree of Connection for Gene Expression Atlas RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Gene Expression Atlas RDF took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Gene Expression Atlas RDF took 3.528594970703125e-05s
Believability | Calculation of trust value for Gene Expression Atlas RDF took 8.344650268554688e-06s
INFO | --- Analysis for gene-expression-atlas-rdf took 4.82060170173645s
Availability | SPARQL endpoint availability check for Super Ontology took 0.3887522220611572s
Availability | VoID file availability check for Super Ontology took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.26535463333129883s
Reputation | Calculation of the PageRank for Super Ontology took 0.020189285278320312s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 3.075599670410156e-05s
Believability | Calculation of trust value for Super Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for Generalized_Super_Ontology took 8.876360893249512s
Availability | SPARQL endpoint availability check for geo.place took 4.00543212890625e-05s
Availability | VoID file availability check for geo.place took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for geo.place took 0.25094032287597656s
Reputation | Calculation of the PageRank for geo.place took 0.020251750946044922s
Interlinking | Calculation of Degree of Connection for geo.place took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for geo.place took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for geo.place took 2.86102294921875e-05s
Believability | Calculation of trust value for geo.place took 5.245208740234375e-06s
INFO | --- Analysis for geo_place took 2.8998234272003174s
Availability | SPARQL endpoint availability check for Geographic detector model took 4.124641418457031e-05s
Availability | VoID file availability check for Geographic detector model took 0.0006256103515625s
Completeness | Calculation of interlinking completeness for Geographic detector model took 0.2715952396392822s
Reputation | Calculation of the PageRank for Geographic detector model took 0.020102739334106445s
Interlinking | Calculation of Degree of Connection for Geographic detector model took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Geographic detector model took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Geographic detector model took 2.8133392333984375e-05s
Believability | Calculation of trust value for Geographic detector model took 7.3909759521484375e-06s
INFO | --- Analysis for GeoDetector took 10.898168563842773s
Availability | SPARQL endpoint availability check for geodomainwn took 9.036064147949219e-05s
Availability | VoID file availability check for geodomainwn took 0.0008070468902587891s
Completeness | Calculation of interlinking completeness for geodomainwn took 0.9504163265228271s
Reputation | Calculation of the PageRank for geodomainwn took 0.0216519832611084s
Interlinking | Calculation of Degree of Connection for geodomainwn took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for geodomainwn took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for geodomainwn took 5.53131103515625e-05s
Believability | Calculation of trust value for geodomainwn took 7.62939453125e-06s
INFO | --- Analysis for geodomainwn took 967.2344136238098s
Availability | SPARQL endpoint availability check for GeoEcuador took 4.7206878662109375e-05s
Availability | VoID file availability check for GeoEcuador took 0.0005552768707275391s
Completeness | Calculation of interlinking completeness for GeoEcuador took 0.7051897048950195s
Reputation | Calculation of the PageRank for GeoEcuador took 0.02053070068359375s
Interlinking | Calculation of Degree of Connection for GeoEcuador took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for GeoEcuador took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for GeoEcuador took 6.651878356933594e-05s
Believability | Calculation of trust value for GeoEcuador took 7.867813110351562e-06s
INFO | --- Analysis for geoecuador took 14.751564264297485s
Availability | SPARQL endpoint availability check for Geographic Names Information System (GNIS) took 3.2174458503723145s
Availability | VoID file availability check for Geographic Names Information System (GNIS) took 0.0007176399230957031s
Completeness | Calculation of interlinking completeness for Geographic Names Information System (GNIS) took 0.7070960998535156s
Reputation | Calculation of the PageRank for Geographic Names Information System (GNIS) took 0.020659446716308594s
Interlinking | Calculation of Degree of Connection for Geographic Names Information System (GNIS) took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for Geographic Names Information System (GNIS) took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Geographic Names Information System (GNIS) took 7.581710815429688e-05s
Believability | Calculation of trust value for Geographic Names Information System (GNIS) took 6.9141387939453125e-06s
INFO | --- Analysis for geographic-names-information-system-gnis took 49.78343939781189s
Availability | SPARQL endpoint availability check for OpenUpLabs Geographic took 4.100799560546875e-05s
Availability | VoID file availability check for OpenUpLabs Geographic took 0.00030922889709472656s
Completeness | Calculation of interlinking completeness for OpenUpLabs Geographic took 0.7001399993896484s
Reputation | Calculation of the PageRank for OpenUpLabs Geographic took 0.020415067672729492s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Geographic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OpenUpLabs Geographic took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Geographic took 3.0040740966796875e-05s
Believability | Calculation of trust value for OpenUpLabs Geographic took 7.152557373046875e-06s
INFO | --- Analysis for geographic-openuplabs took 5.172316312789917s
Availability | SPARQL endpoint availability check for GeoLinkedData took 30.535656452178955s
Availability | VoID file availability check for GeoLinkedData took 0.0007350444793701172s
Completeness | Calculation of interlinking completeness for GeoLinkedData took 0.2740323543548584s
Reputation | Calculation of the PageRank for GeoLinkedData took 0.020540237426757812s
Interlinking | Calculation of Degree of Connection for GeoLinkedData took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GeoLinkedData took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for GeoLinkedData took 8.654594421386719e-05s
Believability | Calculation of trust value for GeoLinkedData took 5.0067901611328125e-06s
INFO | --- Analysis for geolinkeddata took 95.2672700881958s
Availability | SPARQL endpoint availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.9583873748779297s
Availability | VoID file availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.0006272792816162109s
Completeness | Calculation of interlinking completeness for Geological Survey of Austria (GBA) - Thesaurus took 0.29883265495300293s
Reputation | Calculation of the PageRank for Geological Survey of Austria (GBA) - Thesaurus took 0.020646095275878906s
Interlinking | Calculation of Degree of Connection for Geological Survey of Austria (GBA) - Thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Geological Survey of Austria (GBA) - Thesaurus took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Geological Survey of Austria (GBA) - Thesaurus took 7.867813110351562e-05s
Believability | Calculation of trust value for Geological Survey of Austria (GBA) - Thesaurus took 5.7220458984375e-06s
INFO | --- Analysis for geological-survey-of-austria-thesaurus took 8.101329326629639s
Availability | SPARQL endpoint availability check for GeoNames Semantic Web took 4.172325134277344e-05s
Availability | VoID file availability check for GeoNames Semantic Web took 0.0010662078857421875s
Completeness | Calculation of interlinking completeness for GeoNames Semantic Web took 0.2838134765625s
Reputation | Calculation of the PageRank for GeoNames Semantic Web took 0.020535945892333984s
Interlinking | Calculation of Degree of Connection for GeoNames Semantic Web took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for GeoNames Semantic Web took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for GeoNames Semantic Web took 0.00047898292541503906s
Believability | Calculation of trust value for GeoNames Semantic Web took 6.9141387939453125e-06s
INFO | --- Analysis for geonames-semantic-web took 4.55699610710144s
Availability | SPARQL endpoint availability check for Geospatial World  took 4.315376281738281e-05s
Availability | VoID file availability check for Geospatial World  took 0.0005025863647460938s
Completeness | Calculation of interlinking completeness for Geospatial World  took 0.2754349708557129s
Reputation | Calculation of the PageRank for Geospatial World  took 0.020488262176513672s
Interlinking | Calculation of Degree of Connection for Geospatial World  took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Geospatial World  took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Geospatial World  took 0.00010156631469726562s
Believability | Calculation of trust value for Geospatial World  took 7.62939453125e-06s
INFO | --- Analysis for geospatialworld-net took 4.326529026031494s
Availability | SPARQL endpoint availability check for GeoSpecies Knowledge Base took 0.5382530689239502s
Availability | VoID file availability check for GeoSpecies Knowledge Base took 0.0003871917724609375s
Completeness | Calculation of interlinking completeness for GeoSpecies Knowledge Base took 0.25659751892089844s
Reputation | Calculation of the PageRank for GeoSpecies Knowledge Base took 0.020292282104492188s
Interlinking | Calculation of Degree of Connection for GeoSpecies Knowledge Base took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GeoSpecies Knowledge Base took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Knowledge Base took 0.0001373291015625s
Believability | Calculation of trust value for GeoSpecies Knowledge Base took 8.344650268554688e-06s
INFO | --- Analysis for geospecies took 5.842059135437012s
Availability | SPARQL endpoint availability check for GeoWordNet took 4.076957702636719e-05s
Availability | VoID file availability check for GeoWordNet took 0.0004534721374511719s
Completeness | Calculation of interlinking completeness for GeoWordNet took 0.2702319622039795s
Reputation | Calculation of the PageRank for GeoWordNet took 0.020511627197265625s
Interlinking | Calculation of Degree of Connection for GeoWordNet took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GeoWordNet took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for GeoWordNet took 5.054473876953125e-05s
Believability | Calculation of trust value for GeoWordNet took 7.867813110351562e-06s
INFO | --- Analysis for geowordnet took 7.725755453109741s
Availability | SPARQL endpoint availability check for German labor law thesaurus took 0.18571901321411133s
Availability | VoID file availability check for German labor law thesaurus took 0.00020837783813476562s
Completeness | Calculation of interlinking completeness for German labor law thesaurus took 0.2648890018463135s
Reputation | Calculation of the PageRank for German labor law thesaurus took 0.02037215232849121s
Interlinking | Calculation of Degree of Connection for German labor law thesaurus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for German labor law thesaurus took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for German labor law thesaurus took 7.939338684082031e-05s
Believability | Calculation of trust value for German labor law thesaurus took 5.0067901611328125e-06s
INFO | --- Analysis for german-labor-law-thesaurus took 3.0589439868927s
Availability | SPARQL endpoint availability check for Linked Old Germanic Dictionaries took 4.0531158447265625e-05s
Availability | VoID file availability check for Linked Old Germanic Dictionaries took 0.0010569095611572266s
Completeness | Calculation of interlinking completeness for Linked Old Germanic Dictionaries took 0.26467037200927734s
Reputation | Calculation of the PageRank for Linked Old Germanic Dictionaries took 0.020312070846557617s
Interlinking | Calculation of Degree of Connection for Linked Old Germanic Dictionaries took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Linked Old Germanic Dictionaries took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Linked Old Germanic Dictionaries took 3.6716461181640625e-05s
Believability | Calculation of trust value for Linked Old Germanic Dictionaries took 6.198883056640625e-06s
INFO | --- Analysis for germlex took 2.4125165939331055s
Availability | SPARQL endpoint availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.6077134609222412s
Availability | VoID file availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0006830692291259766s
Completeness | Calculation of interlinking completeness for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.28388142585754395s
Reputation | Calculation of the PageRank for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.02019953727722168s
Interlinking | Calculation of Degree of Connection for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for TheSoz Thesaurus for the Social Sciences (GESIS) took 8.630752563476562e-05s
Believability | Calculation of trust value for TheSoz Thesaurus for the Social Sciences (GESIS) took 5.245208740234375e-06s
INFO | --- Analysis for gesis-thesoz took 6.230130672454834s
Availability | SPARQL endpoint availability check for Art & Architecture Thesaurus took 2.7927112579345703s
Availability | VoID file availability check for Art & Architecture Thesaurus took 0.00041222572326660156s
Completeness | Calculation of interlinking completeness for Art & Architecture Thesaurus took 0.25724315643310547s
Reputation | Calculation of the PageRank for Art & Architecture Thesaurus took 0.020369529724121094s
Interlinking | Calculation of Degree of Connection for Art & Architecture Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Art & Architecture Thesaurus took 0.0007953643798828125s
Interlinking | Calculation of Clustering coefficient for Art & Architecture Thesaurus took 7.581710815429688e-05s
Believability | Calculation of trust value for Art & Architecture Thesaurus took 6.4373016357421875e-06s
INFO | --- Analysis for getty-aat took 24.69587731361389s
Availability | SPARQL endpoint availability check for The Getty Thesaurus of Geographic Names took 2.471139907836914s
Availability | VoID file availability check for The Getty Thesaurus of Geographic Names took 0.0006356239318847656s
Completeness | Calculation of interlinking completeness for The Getty Thesaurus of Geographic Names took 0.27463650703430176s
Reputation | Calculation of the PageRank for The Getty Thesaurus of Geographic Names took 0.020258426666259766s
Interlinking | Calculation of Degree of Connection for The Getty Thesaurus of Geographic Names took 2.8848648071289062e-05s
Interlinking | Calculation of Centrality for The Getty Thesaurus of Geographic Names took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for The Getty Thesaurus of Geographic Names took 4.982948303222656e-05s
Believability | Calculation of trust value for The Getty Thesaurus of Geographic Names took 6.9141387939453125e-06s
INFO | --- Analysis for getty-tgn took 24.24691677093506s
Availability | SPARQL endpoint availability check for Gipuzkoa Demografia took 0.29492831230163574s
Availability | VoID file availability check for Gipuzkoa Demografia took 0.0004487037658691406s
Completeness | Calculation of interlinking completeness for Gipuzkoa Demografia took 0.27542591094970703s
Reputation | Calculation of the PageRank for Gipuzkoa Demografia took 0.020804882049560547s
Interlinking | Calculation of Degree of Connection for Gipuzkoa Demografia took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Gipuzkoa Demografia took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Gipuzkoa Demografia took 3.409385681152344e-05s
Believability | Calculation of trust value for Gipuzkoa Demografia took 4.291534423828125e-06s
INFO | --- Analysis for gipuzkoademografia took 3.8908779621124268s
Availability | SPARQL endpoint availability check for Glastonbury 2011 Programme took 4.363059997558594e-05s
Availability | VoID file availability check for Glastonbury 2011 Programme took 0.0006439685821533203s
Completeness | Calculation of interlinking completeness for Glastonbury 2011 Programme took 0.6989939212799072s
Reputation | Calculation of the PageRank for Glastonbury 2011 Programme took 0.020447731018066406s
Interlinking | Calculation of Degree of Connection for Glastonbury 2011 Programme took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Glastonbury 2011 Programme took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Glastonbury 2011 Programme took 3.0040740966796875e-05s
Believability | Calculation of trust value for Glastonbury 2011 Programme took 6.67572021484375e-06s
INFO | --- Analysis for glastonbury-2011 took 6.643706321716309s
Availability | SPARQL endpoint availability check for Global Change Information System took 3.9577484130859375e-05s
Availability | VoID file availability check for Global Change Information System took 0.00022840499877929688s
Completeness | Calculation of interlinking completeness for Global Change Information System took 0.2591438293457031s
Reputation | Calculation of the PageRank for Global Change Information System took 0.020252704620361328s
Interlinking | Calculation of Degree of Connection for Global Change Information System took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Global Change Information System took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Global Change Information System took 2.7894973754882812e-05s
Believability | Calculation of trust value for Global Change Information System took 5.7220458984375e-06s
INFO | --- Analysis for global-change-information-system took 2.907087564468384s
Availability | SPARQL endpoint availability check for Global Hunger Index (2011) took 4.6253204345703125e-05s
Availability | VoID file availability check for Global Hunger Index (2011) took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for Global Hunger Index (2011) took 0.26733875274658203s
Reputation | Calculation of the PageRank for Global Hunger Index (2011) took 0.02024698257446289s
Interlinking | Calculation of Degree of Connection for Global Hunger Index (2011) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Global Hunger Index (2011) took 0.0008294582366943359s
Interlinking | Calculation of Clustering coefficient for Global Hunger Index (2011) took 4.744529724121094e-05s
Believability | Calculation of trust value for Global Hunger Index (2011) took 7.152557373046875e-06s
INFO | --- Analysis for global-hunger-index-2011 took 2.993520498275757s
Availability | SPARQL endpoint availability check for Glottolog took 4.220008850097656e-05s
Availability | VoID file availability check for Glottolog took 0.0006005764007568359s
Completeness | Calculation of interlinking completeness for Glottolog took 0.29091501235961914s
Reputation | Calculation of the PageRank for Glottolog took 0.020501375198364258s
Interlinking | Calculation of Degree of Connection for Glottolog took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Glottolog took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Glottolog took 6.151199340820312e-05s
Believability | Calculation of trust value for Glottolog took 6.198883056640625e-06s
INFO | --- Analysis for glottolog took 6.504244089126587s
Availability | SPARQL endpoint availability check for GNOSS.com, a Social and Semantic Platform took 4.4345855712890625e-05s
Availability | VoID file availability check for GNOSS.com, a Social and Semantic Platform took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for GNOSS.com, a Social and Semantic Platform took 0.2702596187591553s
Reputation | Calculation of the PageRank for GNOSS.com, a Social and Semantic Platform took 0.025788307189941406s
Interlinking | Calculation of Degree of Connection for GNOSS.com, a Social and Semantic Platform took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for GNOSS.com, a Social and Semantic Platform took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for GNOSS.com, a Social and Semantic Platform took 0.000141143798828125s
Believability | Calculation of trust value for GNOSS.com, a Social and Semantic Platform took 8.106231689453125e-06s
INFO | --- Analysis for gnoss-com-a-social-and-semantic-platform took 3.2174787521362305s
Availability | SPARQL endpoint availability check for GNUsocial social.umeahackerspace.se took 3.981590270996094e-05s
Availability | VoID file availability check for GNUsocial social.umeahackerspace.se took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for GNUsocial social.umeahackerspace.se took 0.25034618377685547s
Reputation | Calculation of the PageRank for GNUsocial social.umeahackerspace.se took 0.02027750015258789s
Interlinking | Calculation of Degree of Connection for GNUsocial social.umeahackerspace.se took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for GNUsocial social.umeahackerspace.se took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for GNUsocial social.umeahackerspace.se took 2.86102294921875e-05s
Believability | Calculation of trust value for GNUsocial social.umeahackerspace.se took 6.9141387939453125e-06s
INFO | --- Analysis for gnusocial-social-umeahackerspace-se took 2.9463999271392822s
Availability | SPARQL endpoint availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 4.00543212890625e-05s
Availability | VoID file availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0002923011779785156s
Completeness | Calculation of interlinking completeness for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.2512657642364502s
Reputation | Calculation of the PageRank for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.020328760147094727s
Interlinking | Calculation of Degree of Connection for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 3.075599670410156e-05s
Believability | Calculation of trust value for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 7.62939453125e-06s
INFO | --- Analysis for go_annotations_from_ncbi_and_ebi took 2.9121265411376953s
Availability | SPARQL endpoint availability check for 1121 took 4.172325134277344e-05s
Availability | VoID file availability check for 1121 took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for 1121 took 0.24740314483642578s
Reputation | Calculation of the PageRank for 1121 took 0.020879507064819336s
Interlinking | Calculation of Degree of Connection for 1121 took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for 1121 took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for 1121 took 3.457069396972656e-05s
Believability | Calculation of trust value for 1121 took 6.9141387939453125e-06s
INFO | --- Analysis for God_ took 2.9616124629974365s
Availability | SPARQL endpoint availability check for General Ontology of Linguistic Description took 4.100799560546875e-05s
Availability | VoID file availability check for General Ontology of Linguistic Description took 0.0011632442474365234s
Completeness | Calculation of interlinking completeness for General Ontology of Linguistic Description took 0.2776961326599121s
Reputation | Calculation of the PageRank for General Ontology of Linguistic Description took 0.020458459854125977s
Interlinking | Calculation of Degree of Connection for General Ontology of Linguistic Description took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for General Ontology of Linguistic Description took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for General Ontology of Linguistic Description took 5.030632019042969e-05s
Believability | Calculation of trust value for General Ontology of Linguistic Description took 7.3909759521484375e-06s
INFO | --- Analysis for gold took 3.577277421951294s
Availability | SPARQL endpoint availability check for GoogleArt wrapper took 4.124641418457031e-05s
Availability | VoID file availability check for GoogleArt wrapper took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for GoogleArt wrapper took 0.26839256286621094s
Reputation | Calculation of the PageRank for GoogleArt wrapper took 0.020441770553588867s
Interlinking | Calculation of Degree of Connection for GoogleArt wrapper took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GoogleArt wrapper took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for GoogleArt wrapper took 6.580352783203125e-05s
Believability | Calculation of trust value for GoogleArt wrapper took 7.3909759521484375e-06s
INFO | --- Analysis for googleart-wrapper took 2.767094135284424s
Availability | SPARQL endpoint availability check for GovAgriBus Denmark took 0.12297534942626953s
Availability | VoID file availability check for GovAgriBus Denmark took 0.0005810260772705078s
Completeness | Calculation of interlinking completeness for GovAgriBus Denmark took 0.2892906665802002s
Reputation | Calculation of the PageRank for GovAgriBus Denmark took 0.02029871940612793s
Interlinking | Calculation of Degree of Connection for GovAgriBus Denmark took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GovAgriBus Denmark took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for GovAgriBus Denmark took 3.62396240234375e-05s
Believability | Calculation of trust value for GovAgriBus Denmark took 5.9604644775390625e-06s
INFO | --- Analysis for govagribus-denmark took 34.743648290634155s
Availability | SPARQL endpoint availability check for GovWILD - Government Web Integration for Linked Data took 3.994935989379883s
Availability | VoID file availability check for GovWILD - Government Web Integration for Linked Data took 0.0005826950073242188s
Completeness | Calculation of interlinking completeness for GovWILD - Government Web Integration for Linked Data took 0.27866101264953613s
Reputation | Calculation of the PageRank for GovWILD - Government Web Integration for Linked Data took 0.020298242568969727s
Interlinking | Calculation of Degree of Connection for GovWILD - Government Web Integration for Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GovWILD - Government Web Integration for Linked Data took 0.0008044242858886719s
Interlinking | Calculation of Clustering coefficient for GovWILD - Government Web Integration for Linked Data took 8.273124694824219e-05s
Believability | Calculation of trust value for GovWILD - Government Web Integration for Linked Data took 4.291534423828125e-06s
INFO | --- Analysis for government-web-integration-for-linked-data took 24.60210943222046s
Availability | SPARQL endpoint availability check for GovTrack.us U.S Congress Legislative Data took 3.755831480026245s
Availability | VoID file availability check for GovTrack.us U.S Congress Legislative Data took 0.0006620883941650391s
Completeness | Calculation of interlinking completeness for GovTrack.us U.S Congress Legislative Data took 0.2592802047729492s
Reputation | Calculation of the PageRank for GovTrack.us U.S Congress Legislative Data took 0.020270109176635742s
Interlinking | Calculation of Degree of Connection for GovTrack.us U.S Congress Legislative Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GovTrack.us U.S Congress Legislative Data took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for GovTrack.us U.S Congress Legislative Data took 8.749961853027344e-05s
Believability | Calculation of trust value for GovTrack.us U.S Congress Legislative Data took 5.4836273193359375e-06s
INFO | --- Analysis for govtrack took 12.618401050567627s
Availability | SPARQL endpoint availability check for greek-administrative-geography took 4.124641418457031e-05s
Availability | VoID file availability check for greek-administrative-geography took 0.0005850791931152344s
Completeness | Calculation of interlinking completeness for greek-administrative-geography took 0.27932167053222656s
Reputation | Calculation of the PageRank for greek-administrative-geography took 0.02026963233947754s
Interlinking | Calculation of Degree of Connection for greek-administrative-geography took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for greek-administrative-geography took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for greek-administrative-geography took 6.794929504394531e-05s
Believability | Calculation of trust value for greek-administrative-geography took 6.198883056640625e-06s
INFO | --- Analysis for greek-administrative-geography took 3.7373619079589844s
Availability | SPARQL endpoint availability check for Greek Wordnet took 0.7447786331176758s
Availability | VoID file availability check for Greek Wordnet took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for Greek Wordnet took 0.2521820068359375s
Reputation | Calculation of the PageRank for Greek Wordnet took 0.020240306854248047s
Interlinking | Calculation of Degree of Connection for Greek Wordnet took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Greek Wordnet took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Greek Wordnet took 4.00543212890625e-05s
Believability | Calculation of trust value for Greek Wordnet took 6.9141387939453125e-06s
INFO | --- Analysis for greek-wordnet took 3.63680362701416s
Availability | SPARQL endpoint availability check for Greek prisons releases Jan 2018 - Dec 2023 took 2.9364335536956787s
Availability | VoID file availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.0005965232849121094s
Completeness | Calculation of interlinking completeness for Greek prisons releases Jan 2018 - Dec 2023 took 0.262514591217041s
Reputation | Calculation of the PageRank for Greek prisons releases Jan 2018 - Dec 2023 took 0.020318984985351562s
Interlinking | Calculation of Degree of Connection for Greek prisons releases Jan 2018 - Dec 2023 took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Greek prisons releases Jan 2018 - Dec 2023 took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Greek prisons releases Jan 2018 - Dec 2023 took 1.1682510375976562e-05s
Believability | Calculation of trust value for Greek prisons releases Jan 2018 - Dec 2023 took 6.198883056640625e-06s
INFO | --- Analysis for greek_prisons_releases took 7.604665994644165s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 0.8713366985321045s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0005505084991455078s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.2791860103607178s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.020641565322875977s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.390975952148438e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 7.3909759521484375e-06s
INFO | --- Analysis for greekchildrensartmuseum took 4.5379111766815186s
Availability | SPARQL endpoint availability check for Green Competitiveness (GNOSS) took 4.267692565917969e-05s
Availability | VoID file availability check for Green Competitiveness (GNOSS) took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for Green Competitiveness (GNOSS) took 0.2554152011871338s
Reputation | Calculation of the PageRank for Green Competitiveness (GNOSS) took 0.02032470703125s
Interlinking | Calculation of Degree of Connection for Green Competitiveness (GNOSS) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Green Competitiveness (GNOSS) took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Green Competitiveness (GNOSS) took 0.0001010894775390625s
Believability | Calculation of trust value for Green Competitiveness (GNOSS) took 6.198883056640625e-06s
INFO | --- Analysis for green-competitiveness-gnoss took 3.411233901977539s
Availability | SPARQL endpoint availability check for Accommodations in Piedmont (LinkedOpenData.it) took 1.7945213317871094s
Availability | VoID file availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for Accommodations in Piedmont (LinkedOpenData.it) took 0.2837679386138916s
Reputation | Calculation of the PageRank for Accommodations in Piedmont (LinkedOpenData.it) took 0.0204470157623291s
Interlinking | Calculation of Degree of Connection for Accommodations in Piedmont (LinkedOpenData.it) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Accommodations in Piedmont (LinkedOpenData.it) took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Accommodations in Piedmont (LinkedOpenData.it) took 4.673004150390625e-05s
Believability | Calculation of trust value for Accommodations in Piedmont (LinkedOpenData.it) took 6.67572021484375e-06s
INFO | --- Analysis for grrp took 4.373289585113525s
Availability | SPARQL endpoint availability check for Accommodations in Tuscany (LinkedOpenData.it) took 1.607301950454712s
Availability | VoID file availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.0005965232849121094s
Completeness | Calculation of interlinking completeness for Accommodations in Tuscany (LinkedOpenData.it) took 0.28178858757019043s
Reputation | Calculation of the PageRank for Accommodations in Tuscany (LinkedOpenData.it) took 0.020462512969970703s
Interlinking | Calculation of Degree of Connection for Accommodations in Tuscany (LinkedOpenData.it) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Accommodations in Tuscany (LinkedOpenData.it) took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for Accommodations in Tuscany (LinkedOpenData.it) took 7.176399230957031e-05s
Believability | Calculation of trust value for Accommodations in Tuscany (LinkedOpenData.it) took 7.867813110351562e-06s
INFO | --- Analysis for grrt took 4.147946834564209s
Availability | SPARQL endpoint availability check for Geological Timescale took 1.4142868518829346s
Availability | VoID file availability check for Geological Timescale took 0.0006871223449707031s
Extra | Recovery of all triples for Geological Timescale took 2.990997076034546s
Performance | Total latancy measurement for Geological Timescale took 5.224644184112549s
Amount of data | Number of triples check for Geological Timescale took 0.5131595134735107s
Interoperability | New terms check for Geological Timescale took 1.6634020805358887s
Versatility | Languages check for Geological Timescale took 0.6228206157684326s
Interpretability | Number of blank nodes check for Geological Timescale took 1.2249462604522705s
Security | Check HTTPS for Geological Timescale took 0.4657139778137207s
Interpretability | RDF structures check for Geological Timescale took 0.5076398849487305s
Versatility | Serialization formats check for Geological Timescale took 0.47164344787597656s
Availability | RDF dump link check for Geological Timescale took 2.090301990509033s
License | MR license check for Geological Timescale took 0.5456523895263672s
License | HR license check for Geological Timescale took 0.5075147151947021s
Amount of data | Number of property check for Geological Timescale took 0.47728586196899414s
Understandability | Number of label check for Geological Timescale took 1.1863679885864258s
Understandability | URI regex check for Geological Timescale took 1.0215675830841064s
Understandability | Vocabs check for Geological Timescale took 0.6498911380767822s
Verifiability | Authors check for Geological Timescale took 0.5017387866973877s
Verifiability | Publishers check for Geological Timescale took 0.5432496070861816s
Performance | Throughput check for Geological Timescale took 14.933255910873413s
Amount of data | Check the number of entities for Geological Timescale took 0.022460460662841797s
Verifiability | Contribs. check for Geological Timescale took 2.152981996536255s
Interlinking | sameAs chians check for Geological Timescale took 1.1875996589660645s
Interlinking | skos check for Geological Timescale took 0.46970534324645996s
Interlinking | skos check for Geological Timescale took 1.2037875652313232s
Timeliness | dataset update frequency check for Geological Timescale took 1.1625666618347168s
Currency | Creation date check for Geological Timescale took 0.9868052005767822s
Currency | Modification date check for Geological Timescale took 0.4613208770751953s
Rep.Conc. | URIs length for Geological Timescale took 2.5247299671173096s
Consistency | Deprecated classes/propertiers check for Geological Timescale took 0.48174309730529785s
Accuracy | Check Functional Property for Geological Timescale took 0.45239758491516113s
Accuracy | Check Inverse Functional Property for Geological Timescale took 1.139594316482544s
Accuracy | Check Empty annotation labels for Geological Timescale took 1.6911919116973877s
Accuracy | Check White space in annotation for Geological Timescale took 0.01571202278137207s
Accuracy | Check Datatype consistency for Geological Timescale took 0.07595372200012207s
Consistency | Disjoint class check for Geological Timescale took 0.4997999668121338s
Consistency | Check Misplaced properties for Geological Timescale took 2.373659610748291s
Consistency | Misplaced classes for Geological Timescale took 1.281052827835083s
Consistency | Check Ontology hijacking for Geological Timescale took 1.7005863189697266s
Consistency | Check Invalid usage of undefined classes for Geological Timescale took 1.1469595432281494s
Consistency | Check Invalid usage of undefined properties for Geological Timescale took 3.2875096797943115s
Conciseness | Check Extensional conciseness for Geological Timescale took 0.0487060546875s
Conciseness | Check Intensional conciseness for Geological Timescale took 1.1003472805023193s
Security | Sign check for Geological Timescale took 0.44739842414855957s
Availability | Check URIs Dereferenciability for Geological Timescale took 3.1220669746398926s
Completeness | Calculation of interlinking completeness for Geological Timescale took 0.31270503997802734s
Reputation | Calculation of the PageRank for Geological Timescale took 0.02015519142150879s
Interlinking | Calculation of Degree of Connection for Geological Timescale took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Geological Timescale took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Geological Timescale took 7.009506225585938e-05s
Believability | Calculation of trust value for Geological Timescale took 6.9141387939453125e-06s
INFO | --- Analysis for GTS took 118.35203957557678s
Availability | SPARQL endpoint availability check for Geological Timescale Ontology took 4.601478576660156e-05s
Availability | VoID file availability check for Geological Timescale Ontology took 0.00066375732421875s
Completeness | Calculation of interlinking completeness for Geological Timescale Ontology took 0.2837221622467041s
Reputation | Calculation of the PageRank for Geological Timescale Ontology took 0.02075648307800293s
Interlinking | Calculation of Degree of Connection for Geological Timescale Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Geological Timescale Ontology took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Geological Timescale Ontology took 3.24249267578125e-05s
Believability | Calculation of trust value for Geological Timescale Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for GTS-ont took 2.6944921016693115s
Availability | SPARQL endpoint availability check for GUTSTOK  took 4.172325134277344e-05s
Availability | VoID file availability check for GUTSTOK  took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for GUTSTOK  took 0.24610257148742676s
Reputation | Calculation of the PageRank for GUTSTOK  took 0.021676063537597656s
Interlinking | Calculation of Degree of Connection for GUTSTOK  took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for GUTSTOK  took 0.0010743141174316406s
Interlinking | Calculation of Clustering coefficient for GUTSTOK  took 3.933906555175781e-05s
Believability | Calculation of trust value for GUTSTOK  took 6.4373016357421875e-06s
INFO | --- Analysis for Guillaume_Forget took 2.3542892932891846s
Availability | SPARQL endpoint availability check for Project Gutenberg took 4.506111145019531e-05s
Availability | VoID file availability check for Project Gutenberg took 0.000354766845703125s
Completeness | Calculation of interlinking completeness for Project Gutenberg took 0.28028106689453125s
Reputation | Calculation of the PageRank for Project Gutenberg took 0.02023768424987793s
Interlinking | Calculation of Degree of Connection for Project Gutenberg took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Project Gutenberg took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg took 6.651878356933594e-05s
Believability | Calculation of trust value for Project Gutenberg took 6.4373016357421875e-06s
INFO | --- Analysis for gutenberg took 8.420499324798584s
Availability | SPARQL endpoint availability check for Global WordNet Association Interlingual Index took 4.1961669921875e-05s
Availability | VoID file availability check for Global WordNet Association Interlingual Index took 0.0008172988891601562s
Completeness | Calculation of interlinking completeness for Global WordNet Association Interlingual Index took 0.27330636978149414s
Reputation | Calculation of the PageRank for Global WordNet Association Interlingual Index took 0.02062249183654785s
Interlinking | Calculation of Degree of Connection for Global WordNet Association Interlingual Index took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Global WordNet Association Interlingual Index took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Global WordNet Association Interlingual Index took 4.124641418457031e-05s
Believability | Calculation of trust value for Global WordNet Association Interlingual Index took 6.9141387939453125e-06s
INFO | --- Analysis for gwa-ili took 5.174229383468628s
Availability | SPARQL endpoint availability check for Geographically Weighted Regression Model took 4.2438507080078125e-05s
Availability | VoID file availability check for Geographically Weighted Regression Model took 0.0006291866302490234s
Completeness | Calculation of interlinking completeness for Geographically Weighted Regression Model took 0.27585721015930176s
Reputation | Calculation of the PageRank for Geographically Weighted Regression Model took 0.020552873611450195s
Interlinking | Calculation of Degree of Connection for Geographically Weighted Regression Model took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Geographically Weighted Regression Model took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Geographically Weighted Regression Model took 3.123283386230469e-05s
Believability | Calculation of trust value for Geographically Weighted Regression Model took 7.3909759521484375e-06s
INFO | --- Analysis for GWR took 13.31246542930603s
Availability | SPARQL endpoint availability check for High Accuracy Surface Modeling took 4.172325134277344e-05s
Availability | VoID file availability check for High Accuracy Surface Modeling took 0.0006356239318847656s
Completeness | Calculation of interlinking completeness for High Accuracy Surface Modeling took 0.2620115280151367s
Reputation | Calculation of the PageRank for High Accuracy Surface Modeling took 0.020568132400512695s
Interlinking | Calculation of Degree of Connection for High Accuracy Surface Modeling took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for High Accuracy Surface Modeling took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for High Accuracy Surface Modeling took 3.075599670410156e-05s
Believability | Calculation of trust value for High Accuracy Surface Modeling took 6.4373016357421875e-06s
INFO | --- Analysis for HASM took 8.316417932510376s
Availability | SPARQL endpoint availability check for HCLS Knowledge Base took 3.933906555175781e-05s
Availability | VoID file availability check for HCLS Knowledge Base took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for HCLS Knowledge Base took 0.2874114513397217s
Reputation | Calculation of the PageRank for HCLS Knowledge Base took 0.020427227020263672s
Interlinking | Calculation of Degree of Connection for HCLS Knowledge Base took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for HCLS Knowledge Base took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for HCLS Knowledge Base took 3.170967102050781e-05s
Believability | Calculation of trust value for HCLS Knowledge Base took 5.9604644775390625e-06s
INFO | --- Analysis for hcls-knowledge-base took 2.9783811569213867s
Availability | SPARQL endpoint availability check for HealthCare Ontology took 31.786946296691895s
Availability | VoID file availability check for HealthCare Ontology took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for HealthCare Ontology took 0.3002493381500244s
Reputation | Calculation of the PageRank for HealthCare Ontology took 0.020644426345825195s
Interlinking | Calculation of Degree of Connection for HealthCare Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for HealthCare Ontology took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for HealthCare Ontology took 4.3392181396484375e-05s
Believability | Calculation of trust value for HealthCare Ontology took 1.8596649169921875e-05s
INFO | --- Analysis for HealthCare_Ontology took 34.76259636878967s
Availability | SPARQL endpoint availability check for Meriterm Heart Failure Multilingual Terminology took 4.076957702636719e-05s
Availability | VoID file availability check for Meriterm Heart Failure Multilingual Terminology took 0.0005595684051513672s
Completeness | Calculation of interlinking completeness for Meriterm Heart Failure Multilingual Terminology took 0.27037978172302246s
Reputation | Calculation of the PageRank for Meriterm Heart Failure Multilingual Terminology took 0.02046036720275879s
Interlinking | Calculation of Degree of Connection for Meriterm Heart Failure Multilingual Terminology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Meriterm Heart Failure Multilingual Terminology took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Meriterm Heart Failure Multilingual Terminology took 6.0558319091796875e-05s
Believability | Calculation of trust value for Meriterm Heart Failure Multilingual Terminology took 6.4373016357421875e-06s
INFO | --- Analysis for heartfailure took 2.657529592514038s
Availability | SPARQL endpoint availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 21.428630590438843s
Availability | VoID file availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007696151733398438s
Completeness | Calculation of interlinking completeness for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.29716920852661133s
Reputation | Calculation of the PageRank for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.020670413970947266s
Interlinking | Calculation of Degree of Connection for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 9.250640869140625e-05s
Believability | Calculation of trust value for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 5.245208740234375e-06s
INFO | --- Analysis for hebis-bibliographic-resources took 119.24526643753052s
Availability | SPARQL endpoint availability check for Hedatuz took 0.25823044776916504s
Availability | VoID file availability check for Hedatuz took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for Hedatuz took 0.25623273849487305s
Reputation | Calculation of the PageRank for Hedatuz took 0.020379066467285156s
Interlinking | Calculation of Degree of Connection for Hedatuz took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Hedatuz took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Hedatuz took 4.220008850097656e-05s
Believability | Calculation of trust value for Hedatuz took 5.9604644775390625e-06s
INFO | --- Analysis for hedatuz took 3.8379244804382324s
Availability | SPARQL endpoint availability check for Hellenic Fire Brigade took 0.20877552032470703s
Availability | VoID file availability check for Hellenic Fire Brigade took 0.0004532337188720703s
Completeness | Calculation of interlinking completeness for Hellenic Fire Brigade took 0.2663261890411377s
Reputation | Calculation of the PageRank for Hellenic Fire Brigade took 0.020463943481445312s
Interlinking | Calculation of Degree of Connection for Hellenic Fire Brigade took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Hellenic Fire Brigade took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Hellenic Fire Brigade took 0.0001270771026611328s
Believability | Calculation of trust value for Hellenic Fire Brigade took 4.5299530029296875e-06s
INFO | --- Analysis for hellenic-fire-brigade took 2.6308350563049316s
Availability | SPARQL endpoint availability check for Hellenic Police took 0.028644561767578125s
Availability | VoID file availability check for Hellenic Police took 0.00040435791015625s
Completeness | Calculation of interlinking completeness for Hellenic Police took 0.263164758682251s
Reputation | Calculation of the PageRank for Hellenic Police took 0.020616531372070312s
Interlinking | Calculation of Degree of Connection for Hellenic Police took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Hellenic Police took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Hellenic Police took 0.00013065338134765625s
Believability | Calculation of trust value for Hellenic Police took 5.245208740234375e-06s
INFO | --- Analysis for hellenic-police took 3.793937921524048s
Availability | SPARQL endpoint availability check for Hermos took 4.029273986816406e-05s
Availability | VoID file availability check for Hermos took 0.0006594657897949219s
Completeness | Calculation of interlinking completeness for Hermos took 0.2712841033935547s
Reputation | Calculation of the PageRank for Hermos took 0.02035069465637207s
Interlinking | Calculation of Degree of Connection for Hermos took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Hermos took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Hermos took 2.9087066650390625e-05s
Believability | Calculation of trust value for Hermos took 6.9141387939453125e-06s
INFO | --- Analysis for Hermos took 3.1146228313446045s
Availability | SPARQL endpoint availability check for Himanshu Mahawar took 4.38690185546875e-05s
Availability | VoID file availability check for Himanshu Mahawar took 0.000293731689453125s
Completeness | Calculation of interlinking completeness for Himanshu Mahawar took 0.269700288772583s
Reputation | Calculation of the PageRank for Himanshu Mahawar took 0.02082371711730957s
Interlinking | Calculation of Degree of Connection for Himanshu Mahawar took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Himanshu Mahawar took 0.0008149147033691406s
Interlinking | Calculation of Clustering coefficient for Himanshu Mahawar took 3.719329833984375e-05s
Believability | Calculation of trust value for Himanshu Mahawar took 6.9141387939453125e-06s
INFO | --- Analysis for Himanshu_Mahawar took 2.4064290523529053s
Availability | SPARQL endpoint availability check for HITO took 0.4293854236602783s
Availability | VoID file availability check for HITO took 0.0007731914520263672s
Extra | Recovery of all triples for HITO took 4.524318695068359s
Performance | Total latancy measurement for HITO took 0.9847052097320557s
Amount of data | Number of triples check for HITO took 0.197021484375s
Interoperability | New terms check for HITO took 1.4069361686706543s
Versatility | Languages check for HITO took 0.2516660690307617s
Interpretability | Number of blank nodes check for HITO took 0.18580198287963867s
Interpretability | RDF structures check for HITO took 0.20143532752990723s
Versatility | Serialization formats check for HITO took 0.20031166076660156s
Availability | RDF dump link check for HITO took 0.20618796348571777s
License | MR license check for HITO took 0.20997381210327148s
License | HR license check for HITO took 0.2209763526916504s
Amount of data | Number of property check for HITO took 0.20077824592590332s
Understandability | Number of label check for HITO took 0.21228265762329102s
Understandability | URI regex check for HITO took 0.39116978645324707s
Understandability | Vocabs check for HITO took 0.18597626686096191s
Verifiability | Authors check for HITO took 0.1990056037902832s
Verifiability | Publishers check for HITO took 0.18799376487731934s
Performance | Throughput check for HITO took 11.009847640991211s
Amount of data | Check the number of entities for HITO took 6.842613220214844e-05s
Verifiability | Contribs. check for HITO took 0.20902514457702637s
Interlinking | sameAs chians check for HITO took 0.19713568687438965s
Interlinking | skos check for HITO took 0.1870865821838379s
Interlinking | skos check for HITO took 0.21111178398132324s
Timeliness | dataset update frequency check for HITO took 0.2165544033050537s
Currency | Creation date check for HITO took 0.4097931385040283s
Currency | Modification date check for HITO took 0.40592384338378906s
Rep.Conc. | URIs length for HITO took 1.3321075439453125s
Interoperability | New vocabularies check for HITO took 5.245208740234375e-06s
Consistency | Deprecated classes/propertiers check for HITO took 0.20329594612121582s
Accuracy | Check Functional Property for HITO took 0.20590901374816895s
Accuracy | Check Inverse Functional Property for HITO took 0.19851398468017578s
Accuracy | Check Empty annotation labels for HITO took 0.5831680297851562s
Accuracy | Check White space in annotation for HITO took 0.013939619064331055s
Accuracy | Check Datatype consistency for HITO took 0.09119200706481934s
Consistency | Disjoint class check for HITO took 0.19841742515563965s
Consistency | Check Misplaced properties for HITO took 0.5114309787750244s
Consistency | Misplaced classes for HITO took 0.3918125629425049s
Consistency | Check Ontology hijacking for HITO took 1.6497249603271484s
Consistency | Check Invalid usage of undefined classes for HITO took 1.1723313331604004s
Consistency | Check Invalid usage of undefined properties for HITO took 1.4410672187805176s
Conciseness | Check Extensional conciseness for HITO took 0.06785225868225098s
Conciseness | Check Intensional conciseness for HITO took 0.18577909469604492s
Security | Sign check for HITO took 0.19511127471923828s
Availability | Check URIs Dereferenciability for HITO took 1478.5463948249817s
Completeness | Calculation of interlinking completeness for HITO took 1.4912190437316895s
Reputation | Calculation of the PageRank for HITO took 0.020922422409057617s
Interlinking | Calculation of Degree of Connection for HITO took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for HITO took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for HITO took 9.083747863769531e-05s
Interoperability | Check the re-using of existing vocabs for HITO took 1.1920928955078125e-06s
Believability | Calculation of trust value for HITO took 7.867813110351562e-06s
INFO | --- Analysis for hito took 1538.5179069042206s
Availability | SPARQL endpoint availability check for Hoa Thịnh Phát took 2.422739267349243s
Availability | VoID file availability check for Hoa Thịnh Phát took 0.0006341934204101562s
Completeness | Calculation of interlinking completeness for Hoa Thịnh Phát took 0.7222838401794434s
Reputation | Calculation of the PageRank for Hoa Thịnh Phát took 0.0200655460357666s
Interlinking | Calculation of Degree of Connection for Hoa Thịnh Phát took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Hoa Thịnh Phát took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Hoa Thịnh Phát took 2.8133392333984375e-05s
Believability | Calculation of trust value for Hoa Thịnh Phát took 6.198883056640625e-06s
INFO | --- Analysis for Hoa_Thinh_Phat took 21.360113382339478s
Availability | SPARQL endpoint availability check for Homologene took 4.029273986816406e-05s
Availability | VoID file availability check for Homologene took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for Homologene took 0.2615180015563965s
Reputation | Calculation of the PageRank for Homologene took 0.02060556411743164s
Interlinking | Calculation of Degree of Connection for Homologene took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Homologene took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Homologene took 3.5762786865234375e-05s
Believability | Calculation of trust value for Homologene took 6.67572021484375e-06s
INFO | --- Analysis for homologene took 4.269130706787109s
Availability | SPARQL endpoint availability check for gseg took 4.291534423828125e-05s
Availability | VoID file availability check for gseg took 0.0006344318389892578s
Completeness | Calculation of interlinking completeness for gseg took 0.2638568878173828s
Reputation | Calculation of the PageRank for gseg took 0.020584583282470703s
Interlinking | Calculation of Degree of Connection for gseg took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for gseg took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for gseg took 3.0517578125e-05s
Believability | Calculation of trust value for gseg took 6.9141387939453125e-06s
INFO | --- Analysis for hongse took 4.134650945663452s
Availability | SPARQL endpoint availability check for Noticias Universia took 3.9577484130859375e-05s
Availability | VoID file availability check for Noticias Universia took 0.0002796649932861328s
Completeness | Calculation of interlinking completeness for Noticias Universia took 0.25888919830322266s
Reputation | Calculation of the PageRank for Noticias Universia took 0.020524024963378906s
Interlinking | Calculation of Degree of Connection for Noticias Universia took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Noticias Universia took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Noticias Universia took 3.1948089599609375e-05s
Believability | Calculation of trust value for Noticias Universia took 8.106231689453125e-06s
INFO | --- Analysis for http-data-noticias-universia-net took 4.312588214874268s
Availability | SPARQL endpoint availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 4.076957702636719e-05s
Availability | VoID file availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.00027370452880859375s
Completeness | Calculation of interlinking completeness for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.3050248622894287s
Reputation | Calculation of the PageRank for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.020645618438720703s
Interlinking | Calculation of Degree of Connection for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 4.029273986816406e-05s
Believability | Calculation of trust value for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 6.67572021484375e-06s
INFO | --- Analysis for http-www-iwmi-cgiar-org-publications-iwmi-working-papers took 2.9843621253967285s
Availability | SPARQL endpoint availability check for COURAGE Dataset took 1.843275547027588s
Availability | VoID file availability check for COURAGE Dataset took 0.0005948543548583984s
Completeness | Calculation of interlinking completeness for COURAGE Dataset took 0.26028943061828613s
Reputation | Calculation of the PageRank for COURAGE Dataset took 0.020247697830200195s
Interlinking | Calculation of Degree of Connection for COURAGE Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for COURAGE Dataset took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for COURAGE Dataset took 3.266334533691406e-05s
Believability | Calculation of trust value for COURAGE Dataset took 6.67572021484375e-06s
INFO | --- Analysis for http:cultural-opposition.eu took 5.380689859390259s
Availability | SPARQL endpoint availability check for RoadTrb took 4.1961669921875e-05s
Availability | VoID file availability check for RoadTrb took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for RoadTrb took 0.2852151393890381s
Reputation | Calculation of the PageRank for RoadTrb took 0.020751953125s
Interlinking | Calculation of Degree of Connection for RoadTrb took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for RoadTrb took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for RoadTrb took 2.86102294921875e-05s
Believability | Calculation of trust value for RoadTrb took 5.9604644775390625e-06s
INFO | --- Analysis for http:data.linkedeodata.euroadidStateRoadD010Turkey-1 took 2.8482611179351807s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0006501674652099609s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.25283336639404297s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.020300865173339844s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 3.266334533691406e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 8.58306884765625e-06s
INFO | --- Analysis for http:guava.iis.sinica.edu.twr4r took 24.98629927635193s
Availability | SPARQL endpoint availability check for Polictical History of Pakistan took 4.100799560546875e-05s
Availability | VoID file availability check for Polictical History of Pakistan took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Polictical History of Pakistan took 0.2690424919128418s
Reputation | Calculation of the PageRank for Polictical History of Pakistan took 0.020352602005004883s
Interlinking | Calculation of Degree of Connection for Polictical History of Pakistan took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Polictical History of Pakistan took 0.0008122920989990234s
Interlinking | Calculation of Clustering coefficient for Polictical History of Pakistan took 3.361701965332031e-05s
Believability | Calculation of trust value for Polictical History of Pakistan took 6.67572021484375e-06s
INFO | --- Analysis for http:pakistan.com took 2.3696250915527344s
Availability | SPARQL endpoint availability check for CEDICT took 4.2438507080078125e-05s
Availability | VoID file availability check for CEDICT took 0.0006334781646728516s
Completeness | Calculation of interlinking completeness for CEDICT took 0.28434157371520996s
Reputation | Calculation of the PageRank for CEDICT took 0.0202791690826416s
Interlinking | Calculation of Degree of Connection for CEDICT took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CEDICT took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for CEDICT took 2.8848648071289062e-05s
Believability | Calculation of trust value for CEDICT took 6.4373016357421875e-06s
INFO | --- Analysis for http:rdf.naturallexicon.orgzhontCedict took 4.199842214584351s
Availability | SPARQL endpoint availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.5935471057891846s
Availability | VoID file availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0006372928619384766s
Completeness | Calculation of interlinking completeness for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.2533223628997803s
Reputation | Calculation of the PageRank for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.020615339279174805s
Interlinking | Calculation of Degree of Connection for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0008890628814697266s
Interlinking | Calculation of Clustering coefficient for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 8.320808410644531e-05s
Believability | Calculation of trust value for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 7.867813110351562e-06s
INFO | --- Analysis for http:sensormeasurement.appspot.comdatasetnaturopathy-dataset took 4.291218996047974s
Availability | SPARQL endpoint availability check for Pakistan Stock Market Data took 4.172325134277344e-05s
Availability | VoID file availability check for Pakistan Stock Market Data took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for Pakistan Stock Market Data took 0.2694389820098877s
Reputation | Calculation of the PageRank for Pakistan Stock Market Data took 0.0203704833984375s
Interlinking | Calculation of Degree of Connection for Pakistan Stock Market Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Pakistan Stock Market Data took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Pakistan Stock Market Data took 2.9325485229492188e-05s
Believability | Calculation of trust value for Pakistan Stock Market Data took 5.9604644775390625e-06s
INFO | --- Analysis for http:www.atif-sajjad.comSemster-Project# took 2.917816162109375s
Availability | SPARQL endpoint availability check for Grand Slam Knowledge Graph took 4.172325134277344e-05s
Availability | VoID file availability check for Grand Slam Knowledge Graph took 0.00041675567626953125s
Completeness | Calculation of interlinking completeness for Grand Slam Knowledge Graph took 0.28177714347839355s
Reputation | Calculation of the PageRank for Grand Slam Knowledge Graph took 0.020885467529296875s
Interlinking | Calculation of Degree of Connection for Grand Slam Knowledge Graph took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Grand Slam Knowledge Graph took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Grand Slam Knowledge Graph took 3.337860107421875e-05s
Believability | Calculation of trust value for Grand Slam Knowledge Graph took 7.152557373046875e-06s
INFO | --- Analysis for http:www.fateh_fahad_adeel.comgrandSlam took 2.4286181926727295s
Availability | SPARQL endpoint availability check for Soccer Dataset took 4.3392181396484375e-05s
Availability | VoID file availability check for Soccer Dataset took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Soccer Dataset took 0.2677185535430908s
Reputation | Calculation of the PageRank for Soccer Dataset took 0.02069854736328125s
Interlinking | Calculation of Degree of Connection for Soccer Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Soccer Dataset took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Soccer Dataset took 3.457069396972656e-05s
Believability | Calculation of trust value for Soccer Dataset took 7.62939453125e-06s
INFO | --- Analysis for http:www.msm.com took 2.38450288772583s
Availability | SPARQL endpoint availability check for Game Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Game Ontology took 0.0002906322479248047s
Completeness | Calculation of interlinking completeness for Game Ontology took 0.28883838653564453s
Reputation | Calculation of the PageRank for Game Ontology took 0.020401477813720703s
Interlinking | Calculation of Degree of Connection for Game Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Game Ontology took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Game Ontology took 3.3855438232421875e-05s
Believability | Calculation of trust value for Game Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for http:www.RAG.comgameonto# took 2.9954400062561035s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 5.245208740234375e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007507801055908203s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.2704184055328369s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.021907806396484375s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.2901763916015625e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 7.152557373046875e-06s
INFO | --- Analysis for http:www.semanticweb.orgambrishontologies202010untitled-ontology-24 took 3.4894301891326904s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 4.100799560546875e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0002307891845703125s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.2882394790649414s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.020398616790771484s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.0040740966796875e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 6.4373016357421875e-06s
INFO | --- Analysis for http:www.semanticweb.orgarchanaontologies20215untitled-ontology-6 took 2.37205171585083s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.124641418457031e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2573552131652832s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020474672317504883s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.956390380859375e-05s
Believability | Calculation of trust value for Indian Biodiversity took 6.9141387939453125e-06s
INFO | --- Analysis for http:www.semanticweb.orgmcaontologies20188untitled-ontology-47 took 2.4291419982910156s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.220008850097656e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0002334117889404297s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.25746941566467285s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020201444625854492s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.147125244140625e-05s
Believability | Calculation of trust value for Indian Biodiversity took 5.9604644775390625e-06s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIO took 2.384103536605835s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.100799560546875e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.00023412704467773438s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2807176113128662s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020125389099121094s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.8848648071289062e-05s
Believability | Calculation of trust value for Indian Biodiversity took 5.7220458984375e-06s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIOp=summary took 2.4298853874206543s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.1484832763671875e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0006353855133056641s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.26637983322143555s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020625591278076172s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.0040740966796875e-05s
Believability | Calculation of trust value for Indian Biodiversity took 8.106231689453125e-06s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBDsubmissions1downloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb took 3.4168059825897217s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.291534423828125e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.29062366485595703s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020668983459472656s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.123283386230469e-05s
Believability | Calculation of trust value for Indian Biodiversity took 5.245208740234375e-06s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBIOsubmissions1downloadapikey=66c2aec1-4044-4900-979d-6f529857554a took 2.448378324508667s
Availability | SPARQL endpoint availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 4.363059997558594e-05s
Availability | VoID file availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0007259845733642578s
Completeness | Calculation of interlinking completeness for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.29807519912719727s
Reputation | Calculation of the PageRank for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.020142793655395508s
Interlinking | Calculation of Degree of Connection for Diretrizes organizacionais de métodos quantitativos e computação científica took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Diretrizes organizacionais de métodos quantitativos e computação científica took 2.9325485229492188e-05s
Believability | Calculation of trust value for Diretrizes organizacionais de métodos quantitativos e computação científica took 5.4836273193359375e-06s
INFO | --- Analysis for https:orcid.org0000-0002-6194-9354 took 3.9268088340759277s
Availability | SPARQL endpoint availability check for Bookkeeping took 1.1769437789916992s
Availability | VoID file availability check for Bookkeeping took 0.000568389892578125s
Completeness | Calculation of interlinking completeness for Bookkeeping took 0.2516036033630371s
Reputation | Calculation of the PageRank for Bookkeeping took 0.020305156707763672s
Interlinking | Calculation of Degree of Connection for Bookkeeping took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bookkeeping took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Bookkeeping took 3.123283386230469e-05s
Believability | Calculation of trust value for Bookkeeping took 5.245208740234375e-06s
INFO | --- Analysis for https:raw.githubusercontent.comGVogelerbookkeepingmasterbookkeeping.ttl took 4.179472208023071s
Availability | SPARQL endpoint availability check for Legal Ontology took 5.1021575927734375e-05s
Availability | VoID file availability check for Legal Ontology took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for Legal Ontology took 0.2729451656341553s
Reputation | Calculation of the PageRank for Legal Ontology took 0.021536827087402344s
Interlinking | Calculation of Degree of Connection for Legal Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Legal Ontology took 0.0010352134704589844s
Interlinking | Calculation of Clustering coefficient for Legal Ontology took 3.981590270996094e-05s
Believability | Calculation of trust value for Legal Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for https:w3id.orgdefNyOnLegal# took 2.9082915782928467s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 4.887580871582031e-05s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0006601810455322266s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.2652144432067871s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.02050614356994629s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 8.130073547363281e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 7.62939453125e-06s
INFO | --- Analysis for https:www.childrensartmuseum.grLD-project took 2.6683788299560547s
Availability | SPARQL endpoint availability check for Writer Luigi Usai took 4.2438507080078125e-05s
Availability | VoID file availability check for Writer Luigi Usai took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for Writer Luigi Usai took 0.2885317802429199s
Reputation | Calculation of the PageRank for Writer Luigi Usai took 0.020416736602783203s
Interlinking | Calculation of Degree of Connection for Writer Luigi Usai took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Writer Luigi Usai took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Writer Luigi Usai took 2.9802322387695312e-05s
Believability | Calculation of trust value for Writer Luigi Usai took 7.62939453125e-06s
INFO | --- Analysis for https:www.luigiusai.itlinked-dataluigiusai took 2.5942740440368652s
Availability | SPARQL endpoint availability check for Hua Hin Health Tourism Data Set took 4.076957702636719e-05s
Availability | VoID file availability check for Hua Hin Health Tourism Data Set took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for Hua Hin Health Tourism Data Set took 0.25928592681884766s
Reputation | Calculation of the PageRank for Hua Hin Health Tourism Data Set took 0.021268844604492188s
Interlinking | Calculation of Degree of Connection for Hua Hin Health Tourism Data Set took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Hua Hin Health Tourism Data Set took 0.0009131431579589844s
Interlinking | Calculation of Clustering coefficient for Hua Hin Health Tourism Data Set took 4.100799560546875e-05s
Believability | Calculation of trust value for Hua Hin Health Tourism Data Set took 7.62939453125e-06s
INFO | --- Analysis for hua-hin-health-tourism-data-set took 2.960906744003296s
Availability | SPARQL endpoint availability check for University of Huddersfield -- Circulation and Recommendation Data took 4.0531158447265625e-05s
Availability | VoID file availability check for University of Huddersfield -- Circulation and Recommendation Data took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for University of Huddersfield -- Circulation and Recommendation Data took 0.2744870185852051s
Reputation | Calculation of the PageRank for University of Huddersfield -- Circulation and Recommendation Data took 0.02032756805419922s
Interlinking | Calculation of Degree of Connection for University of Huddersfield -- Circulation and Recommendation Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for University of Huddersfield -- Circulation and Recommendation Data took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for University of Huddersfield -- Circulation and Recommendation Data took 3.0279159545898438e-05s
Believability | Calculation of trust value for University of Huddersfield -- Circulation and Recommendation Data took 7.152557373046875e-06s
INFO | --- Analysis for hud-library-usagedata took 3.0077552795410156s
Availability | SPARQL endpoint availability check for Hungarian National Library (NSZL) catalog took 1.620673418045044s
Availability | VoID file availability check for Hungarian National Library (NSZL) catalog took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for Hungarian National Library (NSZL) catalog took 0.24749326705932617s
Reputation | Calculation of the PageRank for Hungarian National Library (NSZL) catalog took 0.02031993865966797s
Interlinking | Calculation of Degree of Connection for Hungarian National Library (NSZL) catalog took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Hungarian National Library (NSZL) catalog took 0.0007996559143066406s
Interlinking | Calculation of Clustering coefficient for Hungarian National Library (NSZL) catalog took 0.000110626220703125s
Believability | Calculation of trust value for Hungarian National Library (NSZL) catalog took 5.7220458984375e-06s
INFO | --- Analysis for hungarian-national-library-catalog took 4.552660942077637s
Availability | SPARQL endpoint availability check for IATE RDF took 5.6743621826171875e-05s
Availability | VoID file availability check for IATE RDF took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for IATE RDF took 0.2747316360473633s
Reputation | Calculation of the PageRank for IATE RDF took 0.020323991775512695s
Interlinking | Calculation of Degree of Connection for IATE RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for IATE RDF took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for IATE RDF took 3.743171691894531e-05s
Believability | Calculation of trust value for IATE RDF took 1.5974044799804688e-05s
INFO | --- Analysis for iate-rdf took 2.459378957748413s
Availability | SPARQL endpoint availability check for IATI as Linked Data took 0.6572310924530029s
Availability | VoID file availability check for IATI as Linked Data took 0.0011782646179199219s
Completeness | Calculation of interlinking completeness for IATI as Linked Data took 0.25655460357666016s
Reputation | Calculation of the PageRank for IATI as Linked Data took 0.02029252052307129s
Interlinking | Calculation of Degree of Connection for IATI as Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for IATI as Linked Data took 0.0007765293121337891s
Interlinking | Calculation of Clustering coefficient for IATI as Linked Data took 8.702278137207031e-05s
Believability | Calculation of trust value for IATI as Linked Data took 6.198883056640625e-06s
INFO | --- Analysis for iati-as-linked-data took 8.044402122497559s
Availability | SPARQL endpoint availability check for ICANE took 0.4367520809173584s
Availability | VoID file availability check for ICANE took 0.0008172988891601562s
Completeness | Calculation of interlinking completeness for ICANE took 0.2887568473815918s
Reputation | Calculation of the PageRank for ICANE took 0.020653486251831055s
Interlinking | Calculation of Degree of Connection for ICANE took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ICANE took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for ICANE took 0.00010848045349121094s
Believability | Calculation of trust value for ICANE took 6.198883056640625e-06s
INFO | --- Analysis for icane took 3.7237253189086914s
Availability | SPARQL endpoint availability check for ichoose took 0.14991331100463867s
Availability | VoID file availability check for ichoose took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for ichoose took 0.27474427223205566s
Reputation | Calculation of the PageRank for ichoose took 0.02041172981262207s
Interlinking | Calculation of Degree of Connection for ichoose took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for ichoose took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for ichoose took 6.651878356933594e-05s
Believability | Calculation of trust value for ichoose took 6.198883056640625e-06s
INFO | --- Analysis for ichoose took 83.89040732383728s
Availability | SPARQL endpoint availability check for The Iconology Dataset took 1.6723442077636719s
Availability | VoID file availability check for The Iconology Dataset took 0.0013439655303955078s
Extra | Recovery of all triples for The Iconology Dataset took 5.348137378692627s
Performance | Total latancy measurement for The Iconology Dataset took 0.5108094215393066s
Amount of data | Number of triples check for The Iconology Dataset took 0.21500396728515625s
Interoperability | New terms check for The Iconology Dataset took 1.3318045139312744s
Versatility | Languages check for The Iconology Dataset took 0.6392159461975098s
Interpretability | Number of blank nodes check for The Iconology Dataset took 0.22158384323120117s
Interpretability | RDF structures check for The Iconology Dataset took 0.14393353462219238s
Versatility | Serialization formats check for The Iconology Dataset took 0.11562108993530273s
Availability | RDF dump link check for The Iconology Dataset took 0.0983896255493164s
License | MR license check for The Iconology Dataset took 0.11678457260131836s
License | HR license check for The Iconology Dataset took 0.38675546646118164s
Amount of data | Number of property check for The Iconology Dataset took 0.10631465911865234s
Understandability | Number of label check for The Iconology Dataset took 0.16256284713745117s
Understandability | URI regex check for The Iconology Dataset took 0.17984437942504883s
Understandability | Vocabs check for The Iconology Dataset took 0.09191679954528809s
Verifiability | Authors check for The Iconology Dataset took 0.10241293907165527s
Verifiability | Publishers check for The Iconology Dataset took 0.09185910224914551s
Performance | Throughput check for The Iconology Dataset took 10.374367952346802s
Amount of data | Check the number of entities for The Iconology Dataset took 0.0003638267517089844s
Verifiability | Contribs. check for The Iconology Dataset took 0.08780074119567871s
Interlinking | sameAs chians check for The Iconology Dataset took 0.09670209884643555s
Interlinking | skos check for The Iconology Dataset took 0.09493660926818848s
Interlinking | skos check for The Iconology Dataset took 0.09113073348999023s
Timeliness | dataset update frequency check for The Iconology Dataset took 0.09486627578735352s
Currency | Creation date check for The Iconology Dataset took 0.19142556190490723s
Currency | Modification date check for The Iconology Dataset took 0.19903206825256348s
Rep.Conc. | URIs length for The Iconology Dataset took 1.3036556243896484s
Interoperability | New vocabularies check for The Iconology Dataset took 6.4373016357421875e-06s
Consistency | Deprecated classes/propertiers check for The Iconology Dataset took 0.08253884315490723s
Accuracy | Check Empty annotation labels for The Iconology Dataset took 0.2671217918395996s
Accuracy | Check White space in annotation for The Iconology Dataset took 0.01667308807373047s
Accuracy | Check Datatype consistency for The Iconology Dataset took 0.44008326530456543s
Consistency | Disjoint class check for The Iconology Dataset took 0.07228660583496094s
Consistency | Check Misplaced properties for The Iconology Dataset took 0.1511387825012207s
Consistency | Misplaced classes for The Iconology Dataset took 0.8820879459381104s
Consistency | Check Ontology hijacking for The Iconology Dataset took 1.493067741394043s
Consistency | Check Invalid usage of undefined classes for The Iconology Dataset took 1.1478726863861084s
Consistency | Check Invalid usage of undefined properties for The Iconology Dataset took 1.2491929531097412s
Conciseness | Check Extensional conciseness for The Iconology Dataset took 0.289661169052124s
Security | Sign check for The Iconology Dataset took 0.08768129348754883s
Availability | Check URIs Dereferenciability for The Iconology Dataset took 2519.546482563019s
Completeness | Calculation of interlinking completeness for The Iconology Dataset took 1.4163942337036133s
Reputation | Calculation of the PageRank for The Iconology Dataset took 0.027991294860839844s
Interlinking | Calculation of Degree of Connection for The Iconology Dataset took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for The Iconology Dataset took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for The Iconology Dataset took 1.6689300537109375e-05s
Interoperability | Check the re-using of existing vocabs for The Iconology Dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for The Iconology Dataset took 6.67572021484375e-06s
INFO | --- Analysis for iconology-dataset took 2581.4954175949097s
Availability | SPARQL endpoint availability check for Identifiers.org took 4.029273986816406e-05s
Availability | VoID file availability check for Identifiers.org took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for Identifiers.org took 0.2684512138366699s
Reputation | Calculation of the PageRank for Identifiers.org took 0.02226114273071289s
Interlinking | Calculation of Degree of Connection for Identifiers.org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Identifiers.org took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Identifiers.org took 3.62396240234375e-05s
Believability | Calculation of trust value for Identifiers.org took 5.9604644775390625e-06s
INFO | --- Analysis for identifiers-org took 4.292741298675537s
Availability | SPARQL endpoint availability check for IdRef: Sudoc authority data took 6.365776062011719e-05s
Availability | VoID file availability check for IdRef: Sudoc authority data took 0.0005838871002197266s
Completeness | Calculation of interlinking completeness for IdRef: Sudoc authority data took 0.3032107353210449s
Reputation | Calculation of the PageRank for IdRef: Sudoc authority data took 0.020136117935180664s
Interlinking | Calculation of Degree of Connection for IdRef: Sudoc authority data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IdRef: Sudoc authority data took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for IdRef: Sudoc authority data took 7.557868957519531e-05s
Believability | Calculation of trust value for IdRef: Sudoc authority data took 7.3909759521484375e-06s
INFO | --- Analysis for idreffr took 4.232549428939819s
Availability | SPARQL endpoint availability check for Intercontinental Dictionary Series took 0.9600865840911865s
Availability | VoID file availability check for Intercontinental Dictionary Series took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for Intercontinental Dictionary Series took 0.7137398719787598s
Reputation | Calculation of the PageRank for Intercontinental Dictionary Series took 0.020035982131958008s
Interlinking | Calculation of Degree of Connection for Intercontinental Dictionary Series took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Intercontinental Dictionary Series took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Intercontinental Dictionary Series took 4.7206878662109375e-05s
Believability | Calculation of trust value for Intercontinental Dictionary Series took 6.198883056640625e-06s
INFO | --- Analysis for ids took 5.241100072860718s
Availability | SPARQL endpoint availability check for ietflang took 4.172325134277344e-05s
Availability | VoID file availability check for ietflang took 0.0006575584411621094s
Completeness | Calculation of interlinking completeness for ietflang took 0.30722618103027344s
Reputation | Calculation of the PageRank for ietflang took 0.020148038864135742s
Interlinking | Calculation of Degree of Connection for ietflang took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for ietflang took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for ietflang took 4.410743713378906e-05s
Believability | Calculation of trust value for ietflang took 6.67572021484375e-06s
INFO | --- Analysis for ietflang took 13.675666570663452s
Availability | SPARQL endpoint availability check for Index Graecorum Vocabulorum in LiLa took 0.5779600143432617s
Availability | VoID file availability check for Index Graecorum Vocabulorum in LiLa took 0.0005970001220703125s
Completeness | Calculation of interlinking completeness for Index Graecorum Vocabulorum in LiLa took 0.2610785961151123s
Reputation | Calculation of the PageRank for Index Graecorum Vocabulorum in LiLa took 0.020218372344970703s
Interlinking | Calculation of Degree of Connection for Index Graecorum Vocabulorum in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Index Graecorum Vocabulorum in LiLa took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Index Graecorum Vocabulorum in LiLa took 3.4809112548828125e-05s
Believability | Calculation of trust value for Index Graecorum Vocabulorum in LiLa took 5.7220458984375e-06s
INFO | --- Analysis for IGVLL took 4.621042251586914s
Availability | SPARQL endpoint availability check for 3LGM² IHE Ontology took 0.520317554473877s
Availability | VoID file availability check for 3LGM² IHE Ontology took 0.0005588531494140625s
Extra | Recovery of all triples for 3LGM² IHE Ontology took 1.7877602577209473s
Performance | Total latancy measurement for 3LGM² IHE Ontology took 0.9527204036712646s
Amount of data | Number of triples check for 3LGM² IHE Ontology took 0.1968672275543213s
Interoperability | New terms check for 3LGM² IHE Ontology took 1.329507827758789s
Versatility | Languages check for 3LGM² IHE Ontology took 0.21283364295959473s
Interpretability | Number of blank nodes check for 3LGM² IHE Ontology took 0.19844818115234375s
Interpretability | RDF structures check for 3LGM² IHE Ontology took 0.209716796875s
Versatility | Serialization formats check for 3LGM² IHE Ontology took 0.18624258041381836s
Availability | RDF dump link check for 3LGM² IHE Ontology took 0.20792198181152344s
License | MR license check for 3LGM² IHE Ontology took 0.2070462703704834s
License | HR license check for 3LGM² IHE Ontology took 0.20353984832763672s
Amount of data | Number of property check for 3LGM² IHE Ontology took 0.19996881484985352s
Understandability | Number of label check for 3LGM² IHE Ontology took 0.18722271919250488s
Understandability | URI regex check for 3LGM² IHE Ontology took 0.38965439796447754s
Understandability | Vocabs check for 3LGM² IHE Ontology took 0.20393848419189453s
Verifiability | Authors check for 3LGM² IHE Ontology took 0.19325685501098633s
Verifiability | Publishers check for 3LGM² IHE Ontology took 0.19569158554077148s
Performance | Throughput check for 3LGM² IHE Ontology took 11.502030849456787s
Amount of data | Check the number of entities for 3LGM² IHE Ontology took 5.91278076171875e-05s
Verifiability | Contribs. check for 3LGM² IHE Ontology took 0.9357471466064453s
Interlinking | sameAs chians check for 3LGM² IHE Ontology took 0.19354557991027832s
Interlinking | skos check for 3LGM² IHE Ontology took 0.20123934745788574s
Interlinking | skos check for 3LGM² IHE Ontology took 0.19609880447387695s
Timeliness | dataset update frequency check for 3LGM² IHE Ontology took 0.19632411003112793s
Currency | Creation date check for 3LGM² IHE Ontology took 0.37026166915893555s
Currency | Modification date check for 3LGM² IHE Ontology took 0.3806295394897461s
Rep.Conc. | URIs length for 3LGM² IHE Ontology took 0.8282184600830078s
Interoperability | New vocabularies check for 3LGM² IHE Ontology took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for 3LGM² IHE Ontology took 0.18552637100219727s
Accuracy | Check Functional Property for 3LGM² IHE Ontology took 0.19623970985412598s
Accuracy | Check Inverse Functional Property for 3LGM² IHE Ontology took 0.18342995643615723s
Accuracy | Check Empty annotation labels for 3LGM² IHE Ontology took 0.32263779640197754s
Accuracy | Check White space in annotation for 3LGM² IHE Ontology took 0.001657724380493164s
Accuracy | Check Datatype consistency for 3LGM² IHE Ontology took 0.05011916160583496s
Consistency | Disjoint class check for 3LGM² IHE Ontology took 0.1940927505493164s
Consistency | Check Misplaced properties for 3LGM² IHE Ontology took 0.46819138526916504s
Consistency | Misplaced classes for 3LGM² IHE Ontology took 0.2774043083190918s
Consistency | Check Ontology hijacking for 3LGM² IHE Ontology took 1.4404239654541016s
Consistency | Check Invalid usage of undefined classes for 3LGM² IHE Ontology took 1.1646535396575928s
Consistency | Check Invalid usage of undefined properties for 3LGM² IHE Ontology took 1.3829033374786377s
Conciseness | Check Extensional conciseness for 3LGM² IHE Ontology took 0.030440330505371094s
Conciseness | Check Intensional conciseness for 3LGM² IHE Ontology took 0.19379258155822754s
Security | Sign check for 3LGM² IHE Ontology took 0.18438720703125s
Availability | Check URIs Dereferenciability for 3LGM² IHE Ontology took 282.3116798400879s
Completeness | Calculation of interlinking completeness for 3LGM² IHE Ontology took 0.8098211288452148s
Reputation | Calculation of the PageRank for 3LGM² IHE Ontology took 0.02044081687927246s
Interlinking | Calculation of Degree of Connection for 3LGM² IHE Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 3LGM² IHE Ontology took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for 3LGM² IHE Ontology took 3.7670135498046875e-05s
Interoperability | Check the re-using of existing vocabs for 3LGM² IHE Ontology took 1.430511474609375e-06s
Believability | Calculation of trust value for 3LGM² IHE Ontology took 6.67572021484375e-06s
INFO | --- Analysis for IHE took 333.9173402786255s
Availability | SPARQL endpoint availability check for Test Site, LOD Lab 317 took 0.06728577613830566s
Availability | VoID file availability check for Test Site, LOD Lab 317 took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Test Site, LOD Lab 317 took 0.7019650936126709s
Reputation | Calculation of the PageRank for Test Site, LOD Lab 317 took 0.020428895950317383s
Interlinking | Calculation of Degree of Connection for Test Site, LOD Lab 317 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Test Site, LOD Lab 317 took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Test Site, LOD Lab 317 took 3.0279159545898438e-05s
Believability | Calculation of trust value for Test Site, LOD Lab 317 took 7.152557373046875e-06s
INFO | --- Analysis for iislod-test took 4.338935613632202s
Availability | SPARQL endpoint availability check for Interpretation of Land Use Data in Ordos City took 4.267692565917969e-05s
Availability | VoID file availability check for Interpretation of Land Use Data in Ordos City took 0.000690460205078125s
Completeness | Calculation of interlinking completeness for Interpretation of Land Use Data in Ordos City took 0.7171542644500732s
Reputation | Calculation of the PageRank for Interpretation of Land Use Data in Ordos City took 0.020180463790893555s
Interlinking | Calculation of Degree of Connection for Interpretation of Land Use Data in Ordos City took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Interpretation of Land Use Data in Ordos City took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Interpretation of Land Use Data in Ordos City took 3.075599670410156e-05s
Believability | Calculation of trust value for Interpretation of Land Use Data in Ordos City took 7.152557373046875e-06s
INFO | --- Analysis for ILUSOC took 19.690608263015747s
Availability | SPARQL endpoint availability check for im@sparql took 6.859005451202393s
Availability | VoID file availability check for im@sparql took 0.0008530616760253906s
Completeness | Calculation of interlinking completeness for im@sparql took 0.28665614128112793s
Reputation | Calculation of the PageRank for im@sparql took 0.022471189498901367s
Interlinking | Calculation of Degree of Connection for im@sparql took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for im@sparql took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for im@sparql took 3.743171691894531e-05s
Believability | Calculation of trust value for im@sparql took 7.152557373046875e-06s
INFO | --- Analysis for im@sparql took 13.752177000045776s
Availability | SPARQL endpoint availability check for imagery bailingniao took 4.172325134277344e-05s
Availability | VoID file availability check for imagery bailingniao took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for imagery bailingniao took 0.2717733383178711s
Reputation | Calculation of the PageRank for imagery bailingniao took 0.02037501335144043s
Interlinking | Calculation of Degree of Connection for imagery bailingniao took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for imagery bailingniao took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for imagery bailingniao took 2.9325485229492188e-05s
Believability | Calculation of trust value for imagery bailingniao took 6.67572021484375e-06s
INFO | --- Analysis for imagery_bailingniao took 3.6391327381134033s
Availability | SPARQL endpoint availability check for Imagesnippets Image Descriptions took 1.1168625354766846s
Availability | VoID file availability check for Imagesnippets Image Descriptions took 0.0006759166717529297s
Extra | Recovery of all triples for Imagesnippets Image Descriptions took 23.508596420288086s
Performance | Total latancy measurement for Imagesnippets Image Descriptions took 3.419011354446411s
Amount of data | Number of triples check for Imagesnippets Image Descriptions took 10.712584972381592s
Interoperability | New terms check for Imagesnippets Image Descriptions took 3.305816888809204s
Versatility | Languages check for Imagesnippets Image Descriptions took 10.694517374038696s
Interpretability | Number of blank nodes check for Imagesnippets Image Descriptions took 8.671282052993774s
Security | Check HTTPS for Imagesnippets Image Descriptions took 0.7063338756561279s
Interpretability | RDF structures check for Imagesnippets Image Descriptions took 0.7455978393554688s
Versatility | Serialization formats check for Imagesnippets Image Descriptions took 0.6996893882751465s
Availability | RDF dump link check for Imagesnippets Image Descriptions took 0.701469898223877s
License | MR license check for Imagesnippets Image Descriptions took 0.7364068031311035s
License | HR license check for Imagesnippets Image Descriptions took 10.724465131759644s
Amount of data | Number of property check for Imagesnippets Image Descriptions took 0.7391290664672852s
Understandability | Number of label check for Imagesnippets Image Descriptions took 2.9161858558654785s
Understandability | URI regex check for Imagesnippets Image Descriptions took 1.3809731006622314s
Understandability | Vocabs check for Imagesnippets Image Descriptions took 0.7128992080688477s
Verifiability | Authors check for Imagesnippets Image Descriptions took 0.7130801677703857s
Verifiability | Publishers check for Imagesnippets Image Descriptions took 0.6753463745117188s
Performance | Throughput check for Imagesnippets Image Descriptions took 13.893956661224365s
Amount of data | Check the number of entities for Imagesnippets Image Descriptions took 8.273124694824219e-05s
Verifiability | Contribs. check for Imagesnippets Image Descriptions took 0.713566780090332s
Interlinking | sameAs chians check for Imagesnippets Image Descriptions took 0.7050654888153076s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.7052488327026367s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.6883034706115723s
Timeliness | dataset update frequency check for Imagesnippets Image Descriptions took 0.7468452453613281s
Currency | Creation date check for Imagesnippets Image Descriptions took 1.411905288696289s
Currency | Modification date check for Imagesnippets Image Descriptions took 1.4127330780029297s
Rep.Conc. | URIs length for Imagesnippets Image Descriptions took 27.298238277435303s
Interoperability | New vocabularies check for Imagesnippets Image Descriptions took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Imagesnippets Image Descriptions took 0.7184581756591797s
Accuracy | Check Functional Property for Imagesnippets Image Descriptions took 0.7146053314208984s
Accuracy | Check Inverse Functional Property for Imagesnippets Image Descriptions took 0.6993999481201172s
Consistency | Disjoint class check for Imagesnippets Image Descriptions took 0.6938667297363281s
Consistency | Check Misplaced properties for Imagesnippets Image Descriptions took 7.524714469909668s
Consistency | Check Ontology hijacking for Imagesnippets Image Descriptions took 16.49086618423462s
Consistency | Check Invalid usage of undefined properties for Imagesnippets Image Descriptions took 8.005090475082397s
Conciseness | Check Extensional conciseness for Imagesnippets Image Descriptions took 0.0001666545867919922s
Security | Sign check for Imagesnippets Image Descriptions took 0.6806647777557373s
Completeness | Calculation of interlinking completeness for Imagesnippets Image Descriptions took 0.281095027923584s
Reputation | Calculation of the PageRank for Imagesnippets Image Descriptions took 0.19917583465576172s
Interlinking | Calculation of Degree of Connection for Imagesnippets Image Descriptions took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Imagesnippets Image Descriptions took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Imagesnippets Image Descriptions took 0.00010585784912109375s
Interoperability | Check the re-using of existing vocabs for Imagesnippets Image Descriptions took 2.1457672119140625e-06s
Believability | Calculation of trust value for Imagesnippets Image Descriptions took 5.4836273193359375e-06s
INFO | --- Analysis for imagesnippets took 257.6947247982025s
Availability | SPARQL endpoint availability check for International Monetary Fund (IMF) Linked Data took 0.48825573921203613s
Availability | VoID file availability check for International Monetary Fund (IMF) Linked Data took 0.00044989585876464844s
Completeness | Calculation of interlinking completeness for International Monetary Fund (IMF) Linked Data took 0.7160863876342773s
Reputation | Calculation of the PageRank for International Monetary Fund (IMF) Linked Data took 0.020094633102416992s
Interlinking | Calculation of Degree of Connection for International Monetary Fund (IMF) Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for International Monetary Fund (IMF) Linked Data took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for International Monetary Fund (IMF) Linked Data took 9.465217590332031e-05s
Believability | Calculation of trust value for International Monetary Fund (IMF) Linked Data took 8.106231689453125e-06s
INFO | --- Analysis for imf-linked-data took 3.940790891647339s
Availability | SPARQL endpoint availability check for IMGpedia took 4.076957702636719e-05s
Availability | VoID file availability check for IMGpedia took 0.0002872943878173828s
Completeness | Calculation of interlinking completeness for IMGpedia took 0.2742021083831787s
Reputation | Calculation of the PageRank for IMGpedia took 0.020238876342773438s
Interlinking | Calculation of Degree of Connection for IMGpedia took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for IMGpedia took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for IMGpedia took 3.552436828613281e-05s
Believability | Calculation of trust value for IMGpedia took 6.67572021484375e-06s
INFO | --- Analysis for imgpedia took 4.386139392852783s
Availability | SPARQL endpoint availability check for Import Status of GMO Crops took 5.340576171875e-05s
Availability | VoID file availability check for Import Status of GMO Crops took 0.0002944469451904297s
Completeness | Calculation of interlinking completeness for Import Status of GMO Crops took 0.2692902088165283s
Reputation | Calculation of the PageRank for Import Status of GMO Crops took 0.020229101181030273s
Interlinking | Calculation of Degree of Connection for Import Status of GMO Crops took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Import Status of GMO Crops took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Import Status of GMO Crops took 2.8371810913085938e-05s
Believability | Calculation of trust value for Import Status of GMO Crops took 6.198883056640625e-06s
INFO | --- Analysis for import-status-of-gmo-crops took 3.4757895469665527s
Availability | SPARQL endpoint availability check for MD Imtiaz Ahammad took 4.100799560546875e-05s
Availability | VoID file availability check for MD Imtiaz Ahammad took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for MD Imtiaz Ahammad took 0.2808837890625s
Reputation | Calculation of the PageRank for MD Imtiaz Ahammad took 0.020316600799560547s
Interlinking | Calculation of Degree of Connection for MD Imtiaz Ahammad took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for MD Imtiaz Ahammad took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for MD Imtiaz Ahammad took 1.1444091796875e-05s
Believability | Calculation of trust value for MD Imtiaz Ahammad took 5.9604644775390625e-06s
INFO | --- Analysis for Imtiaz took 2.8708837032318115s
Availability | SPARQL endpoint availability check for Royalty Free Music took 4.00543212890625e-05s
Availability | VoID file availability check for Royalty Free Music took 0.0006206035614013672s
Completeness | Calculation of interlinking completeness for Royalty Free Music took 0.2700228691101074s
Reputation | Calculation of the PageRank for Royalty Free Music took 0.020088672637939453s
Interlinking | Calculation of Degree of Connection for Royalty Free Music took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Royalty Free Music took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Royalty Free Music took 2.8848648071289062e-05s
Believability | Calculation of trust value for Royalty Free Music took 6.4373016357421875e-06s
INFO | --- Analysis for inaudio.org took 5.0528974533081055s
Availability | SPARQL endpoint availability check for Income and production cost of grape by year took 3.933906555175781e-05s
Availability | VoID file availability check for Income and production cost of grape by year took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for Income and production cost of grape by year took 0.2796814441680908s
Reputation | Calculation of the PageRank for Income and production cost of grape by year took 0.0203707218170166s
Interlinking | Calculation of Degree of Connection for Income and production cost of grape by year took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Income and production cost of grape by year took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Income and production cost of grape by year took 2.765655517578125e-05s
Believability | Calculation of trust value for Income and production cost of grape by year took 5.7220458984375e-06s
INFO | --- Analysis for income-and-production-cost-of-grape-by-year took 3.442464828491211s
Availability | SPARQL endpoint availability check for Income and production cost of pear by year took 3.910064697265625e-05s
Availability | VoID file availability check for Income and production cost of pear by year took 0.00023937225341796875s
Completeness | Calculation of interlinking completeness for Income and production cost of pear by year took 0.28637242317199707s
Reputation | Calculation of the PageRank for Income and production cost of pear by year took 0.020121335983276367s
Interlinking | Calculation of Degree of Connection for Income and production cost of pear by year took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Income and production cost of pear by year took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Income and production cost of pear by year took 2.765655517578125e-05s
Believability | Calculation of trust value for Income and production cost of pear by year took 7.867813110351562e-06s
INFO | --- Analysis for income-and-production-cost-of-pear-by-year took 3.057462692260742s
Availability | SPARQL endpoint availability check for Index Thomisticus Treebank in LiLa took 0.46863746643066406s
Availability | VoID file availability check for Index Thomisticus Treebank in LiLa took 0.0006885528564453125s
Completeness | Calculation of interlinking completeness for Index Thomisticus Treebank in LiLa took 0.27297329902648926s
Reputation | Calculation of the PageRank for Index Thomisticus Treebank in LiLa took 0.02034902572631836s
Interlinking | Calculation of Degree of Connection for Index Thomisticus Treebank in LiLa took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Index Thomisticus Treebank in LiLa took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Index Thomisticus Treebank in LiLa took 3.5762786865234375e-05s
Believability | Calculation of trust value for Index Thomisticus Treebank in LiLa took 7.62939453125e-06s
INFO | --- Analysis for IndexThomisticusTreebank took 4.039112329483032s
Availability | SPARQL endpoint availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 4.124641418457031e-05s
Availability | VoID file availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0002903938293457031s
Completeness | Calculation of interlinking completeness for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.27916812896728516s
Reputation | Calculation of the PageRank for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.020116567611694336s
Interlinking | Calculation of Degree of Connection for INERTIA (INERTIA Energy Consumption Example Linked Data) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for INERTIA (INERTIA Energy Consumption Example Linked Data) took 3.075599670410156e-05s
Believability | Calculation of trust value for INERTIA (INERTIA Energy Consumption Example Linked Data) took 7.3909759521484375e-06s
INFO | --- Analysis for inertia-energy-consumption-example-linked-data took 3.0751190185546875s
Availability | SPARQL endpoint availability check for IneveryCREA, la comunidad de la creatividad educativa took 4.3392181396484375e-05s
Availability | VoID file availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.0006992816925048828s
Completeness | Calculation of interlinking completeness for IneveryCREA, la comunidad de la creatividad educativa took 0.2911720275878906s
Reputation | Calculation of the PageRank for IneveryCREA, la comunidad de la creatividad educativa took 0.020184040069580078s
Interlinking | Calculation of Degree of Connection for IneveryCREA, la comunidad de la creatividad educativa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IneveryCREA, la comunidad de la creatividad educativa took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for IneveryCREA, la comunidad de la creatividad educativa took 0.000110626220703125s
Believability | Calculation of trust value for IneveryCREA, la comunidad de la creatividad educativa took 6.67572021484375e-06s
INFO | --- Analysis for ineverycrea took 17.66160750389099s
Availability | SPARQL endpoint availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 4.291534423828125e-05s
Availability | VoID file availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0006265640258789062s
Completeness | Calculation of interlinking completeness for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.294980525970459s
Reputation | Calculation of the PageRank for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.02170848846435547s
Interlinking | Calculation of Degree of Connection for IneveryCREA Argentina, la comunidad de la creatividad educativa took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0009999275207519531s
Interlinking | Calculation of Clustering coefficient for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.00011014938354492188s
Believability | Calculation of trust value for IneveryCREA Argentina, la comunidad de la creatividad educativa took 7.867813110351562e-06s
INFO | --- Analysis for ineverycrea-argentina took 9.72927474975586s
Availability | SPARQL endpoint availability check for Influence Tracker Dataset took 522.9452500343323s
Availability | VoID file availability check for Influence Tracker Dataset took 0.0007350444793701172s
Completeness | Calculation of interlinking completeness for Influence Tracker Dataset took 0.7026712894439697s
Reputation | Calculation of the PageRank for Influence Tracker Dataset took 0.02118515968322754s
Interlinking | Calculation of Degree of Connection for Influence Tracker Dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Influence Tracker Dataset took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Influence Tracker Dataset took 7.748603820800781e-05s
Believability | Calculation of trust value for Influence Tracker Dataset took 7.152557373046875e-06s
INFO | --- Analysis for influence-tracker-dataset took 1082.2944416999817s
Availability | SPARQL endpoint availability check for INSEMTIVES took 4.124641418457031e-05s
Availability | VoID file availability check for INSEMTIVES took 0.0002834796905517578s
Completeness | Calculation of interlinking completeness for INSEMTIVES took 0.7134182453155518s
Reputation | Calculation of the PageRank for INSEMTIVES took 0.020783185958862305s
Interlinking | Calculation of Degree of Connection for INSEMTIVES took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for INSEMTIVES took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for INSEMTIVES took 2.9802322387695312e-05s
Believability | Calculation of trust value for INSEMTIVES took 6.198883056640625e-06s
INFO | --- Analysis for insemtives took 7.577220678329468s
Availability | SPARQL endpoint availability check for instagram.person took 3.933906555175781e-05s
Availability | VoID file availability check for instagram.person took 0.0002760887145996094s
Completeness | Calculation of interlinking completeness for instagram.person took 0.2828097343444824s
Reputation | Calculation of the PageRank for instagram.person took 0.02037525177001953s
Interlinking | Calculation of Degree of Connection for instagram.person took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for instagram.person took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for instagram.person took 3.170967102050781e-05s
Believability | Calculation of trust value for instagram.person took 7.3909759521484375e-06s
INFO | --- Analysis for instagram_person took 4.87715744972229s
Availability | SPARQL endpoint availability check for instagram.videoobject took 3.910064697265625e-05s
Availability | VoID file availability check for instagram.videoobject took 0.00023412704467773438s
Completeness | Calculation of interlinking completeness for instagram.videoobject took 0.25733041763305664s
Reputation | Calculation of the PageRank for instagram.videoobject took 0.020485639572143555s
Interlinking | Calculation of Degree of Connection for instagram.videoobject took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for instagram.videoobject took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for instagram.videoobject took 3.0279159545898438e-05s
Believability | Calculation of trust value for instagram.videoobject took 5.9604644775390625e-06s
INFO | --- Analysis for instagram_videoobject took 3.763608694076538s
Availability | SPARQL endpoint availability check for Instance Hub Countries took 4.220008850097656e-05s
Availability | VoID file availability check for Instance Hub Countries took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for Instance Hub Countries took 0.2784435749053955s
Reputation | Calculation of the PageRank for Instance Hub Countries took 0.02071976661682129s
Interlinking | Calculation of Degree of Connection for Instance Hub Countries took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Instance Hub Countries took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Instance Hub Countries took 3.62396240234375e-05s
Believability | Calculation of trust value for Instance Hub Countries took 6.198883056640625e-06s
INFO | --- Analysis for instance-hub-countries took 3.911151170730591s
Availability | SPARQL endpoint availability check for Instance Hub Fiscal Years took 4.2438507080078125e-05s
Availability | VoID file availability check for Instance Hub Fiscal Years took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for Instance Hub Fiscal Years took 0.2570788860321045s
Reputation | Calculation of the PageRank for Instance Hub Fiscal Years took 0.020594358444213867s
Interlinking | Calculation of Degree of Connection for Instance Hub Fiscal Years took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Instance Hub Fiscal Years took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Instance Hub Fiscal Years took 3.147125244140625e-05s
Believability | Calculation of trust value for Instance Hub Fiscal Years took 5.7220458984375e-06s
INFO | --- Analysis for instance-hub-fiscal-years took 2.832637071609497s
Availability | SPARQL endpoint availability check for Instance Hub Organizations took 4.0531158447265625e-05s
Availability | VoID file availability check for Instance Hub Organizations took 0.0002295970916748047s
Completeness | Calculation of interlinking completeness for Instance Hub Organizations took 0.25891542434692383s
Reputation | Calculation of the PageRank for Instance Hub Organizations took 0.02062201499938965s
Interlinking | Calculation of Degree of Connection for Instance Hub Organizations took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Instance Hub Organizations took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Instance Hub Organizations took 4.029273986816406e-05s
Believability | Calculation of trust value for Instance Hub Organizations took 7.152557373046875e-06s
INFO | --- Analysis for instance-hub-organizations took 3.4338440895080566s
Availability | SPARQL endpoint availability check for Instance Hub People took 3.9577484130859375e-05s
Availability | VoID file availability check for Instance Hub People took 0.000225067138671875s
Completeness | Calculation of interlinking completeness for Instance Hub People took 0.2807884216308594s
Reputation | Calculation of the PageRank for Instance Hub People took 0.020424842834472656s
Interlinking | Calculation of Degree of Connection for Instance Hub People took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Instance Hub People took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Instance Hub People took 3.0994415283203125e-05s
Believability | Calculation of trust value for Instance Hub People took 2.8133392333984375e-05s
INFO | --- Analysis for instance-hub-people took 2.9844729900360107s
Availability | SPARQL endpoint availability check for Instance Hub US Civil Servants took 4.172325134277344e-05s
Availability | VoID file availability check for Instance Hub US Civil Servants took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for Instance Hub US Civil Servants took 0.2876255512237549s
Reputation | Calculation of the PageRank for Instance Hub US Civil Servants took 0.020638465881347656s
Interlinking | Calculation of Degree of Connection for Instance Hub US Civil Servants took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Instance Hub US Civil Servants took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Civil Servants took 3.147125244140625e-05s
Believability | Calculation of trust value for Instance Hub US Civil Servants took 7.867813110351562e-06s
INFO | --- Analysis for instance-hub-us-civil-servants took 3.0054824352264404s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Committees took 4.172325134277344e-05s
Availability | VoID file availability check for Instance Hub US Congressional Committees took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Committees took 0.2556588649749756s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Committees took 0.02068805694580078s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Committees took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Committees took 0.0008208751678466797s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Committees took 3.409385681152344e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Committees took 6.9141387939453125e-06s
INFO | --- Analysis for instance-hub-us-congressional-committees took 2.9921200275421143s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Districts took 7.987022399902344e-05s
Availability | VoID file availability check for Instance Hub US Congressional Districts took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Districts took 0.27065110206604004s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Districts took 0.02032947540283203s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Districts took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Districts took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Districts took 2.9325485229492188e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Districts took 6.67572021484375e-06s
INFO | --- Analysis for instance-hub-us-congressional-districts took 2.947169542312622s
Availability | SPARQL endpoint availability check for Instance Hub US Crops took 4.100799560546875e-05s
Availability | VoID file availability check for Instance Hub US Crops took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for Instance Hub US Crops took 0.294830322265625s
Reputation | Calculation of the PageRank for Instance Hub US Crops took 0.02080512046813965s
Interlinking | Calculation of Degree of Connection for Instance Hub US Crops took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Instance Hub US Crops took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Crops took 3.123283386230469e-05s
Believability | Calculation of trust value for Instance Hub US Crops took 6.9141387939453125e-06s
INFO | --- Analysis for instance-hub-us-crops took 3.047624349594116s
Availability | SPARQL endpoint availability check for Instance Hub US Federal Agencies took 4.1961669921875e-05s
Availability | VoID file availability check for Instance Hub US Federal Agencies took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for Instance Hub US Federal Agencies took 0.2613692283630371s
Reputation | Calculation of the PageRank for Instance Hub US Federal Agencies took 0.020462751388549805s
Interlinking | Calculation of Degree of Connection for Instance Hub US Federal Agencies took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Instance Hub US Federal Agencies took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Federal Agencies took 3.123283386230469e-05s
Believability | Calculation of trust value for Instance Hub US Federal Agencies took 6.9141387939453125e-06s
INFO | --- Analysis for instance-hub-us-federal-agencies took 2.936117649078369s
Availability | SPARQL endpoint availability check for Instance Hub US States and Territories took 6.604194641113281e-05s
Availability | VoID file availability check for Instance Hub US States and Territories took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for Instance Hub US States and Territories took 0.2771260738372803s
Reputation | Calculation of the PageRank for Instance Hub US States and Territories took 0.02026820182800293s
Interlinking | Calculation of Degree of Connection for Instance Hub US States and Territories took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Instance Hub US States and Territories took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Instance Hub US States and Territories took 3.0279159545898438e-05s
Believability | Calculation of trust value for Instance Hub US States and Territories took 7.3909759521484375e-06s
INFO | --- Analysis for instance-hub-us-states-and-territories took 2.971494436264038s
Availability | SPARQL endpoint availability check for Instance Hub US Toxic Chemicals took 4.029273986816406e-05s
Availability | VoID file availability check for Instance Hub US Toxic Chemicals took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Instance Hub US Toxic Chemicals took 0.27576422691345215s
Reputation | Calculation of the PageRank for Instance Hub US Toxic Chemicals took 0.020746946334838867s
Interlinking | Calculation of Degree of Connection for Instance Hub US Toxic Chemicals took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Instance Hub US Toxic Chemicals took 0.0008161067962646484s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Toxic Chemicals took 4.076957702636719e-05s
Believability | Calculation of trust value for Instance Hub US Toxic Chemicals took 6.67572021484375e-06s
INFO | --- Analysis for instance-hub-us-toxic-chemicals took 3.027411699295044s
Availability | SPARQL endpoint availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 4.00543212890625e-05s
Availability | VoID file availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.2815873622894287s
Reputation | Calculation of the PageRank for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.02034163475036621s
Interlinking | Calculation of Degree of Connection for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 3.075599670410156e-05s
Believability | Calculation of trust value for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 5.7220458984375e-06s
INFO | --- Analysis for integrated-human-geography-service-for-lod took 3.0171327590942383s
Availability | SPARQL endpoint availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 4.220008850097656e-05s
Availability | VoID file availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0005643367767333984s
Completeness | Calculation of interlinking completeness for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.29017162322998047s
Reputation | Calculation of the PageRank for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.020358562469482422s
Interlinking | Calculation of Degree of Connection for Interactive Maps, a collection of interactive flash maps (GNOSS) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.00010204315185546875s
Believability | Calculation of trust value for Interactive Maps, a collection of interactive flash maps (GNOSS) took 6.9141387939453125e-06s
INFO | --- Analysis for interactivemaps-gnoss took 3.1321749687194824s
Availability | SPARQL endpoint availability check for Interakce mezi účinnými látkami took 4.172325134277344e-05s
Availability | VoID file availability check for Interakce mezi účinnými látkami took 0.00023102760314941406s
Completeness | Calculation of interlinking completeness for Interakce mezi účinnými látkami took 0.2771260738372803s
Reputation | Calculation of the PageRank for Interakce mezi účinnými látkami took 0.020476341247558594s
Interlinking | Calculation of Degree of Connection for Interakce mezi účinnými látkami took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Interakce mezi účinnými látkami took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Interakce mezi účinnými látkami took 3.314018249511719e-05s
Believability | Calculation of trust value for Interakce mezi účinnými látkami took 7.152557373046875e-06s
INFO | --- Analysis for interakce-mezi---inn-mi-l-tkami took 3.0051727294921875s
Availability | SPARQL endpoint availability check for intervalue took 3.5513389110565186s
Availability | VoID file availability check for intervalue took 0.0007140636444091797s
Completeness | Calculation of interlinking completeness for intervalue took 0.27052974700927734s
Reputation | Calculation of the PageRank for intervalue took 0.020563364028930664s
Interlinking | Calculation of Degree of Connection for intervalue took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for intervalue took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for intervalue took 6.723403930664062e-05s
Believability | Calculation of trust value for intervalue took 5.9604644775390625e-06s
INFO | --- Analysis for intervalue took 5.99796986579895s
Availability | SPARQL endpoint availability check for Inztrow took 4.2438507080078125e-05s
Availability | VoID file availability check for Inztrow took 0.0007607936859130859s
Completeness | Calculation of interlinking completeness for Inztrow took 0.26023197174072266s
Reputation | Calculation of the PageRank for Inztrow took 0.020751953125s
Interlinking | Calculation of Degree of Connection for Inztrow took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Inztrow took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Inztrow took 3.266334533691406e-05s
Believability | Calculation of trust value for Inztrow took 9.298324584960938e-06s
INFO | --- Analysis for Inztrow took 4.635017395019531s
Availability | SPARQL endpoint availability check for IPBES Assessments Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for IPBES Assessments Ontology took 0.0006597042083740234s
Completeness | Calculation of interlinking completeness for IPBES Assessments Ontology took 0.26207399368286133s
Reputation | Calculation of the PageRank for IPBES Assessments Ontology took 0.020448684692382812s
Interlinking | Calculation of Degree of Connection for IPBES Assessments Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for IPBES Assessments Ontology took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for IPBES Assessments Ontology took 3.218650817871094e-05s
Believability | Calculation of trust value for IPBES Assessments Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for ipbes took 3.9845385551452637s
Availability | SPARQL endpoint availability check for IPTC NewsCodes took 4.1961669921875e-05s
Availability | VoID file availability check for IPTC NewsCodes took 0.0005970001220703125s
Completeness | Calculation of interlinking completeness for IPTC NewsCodes took 0.27080225944519043s
Reputation | Calculation of the PageRank for IPTC NewsCodes took 0.020470619201660156s
Interlinking | Calculation of Degree of Connection for IPTC NewsCodes took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for IPTC NewsCodes took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for IPTC NewsCodes took 4.363059997558594e-05s
Believability | Calculation of trust value for IPTC NewsCodes took 5.7220458984375e-06s
INFO | --- Analysis for iptc-newscodes took 3.6361749172210693s
Availability | SPARQL endpoint availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 4.076957702636719e-05s
Availability | VoID file availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.25931239128112793s
Reputation | Calculation of the PageRank for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.020566225051879883s
Interlinking | Calculation of Degree of Connection for Irstea Weather Dataset of the Montoldre Experimental Farm took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Irstea Weather Dataset of the Montoldre Experimental Farm took 3.147125244140625e-05s
Believability | Calculation of trust value for Irstea Weather Dataset of the Montoldre Experimental Farm took 5.7220458984375e-06s
INFO | --- Analysis for irstea-weather-dataset-of-the-montoldre-experimental-farm took 3.0113120079040527s
Availability | SPARQL endpoint availability check for iServe: Linked Services Registry took 2.531468391418457s
Availability | VoID file availability check for iServe: Linked Services Registry took 0.0003418922424316406s
Completeness | Calculation of interlinking completeness for iServe: Linked Services Registry took 0.2851142883300781s
Reputation | Calculation of the PageRank for iServe: Linked Services Registry took 0.020572900772094727s
Interlinking | Calculation of Degree of Connection for iServe: Linked Services Registry took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for iServe: Linked Services Registry took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for iServe: Linked Services Registry took 0.00010395050048828125s
Believability | Calculation of trust value for iServe: Linked Services Registry took 6.198883056640625e-06s
INFO | --- Analysis for iserve took 9.404708623886108s
Availability | SPARQL endpoint availability check for ISIC V4 took 20.84951424598694s
Availability | VoID file availability check for ISIC V4 took 0.0009009838104248047s
Completeness | Calculation of interlinking completeness for ISIC V4 took 0.2827279567718506s
Reputation | Calculation of the PageRank for ISIC V4 took 0.020664215087890625s
Interlinking | Calculation of Degree of Connection for ISIC V4 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ISIC V4 took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for ISIC V4 took 3.4332275390625e-05s
Believability | Calculation of trust value for ISIC V4 took 5.0067901611328125e-06s
INFO | --- Analysis for isic-v4 took 113.35261845588684s
Availability | SPARQL endpoint availability check for Isidore took 4.267692565917969e-05s
Availability | VoID file availability check for Isidore took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Isidore took 0.7029156684875488s
Reputation | Calculation of the PageRank for Isidore took 0.020659446716308594s
Interlinking | Calculation of Degree of Connection for Isidore took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Isidore took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Isidore took 2.9802322387695312e-05s
Believability | Calculation of trust value for Isidore took 7.867813110351562e-06s
INFO | --- Analysis for isidore took 3.9411323070526123s
Availability | SPARQL endpoint availability check for ISIL->DBpedia took 4.124641418457031e-05s
Availability | VoID file availability check for ISIL->DBpedia took 0.0006432533264160156s
Completeness | Calculation of interlinking completeness for ISIL->DBpedia took 0.29988646507263184s
Reputation | Calculation of the PageRank for ISIL->DBpedia took 0.020284414291381836s
Interlinking | Calculation of Degree of Connection for ISIL->DBpedia took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ISIL->DBpedia took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for ISIL->DBpedia took 7.462501525878906e-05s
Believability | Calculation of trust value for ISIL->DBpedia took 5.245208740234375e-06s
INFO | --- Analysis for isil-dbpedia took 5.074662685394287s
Availability | SPARQL endpoint availability check for Linked ISO 3166-2 Data took 3.981590270996094e-05s
Availability | VoID file availability check for Linked ISO 3166-2 Data took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for Linked ISO 3166-2 Data took 0.2890803813934326s
Reputation | Calculation of the PageRank for Linked ISO 3166-2 Data took 0.020250797271728516s
Interlinking | Calculation of Degree of Connection for Linked ISO 3166-2 Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked ISO 3166-2 Data took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Linked ISO 3166-2 Data took 3.1948089599609375e-05s
Believability | Calculation of trust value for Linked ISO 3166-2 Data took 6.198883056640625e-06s
INFO | --- Analysis for iso-3166-2-data took 3.0628294944763184s
Availability | SPARQL endpoint availability check for Published subjects for languages in ISO 639 took 4.220008850097656e-05s
Availability | VoID file availability check for Published subjects for languages in ISO 639 took 0.0005843639373779297s
Completeness | Calculation of interlinking completeness for Published subjects for languages in ISO 639 took 0.2838771343231201s
Reputation | Calculation of the PageRank for Published subjects for languages in ISO 639 took 0.0205385684967041s
Interlinking | Calculation of Degree of Connection for Published subjects for languages in ISO 639 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Published subjects for languages in ISO 639 took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Published subjects for languages in ISO 639 took 3.62396240234375e-05s
Believability | Calculation of trust value for Published subjects for languages in ISO 639 took 6.67572021484375e-06s
INFO | --- Analysis for iso-639-oasis took 3.3080334663391113s
Availability | SPARQL endpoint availability check for ISOcat took 4.1961669921875e-05s
Availability | VoID file availability check for ISOcat took 0.0005676746368408203s
Completeness | Calculation of interlinking completeness for ISOcat took 0.273754358291626s
Reputation | Calculation of the PageRank for ISOcat took 0.020184040069580078s
Interlinking | Calculation of Degree of Connection for ISOcat took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ISOcat took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for ISOcat took 5.888938903808594e-05s
Believability | Calculation of trust value for ISOcat took 1.71661376953125e-05s
INFO | --- Analysis for isocat took 3.9532620906829834s
Availability | SPARQL endpoint availability check for ISOcat-metadata took 4.1484832763671875e-05s
Availability | VoID file availability check for ISOcat-metadata took 0.0005328655242919922s
Completeness | Calculation of interlinking completeness for ISOcat-metadata took 0.2807044982910156s
Reputation | Calculation of the PageRank for ISOcat-metadata took 0.020667076110839844s
Interlinking | Calculation of Degree of Connection for ISOcat-metadata took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ISOcat-metadata took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for ISOcat-metadata took 3.8623809814453125e-05s
Believability | Calculation of trust value for ISOcat-metadata took 7.3909759521484375e-06s
INFO | --- Analysis for isocat-metadata took 4.876288890838623s
Availability | SPARQL endpoint availability check for ISPRA - Mitigation measures in Italy for national soil protection took 4.267692565917969e-05s
Availability | VoID file availability check for ISPRA - Mitigation measures in Italy for national soil protection took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for ISPRA - Mitigation measures in Italy for national soil protection took 0.26711368560791016s
Reputation | Calculation of the PageRank for ISPRA - Mitigation measures in Italy for national soil protection took 0.02042245864868164s
Interlinking | Calculation of Degree of Connection for ISPRA - Mitigation measures in Italy for national soil protection took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ISPRA - Mitigation measures in Italy for national soil protection took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for ISPRA - Mitigation measures in Italy for national soil protection took 2.956390380859375e-05s
Believability | Calculation of trust value for ISPRA - Mitigation measures in Italy for national soil protection took 6.4373016357421875e-06s
INFO | --- Analysis for ispra-lod-ihi took 2.9765095710754395s
Availability | SPARQL endpoint availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.30084824562072754s
Availability | VoID file availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0005645751953125s
Extra | Recovery of all triples for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 8.430138349533081s
Performance | Total latancy measurement for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.7631943225860596s
Amount of data | Number of triples check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.249281644821167s
Interoperability | New terms check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.966433525085449s
Versatility | Languages check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 90.36202263832092s
Interpretability | Number of blank nodes check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.27892374992370605s
Security | Check HTTPS for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.10002446174621582s
Interpretability | RDF structures check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.26641082763671875s
Versatility | Serialization formats check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.20587992668151855s
Availability | RDF dump link check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.15491771697998047s
License | MR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.276857852935791s
License | HR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 90.35811233520508s
Amount of data | Number of property check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.18857765197753906s
Understandability | Number of label check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.6457879543304443s
Understandability | URI regex check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.5077664852142334s
Understandability | Vocabs check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.20918917655944824s
Verifiability | Authors check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2797684669494629s
Verifiability | Publishers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1972203254699707s
Performance | Throughput check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.500779628753662s
Amount of data | Check the number of entities for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 4.839897155761719e-05s
Verifiability | Contribs. check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.18702912330627441s
Interlinking | sameAs chians check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3343183994293213s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.529994010925293s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.44337010383605957s
Timeliness | dataset update frequency check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.26666855812072754s
Currency | Creation date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.9801006317138672s
Currency | Modification date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2227795124053955s
Rep.Conc. | URIs length for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 15.209328889846802s
Interoperability | New vocabularies check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.15094304084777832s
Accuracy | Check Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.14183568954467773s
Accuracy | Check Inverse Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.14332842826843262s
Accuracy | Check Empty annotation labels for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 4.825246810913086s
Accuracy | Check White space in annotation for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3147010803222656s
Accuracy | Check Datatype consistency for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2596254348754883s
Consistency | Disjoint class check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.20006632804870605s
Consistency | Check Misplaced properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.941917896270752s
Consistency | Misplaced classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.9777834415435791s
Consistency | Check Ontology hijacking for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 4.28421950340271s
Consistency | Check Invalid usage of undefined classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.1825344562530518s
Consistency | Check Invalid usage of undefined properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.700223922729492s
Conciseness | Check Extensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.28469157218933105s
Conciseness | Check Intensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.20497679710388184s
Security | Sign check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.14962530136108398s
Availability | Check URIs Dereferenciability for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 5.314309358596802s
Completeness | Calculation of interlinking completeness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.8601210117340088s
Reputation | Calculation of the PageRank for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.02747821807861328s
Interlinking | Calculation of Degree of Connection for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0015797615051269531s
Interlinking | Calculation of Clustering coefficient for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.00019669532775878906s
Interoperability | Check the re-using of existing vocabs for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.86102294921875e-06s
Believability | Calculation of trust value for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 7.62939453125e-06s
INFO | --- Analysis for ispra-lod-place took 463.2885162830353s
Availability | SPARQL endpoint availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 4.00543212890625e-05s
Availability | VoID file availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.7120985984802246s
Reputation | Calculation of the PageRank for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.020718812942504883s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian National Tide Gauge Network (RMN) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian National Tide Gauge Network (RMN) took 3.0279159545898438e-05s
Believability | Calculation of trust value for ISPRA - The Italian National Tide Gauge Network (RMN) took 6.9141387939453125e-06s
INFO | --- Analysis for ispra-lod-rmn took 5.1128129959106445s
Availability | SPARQL endpoint availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.15640926361083984s
Availability | VoID file availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.0005421638488769531s
Extra | Recovery of all triples for ISPRA - The Italian Data Buoy Network (RON) took 10.439470767974854s
Performance | Total latancy measurement for ISPRA - The Italian Data Buoy Network (RON) took 0.8625326156616211s
Amount of data | Number of triples check for ISPRA - The Italian Data Buoy Network (RON) took 0.24472379684448242s
Interoperability | New terms check for ISPRA - The Italian Data Buoy Network (RON) took 2.9090018272399902s
Versatility | Languages check for ISPRA - The Italian Data Buoy Network (RON) took 92.24576234817505s
Interpretability | Number of blank nodes check for ISPRA - The Italian Data Buoy Network (RON) took 0.20227980613708496s
Security | Check HTTPS for ISPRA - The Italian Data Buoy Network (RON) took 0.10072064399719238s
Interpretability | RDF structures check for ISPRA - The Italian Data Buoy Network (RON) took 0.16511964797973633s
Versatility | Serialization formats check for ISPRA - The Italian Data Buoy Network (RON) took 0.17122554779052734s
Availability | RDF dump link check for ISPRA - The Italian Data Buoy Network (RON) took 0.19634366035461426s
License | MR license check for ISPRA - The Italian Data Buoy Network (RON) took 0.25127315521240234s
License | HR license check for ISPRA - The Italian Data Buoy Network (RON) took 92.10022807121277s
Amount of data | Number of property check for ISPRA - The Italian Data Buoy Network (RON) took 0.18065905570983887s
Understandability | Number of label check for ISPRA - The Italian Data Buoy Network (RON) took 1.608884334564209s
Understandability | URI regex check for ISPRA - The Italian Data Buoy Network (RON) took 0.5402979850769043s
Understandability | Vocabs check for ISPRA - The Italian Data Buoy Network (RON) took 0.26604390144348145s
Verifiability | Authors check for ISPRA - The Italian Data Buoy Network (RON) took 0.2489008903503418s
Verifiability | Publishers check for ISPRA - The Italian Data Buoy Network (RON) took 0.17671656608581543s
Performance | Throughput check for ISPRA - The Italian Data Buoy Network (RON) took 10.542985916137695s
Amount of data | Check the number of entities for ISPRA - The Italian Data Buoy Network (RON) took 7.05718994140625e-05s
Verifiability | Contribs. check for ISPRA - The Italian Data Buoy Network (RON) took 0.24255895614624023s
Interlinking | sameAs chians check for ISPRA - The Italian Data Buoy Network (RON) took 0.27229857444763184s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.48816776275634766s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.4807565212249756s
Timeliness | dataset update frequency check for ISPRA - The Italian Data Buoy Network (RON) took 0.27236104011535645s
Currency | Creation date check for ISPRA - The Italian Data Buoy Network (RON) took 0.3255951404571533s
Currency | Modification date check for ISPRA - The Italian Data Buoy Network (RON) took 0.13717103004455566s
Rep.Conc. | URIs length for ISPRA - The Italian Data Buoy Network (RON) took 15.504018783569336s
Interoperability | New vocabularies check for ISPRA - The Italian Data Buoy Network (RON) took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The Italian Data Buoy Network (RON) took 0.14627981185913086s
Accuracy | Check Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.15143537521362305s
Accuracy | Check Inverse Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.1676647663116455s
Accuracy | Check Empty annotation labels for ISPRA - The Italian Data Buoy Network (RON) took 4.7067835330963135s
Accuracy | Check White space in annotation for ISPRA - The Italian Data Buoy Network (RON) took 0.3161191940307617s
Accuracy | Check Datatype consistency for ISPRA - The Italian Data Buoy Network (RON) took 0.2763521671295166s
Consistency | Disjoint class check for ISPRA - The Italian Data Buoy Network (RON) took 0.180680513381958s
Consistency | Check Misplaced properties for ISPRA - The Italian Data Buoy Network (RON) took 9.718002319335938s
Consistency | Misplaced classes for ISPRA - The Italian Data Buoy Network (RON) took 0.9992377758026123s
Consistency | Check Ontology hijacking for ISPRA - The Italian Data Buoy Network (RON) took 4.859700441360474s
Consistency | Check Invalid usage of undefined classes for ISPRA - The Italian Data Buoy Network (RON) took 1.1869311332702637s
Consistency | Check Invalid usage of undefined properties for ISPRA - The Italian Data Buoy Network (RON) took 10.756872177124023s
Conciseness | Check Extensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.2783501148223877s
Conciseness | Check Intensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.16506719589233398s
Security | Sign check for ISPRA - The Italian Data Buoy Network (RON) took 0.18523001670837402s
Availability | Check URIs Dereferenciability for ISPRA - The Italian Data Buoy Network (RON) took 5.342167139053345s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian Data Buoy Network (RON) took 0.7049770355224609s
Reputation | Calculation of the PageRank for ISPRA - The Italian Data Buoy Network (RON) took 0.020946025848388672s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian Data Buoy Network (RON) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian Data Buoy Network (RON) took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian Data Buoy Network (RON) took 4.887580871582031e-05s
Interoperability | Check the re-using of existing vocabs for ISPRA - The Italian Data Buoy Network (RON) took 2.1457672119140625e-06s
Believability | Calculation of trust value for ISPRA - The Italian Data Buoy Network (RON) took 5.9604644775390625e-06s
INFO | --- Analysis for ispra-lod-ron took 472.16653323173523s
Availability | SPARQL endpoint availability check for ISPRA - Soil Consumption Indicators in Italy took 4.1961669921875e-05s
Availability | VoID file availability check for ISPRA - Soil Consumption Indicators in Italy took 0.00033855438232421875s
Completeness | Calculation of interlinking completeness for ISPRA - Soil Consumption Indicators in Italy took 0.2628664970397949s
Reputation | Calculation of the PageRank for ISPRA - Soil Consumption Indicators in Italy took 0.02019190788269043s
Interlinking | Calculation of Degree of Connection for ISPRA - Soil Consumption Indicators in Italy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ISPRA - Soil Consumption Indicators in Italy took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for ISPRA - Soil Consumption Indicators in Italy took 3.361701965332031e-05s
Believability | Calculation of trust value for ISPRA - Soil Consumption Indicators in Italy took 6.67572021484375e-06s
INFO | --- Analysis for ispra-lod-sc took 5.867565870285034s
Availability | SPARQL endpoint availability check for ISSA Agritrop Dataset took 20.53252148628235s
Availability | VoID file availability check for ISSA Agritrop Dataset took 0.0006499290466308594s
Completeness | Calculation of interlinking completeness for ISSA Agritrop Dataset took 0.2690250873565674s
Reputation | Calculation of the PageRank for ISSA Agritrop Dataset took 0.020542144775390625s
Interlinking | Calculation of Degree of Connection for ISSA Agritrop Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ISSA Agritrop Dataset took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for ISSA Agritrop Dataset took 9.202957153320312e-05s
Believability | Calculation of trust value for ISSA Agritrop Dataset took 5.9604644775390625e-06s
INFO | --- Analysis for issa-agritrop took 55.7037079334259s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.220008850097656e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.2684624195098877s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.020771026611328125s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 3.0517578125e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 9.059906005859375e-06s
INFO | --- Analysis for ISSN:0080-3626 took 3.7103824615478516s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 5.650520324707031e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0006258487701416016s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.3128378391265869s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.020615339279174805s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 3.218650817871094e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 5.0067901611328125e-06s
INFO | --- Analysis for ISSN:_0080-3626 took 3.3047876358032227s
Availability | SPARQL endpoint availability check for Aktualne zagadnienia klasyfikacji map took 4.1484832763671875e-05s
Availability | VoID file availability check for Aktualne zagadnienia klasyfikacji map took 0.0003859996795654297s
Completeness | Calculation of interlinking completeness for Aktualne zagadnienia klasyfikacji map took 0.7045159339904785s
Reputation | Calculation of the PageRank for Aktualne zagadnienia klasyfikacji map took 0.020719051361083984s
Interlinking | Calculation of Degree of Connection for Aktualne zagadnienia klasyfikacji map took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Aktualne zagadnienia klasyfikacji map took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Aktualne zagadnienia klasyfikacji map took 3.0994415283203125e-05s
Believability | Calculation of trust value for Aktualne zagadnienia klasyfikacji map took 5.0067901611328125e-06s
INFO | --- Analysis for ISSN:_0080-3626. took 3.057304620742798s
Availability | SPARQL endpoint availability check for ISTAT Immigration (LinkedOpenData.it) took 1.679102897644043s
Availability | VoID file availability check for ISTAT Immigration (LinkedOpenData.it) took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for ISTAT Immigration (LinkedOpenData.it) took 0.28150367736816406s
Reputation | Calculation of the PageRank for ISTAT Immigration (LinkedOpenData.it) took 0.020509958267211914s
Interlinking | Calculation of Degree of Connection for ISTAT Immigration (LinkedOpenData.it) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ISTAT Immigration (LinkedOpenData.it) took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigration (LinkedOpenData.it) took 8.606910705566406e-05s
Believability | Calculation of trust value for ISTAT Immigration (LinkedOpenData.it) took 4.0531158447265625e-06s
INFO | --- Analysis for istat-immigration took 4.1574015617370605s
Availability | SPARQL endpoint availability check for ISTAT Immigrazione (Linkedopendata.it) took 3.8623809814453125e-05s
Availability | VoID file availability check for ISTAT Immigrazione (Linkedopendata.it) took 0.00022482872009277344s
Completeness | Calculation of interlinking completeness for ISTAT Immigrazione (Linkedopendata.it) took 0.26190805435180664s
Reputation | Calculation of the PageRank for ISTAT Immigrazione (Linkedopendata.it) took 0.020685672760009766s
Interlinking | Calculation of Degree of Connection for ISTAT Immigrazione (Linkedopendata.it) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ISTAT Immigrazione (Linkedopendata.it) took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigrazione (Linkedopendata.it) took 2.9087066650390625e-05s
Believability | Calculation of trust value for ISTAT Immigrazione (Linkedopendata.it) took 5.4836273193359375e-06s
INFO | --- Analysis for istat-immigrazione took 3.074516773223877s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Italian Republic took 30.876471042633057s
Availability | VoID file availability check for List of prices of medicinal products marketed in Italian Republic took 0.000762939453125s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Italian Republic took 0.2752704620361328s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Italian Republic took 0.020548582077026367s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Italian Republic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Italian Republic took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Italian Republic took 3.719329833984375e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Italian Republic took 4.5299530029296875e-06s
INFO | --- Analysis for it-aifa-drug-prices took 105.5446937084198s
Availability | SPARQL endpoint availability check for Italian public schools (LinkedOpenData.it) took 1.6969947814941406s
Availability | VoID file availability check for Italian public schools (LinkedOpenData.it) took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for Italian public schools (LinkedOpenData.it) took 0.2672998905181885s
Reputation | Calculation of the PageRank for Italian public schools (LinkedOpenData.it) took 0.0209348201751709s
Interlinking | Calculation of Degree of Connection for Italian public schools (LinkedOpenData.it) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Italian public schools (LinkedOpenData.it) took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Italian public schools (LinkedOpenData.it) took 7.653236389160156e-05s
Believability | Calculation of trust value for Italian public schools (LinkedOpenData.it) took 6.198883056640625e-06s
INFO | --- Analysis for italian-public-schools-linkedopendata-it took 5.556057929992676s
Availability | SPARQL endpoint availability check for Academic Bibliography data available from Acta Cryst E took 4.0531158447265625e-05s
Availability | VoID file availability check for Academic Bibliography data available from Acta Cryst E took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for Academic Bibliography data available from Acta Cryst E took 0.26688408851623535s
Reputation | Calculation of the PageRank for Academic Bibliography data available from Acta Cryst E took 0.020397663116455078s
Interlinking | Calculation of Degree of Connection for Academic Bibliography data available from Acta Cryst E took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Academic Bibliography data available from Acta Cryst E took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Academic Bibliography data available from Acta Cryst E took 3.075599670410156e-05s
Believability | Calculation of trust value for Academic Bibliography data available from Acta Cryst E took 5.7220458984375e-06s
INFO | --- Analysis for iucr-acta-cryst-e took 3.7500481605529785s
Availability | SPARQL endpoint availability check for Global Data on PFAS Contamination in Organisms took 4.3392181396484375e-05s
Availability | VoID file availability check for Global Data on PFAS Contamination in Organisms took 0.00022459030151367188s
Completeness | Calculation of interlinking completeness for Global Data on PFAS Contamination in Organisms took 0.28963565826416016s
Reputation | Calculation of the PageRank for Global Data on PFAS Contamination in Organisms took 0.025101184844970703s
Interlinking | Calculation of Degree of Connection for Global Data on PFAS Contamination in Organisms took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Global Data on PFAS Contamination in Organisms took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Global Data on PFAS Contamination in Organisms took 1.3113021850585938e-05s
Believability | Calculation of trust value for Global Data on PFAS Contamination in Organisms took 7.3909759521484375e-06s
INFO | --- Analysis for iue-PFASData took 2.947437047958374s
Availability | SPARQL endpoint availability check for IWMI Research Reports took 4.1484832763671875e-05s
Availability | VoID file availability check for IWMI Research Reports took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for IWMI Research Reports took 0.270458459854126s
Reputation | Calculation of the PageRank for IWMI Research Reports took 0.0204620361328125s
Interlinking | Calculation of Degree of Connection for IWMI Research Reports took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for IWMI Research Reports took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for IWMI Research Reports took 2.956390380859375e-05s
Believability | Calculation of trust value for IWMI Research Reports took 6.4373016357421875e-06s
INFO | --- Analysis for iwmi-research-reports took 3.44423508644104s
Availability | SPARQL endpoint availability check for IWN took 4.2438507080078125e-05s
Availability | VoID file availability check for IWN took 0.0007026195526123047s
Completeness | Calculation of interlinking completeness for IWN took 0.8047606945037842s
Reputation | Calculation of the PageRank for IWN took 0.02077507972717285s
Interlinking | Calculation of Degree of Connection for IWN took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for IWN took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for IWN took 4.6253204345703125e-05s
Believability | Calculation of trust value for IWN took 1.0251998901367188e-05s
INFO | --- Analysis for iwn took 364.72444009780884s
Availability | SPARQL endpoint availability check for J-GLOBAL knowledge took 5.626678466796875e-05s
Availability | VoID file availability check for J-GLOBAL knowledge took 0.00028777122497558594s
Completeness | Calculation of interlinking completeness for J-GLOBAL knowledge took 0.27693915367126465s
Reputation | Calculation of the PageRank for J-GLOBAL knowledge took 0.020290613174438477s
Interlinking | Calculation of Degree of Connection for J-GLOBAL knowledge took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for J-GLOBAL knowledge took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for J-GLOBAL knowledge took 2.9802322387695312e-05s
Believability | Calculation of trust value for J-GLOBAL knowledge took 6.9141387939453125e-06s
INFO | --- Analysis for j-global-knowledge took 3.8483023643493652s
Availability | SPARQL endpoint availability check for J.UCS Journal of Universal Computer Science took 5.125999450683594e-05s
Availability | VoID file availability check for J.UCS Journal of Universal Computer Science took 0.00022792816162109375s
Completeness | Calculation of interlinking completeness for J.UCS Journal of Universal Computer Science took 0.25783824920654297s
Reputation | Calculation of the PageRank for J.UCS Journal of Universal Computer Science took 0.020211219787597656s
Interlinking | Calculation of Degree of Connection for J.UCS Journal of Universal Computer Science took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for J.UCS Journal of Universal Computer Science took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for J.UCS Journal of Universal Computer Science took 2.7894973754882812e-05s
Believability | Calculation of trust value for J.UCS Journal of Universal Computer Science took 5.7220458984375e-06s
INFO | --- Analysis for j-ucs-journal-of-universal-computer-science took 3.4241690635681152s
Availability | SPARQL endpoint availability check for DBTune.org Jamendo RDF Server took 9.011184692382812s
Availability | VoID file availability check for DBTune.org Jamendo RDF Server took 0.0007348060607910156s
Completeness | Calculation of interlinking completeness for DBTune.org Jamendo RDF Server took 0.3013303279876709s
Reputation | Calculation of the PageRank for DBTune.org Jamendo RDF Server took 0.0206754207611084s
Interlinking | Calculation of Degree of Connection for DBTune.org Jamendo RDF Server took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for DBTune.org Jamendo RDF Server took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for DBTune.org Jamendo RDF Server took 6.532669067382812e-05s
Believability | Calculation of trust value for DBTune.org Jamendo RDF Server took 6.9141387939453125e-06s
INFO | --- Analysis for jamendo-dbtune took 25.16836428642273s
Availability | SPARQL endpoint availability check for National Radioactivity Stat as Linked Data took 4.124641418457031e-05s
Availability | VoID file availability check for National Radioactivity Stat as Linked Data took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for National Radioactivity Stat as Linked Data took 0.2756776809692383s
Reputation | Calculation of the PageRank for National Radioactivity Stat as Linked Data took 0.0211639404296875s
Interlinking | Calculation of Degree of Connection for National Radioactivity Stat as Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for National Radioactivity Stat as Linked Data took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for National Radioactivity Stat as Linked Data took 4.744529724121094e-05s
Believability | Calculation of trust value for National Radioactivity Stat as Linked Data took 4.76837158203125e-06s
INFO | --- Analysis for japan-radioactivity-stat took 5.401821136474609s
Availability | SPARQL endpoint availability check for JEL Classification took 4.0531158447265625e-05s
Availability | VoID file availability check for JEL Classification took 0.0006144046783447266s
Completeness | Calculation of interlinking completeness for JEL Classification took 0.2575185298919678s
Reputation | Calculation of the PageRank for JEL Classification took 0.02043318748474121s
Interlinking | Calculation of Degree of Connection for JEL Classification took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for JEL Classification took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for JEL Classification took 3.075599670410156e-05s
Believability | Calculation of trust value for JEL Classification took 7.62939453125e-06s
INFO | --- Analysis for jel-classification took 4.808477878570557s
Availability | SPARQL endpoint availability check for JISC Open Bibliography British National Bibliography dataset took 0.44548630714416504s
Availability | VoID file availability check for JISC Open Bibliography British National Bibliography dataset took 0.0006654262542724609s
Completeness | Calculation of interlinking completeness for JISC Open Bibliography British National Bibliography dataset took 0.30205297470092773s
Reputation | Calculation of the PageRank for JISC Open Bibliography British National Bibliography dataset took 0.020357370376586914s
Interlinking | Calculation of Degree of Connection for JISC Open Bibliography British National Bibliography dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for JISC Open Bibliography British National Bibliography dataset took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for JISC Open Bibliography British National Bibliography dataset took 2.9802322387695312e-05s
Believability | Calculation of trust value for JISC Open Bibliography British National Bibliography dataset took 7.3909759521484375e-06s
INFO | --- Analysis for jiscopenbib-bl_bnb-1 took 6.0359721183776855s
Availability | SPARQL endpoint availability check for JITA Classification System of Library and Information Science took 260.5811231136322s
Availability | VoID file availability check for JITA Classification System of Library and Information Science took 0.0006515979766845703s
Completeness | Calculation of interlinking completeness for JITA Classification System of Library and Information Science took 0.773698091506958s
Reputation | Calculation of the PageRank for JITA Classification System of Library and Information Science took 0.020618915557861328s
Interlinking | Calculation of Degree of Connection for JITA Classification System of Library and Information Science took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for JITA Classification System of Library and Information Science took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for JITA Classification System of Library and Information Science took 7.987022399902344e-05s
Believability | Calculation of trust value for JITA Classification System of Library and Information Science took 6.4373016357421875e-06s
INFO | --- Analysis for jita took 539.4570503234863s
Availability | SPARQL endpoint availability check for The JMdict (Japanese-Multilingual Dictionary) project took 4.9591064453125e-05s
Availability | VoID file availability check for The JMdict (Japanese-Multilingual Dictionary) project took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for The JMdict (Japanese-Multilingual Dictionary) project took 0.2698085308074951s
Reputation | Calculation of the PageRank for The JMdict (Japanese-Multilingual Dictionary) project took 0.021663665771484375s
Interlinking | Calculation of Degree of Connection for The JMdict (Japanese-Multilingual Dictionary) project took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The JMdict (Japanese-Multilingual Dictionary) project took 0.0007846355438232422s
Interlinking | Calculation of Clustering coefficient for The JMdict (Japanese-Multilingual Dictionary) project took 4.029273986816406e-05s
Believability | Calculation of trust value for The JMdict (Japanese-Multilingual Dictionary) project took 6.9141387939453125e-06s
INFO | --- Analysis for jmdict took 5.170181751251221s
Availability | SPARQL endpoint availability check for John Goodwin's Family Tree took 20.07007336616516s
Availability | VoID file availability check for John Goodwin's Family Tree took 0.0007708072662353516s
Completeness | Calculation of interlinking completeness for John Goodwin's Family Tree took 0.6935398578643799s
Reputation | Calculation of the PageRank for John Goodwin's Family Tree took 0.020595788955688477s
Interlinking | Calculation of Degree of Connection for John Goodwin's Family Tree took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for John Goodwin's Family Tree took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for John Goodwin's Family Tree took 8.7738037109375e-05s
Believability | Calculation of trust value for John Goodwin's Family Tree took 1.7642974853515625e-05s
INFO | --- Analysis for john-goodwins-family-tree took 64.2261323928833s
Availability | SPARQL endpoint availability check for Japanese Course of Study LOD took 5.435943603515625e-05s
Availability | VoID file availability check for Japanese Course of Study LOD took 0.0005857944488525391s
Completeness | Calculation of interlinking completeness for Japanese Course of Study LOD took 0.2987098693847656s
Reputation | Calculation of the PageRank for Japanese Course of Study LOD took 0.020705699920654297s
Interlinking | Calculation of Degree of Connection for Japanese Course of Study LOD took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Japanese Course of Study LOD took 0.0008280277252197266s
Interlinking | Calculation of Clustering coefficient for Japanese Course of Study LOD took 3.7670135498046875e-05s
Believability | Calculation of trust value for Japanese Course of Study LOD took 7.152557373046875e-06s
INFO | --- Analysis for jp-cos took 5.393273115158081s
Availability | SPARQL endpoint availability check for Japanese Textbook LOD took 7.677078247070312e-05s
Availability | VoID file availability check for Japanese Textbook LOD took 0.0006866455078125s
Completeness | Calculation of interlinking completeness for Japanese Textbook LOD took 0.29483842849731445s
Reputation | Calculation of the PageRank for Japanese Textbook LOD took 0.020844459533691406s
Interlinking | Calculation of Degree of Connection for Japanese Textbook LOD took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Japanese Textbook LOD took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Japanese Textbook LOD took 4.553794860839844e-05s
Believability | Calculation of trust value for Japanese Textbook LOD took 6.67572021484375e-06s
INFO | --- Analysis for jp-textbook took 5.226696729660034s
Availability | SPARQL endpoint availability check for JRC-Names took 4.315376281738281e-05s
Availability | VoID file availability check for JRC-Names took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for JRC-Names took 0.7113628387451172s
Reputation | Calculation of the PageRank for JRC-Names took 0.020265817642211914s
Interlinking | Calculation of Degree of Connection for JRC-Names took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for JRC-Names took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for JRC-Names took 3.314018249511719e-05s
Believability | Calculation of trust value for JRC-Names took 7.152557373046875e-06s
INFO | --- Analysis for jrc-names-ec took 5.725288391113281s
Availability | SPARQL endpoint availability check for JRC-Names-MLODE took 1.1148178577423096s
Availability | VoID file availability check for JRC-Names-MLODE took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for JRC-Names-MLODE took 0.272768497467041s
Reputation | Calculation of the PageRank for JRC-Names-MLODE took 0.020445823669433594s
Interlinking | Calculation of Degree of Connection for JRC-Names-MLODE took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for JRC-Names-MLODE took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for JRC-Names-MLODE took 6.699562072753906e-05s
Believability | Calculation of trust value for JRC-Names-MLODE took 7.152557373046875e-06s
INFO | --- Analysis for jrc-names-mlode took 3.641556739807129s
Availability | SPARQL endpoint availability check for JudaicaLink took 4.1484832763671875e-05s
Availability | VoID file availability check for JudaicaLink took 0.0007088184356689453s
Completeness | Calculation of interlinking completeness for JudaicaLink took 0.2695322036743164s
Reputation | Calculation of the PageRank for JudaicaLink took 0.02057623863220215s
Interlinking | Calculation of Degree of Connection for JudaicaLink took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for JudaicaLink took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for JudaicaLink took 0.00010251998901367188s
Believability | Calculation of trust value for JudaicaLink took 7.152557373046875e-06s
INFO | --- Analysis for judaicalink took 6.057344436645508s
Availability | SPARQL endpoint availability check for KAIST silver standard corpus took 3.910064697265625e-05s
Availability | VoID file availability check for KAIST silver standard corpus took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for KAIST silver standard corpus took 0.24716734886169434s
Reputation | Calculation of the PageRank for KAIST silver standard corpus took 0.020596027374267578s
Interlinking | Calculation of Degree of Connection for KAIST silver standard corpus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for KAIST silver standard corpus took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for KAIST silver standard corpus took 2.9087066650390625e-05s
Believability | Calculation of trust value for KAIST silver standard corpus took 5.7220458984375e-06s
INFO | --- Analysis for kaist-silver-standard-corpus took 2.9614481925964355s
Availability | SPARQL endpoint availability check for KAKEN took 4.100799560546875e-05s
Availability | VoID file availability check for KAKEN took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for KAKEN took 0.2764132022857666s
Reputation | Calculation of the PageRank for KAKEN took 0.02055644989013672s
Interlinking | Calculation of Degree of Connection for KAKEN took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for KAKEN took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for KAKEN took 2.9802322387695312e-05s
Believability | Calculation of trust value for KAKEN took 6.4373016357421875e-06s
INFO | --- Analysis for kaken took 3.0156619548797607s
Availability | SPARQL endpoint availability check for Kallikratis municipalities took 0.07998490333557129s
Availability | VoID file availability check for Kallikratis municipalities took 0.0002219676971435547s
Completeness | Calculation of interlinking completeness for Kallikratis municipalities took 0.2829461097717285s
Reputation | Calculation of the PageRank for Kallikratis municipalities took 0.02034282684326172s
Interlinking | Calculation of Degree of Connection for Kallikratis municipalities took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Kallikratis municipalities took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Kallikratis municipalities took 9.131431579589844e-05s
Believability | Calculation of trust value for Kallikratis municipalities took 4.76837158203125e-06s
INFO | --- Analysis for kallikratis-municipalities took 2.515660285949707s
Availability | SPARQL endpoint availability check for Openflights Routes took 3.933906555175781e-05s
Availability | VoID file availability check for Openflights Routes took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for Openflights Routes took 0.2607097625732422s
Reputation | Calculation of the PageRank for Openflights Routes took 0.02042412757873535s
Interlinking | Calculation of Degree of Connection for Openflights Routes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Openflights Routes took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Openflights Routes took 3.0279159545898438e-05s
Believability | Calculation of trust value for Openflights Routes took 7.867813110351562e-06s
INFO | --- Analysis for kasabi-openflights-routes took 2.990628957748413s
Availability | SPARQL endpoint availability check for EU Soccer League took 4.1484832763671875e-05s
Availability | VoID file availability check for EU Soccer League took 0.0003566741943359375s
Completeness | Calculation of interlinking completeness for EU Soccer League took 0.26975226402282715s
Reputation | Calculation of the PageRank for EU Soccer League took 0.020349502563476562s
Interlinking | Calculation of Degree of Connection for EU Soccer League took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EU Soccer League took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for EU Soccer League took 2.956390380859375e-05s
Believability | Calculation of trust value for EU Soccer League took 5.4836273193359375e-06s
INFO | --- Analysis for KG:Course_Submission took 3.828749656677246s
Availability | SPARQL endpoint availability check for Legal Knowledge Graph took 4.076957702636719e-05s
Availability | VoID file availability check for Legal Knowledge Graph took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for Legal Knowledge Graph took 0.28183746337890625s
Reputation | Calculation of the PageRank for Legal Knowledge Graph took 0.020572662353515625s
Interlinking | Calculation of Degree of Connection for Legal Knowledge Graph took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Legal Knowledge Graph took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Legal Knowledge Graph took 1.1920928955078125e-05s
Believability | Calculation of trust value for Legal Knowledge Graph took 3.24249267578125e-05s
INFO | --- Analysis for KING took 2.753685474395752s
Availability | SPARQL endpoint availability check for Klappstuhlclub took 4.5299530029296875e-05s
Availability | VoID file availability check for Klappstuhlclub took 0.0006740093231201172s
Completeness | Calculation of interlinking completeness for Klappstuhlclub took 0.2790071964263916s
Reputation | Calculation of the PageRank for Klappstuhlclub took 0.022219181060791016s
Interlinking | Calculation of Degree of Connection for Klappstuhlclub took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Klappstuhlclub took 0.0008065700531005859s
Interlinking | Calculation of Clustering coefficient for Klappstuhlclub took 6.985664367675781e-05s
Believability | Calculation of trust value for Klappstuhlclub took 4.76837158203125e-06s
INFO | --- Analysis for klappstuhlclub took 12.606040716171265s
Availability | SPARQL endpoint availability check for Linked Sensor Data (Kno.e.sis) took 10.72419786453247s
Availability | VoID file availability check for Linked Sensor Data (Kno.e.sis) took 0.0005357265472412109s
Completeness | Calculation of interlinking completeness for Linked Sensor Data (Kno.e.sis) took 0.28965115547180176s
Reputation | Calculation of the PageRank for Linked Sensor Data (Kno.e.sis) took 0.020656108856201172s
Interlinking | Calculation of Degree of Connection for Linked Sensor Data (Kno.e.sis) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Sensor Data (Kno.e.sis) took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Linked Sensor Data (Kno.e.sis) took 6.151199340820312e-05s
Believability | Calculation of trust value for Linked Sensor Data (Kno.e.sis) took 7.62939453125e-06s
INFO | --- Analysis for knoesis-linked-sensor-data took 23.235239267349243s
Availability | SPARQL endpoint availability check for Knowledge Forest took 3.981590270996094e-05s
Availability | VoID file availability check for Knowledge Forest took 0.00022363662719726562s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.29151201248168945s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.020374059677124023s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 2.8371810913085938e-05s
Believability | Calculation of trust value for Knowledge Forest took 6.67572021484375e-06s
INFO | --- Analysis for knowledge-map took 3.017242193222046s
Availability | SPARQL endpoint availability check for Knowledge Forest took 4.124641418457031e-05s
Availability | VoID file availability check for Knowledge Forest took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.2789032459259033s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.020261526107788086s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 2.7179718017578125e-05s
Believability | Calculation of trust value for Knowledge Forest took 6.67572021484375e-06s
INFO | --- Analysis for KnowledgeFusion took 2.4189417362213135s
Availability | SPARQL endpoint availability check for KORE 50 NIF NER Corpus took 4.2438507080078125e-05s
Availability | VoID file availability check for KORE 50 NIF NER Corpus took 0.0007431507110595703s
Completeness | Calculation of interlinking completeness for KORE 50 NIF NER Corpus took 0.3015255928039551s
Reputation | Calculation of the PageRank for KORE 50 NIF NER Corpus took 0.020719289779663086s
Interlinking | Calculation of Degree of Connection for KORE 50 NIF NER Corpus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for KORE 50 NIF NER Corpus took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for KORE 50 NIF NER Corpus took 6.771087646484375e-05s
Believability | Calculation of trust value for KORE 50 NIF NER Corpus took 6.9141387939453125e-06s
INFO | --- Analysis for kore-50-nif-ner-corpus took 14.29282259941101s
Availability | SPARQL endpoint availability check for Korea Intellectual Propert Office(KIPO) took 3.9577484130859375e-05s
Availability | VoID file availability check for Korea Intellectual Propert Office(KIPO) took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for Korea Intellectual Propert Office(KIPO) took 0.26828432083129883s
Reputation | Calculation of the PageRank for Korea Intellectual Propert Office(KIPO) took 0.020780086517333984s
Interlinking | Calculation of Degree of Connection for Korea Intellectual Propert Office(KIPO) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Korea Intellectual Propert Office(KIPO) took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Korea Intellectual Propert Office(KIPO) took 3.075599670410156e-05s
Believability | Calculation of trust value for Korea Intellectual Propert Office(KIPO) took 8.106231689453125e-06s
INFO | --- Analysis for korea-intellectual-propert-office-kipo took 3.3234705924987793s
Availability | SPARQL endpoint availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 5.555152893066406e-05s
Availability | VoID file availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.2869124412536621s
Reputation | Calculation of the PageRank for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.020186185836791992s
Interlinking | Calculation of Degree of Connection for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 2.7418136596679688e-05s
Believability | Calculation of trust value for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 5.9604644775390625e-06s
INFO | --- Analysis for Kronika_naukowa_Biblioteki_Jagiellońskiej took 2.4299612045288086s
Availability | SPARQL endpoint availability check for Korean Traditional Recipes took 9.465217590332031e-05s
Availability | VoID file availability check for Korean Traditional Recipes took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for Korean Traditional Recipes took 0.26018476486206055s
Reputation | Calculation of the PageRank for Korean Traditional Recipes took 0.021010637283325195s
Interlinking | Calculation of Degree of Connection for Korean Traditional Recipes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Korean Traditional Recipes took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Korean Traditional Recipes took 3.075599670410156e-05s
Believability | Calculation of trust value for Korean Traditional Recipes took 7.62939453125e-06s
INFO | --- Analysis for ktr took 3.019202709197998s
Availability | SPARQL endpoint availability check for Informatics Studies took 4.172325134277344e-05s
Availability | VoID file availability check for Informatics Studies took 0.0005774497985839844s
Completeness | Calculation of interlinking completeness for Informatics Studies took 0.27352118492126465s
Reputation | Calculation of the PageRank for Informatics Studies took 0.020690441131591797s
Interlinking | Calculation of Degree of Connection for Informatics Studies took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Informatics Studies took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for Informatics Studies took 3.337860107421875e-05s
Believability | Calculation of trust value for Informatics Studies took 7.3909759521484375e-06s
INFO | --- Analysis for Kumar,_Gireesh__and_Singh,_Anand took 3.000138282775879s
Availability | SPARQL endpoint availability check for Kidney and Urinary Pathway Knowledge Base took 0.03830599784851074s
Availability | VoID file availability check for Kidney and Urinary Pathway Knowledge Base took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for Kidney and Urinary Pathway Knowledge Base took 0.2756316661834717s
Reputation | Calculation of the PageRank for Kidney and Urinary Pathway Knowledge Base took 0.02031397819519043s
Interlinking | Calculation of Degree of Connection for Kidney and Urinary Pathway Knowledge Base took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Kidney and Urinary Pathway Knowledge Base took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Kidney and Urinary Pathway Knowledge Base took 3.5762786865234375e-05s
Believability | Calculation of trust value for Kidney and Urinary Pathway Knowledge Base took 5.9604644775390625e-06s
INFO | --- Analysis for kupkb took 2.5145833492279053s
Availability | SPARQL endpoint availability check for Léčivé přípravky ze SÚKL took 4.2438507080078125e-05s
Availability | VoID file availability check for Léčivé přípravky ze SÚKL took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for Léčivé přípravky ze SÚKL took 0.25829195976257324s
Reputation | Calculation of the PageRank for Léčivé přípravky ze SÚKL took 0.020734786987304688s
Interlinking | Calculation of Degree of Connection for Léčivé přípravky ze SÚKL took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Léčivé přípravky ze SÚKL took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Léčivé přípravky ze SÚKL took 3.170967102050781e-05s
Believability | Calculation of trust value for Léčivé přípravky ze SÚKL took 8.106231689453125e-06s
INFO | --- Analysis for l--iv--p--pravky-ze-s-kl took 2.9408321380615234s
Availability | SPARQL endpoint availability check for DBLP in RDF (L3S) took 10.055626153945923s
Availability | VoID file availability check for DBLP in RDF (L3S) took 0.0006818771362304688s
Completeness | Calculation of interlinking completeness for DBLP in RDF (L3S) took 0.27811646461486816s
Reputation | Calculation of the PageRank for DBLP in RDF (L3S) took 0.02066349983215332s
Interlinking | Calculation of Degree of Connection for DBLP in RDF (L3S) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBLP in RDF (L3S) took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for DBLP in RDF (L3S) took 7.939338684082031e-05s
Believability | Calculation of trust value for DBLP in RDF (L3S) took 8.344650268554688e-06s
INFO | --- Analysis for l3s-dblp took 48.53721880912781s
Availability | SPARQL endpoint availability check for Learning Analytics and Knowledge (LAK) Dataset took 24.108201026916504s
Availability | VoID file availability check for Learning Analytics and Knowledge (LAK) Dataset took 0.0005428791046142578s
Completeness | Calculation of interlinking completeness for Learning Analytics and Knowledge (LAK) Dataset took 0.29225659370422363s
Reputation | Calculation of the PageRank for Learning Analytics and Knowledge (LAK) Dataset took 0.020429134368896484s
Interlinking | Calculation of Degree of Connection for Learning Analytics and Knowledge (LAK) Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Learning Analytics and Knowledge (LAK) Dataset took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Learning Analytics and Knowledge (LAK) Dataset took 7.390975952148438e-05s
Believability | Calculation of trust value for Learning Analytics and Knowledge (LAK) Dataset took 7.867813110351562e-06s
INFO | --- Analysis for lak-dataset took 67.91698431968689s
Availability | SPARQL endpoint availability check for  Language Name Authority List  took 0.20685982704162598s
Availability | VoID file availability check for  Language Name Authority List  took 0.00043320655822753906s
Extra | Recovery of all triples for  Language Name Authority List  took 300.04465913772583s
Performance | Total latancy measurement for  Language Name Authority List  took 0.6246297359466553s
Amount of data | Number of triples check for  Language Name Authority List  took 300.07397508621216s
Interoperability | New terms check for  Language Name Authority List  took 201.6400167942047s
Versatility | Languages check for  Language Name Authority List  took 300.1401252746582s
Interpretability | Number of blank nodes check for  Language Name Authority List  took 16.74840760231018s
Security | Check HTTPS for  Language Name Authority List  took 0.3205242156982422s
Interpretability | RDF structures check for  Language Name Authority List  took 0.7073125839233398s
Versatility | Serialization formats check for  Language Name Authority List  took 17.717164039611816s
Availability | RDF dump link check for  Language Name Authority List  took 0.22310924530029297s
License | MR license check for  Language Name Authority List  took 0.20808959007263184s
License | HR license check for  Language Name Authority List  took 300.0477092266083s
Amount of data | Number of property check for  Language Name Authority List  took 0.1579744815826416s
Understandability | Number of label check for  Language Name Authority List  took 5.359912872314453s
Understandability | URI regex check for  Language Name Authority List  took 0.2692539691925049s
Understandability | Vocabs check for  Language Name Authority List  took 0.1539628505706787s
Verifiability | Authors check for  Language Name Authority List  took 0.455230712890625s
Verifiability | Publishers check for  Language Name Authority List  took 0.30914878845214844s
Performance | Throughput check for  Language Name Authority List  took 10.741788387298584s
Amount of data | Check the number of entities for  Language Name Authority List  took 3.0040740966796875e-05s
Verifiability | Contribs. check for  Language Name Authority List  took 0.10817146301269531s
Interlinking | sameAs chians check for  Language Name Authority List  took 11.10010313987732s
Interlinking | skos check for  Language Name Authority List  took 0.2960703372955322s
Interlinking | skos check for  Language Name Authority List  took 0.28874802589416504s
Timeliness | dataset update frequency check for  Language Name Authority List  took 0.21997928619384766s
Currency | Creation date check for  Language Name Authority List  took 0.9374713897705078s
Currency | Modification date check for  Language Name Authority List  took 0.1978473663330078s
Rep.Conc. | URIs length for  Language Name Authority List  took 603.9938898086548s
Interoperability | New vocabularies check for  Language Name Authority List  took 5.245208740234375e-06s
Consistency | Deprecated classes/propertiers check for  Language Name Authority List  took 0.18906044960021973s
Accuracy | Check Empty annotation labels for  Language Name Authority List  took 141.85452961921692s
Accuracy | Check White space in annotation for  Language Name Authority List  took 3.1933786869049072s
Consistency | Disjoint class check for  Language Name Authority List  took 0.20770478248596191s
Consistency | Check Misplaced properties for  Language Name Authority List  took 300.8456883430481s
Consistency | Misplaced classes for  Language Name Authority List  took 0.5220599174499512s
Consistency | Check Ontology hijacking for  Language Name Authority List  took 129.59432363510132s
Consistency | Check Invalid usage of undefined properties for  Language Name Authority List  took 301.4407248497009s
Conciseness | Check Extensional conciseness for  Language Name Authority List  took 0.00020503997802734375s
Conciseness | Check Intensional conciseness for  Language Name Authority List  took 0.8181507587432861s
Security | Sign check for  Language Name Authority List  took 0.20692205429077148s
Completeness | Calculation of interlinking completeness for  Language Name Authority List  took 1.15936279296875s
Reputation | Calculation of the PageRank for  Language Name Authority List  took 0.02110457420349121s
Interlinking | Calculation of Degree of Connection for  Language Name Authority List  took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for  Language Name Authority List  took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for  Language Name Authority List  took 9.965896606445312e-05s
Interoperability | Check the re-using of existing vocabs for  Language Name Authority List  took 1.9073486328125e-06s
Believability | Calculation of trust value for  Language Name Authority List  took 1.0013580322265625e-05s
INFO | --- Analysis for language-authority-list took 16239.214010715485s
Availability | SPARQL endpoint availability check for Lark took 383.45514822006226s
Availability | VoID file availability check for Lark took 0.0007598400115966797s
Completeness | Calculation of interlinking completeness for Lark took 0.9658036231994629s
Reputation | Calculation of the PageRank for Lark took 0.026000499725341797s
Interlinking | Calculation of Degree of Connection for Lark took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Lark took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Lark took 7.486343383789062e-05s
Believability | Calculation of trust value for Lark took 6.67572021484375e-06s
INFO | --- Analysis for LARK took 1677.5183143615723s
Availability | SPARQL endpoint availability check for LASLA corpus in LiLa took 0.5130395889282227s
Availability | VoID file availability check for LASLA corpus in LiLa took 0.0007767677307128906s
Completeness | Calculation of interlinking completeness for LASLA corpus in LiLa took 0.7056825160980225s
Reputation | Calculation of the PageRank for LASLA corpus in LiLa took 0.020505905151367188s
Interlinking | Calculation of Degree of Connection for LASLA corpus in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LASLA corpus in LiLa took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for LASLA corpus in LiLa took 3.600120544433594e-05s
Believability | Calculation of trust value for LASLA corpus in LiLa took 6.67572021484375e-06s
INFO | --- Analysis for LASLA took 5.339284896850586s
Availability | SPARQL endpoint availability check for LATC Linksets took 4.076957702636719e-05s
Availability | VoID file availability check for LATC Linksets took 0.00022649765014648438s
Completeness | Calculation of interlinking completeness for LATC Linksets took 0.27881288528442383s
Reputation | Calculation of the PageRank for LATC Linksets took 0.021646738052368164s
Interlinking | Calculation of Degree of Connection for LATC Linksets took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for LATC Linksets took 0.0009577274322509766s
Interlinking | Calculation of Clustering coefficient for LATC Linksets took 3.600120544433594e-05s
Believability | Calculation of trust value for LATC Linksets took 7.3909759521484375e-06s
INFO | --- Analysis for latc-linksets took 3.9005231857299805s
Availability | SPARQL endpoint availability check for Latin Vallex 2.0 in LiLa took 0.4623715877532959s
Availability | VoID file availability check for Latin Vallex 2.0 in LiLa took 0.0007498264312744141s
Completeness | Calculation of interlinking completeness for Latin Vallex 2.0 in LiLa took 0.2845463752746582s
Reputation | Calculation of the PageRank for Latin Vallex 2.0 in LiLa took 0.02049541473388672s
Interlinking | Calculation of Degree of Connection for Latin Vallex 2.0 in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Latin Vallex 2.0 in LiLa took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Latin Vallex 2.0 in LiLa took 3.910064697265625e-05s
Believability | Calculation of trust value for Latin Vallex 2.0 in LiLa took 5.4836273193359375e-06s
INFO | --- Analysis for Latin_Vallex2.0 took 4.315296173095703s
Availability | SPARQL endpoint availability check for LatinAffectus in LiLa took 0.4303293228149414s
Availability | VoID file availability check for LatinAffectus in LiLa took 0.0005850791931152344s
Completeness | Calculation of interlinking completeness for LatinAffectus in LiLa took 0.25464606285095215s
Reputation | Calculation of the PageRank for LatinAffectus in LiLa took 0.02169013023376465s
Interlinking | Calculation of Degree of Connection for LatinAffectus in LiLa took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for LatinAffectus in LiLa took 0.0012204647064208984s
Interlinking | Calculation of Clustering coefficient for LatinAffectus in LiLa took 4.8160552978515625e-05s
Believability | Calculation of trust value for LatinAffectus in LiLa took 7.3909759521484375e-06s
INFO | --- Analysis for LatinAffectus took 4.285187721252441s
Availability | SPARQL endpoint availability check for Latin WordNet Revision in LiLa took 0.47754454612731934s
Availability | VoID file availability check for Latin WordNet Revision in LiLa took 0.0006330013275146484s
Completeness | Calculation of interlinking completeness for Latin WordNet Revision in LiLa took 0.2879292964935303s
Reputation | Calculation of the PageRank for Latin WordNet Revision in LiLa took 0.020419836044311523s
Interlinking | Calculation of Degree of Connection for Latin WordNet Revision in LiLa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Latin WordNet Revision in LiLa took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Latin WordNet Revision in LiLa took 3.910064697265625e-05s
Believability | Calculation of trust value for Latin WordNet Revision in LiLa took 8.821487426757812e-06s
INFO | --- Analysis for LatinWordnetLiLa took 4.097126007080078s
Availability | SPARQL endpoint availability check for Leipzig Corpora Collection (LCC) took 4.00543212890625e-05s
Availability | VoID file availability check for Leipzig Corpora Collection (LCC) took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for Leipzig Corpora Collection (LCC) took 1.3407714366912842s
Reputation | Calculation of the PageRank for Leipzig Corpora Collection (LCC) took 0.020419836044311523s
Interlinking | Calculation of Degree of Connection for Leipzig Corpora Collection (LCC) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Leipzig Corpora Collection (LCC) took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Leipzig Corpora Collection (LCC) took 3.075599670410156e-05s
Believability | Calculation of trust value for Leipzig Corpora Collection (LCC) took 5.9604644775390625e-06s
INFO | --- Analysis for lcc took 3.9811718463897705s
Availability | SPARQL endpoint availability check for Library of Congress Subject Headings took 4.1961669921875e-05s
Availability | VoID file availability check for Library of Congress Subject Headings took 0.0006842613220214844s
Completeness | Calculation of interlinking completeness for Library of Congress Subject Headings took 0.2687644958496094s
Reputation | Calculation of the PageRank for Library of Congress Subject Headings took 0.02058100700378418s
Interlinking | Calculation of Degree of Connection for Library of Congress Subject Headings took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Library of Congress Subject Headings took 0.0008378028869628906s
Interlinking | Calculation of Clustering coefficient for Library of Congress Subject Headings took 0.0001270771026611328s
Believability | Calculation of trust value for Library of Congress Subject Headings took 8.58306884765625e-06s
INFO | --- Analysis for lcsh took 6.145859479904175s
Availability | SPARQL endpoint availability check for LCSubjects.org Library of Congress Subject Headings took 4.220008850097656e-05s
Availability | VoID file availability check for LCSubjects.org Library of Congress Subject Headings took 0.0005500316619873047s
Completeness | Calculation of interlinking completeness for LCSubjects.org Library of Congress Subject Headings took 0.278550386428833s
Reputation | Calculation of the PageRank for LCSubjects.org Library of Congress Subject Headings took 0.02038407325744629s
Interlinking | Calculation of Degree of Connection for LCSubjects.org Library of Congress Subject Headings took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LCSubjects.org Library of Congress Subject Headings took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for LCSubjects.org Library of Congress Subject Headings took 8.749961853027344e-05s
Believability | Calculation of trust value for LCSubjects.org Library of Congress Subject Headings took 7.152557373046875e-06s
INFO | --- Analysis for lcsubjects took 2.7958648204803467s
Availability | SPARQL endpoint availability check for LDQM - Accessibility of DBpedia resources took 6.985664367675781e-05s
Availability | VoID file availability check for LDQM - Accessibility of DBpedia resources took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for LDQM - Accessibility of DBpedia resources took 0.27191948890686035s
Reputation | Calculation of the PageRank for LDQM - Accessibility of DBpedia resources took 0.021542787551879883s
Interlinking | Calculation of Degree of Connection for LDQM - Accessibility of DBpedia resources took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for LDQM - Accessibility of DBpedia resources took 0.0008177757263183594s
Interlinking | Calculation of Clustering coefficient for LDQM - Accessibility of DBpedia resources took 3.337860107421875e-05s
Believability | Calculation of trust value for LDQM - Accessibility of DBpedia resources took 7.152557373046875e-06s
INFO | --- Analysis for ldqm-dbpedia-2016 took 3.4084713459014893s
Availability | SPARQL endpoint availability check for Linked Open Data Taiwan @ Library took 7.628387212753296s
Availability | VoID file availability check for Linked Open Data Taiwan @ Library took 0.0006546974182128906s
Completeness | Calculation of interlinking completeness for Linked Open Data Taiwan @ Library took 0.2613489627838135s
Reputation | Calculation of the PageRank for Linked Open Data Taiwan @ Library took 0.020638704299926758s
Interlinking | Calculation of Degree of Connection for Linked Open Data Taiwan @ Library took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Open Data Taiwan @ Library took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Linked Open Data Taiwan @ Library took 4.887580871582031e-05s
Believability | Calculation of trust value for Linked Open Data Taiwan @ Library took 6.67572021484375e-06s
INFO | --- Analysis for ldt@library took 32.29101514816284s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Eng took 5.91278076171875e-05s
Availability | VoID file availability check for Learned Genre Ontology Eng took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Eng took 0.28063535690307617s
Reputation | Calculation of the PageRank for Learned Genre Ontology Eng took 0.02058100700378418s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Eng took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Learned Genre Ontology Eng took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Eng took 3.0040740966796875e-05s
Believability | Calculation of trust value for Learned Genre Ontology Eng took 6.67572021484375e-06s
INFO | --- Analysis for learned-genre-ontology-eng took 2.9331936836242676s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Intl took 3.910064697265625e-05s
Availability | VoID file availability check for Learned Genre Ontology Intl took 0.00022983551025390625s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Intl took 0.24187397956848145s
Reputation | Calculation of the PageRank for Learned Genre Ontology Intl took 0.020432710647583008s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Intl took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Learned Genre Ontology Intl took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Intl took 2.8848648071289062e-05s
Believability | Calculation of trust value for Learned Genre Ontology Intl took 5.7220458984375e-06s
INFO | --- Analysis for learned-genre-ontology-intl took 2.9264097213745117s
Availability | SPARQL endpoint availability check for U ime Legije took 4.172325134277344e-05s
Availability | VoID file availability check for U ime Legije took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for U ime Legije took 0.27971720695495605s
Reputation | Calculation of the PageRank for U ime Legije took 0.020276546478271484s
Interlinking | Calculation of Degree of Connection for U ime Legije took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for U ime Legije took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for U ime Legije took 2.6941299438476562e-05s
Believability | Calculation of trust value for U ime Legije took 6.9141387939453125e-06s
INFO | --- Analysis for LEGIJA_STRANACA took 2.8389172554016113s
Availability | SPARQL endpoint availability check for OpenUpLabs Legislation took 4.0531158447265625e-05s
Availability | VoID file availability check for OpenUpLabs Legislation took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for OpenUpLabs Legislation took 0.26985788345336914s
Reputation | Calculation of the PageRank for OpenUpLabs Legislation took 0.020304203033447266s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Legislation took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OpenUpLabs Legislation took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Legislation took 2.6464462280273438e-05s
Believability | Calculation of trust value for OpenUpLabs Legislation took 7.152557373046875e-06s
INFO | --- Analysis for legislation-openuplabs took 2.9428768157958984s
Availability | SPARQL endpoint availability check for LiLa Lemma Bank took 0.4053525924682617s
Availability | VoID file availability check for LiLa Lemma Bank took 0.0006794929504394531s
Completeness | Calculation of interlinking completeness for LiLa Lemma Bank took 0.27298474311828613s
Reputation | Calculation of the PageRank for LiLa Lemma Bank took 0.022696256637573242s
Interlinking | Calculation of Degree of Connection for LiLa Lemma Bank took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for LiLa Lemma Bank took 0.0011706352233886719s
Interlinking | Calculation of Clustering coefficient for LiLa Lemma Bank took 8.440017700195312e-05s
Believability | Calculation of trust value for LiLa Lemma Bank took 7.3909759521484375e-06s
INFO | --- Analysis for LemmaBank took 4.395222425460815s
Availability | SPARQL endpoint availability check for lemonUby took 4.172325134277344e-05s
Availability | VoID file availability check for lemonUby took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for lemonUby took 0.29482030868530273s
Reputation | Calculation of the PageRank for lemonUby took 0.020291805267333984s
Interlinking | Calculation of Degree of Connection for lemonUby took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for lemonUby took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for lemonUby took 6.29425048828125e-05s
Believability | Calculation of trust value for lemonUby took 6.198883056640625e-06s
INFO | --- Analysis for lemonuby took 3.2398200035095215s
Availability | SPARQL endpoint availability check for LemonWiktionary took 4.1484832763671875e-05s
Availability | VoID file availability check for LemonWiktionary took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for LemonWiktionary took 0.24720549583435059s
Reputation | Calculation of the PageRank for LemonWiktionary took 0.020532608032226562s
Interlinking | Calculation of Degree of Connection for LemonWiktionary took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LemonWiktionary took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for LemonWiktionary took 3.62396240234375e-05s
Believability | Calculation of trust value for LemonWiktionary took 6.198883056640625e-06s
INFO | --- Analysis for lemonwiktionary took 4.228362321853638s
Availability | SPARQL endpoint availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.4393424987792969s
Availability | VoID file availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.0005846023559570312s
Completeness | Calculation of interlinking completeness for Lewis and Short Latin-English Dictionary in LiLa took 0.2720322608947754s
Reputation | Calculation of the PageRank for Lewis and Short Latin-English Dictionary in LiLa took 0.02036261558532715s
Interlinking | Calculation of Degree of Connection for Lewis and Short Latin-English Dictionary in LiLa took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Lewis and Short Latin-English Dictionary in LiLa took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Lewis and Short Latin-English Dictionary in LiLa took 3.552436828613281e-05s
Believability | Calculation of trust value for Lewis and Short Latin-English Dictionary in LiLa took 6.198883056640625e-06s
INFO | --- Analysis for LewisShort took 3.7521674633026123s
Availability | SPARQL endpoint availability check for LEXIN-RDF took 1.0742461681365967s
Availability | VoID file availability check for LEXIN-RDF took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for LEXIN-RDF took 0.2509419918060303s
Reputation | Calculation of the PageRank for LEXIN-RDF took 0.020099401473999023s
Interlinking | Calculation of Degree of Connection for LEXIN-RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LEXIN-RDF took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for LEXIN-RDF took 2.6464462280273438e-05s
Believability | Calculation of trust value for LEXIN-RDF took 6.198883056640625e-06s
INFO | --- Analysis for lexin-rdf took 5.455666542053223s
Availability | SPARQL endpoint availability check for lexinfo took 4.220008850097656e-05s
Availability | VoID file availability check for lexinfo took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for lexinfo took 0.25657129287719727s
Reputation | Calculation of the PageRank for lexinfo took 0.02017498016357422s
Interlinking | Calculation of Degree of Connection for lexinfo took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for lexinfo took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for lexinfo took 8.559226989746094e-05s
Believability | Calculation of trust value for lexinfo took 5.9604644775390625e-06s
INFO | --- Analysis for lexinfo took 2.893348455429077s
Availability | SPARQL endpoint availability check for Lexvo took 4.124641418457031e-05s
Availability | VoID file availability check for Lexvo took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for Lexvo took 0.2600376605987549s
Reputation | Calculation of the PageRank for Lexvo took 0.02021312713623047s
Interlinking | Calculation of Degree of Connection for Lexvo took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Lexvo took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Lexvo took 0.00017213821411132812s
Believability | Calculation of trust value for Lexvo took 5.9604644775390625e-06s
INFO | --- Analysis for lexvo took 3.0726938247680664s
Availability | SPARQL endpoint availability check for Lexvo.org took 5.340576171875e-05s
Availability | VoID file availability check for Lexvo.org took 0.0005648136138916016s
Completeness | Calculation of interlinking completeness for Lexvo.org took 0.27138185501098633s
Reputation | Calculation of the PageRank for Lexvo.org took 0.020284175872802734s
Interlinking | Calculation of Degree of Connection for Lexvo.org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Lexvo.org took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Lexvo.org took 7.224082946777344e-05s
Believability | Calculation of trust value for Lexvo.org took 5.7220458984375e-06s
INFO | --- Analysis for lexvo-org took 2.5260748863220215s
Availability | SPARQL endpoint availability check for LIBRIS took 0.3228912353515625s
Availability | VoID file availability check for LIBRIS took 0.000614166259765625s
Extra | Recovery of all triples for LIBRIS took 17.72527766227722s
Performance | Total latancy measurement for LIBRIS took 0.7005865573883057s
Amount of data | Number of triples check for LIBRIS took 26.0189151763916s
Interoperability | New terms check for LIBRIS took 15.539891004562378s
Versatility | Languages check for LIBRIS took 0.19598102569580078s
Interpretability | Number of blank nodes check for LIBRIS took 300.0308346748352s
Security | Check HTTPS for LIBRIS took 0.3364439010620117s
Interpretability | RDF structures check for LIBRIS took 2.4599757194519043s
Versatility | Serialization formats check for LIBRIS took 0.24625802040100098s
Availability | RDF dump link check for LIBRIS took 0.15004801750183105s
License | MR license check for LIBRIS took 0.27171754837036133s
License | HR license check for LIBRIS took 0.2177896499633789s
Amount of data | Number of property check for LIBRIS took 0.1824808120727539s
Understandability | Number of label check for LIBRIS took 0.48322486877441406s
Understandability | URI regex check for LIBRIS took 0.3187873363494873s
Understandability | Vocabs check for LIBRIS took 0.15041112899780273s
Verifiability | Authors check for LIBRIS took 0.17062664031982422s
Verifiability | Publishers check for LIBRIS took 0.14823150634765625s
Performance | Throughput check for LIBRIS took 10.538164854049683s
Amount of data | Check the number of entities for LIBRIS took 6.651878356933594e-05s
Verifiability | Contribs. check for LIBRIS took 0.15780949592590332s
Interlinking | sameAs chians check for LIBRIS took 0.1607985496520996s
Interlinking | skos check for LIBRIS took 0.2511751651763916s
Interlinking | skos check for LIBRIS took 0.13116240501403809s
Timeliness | dataset update frequency check for LIBRIS took 0.15999746322631836s
Currency | Creation date check for LIBRIS took 0.36240482330322266s
Currency | Modification date check for LIBRIS took 0.64261794090271s
Rep.Conc. | URIs length for LIBRIS took 82.88152813911438s
Interoperability | New vocabularies check for LIBRIS took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for LIBRIS took 0.1767411231994629s
Accuracy | Check Functional Property for LIBRIS took 0.19180989265441895s
Accuracy | Check Inverse Functional Property for LIBRIS took 0.145158052444458s
Accuracy | Check Datatype consistency for LIBRIS took 0.28084683418273926s
Consistency | Disjoint class check for LIBRIS took 0.20900821685791016s
Consistency | Check Misplaced properties for LIBRIS took 61.9949688911438s
Consistency | Misplaced classes for LIBRIS took 1.12318754196167s
Consistency | Check Ontology hijacking for LIBRIS took 6.1035051345825195s
Consistency | Check Invalid usage of undefined classes for LIBRIS took 1.1791105270385742s
Consistency | Check Invalid usage of undefined properties for LIBRIS took 64.08190965652466s
Conciseness | Check Extensional conciseness for LIBRIS took 0.29734182357788086s
Conciseness | Check Intensional conciseness for LIBRIS took 0.410952091217041s
Security | Sign check for LIBRIS took 0.2849442958831787s
Availability | Check URIs Dereferenciability for LIBRIS took 5.992416620254517s
Completeness | Calculation of interlinking completeness for LIBRIS took 1.300933599472046s
Reputation | Calculation of the PageRank for LIBRIS took 0.020334243774414062s
Interlinking | Calculation of Degree of Connection for LIBRIS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LIBRIS took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for LIBRIS took 0.0001506805419921875s
Interoperability | Check the re-using of existing vocabs for LIBRIS took 1.6689300537109375e-06s
Believability | Calculation of trust value for LIBRIS took 7.3909759521484375e-06s
INFO | --- Analysis for libris took 1075.353194475174s
Availability | SPARQL endpoint availability check for Public Library of Veroia took 0.06751465797424316s
Availability | VoID file availability check for Public Library of Veroia took 0.0006849765777587891s
Completeness | Calculation of interlinking completeness for Public Library of Veroia took 0.744725227355957s
Reputation | Calculation of the PageRank for Public Library of Veroia took 0.021040916442871094s
Interlinking | Calculation of Degree of Connection for Public Library of Veroia took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Public Library of Veroia took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Public Library of Veroia took 7.43865966796875e-05s
Believability | Calculation of trust value for Public Library of Veroia took 7.867813110351562e-06s
INFO | --- Analysis for libver took 5.308016300201416s
Availability | SPARQL endpoint availability check for Lichfield District Council - Spending took 0.18008160591125488s
Availability | VoID file availability check for Lichfield District Council - Spending took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for Lichfield District Council - Spending took 0.2569882869720459s
Reputation | Calculation of the PageRank for Lichfield District Council - Spending took 0.02051711082458496s
Interlinking | Calculation of Degree of Connection for Lichfield District Council - Spending took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Lichfield District Council - Spending took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Lichfield District Council - Spending took 8.20159912109375e-05s
Believability | Calculation of trust value for Lichfield District Council - Spending took 4.76837158203125e-06s
INFO | --- Analysis for lichfield-spending took 3.4777560234069824s
Availability | SPARQL endpoint availability check for Linguistic Metadata (LIME) vocabulary took 4.100799560546875e-05s
Availability | VoID file availability check for Linguistic Metadata (LIME) vocabulary took 0.0007336139678955078s
Completeness | Calculation of interlinking completeness for Linguistic Metadata (LIME) vocabulary took 0.6911299228668213s
Reputation | Calculation of the PageRank for Linguistic Metadata (LIME) vocabulary took 0.02058100700378418s
Interlinking | Calculation of Degree of Connection for Linguistic Metadata (LIME) vocabulary took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linguistic Metadata (LIME) vocabulary took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Linguistic Metadata (LIME) vocabulary took 4.267692565917969e-05s
Believability | Calculation of trust value for Linguistic Metadata (LIME) vocabulary took 7.152557373046875e-06s
INFO | --- Analysis for lime took 6.992089509963989s
Availability | SPARQL endpoint availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 7.152557373046875e-05s
Availability | VoID file availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.2629094123840332s
Reputation | Calculation of the PageRank for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.020751237869262695s
Interlinking | Calculation of Degree of Connection for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.00010633468627929688s
Believability | Calculation of trust value for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 7.152557373046875e-06s
INFO | --- Analysis for lingvoj took 4.763566732406616s
Availability | SPARQL endpoint availability check for Linked Crunchbase took 4.315376281738281e-05s
Availability | VoID file availability check for Linked Crunchbase took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for Linked Crunchbase took 0.27781176567077637s
Reputation | Calculation of the PageRank for Linked Crunchbase took 0.020601272583007812s
Interlinking | Calculation of Degree of Connection for Linked Crunchbase took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Crunchbase took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Linked Crunchbase took 8.511543273925781e-05s
Believability | Calculation of trust value for Linked Crunchbase took 6.9141387939453125e-06s
INFO | --- Analysis for linked-crunchbase took 3.281909942626953s
Availability | SPARQL endpoint availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 6.268820524215698s
Availability | VoID file availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0007960796356201172s
Completeness | Calculation of interlinking completeness for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.30339765548706055s
Reputation | Calculation of the PageRank for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.020414113998413086s
Interlinking | Calculation of Degree of Connection for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for LinkedDrugs: Linked Drug Product Data on a Global Scale took 7.390975952148438e-05s
Believability | Calculation of trust value for LinkedDrugs: Linked Drug Product Data on a Global Scale took 7.62939453125e-06s
INFO | --- Analysis for linked-drugs took 21.0143780708313s
Availability | SPARQL endpoint availability check for Linked EDGAR (OntologyCentral) took 4.100799560546875e-05s
Availability | VoID file availability check for Linked EDGAR (OntologyCentral) took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for Linked EDGAR (OntologyCentral) took 0.3249642848968506s
Reputation | Calculation of the PageRank for Linked EDGAR (OntologyCentral) took 0.020346879959106445s
Interlinking | Calculation of Degree of Connection for Linked EDGAR (OntologyCentral) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked EDGAR (OntologyCentral) took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Linked EDGAR (OntologyCentral) took 9.989738464355469e-05s
Believability | Calculation of trust value for Linked EDGAR (OntologyCentral) took 5.0067901611328125e-06s
INFO | --- Analysis for linked-edgar took 5.961050033569336s
Availability | SPARQL endpoint availability check for Linked Eurostat (OntologyCentral) took 4.291534423828125e-05s
Availability | VoID file availability check for Linked Eurostat (OntologyCentral) took 0.0006005764007568359s
Completeness | Calculation of interlinking completeness for Linked Eurostat (OntologyCentral) took 0.31970643997192383s
Reputation | Calculation of the PageRank for Linked Eurostat (OntologyCentral) took 0.020492076873779297s
Interlinking | Calculation of Degree of Connection for Linked Eurostat (OntologyCentral) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Eurostat (OntologyCentral) took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Linked Eurostat (OntologyCentral) took 0.00011181831359863281s
Believability | Calculation of trust value for Linked Eurostat (OntologyCentral) took 7.867813110351562e-06s
INFO | --- Analysis for linked-eurostat took 5.278416633605957s
Availability | SPARQL endpoint availability check for linked hypernyms took 4.1484832763671875e-05s
Availability | VoID file availability check for linked hypernyms took 0.0006718635559082031s
Completeness | Calculation of interlinking completeness for linked hypernyms took 0.6125349998474121s
Reputation | Calculation of the PageRank for linked hypernyms took 0.02046990394592285s
Interlinking | Calculation of Degree of Connection for linked hypernyms took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for linked hypernyms took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for linked hypernyms took 7.486343383789062e-05s
Believability | Calculation of trust value for linked hypernyms took 7.152557373046875e-06s
INFO | --- Analysis for linked-hypernyms took 6.26435923576355s
Availability | SPARQL endpoint availability check for Linked Life Data took 228.01008248329163s
Availability | VoID file availability check for Linked Life Data took 0.0008223056793212891s
Completeness | Calculation of interlinking completeness for Linked Life Data took 0.9100661277770996s
Reputation | Calculation of the PageRank for Linked Life Data took 0.0209808349609375s
Interlinking | Calculation of Degree of Connection for Linked Life Data took 2.574920654296875e-05s
Interlinking | Calculation of Centrality for Linked Life Data took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Linked Life Data took 4.458427429199219e-05s
Believability | Calculation of trust value for Linked Life Data took 7.3909759521484375e-06s
INFO | --- Analysis for linked-life-data took 713.8254697322845s
Availability | SPARQL endpoint availability check for Linked Logainm took 0.24570465087890625s
Availability | VoID file availability check for Linked Logainm took 0.0006425380706787109s
Extra | Recovery of all triples for Linked Logainm took 2.8532662391662598s
Performance | Total latancy measurement for Linked Logainm took 0.5644223690032959s
Amount of data | Number of triples check for Linked Logainm took 0.16158413887023926s
Interoperability | New terms check for Linked Logainm took 1.2875216007232666s
Versatility | Languages check for Linked Logainm took 1.522886037826538s
Interpretability | Number of blank nodes check for Linked Logainm took 0.1344001293182373s
Security | Check HTTPS for Linked Logainm took 0.26951074600219727s
Interpretability | RDF structures check for Linked Logainm took 0.41007089614868164s
Versatility | Serialization formats check for Linked Logainm took 0.15691113471984863s
Availability | RDF dump link check for Linked Logainm took 0.12095761299133301s
License | MR license check for Linked Logainm took 0.12475895881652832s
License | HR license check for Linked Logainm took 0.15646767616271973s
Amount of data | Number of property check for Linked Logainm took 0.1344461441040039s
Understandability | Number of label check for Linked Logainm took 0.1971757411956787s
Understandability | URI regex check for Linked Logainm took 0.2192215919494629s
Understandability | Vocabs check for Linked Logainm took 0.12105870246887207s
Verifiability | Authors check for Linked Logainm took 0.11885929107666016s
Verifiability | Publishers check for Linked Logainm took 0.11269211769104004s
Performance | Throughput check for Linked Logainm took 10.561892747879028s
Amount of data | Check the number of entities for Linked Logainm took 6.890296936035156e-05s
Verifiability | Contribs. check for Linked Logainm took 0.12024569511413574s
Interlinking | sameAs chians check for Linked Logainm took 0.13685083389282227s
Interlinking | skos check for Linked Logainm took 0.15083813667297363s
Interlinking | skos check for Linked Logainm took 0.10529255867004395s
Timeliness | dataset update frequency check for Linked Logainm took 0.12395930290222168s
Currency | Creation date check for Linked Logainm took 0.25290703773498535s
Currency | Modification date check for Linked Logainm took 0.27061963081359863s
Rep.Conc. | URIs length for Linked Logainm took 1.2082726955413818s
Interoperability | New vocabularies check for Linked Logainm took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Linked Logainm took 0.14214706420898438s
Accuracy | Check Functional Property for Linked Logainm took 0.2036747932434082s
Accuracy | Check Inverse Functional Property for Linked Logainm took 0.19493913650512695s
Accuracy | Check Empty annotation labels for Linked Logainm took 0.6243758201599121s
Accuracy | Check White space in annotation for Linked Logainm took 0.024555206298828125s
Accuracy | Check Datatype consistency for Linked Logainm took 0.03050684928894043s
Consistency | Disjoint class check for Linked Logainm took 0.19167113304138184s
Consistency | Check Misplaced properties for Linked Logainm took 0.3377532958984375s
Consistency | Misplaced classes for Linked Logainm took 0.2849721908569336s
Consistency | Check Ontology hijacking for Linked Logainm took 1.8187813758850098s
Consistency | Check Invalid usage of undefined classes for Linked Logainm took 1.1890895366668701s
Consistency | Check Invalid usage of undefined properties for Linked Logainm took 1.3818612098693848s
Conciseness | Check Extensional conciseness for Linked Logainm took 0.033997297286987305s
Conciseness | Check Intensional conciseness for Linked Logainm took 0.19320464134216309s
Security | Sign check for Linked Logainm took 0.11697530746459961s
Availability | Check URIs Dereferenciability for Linked Logainm took 993.0059428215027s
Completeness | Calculation of interlinking completeness for Linked Logainm took 1.2921957969665527s
Reputation | Calculation of the PageRank for Linked Logainm took 0.021344900131225586s
Interlinking | Calculation of Degree of Connection for Linked Logainm took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Linked Logainm took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Linked Logainm took 8.821487426757812e-05s
Interoperability | Check the re-using of existing vocabs for Linked Logainm took 2.1457672119140625e-06s
Believability | Calculation of trust value for Linked Logainm took 6.9141387939453125e-06s
INFO | --- Analysis for linked-logainm took 1050.4130046367645s
Availability | SPARQL endpoint availability check for Linked NUTS took 4.220008850097656e-05s
Availability | VoID file availability check for Linked NUTS took 0.0004711151123046875s
Completeness | Calculation of interlinking completeness for Linked NUTS took 0.6952366828918457s
Reputation | Calculation of the PageRank for Linked NUTS took 0.020262479782104492s
Interlinking | Calculation of Degree of Connection for Linked NUTS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked NUTS took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Linked NUTS took 5.078315734863281e-05s
Believability | Calculation of trust value for Linked NUTS took 5.0067901611328125e-06s
INFO | --- Analysis for linked-nuts took 4.166413068771362s
Availability | SPARQL endpoint availability check for Linked Open Aalto Data Service took 4.100799560546875e-05s
Availability | VoID file availability check for Linked Open Aalto Data Service took 0.0002865791320800781s
Completeness | Calculation of interlinking completeness for Linked Open Aalto Data Service took 0.27030348777770996s
Reputation | Calculation of the PageRank for Linked Open Aalto Data Service took 0.02038097381591797s
Interlinking | Calculation of Degree of Connection for Linked Open Aalto Data Service took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Open Aalto Data Service took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Linked Open Aalto Data Service took 2.9087066650390625e-05s
Believability | Calculation of trust value for Linked Open Aalto Data Service took 7.62939453125e-06s
INFO | --- Analysis for linked-open-aalto-data-service took 4.712991237640381s
Availability | SPARQL endpoint availability check for Linked Open Camera (LinkedOpenData.it) took 2.3957228660583496s
Availability | VoID file availability check for Linked Open Camera (LinkedOpenData.it) took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for Linked Open Camera (LinkedOpenData.it) took 0.2735428810119629s
Reputation | Calculation of the PageRank for Linked Open Camera (LinkedOpenData.it) took 0.02027106285095215s
Interlinking | Calculation of Degree of Connection for Linked Open Camera (LinkedOpenData.it) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Open Camera (LinkedOpenData.it) took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Linked Open Camera (LinkedOpenData.it) took 3.504753112792969e-05s
Believability | Calculation of trust value for Linked Open Camera (LinkedOpenData.it) took 5.245208740234375e-06s
INFO | --- Analysis for linked-open-camera took 5.315622806549072s
Availability | SPARQL endpoint availability check for Linked Open Commerce took 0.6520590782165527s
Availability | VoID file availability check for Linked Open Commerce took 0.0007100105285644531s
Completeness | Calculation of interlinking completeness for Linked Open Commerce took 0.25614309310913086s
Reputation | Calculation of the PageRank for Linked Open Commerce took 0.020335912704467773s
Interlinking | Calculation of Degree of Connection for Linked Open Commerce took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Linked Open Commerce took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for Linked Open Commerce took 3.0279159545898438e-05s
Believability | Calculation of trust value for Linked Open Commerce took 6.67572021484375e-06s
INFO | --- Analysis for linked-open-commerce took 5.005777835845947s
Availability | SPARQL endpoint availability check for Linked Open Data of Ecology took 1.244140386581421s
Availability | VoID file availability check for Linked Open Data of Ecology took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for Linked Open Data of Ecology took 0.26907873153686523s
Reputation | Calculation of the PageRank for Linked Open Data of Ecology took 0.02059197425842285s
Interlinking | Calculation of Degree of Connection for Linked Open Data of Ecology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Open Data of Ecology took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Linked Open Data of Ecology took 0.00010371208190917969s
Believability | Calculation of trust value for Linked Open Data of Ecology took 7.62939453125e-06s
INFO | --- Analysis for linked-open-data-of-ecology took 3.7208054065704346s
Availability | SPARQL endpoint availability check for Linked Open Numbers took 4.0531158447265625e-05s
Availability | VoID file availability check for Linked Open Numbers took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for Linked Open Numbers took 0.26165032386779785s
Reputation | Calculation of the PageRank for Linked Open Numbers took 0.020593643188476562s
Interlinking | Calculation of Degree of Connection for Linked Open Numbers took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Open Numbers took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Linked Open Numbers took 8.821487426757812e-05s
Believability | Calculation of trust value for Linked Open Numbers took 7.3909759521484375e-06s
INFO | --- Analysis for linked-open-numbers took 2.702972412109375s
Availability | SPARQL endpoint availability check for Linked Open Piracy took 5.221366882324219e-05s
Availability | VoID file availability check for Linked Open Piracy took 0.0006566047668457031s
Completeness | Calculation of interlinking completeness for Linked Open Piracy took 0.2930641174316406s
Reputation | Calculation of the PageRank for Linked Open Piracy took 0.020650386810302734s
Interlinking | Calculation of Degree of Connection for Linked Open Piracy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Open Piracy took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Linked Open Piracy took 3.0994415283203125e-05s
Believability | Calculation of trust value for Linked Open Piracy took 5.4836273193359375e-06s
INFO | --- Analysis for linked-open-piracy took 6.299669504165649s
Availability | SPARQL endpoint availability check for Linked Open Senate (linkedopendata.it) took 4.1484832763671875e-05s
Availability | VoID file availability check for Linked Open Senate (linkedopendata.it) took 0.00028443336486816406s
Completeness | Calculation of interlinking completeness for Linked Open Senate (linkedopendata.it) took 0.2698822021484375s
Reputation | Calculation of the PageRank for Linked Open Senate (linkedopendata.it) took 0.027892589569091797s
Interlinking | Calculation of Degree of Connection for Linked Open Senate (linkedopendata.it) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Linked Open Senate (linkedopendata.it) took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Linked Open Senate (linkedopendata.it) took 3.314018249511719e-05s
Believability | Calculation of trust value for Linked Open Senate (linkedopendata.it) took 6.67572021484375e-06s
INFO | --- Analysis for linked-open-senate took 3.063666582107544s
Availability | SPARQL endpoint availability check for Linked Open Vocabularies (LOV) took 0.5848591327667236s
Availability | VoID file availability check for Linked Open Vocabularies (LOV) took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for Linked Open Vocabularies (LOV) took 0.2590336799621582s
Reputation | Calculation of the PageRank for Linked Open Vocabularies (LOV) took 0.020183324813842773s
Interlinking | Calculation of Degree of Connection for Linked Open Vocabularies (LOV) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Open Vocabularies (LOV) took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Linked Open Vocabularies (LOV) took 4.5299530029296875e-05s
Believability | Calculation of trust value for Linked Open Vocabularies (LOV) took 6.67572021484375e-06s
INFO | --- Analysis for linked-open-vocabularies-lov took 4.2429022789001465s
Availability | SPARQL endpoint availability check for Linked Periodicals Database took 4.315376281738281e-05s
Availability | VoID file availability check for Linked Periodicals Database took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for Linked Periodicals Database took 0.2924039363861084s
Reputation | Calculation of the PageRank for Linked Periodicals Database took 0.02027606964111328s
Interlinking | Calculation of Degree of Connection for Linked Periodicals Database took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Linked Periodicals Database took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Linked Periodicals Database took 3.1948089599609375e-05s
Believability | Calculation of trust value for Linked Periodicals Database took 4.76837158203125e-06s
INFO | --- Analysis for linked-periodicals took 2.690412759780884s
Availability | SPARQL endpoint availability check for Linked Index took 4.220008850097656e-05s
Availability | VoID file availability check for Linked Index took 0.00044608116149902344s
Completeness | Calculation of interlinking completeness for Linked Index took 0.2677490711212158s
Reputation | Calculation of the PageRank for Linked Index took 0.020496368408203125s
Interlinking | Calculation of Degree of Connection for Linked Index took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Index took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Linked Index took 8.916854858398438e-05s
Believability | Calculation of trust value for Linked Index took 6.4373016357421875e-06s
INFO | --- Analysis for linked-stockindex took 2.3887827396392822s
Availability | SPARQL endpoint availability check for Linked Structured Product Labels took 5.139650583267212s
Availability | VoID file availability check for Linked Structured Product Labels took 0.0005474090576171875s
Completeness | Calculation of interlinking completeness for Linked Structured Product Labels took 0.2763650417327881s
Reputation | Calculation of the PageRank for Linked Structured Product Labels took 0.020397663116455078s
Interlinking | Calculation of Degree of Connection for Linked Structured Product Labels took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Linked Structured Product Labels took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Linked Structured Product Labels took 3.6716461181640625e-05s
Believability | Calculation of trust value for Linked Structured Product Labels took 6.67572021484375e-06s
INFO | --- Analysis for linked-structured-product-labels took 30.445385932922363s
Availability | SPARQL endpoint availability check for Linked Taiwan Geo-Names took 0.6392130851745605s
Availability | VoID file availability check for Linked Taiwan Geo-Names took 0.0005598068237304688s
Completeness | Calculation of interlinking completeness for Linked Taiwan Geo-Names took 0.27680253982543945s
Reputation | Calculation of the PageRank for Linked Taiwan Geo-Names took 0.0206453800201416s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Geo-Names took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Geo-Names took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Geo-Names took 3.457069396972656e-05s
Believability | Calculation of trust value for Linked Taiwan Geo-Names took 6.67572021484375e-06s
INFO | --- Analysis for linked-taiwan-geo-names took 4.0080506801605225s
Availability | SPARQL endpoint availability check for Linked TCGA took 20.2011137008667s
Availability | VoID file availability check for Linked TCGA took 0.0007412433624267578s
Completeness | Calculation of interlinking completeness for Linked TCGA took 0.674109935760498s
Reputation | Calculation of the PageRank for Linked TCGA took 0.02030467987060547s
Interlinking | Calculation of Degree of Connection for Linked TCGA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked TCGA took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Linked TCGA took 9.989738464355469e-05s
Believability | Calculation of trust value for Linked TCGA took 7.152557373046875e-06s
INFO | --- Analysis for linked-tcga took 63.21116280555725s
Availability | SPARQL endpoint availability check for Linked User Feedback took 0.09865903854370117s
Availability | VoID file availability check for Linked User Feedback took 0.00042700767517089844s
Completeness | Calculation of interlinking completeness for Linked User Feedback took 0.2909393310546875s
Reputation | Calculation of the PageRank for Linked User Feedback took 0.02038431167602539s
Interlinking | Calculation of Degree of Connection for Linked User Feedback took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Linked User Feedback took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Linked User Feedback took 3.8623809814453125e-05s
Believability | Calculation of trust value for Linked User Feedback took 6.9141387939453125e-06s
INFO | --- Analysis for linked-user-feedback took 3.098186731338501s
Availability | SPARQL endpoint availability check for USPTO Patent data took 4.1484832763671875e-05s
Availability | VoID file availability check for USPTO Patent data took 0.0008263587951660156s
Completeness | Calculation of interlinking completeness for USPTO Patent data took 0.2616877555847168s
Reputation | Calculation of the PageRank for USPTO Patent data took 0.020647525787353516s
Interlinking | Calculation of Degree of Connection for USPTO Patent data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for USPTO Patent data took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for USPTO Patent data took 7.748603820800781e-05s
Believability | Calculation of trust value for USPTO Patent data took 7.3909759521484375e-06s
INFO | --- Analysis for linked-uspto-patent-data took 53.870269775390625s
Availability | SPARQL endpoint availability check for Linked Web APIs dataset took 3.9577484130859375e-05s
Availability | VoID file availability check for Linked Web APIs dataset took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for Linked Web APIs dataset took 0.2581143379211426s
Reputation | Calculation of the PageRank for Linked Web APIs dataset took 0.020816564559936523s
Interlinking | Calculation of Degree of Connection for Linked Web APIs dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Web APIs dataset took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Linked Web APIs dataset took 3.0279159545898438e-05s
Believability | Calculation of trust value for Linked Web APIs dataset took 7.62939453125e-06s
INFO | --- Analysis for linked-web-apis took 2.950028896331787s
Availability | SPARQL endpoint availability check for linkedarc.net archaeological datasets took 4.124641418457031e-05s
Availability | VoID file availability check for linkedarc.net archaeological datasets took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for linkedarc.net archaeological datasets took 0.2745068073272705s
Reputation | Calculation of the PageRank for linkedarc.net archaeological datasets took 0.02056741714477539s
Interlinking | Calculation of Degree of Connection for linkedarc.net archaeological datasets took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for linkedarc.net archaeological datasets took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for linkedarc.net archaeological datasets took 3.170967102050781e-05s
Believability | Calculation of trust value for linkedarc.net archaeological datasets took 7.3909759521484375e-06s
INFO | --- Analysis for linkedarc took 3.423466444015503s
Availability | SPARQL endpoint availability check for Linked Crowdsourced Data took 0.07643389701843262s
Availability | VoID file availability check for Linked Crowdsourced Data took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for Linked Crowdsourced Data took 0.2745208740234375s
Reputation | Calculation of the PageRank for Linked Crowdsourced Data took 0.020548582077026367s
Interlinking | Calculation of Degree of Connection for Linked Crowdsourced Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Crowdsourced Data took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Linked Crowdsourced Data took 3.4809112548828125e-05s
Believability | Calculation of trust value for Linked Crowdsourced Data took 6.4373016357421875e-06s
INFO | --- Analysis for linkedcrowdsourceddata took 2.7446765899658203s
Availability | SPARQL endpoint availability check for LinkedCT took 0.6257109642028809s
Availability | VoID file availability check for LinkedCT took 0.000629425048828125s
Completeness | Calculation of interlinking completeness for LinkedCT took 0.28518199920654297s
Reputation | Calculation of the PageRank for LinkedCT took 0.020405292510986328s
Interlinking | Calculation of Degree of Connection for LinkedCT took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LinkedCT took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for LinkedCT took 0.00010037422180175781s
Believability | Calculation of trust value for LinkedCT took 6.4373016357421875e-06s
INFO | --- Analysis for linkedct took 5.397701025009155s
Availability | SPARQL endpoint availability check for LinkedGeoData took 9.673453569412231s
Availability | VoID file availability check for LinkedGeoData took 0.0007054805755615234s
Completeness | Calculation of interlinking completeness for LinkedGeoData took 0.24944448471069336s
Reputation | Calculation of the PageRank for LinkedGeoData took 0.020554065704345703s
Interlinking | Calculation of Degree of Connection for LinkedGeoData took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for LinkedGeoData took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData took 0.00013494491577148438s
Believability | Calculation of trust value for LinkedGeoData took 5.245208740234375e-06s
INFO | --- Analysis for linkedgeodata took 26.228047609329224s
Availability | SPARQL endpoint availability check for LinkedGeoData: Aerodromes took 3.981590270996094e-05s
Availability | VoID file availability check for LinkedGeoData: Aerodromes took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for LinkedGeoData: Aerodromes took 0.27779579162597656s
Reputation | Calculation of the PageRank for LinkedGeoData: Aerodromes took 0.020412683486938477s
Interlinking | Calculation of Degree of Connection for LinkedGeoData: Aerodromes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LinkedGeoData: Aerodromes took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData: Aerodromes took 3.7670135498046875e-05s
Believability | Calculation of trust value for LinkedGeoData: Aerodromes took 5.4836273193359375e-06s
INFO | --- Analysis for linkedgeodata-aerodromes took 2.890141248703003s
Availability | SPARQL endpoint availability check for LinkedLCCN took 0.7758650779724121s
Availability | VoID file availability check for LinkedLCCN took 0.0007011890411376953s
Completeness | Calculation of interlinking completeness for LinkedLCCN took 0.26250362396240234s
Reputation | Calculation of the PageRank for LinkedLCCN took 0.020772218704223633s
Interlinking | Calculation of Degree of Connection for LinkedLCCN took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LinkedLCCN took 0.0008723735809326172s
Interlinking | Calculation of Clustering coefficient for LinkedLCCN took 0.00011301040649414062s
Believability | Calculation of trust value for LinkedLCCN took 7.152557373046875e-06s
INFO | --- Analysis for linkedlccn took 9.313544988632202s
Availability | SPARQL endpoint availability check for LinkedMarkMail took 7.367134094238281e-05s
Availability | VoID file availability check for LinkedMarkMail took 0.00043272972106933594s
Completeness | Calculation of interlinking completeness for LinkedMarkMail took 0.2698502540588379s
Reputation | Calculation of the PageRank for LinkedMarkMail took 0.020763158798217773s
Interlinking | Calculation of Degree of Connection for LinkedMarkMail took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LinkedMarkMail took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for LinkedMarkMail took 3.6716461181640625e-05s
Believability | Calculation of trust value for LinkedMarkMail took 5.9604644775390625e-06s
INFO | --- Analysis for linkedmarkmail took 2.547985792160034s
Availability | SPARQL endpoint availability check for Linked Movie DataBase took 40.62548637390137s
Availability | VoID file availability check for Linked Movie DataBase took 0.0006706714630126953s
Completeness | Calculation of interlinking completeness for Linked Movie DataBase took 0.2837700843811035s
Reputation | Calculation of the PageRank for Linked Movie DataBase took 0.020381689071655273s
Interlinking | Calculation of Degree of Connection for Linked Movie DataBase took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Movie DataBase took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Linked Movie DataBase took 0.00014066696166992188s
Believability | Calculation of trust value for Linked Movie DataBase took 6.9141387939453125e-06s
INFO | --- Analysis for linkedmdb took 133.65392637252808s
Availability | SPARQL endpoint availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 393.0504882335663s
Availability | VoID file availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0006806850433349609s
Completeness | Calculation of interlinking completeness for LinkedSpending: OpenSpending becomes Linked Open Data took 1.3245329856872559s
Reputation | Calculation of the PageRank for LinkedSpending: OpenSpending becomes Linked Open Data took 0.02134108543395996s
Interlinking | Calculation of Degree of Connection for LinkedSpending: OpenSpending becomes Linked Open Data took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for LinkedSpending: OpenSpending becomes Linked Open Data took 8.130073547363281e-05s
Believability | Calculation of trust value for LinkedSpending: OpenSpending becomes Linked Open Data took 7.152557373046875e-06s
INFO | --- Analysis for linkedspending took 1457.0445334911346s
Availability | SPARQL endpoint availability check for LinkedStats took 4.029273986816406e-05s
Availability | VoID file availability check for LinkedStats took 0.00031495094299316406s
Completeness | Calculation of interlinking completeness for LinkedStats took 0.28528428077697754s
Reputation | Calculation of the PageRank for LinkedStats took 0.02229785919189453s
Interlinking | Calculation of Degree of Connection for LinkedStats took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LinkedStats took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for LinkedStats took 3.2901763916015625e-05s
Believability | Calculation of trust value for LinkedStats took 7.867813110351562e-06s
INFO | --- Analysis for linkedstats took 5.720075845718384s
Availability | SPARQL endpoint availability check for LinkedUp Catalogue of Educational Datasets took 4.1484832763671875e-05s
Availability | VoID file availability check for LinkedUp Catalogue of Educational Datasets took 0.00028061866760253906s
Completeness | Calculation of interlinking completeness for LinkedUp Catalogue of Educational Datasets took 0.7298860549926758s
Reputation | Calculation of the PageRank for LinkedUp Catalogue of Educational Datasets took 0.02024078369140625s
Interlinking | Calculation of Degree of Connection for LinkedUp Catalogue of Educational Datasets took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LinkedUp Catalogue of Educational Datasets took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for LinkedUp Catalogue of Educational Datasets took 3.0040740966796875e-05s
Believability | Calculation of trust value for LinkedUp Catalogue of Educational Datasets took 7.152557373046875e-06s
INFO | --- Analysis for linkedup-catalogue-of-educational-datasets took 5.615128040313721s
Availability | SPARQL endpoint availability check for Linking Open Drug Data (LODD) took 4.100799560546875e-05s
Availability | VoID file availability check for Linking Open Drug Data (LODD) took 0.0003032684326171875s
Completeness | Calculation of interlinking completeness for Linking Open Drug Data (LODD) took 0.29053831100463867s
Reputation | Calculation of the PageRank for Linking Open Drug Data (LODD) took 0.021953105926513672s
Interlinking | Calculation of Degree of Connection for Linking Open Drug Data (LODD) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Linking Open Drug Data (LODD) took 0.0009262561798095703s
Interlinking | Calculation of Clustering coefficient for Linking Open Drug Data (LODD) took 3.5762786865234375e-05s
Believability | Calculation of trust value for Linking Open Drug Data (LODD) took 7.3909759521484375e-06s
INFO | --- Analysis for linking-open-drug-data took 3.815274477005005s
Availability | SPARQL endpoint availability check for LinkLion - A Link Repository for the Web of Data took 0.03398466110229492s
Availability | VoID file availability check for LinkLion - A Link Repository for the Web of Data took 0.00022983551025390625s
Completeness | Calculation of interlinking completeness for LinkLion - A Link Repository for the Web of Data took 0.268662691116333s
Reputation | Calculation of the PageRank for LinkLion - A Link Repository for the Web of Data took 0.020125865936279297s
Interlinking | Calculation of Degree of Connection for LinkLion - A Link Repository for the Web of Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LinkLion - A Link Repository for the Web of Data took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for LinkLion - A Link Repository for the Web of Data took 0.00010704994201660156s
Believability | Calculation of trust value for LinkLion - A Link Repository for the Web of Data took 7.62939453125e-06s
INFO | --- Analysis for linklion took 2.385054588317871s
Availability | SPARQL endpoint availability check for Lion's Den took 3.933906555175781e-05s
Availability | VoID file availability check for Lion's Den took 0.0003142356872558594s
Completeness | Calculation of interlinking completeness for Lion's Den took 0.27318572998046875s
Reputation | Calculation of the PageRank for Lion's Den took 0.020621299743652344s
Interlinking | Calculation of Degree of Connection for Lion's Den took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Lion's Den took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Lion's Den took 3.314018249511719e-05s
Believability | Calculation of trust value for Lion's Den took 7.3909759521484375e-06s
INFO | --- Analysis for lionsden took 3.4564507007598877s
Availability | SPARQL endpoint availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 47.4592227935791s
Availability | VoID file availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0006210803985595703s
Completeness | Calculation of interlinking completeness for Lista de  Encabezamientos de Materia as Linked Open Data took 1.1723864078521729s
Reputation | Calculation of the PageRank for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0204007625579834s
Interlinking | Calculation of Degree of Connection for Lista de  Encabezamientos de Materia as Linked Open Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Lista de  Encabezamientos de Materia as Linked Open Data took 5.8650970458984375e-05s
Believability | Calculation of trust value for Lista de  Encabezamientos de Materia as Linked Open Data took 7.152557373046875e-06s
INFO | --- Analysis for lista-encabezamientos-materia took 56.53296422958374s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data took 4.00543212890625e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data took 0.25353288650512695s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data took 0.020404338836669922s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data took 3.0040740966796875e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data took 5.9604644775390625e-06s
INFO | --- Analysis for livtdm took 3.7061564922332764s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data 2017 took 3.910064697265625e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data 2017 took 0.00022673606872558594s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data 2017 took 0.26931166648864746s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data 2017 took 0.020226240158081055s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data 2017 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data 2017 took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data 2017 took 2.7418136596679688e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data 2017 took 5.9604644775390625e-06s
INFO | --- Analysis for livtdm2017 took 2.9386425018310547s
Availability | SPARQL endpoint availability check for Linked Open Biomedical Investigations took 3.981590270996094e-05s
Availability | VoID file availability check for Linked Open Biomedical Investigations took 0.0002295970916748047s
Completeness | Calculation of interlinking completeness for Linked Open Biomedical Investigations took 0.26134300231933594s
Reputation | Calculation of the PageRank for Linked Open Biomedical Investigations took 0.020359039306640625s
Interlinking | Calculation of Degree of Connection for Linked Open Biomedical Investigations took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Open Biomedical Investigations took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Linked Open Biomedical Investigations took 2.9087066650390625e-05s
Believability | Calculation of trust value for Linked Open Biomedical Investigations took 5.9604644775390625e-06s
INFO | --- Analysis for lobi took 2.9667747020721436s
Availability | SPARQL endpoint availability check for lobid-organisations took 1.1759262084960938s
Availability | VoID file availability check for lobid-organisations took 0.0005447864532470703s
Completeness | Calculation of interlinking completeness for lobid-organisations took 0.29518866539001465s
Reputation | Calculation of the PageRank for lobid-organisations took 0.020229578018188477s
Interlinking | Calculation of Degree of Connection for lobid-organisations took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for lobid-organisations took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for lobid-organisations took 9.34600830078125e-05s
Believability | Calculation of trust value for lobid-organisations took 7.152557373046875e-06s
INFO | --- Analysis for lobid-organisations took 6.580710172653198s
Availability | SPARQL endpoint availability check for lobid-Bibliographic Resources took 0.8720242977142334s
Availability | VoID file availability check for lobid-Bibliographic Resources took 0.0011963844299316406s
Completeness | Calculation of interlinking completeness for lobid-Bibliographic Resources took 0.2654147148132324s
Reputation | Calculation of the PageRank for lobid-Bibliographic Resources took 0.020060062408447266s
Interlinking | Calculation of Degree of Connection for lobid-Bibliographic Resources took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for lobid-Bibliographic Resources took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for lobid-Bibliographic Resources took 0.00010633468627929688s
Believability | Calculation of trust value for lobid-Bibliographic Resources took 6.9141387939453125e-06s
INFO | --- Analysis for lobid-resources took 8.457540512084961s
Availability | SPARQL endpoint availability check for Linked Open Colors took 4.601478576660156e-05s
Availability | VoID file availability check for Linked Open Colors took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for Linked Open Colors took 0.26502490043640137s
Reputation | Calculation of the PageRank for Linked Open Colors took 0.020382165908813477s
Interlinking | Calculation of Degree of Connection for Linked Open Colors took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Open Colors took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Linked Open Colors took 7.128715515136719e-05s
Believability | Calculation of trust value for Linked Open Colors took 6.9141387939453125e-06s
INFO | --- Analysis for loc took 7.303920745849609s
Availability | SPARQL endpoint availability check for Location Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Location Ontology took 0.000652313232421875s
Completeness | Calculation of interlinking completeness for Location Ontology took 0.2608065605163574s
Reputation | Calculation of the PageRank for Location Ontology took 0.02034282684326172s
Interlinking | Calculation of Degree of Connection for Location Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Location Ontology took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Location Ontology took 2.8371810913085938e-05s
Believability | Calculation of trust value for Location Ontology took 7.62939453125e-06s
INFO | --- Analysis for Location_Ontology took 3.5538265705108643s
Availability | SPARQL endpoint availability check for Linked Open Computer Vision took 4.315376281738281e-05s
Availability | VoID file availability check for Linked Open Computer Vision took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for Linked Open Computer Vision took 0.2794811725616455s
Reputation | Calculation of the PageRank for Linked Open Computer Vision took 0.020341873168945312s
Interlinking | Calculation of Degree of Connection for Linked Open Computer Vision took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Linked Open Computer Vision took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for Linked Open Computer Vision took 3.123283386230469e-05s
Believability | Calculation of trust value for Linked Open Computer Vision took 5.9604644775390625e-06s
INFO | --- Analysis for locv took 32.730117082595825s
Availability | SPARQL endpoint availability check for LOD-a-lot took 0.771517276763916s
Availability | VoID file availability check for LOD-a-lot took 0.0007636547088623047s
Completeness | Calculation of interlinking completeness for LOD-a-lot took 0.27737951278686523s
Reputation | Calculation of the PageRank for LOD-a-lot took 0.02025890350341797s
Interlinking | Calculation of Degree of Connection for LOD-a-lot took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LOD-a-lot took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for LOD-a-lot took 2.86102294921875e-05s
Believability | Calculation of trust value for LOD-a-lot took 7.3909759521484375e-06s
INFO | --- Analysis for lod-a-lot took 14.46013855934143s
Availability | SPARQL endpoint availability check for Scuole Italiane (linkedopendata.it) took 4.100799560546875e-05s
Availability | VoID file availability check for Scuole Italiane (linkedopendata.it) took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for Scuole Italiane (linkedopendata.it) took 0.7091982364654541s
Reputation | Calculation of the PageRank for Scuole Italiane (linkedopendata.it) took 0.02056717872619629s
Interlinking | Calculation of Degree of Connection for Scuole Italiane (linkedopendata.it) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Scuole Italiane (linkedopendata.it) took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Scuole Italiane (linkedopendata.it) took 3.552436828613281e-05s
Believability | Calculation of trust value for Scuole Italiane (linkedopendata.it) took 7.3909759521484375e-06s
INFO | --- Analysis for lod-it_scuole-italiane took 3.3813791275024414s
Availability | SPARQL endpoint availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 3.9577484130859375e-05s
Availability | VoID file availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.29892635345458984s
Reputation | Calculation of the PageRank for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.020569801330566406s
Interlinking | Calculation of Degree of Connection for Open Data Web - a CKAN based linked open data repository in Taiwan took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0007765293121337891s
Interlinking | Calculation of Clustering coefficient for Open Data Web - a CKAN based linked open data repository in Taiwan took 2.9802322387695312e-05s
Believability | Calculation of trust value for Open Data Web - a CKAN based linked open data repository in Taiwan took 6.67572021484375e-06s
INFO | --- Analysis for lod-taiwan took 2.9917972087860107s
Availability | SPARQL endpoint availability check for LOD2 Project Wiki took 4.458427429199219e-05s
Availability | VoID file availability check for LOD2 Project Wiki took 0.00047397613525390625s
Completeness | Calculation of interlinking completeness for LOD2 Project Wiki took 0.29015159606933594s
Reputation | Calculation of the PageRank for LOD2 Project Wiki took 0.020646095275878906s
Interlinking | Calculation of Degree of Connection for LOD2 Project Wiki took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LOD2 Project Wiki took 0.0007903575897216797s
Interlinking | Calculation of Clustering coefficient for LOD2 Project Wiki took 9.417533874511719e-05s
Believability | Calculation of trust value for LOD2 Project Wiki took 6.67572021484375e-06s
INFO | --- Analysis for lod2-project-wiki took 2.861501693725586s
Availability | SPARQL endpoint availability check for LODAC BDLS took 3.062675952911377s
Availability | VoID file availability check for LODAC BDLS took 0.0006225109100341797s
Completeness | Calculation of interlinking completeness for LODAC BDLS took 0.30310750007629395s
Reputation | Calculation of the PageRank for LODAC BDLS took 0.02036142349243164s
Interlinking | Calculation of Degree of Connection for LODAC BDLS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LODAC BDLS took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for LODAC BDLS took 7.05718994140625e-05s
Believability | Calculation of trust value for LODAC BDLS took 8.106231689453125e-06s
INFO | --- Analysis for lodac-bdls took 14.19499397277832s
Availability | SPARQL endpoint availability check for LODRussia Math took 3.933906555175781e-05s
Availability | VoID file availability check for LODRussia Math took 0.00028634071350097656s
Completeness | Calculation of interlinking completeness for LODRussia Math took 0.2689948081970215s
Reputation | Calculation of the PageRank for LODRussia Math took 0.0203859806060791s
Interlinking | Calculation of Degree of Connection for LODRussia Math took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LODRussia Math took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for LODRussia Math took 2.8133392333984375e-05s
Believability | Calculation of trust value for LODRussia Math took 7.152557373046875e-06s
INFO | --- Analysis for lodrussia-math took 2.858787775039673s
Availability | SPARQL endpoint availability check for LODRussia Nano took 5.0067901611328125e-05s
Availability | VoID file availability check for LODRussia Nano took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for LODRussia Nano took 0.28870105743408203s
Reputation | Calculation of the PageRank for LODRussia Nano took 0.02019667625427246s
Interlinking | Calculation of Degree of Connection for LODRussia Nano took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LODRussia Nano took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for LODRussia Nano took 2.7418136596679688e-05s
Believability | Calculation of trust value for LODRussia Nano took 5.7220458984375e-06s
INFO | --- Analysis for lodrussia-nano took 2.9457967281341553s
Availability | SPARQL endpoint availability check for LODStats took 4.029273986816406e-05s
Availability | VoID file availability check for LODStats took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for LODStats took 0.28078556060791016s
Reputation | Calculation of the PageRank for LODStats took 0.020278215408325195s
Interlinking | Calculation of Degree of Connection for LODStats took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LODStats took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for LODStats took 2.765655517578125e-05s
Believability | Calculation of trust value for LODStats took 5.4836273193359375e-06s
INFO | --- Analysis for lodstats took 2.9320218563079834s
Availability | SPARQL endpoint availability check for LODUM took 4.38690185546875e-05s
Availability | VoID file availability check for LODUM took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for LODUM took 0.260556697845459s
Reputation | Calculation of the PageRank for LODUM took 0.020426034927368164s
Interlinking | Calculation of Degree of Connection for LODUM took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LODUM took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for LODUM took 2.9802322387695312e-05s
Believability | Calculation of trust value for LODUM took 6.198883056640625e-06s
INFO | --- Analysis for lodum took 2.906046152114868s
Availability | SPARQL endpoint availability check for lofd took 0.1305854320526123s
Availability | VoID file availability check for lofd took 0.00023651123046875s
Completeness | Calculation of interlinking completeness for lofd took 0.2770519256591797s
Reputation | Calculation of the PageRank for lofd took 0.020204544067382812s
Interlinking | Calculation of Degree of Connection for lofd took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for lofd took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for lofd took 2.8371810913085938e-05s
Believability | Calculation of trust value for lofd took 5.9604644775390625e-06s
INFO | --- Analysis for lofd took 2.497171401977539s
Availability | SPARQL endpoint availability check for Linking Italian University Statistics Project took 270.9994351863861s
Availability | VoID file availability check for Linking Italian University Statistics Project took 0.0009543895721435547s
Completeness | Calculation of interlinking completeness for Linking Italian University Statistics Project took 0.30782485008239746s
Reputation | Calculation of the PageRank for Linking Italian University Statistics Project took 0.020832538604736328s
Interlinking | Calculation of Degree of Connection for Linking Italian University Statistics Project took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Linking Italian University Statistics Project took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Linking Italian University Statistics Project took 6.4849853515625e-05s
Believability | Calculation of trust value for Linking Italian University Statistics Project took 4.76837158203125e-06s
INFO | --- Analysis for loius took 585.0080573558807s
Availability | SPARQL endpoint availability check for LOIUS project - Linking Italian University Statistics took 4.0531158447265625e-05s
Availability | VoID file availability check for LOIUS project - Linking Italian University Statistics took 0.00023245811462402344s
Completeness | Calculation of interlinking completeness for LOIUS project - Linking Italian University Statistics took 0.7591836452484131s
Reputation | Calculation of the PageRank for LOIUS project - Linking Italian University Statistics took 0.0206148624420166s
Interlinking | Calculation of Degree of Connection for LOIUS project - Linking Italian University Statistics took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for LOIUS project - Linking Italian University Statistics took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for LOIUS project - Linking Italian University Statistics took 2.956390380859375e-05s
Believability | Calculation of trust value for LOIUS project - Linking Italian University Statistics took 6.67572021484375e-06s
INFO | --- Analysis for loius-linking-italian-university-statistics took 8.726805925369263s
Availability | SPARQL endpoint availability check for The London Gazette - Gazettes Data took 1.8656928539276123s
Availability | VoID file availability check for The London Gazette - Gazettes Data took 0.0005590915679931641s
Completeness | Calculation of interlinking completeness for The London Gazette - Gazettes Data took 0.328249454498291s
Reputation | Calculation of the PageRank for The London Gazette - Gazettes Data took 0.02059483528137207s
Interlinking | Calculation of Degree of Connection for The London Gazette - Gazettes Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for The London Gazette - Gazettes Data took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for The London Gazette - Gazettes Data took 5.602836608886719e-05s
Believability | Calculation of trust value for The London Gazette - Gazettes Data took 5.9604644775390625e-06s
INFO | --- Analysis for london-gazette took 10.44440484046936s
Availability | SPARQL endpoint availability check for Weather Stations took 4.1484832763671875e-05s
Availability | VoID file availability check for Weather Stations took 0.0005917549133300781s
Completeness | Calculation of interlinking completeness for Weather Stations took 0.3085172176361084s
Reputation | Calculation of the PageRank for Weather Stations took 0.020314931869506836s
Interlinking | Calculation of Degree of Connection for Weather Stations took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Weather Stations took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Weather Stations took 8.0108642578125e-05s
Believability | Calculation of trust value for Weather Stations took 5.9604644775390625e-06s
INFO | --- Analysis for los_metar took 13.381036520004272s
Availability | SPARQL endpoint availability check for Lotico took 0.9281513690948486s
Availability | VoID file availability check for Lotico took 0.0005819797515869141s
Completeness | Calculation of interlinking completeness for Lotico took 0.2790248394012451s
Reputation | Calculation of the PageRank for Lotico took 0.020226240158081055s
Interlinking | Calculation of Degree of Connection for Lotico took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Lotico took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Lotico took 7.867813110351562e-05s
Believability | Calculation of trust value for Lotico took 5.9604644775390625e-06s
INFO | --- Analysis for lotico took 7.951766729354858s
Availability | SPARQL endpoint availability check for Lower Layer Super Output Areas took 0.32581067085266113s
Availability | VoID file availability check for Lower Layer Super Output Areas took 0.0005588531494140625s
Completeness | Calculation of interlinking completeness for Lower Layer Super Output Areas took 0.9225578308105469s
Reputation | Calculation of the PageRank for Lower Layer Super Output Areas took 0.020606279373168945s
Interlinking | Calculation of Degree of Connection for Lower Layer Super Output Areas took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Lower Layer Super Output Areas took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Lower Layer Super Output Areas took 2.956390380859375e-05s
Believability | Calculation of trust value for Lower Layer Super Output Areas took 5.9604644775390625e-06s
INFO | --- Analysis for lower-layer-super-output-areas took 6.013205528259277s
Availability | SPARQL endpoint availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.6061460971832275s
Availability | VoID file availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0002636909484863281s
Extra | Recovery of all triples for Polish Land Parcel Information System (LPIS) dataset @PSNC took 110.65122246742249s
Performance | Total latancy measurement for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.9756395816802979s
Amount of data | Number of triples check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.999727725982666s
Interoperability | New terms check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 15.058490514755249s
Versatility | Languages check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.17895674705505s
Interpretability | Number of blank nodes check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 3.134023427963257s
Interpretability | RDF structures check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2431023120880127s
Versatility | Serialization formats check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 10.019949674606323s
Availability | RDF dump link check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2947664260864258s
License | MR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5339441299438477s
License | HR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.2510631084442s
Amount of data | Number of property check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.43795347213745117s
Understandability | Number of label check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.9502577781677246s
Understandability | URI regex check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.8221211433410645s
Understandability | Vocabs check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.4356503486633301s
Verifiability | Authors check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.22214460372924805s
Verifiability | Publishers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.24686384201049805s
Performance | Throughput check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 10.951558828353882s
Amount of data | Check the number of entities for Polish Land Parcel Information System (LPIS) dataset @PSNC took 7.390975952148438e-05s
Verifiability | Contribs. check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.1916368007659912s
Interlinking | sameAs chians check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.21329259872436523s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.46758508682250977s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.4666173458099365s
Timeliness | dataset update frequency check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 5.574466228485107s
Currency | Creation date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.470736026763916s
Currency | Modification date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2258291244506836s
Rep.Conc. | URIs length for Polish Land Parcel Information System (LPIS) dataset @PSNC took 148.89923238754272s
Interoperability | New vocabularies check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.20104455947875977s
Accuracy | Check Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.3199598789215088s
Accuracy | Check Inverse Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.31685495376586914s
Accuracy | Check Empty annotation labels for Polish Land Parcel Information System (LPIS) dataset @PSNC took 38.57727241516113s
Accuracy | Check White space in annotation for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.688011884689331s
Accuracy | Check Datatype consistency for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.6123039722442627s
Consistency | Disjoint class check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2080674171447754s
Consistency | Check Misplaced properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 86.4940767288208s
Consistency | Misplaced classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.532055377960205s
Consistency | Check Ontology hijacking for Polish Land Parcel Information System (LPIS) dataset @PSNC took 32.67007899284363s
Consistency | Check Invalid usage of undefined classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.2887511253356934s
Consistency | Check Invalid usage of undefined properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 86.96641039848328s
Conciseness | Check Extensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.7044506072998047s
Conciseness | Check Intensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.6038541793823242s
Security | Sign check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.8508996963500977s
Availability | Check URIs Dereferenciability for Polish Land Parcel Information System (LPIS) dataset @PSNC took 6.111999034881592s
Completeness | Calculation of interlinking completeness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.299530029296875s
Reputation | Calculation of the PageRank for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.020908355712890625s
Interlinking | Calculation of Degree of Connection for Polish Land Parcel Information System (LPIS) dataset @PSNC took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Polish Land Parcel Information System (LPIS) dataset @PSNC took 4.458427429199219e-05s
Interoperability | Check the re-using of existing vocabs for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Polish Land Parcel Information System (LPIS) dataset @PSNC took 6.9141387939453125e-06s
INFO | --- Analysis for LPIS_(Poland) took 2300.9593074321747s
Availability | SPARQL endpoint availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.20046377182006836s
Availability | VoID file availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0002551078796386719s
Extra | Recovery of all triples for Land parcel dataset (LPIS) from Czech Republic @PSNC took 116.29255509376526s
Performance | Total latancy measurement for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.0394997596740723s
Amount of data | Number of triples check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 9.432094097137451s
Interoperability | New terms check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 13.489124774932861s
Versatility | Languages check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.2221682071686s
Interpretability | Number of blank nodes check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 3.151352882385254s
Interpretability | RDF structures check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2984344959259033s
Versatility | Serialization formats check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 12.118839263916016s
Availability | RDF dump link check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.3295614719390869s
License | MR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.663217306137085s
License | HR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.14835596084595s
Amount of data | Number of property check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2739236354827881s
Understandability | Number of label check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.9104628562927246s
Understandability | URI regex check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.8590812683105469s
Understandability | Vocabs check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.44847702980041504s
Verifiability | Authors check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.22558140754699707s
Verifiability | Publishers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2766239643096924s
Performance | Throughput check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 11.314063549041748s
Amount of data | Check the number of entities for Land parcel dataset (LPIS) from Czech Republic @PSNC took 7.796287536621094e-05s
Verifiability | Contribs. check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.20253658294677734s
Interlinking | sameAs chians check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.18265080451965332s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.4843871593475342s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.4243175983428955s
Timeliness | dataset update frequency check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 5.846649885177612s
Currency | Creation date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.5266788005828857s
Currency | Modification date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2509622573852539s
Rep.Conc. | URIs length for Land parcel dataset (LPIS) from Czech Republic @PSNC took 172.6378996372223s
Interoperability | New vocabularies check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.1682510375976562e-05s
Consistency | Deprecated classes/propertiers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2002420425415039s
Accuracy | Check Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.33356285095214844s
Accuracy | Check Inverse Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.3265073299407959s
Accuracy | Check Empty annotation labels for Land parcel dataset (LPIS) from Czech Republic @PSNC took 43.56935501098633s
Accuracy | Check White space in annotation for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.7161190509796143s
Accuracy | Check Datatype consistency for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.749357223510742s
Consistency | Disjoint class check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19668221473693848s
Consistency | Check Misplaced properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 93.53148007392883s
Consistency | Misplaced classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.674098253250122s
Consistency | Check Ontology hijacking for Land parcel dataset (LPIS) from Czech Republic @PSNC took 34.50674080848694s
Consistency | Check Invalid usage of undefined classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.2215876579284668s
Consistency | Check Invalid usage of undefined properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 93.67316627502441s
Conciseness | Check Extensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.7686452865600586s
Conciseness | Check Intensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.5185754299163818s
Security | Sign check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2228410243988037s
Availability | Check URIs Dereferenciability for Land parcel dataset (LPIS) from Czech Republic @PSNC took 5.202669620513916s
Completeness | Calculation of interlinking completeness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.937629222869873s
Reputation | Calculation of the PageRank for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.02083110809326172s
Interlinking | Calculation of Degree of Connection for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Land parcel dataset (LPIS) from Czech Republic @PSNC took 4.649162292480469e-05s
Interoperability | Check the re-using of existing vocabs for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Land parcel dataset (LPIS) from Czech Republic @PSNC took 7.867813110351562e-06s
INFO | --- Analysis for LPIS_Czech_Republic took 2309.7927026748657s
Availability | SPARQL endpoint availability check for A collection of Authors for LREC2014 and related Workshops took 4.3392181396484375e-05s
Availability | VoID file availability check for A collection of Authors for LREC2014 and related Workshops took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for A collection of Authors for LREC2014 and related Workshops took 0.691342830657959s
Reputation | Calculation of the PageRank for A collection of Authors for LREC2014 and related Workshops took 0.02053666114807129s
Interlinking | Calculation of Degree of Connection for A collection of Authors for LREC2014 and related Workshops took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for A collection of Authors for LREC2014 and related Workshops took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for A collection of Authors for LREC2014 and related Workshops took 3.0040740966796875e-05s
Believability | Calculation of trust value for A collection of Authors for LREC2014 and related Workshops took 5.245208740234375e-06s
INFO | --- Analysis for lremap-auth took 4.797463893890381s
Availability | SPARQL endpoint availability check for LREC2014 and related Workshops took 7.605552673339844e-05s
Availability | VoID file availability check for LREC2014 and related Workshops took 0.0005578994750976562s
Completeness | Calculation of interlinking completeness for LREC2014 and related Workshops took 0.2738611698150635s
Reputation | Calculation of the PageRank for LREC2014 and related Workshops took 0.020468473434448242s
Interlinking | Calculation of Degree of Connection for LREC2014 and related Workshops took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LREC2014 and related Workshops took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for LREC2014 and related Workshops took 3.075599670410156e-05s
Believability | Calculation of trust value for LREC2014 and related Workshops took 6.9141387939453125e-06s
INFO | --- Analysis for lremap-conf took 4.331515312194824s
Availability | SPARQL endpoint availability check for First not-normalized set of language resources from LREC2014 took 4.076957702636719e-05s
Availability | VoID file availability check for First not-normalized set of language resources from LREC2014 took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for First not-normalized set of language resources from LREC2014 took 0.2577948570251465s
Reputation | Calculation of the PageRank for First not-normalized set of language resources from LREC2014 took 0.020397424697875977s
Interlinking | Calculation of Degree of Connection for First not-normalized set of language resources from LREC2014 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for First not-normalized set of language resources from LREC2014 took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for First not-normalized set of language resources from LREC2014 took 3.075599670410156e-05s
Believability | Calculation of trust value for First not-normalized set of language resources from LREC2014 took 7.152557373046875e-06s
INFO | --- Analysis for lremap-ri took 3.467254161834717s
Availability | SPARQL endpoint availability check for A collection of Submissions for LREC2014 and related Workshops took 4.1484832763671875e-05s
Availability | VoID file availability check for A collection of Submissions for LREC2014 and related Workshops took 0.0005469322204589844s
Completeness | Calculation of interlinking completeness for A collection of Submissions for LREC2014 and related Workshops took 0.29422688484191895s
Reputation | Calculation of the PageRank for A collection of Submissions for LREC2014 and related Workshops took 0.02060532569885254s
Interlinking | Calculation of Degree of Connection for A collection of Submissions for LREC2014 and related Workshops took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for A collection of Submissions for LREC2014 and related Workshops took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for A collection of Submissions for LREC2014 and related Workshops took 4.410743713378906e-05s
Believability | Calculation of trust value for A collection of Submissions for LREC2014 and related Workshops took 3.0517578125e-05s
INFO | --- Analysis for lremap-sub took 3.9943439960479736s
Availability | SPARQL endpoint availability check for LSQ took 4.410743713378906e-05s
Availability | VoID file availability check for LSQ took 0.0006747245788574219s
Completeness | Calculation of interlinking completeness for LSQ took 0.28424668312072754s
Reputation | Calculation of the PageRank for LSQ took 0.020370960235595703s
Interlinking | Calculation of Degree of Connection for LSQ took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for LSQ took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for LSQ took 2.86102294921875e-05s
Believability | Calculation of trust value for LSQ took 7.62939453125e-06s
INFO | --- Analysis for lsq took 3.9605956077575684s
Availability | SPARQL endpoint availability check for Lucani Pharsalia in LiLa took 0.5316922664642334s
Availability | VoID file availability check for Lucani Pharsalia in LiLa took 0.000659942626953125s
Completeness | Calculation of interlinking completeness for Lucani Pharsalia in LiLa took 0.2613403797149658s
Reputation | Calculation of the PageRank for Lucani Pharsalia in LiLa took 0.020342111587524414s
Interlinking | Calculation of Degree of Connection for Lucani Pharsalia in LiLa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Lucani Pharsalia in LiLa took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Lucani Pharsalia in LiLa took 3.5762786865234375e-05s
Believability | Calculation of trust value for Lucani Pharsalia in LiLa took 6.9141387939453125e-06s
INFO | --- Analysis for LucaniPharsalia took 4.053019285202026s
Availability | SPARQL endpoint availability check for Linked rules took 4.172325134277344e-05s
Availability | VoID file availability check for Linked rules took 0.00037598609924316406s
Completeness | Calculation of interlinking completeness for Linked rules took 0.2851567268371582s
Reputation | Calculation of the PageRank for Linked rules took 0.020663738250732422s
Interlinking | Calculation of Degree of Connection for Linked rules took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked rules took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Linked rules took 3.123283386230469e-05s
Believability | Calculation of trust value for Linked rules took 6.9141387939453125e-06s
INFO | --- Analysis for Luminaires_senlis took 2.4651567935943604s
Availability | SPARQL endpoint availability check for Měnové kurzy vzhledem k EUR took 4.1484832763671875e-05s
Availability | VoID file availability check for Měnové kurzy vzhledem k EUR took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for Měnové kurzy vzhledem k EUR took 0.26879048347473145s
Reputation | Calculation of the PageRank for Měnové kurzy vzhledem k EUR took 0.020350217819213867s
Interlinking | Calculation of Degree of Connection for Měnové kurzy vzhledem k EUR took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Měnové kurzy vzhledem k EUR took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Měnové kurzy vzhledem k EUR took 2.9802322387695312e-05s
Believability | Calculation of trust value for Měnové kurzy vzhledem k EUR took 6.4373016357421875e-06s
INFO | --- Analysis for m-nov--kurzy-vzhledem-k-eur took 3.0044546127319336s
Availability | SPARQL endpoint availability check for Microsoft Academic Knowledge Graph took 30.113460063934326s
Availability | VoID file availability check for Microsoft Academic Knowledge Graph took 0.0006330013275146484s
Completeness | Calculation of interlinking completeness for Microsoft Academic Knowledge Graph took 0.7066540718078613s
Reputation | Calculation of the PageRank for Microsoft Academic Knowledge Graph took 0.020206689834594727s
Interlinking | Calculation of Degree of Connection for Microsoft Academic Knowledge Graph took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Microsoft Academic Knowledge Graph took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Microsoft Academic Knowledge Graph took 2.9802322387695312e-05s
Believability | Calculation of trust value for Microsoft Academic Knowledge Graph took 6.9141387939453125e-06s
INFO | --- Analysis for makg took 64.53072762489319s
Availability | SPARQL endpoint availability check for Manchester University Reading Lists took 4.1484832763671875e-05s
Availability | VoID file availability check for Manchester University Reading Lists took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for Manchester University Reading Lists took 0.28658390045166016s
Reputation | Calculation of the PageRank for Manchester University Reading Lists took 0.020418882369995117s
Interlinking | Calculation of Degree of Connection for Manchester University Reading Lists took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Manchester University Reading Lists took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Manchester University Reading Lists took 3.600120544433594e-05s
Believability | Calculation of trust value for Manchester University Reading Lists took 8.821487426757812e-06s
INFO | --- Analysis for manchester-university-reading-lists took 4.342363357543945s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 4.315376281738281e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.25855350494384766s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.020618915557861328s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 4.1484832763671875e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 3.0994415283203125e-05s
Believability | Calculation of trust value for engineering equipment ontology took 6.4373016357421875e-06s
INFO | --- Analysis for manish took 2.3957457542419434s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá, Distrito Capital took 5.53131103515625e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá, Distrito Capital took 0.00022745132446289062s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá, Distrito Capital took 0.26310157775878906s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá, Distrito Capital took 0.020760774612426758s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá, Distrito Capital took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá, Distrito Capital took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá, Distrito Capital took 3.0279159545898438e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá, Distrito Capital took 6.9141387939453125e-06s
INFO | --- Analysis for mapa-referencia-bogota took 2.967477798461914s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá D.C took 4.0531158447265625e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá D.C took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá D.C took 0.28025341033935547s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá D.C took 0.02043604850769043s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá D.C took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá D.C took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá D.C took 3.0994415283203125e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá D.C took 6.198883056640625e-06s
INFO | --- Analysis for mapa-referencia-bogota-dc took 3.4358620643615723s
Availability | SPARQL endpoint availability check for MARC Codes List took 4.1484832763671875e-05s
Availability | VoID file availability check for MARC Codes List took 0.00035572052001953125s
Completeness | Calculation of interlinking completeness for MARC Codes List took 0.2709054946899414s
Reputation | Calculation of the PageRank for MARC Codes List took 0.020377159118652344s
Interlinking | Calculation of Degree of Connection for MARC Codes List took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MARC Codes List took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for MARC Codes List took 0.00012040138244628906s
Believability | Calculation of trust value for MARC Codes List took 7.3909759521484375e-06s
INFO | --- Analysis for marc-codes took 13.837700605392456s
Availability | SPARQL endpoint availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 4.220008850097656e-05s
Availability | VoID file availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0005025863647460938s
Completeness | Calculation of interlinking completeness for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.27689552307128906s
Reputation | Calculation of the PageRank for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.020208358764648438s
Interlinking | Calculation of Degree of Connection for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 3.933906555175781e-05s
Believability | Calculation of trust value for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 6.198883056640625e-06s
INFO | --- Analysis for masc took 5.713988542556763s
Availability | SPARQL endpoint availability check for MASC-BN-NIF took 4.100799560546875e-05s
Availability | VoID file availability check for MASC-BN-NIF took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for MASC-BN-NIF took 0.2726738452911377s
Reputation | Calculation of the PageRank for MASC-BN-NIF took 0.020431995391845703s
Interlinking | Calculation of Degree of Connection for MASC-BN-NIF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MASC-BN-NIF took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for MASC-BN-NIF took 3.695487976074219e-05s
Believability | Calculation of trust value for MASC-BN-NIF took 7.152557373046875e-06s
INFO | --- Analysis for masc-bn-nif took 2.455719232559204s
Availability | SPARQL endpoint availability check for Mass Observation Archive catalogue took 1.5259103775024414s
Availability | VoID file availability check for Mass Observation Archive catalogue took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for Mass Observation Archive catalogue took 0.264512300491333s
Reputation | Calculation of the PageRank for Mass Observation Archive catalogue took 0.0204617977142334s
Interlinking | Calculation of Degree of Connection for Mass Observation Archive catalogue took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Mass Observation Archive catalogue took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Mass Observation Archive catalogue took 3.170967102050781e-05s
Believability | Calculation of trust value for Mass Observation Archive catalogue took 1.6689300537109375e-05s
INFO | --- Analysis for massobservationarchivecatalogue took 4.128035306930542s
Availability | SPARQL endpoint availability check for medline took 4.1484832763671875e-05s
Availability | VoID file availability check for medline took 0.0008807182312011719s
Completeness | Calculation of interlinking completeness for medline took 0.29964447021484375s
Reputation | Calculation of the PageRank for medline took 0.020308732986450195s
Interlinking | Calculation of Degree of Connection for medline took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for medline took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for medline took 3.409385681152344e-05s
Believability | Calculation of trust value for medline took 6.198883056640625e-06s
INFO | --- Analysis for medline took 6.642379522323608s
Availability | SPARQL endpoint availability check for mEducator: Linked Educational Resources took 2.052427053451538s
Availability | VoID file availability check for mEducator: Linked Educational Resources took 0.0007026195526123047s
Completeness | Calculation of interlinking completeness for mEducator: Linked Educational Resources took 0.2934763431549072s
Reputation | Calculation of the PageRank for mEducator: Linked Educational Resources took 0.020548343658447266s
Interlinking | Calculation of Degree of Connection for mEducator: Linked Educational Resources took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for mEducator: Linked Educational Resources took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for mEducator: Linked Educational Resources took 6.4849853515625e-05s
Believability | Calculation of trust value for mEducator: Linked Educational Resources took 7.867813110351562e-06s
INFO | --- Analysis for meducator took 33.1178560256958s
Availability | SPARQL endpoint availability check for Finnish translation of mesh took 4.601478576660156e-05s
Availability | VoID file availability check for Finnish translation of mesh took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for Finnish translation of mesh took 0.2665066719055176s
Reputation | Calculation of the PageRank for Finnish translation of mesh took 0.02047252655029297s
Interlinking | Calculation of Degree of Connection for Finnish translation of mesh took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Finnish translation of mesh took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for Finnish translation of mesh took 2.9802322387695312e-05s
Believability | Calculation of trust value for Finnish translation of mesh took 6.9141387939453125e-06s
INFO | --- Analysis for mesh-finnish took 2.9112565517425537s
Availability | SPARQL endpoint availability check for MeSH headings took 3.981590270996094e-05s
Availability | VoID file availability check for MeSH headings took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for MeSH headings took 0.26877474784851074s
Reputation | Calculation of the PageRank for MeSH headings took 0.020276308059692383s
Interlinking | Calculation of Degree of Connection for MeSH headings took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for MeSH headings took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for MeSH headings took 2.7418136596679688e-05s
Believability | Calculation of trust value for MeSH headings took 6.198883056640625e-06s
INFO | --- Analysis for mesh_headings took 2.9324681758880615s
Availability | SPARQL endpoint availability check for MeSH, IPSV - SKOS RDF took 3.910064697265625e-05s
Availability | VoID file availability check for MeSH, IPSV - SKOS RDF took 0.00032830238342285156s
Completeness | Calculation of interlinking completeness for MeSH, IPSV - SKOS RDF took 0.25931334495544434s
Reputation | Calculation of the PageRank for MeSH, IPSV - SKOS RDF took 0.02025008201599121s
Interlinking | Calculation of Degree of Connection for MeSH, IPSV - SKOS RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MeSH, IPSV - SKOS RDF took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for MeSH, IPSV - SKOS RDF took 3.075599670410156e-05s
Believability | Calculation of trust value for MeSH, IPSV - SKOS RDF took 6.198883056640625e-06s
INFO | --- Analysis for mesh_ipsv_skos_rdf took 2.8971498012542725s
Availability | SPARQL endpoint availability check for MeSH pairs took 4.076957702636719e-05s
Availability | VoID file availability check for MeSH pairs took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for MeSH pairs took 0.27072644233703613s
Reputation | Calculation of the PageRank for MeSH pairs took 0.02033066749572754s
Interlinking | Calculation of Degree of Connection for MeSH pairs took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MeSH pairs took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for MeSH pairs took 3.1948089599609375e-05s
Believability | Calculation of trust value for MeSH pairs took 9.5367431640625e-06s
INFO | --- Analysis for mesh_pairs took 2.9968037605285645s
Availability | SPARQL endpoint availability check for MeSH titles took 3.9577484130859375e-05s
Availability | VoID file availability check for MeSH titles took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for MeSH titles took 0.2687869071960449s
Reputation | Calculation of the PageRank for MeSH titles took 0.02034926414489746s
Interlinking | Calculation of Degree of Connection for MeSH titles took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for MeSH titles took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for MeSH titles took 2.8133392333984375e-05s
Believability | Calculation of trust value for MeSH titles took 7.62939453125e-06s
INFO | --- Analysis for mesh_titles took 2.960318088531494s
Availability | SPARQL endpoint availability check for Metadata k zákonům z psp.cz took 4.0531158447265625e-05s
Availability | VoID file availability check for Metadata k zákonům z psp.cz took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for Metadata k zákonům z psp.cz took 0.288341760635376s
Reputation | Calculation of the PageRank for Metadata k zákonům z psp.cz took 0.020550251007080078s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům z psp.cz took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Metadata k zákonům z psp.cz took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům z psp.cz took 2.7418136596679688e-05s
Believability | Calculation of trust value for Metadata k zákonům z psp.cz took 8.58306884765625e-06s
INFO | --- Analysis for metadata-k-z-kon-m-z-psp-cz took 2.941986322402954s
Availability | SPARQL endpoint availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 4.1961669921875e-05s
Availability | VoID file availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.2733004093170166s
Reputation | Calculation of the PageRank for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.02033066749572754s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 2.86102294921875e-05s
Believability | Calculation of trust value for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 8.58306884765625e-06s
INFO | --- Analysis for metadata-k-z-kon-m-ze-zakonyprolidi-cz---dv--uk-zkov--zn-n- took 2.9450714588165283s
Availability | SPARQL endpoint availability check for MetaShare metadata model took 4.1961669921875e-05s
Availability | VoID file availability check for MetaShare metadata model took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for MetaShare metadata model took 0.24780559539794922s
Reputation | Calculation of the PageRank for MetaShare metadata model took 0.020654916763305664s
Interlinking | Calculation of Degree of Connection for MetaShare metadata model took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MetaShare metadata model took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for MetaShare metadata model took 6.985664367675781e-05s
Believability | Calculation of trust value for MetaShare metadata model took 5.9604644775390625e-06s
INFO | --- Analysis for metashare took 2.4699347019195557s
Availability | SPARQL endpoint availability check for MExiCo took 4.267692565917969e-05s
Availability | VoID file availability check for MExiCo took 0.0006325244903564453s
Completeness | Calculation of interlinking completeness for MExiCo took 0.27227783203125s
Reputation | Calculation of the PageRank for MExiCo took 0.020113468170166016s
Interlinking | Calculation of Degree of Connection for MExiCo took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for MExiCo took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for MExiCo took 4.363059997558594e-05s
Believability | Calculation of trust value for MExiCo took 7.152557373046875e-06s
INFO | --- Analysis for mexico took 22.469318389892578s
Availability | SPARQL endpoint availability check for Coronavirus dataset took 1.0417189598083496s
Availability | VoID file availability check for Coronavirus dataset took 0.0002796649932861328s
Extra | Recovery of all triples for Coronavirus dataset took 11.353339672088623s
Performance | Total latancy measurement for Coronavirus dataset took 2.477327346801758s
Amount of data | Number of triples check for Coronavirus dataset took 1.1938095092773438s
Interoperability | New terms check for Coronavirus dataset took 2.455414056777954s
Versatility | Languages check for Coronavirus dataset took 60.509795904159546s
Interpretability | Number of blank nodes check for Coronavirus dataset took 3.1113169193267822s
Interpretability | RDF structures check for Coronavirus dataset took 0.5271296501159668s
Versatility | Serialization formats check for Coronavirus dataset took 0.538109540939331s
Availability | RDF dump link check for Coronavirus dataset took 0.5041542053222656s
License | MR license check for Coronavirus dataset took 0.5536844730377197s
License | HR license check for Coronavirus dataset took 42.058995723724365s
Amount of data | Number of property check for Coronavirus dataset took 0.5438525676727295s
Understandability | Number of label check for Coronavirus dataset took 1.3825438022613525s
Understandability | URI regex check for Coronavirus dataset took 0.9909837245941162s
Understandability | Vocabs check for Coronavirus dataset took 0.5085501670837402s
Verifiability | Authors check for Coronavirus dataset took 0.5546450614929199s
Verifiability | Publishers check for Coronavirus dataset took 0.5019693374633789s
Performance | Throughput check for Coronavirus dataset took 13.912185430526733s
Amount of data | Check the number of entities for Coronavirus dataset took 7.271766662597656e-05s
Verifiability | Contribs. check for Coronavirus dataset took 0.5106096267700195s
Interlinking | sameAs chians check for Coronavirus dataset took 0.5222816467285156s
Interlinking | skos check for Coronavirus dataset took 0.5430042743682861s
Interlinking | skos check for Coronavirus dataset took 0.5089263916015625s
Timeliness | dataset update frequency check for Coronavirus dataset took 0.5050678253173828s
Currency | Creation date check for Coronavirus dataset took 1.026050090789795s
Currency | Modification date check for Coronavirus dataset took 1.0175516605377197s
Rep.Conc. | URIs length for Coronavirus dataset took 8.99378252029419s
Interoperability | New vocabularies check for Coronavirus dataset took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Coronavirus dataset took 0.5155439376831055s
Accuracy | Check Functional Property for Coronavirus dataset took 0.7491834163665771s
Accuracy | Check Inverse Functional Property for Coronavirus dataset took 0.6997787952423096s
Accuracy | Check Empty annotation labels for Coronavirus dataset took 2.334280490875244s
Accuracy | Check White space in annotation for Coronavirus dataset took 0.022583961486816406s
Accuracy | Check Datatype consistency for Coronavirus dataset took 0.028395414352416992s
Consistency | Disjoint class check for Coronavirus dataset took 0.9466102123260498s
Consistency | Check Misplaced properties for Coronavirus dataset took 8.234551668167114s
Consistency | Misplaced classes for Coronavirus dataset took 0.6237399578094482s
Consistency | Check Ontology hijacking for Coronavirus dataset took 4.015536308288574s
Consistency | Check Invalid usage of undefined classes for Coronavirus dataset took 1.12754225730896s
Consistency | Check Invalid usage of undefined properties for Coronavirus dataset took 6.538015604019165s
Conciseness | Check Extensional conciseness for Coronavirus dataset took 0.03127861022949219s
Conciseness | Check Intensional conciseness for Coronavirus dataset took 0.5183868408203125s
Security | Sign check for Coronavirus dataset took 0.5356733798980713s
Availability | Check URIs Dereferenciability for Coronavirus dataset took 3170.9552137851715s
Completeness | Calculation of interlinking completeness for Coronavirus dataset took 1.5661780834197998s
Reputation | Calculation of the PageRank for Coronavirus dataset took 0.021436214447021484s
Interlinking | Calculation of Degree of Connection for Coronavirus dataset took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Coronavirus dataset took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Coronavirus dataset took 8.034706115722656e-05s
Interoperability | Check the re-using of existing vocabs for Coronavirus dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for Coronavirus dataset took 6.9141387939453125e-06s
INFO | --- Analysis for micro-coronavirus took 3412.303270816803s
Availability | SPARQL endpoint availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 6.461143493652344e-05s
Availability | VoID file availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.28888726234436035s
Reputation | Calculation of the PageRank for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.01999831199645996s
Interlinking | Calculation of Degree of Connection for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0006797313690185547s
Interlinking | Calculation of Clustering coefficient for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.00010442733764648438s
Believability | Calculation of trust value for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 6.9141387939453125e-06s
INFO | --- Analysis for miguiadeviajes-gnoss took 8.228667974472046s
Availability | SPARQL endpoint availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 4.267692565917969e-05s
Availability | VoID file availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.7330341339111328s
Reputation | Calculation of the PageRank for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.02086353302001953s
Interlinking | Calculation of Degree of Connection for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.00010967254638671875s
Believability | Calculation of trust value for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 6.67572021484375e-06s
INFO | --- Analysis for mismuseos-gnoss took 5.111854553222656s
Availability | SPARQL endpoint availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.09731554985046387s
Availability | VoID file availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0005383491516113281s
Completeness | Calculation of interlinking completeness for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.29171133041381836s
Reputation | Calculation of the PageRank for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.020627498626708984s
Interlinking | Calculation of Degree of Connection for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0010693073272705078s
Interlinking | Calculation of Clustering coefficient for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 5.5789947509765625e-05s
Believability | Calculation of trust value for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 7.62939453125e-06s
INFO | --- Analysis for mlsa took 4.551103353500366s
Availability | SPARQL endpoint availability check for Atmospheric Correction of High Resolution Optical Images model took 4.220008850097656e-05s
Availability | VoID file availability check for Atmospheric Correction of High Resolution Optical Images model took 0.0006258487701416016s
Completeness | Calculation of interlinking completeness for Atmospheric Correction of High Resolution Optical Images model took 0.27875423431396484s
Reputation | Calculation of the PageRank for Atmospheric Correction of High Resolution Optical Images model took 0.020695924758911133s
Interlinking | Calculation of Degree of Connection for Atmospheric Correction of High Resolution Optical Images model took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Atmospheric Correction of High Resolution Optical Images model took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Atmospheric Correction of High Resolution Optical Images model took 2.9325485229492188e-05s
Believability | Calculation of trust value for Atmospheric Correction of High Resolution Optical Images model took 7.867813110351562e-06s
INFO | --- Analysis for model took 33.9831964969635s
Availability | SPARQL endpoint availability check for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 4.57763671875e-05s
Availability | VoID file availability check for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.0006849765777587891s
Completeness | Calculation of interlinking completeness for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.29787564277648926s
Reputation | Calculation of the PageRank for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.020285606384277344s
Interlinking | Calculation of Degree of Connection for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 2.8133392333984375e-05s
Believability | Calculation of trust value for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 6.67572021484375e-06s
INFO | --- Analysis for model1 took 19.72680163383484s
Availability | SPARQL endpoint availability check for The MOND modular ontology for NIF data took 5.3882598876953125e-05s
Availability | VoID file availability check for The MOND modular ontology for NIF data took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for The MOND modular ontology for NIF data took 0.6901445388793945s
Reputation | Calculation of the PageRank for The MOND modular ontology for NIF data took 0.02044987678527832s
Interlinking | Calculation of Degree of Connection for The MOND modular ontology for NIF data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The MOND modular ontology for NIF data took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for The MOND modular ontology for NIF data took 2.8371810913085938e-05s
Believability | Calculation of trust value for The MOND modular ontology for NIF data took 1.71661376953125e-05s
INFO | --- Analysis for mond took 5.206183195114136s
Availability | SPARQL endpoint availability check for MONDIS took 3.981590270996094e-05s
Availability | VoID file availability check for MONDIS took 0.00030112266540527344s
Completeness | Calculation of interlinking completeness for MONDIS took 0.7210257053375244s
Reputation | Calculation of the PageRank for MONDIS took 0.020299434661865234s
Interlinking | Calculation of Degree of Connection for MONDIS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MONDIS took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for MONDIS took 2.9087066650390625e-05s
Believability | Calculation of trust value for MONDIS took 6.9141387939453125e-06s
INFO | --- Analysis for mondis took 3.3732969760894775s
Availability | SPARQL endpoint availability check for Monumentos took 4.029273986816406e-05s
Availability | VoID file availability check for Monumentos took 0.0003170967102050781s
Completeness | Calculation of interlinking completeness for Monumentos took 0.2791104316711426s
Reputation | Calculation of the PageRank for Monumentos took 0.0202939510345459s
Interlinking | Calculation of Degree of Connection for Monumentos took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Monumentos took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Monumentos took 2.9802322387695312e-05s
Believability | Calculation of trust value for Monumentos took 6.198883056640625e-06s
INFO | --- Analysis for monumentos-zaragoza took 3.038250207901001s
Availability | SPARQL endpoint availability check for MORElab took 1.2684426307678223s
Availability | VoID file availability check for MORElab took 0.000774383544921875s
Completeness | Calculation of interlinking completeness for MORElab took 0.2917008399963379s
Reputation | Calculation of the PageRank for MORElab took 0.020391225814819336s
Interlinking | Calculation of Degree of Connection for MORElab took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for MORElab took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for MORElab took 8.678436279296875e-05s
Believability | Calculation of trust value for MORElab took 7.867813110351562e-06s
INFO | --- Analysis for morelab took 4.995753049850464s
Availability | SPARQL endpoint availability check for Mathematics Subject Classification took 1.8613924980163574s
Availability | VoID file availability check for Mathematics Subject Classification took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for Mathematics Subject Classification took 0.2942497730255127s
Reputation | Calculation of the PageRank for Mathematics Subject Classification took 0.020305156707763672s
Interlinking | Calculation of Degree of Connection for Mathematics Subject Classification took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Mathematics Subject Classification took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Mathematics Subject Classification took 8.58306884765625e-05s
Believability | Calculation of trust value for Mathematics Subject Classification took 7.152557373046875e-06s
INFO | --- Analysis for msc took 5.82057523727417s
Availability | SPARQL endpoint availability check for Multext-East took 4.1961669921875e-05s
Availability | VoID file availability check for Multext-East took 0.0010616779327392578s
Completeness | Calculation of interlinking completeness for Multext-East took 0.2823336124420166s
Reputation | Calculation of the PageRank for Multext-East took 0.020329713821411133s
Interlinking | Calculation of Degree of Connection for Multext-East took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Multext-East took 0.0010030269622802734s
Interlinking | Calculation of Clustering coefficient for Multext-East took 4.2438507080078125e-05s
Believability | Calculation of trust value for Multext-East took 6.198883056640625e-06s
INFO | --- Analysis for multext-east took 2.883200168609619s
Availability | SPARQL endpoint availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 4.172325134277344e-05s
Availability | VoID file availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.00023412704467773438s
Completeness | Calculation of interlinking completeness for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.24882769584655762s
Reputation | Calculation of the PageRank for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.020251750946044922s
Interlinking | Calculation of Degree of Connection for The DGT Multilingual Translation Memory of the Acquis Communautaire took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for The DGT Multilingual Translation Memory of the Acquis Communautaire took 3.0279159545898438e-05s
Believability | Calculation of trust value for The DGT Multilingual Translation Memory of the Acquis Communautaire took 7.152557373046875e-06s
INFO | --- Analysis for multilingualeulaw took 2.9850711822509766s
Availability | SPARQL endpoint availability check for Multimedia Lab took 4.1961669921875e-05s
Availability | VoID file availability check for Multimedia Lab took 0.0004305839538574219s
Completeness | Calculation of interlinking completeness for Multimedia Lab took 0.2892732620239258s
Reputation | Calculation of the PageRank for Multimedia Lab took 0.02056145668029785s
Interlinking | Calculation of Degree of Connection for Multimedia Lab took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Multimedia Lab took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Multimedia Lab took 3.0994415283203125e-05s
Believability | Calculation of trust value for Multimedia Lab took 6.9141387939453125e-06s
INFO | --- Analysis for multimedia-lab took 2.5372395515441895s
Availability | SPARQL endpoint availability check for Munich Offener Haushalt took 4.1484832763671875e-05s
Availability | VoID file availability check for Munich Offener Haushalt took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for Munich Offener Haushalt took 0.27232909202575684s
Reputation | Calculation of the PageRank for Munich Offener Haushalt took 0.02028059959411621s
Interlinking | Calculation of Degree of Connection for Munich Offener Haushalt took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Munich Offener Haushalt took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Munich Offener Haushalt took 2.8848648071289062e-05s
Believability | Calculation of trust value for Munich Offener Haushalt took 6.9141387939453125e-06s
INFO | --- Analysis for munich-offener-haushalt took 3.0017824172973633s
Availability | SPARQL endpoint availability check for Muninn World War I took 1.5593392848968506s
Availability | VoID file availability check for Muninn World War I took 0.0006673336029052734s
Completeness | Calculation of interlinking completeness for Muninn World War I took 0.2817683219909668s
Reputation | Calculation of the PageRank for Muninn World War I took 0.02037787437438965s
Interlinking | Calculation of Degree of Connection for Muninn World War I took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Muninn World War I took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Muninn World War I took 7.891654968261719e-05s
Believability | Calculation of trust value for Muninn World War I took 5.4836273193359375e-06s
INFO | --- Analysis for muninn-world-war-i took 10.448143482208252s
Availability | SPARQL endpoint availability check for Musei Italiani took 3.933906555175781e-05s
Availability | VoID file availability check for Musei Italiani took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for Musei Italiani took 0.29456496238708496s
Reputation | Calculation of the PageRank for Musei Italiani took 0.0201871395111084s
Interlinking | Calculation of Degree of Connection for Musei Italiani took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Musei Italiani took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Musei Italiani took 2.8133392333984375e-05s
Believability | Calculation of trust value for Musei Italiani took 6.4373016357421875e-06s
INFO | --- Analysis for musei-italiani took 3.468402862548828s
Availability | SPARQL endpoint availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 4.267692565917969e-05s
Availability | VoID file availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0005855560302734375s
Completeness | Calculation of interlinking completeness for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.27616262435913086s
Reputation | Calculation of the PageRank for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.020223140716552734s
Interlinking | Calculation of Degree of Connection for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0001010894775390625s
Believability | Calculation of trust value for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 5.7220458984375e-06s
INFO | --- Analysis for museosespania-gnoss took 4.105539083480835s
Availability | SPARQL endpoint availability check for Italian Museums took 2.1294987201690674s
Availability | VoID file availability check for Italian Museums took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for Italian Museums took 0.26029014587402344s
Reputation | Calculation of the PageRank for Italian Museums took 0.02022838592529297s
Interlinking | Calculation of Degree of Connection for Italian Museums took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Italian Museums took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Italian Museums took 7.843971252441406e-05s
Believability | Calculation of trust value for Italian Museums took 5.245208740234375e-06s
INFO | --- Analysis for museums-in-italy took 4.652131795883179s
Availability | SPARQL endpoint availability check for MusicBrainz took 5.1975250244140625e-05s
Availability | VoID file availability check for MusicBrainz took 0.0002288818359375s
Completeness | Calculation of interlinking completeness for MusicBrainz took 0.26824235916137695s
Reputation | Calculation of the PageRank for MusicBrainz took 0.020522356033325195s
Interlinking | Calculation of Degree of Connection for MusicBrainz took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MusicBrainz took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for MusicBrainz took 2.8848648071289062e-05s
Believability | Calculation of trust value for MusicBrainz took 5.9604644775390625e-06s
INFO | --- Analysis for musicbrainz_ took 2.9686005115509033s
Availability | SPARQL endpoint availability check for MusicNet Codex took 4.0531158447265625e-05s
Availability | VoID file availability check for MusicNet Codex took 0.0008389949798583984s
Completeness | Calculation of interlinking completeness for MusicNet Codex took 0.26043176651000977s
Reputation | Calculation of the PageRank for MusicNet Codex took 0.020369291305541992s
Interlinking | Calculation of Degree of Connection for MusicNet Codex took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MusicNet Codex took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for MusicNet Codex took 2.6464462280273438e-05s
Believability | Calculation of trust value for MusicNet Codex took 7.152557373046875e-06s
INFO | --- Analysis for musicnet_codex took 2.84956955909729s
Availability | SPARQL endpoint availability check for Muziekweb took 0.8304634094238281s
Availability | VoID file availability check for Muziekweb took 0.0005757808685302734s
Extra | Recovery of all triples for Muziekweb took 1.6476209163665771s
Performance | Total latancy measurement for Muziekweb took 1.4156951904296875s
Amount of data | Number of triples check for Muziekweb took 0.26202917098999023s
Interoperability | New terms check for Muziekweb took 1.4519362449645996s
Versatility | Languages check for Muziekweb took 0.27861952781677246s
Interpretability | Number of blank nodes check for Muziekweb took 0.3155853748321533s
Interpretability | RDF structures check for Muziekweb took 0.24976181983947754s
Versatility | Serialization formats check for Muziekweb took 0.24953746795654297s
Availability | RDF dump link check for Muziekweb took 0.3054821491241455s
License | MR license check for Muziekweb took 0.27106761932373047s
License | HR license check for Muziekweb took 0.3103494644165039s
Amount of data | Number of property check for Muziekweb took 0.25257444381713867s
Understandability | Number of label check for Muziekweb took 0.25029850006103516s
Understandability | URI regex check for Muziekweb took 0.5564508438110352s
Understandability | Vocabs check for Muziekweb took 0.3004946708679199s
Verifiability | Authors check for Muziekweb took 0.30812668800354004s
Verifiability | Publishers check for Muziekweb took 0.3229231834411621s
Performance | Throughput check for Muziekweb took 11.259531259536743s
Amount of data | Check the number of entities for Muziekweb took 6.67572021484375e-05s
Verifiability | Contribs. check for Muziekweb took 0.26647019386291504s
Interlinking | sameAs chians check for Muziekweb took 0.26236820220947266s
Interlinking | skos check for Muziekweb took 0.24990344047546387s
Interlinking | skos check for Muziekweb took 0.31479907035827637s
Timeliness | dataset update frequency check for Muziekweb took 0.29489564895629883s
Currency | Creation date check for Muziekweb took 0.5710599422454834s
Currency | Modification date check for Muziekweb took 0.5495166778564453s
Rep.Conc. | URIs length for Muziekweb took 1.1430389881134033s
Interoperability | New vocabularies check for Muziekweb took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for Muziekweb took 0.2713353633880615s
Accuracy | Check Functional Property for Muziekweb took 0.3040590286254883s
Accuracy | Check Inverse Functional Property for Muziekweb took 0.26227736473083496s
Accuracy | Check Empty annotation labels for Muziekweb took 0.6999835968017578s
Accuracy | Check White space in annotation for Muziekweb took 0.028548002243041992s
Accuracy | Check Datatype consistency for Muziekweb took 0.028094053268432617s
Consistency | Disjoint class check for Muziekweb took 0.32122802734375s
Consistency | Check Misplaced properties for Muziekweb took 0.5794558525085449s
Consistency | Check Ontology hijacking for Muziekweb took 1.796973705291748s
Consistency | Check Invalid usage of undefined classes for Muziekweb took 1.1289587020874023s
Consistency | Check Invalid usage of undefined properties for Muziekweb took 1.400381088256836s
Conciseness | Check Extensional conciseness for Muziekweb took 0.03277397155761719s
Conciseness | Check Intensional conciseness for Muziekweb took 0.3046562671661377s
Security | Sign check for Muziekweb took 0.2536029815673828s
Availability | Check URIs Dereferenciability for Muziekweb took 729.3420667648315s
Completeness | Calculation of interlinking completeness for Muziekweb took 1.2847414016723633s
Reputation | Calculation of the PageRank for Muziekweb took 0.020640134811401367s
Interlinking | Calculation of Degree of Connection for Muziekweb took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Muziekweb took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for Muziekweb took 6.079673767089844e-05s
Interoperability | Check the re-using of existing vocabs for Muziekweb took 1.6689300537109375e-06s
Believability | Calculation of trust value for Muziekweb took 7.867813110351562e-06s
INFO | --- Analysis for muziekweb took 782.599392414093s
Availability | SPARQL endpoint availability check for myExperiment took 0.29430341720581055s
Availability | VoID file availability check for myExperiment took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for myExperiment took 0.28026390075683594s
Reputation | Calculation of the PageRank for myExperiment took 0.020490407943725586s
Interlinking | Calculation of Degree of Connection for myExperiment took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for myExperiment took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for myExperiment took 9.942054748535156e-05s
Believability | Calculation of trust value for myExperiment took 5.4836273193359375e-06s
INFO | --- Analysis for my-experiment took 5.971954107284546s
Availability | SPARQL endpoint availability check for My Family Lineage took 0.10596442222595215s
Availability | VoID file availability check for My Family Lineage took 0.00058746337890625s
Completeness | Calculation of interlinking completeness for My Family Lineage took 0.28821277618408203s
Reputation | Calculation of the PageRank for My Family Lineage took 0.02056431770324707s
Interlinking | Calculation of Degree of Connection for My Family Lineage took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for My Family Lineage took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for My Family Lineage took 0.00010609626770019531s
Believability | Calculation of trust value for My Family Lineage took 4.76837158203125e-06s
INFO | --- Analysis for my-family-lineage took 4.4558610916137695s
Availability | SPARQL endpoint availability check for My ontology test took 0.48595380783081055s
Availability | VoID file availability check for My ontology test took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for My ontology test took 0.27060985565185547s
Reputation | Calculation of the PageRank for My ontology test took 0.02019810676574707s
Interlinking | Calculation of Degree of Connection for My ontology test took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for My ontology test took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for My ontology test took 3.0040740966796875e-05s
Believability | Calculation of trust value for My ontology test took 5.7220458984375e-06s
INFO | --- Analysis for myontologytest took 4.025013446807861s
Availability | SPARQL endpoint availability check for myopenlink dataspaces took 4.220008850097656e-05s
Availability | VoID file availability check for myopenlink dataspaces took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for myopenlink dataspaces took 0.2548635005950928s
Reputation | Calculation of the PageRank for myopenlink dataspaces took 0.020535945892333984s
Interlinking | Calculation of Degree of Connection for myopenlink dataspaces took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for myopenlink dataspaces took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for myopenlink dataspaces took 0.000102996826171875s
Believability | Calculation of trust value for myopenlink dataspaces took 6.9141387939453125e-06s
INFO | --- Analysis for myopenlink-dataspaces took 3.1334524154663086s
Availability | SPARQL endpoint availability check for N-Lex as Linked Data took 5.033545970916748s
Availability | VoID file availability check for N-Lex as Linked Data took 0.0006659030914306641s
Completeness | Calculation of interlinking completeness for N-Lex as Linked Data took 0.709639310836792s
Reputation | Calculation of the PageRank for N-Lex as Linked Data took 0.020575761795043945s
Interlinking | Calculation of Degree of Connection for N-Lex as Linked Data took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for N-Lex as Linked Data took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for N-Lex as Linked Data took 7.510185241699219e-05s
Believability | Calculation of trust value for N-Lex as Linked Data took 4.76837158203125e-06s
INFO | --- Analysis for n-lex-as-linked-data took 14.676979541778564s
Availability | SPARQL endpoint availability check for NAICS 2007 took 25.115168809890747s
Availability | VoID file availability check for NAICS 2007 took 0.000774383544921875s
Completeness | Calculation of interlinking completeness for NAICS 2007 took 0.7102603912353516s
Reputation | Calculation of the PageRank for NAICS 2007 took 0.020552635192871094s
Interlinking | Calculation of Degree of Connection for NAICS 2007 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for NAICS 2007 took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for NAICS 2007 took 3.62396240234375e-05s
Believability | Calculation of trust value for NAICS 2007 took 5.7220458984375e-06s
INFO | --- Analysis for naics-2007 took 122.07015538215637s
Availability | SPARQL endpoint availability check for NAICS 2012 took 23.398267030715942s
Availability | VoID file availability check for NAICS 2012 took 0.0008318424224853516s
Completeness | Calculation of interlinking completeness for NAICS 2012 took 0.7100880146026611s
Reputation | Calculation of the PageRank for NAICS 2012 took 0.021651029586791992s
Interlinking | Calculation of Degree of Connection for NAICS 2012 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for NAICS 2012 took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for NAICS 2012 took 5.030632019042969e-05s
Believability | Calculation of trust value for NAICS 2012 took 5.245208740234375e-06s
INFO | --- Analysis for naics-2012 took 120.32457661628723s
Availability | SPARQL endpoint availability check for National Agricultural Library Thesaurus took 3.981590270996094e-05s
Availability | VoID file availability check for National Agricultural Library Thesaurus took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for National Agricultural Library Thesaurus took 0.7171547412872314s
Reputation | Calculation of the PageRank for National Agricultural Library Thesaurus took 0.020528316497802734s
Interlinking | Calculation of Degree of Connection for National Agricultural Library Thesaurus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for National Agricultural Library Thesaurus took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for National Agricultural Library Thesaurus took 5.507469177246094e-05s
Believability | Calculation of trust value for National Agricultural Library Thesaurus took 5.0067901611328125e-06s
INFO | --- Analysis for nalt took 4.7022576332092285s
Availability | SPARQL endpoint availability check for Usernames  took 4.1484832763671875e-05s
Availability | VoID file availability check for Usernames  took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for Usernames  took 0.26059699058532715s
Reputation | Calculation of the PageRank for Usernames  took 0.02015233039855957s
Interlinking | Calculation of Degree of Connection for Usernames  took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Usernames  took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Usernames  took 2.86102294921875e-05s
Believability | Calculation of trust value for Usernames  took 6.9141387939453125e-06s
INFO | --- Analysis for Names took 3.95428729057312s
Availability | SPARQL endpoint availability check for Web NDL Authorities - National Diet Library of Japan took 2.0245273113250732s
Availability | VoID file availability check for Web NDL Authorities - National Diet Library of Japan took 0.0007088184356689453s
Extra | Recovery of all triples for Web NDL Authorities - National Diet Library of Japan took 0.981273889541626s
Performance | Total latancy measurement for Web NDL Authorities - National Diet Library of Japan took 1.82806396484375s
Amount of data | Number of triples check for Web NDL Authorities - National Diet Library of Japan took 12.429365396499634s
Interoperability | New terms check for Web NDL Authorities - National Diet Library of Japan took 21.047085523605347s
Versatility | Languages check for Web NDL Authorities - National Diet Library of Japan took 0.37897348403930664s
Interpretability | Number of blank nodes check for Web NDL Authorities - National Diet Library of Japan took 13.700621366500854s
Security | Check HTTPS for Web NDL Authorities - National Diet Library of Japan took 0.3203253746032715s
Interpretability | RDF structures check for Web NDL Authorities - National Diet Library of Japan took 0.41782617568969727s
Versatility | Serialization formats check for Web NDL Authorities - National Diet Library of Japan took 0.420729398727417s
Availability | RDF dump link check for Web NDL Authorities - National Diet Library of Japan took 0.36385607719421387s
License | MR license check for Web NDL Authorities - National Diet Library of Japan took 0.3888967037200928s
License | HR license check for Web NDL Authorities - National Diet Library of Japan took 91.81751370429993s
Amount of data | Number of property check for Web NDL Authorities - National Diet Library of Japan took 0.9068050384521484s
Understandability | Number of label check for Web NDL Authorities - National Diet Library of Japan took 6.115838050842285s
Understandability | URI regex check for Web NDL Authorities - National Diet Library of Japan took 0.7852020263671875s
Understandability | Vocabs check for Web NDL Authorities - National Diet Library of Japan took 0.3706510066986084s
Verifiability | Authors check for Web NDL Authorities - National Diet Library of Japan took 0.401456356048584s
Verifiability | Publishers check for Web NDL Authorities - National Diet Library of Japan took 0.37872743606567383s
Performance | Throughput check for Web NDL Authorities - National Diet Library of Japan took 11.709269285202026s
Amount of data | Check the number of entities for Web NDL Authorities - National Diet Library of Japan took 9.679794311523438e-05s
Verifiability | Contribs. check for Web NDL Authorities - National Diet Library of Japan took 0.3390207290649414s
Interlinking | sameAs chians check for Web NDL Authorities - National Diet Library of Japan took 0.5679042339324951s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.6545753479003906s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.3896942138671875s
Timeliness | dataset update frequency check for Web NDL Authorities - National Diet Library of Japan took 0.3747553825378418s
Currency | Creation date check for Web NDL Authorities - National Diet Library of Japan took 1.1128242015838623s
Currency | Modification date check for Web NDL Authorities - National Diet Library of Japan took 0.7277073860168457s
Rep.Conc. | URIs length for Web NDL Authorities - National Diet Library of Japan took 1.0172626972198486s
Interoperability | New vocabularies check for Web NDL Authorities - National Diet Library of Japan took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Web NDL Authorities - National Diet Library of Japan took 0.411975622177124s
Accuracy | Check Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.3890962600708008s
Accuracy | Check Inverse Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.354813814163208s
Accuracy | Check Empty annotation labels for Web NDL Authorities - National Diet Library of Japan took 0.4180338382720947s
Accuracy | Check White space in annotation for Web NDL Authorities - National Diet Library of Japan took 0.0007848739624023438s
Accuracy | Check Datatype consistency for Web NDL Authorities - National Diet Library of Japan took 0.001058816909790039s
Consistency | Disjoint class check for Web NDL Authorities - National Diet Library of Japan took 0.4026165008544922s
Consistency | Check Misplaced properties for Web NDL Authorities - National Diet Library of Japan took 0.7943429946899414s
Consistency | Misplaced classes for Web NDL Authorities - National Diet Library of Japan took 0.3208649158477783s
Consistency | Check Ontology hijacking for Web NDL Authorities - National Diet Library of Japan took 1.5939788818359375s
Consistency | Check Invalid usage of undefined classes for Web NDL Authorities - National Diet Library of Japan took 1.1806447505950928s
Consistency | Check Invalid usage of undefined properties for Web NDL Authorities - National Diet Library of Japan took 1.5444262027740479s
Conciseness | Check Extensional conciseness for Web NDL Authorities - National Diet Library of Japan took 0.0009751319885253906s
Security | Sign check for Web NDL Authorities - National Diet Library of Japan took 0.3308722972869873s
Availability | Check URIs Dereferenciability for Web NDL Authorities - National Diet Library of Japan took 4.1050124168396s
Completeness | Calculation of interlinking completeness for Web NDL Authorities - National Diet Library of Japan took 0.344696044921875s
Reputation | Calculation of the PageRank for Web NDL Authorities - National Diet Library of Japan took 0.020613908767700195s
Interlinking | Calculation of Degree of Connection for Web NDL Authorities - National Diet Library of Japan took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Web NDL Authorities - National Diet Library of Japan took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Web NDL Authorities - National Diet Library of Japan took 6.794929504394531e-05s
Interoperability | Check the re-using of existing vocabs for Web NDL Authorities - National Diet Library of Japan took 1.1920928955078125e-06s
Believability | Calculation of trust value for Web NDL Authorities - National Diet Library of Japan took 5.0067901611328125e-06s
INFO | --- Analysis for national-diet-library-authorities took 235.284836769104s
Availability | SPARQL endpoint availability check for National Diet Library of Japan subject headings took 0.33968472480773926s
Availability | VoID file availability check for National Diet Library of Japan subject headings took 0.0006582736968994141s
Extra | Recovery of all triples for National Diet Library of Japan subject headings took 1.5797882080078125s
Performance | Total latancy measurement for National Diet Library of Japan subject headings took 1.9088048934936523s
Amount of data | Number of triples check for National Diet Library of Japan subject headings took 12.0275559425354s
Interoperability | New terms check for National Diet Library of Japan subject headings took 25.42980933189392s
Versatility | Languages check for National Diet Library of Japan subject headings took 0.42406558990478516s
Interpretability | Number of blank nodes check for National Diet Library of Japan subject headings took 13.80381464958191s
Security | Check HTTPS for National Diet Library of Japan subject headings took 0.3860132694244385s
Interpretability | RDF structures check for National Diet Library of Japan subject headings took 0.39614129066467285s
Versatility | Serialization formats check for National Diet Library of Japan subject headings took 0.3569762706756592s
Availability | RDF dump link check for National Diet Library of Japan subject headings took 0.41091203689575195s
License | MR license check for National Diet Library of Japan subject headings took 0.3696560859680176s
License | HR license check for National Diet Library of Japan subject headings took 91.76593899726868s
Amount of data | Number of property check for National Diet Library of Japan subject headings took 0.884702205657959s
Understandability | Number of label check for National Diet Library of Japan subject headings took 5.380609512329102s
Understandability | URI regex check for National Diet Library of Japan subject headings took 0.7203991413116455s
Understandability | Vocabs check for National Diet Library of Japan subject headings took 0.37169528007507324s
Verifiability | Authors check for National Diet Library of Japan subject headings took 0.3785979747772217s
Verifiability | Publishers check for National Diet Library of Japan subject headings took 0.3725094795227051s
Performance | Throughput check for National Diet Library of Japan subject headings took 11.836690902709961s
Amount of data | Check the number of entities for National Diet Library of Japan subject headings took 9.512901306152344e-05s
Verifiability | Contribs. check for National Diet Library of Japan subject headings took 0.3363780975341797s
Interlinking | sameAs chians check for National Diet Library of Japan subject headings took 0.5310261249542236s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.4765625s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.394005298614502s
Timeliness | dataset update frequency check for National Diet Library of Japan subject headings took 0.3597538471221924s
Currency | Creation date check for National Diet Library of Japan subject headings took 1.1624200344085693s
Currency | Modification date check for National Diet Library of Japan subject headings took 0.7691419124603271s
Rep.Conc. | URIs length for National Diet Library of Japan subject headings took 1.06196928024292s
Interoperability | New vocabularies check for National Diet Library of Japan subject headings took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for National Diet Library of Japan subject headings took 0.37063050270080566s
Accuracy | Check Functional Property for National Diet Library of Japan subject headings took 0.3959941864013672s
Accuracy | Check Inverse Functional Property for National Diet Library of Japan subject headings took 0.4017648696899414s
Accuracy | Check Empty annotation labels for National Diet Library of Japan subject headings took 0.4165503978729248s
Accuracy | Check White space in annotation for National Diet Library of Japan subject headings took 0.0007388591766357422s
Accuracy | Check Datatype consistency for National Diet Library of Japan subject headings took 0.0010712146759033203s
Consistency | Disjoint class check for National Diet Library of Japan subject headings took 0.3989722728729248s
Consistency | Check Misplaced properties for National Diet Library of Japan subject headings took 0.79351806640625s
Consistency | Misplaced classes for National Diet Library of Japan subject headings took 0.37932872772216797s
Consistency | Check Ontology hijacking for National Diet Library of Japan subject headings took 1.5849997997283936s
Consistency | Check Invalid usage of undefined classes for National Diet Library of Japan subject headings took 1.1702206134796143s
Consistency | Check Invalid usage of undefined properties for National Diet Library of Japan subject headings took 1.5769994258880615s
Conciseness | Check Extensional conciseness for National Diet Library of Japan subject headings took 0.0006878376007080078s
Security | Sign check for National Diet Library of Japan subject headings took 0.3803067207336426s
Availability | Check URIs Dereferenciability for National Diet Library of Japan subject headings took 4.059773206710815s
Completeness | Calculation of interlinking completeness for National Diet Library of Japan subject headings took 0.27980518341064453s
Reputation | Calculation of the PageRank for National Diet Library of Japan subject headings took 0.02039027214050293s
Interlinking | Calculation of Degree of Connection for National Diet Library of Japan subject headings took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for National Diet Library of Japan subject headings took 0.0007774829864501953s
Interlinking | Calculation of Clustering coefficient for National Diet Library of Japan subject headings took 4.982948303222656e-05s
Interoperability | Check the re-using of existing vocabs for National Diet Library of Japan subject headings took 1.430511474609375e-06s
Believability | Calculation of trust value for National Diet Library of Japan subject headings took 7.152557373046875e-06s
INFO | --- Analysis for national-diet-library-subject-headings took 237.21727514266968s
Availability | SPARQL endpoint availability check for National Library of Greece Authority Records took 58.054450035095215s
Availability | VoID file availability check for National Library of Greece Authority Records took 0.0006732940673828125s
Completeness | Calculation of interlinking completeness for National Library of Greece Authority Records took 0.8928937911987305s
Reputation | Calculation of the PageRank for National Library of Greece Authority Records took 0.020583629608154297s
Interlinking | Calculation of Degree of Connection for National Library of Greece Authority Records took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for National Library of Greece Authority Records took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for National Library of Greece Authority Records took 4.363059997558594e-05s
Believability | Calculation of trust value for National Library of Greece Authority Records took 5.7220458984375e-06s
INFO | --- Analysis for national-library-of-greece-authority-records took 150.6925756931305s
Availability | SPARQL endpoint availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 4.220008850097656e-05s
Availability | VoID file availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0006163120269775391s
Completeness | Calculation of interlinking completeness for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.2935211658477783s
Reputation | Calculation of the PageRank for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.02040386199951172s
Interlinking | Calculation of Degree of Connection for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.67572021484375e-05s
Believability | Calculation of trust value for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.9141387939453125e-06s
INFO | --- Analysis for Naturopathy took 6.086225271224976s
Availability | SPARQL endpoint availability check for Naturopathy took 4.00543212890625e-05s
Availability | VoID file availability check for Naturopathy took 0.00035643577575683594s
Completeness | Calculation of interlinking completeness for Naturopathy took 0.27842140197753906s
Reputation | Calculation of the PageRank for Naturopathy took 0.02038884162902832s
Interlinking | Calculation of Degree of Connection for Naturopathy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Naturopathy took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Naturopathy took 3.0994415283203125e-05s
Believability | Calculation of trust value for Naturopathy took 6.67572021484375e-06s
INFO | --- Analysis for naturopathy2 took 2.904850721359253s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 4.0531158447265625e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.2899656295776367s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.020280838012695312s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 2.9087066650390625e-05s
Believability | Calculation of trust value for NCI Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for nci-thesaurus took 3.4252896308898926s
Availability | SPARQL endpoint availability check for COVID-19 Data took 3.3852968215942383s
Availability | VoID file availability check for COVID-19 Data took 0.00029206275939941406s
Completeness | Calculation of interlinking completeness for COVID-19 Data took 0.27046823501586914s
Reputation | Calculation of the PageRank for COVID-19 Data took 0.020264148712158203s
Interlinking | Calculation of Degree of Connection for COVID-19 Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for COVID-19 Data took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for COVID-19 Data took 2.8133392333984375e-05s
Believability | Calculation of trust value for COVID-19 Data took 7.152557373046875e-06s
INFO | --- Analysis for NCMI-COVID-19 took 7.25297212600708s
Availability | SPARQL endpoint availability check for NCMI-COVID-19 took 2.3960230350494385s
Availability | VoID file availability check for NCMI-COVID-19 took 0.000278472900390625s
Completeness | Calculation of interlinking completeness for NCMI-COVID-19 took 0.2593865394592285s
Reputation | Calculation of the PageRank for NCMI-COVID-19 took 0.020301103591918945s
Interlinking | Calculation of Degree of Connection for NCMI-COVID-19 took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for NCMI-COVID-19 took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for NCMI-COVID-19 took 1.2159347534179688e-05s
Believability | Calculation of trust value for NCMI-COVID-19 took 6.67572021484375e-06s
INFO | --- Analysis for NCMICOVID-19 took 6.2865941524505615s
Availability | SPARQL endpoint availability check for NDF-RT took 3.981590270996094e-05s
Availability | VoID file availability check for NDF-RT took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for NDF-RT took 0.2778606414794922s
Reputation | Calculation of the PageRank for NDF-RT took 0.020148277282714844s
Interlinking | Calculation of Degree of Connection for NDF-RT took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NDF-RT took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for NDF-RT took 2.6941299438476562e-05s
Believability | Calculation of trust value for NDF-RT took 6.67572021484375e-06s
INFO | --- Analysis for ndf-rt took 3.7645394802093506s
Availability | SPARQL endpoint availability check for Near took 4.982948303222656e-05s
Availability | VoID file availability check for Near took 0.0005769729614257812s
Completeness | Calculation of interlinking completeness for Near took 0.276564359664917s
Reputation | Calculation of the PageRank for Near took 0.020358562469482422s
Interlinking | Calculation of Degree of Connection for Near took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Near took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Near took 9.1552734375e-05s
Believability | Calculation of trust value for Near took 7.3909759521484375e-06s
INFO | --- Analysis for near took 9.239543676376343s
Availability | SPARQL endpoint availability check for Neel took 5.14984130859375e-05s
Availability | VoID file availability check for Neel took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for Neel took 0.2670421600341797s
Reputation | Calculation of the PageRank for Neel took 0.020464420318603516s
Interlinking | Calculation of Degree of Connection for Neel took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Neel took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Neel took 2.8848648071289062e-05s
Believability | Calculation of trust value for Neel took 5.7220458984375e-06s
INFO | --- Analysis for neel took 2.9923934936523438s
Availability | SPARQL endpoint availability check for Neurocommons text mining pilot took 4.1484832763671875e-05s
Availability | VoID file availability check for Neurocommons text mining pilot took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for Neurocommons text mining pilot took 0.27335286140441895s
Reputation | Calculation of the PageRank for Neurocommons text mining pilot took 0.020488739013671875s
Interlinking | Calculation of Degree of Connection for Neurocommons text mining pilot took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Neurocommons text mining pilot took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for Neurocommons text mining pilot took 3.0279159545898438e-05s
Believability | Calculation of trust value for Neurocommons text mining pilot took 7.3909759521484375e-06s
INFO | --- Analysis for neurocommons_text_mining_pilot took 3.015681505203247s
Availability | SPARQL endpoint availability check for NeuroLex Wiki took 4.00543212890625e-05s
Availability | VoID file availability check for NeuroLex Wiki took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for NeuroLex Wiki took 0.26263427734375s
Reputation | Calculation of the PageRank for NeuroLex Wiki took 0.020238161087036133s
Interlinking | Calculation of Degree of Connection for NeuroLex Wiki took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NeuroLex Wiki took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for NeuroLex Wiki took 2.6941299438476562e-05s
Believability | Calculation of trust value for NeuroLex Wiki took 5.9604644775390625e-06s
INFO | --- Analysis for neurolex-wiki took 2.3502144813537598s
Availability | SPARQL endpoint availability check for Shivani Goyal Photography took 4.1961669921875e-05s
Availability | VoID file availability check for Shivani Goyal Photography took 0.0006473064422607422s
Completeness | Calculation of interlinking completeness for Shivani Goyal Photography took 0.24839258193969727s
Reputation | Calculation of the PageRank for Shivani Goyal Photography took 0.020537614822387695s
Interlinking | Calculation of Degree of Connection for Shivani Goyal Photography took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Shivani Goyal Photography took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for Shivani Goyal Photography took 4.38690185546875e-05s
Believability | Calculation of trust value for Shivani Goyal Photography took 6.4373016357421875e-06s
INFO | --- Analysis for newborn-photography-maternity-photoshoot-shivani-goyal took 3.4186949729919434s
Availability | SPARQL endpoint availability check for News-100 NIF NER Corpus took 4.1484832763671875e-05s
Availability | VoID file availability check for News-100 NIF NER Corpus took 0.000629425048828125s
Completeness | Calculation of interlinking completeness for News-100 NIF NER Corpus took 0.2516365051269531s
Reputation | Calculation of the PageRank for News-100 NIF NER Corpus took 0.020274877548217773s
Interlinking | Calculation of Degree of Connection for News-100 NIF NER Corpus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for News-100 NIF NER Corpus took 0.0007848739624023438s
Interlinking | Calculation of Clustering coefficient for News-100 NIF NER Corpus took 6.914138793945312e-05s
Believability | Calculation of trust value for News-100 NIF NER Corpus took 6.67572021484375e-06s
INFO | --- Analysis for news-100-nif-ner-corpus took 4.043302297592163s
Availability | SPARQL endpoint availability check for Newsweek took 3.886222839355469e-05s
Availability | VoID file availability check for Newsweek took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for Newsweek took 0.29268312454223633s
Reputation | Calculation of the PageRank for Newsweek took 0.0202333927154541s
Interlinking | Calculation of Degree of Connection for Newsweek took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Newsweek took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Newsweek took 2.6464462280273438e-05s
Believability | Calculation of trust value for Newsweek took 6.67572021484375e-06s
INFO | --- Analysis for newsweek took 3.418349027633667s
Availability | SPARQL endpoint availability check for neXtProt took 1.5489518642425537s
Availability | VoID file availability check for neXtProt took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for neXtProt took 0.2802553176879883s
Reputation | Calculation of the PageRank for neXtProt took 0.020453453063964844s
Interlinking | Calculation of Degree of Connection for neXtProt took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for neXtProt took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for neXtProt took 3.552436828613281e-05s
Believability | Calculation of trust value for neXtProt took 6.9141387939453125e-06s
INFO | --- Analysis for nextprot took 4.688612699508667s
Availability | SPARQL endpoint availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 4.220008850097656e-05s
Availability | VoID file availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.25937557220458984s
Reputation | Calculation of the PageRank for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.02053070068359375s
Interlinking | Calculation of Degree of Connection for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.00010633468627929688s
Believability | Calculation of trust value for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 6.67572021484375e-06s
INFO | --- Analysis for nextweb-gnoss took 3.112647771835327s
Availability | SPARQL endpoint availability check for NHS Jargon RDF took 5.507469177246094e-05s
Availability | VoID file availability check for NHS Jargon RDF took 0.0006072521209716797s
Completeness | Calculation of interlinking completeness for NHS Jargon RDF took 0.25815749168395996s
Reputation | Calculation of the PageRank for NHS Jargon RDF took 0.020521879196166992s
Interlinking | Calculation of Degree of Connection for NHS Jargon RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NHS Jargon RDF took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for NHS Jargon RDF took 8.177757263183594e-05s
Believability | Calculation of trust value for NHS Jargon RDF took 5.9604644775390625e-06s
INFO | --- Analysis for nhs-jargon took 2.9431703090667725s
Availability | SPARQL endpoint availability check for NIT Patna took 4.363059997558594e-05s
Availability | VoID file availability check for NIT Patna took 0.0006656646728515625s
Completeness | Calculation of interlinking completeness for NIT Patna took 0.2714071273803711s
Reputation | Calculation of the PageRank for NIT Patna took 0.02059340476989746s
Interlinking | Calculation of Degree of Connection for NIT Patna took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for NIT Patna took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for NIT Patna took 7.82012939453125e-05s
Believability | Calculation of trust value for NIT Patna took 7.152557373046875e-06s
INFO | --- Analysis for NITP took 3.4023101329803467s
Availability | SPARQL endpoint availability check for NLM 2007 MeSH took 3.9577484130859375e-05s
Availability | VoID file availability check for NLM 2007 MeSH took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for NLM 2007 MeSH took 0.2689387798309326s
Reputation | Calculation of the PageRank for NLM 2007 MeSH took 0.020355701446533203s
Interlinking | Calculation of Degree of Connection for NLM 2007 MeSH took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NLM 2007 MeSH took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for NLM 2007 MeSH took 3.361701965332031e-05s
Believability | Calculation of trust value for NLM 2007 MeSH took 6.9141387939453125e-06s
INFO | --- Analysis for nlm_2007_mesh took 2.940203905105591s
Availability | SPARQL endpoint availability check for National Library of Russia BibCore Dataset took 4.172325134277344e-05s
Availability | VoID file availability check for National Library of Russia BibCore Dataset took 0.0005645751953125s
Completeness | Calculation of interlinking completeness for National Library of Russia BibCore Dataset took 0.24924087524414062s
Reputation | Calculation of the PageRank for National Library of Russia BibCore Dataset took 0.020509958267211914s
Interlinking | Calculation of Degree of Connection for National Library of Russia BibCore Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for National Library of Russia BibCore Dataset took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for National Library of Russia BibCore Dataset took 2.86102294921875e-05s
Believability | Calculation of trust value for National Library of Russia BibCore Dataset took 7.152557373046875e-06s
INFO | --- Analysis for nlr-dataset-mod took 4.069261789321899s
Availability | SPARQL endpoint availability check for Neulateinische Wortliste in LiLa took 0.5998654365539551s
Availability | VoID file availability check for Neulateinische Wortliste in LiLa took 0.0007030963897705078s
Completeness | Calculation of interlinking completeness for Neulateinische Wortliste in LiLa took 0.2963709831237793s
Reputation | Calculation of the PageRank for Neulateinische Wortliste in LiLa took 0.02050018310546875s
Interlinking | Calculation of Degree of Connection for Neulateinische Wortliste in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Neulateinische Wortliste in LiLa took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Neulateinische Wortliste in LiLa took 3.528594970703125e-05s
Believability | Calculation of trust value for Neulateinische Wortliste in LiLa took 5.9604644775390625e-06s
INFO | --- Analysis for NLW took 4.230816125869751s
Availability | SPARQL endpoint availability check for Nobel Prizes took 3.2525997161865234s
Availability | VoID file availability check for Nobel Prizes took 0.0007345676422119141s
Completeness | Calculation of interlinking completeness for Nobel Prizes took 0.2847442626953125s
Reputation | Calculation of the PageRank for Nobel Prizes took 0.02053236961364746s
Interlinking | Calculation of Degree of Connection for Nobel Prizes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Nobel Prizes took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Nobel Prizes took 9.036064147949219e-05s
Believability | Calculation of trust value for Nobel Prizes took 6.4373016357421875e-06s
INFO | --- Analysis for nobelprizes took 8.307827472686768s
Availability | SPARQL endpoint availability check for NoiPA took 0.35639429092407227s
Availability | VoID file availability check for NoiPA took 0.00024962425231933594s
Extra | Recovery of all triples for NoiPA took 83.67799592018127s
Performance | Total latancy measurement for NoiPA took 1.0389997959136963s
Amount of data | Number of triples check for NoiPA took 1.6971828937530518s
Interoperability | New terms check for NoiPA took 3.175142526626587s
Versatility | Languages check for NoiPA took 60.159326791763306s
Interpretability | Number of blank nodes check for NoiPA took 0.37679147720336914s
Interpretability | RDF structures check for NoiPA took 0.12720274925231934s
Versatility | Serialization formats check for NoiPA took 0.12286019325256348s
Availability | RDF dump link check for NoiPA took 0.3643815517425537s
License | MR license check for NoiPA took 0.2879502773284912s
License | HR license check for NoiPA took 60.23943614959717s
Amount of data | Number of property check for NoiPA took 0.22655892372131348s
Understandability | Number of label check for NoiPA took 0.732440710067749s
Understandability | URI regex check for NoiPA took 1.0464651584625244s
Understandability | Vocabs check for NoiPA took 0.18016839027404785s
Verifiability | Authors check for NoiPA took 0.13542723655700684s
Verifiability | Publishers check for NoiPA took 0.200364351272583s
Performance | Throughput check for NoiPA took 11.174613952636719s
Amount of data | Check the number of entities for NoiPA took 7.939338684082031e-05s
Verifiability | Contribs. check for NoiPA took 0.1553964614868164s
Interlinking | sameAs chians check for NoiPA took 0.2039201259613037s
Interlinking | skos check for NoiPA took 0.16812658309936523s
Interlinking | skos check for NoiPA took 0.10532760620117188s
Timeliness | dataset update frequency check for NoiPA took 0.13285613059997559s
Currency | Creation date check for NoiPA took 0.47131848335266113s
Currency | Modification date check for NoiPA took 0.11022281646728516s
Rep.Conc. | URIs length for NoiPA took 59.179412841796875s
Interoperability | New vocabularies check for NoiPA took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for NoiPA took 0.267747163772583s
Accuracy | Check Functional Property for NoiPA took 0.25920987129211426s
Accuracy | Check Inverse Functional Property for NoiPA took 0.3683745861053467s
Accuracy | Check Empty annotation labels for NoiPA took 27.73221492767334s
Accuracy | Check White space in annotation for NoiPA took 2.2691574096679688s
Accuracy | Check Datatype consistency for NoiPA took 1.9987199306488037s
Consistency | Disjoint class check for NoiPA took 0.20406556129455566s
Consistency | Check Misplaced properties for NoiPA took 20.989856004714966s
Consistency | Misplaced classes for NoiPA took 6.3963165283203125s
Consistency | Check Ontology hijacking for NoiPA took 28.39281988143921s
Consistency | Check Invalid usage of undefined classes for NoiPA took 1.5596845149993896s
Consistency | Check Invalid usage of undefined properties for NoiPA took 21.991114854812622s
Conciseness | Check Extensional conciseness for NoiPA took 2.1348888874053955s
Conciseness | Check Intensional conciseness for NoiPA took 0.24935102462768555s
Security | Sign check for NoiPA took 0.15464258193969727s
Availability | Check URIs Dereferenciability for NoiPA took 19.381677865982056s
Completeness | Calculation of interlinking completeness for NoiPA took 0.38955116271972656s
Reputation | Calculation of the PageRank for NoiPA took 0.020677566528320312s
Interlinking | Calculation of Degree of Connection for NoiPA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NoiPA took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for NoiPA took 4.315376281738281e-05s
Interoperability | Check the re-using of existing vocabs for NoiPA took 1.430511474609375e-06s
Believability | Calculation of trust value for NoiPA took 7.62939453125e-06s
INFO | --- Analysis for NoiPA took 584.2997932434082s
Availability | SPARQL endpoint availability check for Nomenclature for Museum Cataloging took 6.193052291870117s
Availability | VoID file availability check for Nomenclature for Museum Cataloging took 0.0007269382476806641s
Completeness | Calculation of interlinking completeness for Nomenclature for Museum Cataloging took 0.7141783237457275s
Reputation | Calculation of the PageRank for Nomenclature for Museum Cataloging took 0.02039790153503418s
Interlinking | Calculation of Degree of Connection for Nomenclature for Museum Cataloging took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Nomenclature for Museum Cataloging took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Nomenclature for Museum Cataloging took 9.036064147949219e-05s
Believability | Calculation of trust value for Nomenclature for Museum Cataloging took 7.3909759521484375e-06s
INFO | --- Analysis for nom took 27.192559480667114s
Availability | SPARQL endpoint availability check for Nomenclator Asturias took 24.03091597557068s
Availability | VoID file availability check for Nomenclator Asturias took 0.0009379386901855469s
Completeness | Calculation of interlinking completeness for Nomenclator Asturias took 0.2800745964050293s
Reputation | Calculation of the PageRank for Nomenclator Asturias took 0.020718097686767578s
Interlinking | Calculation of Degree of Connection for Nomenclator Asturias took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Nomenclator Asturias took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Nomenclator Asturias took 7.605552673339844e-05s
Believability | Calculation of trust value for Nomenclator Asturias took 4.76837158203125e-06s
INFO | --- Analysis for nomenclator-asturias took 133.76963186264038s
Availability | SPARQL endpoint availability check for nomisma took 4.0531158447265625e-05s
Availability | VoID file availability check for nomisma took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for nomisma took 0.27611374855041504s
Reputation | Calculation of the PageRank for nomisma took 0.020609378814697266s
Interlinking | Calculation of Degree of Connection for nomisma took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for nomisma took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for nomisma took 2.9802322387695312e-05s
Believability | Calculation of trust value for nomisma took 6.67572021484375e-06s
INFO | --- Analysis for nomisma took 4.7316718101501465s
Availability | SPARQL endpoint availability check for Nomisma.org  took 16.638498783111572s
Availability | VoID file availability check for Nomisma.org  took 0.0006601810455322266s
Extra | Recovery of all triples for Nomisma.org  took 407.01908111572266s
Performance | Total latancy measurement for Nomisma.org  took 1.454944372177124s
Amount of data | Number of triples check for Nomisma.org  took 61.75908589363098s
Interoperability | New terms check for Nomisma.org  took 8.326558589935303s
Versatility | Languages check for Nomisma.org  took 126.70128035545349s
Interpretability | Number of blank nodes check for Nomisma.org  took 46.452924966812134s
Security | Check HTTPS for Nomisma.org  took 0.6726078987121582s
Interpretability | RDF structures check for Nomisma.org  took 0.29822540283203125s
Versatility | Serialization formats check for Nomisma.org  took 0.29740166664123535s
Availability | RDF dump link check for Nomisma.org  took 1812.2609193325043s
License | MR license check for Nomisma.org  took 0.326326847076416s
License | HR license check for Nomisma.org  took 60.96964979171753s
Amount of data | Number of property check for Nomisma.org  took 0.327085018157959s
Understandability | Number of label check for Nomisma.org  took 13.924432277679443s
Understandability | URI regex check for Nomisma.org  took 0.6065597534179688s
Understandability | Vocabs check for Nomisma.org  took 0.29045820236206055s
Verifiability | Authors check for Nomisma.org  took 0.2828502655029297s
Verifiability | Publishers check for Nomisma.org  took 0.30943894386291504s
Performance | Throughput check for Nomisma.org  took 11.116105079650879s
Amount of data | Check the number of entities for Nomisma.org  took 61.88314771652222s
Verifiability | Contribs. check for Nomisma.org  took 0.34911012649536133s
Interlinking | sameAs chians check for Nomisma.org  took 0.31484317779541016s
Interlinking | skos check for Nomisma.org  took 1.2146332263946533s
Interlinking | skos check for Nomisma.org  took 0.4437284469604492s
Timeliness | dataset update frequency check for Nomisma.org  took 0.2869529724121094s
Currency | Creation date check for Nomisma.org  took 0.6136984825134277s
Currency | Modification date check for Nomisma.org  took 0.3187868595123291s
Rep.Conc. | URIs length for Nomisma.org  took 194.50558948516846s
Interoperability | New vocabularies check for Nomisma.org  took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Nomisma.org  took 0.3212406635284424s
Accuracy | Check Functional Property for Nomisma.org  took 0.32207512855529785s
Accuracy | Check Inverse Functional Property for Nomisma.org  took 0.2858772277832031s
Accuracy | Check Empty annotation labels for Nomisma.org  took 123.78004264831543s
Accuracy | Check White space in annotation for Nomisma.org  took 2.8335249423980713s
Accuracy | Check Datatype consistency for Nomisma.org  took 5.659326076507568s
Consistency | Disjoint class check for Nomisma.org  took 0.3259885311126709s
Consistency | Check Misplaced properties for Nomisma.org  took 26.898048162460327s
Consistency | Check Ontology hijacking for Nomisma.org  took 133.33073782920837s
Consistency | Check Invalid usage of undefined classes for Nomisma.org  took 1.9489922523498535s
Consistency | Check Invalid usage of undefined properties for Nomisma.org  took 30.157109022140503s
Conciseness | Check Extensional conciseness for Nomisma.org  took 2.772761344909668s
Conciseness | Check Intensional conciseness for Nomisma.org  took 0.4541807174682617s
Security | Sign check for Nomisma.org  took 0.3226339817047119s
Availability | Check URIs Dereferenciability for Nomisma.org  took 1716.8421478271484s
Completeness | Calculation of interlinking completeness for Nomisma.org  took 0.9904294013977051s
Reputation | Calculation of the PageRank for Nomisma.org  took 0.02196812629699707s
Interlinking | Calculation of Degree of Connection for Nomisma.org  took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Nomisma.org  took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for Nomisma.org  took 0.00014781951904296875s
Interoperability | Check the re-using of existing vocabs for Nomisma.org  took 4.0531158447265625e-06s
Believability | Calculation of trust value for Nomisma.org  took 0.0001571178436279297s
INFO | --- Analysis for nomisma_org took 10828.96372127533s
Availability | SPARQL endpoint availability check for Curriculum Vitae took 0.5018744468688965s
Availability | VoID file availability check for Curriculum Vitae took 0.0002887248992919922s
Extra | Recovery of all triples for Curriculum Vitae took 0.6982214450836182s
Performance | Total latancy measurement for Curriculum Vitae took 0.8520355224609375s
Amount of data | Number of triples check for Curriculum Vitae took 0.17102622985839844s
Interoperability | New terms check for Curriculum Vitae took 1.4638493061065674s
Versatility | Languages check for Curriculum Vitae took 0.1524355411529541s
Interpretability | Number of blank nodes check for Curriculum Vitae took 0.2449970245361328s
Interpretability | RDF structures check for Curriculum Vitae took 0.17548823356628418s
Versatility | Serialization formats check for Curriculum Vitae took 0.14878034591674805s
Availability | RDF dump link check for Curriculum Vitae took 0.14930963516235352s
License | MR license check for Curriculum Vitae took 0.1460878849029541s
License | HR license check for Curriculum Vitae took 0.15293097496032715s
Amount of data | Number of property check for Curriculum Vitae took 0.21608233451843262s
Understandability | Number of label check for Curriculum Vitae took 0.14124584197998047s
Understandability | URI regex check for Curriculum Vitae took 0.30597543716430664s
Understandability | Vocabs check for Curriculum Vitae took 0.13468050956726074s
Verifiability | Authors check for Curriculum Vitae took 0.1525278091430664s
Verifiability | Publishers check for Curriculum Vitae took 0.13396286964416504s
Amount of data | Check the number of entities for Curriculum Vitae took 7.152557373046875e-05s
Verifiability | Contribs. check for Curriculum Vitae took 0.13879632949829102s
Interlinking | sameAs chians check for Curriculum Vitae took 0.1481950283050537s
Interlinking | skos check for Curriculum Vitae took 0.8617391586303711s
Interlinking | skos check for Curriculum Vitae took 0.14504408836364746s
Timeliness | dataset update frequency check for Curriculum Vitae took 0.4463052749633789s
Currency | Creation date check for Curriculum Vitae took 0.34107303619384766s
Currency | Modification date check for Curriculum Vitae took 0.33142971992492676s
Rep.Conc. | URIs length for Curriculum Vitae took 0.363081693649292s
Interoperability | New vocabularies check for Curriculum Vitae took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Curriculum Vitae took 0.1465156078338623s
Accuracy | Check Functional Property for Curriculum Vitae took 0.14155364036560059s
Accuracy | Check Inverse Functional Property for Curriculum Vitae took 0.12698745727539062s
Accuracy | Check Empty annotation labels for Curriculum Vitae took 0.13243317604064941s
Accuracy | Check White space in annotation for Curriculum Vitae took 0.00011873245239257812s
Accuracy | Check Datatype consistency for Curriculum Vitae took 0.0033283233642578125s
Consistency | Disjoint class check for Curriculum Vitae took 0.13139629364013672s
Consistency | Check Misplaced properties for Curriculum Vitae took 0.2759065628051758s
Consistency | Check Ontology hijacking for Curriculum Vitae took 1.4638385772705078s
Consistency | Check Invalid usage of undefined classes for Curriculum Vitae took 1.3524160385131836s
Consistency | Check Invalid usage of undefined properties for Curriculum Vitae took 1.5216705799102783s
Conciseness | Check Extensional conciseness for Curriculum Vitae took 0.001209259033203125s
Security | Sign check for Curriculum Vitae took 0.1305069923400879s
Availability | Check URIs Dereferenciability for Curriculum Vitae took 18.276842832565308s
Completeness | Calculation of interlinking completeness for Curriculum Vitae took 0.289142370223999s
Reputation | Calculation of the PageRank for Curriculum Vitae took 0.020651817321777344s
Interlinking | Calculation of Degree of Connection for Curriculum Vitae took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Curriculum Vitae took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Curriculum Vitae took 4.124641418457031e-05s
Interoperability | Check the re-using of existing vocabs for Curriculum Vitae took 1.9073486328125e-06s
Believability | Calculation of trust value for Curriculum Vitae took 7.152557373046875e-06s
INFO | --- Analysis for Nordine_Bittich took 51.532944679260254s
Availability | SPARQL endpoint availability check for NorPark took 1.590719223022461s
Availability | VoID file availability check for NorPark took 0.0006282329559326172s
Completeness | Calculation of interlinking completeness for NorPark took 0.2833075523376465s
Reputation | Calculation of the PageRank for NorPark took 0.020203590393066406s
Interlinking | Calculation of Degree of Connection for NorPark took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for NorPark took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for NorPark took 4.172325134277344e-05s
Believability | Calculation of trust value for NorPark took 5.0067901611328125e-06s
INFO | --- Analysis for norpark took 5.1593968868255615s
Availability | SPARQL endpoint availability check for Parking Dataset took 0.02400994300842285s
Availability | VoID file availability check for Parking Dataset took 0.00022363662719726562s
Completeness | Calculation of interlinking completeness for Parking Dataset took 0.2914586067199707s
Reputation | Calculation of the PageRank for Parking Dataset took 0.02062535285949707s
Interlinking | Calculation of Degree of Connection for Parking Dataset took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Parking Dataset took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Parking Dataset took 4.458427429199219e-05s
Believability | Calculation of trust value for Parking Dataset took 5.9604644775390625e-06s
INFO | --- Analysis for norpark2 took 2.685988426208496s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset took 1.054380178451538s
Availability | VoID file availability check for Norway fishery stocks dataset took 0.0004086494445800781s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset took 0.27782177925109863s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset took 0.022939205169677734s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset took 0.0008213520050048828s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset took 3.4332275390625e-05s
Believability | Calculation of trust value for Norway fishery stocks dataset took 7.3909759521484375e-06s
INFO | --- Analysis for Norway_Fishery_ took 4.312274217605591s
Availability | SPARQL endpoint availability check for Norwegian geo-divisions took 0.36279988288879395s
Availability | VoID file availability check for Norwegian geo-divisions took 0.000560760498046875s
Completeness | Calculation of interlinking completeness for Norwegian geo-divisions took 0.3116164207458496s
Reputation | Calculation of the PageRank for Norwegian geo-divisions took 0.020427227020263672s
Interlinking | Calculation of Degree of Connection for Norwegian geo-divisions took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Norwegian geo-divisions took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Norwegian geo-divisions took 4.744529724121094e-05s
Believability | Calculation of trust value for Norwegian geo-divisions took 6.67572021484375e-06s
INFO | --- Analysis for norwegian-geo-divisions took 7.689175605773926s
Availability | SPARQL endpoint availability check for NorwegianSoE took 3.981590270996094e-05s
Availability | VoID file availability check for NorwegianSoE took 0.00023484230041503906s
Completeness | Calculation of interlinking completeness for NorwegianSoE took 0.28115367889404297s
Reputation | Calculation of the PageRank for NorwegianSoE took 0.02052021026611328s
Interlinking | Calculation of Degree of Connection for NorwegianSoE took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NorwegianSoE took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for NorwegianSoE took 3.0040740966796875e-05s
Believability | Calculation of trust value for NorwegianSoE took 6.67572021484375e-06s
INFO | --- Analysis for norwegiansoe took 3.24224853515625s
Availability | SPARQL endpoint availability check for NITP took 4.2438507080078125e-05s
Availability | VoID file availability check for NITP took 0.0006072521209716797s
Completeness | Calculation of interlinking completeness for NITP took 0.29782748222351074s
Reputation | Calculation of the PageRank for NITP took 0.020451784133911133s
Interlinking | Calculation of Degree of Connection for NITP took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NITP took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for NITP took 6.723403930664062e-05s
Believability | Calculation of trust value for NITP took 8.821487426757812e-06s
INFO | --- Analysis for notIdentifier took 3.4697232246398926s
Availability | SPARQL endpoint availability check for Nottingham Trent University Resource Lists took 4.315376281738281e-05s
Availability | VoID file availability check for Nottingham Trent University Resource Lists took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for Nottingham Trent University Resource Lists took 0.28354549407958984s
Reputation | Calculation of the PageRank for Nottingham Trent University Resource Lists took 0.020808696746826172s
Interlinking | Calculation of Degree of Connection for Nottingham Trent University Resource Lists took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Nottingham Trent University Resource Lists took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Nottingham Trent University Resource Lists took 3.600120544433594e-05s
Believability | Calculation of trust value for Nottingham Trent University Resource Lists took 6.4373016357421875e-06s
INFO | --- Analysis for nottingham-trent-university-resource-lists took 3.047656536102295s
Availability | SPARQL endpoint availability check for Nature Publishing Group - ALL took 5.602836608886719e-05s
Availability | VoID file availability check for Nature Publishing Group - ALL took 0.000278472900390625s
Completeness | Calculation of interlinking completeness for Nature Publishing Group - ALL took 0.28107309341430664s
Reputation | Calculation of the PageRank for Nature Publishing Group - ALL took 0.02033257484436035s
Interlinking | Calculation of Degree of Connection for Nature Publishing Group - ALL took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Nature Publishing Group - ALL took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Nature Publishing Group - ALL took 2.9802322387695312e-05s
Believability | Calculation of trust value for Nature Publishing Group - ALL took 7.152557373046875e-06s
INFO | --- Analysis for npg took 3.2272706031799316s
Availability | SPARQL endpoint availability check for NPM took 5.173683166503906e-05s
Availability | VoID file availability check for NPM took 0.0005228519439697266s
Completeness | Calculation of interlinking completeness for NPM took 0.3004772663116455s
Reputation | Calculation of the PageRank for NPM took 0.020161867141723633s
Interlinking | Calculation of Degree of Connection for NPM took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NPM took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for NPM took 3.218650817871094e-05s
Believability | Calculation of trust value for NPM took 7.3909759521484375e-06s
INFO | --- Analysis for npm took 3.5820658206939697s
Availability | SPARQL endpoint availability check for NTNU special collections took 0.05044078826904297s
Availability | VoID file availability check for NTNU special collections took 0.0005981922149658203s
Completeness | Calculation of interlinking completeness for NTNU special collections took 0.29723691940307617s
Reputation | Calculation of the PageRank for NTNU special collections took 0.020227670669555664s
Interlinking | Calculation of Degree of Connection for NTNU special collections took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NTNU special collections took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for NTNU special collections took 5.316734313964844e-05s
Believability | Calculation of trust value for NTNU special collections took 7.867813110351562e-06s
INFO | --- Analysis for ntnusc took 5.4497764110565186s
Availability | SPARQL endpoint availability check for links took 4.0531158447265625e-05s
Availability | VoID file availability check for links took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for links took 0.27680110931396484s
Reputation | Calculation of the PageRank for links took 0.020135879516601562s
Interlinking | Calculation of Degree of Connection for links took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for links took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for links took 1.0967254638671875e-05s
Believability | Calculation of trust value for links took 7.152557373046875e-06s
INFO | --- Analysis for nugmyanmar took 2.5844690799713135s
Availability | SPARQL endpoint availability check for NUTS (GeoVocab) took 4.124641418457031e-05s
Availability | VoID file availability check for NUTS (GeoVocab) took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for NUTS (GeoVocab) took 0.2845339775085449s
Reputation | Calculation of the PageRank for NUTS (GeoVocab) took 0.020478248596191406s
Interlinking | Calculation of Degree of Connection for NUTS (GeoVocab) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NUTS (GeoVocab) took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for NUTS (GeoVocab) took 0.00010514259338378906s
Believability | Calculation of trust value for NUTS (GeoVocab) took 4.5299530029296875e-06s
INFO | --- Analysis for nuts-geovocab took 2.669187068939209s
Availability | SPARQL endpoint availability check for Norsk inndeling av vitenskapsdisipliner took 0.4517941474914551s
Availability | VoID file availability check for Norsk inndeling av vitenskapsdisipliner took 0.0007159709930419922s
Completeness | Calculation of interlinking completeness for Norsk inndeling av vitenskapsdisipliner took 0.2997171878814697s
Reputation | Calculation of the PageRank for Norsk inndeling av vitenskapsdisipliner took 0.020321369171142578s
Interlinking | Calculation of Degree of Connection for Norsk inndeling av vitenskapsdisipliner took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Norsk inndeling av vitenskapsdisipliner took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Norsk inndeling av vitenskapsdisipliner took 6.580352783203125e-05s
Believability | Calculation of trust value for Norsk inndeling av vitenskapsdisipliner took 6.9141387939453125e-06s
INFO | --- Analysis for nvd took 4.286028861999512s
Availability | SPARQL endpoint availability check for NERC Vocabulary Server 2.0 took 0.8450191020965576s
Availability | VoID file availability check for NERC Vocabulary Server 2.0 took 0.0005795955657958984s
Completeness | Calculation of interlinking completeness for NERC Vocabulary Server 2.0 took 0.3952009677886963s
Reputation | Calculation of the PageRank for NERC Vocabulary Server 2.0 took 0.020162105560302734s
Interlinking | Calculation of Degree of Connection for NERC Vocabulary Server 2.0 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NERC Vocabulary Server 2.0 took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for NERC Vocabulary Server 2.0 took 7.581710815429688e-05s
Believability | Calculation of trust value for NERC Vocabulary Server 2.0 took 7.3909759521484375e-06s
INFO | --- Analysis for nvs took 10.907603740692139s
Availability | SPARQL endpoint availability check for New York Times - Linked Open Data took 4.0531158447265625e-05s
Availability | VoID file availability check for New York Times - Linked Open Data took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for New York Times - Linked Open Data took 0.2900869846343994s
Reputation | Calculation of the PageRank for New York Times - Linked Open Data took 0.02073502540588379s
Interlinking | Calculation of Degree of Connection for New York Times - Linked Open Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for New York Times - Linked Open Data took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for New York Times - Linked Open Data took 0.000186920166015625s
Believability | Calculation of trust value for New York Times - Linked Open Data took 6.67572021484375e-06s
INFO | --- Analysis for nytimes-linked-open-data took 2.749687433242798s
Availability | SPARQL endpoint availability check for American National Corpus - Open Portion took 3.9577484130859375e-05s
Availability | VoID file availability check for American National Corpus - Open Portion took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for American National Corpus - Open Portion took 0.29896116256713867s
Reputation | Calculation of the PageRank for American National Corpus - Open Portion took 0.02075505256652832s
Interlinking | Calculation of Degree of Connection for American National Corpus - Open Portion took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for American National Corpus - Open Portion took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for American National Corpus - Open Portion took 2.7418136596679688e-05s
Believability | Calculation of trust value for American National Corpus - Open Portion took 6.4373016357421875e-06s
INFO | --- Analysis for o-anc took 4.298404932022095s
Availability | SPARQL endpoint availability check for OANetzwerk took 4.124641418457031e-05s
Availability | VoID file availability check for OANetzwerk took 0.00022935867309570312s
Completeness | Calculation of interlinking completeness for OANetzwerk took 0.3039875030517578s
Reputation | Calculation of the PageRank for OANetzwerk took 0.020932435989379883s
Interlinking | Calculation of Degree of Connection for OANetzwerk took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for OANetzwerk took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for OANetzwerk took 3.24249267578125e-05s
Believability | Calculation of trust value for OANetzwerk took 6.4373016357421875e-06s
INFO | --- Analysis for oanetzwerk took 3.231579065322876s
Availability | SPARQL endpoint availability check for Obce, okresy a kraje České republiky took 3.981590270996094e-05s
Availability | VoID file availability check for Obce, okresy a kraje České republiky took 0.00022721290588378906s
Completeness | Calculation of interlinking completeness for Obce, okresy a kraje České republiky took 0.28596973419189453s
Reputation | Calculation of the PageRank for Obce, okresy a kraje České republiky took 0.02064800262451172s
Interlinking | Calculation of Degree of Connection for Obce, okresy a kraje České republiky took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Obce, okresy a kraje České republiky took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Obce, okresy a kraje České republiky took 3.0279159545898438e-05s
Believability | Calculation of trust value for Obce, okresy a kraje České republiky took 6.9141387939453125e-06s
INFO | --- Analysis for obce--okresy-a-kraje--esk--republiky took 3.1899046897888184s
Availability | SPARQL endpoint availability check for Italian Chamber of Deputies - official dataset took 0.4271574020385742s
Availability | VoID file availability check for Italian Chamber of Deputies - official dataset took 0.00033020973205566406s
Extra | Recovery of all triples for Italian Chamber of Deputies - official dataset took 1.7026329040527344s
Performance | Total latancy measurement for Italian Chamber of Deputies - official dataset took 1.529517650604248s
Amount of data | Number of triples check for Italian Chamber of Deputies - official dataset took 5.906960487365723s
Interoperability | New terms check for Italian Chamber of Deputies - official dataset took 3.7154541015625s
Versatility | Languages check for Italian Chamber of Deputies - official dataset took 60.31021046638489s
Interpretability | Number of blank nodes check for Italian Chamber of Deputies - official dataset took 3.923001289367676s
Security | Check HTTPS for Italian Chamber of Deputies - official dataset took 0.2414560317993164s
Interpretability | RDF structures check for Italian Chamber of Deputies - official dataset took 0.2573361396789551s
Versatility | Serialization formats check for Italian Chamber of Deputies - official dataset took 0.5729935169219971s
Availability | RDF dump link check for Italian Chamber of Deputies - official dataset took 0.451690673828125s
License | MR license check for Italian Chamber of Deputies - official dataset took 0.2619335651397705s
License | HR license check for Italian Chamber of Deputies - official dataset took 60.284369468688965s
Amount of data | Number of property check for Italian Chamber of Deputies - official dataset took 0.3179652690887451s
Understandability | Number of label check for Italian Chamber of Deputies - official dataset took 1.6063601970672607s
Understandability | URI regex check for Italian Chamber of Deputies - official dataset took 0.6678917407989502s
Understandability | Vocabs check for Italian Chamber of Deputies - official dataset took 0.5367224216461182s
Verifiability | Authors check for Italian Chamber of Deputies - official dataset took 0.34475255012512207s
Verifiability | Publishers check for Italian Chamber of Deputies - official dataset took 0.29320478439331055s
Performance | Throughput check for Italian Chamber of Deputies - official dataset took 12.153761625289917s
Amount of data | Check the number of entities for Italian Chamber of Deputies - official dataset took 9.369850158691406e-05s
Verifiability | Contribs. check for Italian Chamber of Deputies - official dataset took 0.3066902160644531s
Interlinking | sameAs chians check for Italian Chamber of Deputies - official dataset took 0.34392762184143066s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.340101957321167s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.3094465732574463s
Timeliness | dataset update frequency check for Italian Chamber of Deputies - official dataset took 0.47849059104919434s
Currency | Creation date check for Italian Chamber of Deputies - official dataset took 0.6713080406188965s
Currency | Modification date check for Italian Chamber of Deputies - official dataset took 0.30588579177856445s
Rep.Conc. | URIs length for Italian Chamber of Deputies - official dataset took 18.64185881614685s
Interoperability | New vocabularies check for Italian Chamber of Deputies - official dataset took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Italian Chamber of Deputies - official dataset took 0.32276034355163574s
Accuracy | Check Functional Property for Italian Chamber of Deputies - official dataset took 0.31163883209228516s
Accuracy | Check Inverse Functional Property for Italian Chamber of Deputies - official dataset took 0.31617116928100586s
Accuracy | Check Empty annotation labels for Italian Chamber of Deputies - official dataset took 1.1222236156463623s
Accuracy | Check White space in annotation for Italian Chamber of Deputies - official dataset took 0.03128170967102051s
Accuracy | Check Datatype consistency for Italian Chamber of Deputies - official dataset took 0.029497861862182617s
Consistency | Disjoint class check for Italian Chamber of Deputies - official dataset took 0.2892911434173584s
Consistency | Check Misplaced properties for Italian Chamber of Deputies - official dataset took 13.944181203842163s
Consistency | Misplaced classes for Italian Chamber of Deputies - official dataset took 0.41582155227661133s
Consistency | Check Ontology hijacking for Italian Chamber of Deputies - official dataset took 2.4801697731018066s
Consistency | Check Invalid usage of undefined classes for Italian Chamber of Deputies - official dataset took 1.1679527759552002s
Consistency | Check Invalid usage of undefined properties for Italian Chamber of Deputies - official dataset took 14.660245180130005s
Conciseness | Check Extensional conciseness for Italian Chamber of Deputies - official dataset took 0.03374457359313965s
Conciseness | Check Intensional conciseness for Italian Chamber of Deputies - official dataset took 0.37078857421875s
Security | Sign check for Italian Chamber of Deputies - official dataset took 0.25943517684936523s
Availability | Check URIs Dereferenciability for Italian Chamber of Deputies - official dataset took 19.583868265151978s
Completeness | Calculation of interlinking completeness for Italian Chamber of Deputies - official dataset took 21.057491302490234s
Reputation | Calculation of the PageRank for Italian Chamber of Deputies - official dataset took 0.02034759521484375s
Interlinking | Calculation of Degree of Connection for Italian Chamber of Deputies - official dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Italian Chamber of Deputies - official dataset took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Italian Chamber of Deputies - official dataset took 0.0001068115234375s
Interoperability | Check the re-using of existing vocabs for Italian Chamber of Deputies - official dataset took 1.1920928955078125e-06s
Believability | Calculation of trust value for Italian Chamber of Deputies - official dataset took 8.58306884765625e-06s
INFO | --- Analysis for ocd took 463.97225427627563s
Availability | SPARQL endpoint availability check for oceandrilling-borehole took 5.7220458984375e-05s
Availability | VoID file availability check for oceandrilling-borehole took 0.0007460117340087891s
Completeness | Calculation of interlinking completeness for oceandrilling-borehole took 0.3352928161621094s
Reputation | Calculation of the PageRank for oceandrilling-borehole took 0.020041227340698242s
Interlinking | Calculation of Degree of Connection for oceandrilling-borehole took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for oceandrilling-borehole took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for oceandrilling-borehole took 3.814697265625e-05s
Believability | Calculation of trust value for oceandrilling-borehole took 7.3909759521484375e-06s
INFO | --- Analysis for oceandrilling-borehole took 4.504611492156982s
Availability | SPARQL endpoint availability check for Ocean Drilling - Codices took 1.5539534091949463s
Availability | VoID file availability check for Ocean Drilling - Codices took 0.0006625652313232422s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Codices took 0.301769495010376s
Reputation | Calculation of the PageRank for Ocean Drilling - Codices took 0.02089381217956543s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Codices took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Codices took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Codices took 8.249282836914062e-05s
Believability | Calculation of trust value for Ocean Drilling - Codices took 7.3909759521484375e-06s
INFO | --- Analysis for oceandrilling-codices took 8.661146640777588s
Availability | SPARQL endpoint availability check for Ocean Drilling - dbSEABED took 1.3339684009552002s
Availability | VoID file availability check for Ocean Drilling - dbSEABED took 0.0006222724914550781s
Completeness | Calculation of interlinking completeness for Ocean Drilling - dbSEABED took 0.30566835403442383s
Reputation | Calculation of the PageRank for Ocean Drilling - dbSEABED took 0.021270036697387695s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - dbSEABED took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - dbSEABED took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - dbSEABED took 3.743171691894531e-05s
Believability | Calculation of trust value for Ocean Drilling - dbSEABED took 8.106231689453125e-06s
INFO | --- Analysis for oceandrilling-dbseabed took 7.359293460845947s
Availability | SPARQL endpoint availability check for Ocean Drilling - Forams took 1.332465410232544s
Availability | VoID file availability check for Ocean Drilling - Forams took 0.0007021427154541016s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Forams took 0.2960476875305176s
Reputation | Calculation of the PageRank for Ocean Drilling - Forams took 0.020811080932617188s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Forams took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Forams took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Forams took 3.457069396972656e-05s
Believability | Calculation of trust value for Ocean Drilling - Forams took 7.3909759521484375e-06s
INFO | --- Analysis for oceandrilling-forams took 6.386556386947632s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus LOD took 1.4295408725738525s
Availability | VoID file availability check for Ocean Drilling - Janus LOD took 0.0006453990936279297s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus LOD took 0.29877567291259766s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus LOD took 0.03282880783081055s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus LOD took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus LOD took 0.0016353130340576172s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus LOD took 5.793571472167969e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus LOD took 6.67572021484375e-06s
INFO | --- Analysis for oceandrilling-janus took 6.49344801902771s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus Age Models took 11.56654167175293s
Availability | VoID file availability check for Ocean Drilling - Janus Age Models took 0.00028061866760253906s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus Age Models took 77.57665753364563s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus Age Models took 0.020599842071533203s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus Age Models took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus Age Models took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus Age Models took 3.886222839355469e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus Age Models took 7.152557373046875e-06s
INFO | --- Analysis for oceandrilling-janusamp took 119.8550534248352s
Availability | SPARQL endpoint availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.4820432662963867s
Availability | VoID file availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.000335693359375s
Completeness | Calculation of interlinking completeness for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.3191506862640381s
Reputation | Calculation of the PageRank for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.02042841911315918s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 3.147125244140625e-05s
Believability | Calculation of trust value for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 6.67572021484375e-06s
INFO | --- Analysis for oceandrilling-ldeo took 7.404377222061157s
Availability | SPARQL endpoint availability check for Faceted Application of Subject Terminology took 4.172325134277344e-05s
Availability | VoID file availability check for Faceted Application of Subject Terminology took 0.0006563663482666016s
Completeness | Calculation of interlinking completeness for Faceted Application of Subject Terminology took 0.3620748519897461s
Reputation | Calculation of the PageRank for Faceted Application of Subject Terminology took 0.02066802978515625s
Interlinking | Calculation of Degree of Connection for Faceted Application of Subject Terminology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Faceted Application of Subject Terminology took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Faceted Application of Subject Terminology took 5.817413330078125e-05s
Believability | Calculation of trust value for Faceted Application of Subject Terminology took 6.4373016357421875e-06s
INFO | --- Analysis for oclc-fast took 9.366218090057373s
Availability | SPARQL endpoint availability check for Open Data Communities took 4.863739013671875e-05s
Availability | VoID file availability check for Open Data Communities took 0.0002346038818359375s
Completeness | Calculation of interlinking completeness for Open Data Communities took 0.3063783645629883s
Reputation | Calculation of the PageRank for Open Data Communities took 0.020693302154541016s
Interlinking | Calculation of Degree of Connection for Open Data Communities took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Data Communities took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Open Data Communities took 3.0994415283203125e-05s
Believability | Calculation of trust value for Open Data Communities took 5.7220458984375e-06s
INFO | --- Analysis for odc took 4.3730127811431885s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 4.220008850097656e-05s
Availability | VoID file availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0006461143493652344s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.31022095680236816s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.020297527313232422s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 2.956390380859375e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 5.9604644775390625e-06s
INFO | --- Analysis for odc-imd-environment-score took 4.046196699142456s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation Ranking, 2007 took 4.00543212890625e-05s
Availability | VoID file availability check for Index of Multiple Deprivation Ranking, 2007 took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation Ranking, 2007 took 0.3163621425628662s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation Ranking, 2007 took 0.02023458480834961s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation Ranking, 2007 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation Ranking, 2007 took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation Ranking, 2007 took 2.8371810913085938e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation Ranking, 2007 took 6.4373016357421875e-06s
INFO | --- Analysis for odc-imd-rank-2007 took 3.31683349609375s
Availability | SPARQL endpoint availability check for Open Data Communities - Lower layer Super Output Areas took 0.30211544036865234s
Availability | VoID file availability check for Open Data Communities - Lower layer Super Output Areas took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for Open Data Communities - Lower layer Super Output Areas took 0.3314807415008545s
Reputation | Calculation of the PageRank for Open Data Communities - Lower layer Super Output Areas took 0.020626068115234375s
Interlinking | Calculation of Degree of Connection for Open Data Communities - Lower layer Super Output Areas took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Open Data Communities - Lower layer Super Output Areas took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Open Data Communities - Lower layer Super Output Areas took 3.62396240234375e-05s
Believability | Calculation of trust value for Open Data Communities - Lower layer Super Output Areas took 5.0067901611328125e-06s
INFO | --- Analysis for odc-lsoa took 4.167472839355469s
Availability | SPARQL endpoint availability check for Estimated mid-year population 2005 took 4.935264587402344e-05s
Availability | VoID file availability check for Estimated mid-year population 2005 took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for Estimated mid-year population 2005 took 0.28150033950805664s
Reputation | Calculation of the PageRank for Estimated mid-year population 2005 took 0.020277738571166992s
Interlinking | Calculation of Degree of Connection for Estimated mid-year population 2005 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Estimated mid-year population 2005 took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Estimated mid-year population 2005 took 2.8133392333984375e-05s
Believability | Calculation of trust value for Estimated mid-year population 2005 took 7.867813110351562e-06s
INFO | --- Analysis for odc-population-2005 took 3.187753200531006s
Availability | SPARQL endpoint availability check for Open Discovery Space (ODS) took 3.981590270996094e-05s
Availability | VoID file availability check for Open Discovery Space (ODS) took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for Open Discovery Space (ODS) took 0.2974097728729248s
Reputation | Calculation of the PageRank for Open Discovery Space (ODS) took 0.02048468589782715s
Interlinking | Calculation of Degree of Connection for Open Discovery Space (ODS) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Open Discovery Space (ODS) took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Open Discovery Space (ODS) took 2.9087066650390625e-05s
Believability | Calculation of trust value for Open Discovery Space (ODS) took 6.67572021484375e-06s
INFO | --- Analysis for ods took 4.323923110961914s
Availability | SPARQL endpoint availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.736257791519165s
Availability | VoID file availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.30496716499328613s
Reputation | Calculation of the PageRank for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.020133256912231445s
Interlinking | Calculation of Degree of Connection for Organisation for Economic Co-operation and Development (OECD) Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Organisation for Economic Co-operation and Development (OECD) Linked Data took 9.298324584960938e-05s
Believability | Calculation of trust value for Organisation for Economic Co-operation and Development (OECD) Linked Data took 3.814697265625e-06s
INFO | --- Analysis for oecd-linked-data took 3.49257755279541s
Availability | SPARQL endpoint availability check for Offener Haushalt took 4.076957702636719e-05s
Availability | VoID file availability check for Offener Haushalt took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for Offener Haushalt took 0.320659875869751s
Reputation | Calculation of the PageRank for Offener Haushalt took 0.020560026168823242s
Interlinking | Calculation of Degree of Connection for Offener Haushalt took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Offener Haushalt took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Offener Haushalt took 3.0279159545898438e-05s
Believability | Calculation of trust value for Offener Haushalt took 7.152557373046875e-06s
INFO | --- Analysis for offener-haushalt took 3.317553758621216s
Availability | SPARQL endpoint availability check for Orthology and Diseases Information - OGO took 30.1121244430542s
Availability | VoID file availability check for Orthology and Diseases Information - OGO took 0.0007255077362060547s
Completeness | Calculation of interlinking completeness for Orthology and Diseases Information - OGO took 0.2922797203063965s
Reputation | Calculation of the PageRank for Orthology and Diseases Information - OGO took 0.020573854446411133s
Interlinking | Calculation of Degree of Connection for Orthology and Diseases Information - OGO took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Orthology and Diseases Information - OGO took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Orthology and Diseases Information - OGO took 5.888938903808594e-05s
Believability | Calculation of trust value for Orthology and Diseases Information - OGO took 5.7220458984375e-06s
INFO | --- Analysis for ogolod took 102.81019043922424s
Availability | SPARQL endpoint availability check for OLAC Metadata took 4.2438507080078125e-05s
Availability | VoID file availability check for OLAC Metadata took 0.0006442070007324219s
Completeness | Calculation of interlinking completeness for OLAC Metadata took 0.29054927825927734s
Reputation | Calculation of the PageRank for OLAC Metadata took 0.020483016967773438s
Interlinking | Calculation of Degree of Connection for OLAC Metadata took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OLAC Metadata took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for OLAC Metadata took 3.647804260253906e-05s
Believability | Calculation of trust value for OLAC Metadata took 5.9604644775390625e-06s
INFO | --- Analysis for olac took 34.79392457008362s
Availability | SPARQL endpoint availability check for OLiA took 6.67572021484375e-05s
Availability | VoID file availability check for OLiA took 0.0008080005645751953s
Completeness | Calculation of interlinking completeness for OLiA took 0.28571057319641113s
Reputation | Calculation of the PageRank for OLiA took 0.02045273780822754s
Interlinking | Calculation of Degree of Connection for OLiA took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for OLiA took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for OLiA took 0.00012946128845214844s
Believability | Calculation of trust value for OLiA took 6.67572021484375e-06s
INFO | --- Analysis for olia took 11.801264524459839s
Availability | SPARQL endpoint availability check for OLiA Discourse took 4.267692565917969e-05s
Availability | VoID file availability check for OLiA Discourse took 0.00037670135498046875s
Completeness | Calculation of interlinking completeness for OLiA Discourse took 0.3048582077026367s
Reputation | Calculation of the PageRank for OLiA Discourse took 0.02041029930114746s
Interlinking | Calculation of Degree of Connection for OLiA Discourse took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OLiA Discourse took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for OLiA Discourse took 3.790855407714844e-05s
Believability | Calculation of trust value for OLiA Discourse took 5.9604644775390625e-06s
INFO | --- Analysis for olia-discourse took 7.301624298095703s
Availability | SPARQL endpoint availability check for Open Land Use took 1.1574041843414307s
Availability | VoID file availability check for Open Land Use took 0.00023174285888671875s
Completeness | Calculation of interlinking completeness for Open Land Use took 0.33988332748413086s
Reputation | Calculation of the PageRank for Open Land Use took 0.02056145668029785s
Interlinking | Calculation of Degree of Connection for Open Land Use took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Land Use took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Open Land Use took 2.9087066650390625e-05s
Believability | Calculation of trust value for Open Land Use took 5.9604644775390625e-06s
INFO | --- Analysis for OLU took 4.444979190826416s
Availability | SPARQL endpoint availability check for OmegaWiki took 4.029273986816406e-05s
Availability | VoID file availability check for OmegaWiki took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for OmegaWiki took 0.28355884552001953s
Reputation | Calculation of the PageRank for OmegaWiki took 0.020194530487060547s
Interlinking | Calculation of Degree of Connection for OmegaWiki took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OmegaWiki took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for OmegaWiki took 2.8848648071289062e-05s
Believability | Calculation of trust value for OmegaWiki took 5.9604644775390625e-06s
INFO | --- Analysis for omegawiki took 3.232182502746582s
Availability | SPARQL endpoint availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 1.0999817848205566s
Availability | VoID file availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.00021696090698242188s
Completeness | Calculation of interlinking completeness for Albanet WordNet (as part of Open Multilingual WordNet) took 0.2818880081176758s
Reputation | Calculation of the PageRank for Albanet WordNet (as part of Open Multilingual WordNet) took 0.02075052261352539s
Interlinking | Calculation of Degree of Connection for Albanet WordNet (as part of Open Multilingual WordNet) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0008215904235839844s
Interlinking | Calculation of Clustering coefficient for Albanet WordNet (as part of Open Multilingual WordNet) took 4.38690185546875e-05s
Believability | Calculation of trust value for Albanet WordNet (as part of Open Multilingual WordNet) took 8.821487426757812e-06s
INFO | --- Analysis for omwn-als took 4.1732261180877686s
Availability | SPARQL endpoint availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.26528263092041016s
Availability | VoID file availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for Arabic WordNet (as part of Open Multilingual WordNet) took 0.29924964904785156s
Reputation | Calculation of the PageRank for Arabic WordNet (as part of Open Multilingual WordNet) took 0.02061772346496582s
Interlinking | Calculation of Degree of Connection for Arabic WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for Arabic WordNet (as part of Open Multilingual WordNet) took 3.886222839355469e-05s
Believability | Calculation of trust value for Arabic WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-arb took 3.3283259868621826s
Availability | SPARQL endpoint availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.25761938095092773s
Availability | VoID file availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.287334680557251s
Reputation | Calculation of the PageRank for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.020231008529663086s
Interlinking | Calculation of Degree of Connection for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 3.6716461181640625e-05s
Believability | Calculation of trust value for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 6.198883056640625e-06s
INFO | --- Analysis for omwn-bul took 3.7478816509246826s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2435898780822754s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0004439353942871094s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.29181933403015137s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.02023029327392578s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0008039474487304688s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.5762786865234375e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 5.4836273193359375e-06s
INFO | --- Analysis for omwn-cow took 3.241359233856201s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.24873661994934082s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2971796989440918s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.02062058448791504s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.5762786865234375e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-cwn took 3.2272403240203857s
Availability | SPARQL endpoint availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.24518704414367676s
Availability | VoID file availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for DanNet WordNet (as part of Open Multilingual WordNet) took 0.27960753440856934s
Reputation | Calculation of the PageRank for DanNet WordNet (as part of Open Multilingual WordNet) took 0.020231008529663086s
Interlinking | Calculation of Degree of Connection for DanNet WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for DanNet WordNet (as part of Open Multilingual WordNet) took 3.5762786865234375e-05s
Believability | Calculation of trust value for DanNet WordNet (as part of Open Multilingual WordNet) took 6.67572021484375e-06s
INFO | --- Analysis for omwn-dan took 3.193999767303467s
Availability | SPARQL endpoint availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.2561650276184082s
Availability | VoID file availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.00023102760314941406s
Completeness | Calculation of interlinking completeness for Greek WordNet (as part of Open Multilingual WordNet) took 0.2913532257080078s
Reputation | Calculation of the PageRank for Greek WordNet (as part of Open Multilingual WordNet) took 0.020393848419189453s
Interlinking | Calculation of Degree of Connection for Greek WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Greek WordNet (as part of Open Multilingual WordNet) took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Greek WordNet (as part of Open Multilingual WordNet) took 3.5762786865234375e-05s
Believability | Calculation of trust value for Greek WordNet (as part of Open Multilingual WordNet) took 6.67572021484375e-06s
INFO | --- Analysis for omwn-ell took 3.264768362045288s
Availability | SPARQL endpoint availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.24164628982543945s
Availability | VoID file availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0005290508270263672s
Completeness | Calculation of interlinking completeness for Princeton WordNet (as part of Open Multilingual WordNet) took 0.27960634231567383s
Reputation | Calculation of the PageRank for Princeton WordNet (as part of Open Multilingual WordNet) took 0.02027297019958496s
Interlinking | Calculation of Degree of Connection for Princeton WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Princeton WordNet (as part of Open Multilingual WordNet) took 3.5762786865234375e-05s
Believability | Calculation of trust value for Princeton WordNet (as part of Open Multilingual WordNet) took 6.198883056640625e-06s
INFO | --- Analysis for omwn-eng took 3.1889102458953857s
Availability | SPARQL endpoint availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.24280619621276855s
Availability | VoID file availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.00035119056701660156s
Completeness | Calculation of interlinking completeness for Persian WordNet (as part of Open Multilingual WordNet) took 0.2832760810852051s
Reputation | Calculation of the PageRank for Persian WordNet (as part of Open Multilingual WordNet) took 0.02030634880065918s
Interlinking | Calculation of Degree of Connection for Persian WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Persian WordNet (as part of Open Multilingual WordNet) took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Persian WordNet (as part of Open Multilingual WordNet) took 3.5762786865234375e-05s
Believability | Calculation of trust value for Persian WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-fas took 3.2674288749694824s
Availability | SPARQL endpoint availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.26206278800964355s
Availability | VoID file availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0003552436828613281s
Completeness | Calculation of interlinking completeness for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.30568432807922363s
Reputation | Calculation of the PageRank for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0208132266998291s
Interlinking | Calculation of Degree of Connection for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 4.029273986816406e-05s
Believability | Calculation of trust value for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-fin took 3.308654546737671s
Availability | SPARQL endpoint availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.24664664268493652s
Availability | VoID file availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for WOLF WordNet (as part of Open Multilingual WordNet) took 0.2884955406188965s
Reputation | Calculation of the PageRank for WOLF WordNet (as part of Open Multilingual WordNet) took 0.02034282684326172s
Interlinking | Calculation of Degree of Connection for WOLF WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for WOLF WordNet (as part of Open Multilingual WordNet) took 3.814697265625e-05s
Believability | Calculation of trust value for WOLF WordNet (as part of Open Multilingual WordNet) took 6.67572021484375e-06s
INFO | --- Analysis for omwn-fra took 3.270009756088257s
Availability | SPARQL endpoint availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.24702119827270508s
Availability | VoID file availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0004611015319824219s
Completeness | Calculation of interlinking completeness for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.2802150249481201s
Reputation | Calculation of the PageRank for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.020547866821289062s
Interlinking | Calculation of Degree of Connection for Hebrew WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Hebrew WordNet (as part of Open Multilingual WordNet) took 3.528594970703125e-05s
Believability | Calculation of trust value for Hebrew WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-heb took 3.231889009475708s
Availability | SPARQL endpoint availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.24367046356201172s
Availability | VoID file availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for Croatian WordNet (as part of Open Multilingual WordNet) took 0.28462743759155273s
Reputation | Calculation of the PageRank for Croatian WordNet (as part of Open Multilingual WordNet) took 0.020457983016967773s
Interlinking | Calculation of Degree of Connection for Croatian WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Croatian WordNet (as part of Open Multilingual WordNet) took 3.647804260253906e-05s
Believability | Calculation of trust value for Croatian WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-hrv took 3.2992355823516846s
Availability | SPARQL endpoint availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.2493908405303955s
Availability | VoID file availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0002257823944091797s
Completeness | Calculation of interlinking completeness for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.2971029281616211s
Reputation | Calculation of the PageRank for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.020663022994995117s
Interlinking | Calculation of Degree of Connection for IceWordNet WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for IceWordNet WordNet (as part of Open Multilingual WordNet) took 3.62396240234375e-05s
Believability | Calculation of trust value for IceWordNet WordNet (as part of Open Multilingual WordNet) took 6.198883056640625e-06s
INFO | --- Analysis for omwn-isl took 3.21506667137146s
Availability | SPARQL endpoint availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.2483069896697998s
Availability | VoID file availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.3174247741699219s
Reputation | Calculation of the PageRank for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.020714521408081055s
Interlinking | Calculation of Degree of Connection for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 3.814697265625e-05s
Believability | Calculation of trust value for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 6.198883056640625e-06s
INFO | --- Analysis for omwn-ita took 3.237874746322632s
Availability | SPARQL endpoint availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.24690794944763184s
Availability | VoID file availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.000457763671875s
Completeness | Calculation of interlinking completeness for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.30277228355407715s
Reputation | Calculation of the PageRank for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.02042555809020996s
Interlinking | Calculation of Degree of Connection for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 4.172325134277344e-05s
Believability | Calculation of trust value for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 7.867813110351562e-06s
INFO | --- Analysis for omwn-iwn took 3.2931411266326904s
Availability | SPARQL endpoint availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.2538485527038574s
Availability | VoID file availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0005707740783691406s
Completeness | Calculation of interlinking completeness for Japanese WordNet (as part of Open Multilingual WordNet) took 0.30130982398986816s
Reputation | Calculation of the PageRank for Japanese WordNet (as part of Open Multilingual WordNet) took 0.02059173583984375s
Interlinking | Calculation of Degree of Connection for Japanese WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Japanese WordNet (as part of Open Multilingual WordNet) took 4.220008850097656e-05s
Believability | Calculation of trust value for Japanese WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-jpn took 3.320441722869873s
Availability | SPARQL endpoint availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.23943305015563965s
Availability | VoID file availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.2896134853363037s
Reputation | Calculation of the PageRank for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.02045917510986328s
Interlinking | Calculation of Degree of Connection for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Multilingual Central Repository (as part of Open Multilingual WordNet) took 3.9577484130859375e-05s
Believability | Calculation of trust value for Multilingual Central Repository (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-mcr took 3.240435838699341s
Availability | SPARQL endpoint availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.2536129951477051s
Availability | VoID file availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.29488539695739746s
Reputation | Calculation of the PageRank for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.020339250564575195s
Interlinking | Calculation of Degree of Connection for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Wordnet WordNet (as part of Open Multilingual WordNet) took 3.719329833984375e-05s
Believability | Calculation of trust value for Wordnet WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-msa took 3.251569986343384s
Availability | SPARQL endpoint availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.24868011474609375s
Availability | VoID file availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for Open WordNet (as part of Open Multilingual WordNet) took 0.30951523780822754s
Reputation | Calculation of the PageRank for Open WordNet (as part of Open Multilingual WordNet) took 0.020525455474853516s
Interlinking | Calculation of Degree of Connection for Open WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open WordNet (as part of Open Multilingual WordNet) took 0.0007951259613037109s
Interlinking | Calculation of Clustering coefficient for Open WordNet (as part of Open Multilingual WordNet) took 3.719329833984375e-05s
Believability | Calculation of trust value for Open WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-nld took 3.260162353515625s
Availability | SPARQL endpoint availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.2419421672821045s
Availability | VoID file availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0006816387176513672s
Completeness | Calculation of interlinking completeness for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.30333566665649414s
Reputation | Calculation of the PageRank for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.020260095596313477s
Interlinking | Calculation of Degree of Connection for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Norwegian WordNet (as part of Open Multilingual WordNet) took 3.8623809814453125e-05s
Believability | Calculation of trust value for Norwegian WordNet (as part of Open Multilingual WordNet) took 5.7220458984375e-06s
INFO | --- Analysis for omwn-nor took 3.2381863594055176s
Availability | SPARQL endpoint availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.26056742668151855s
Availability | VoID file availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.29924488067626953s
Reputation | Calculation of the PageRank for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.020687580108642578s
Interlinking | Calculation of Degree of Connection for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for plWordNet WordNet (as part of Open Multilingual WordNet) took 3.695487976074219e-05s
Believability | Calculation of trust value for plWordNet WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-pol took 3.271824359893799s
Availability | SPARQL endpoint availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.2611258029937744s
Availability | VoID file availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.3626282215118408s
Reputation | Calculation of the PageRank for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.02071666717529297s
Interlinking | Calculation of Degree of Connection for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 3.790855407714844e-05s
Believability | Calculation of trust value for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-por took 3.3297500610351562s
Availability | SPARQL endpoint availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.2524449825286865s
Availability | VoID file availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.00044798851013183594s
Completeness | Calculation of interlinking completeness for Romanian WordNet (as part of Open Multilingual WordNet) took 0.290102481842041s
Reputation | Calculation of the PageRank for Romanian WordNet (as part of Open Multilingual WordNet) took 0.020171165466308594s
Interlinking | Calculation of Degree of Connection for Romanian WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0008339881896972656s
Interlinking | Calculation of Clustering coefficient for Romanian WordNet (as part of Open Multilingual WordNet) took 3.886222839355469e-05s
Believability | Calculation of trust value for Romanian WordNet (as part of Open Multilingual WordNet) took 5.9604644775390625e-06s
INFO | --- Analysis for omwn-ron took 3.2354860305786133s
Availability | SPARQL endpoint availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.24574494361877441s
Availability | VoID file availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0004611015319824219s
Completeness | Calculation of interlinking completeness for Slovak WordNet (as part of Open Multilingual WordNet) took 0.2916584014892578s
Reputation | Calculation of the PageRank for Slovak WordNet (as part of Open Multilingual WordNet) took 0.02044224739074707s
Interlinking | Calculation of Degree of Connection for Slovak WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Slovak WordNet (as part of Open Multilingual WordNet) took 3.695487976074219e-05s
Believability | Calculation of trust value for Slovak WordNet (as part of Open Multilingual WordNet) took 6.198883056640625e-06s
INFO | --- Analysis for omwn-slk took 3.217623472213745s
Availability | SPARQL endpoint availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.24280238151550293s
Availability | VoID file availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.28541088104248047s
Reputation | Calculation of the PageRank for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.020300865173339844s
Interlinking | Calculation of Degree of Connection for sloWNet WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for sloWNet WordNet (as part of Open Multilingual WordNet) took 3.504753112792969e-05s
Believability | Calculation of trust value for sloWNet WordNet (as part of Open Multilingual WordNet) took 6.67572021484375e-06s
INFO | --- Analysis for omwn-slv took 3.1753365993499756s
Availability | SPARQL endpoint availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.2421884536743164s
Availability | VoID file availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0002276897430419922s
Completeness | Calculation of interlinking completeness for Swedish WordNet (as part of Open Multilingual WordNet) took 0.276508092880249s
Reputation | Calculation of the PageRank for Swedish WordNet (as part of Open Multilingual WordNet) took 0.020376920700073242s
Interlinking | Calculation of Degree of Connection for Swedish WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Swedish WordNet (as part of Open Multilingual WordNet) took 3.62396240234375e-05s
Believability | Calculation of trust value for Swedish WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-swe took 3.3005359172821045s
Availability | SPARQL endpoint availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.23586606979370117s
Availability | VoID file availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.0002276897430419922s
Completeness | Calculation of interlinking completeness for Thai WordNet (as part of Open Multilingual WordNet) took 0.2905454635620117s
Reputation | Calculation of the PageRank for Thai WordNet (as part of Open Multilingual WordNet) took 0.020292282104492188s
Interlinking | Calculation of Degree of Connection for Thai WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Thai WordNet (as part of Open Multilingual WordNet) took 0.0007784366607666016s
Interlinking | Calculation of Clustering coefficient for Thai WordNet (as part of Open Multilingual WordNet) took 3.6716461181640625e-05s
Believability | Calculation of trust value for Thai WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-tha took 3.2029342651367188s
Availability | SPARQL endpoint availability check for OntoBeef Domain took 4.790223836898804s
Availability | VoID file availability check for OntoBeef Domain took 0.0006129741668701172s
Completeness | Calculation of interlinking completeness for OntoBeef Domain took 0.29648494720458984s
Reputation | Calculation of the PageRank for OntoBeef Domain took 0.02051377296447754s
Interlinking | Calculation of Degree of Connection for OntoBeef Domain took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OntoBeef Domain took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for OntoBeef Domain took 4.1484832763671875e-05s
Believability | Calculation of trust value for OntoBeef Domain took 6.4373016357421875e-06s
INFO | --- Analysis for ontobeef-domain took 32.76073217391968s
Availability | SPARQL endpoint availability check for Ontos News Portal took 4.2438507080078125e-05s
Availability | VoID file availability check for Ontos News Portal took 0.0009021759033203125s
Completeness | Calculation of interlinking completeness for Ontos News Portal took 0.28394126892089844s
Reputation | Calculation of the PageRank for Ontos News Portal took 0.020360946655273438s
Interlinking | Calculation of Degree of Connection for Ontos News Portal took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontos News Portal took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Ontos News Portal took 0.00010251998901367188s
Believability | Calculation of trust value for Ontos News Portal took 5.245208740234375e-06s
INFO | --- Analysis for ontos-news-portal took 42.63650894165039s
Availability | SPARQL endpoint availability check for Ookaboo RDF dump took 4.220008850097656e-05s
Availability | VoID file availability check for Ookaboo RDF dump took 0.0007660388946533203s
Completeness | Calculation of interlinking completeness for Ookaboo RDF dump took 0.31472277641296387s
Reputation | Calculation of the PageRank for Ookaboo RDF dump took 0.02068638801574707s
Interlinking | Calculation of Degree of Connection for Ookaboo RDF dump took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ookaboo RDF dump took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Ookaboo RDF dump took 3.075599670410156e-05s
Believability | Calculation of trust value for Ookaboo RDF dump took 7.867813110351562e-06s
INFO | --- Analysis for ookaboo-rdf-dump took 2.8510735034942627s
Availability | SPARQL endpoint availability check for Open Bantu isiXhosa Lexicon took 4.1961669921875e-05s
Availability | VoID file availability check for Open Bantu isiXhosa Lexicon took 0.0006856918334960938s
Completeness | Calculation of interlinking completeness for Open Bantu isiXhosa Lexicon took 0.29920077323913574s
Reputation | Calculation of the PageRank for Open Bantu isiXhosa Lexicon took 0.020464658737182617s
Interlinking | Calculation of Degree of Connection for Open Bantu isiXhosa Lexicon took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Bantu isiXhosa Lexicon took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Open Bantu isiXhosa Lexicon took 4.267692565917969e-05s
Believability | Calculation of trust value for Open Bantu isiXhosa Lexicon took 7.152557373046875e-06s
INFO | --- Analysis for open-bantu-isixhosa-lexicon took 6.365085601806641s
Availability | SPARQL endpoint availability check for Open Courseware Consortium metadata in RDF took 4.076957702636719e-05s
Availability | VoID file availability check for Open Courseware Consortium metadata in RDF took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for Open Courseware Consortium metadata in RDF took 0.2813420295715332s
Reputation | Calculation of the PageRank for Open Courseware Consortium metadata in RDF took 0.020267963409423828s
Interlinking | Calculation of Degree of Connection for Open Courseware Consortium metadata in RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Courseware Consortium metadata in RDF took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Open Courseware Consortium metadata in RDF took 2.765655517578125e-05s
Believability | Calculation of trust value for Open Courseware Consortium metadata in RDF took 6.198883056640625e-06s
INFO | --- Analysis for open-courseware-consortium-metadata-in-rdf took 3.227665424346924s
Availability | SPARQL endpoint availability check for Open Data Euskadi took 4.029273986816406e-05s
Availability | VoID file availability check for Open Data Euskadi took 0.0007507801055908203s
Completeness | Calculation of interlinking completeness for Open Data Euskadi took 0.28569936752319336s
Reputation | Calculation of the PageRank for Open Data Euskadi took 0.02040839195251465s
Interlinking | Calculation of Degree of Connection for Open Data Euskadi took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Open Data Euskadi took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Open Data Euskadi took 4.57763671875e-05s
Believability | Calculation of trust value for Open Data Euskadi took 4.291534423828125e-06s
INFO | --- Analysis for open-data-euskadi took 9.526700019836426s
Availability | SPARQL endpoint availability check for Open Data RISP, the Spanish Open Data community took 4.172325134277344e-05s
Availability | VoID file availability check for Open Data RISP, the Spanish Open Data community took 0.0005469322204589844s
Completeness | Calculation of interlinking completeness for Open Data RISP, the Spanish Open Data community took 0.30230259895324707s
Reputation | Calculation of the PageRank for Open Data RISP, the Spanish Open Data community took 0.020313024520874023s
Interlinking | Calculation of Degree of Connection for Open Data RISP, the Spanish Open Data community took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Data RISP, the Spanish Open Data community took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Open Data RISP, the Spanish Open Data community took 0.00010347366333007812s
Believability | Calculation of trust value for Open Data RISP, the Spanish Open Data community took 7.152557373046875e-06s
INFO | --- Analysis for open-data-risp took 3.380030870437622s
Availability | SPARQL endpoint availability check for Open Data Thesaurus took 0.300950288772583s
Availability | VoID file availability check for Open Data Thesaurus took 0.0007097721099853516s
Extra | Recovery of all triples for Open Data Thesaurus took 1.324648141860962s
Performance | Total latancy measurement for Open Data Thesaurus took 0.582460880279541s
Amount of data | Number of triples check for Open Data Thesaurus took 0.13218045234680176s
Interoperability | New terms check for Open Data Thesaurus took 1.3542709350585938s
Versatility | Languages check for Open Data Thesaurus took 0.15476179122924805s
Interpretability | Number of blank nodes check for Open Data Thesaurus took 0.14633631706237793s
Security | Check HTTPS for Open Data Thesaurus took 0.3662123680114746s
Interpretability | RDF structures check for Open Data Thesaurus took 0.14800095558166504s
Versatility | Serialization formats check for Open Data Thesaurus took 0.1444845199584961s
Availability | RDF dump link check for Open Data Thesaurus took 1.2605249881744385s
License | MR license check for Open Data Thesaurus took 0.14132118225097656s
License | HR license check for Open Data Thesaurus took 0.12100911140441895s
Amount of data | Number of property check for Open Data Thesaurus took 0.15181446075439453s
Understandability | Number of label check for Open Data Thesaurus took 0.15106797218322754s
Understandability | URI regex check for Open Data Thesaurus took 0.21494722366333008s
Understandability | Vocabs check for Open Data Thesaurus took 0.15241432189941406s
Verifiability | Authors check for Open Data Thesaurus took 0.13295292854309082s
Verifiability | Publishers check for Open Data Thesaurus took 0.13382291793823242s
Performance | Throughput check for Open Data Thesaurus took 10.62092399597168s
Amount of data | Check the number of entities for Open Data Thesaurus took 8.463859558105469e-05s
Verifiability | Contribs. check for Open Data Thesaurus took 0.1328718662261963s
Interlinking | sameAs chians check for Open Data Thesaurus took 0.13325095176696777s
Interlinking | skos check for Open Data Thesaurus took 0.1504991054534912s
Interlinking | skos check for Open Data Thesaurus took 0.10138559341430664s
Timeliness | dataset update frequency check for Open Data Thesaurus took 0.10085701942443848s
Currency | Creation date check for Open Data Thesaurus took 0.20167064666748047s
Currency | Modification date check for Open Data Thesaurus took 0.25604820251464844s
Rep.Conc. | URIs length for Open Data Thesaurus took 0.5316269397735596s
Consistency | Deprecated classes/propertiers check for Open Data Thesaurus took 0.17339825630187988s
Accuracy | Check Functional Property for Open Data Thesaurus took 0.09881782531738281s
Accuracy | Check Inverse Functional Property for Open Data Thesaurus took 0.10014104843139648s
Accuracy | Check Empty annotation labels for Open Data Thesaurus took 0.22851800918579102s
Accuracy | Check White space in annotation for Open Data Thesaurus took 0.0011529922485351562s
Consistency | Disjoint class check for Open Data Thesaurus took 0.09917616844177246s
Consistency | Check Misplaced properties for Open Data Thesaurus took 0.22319650650024414s
Consistency | Misplaced classes for Open Data Thesaurus took 0.0994117259979248s
Consistency | Check Ontology hijacking for Open Data Thesaurus took 1.3517017364501953s
Consistency | Check Invalid usage of undefined properties for Open Data Thesaurus took 1.279860258102417s
Conciseness | Check Extensional conciseness for Open Data Thesaurus took 0.00016427040100097656s
Security | Sign check for Open Data Thesaurus took 0.09999346733093262s
Completeness | Calculation of interlinking completeness for Open Data Thesaurus took 0.34728312492370605s
Reputation | Calculation of the PageRank for Open Data Thesaurus took 0.019732236862182617s
Interlinking | Calculation of Degree of Connection for Open Data Thesaurus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open Data Thesaurus took 0.0017256736755371094s
Interlinking | Calculation of Clustering coefficient for Open Data Thesaurus took 8.273124694824219e-05s
Believability | Calculation of trust value for Open Data Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for open-data-thesaurus took 87.60000443458557s
Availability | SPARQL endpoint availability check for Open Data @ Tor Vergata took 4.935264587402344e-05s
Availability | VoID file availability check for Open Data @ Tor Vergata took 0.00029730796813964844s
Completeness | Calculation of interlinking completeness for Open Data @ Tor Vergata took 0.2794315814971924s
Reputation | Calculation of the PageRank for Open Data @ Tor Vergata took 0.02080225944519043s
Interlinking | Calculation of Degree of Connection for Open Data @ Tor Vergata took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Data @ Tor Vergata took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Open Data @ Tor Vergata took 3.123283386230469e-05s
Believability | Calculation of trust value for Open Data @ Tor Vergata took 7.867813110351562e-06s
INFO | --- Analysis for open-data-tor-vergata took 3.2936973571777344s
Availability | SPARQL endpoint availability check for Open Election Data Project took 5.316734313964844e-05s
Availability | VoID file availability check for Open Election Data Project took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for Open Election Data Project took 0.3000926971435547s
Reputation | Calculation of the PageRank for Open Election Data Project took 0.020830631256103516s
Interlinking | Calculation of Degree of Connection for Open Election Data Project took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Election Data Project took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Open Election Data Project took 6.67572021484375e-05s
Believability | Calculation of trust value for Open Election Data Project took 4.76837158203125e-06s
INFO | --- Analysis for open-election-data-project took 4.337606191635132s
Availability | SPARQL endpoint availability check for OpenEI - Open Energy Info took 4.38143515586853s
Availability | VoID file availability check for OpenEI - Open Energy Info took 0.0006699562072753906s
Completeness | Calculation of interlinking completeness for OpenEI - Open Energy Info took 0.28583693504333496s
Reputation | Calculation of the PageRank for OpenEI - Open Energy Info took 0.020537614822387695s
Interlinking | Calculation of Degree of Connection for OpenEI - Open Energy Info took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for OpenEI - Open Energy Info took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for OpenEI - Open Energy Info took 8.463859558105469e-05s
Believability | Calculation of trust value for OpenEI - Open Energy Info took 5.7220458984375e-06s
INFO | --- Analysis for open-energy-info-wiki took 11.914771318435669s
Availability | SPARQL endpoint availability check for Open Library took 4.2438507080078125e-05s
Availability | VoID file availability check for Open Library took 0.0008137226104736328s
Completeness | Calculation of interlinking completeness for Open Library took 0.3019294738769531s
Reputation | Calculation of the PageRank for Open Library took 0.020305156707763672s
Interlinking | Calculation of Degree of Connection for Open Library took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Open Library took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Open Library took 6.794929504394531e-05s
Believability | Calculation of trust value for Open Library took 5.9604644775390625e-06s
INFO | --- Analysis for open-library took 12.224247694015503s
Availability | SPARQL endpoint availability check for Open Directory took 3.9577484130859375e-05s
Availability | VoID file availability check for Open Directory took 0.00023651123046875s
Completeness | Calculation of interlinking completeness for Open Directory took 0.28921937942504883s
Reputation | Calculation of the PageRank for Open Directory took 0.02012157440185547s
Interlinking | Calculation of Degree of Connection for Open Directory took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Open Directory took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Open Directory took 3.1948089599609375e-05s
Believability | Calculation of trust value for Open Directory took 6.4373016357421875e-06s
INFO | --- Analysis for open_directory took 3.1906661987304688s
Availability | SPARQL endpoint availability check for Open Land Use @PSNC took 0.6320428848266602s
Availability | VoID file availability check for Open Land Use @PSNC took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for Open Land Use @PSNC took 0.28014254570007324s
Reputation | Calculation of the PageRank for Open Land Use @PSNC took 0.020267248153686523s
Interlinking | Calculation of Degree of Connection for Open Land Use @PSNC took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Land Use @PSNC took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Open Land Use @PSNC took 2.7179718017578125e-05s
Believability | Calculation of trust value for Open Land Use @PSNC took 7.3909759521484375e-06s
INFO | --- Analysis for Open_Land_Use took 3.883697986602783s
Availability | SPARQL endpoint availability check for flyatlas took 1.7914032936096191s
Availability | VoID file availability check for flyatlas took 0.0005693435668945312s
Completeness | Calculation of interlinking completeness for flyatlas took 0.288057804107666s
Reputation | Calculation of the PageRank for flyatlas took 0.020372390747070312s
Interlinking | Calculation of Degree of Connection for flyatlas took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for flyatlas took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for flyatlas took 2.8848648071289062e-05s
Believability | Calculation of trust value for flyatlas took 7.152557373046875e-06s
INFO | --- Analysis for openbiomed-flyatlas took 10.806680679321289s
Availability | SPARQL endpoint availability check for OpenCalais took 4.315376281738281e-05s
Availability | VoID file availability check for OpenCalais took 0.0006692409515380859s
Completeness | Calculation of interlinking completeness for OpenCalais took 0.2886037826538086s
Reputation | Calculation of the PageRank for OpenCalais took 0.020532608032226562s
Interlinking | Calculation of Degree of Connection for OpenCalais took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OpenCalais took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for OpenCalais took 0.00011277198791503906s
Believability | Calculation of trust value for OpenCalais took 8.344650268554688e-06s
INFO | --- Analysis for opencalais took 5.736240863800049s
Availability | SPARQL endpoint availability check for OpenCorporates - The Open Database Of The Corporate World took 4.124641418457031e-05s
Availability | VoID file availability check for OpenCorporates - The Open Database Of The Corporate World took 0.0005860328674316406s
Completeness | Calculation of interlinking completeness for OpenCorporates - The Open Database Of The Corporate World took 0.28345179557800293s
Reputation | Calculation of the PageRank for OpenCorporates - The Open Database Of The Corporate World took 0.020714759826660156s
Interlinking | Calculation of Degree of Connection for OpenCorporates - The Open Database Of The Corporate World took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OpenCorporates - The Open Database Of The Corporate World took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for OpenCorporates - The Open Database Of The Corporate World took 7.62939453125e-05s
Believability | Calculation of trust value for OpenCorporates - The Open Database Of The Corporate World took 5.7220458984375e-06s
INFO | --- Analysis for opencorporates took 3.047607421875s
Availability | SPARQL endpoint availability check for OpenCyc took 4.8160552978515625e-05s
Availability | VoID file availability check for OpenCyc took 0.00039124488830566406s
Completeness | Calculation of interlinking completeness for OpenCyc took 0.3042120933532715s
Reputation | Calculation of the PageRank for OpenCyc took 0.020529508590698242s
Interlinking | Calculation of Degree of Connection for OpenCyc took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OpenCyc took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for OpenCyc took 0.00011444091796875s
Believability | Calculation of trust value for OpenCyc took 7.152557373046875e-06s
INFO | --- Analysis for opencyc took 2.6331231594085693s
Availability | SPARQL endpoint availability check for opendatacommunities-dev-local-authority-services took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-dev-local-authority-services took 0.0005588531494140625s
Completeness | Calculation of interlinking completeness for opendatacommunities-dev-local-authority-services took 0.28394651412963867s
Reputation | Calculation of the PageRank for opendatacommunities-dev-local-authority-services took 0.020511627197265625s
Interlinking | Calculation of Degree of Connection for opendatacommunities-dev-local-authority-services took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-dev-local-authority-services took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-dev-local-authority-services took 3.4809112548828125e-05s
Believability | Calculation of trust value for opendatacommunities-dev-local-authority-services took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-dev-local-authority-services took 2.7698183059692383s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-acceptances-per-1000 took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-acceptances-per-1000 took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-acceptances-per-1000 took 0.287121057510376s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-acceptances-per-1000 took 0.02056741714477539s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-acceptances-per-1000 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-acceptances-per-1000 took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-acceptances-per-1000 took 3.743171691894531e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-acceptances-per-1000 took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-homelessness-acceptances-per-1000 took 2.7492775917053223s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.2977147102355957s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.020634174346923828s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 2.8125572204589844s
Availability | SPARQL endpoint availability check for opendatacommunities-households-2008 took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-households-2008 took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-2008 took 0.282773494720459s
Reputation | Calculation of the PageRank for opendatacommunities-households-2008 took 0.020497798919677734s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-2008 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-2008 took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-2008 took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatacommunities-households-2008 took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-households-2008 took 2.6169300079345703s
Availability | SPARQL endpoint availability check for opendatacommunities-households-accommodated-per-1000 took 4.363059997558594e-05s
Availability | VoID file availability check for opendatacommunities-households-accommodated-per-1000 took 0.0006082057952880859s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-accommodated-per-1000 took 0.3016359806060791s
Reputation | Calculation of the PageRank for opendatacommunities-households-accommodated-per-1000 took 0.020341873168945312s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-accommodated-per-1000 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-accommodated-per-1000 took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-accommodated-per-1000 took 3.886222839355469e-05s
Believability | Calculation of trust value for opendatacommunities-households-accommodated-per-1000 took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-households-accommodated-per-1000 took 2.8787038326263428s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-population took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-population took 0.0004398822784423828s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-population took 0.29633045196533203s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-population took 0.0205838680267334s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-population took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-population took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-population took 3.910064697265625e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-population took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-households-projections-population took 2.7289211750030518s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-totalhouseolds took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-totalhouseolds took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-totalhouseolds took 0.31070566177368164s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-totalhouseolds took 0.02033090591430664s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-totalhouseolds took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-totalhouseolds took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-totalhouseolds took 3.62396240234375e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-totalhouseolds took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-households-projections-totalhouseolds took 2.742457389831543s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.29157352447509766s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.020095109939575195s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 3.504753112792969e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 6.4373016357421875e-06s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 2.593146324157715s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 5.435943603515625e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.2812361717224121s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.02016162872314453s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 3.62396240234375e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 5.9604644775390625e-06s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 2.807832956314087s
Availability | SPARQL endpoint availability check for opendatacommunities-housing-market took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-housing-market took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for opendatacommunities-housing-market took 0.3313267230987549s
Reputation | Calculation of the PageRank for opendatacommunities-housing-market took 0.02026653289794922s
Interlinking | Calculation of Degree of Connection for opendatacommunities-housing-market took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatacommunities-housing-market took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-housing-market took 3.4809112548828125e-05s
Believability | Calculation of trust value for opendatacommunities-housing-market took 5.7220458984375e-06s
INFO | --- Analysis for opendatacommunities-housing-market took 2.7772092819213867s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-crime-rank-2010 took 4.0531158447265625e-05s
Availability | VoID file availability check for opendatacommunities-imd-crime-rank-2010 took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-crime-rank-2010 took 0.29671621322631836s
Reputation | Calculation of the PageRank for opendatacommunities-imd-crime-rank-2010 took 0.02018260955810547s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-crime-rank-2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-imd-crime-rank-2010 took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-crime-rank-2010 took 3.7670135498046875e-05s
Believability | Calculation of trust value for opendatacommunities-imd-crime-rank-2010 took 5.4836273193359375e-06s
INFO | --- Analysis for opendatacommunities-imd-crime-rank-2010 took 2.720935821533203s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-environment-rank-2010 took 4.100799560546875e-05s
Availability | VoID file availability check for opendatacommunities-imd-environment-rank-2010 took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-environment-rank-2010 took 0.28436946868896484s
Reputation | Calculation of the PageRank for opendatacommunities-imd-environment-rank-2010 took 0.02022862434387207s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-environment-rank-2010 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-imd-environment-rank-2010 took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-environment-rank-2010 took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatacommunities-imd-environment-rank-2010 took 5.245208740234375e-06s
INFO | --- Analysis for opendatacommunities-imd-environment-rank-2010 took 2.7167375087738037s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-income-rank-la-2010 took 4.482269287109375e-05s
Availability | VoID file availability check for opendatacommunities-imd-income-rank-la-2010 took 0.0005514621734619141s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-income-rank-la-2010 took 0.29123950004577637s
Reputation | Calculation of the PageRank for opendatacommunities-imd-income-rank-la-2010 took 0.02078723907470703s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-income-rank-la-2010 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-income-rank-la-2010 took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-income-rank-la-2010 took 4.4345855712890625e-05s
Believability | Calculation of trust value for opendatacommunities-imd-income-rank-la-2010 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-imd-income-rank-la-2010 took 2.753715991973877s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-rank-2010 took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-imd-rank-2010 took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-rank-2010 took 0.2785465717315674s
Reputation | Calculation of the PageRank for opendatacommunities-imd-rank-2010 took 0.020425796508789062s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-rank-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-rank-2010 took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-rank-2010 took 4.124641418457031e-05s
Believability | Calculation of trust value for opendatacommunities-imd-rank-2010 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-imd-rank-2010 took 2.6520369052886963s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-score-2010 took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-imd-score-2010 took 0.0005505084991455078s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-score-2010 took 0.2845485210418701s
Reputation | Calculation of the PageRank for opendatacommunities-imd-score-2010 took 0.020412445068359375s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-score-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-score-2010 took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-score-2010 took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatacommunities-imd-score-2010 took 8.58306884765625e-06s
INFO | --- Analysis for opendatacommunities-imd-score-2010 took 2.830298900604248s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-affordable-housing-starts took 0.2861292362213135s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-affordable-housing-starts took 0.020123720169067383s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-affordable-housing-starts took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-affordable-housing-starts took 3.886222839355469e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-affordable-housing-starts took 5.0067901611328125e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-affordable-housing-starts took 2.760737657546997s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0006914138793945312s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.30083656311035156s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.02068042755126953s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 2.7356033325195312s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-housing-starts took 5.1021575927734375e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-housing-starts took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-housing-starts took 0.2984476089477539s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-housing-starts took 0.020603656768798828s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-housing-starts took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-housing-starts took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-housing-starts took 4.267692565917969e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-housing-starts took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-housing-starts took 2.7424192428588867s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-planning-applications-granted took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-planning-applications-granted took 0.0002760887145996094s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-planning-applications-granted took 0.29906630516052246s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-planning-applications-granted took 0.020352840423583984s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-planning-applications-granted took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-planning-applications-granted took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-planning-applications-granted took 4.029273986816406e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-planning-applications-granted took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-planning-applications-granted took 2.657684087753296s
Availability | SPARQL endpoint availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.30418944358825684s
Reputation | Calculation of the PageRank for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.020412921905517578s
Interlinking | Calculation of Degree of Connection for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.124641418457031e-05s
Believability | Calculation of trust value for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 2.881446123123169s
Availability | SPARQL endpoint availability check for opendatacommunities-net-additional-dwellings took 0.00010085105895996094s
Availability | VoID file availability check for opendatacommunities-net-additional-dwellings took 0.00043463706970214844s
Completeness | Calculation of interlinking completeness for opendatacommunities-net-additional-dwellings took 0.29555654525756836s
Reputation | Calculation of the PageRank for opendatacommunities-net-additional-dwellings took 0.02041006088256836s
Interlinking | Calculation of Degree of Connection for opendatacommunities-net-additional-dwellings took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-net-additional-dwellings took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-net-additional-dwellings took 3.886222839355469e-05s
Believability | Calculation of trust value for opendatacommunities-net-additional-dwellings took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-net-additional-dwellings took 2.7335503101348877s
Availability | SPARQL endpoint availability check for opendatacommunities-service-expenditure took 7.843971252441406e-05s
Availability | VoID file availability check for opendatacommunities-service-expenditure took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for opendatacommunities-service-expenditure took 0.29166340827941895s
Reputation | Calculation of the PageRank for opendatacommunities-service-expenditure took 0.0208132266998291s
Interlinking | Calculation of Degree of Connection for opendatacommunities-service-expenditure took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-service-expenditure took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-service-expenditure took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatacommunities-service-expenditure took 6.4373016357421875e-06s
INFO | --- Analysis for opendatacommunities-service-expenditure took 2.753864288330078s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.3013129234313965s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.020381450653076172s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.267692565917969e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 6.4373016357421875e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 2.7591745853424072s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.32593607902526855s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.02067852020263672s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.3392181396484375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 2.9608776569366455s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.458427429199219e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0005457401275634766s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.2906758785247803s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.020589351654052734s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.5299530029296875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 2.795625686645508s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0006005764007568359s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.2996644973754883s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.020173311233520508s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.220008850097656e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 2.7793033123016357s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0005381107330322266s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.3037569522857666s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.020509958267211914s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.315376281738281e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 2.7206356525421143s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 5.555152893066406e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0006623268127441406s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.28325366973876953s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.020510196685791016s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.291534423828125e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 2.812483549118042s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0005629062652587891s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.302654504776001s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0203855037689209s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0007925033569335938s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.982948303222656e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 2.803544521331787s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.3012733459472656s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.02052760124206543s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.506111145019531e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 2.77553653717041s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.2987508773803711s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.02065420150756836s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 6.198883056640625e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 2.768148422241211s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.2965381145477295s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.020547866821289062s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.482269287109375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 5.7220458984375e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 2.7595267295837402s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.100799560546875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.3030219078063965s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.020641088485717773s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.696846008300781e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 2.838651180267334s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.124641418457031e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0002338886260986328s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.28057098388671875s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.020557165145874023s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.7206878662109375e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 2.596954584121704s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.298856258392334s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0206143856048584s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.4345855712890625e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 6.4373016357421875e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 2.6438732147216797s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-housing-starts took 0.2876620292663574s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-housing-starts took 0.020620346069335938s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-housing-starts took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-housing-starts took 4.601478576660156e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-housing-starts took 5.9604644775390625e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-housing-starts took 2.6883792877197266s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.076957702636719e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.2995142936706543s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.02055668830871582s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.2438507080078125e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 5.7220458984375e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 2.8178837299346924s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 5.7220458984375e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-troubled-families took 0.3188769817352295s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-troubled-families took 0.02051234245300293s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-troubled-families took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-troubled-families took 4.3392181396484375e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-troubled-families took 5.7220458984375e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-troubled-families took 2.7121219635009766s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0004417896270751953s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.3057699203491211s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.020563125610351562s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.3392181396484375e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 5.0067901611328125e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 2.727226734161377s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.2890138626098633s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.020650625228881836s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.601478576660156e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 2.7385354042053223s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.302706241607666s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.02069711685180664s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 4.029273986816406e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 5.9604644775390625e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 2.8716957569122314s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.2991771697998047s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.020516395568847656s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 2.7623531818389893s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-worthwhile-mean took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-worthwhile-mean took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-worthwhile-mean took 0.28266143798828125s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-worthwhile-mean took 0.020516157150268555s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-worthwhile-mean took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-worthwhile-mean took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-worthwhile-mean took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-worthwhile-mean took 1.0728836059570312e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-worthwhile-mean took 2.8097712993621826s
Availability | SPARQL endpoint availability check for Open Data of Ecuador took 3.7856788635253906s
Availability | VoID file availability check for Open Data of Ecuador took 0.0002765655517578125s
Completeness | Calculation of interlinking completeness for Open Data of Ecuador took 0.29480814933776855s
Reputation | Calculation of the PageRank for Open Data of Ecuador took 0.020550966262817383s
Interlinking | Calculation of Degree of Connection for Open Data of Ecuador took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open Data of Ecuador took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Open Data of Ecuador took 8.535385131835938e-05s
Believability | Calculation of trust value for Open Data of Ecuador took 5.7220458984375e-06s
INFO | --- Analysis for opendataec took 8.75797724723816s
Availability | SPARQL endpoint availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 4.076957702636719e-05s
Availability | VoID file availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0005338191986083984s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.29968738555908203s
Reputation | Calculation of the PageRank for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.02058887481689453s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-education-pupils-by-school-and-datazone took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatascotland-graph-education-pupils-by-school-and-datazone took 5.4836273193359375e-06s
INFO | --- Analysis for opendatascotland-graph-education-pupils-by-school-and-datazone took 3.8367209434509277s
Availability | SPARQL endpoint availability check for opendatascotland-graph-simd-rank took 4.00543212890625e-05s
Availability | VoID file availability check for opendatascotland-graph-simd-rank took 0.0005383491516113281s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-simd-rank took 0.28794002532958984s
Reputation | Calculation of the PageRank for opendatascotland-graph-simd-rank took 0.02091503143310547s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-simd-rank took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-simd-rank took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-simd-rank took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatascotland-graph-simd-rank took 7.867813110351562e-06s
INFO | --- Analysis for opendatascotland-graph-simd-rank took 2.7542760372161865s
Availability | SPARQL endpoint availability check for opendatascotland-simd-crime-rank took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatascotland-simd-crime-rank took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-crime-rank took 0.2899465560913086s
Reputation | Calculation of the PageRank for opendatascotland-simd-crime-rank took 0.020621538162231445s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-crime-rank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-crime-rank took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-crime-rank took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatascotland-simd-crime-rank took 7.152557373046875e-06s
INFO | --- Analysis for opendatascotland-simd-crime-rank took 3.1805496215820312s
Availability | SPARQL endpoint availability check for opendatascotland-simd-education-rank took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatascotland-simd-education-rank took 0.0005855560302734375s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-education-rank took 0.28744006156921387s
Reputation | Calculation of the PageRank for opendatascotland-simd-education-rank took 0.02108931541442871s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-education-rank took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-education-rank took 0.0009701251983642578s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-education-rank took 4.482269287109375e-05s
Believability | Calculation of trust value for opendatascotland-simd-education-rank took 7.62939453125e-06s
INFO | --- Analysis for opendatascotland-simd-education-rank took 3.129009246826172s
Availability | SPARQL endpoint availability check for opendatascotland-simd-employment-rank took 4.1961669921875e-05s
Availability | VoID file availability check for opendatascotland-simd-employment-rank took 0.0005583763122558594s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-employment-rank took 0.2971348762512207s
Reputation | Calculation of the PageRank for opendatascotland-simd-employment-rank took 0.0206758975982666s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-employment-rank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-employment-rank took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-employment-rank took 3.814697265625e-05s
Believability | Calculation of trust value for opendatascotland-simd-employment-rank took 7.3909759521484375e-06s
INFO | --- Analysis for opendatascotland-simd-employment-rank took 3.1719911098480225s
Availability | SPARQL endpoint availability check for opendatascotland-simd-geographic-access-rank took 4.172325134277344e-05s
Availability | VoID file availability check for opendatascotland-simd-geographic-access-rank took 0.00044918060302734375s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-geographic-access-rank took 0.29019999504089355s
Reputation | Calculation of the PageRank for opendatascotland-simd-geographic-access-rank took 0.020729780197143555s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-geographic-access-rank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-geographic-access-rank took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-geographic-access-rank took 5.2928924560546875e-05s
Believability | Calculation of trust value for opendatascotland-simd-geographic-access-rank took 5.245208740234375e-06s
INFO | --- Analysis for opendatascotland-simd-geographic-access-rank took 3.172053575515747s
Availability | SPARQL endpoint availability check for opendatascotland-simd-health-rank took 4.124641418457031e-05s
Availability | VoID file availability check for opendatascotland-simd-health-rank took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-health-rank took 0.2862412929534912s
Reputation | Calculation of the PageRank for opendatascotland-simd-health-rank took 0.02057623863220215s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-health-rank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-health-rank took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-health-rank took 3.6716461181640625e-05s
Believability | Calculation of trust value for opendatascotland-simd-health-rank took 7.3909759521484375e-06s
INFO | --- Analysis for opendatascotland-simd-health-rank took 3.2124156951904297s
Availability | SPARQL endpoint availability check for opendatascotland-simd-housing-rank took 4.1961669921875e-05s
Availability | VoID file availability check for opendatascotland-simd-housing-rank took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-housing-rank took 0.29673314094543457s
Reputation | Calculation of the PageRank for opendatascotland-simd-housing-rank took 0.020545482635498047s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-housing-rank took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-housing-rank took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-housing-rank took 3.814697265625e-05s
Believability | Calculation of trust value for opendatascotland-simd-housing-rank took 5.4836273193359375e-06s
INFO | --- Analysis for opendatascotland-simd-housing-rank took 3.1773414611816406s
Availability | SPARQL endpoint availability check for opendatascotland-simd-income-rank took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatascotland-simd-income-rank took 0.00023412704467773438s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-income-rank took 0.2801828384399414s
Reputation | Calculation of the PageRank for opendatascotland-simd-income-rank took 0.02070927619934082s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-income-rank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-income-rank took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-income-rank took 3.7670135498046875e-05s
Believability | Calculation of trust value for opendatascotland-simd-income-rank took 5.7220458984375e-06s
INFO | --- Analysis for opendatascotland-simd-income-rank took 2.573763847351074s
Availability | SPARQL endpoint availability check for OpenLink Software LOD Cache took 30.54138731956482s
Availability | VoID file availability check for OpenLink Software LOD Cache took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for OpenLink Software LOD Cache took 0.2807650566101074s
Reputation | Calculation of the PageRank for OpenLink Software LOD Cache took 0.020874500274658203s
Interlinking | Calculation of Degree of Connection for OpenLink Software LOD Cache took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OpenLink Software LOD Cache took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for OpenLink Software LOD Cache took 3.0279159545898438e-05s
Believability | Calculation of trust value for OpenLink Software LOD Cache took 5.4836273193359375e-06s
INFO | --- Analysis for openlink-lod-cache took 63.33378195762634s
Availability | SPARQL endpoint availability check for openlinksw dataspaces took 4.220008850097656e-05s
Availability | VoID file availability check for openlinksw dataspaces took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for openlinksw dataspaces took 0.28148317337036133s
Reputation | Calculation of the PageRank for openlinksw dataspaces took 0.020536422729492188s
Interlinking | Calculation of Degree of Connection for openlinksw dataspaces took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for openlinksw dataspaces took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for openlinksw dataspaces took 9.560585021972656e-05s
Believability | Calculation of trust value for openlinksw dataspaces took 1.2636184692382812e-05s
INFO | --- Analysis for openlinksw-dataspaces took 2.8674097061157227s
Availability | SPARQL endpoint availability check for Openly Local :: Making Local Government More Transparent took 4.315376281738281e-05s
Availability | VoID file availability check for Openly Local :: Making Local Government More Transparent took 0.0008237361907958984s
Completeness | Calculation of interlinking completeness for Openly Local :: Making Local Government More Transparent took 0.4177284240722656s
Reputation | Calculation of the PageRank for Openly Local :: Making Local Government More Transparent took 0.020493030548095703s
Interlinking | Calculation of Degree of Connection for Openly Local :: Making Local Government More Transparent took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Openly Local :: Making Local Government More Transparent took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Openly Local :: Making Local Government More Transparent took 9.703636169433594e-05s
Believability | Calculation of trust value for Openly Local :: Making Local Government More Transparent took 4.76837158203125e-06s
INFO | --- Analysis for openlylocal took 347.93345046043396s
Availability | SPARQL endpoint availability check for OpenMobileNetwork took 1.122232437133789s
Availability | VoID file availability check for OpenMobileNetwork took 0.000560760498046875s
Completeness | Calculation of interlinking completeness for OpenMobileNetwork took 0.30092835426330566s
Reputation | Calculation of the PageRank for OpenMobileNetwork took 0.02022838592529297s
Interlinking | Calculation of Degree of Connection for OpenMobileNetwork took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OpenMobileNetwork took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for OpenMobileNetwork took 7.343292236328125e-05s
Believability | Calculation of trust value for OpenMobileNetwork took 6.198883056640625e-06s
INFO | --- Analysis for openmobilenetwork took 4.321478366851807s
Availability | SPARQL endpoint availability check for OpenTox took 4.00543212890625e-05s
Availability | VoID file availability check for OpenTox took 0.00023651123046875s
Completeness | Calculation of interlinking completeness for OpenTox took 0.27988386154174805s
Reputation | Calculation of the PageRank for OpenTox took 0.02018594741821289s
Interlinking | Calculation of Degree of Connection for OpenTox took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for OpenTox took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for OpenTox took 2.8133392333984375e-05s
Believability | Calculation of trust value for OpenTox took 6.67572021484375e-06s
INFO | --- Analysis for opentox took 3.1756091117858887s
Availability | SPARQL endpoint availability check for OpenUpLabs Datasets took 4.00543212890625e-05s
Availability | VoID file availability check for OpenUpLabs Datasets took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for OpenUpLabs Datasets took 0.30905961990356445s
Reputation | Calculation of the PageRank for OpenUpLabs Datasets took 0.020378589630126953s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Datasets took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OpenUpLabs Datasets took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Datasets took 2.7894973754882812e-05s
Believability | Calculation of trust value for OpenUpLabs Datasets took 5.9604644775390625e-06s
INFO | --- Analysis for openuplabs took 3.192002773284912s
Availability | SPARQL endpoint availability check for OPUS - an open source parallel corpus took 5.316734313964844e-05s
Availability | VoID file availability check for OPUS - an open source parallel corpus took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for OPUS - an open source parallel corpus took 0.2882983684539795s
Reputation | Calculation of the PageRank for OPUS - an open source parallel corpus took 0.020596027374267578s
Interlinking | Calculation of Degree of Connection for OPUS - an open source parallel corpus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OPUS - an open source parallel corpus took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for OPUS - an open source parallel corpus took 2.9087066650390625e-05s
Believability | Calculation of trust value for OPUS - an open source parallel corpus took 6.4373016357421875e-06s
INFO | --- Analysis for opus took 3.168633460998535s
Availability | SPARQL endpoint availability check for ORCID Connecting Research and Researchers took 4.0531158447265625e-05s
Availability | VoID file availability check for ORCID Connecting Research and Researchers took 0.00035500526428222656s
Completeness | Calculation of interlinking completeness for ORCID Connecting Research and Researchers took 0.2851676940917969s
Reputation | Calculation of the PageRank for ORCID Connecting Research and Researchers took 0.020152568817138672s
Interlinking | Calculation of Degree of Connection for ORCID Connecting Research and Researchers took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ORCID Connecting Research and Researchers took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for ORCID Connecting Research and Researchers took 3.361701965332031e-05s
Believability | Calculation of trust value for ORCID Connecting Research and Researchers took 8.58306884765625e-06s
INFO | --- Analysis for orcid took 3.178446054458618s
Availability | SPARQL endpoint availability check for Ordnance Survey Linked Data took 0.9917933940887451s
Availability | VoID file availability check for Ordnance Survey Linked Data took 0.0005822181701660156s
Completeness | Calculation of interlinking completeness for Ordnance Survey Linked Data took 0.3004279136657715s
Reputation | Calculation of the PageRank for Ordnance Survey Linked Data took 0.02026963233947754s
Interlinking | Calculation of Degree of Connection for Ordnance Survey Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ordnance Survey Linked Data took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey Linked Data took 9.417533874511719e-05s
Believability | Calculation of trust value for Ordnance Survey Linked Data took 5.4836273193359375e-06s
INFO | --- Analysis for ordnance-survey-linked-data took 5.60551905632019s
Availability | SPARQL endpoint availability check for oreilly took 4.220008850097656e-05s
Availability | VoID file availability check for oreilly took 0.0005791187286376953s
Completeness | Calculation of interlinking completeness for oreilly took 0.3036048412322998s
Reputation | Calculation of the PageRank for oreilly took 0.020223140716552734s
Interlinking | Calculation of Degree of Connection for oreilly took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for oreilly took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for oreilly took 4.8160552978515625e-05s
Believability | Calculation of trust value for oreilly took 9.059906005859375e-06s
INFO | --- Analysis for oreilly took 4.891260385513306s
Availability | SPARQL endpoint availability check for Medicine and Natural Product Data took 3.4560294151306152s
Availability | VoID file availability check for Medicine and Natural Product Data took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for Medicine and Natural Product Data took 0.28269147872924805s
Reputation | Calculation of the PageRank for Medicine and Natural Product Data took 0.020493030548095703s
Interlinking | Calculation of Degree of Connection for Medicine and Natural Product Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Medicine and Natural Product Data took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Medicine and Natural Product Data took 3.075599670410156e-05s
Believability | Calculation of trust value for Medicine and Natural Product Data took 7.152557373046875e-06s
INFO | --- Analysis for Organchem-Data took 7.522043943405151s
Availability | SPARQL endpoint availability check for Organic Edunet Linked Open Data took 0.07110452651977539s
Availability | VoID file availability check for Organic Edunet Linked Open Data took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for Organic Edunet Linked Open Data took 0.2817809581756592s
Reputation | Calculation of the PageRank for Organic Edunet Linked Open Data took 0.020188331604003906s
Interlinking | Calculation of Degree of Connection for Organic Edunet Linked Open Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Organic Edunet Linked Open Data took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Organic Edunet Linked Open Data took 8.296966552734375e-05s
Believability | Calculation of trust value for Organic Edunet Linked Open Data took 5.245208740234375e-06s
INFO | --- Analysis for organic-edunet took 9.278894186019897s
Availability | SPARQL endpoint availability check for Open Research Knowledge Graph (ORKG) took 0.4044020175933838s
Availability | VoID file availability check for Open Research Knowledge Graph (ORKG) took 0.0005996227264404297s
Extra | Recovery of all triples for Open Research Knowledge Graph (ORKG) took 6.780325889587402s
Performance | Total latancy measurement for Open Research Knowledge Graph (ORKG) took 0.845069408416748s
Amount of data | Number of triples check for Open Research Knowledge Graph (ORKG) took 0.2219409942626953s
Interoperability | New terms check for Open Research Knowledge Graph (ORKG) took 1.541184425354004s
Versatility | Languages check for Open Research Knowledge Graph (ORKG) took 9.61485767364502s
Interpretability | Number of blank nodes check for Open Research Knowledge Graph (ORKG) took 0.16836214065551758s
Interpretability | RDF structures check for Open Research Knowledge Graph (ORKG) took 0.40426111221313477s
Versatility | Serialization formats check for Open Research Knowledge Graph (ORKG) took 0.16138863563537598s
Availability | RDF dump link check for Open Research Knowledge Graph (ORKG) took 0.1716756820678711s
License | MR license check for Open Research Knowledge Graph (ORKG) took 0.15990924835205078s
License | HR license check for Open Research Knowledge Graph (ORKG) took 6.164815902709961s
Amount of data | Number of property check for Open Research Knowledge Graph (ORKG) took 0.17452692985534668s
Understandability | Number of label check for Open Research Knowledge Graph (ORKG) took 0.23273658752441406s
Understandability | URI regex check for Open Research Knowledge Graph (ORKG) took 0.32630181312561035s
Understandability | Vocabs check for Open Research Knowledge Graph (ORKG) took 0.16602492332458496s
Verifiability | Authors check for Open Research Knowledge Graph (ORKG) took 0.15245318412780762s
Verifiability | Publishers check for Open Research Knowledge Graph (ORKG) took 0.1771259307861328s
Performance | Throughput check for Open Research Knowledge Graph (ORKG) took 10.31283712387085s
Amount of data | Check the number of entities for Open Research Knowledge Graph (ORKG) took 8.058547973632812e-05s
Verifiability | Contribs. check for Open Research Knowledge Graph (ORKG) took 0.1560227870941162s
Interlinking | sameAs chians check for Open Research Knowledge Graph (ORKG) took 0.14811944961547852s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.15963149070739746s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.17984986305236816s
Timeliness | dataset update frequency check for Open Research Knowledge Graph (ORKG) took 0.1585705280303955s
Currency | Creation date check for Open Research Knowledge Graph (ORKG) took 0.37793970108032227s
Currency | Modification date check for Open Research Knowledge Graph (ORKG) took 0.34429049491882324s
Rep.Conc. | URIs length for Open Research Knowledge Graph (ORKG) took 4.01547384262085s
Interoperability | New vocabularies check for Open Research Knowledge Graph (ORKG) took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for Open Research Knowledge Graph (ORKG) took 0.18726825714111328s
Accuracy | Check Functional Property for Open Research Knowledge Graph (ORKG) took 0.2068347930908203s
Accuracy | Check Inverse Functional Property for Open Research Knowledge Graph (ORKG) took 0.1814107894897461s
Accuracy | Check Empty annotation labels for Open Research Knowledge Graph (ORKG) took 2.5434651374816895s
Accuracy | Check White space in annotation for Open Research Knowledge Graph (ORKG) took 0.2735018730163574s
Accuracy | Check Datatype consistency for Open Research Knowledge Graph (ORKG) took 0.2647998332977295s
Consistency | Disjoint class check for Open Research Knowledge Graph (ORKG) took 0.2735891342163086s
Consistency | Check Misplaced properties for Open Research Knowledge Graph (ORKG) took 1.663379430770874s
Consistency | Misplaced classes for Open Research Knowledge Graph (ORKG) took 0.8851487636566162s
Consistency | Check Ontology hijacking for Open Research Knowledge Graph (ORKG) took 3.113065004348755s
Consistency | Check Invalid usage of undefined classes for Open Research Knowledge Graph (ORKG) took 1.1518213748931885s
Consistency | Check Invalid usage of undefined properties for Open Research Knowledge Graph (ORKG) took 2.0008127689361572s
Conciseness | Check Extensional conciseness for Open Research Knowledge Graph (ORKG) took 0.2808518409729004s
Conciseness | Check Intensional conciseness for Open Research Knowledge Graph (ORKG) took 0.17098379135131836s
Security | Sign check for Open Research Knowledge Graph (ORKG) took 0.18738341331481934s
Availability | Check URIs Dereferenciability for Open Research Knowledge Graph (ORKG) took 2255.0694365501404s
Completeness | Calculation of interlinking completeness for Open Research Knowledge Graph (ORKG) took 1.1979353427886963s
Reputation | Calculation of the PageRank for Open Research Knowledge Graph (ORKG) took 0.021886825561523438s
Interlinking | Calculation of Degree of Connection for Open Research Knowledge Graph (ORKG) took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Open Research Knowledge Graph (ORKG) took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for Open Research Knowledge Graph (ORKG) took 2.5272369384765625e-05s
Interoperability | Check the re-using of existing vocabs for Open Research Knowledge Graph (ORKG) took 1.9073486328125e-06s
Believability | Calculation of trust value for Open Research Knowledge Graph (ORKG) took 7.867813110351562e-06s
INFO | --- Analysis for orkg took 2555.573811531067s
Availability | SPARQL endpoint availability check for The Orlando Women's Writing Linked Open Data Set took 3.050481081008911s
Availability | VoID file availability check for The Orlando Women's Writing Linked Open Data Set took 0.0007040500640869141s
Completeness | Calculation of interlinking completeness for The Orlando Women's Writing Linked Open Data Set took 0.31012630462646484s
Reputation | Calculation of the PageRank for The Orlando Women's Writing Linked Open Data Set took 0.020739316940307617s
Interlinking | Calculation of Degree of Connection for The Orlando Women's Writing Linked Open Data Set took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The Orlando Women's Writing Linked Open Data Set took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for The Orlando Women's Writing Linked Open Data Set took 8.273124694824219e-05s
Believability | Calculation of trust value for The Orlando Women's Writing Linked Open Data Set took 1.2159347534179688e-05s
INFO | --- Analysis for orlando-womens-writing-linked-open-data-set took 32.151251554489136s
Availability | SPARQL endpoint availability check for OSM Semantic Network took 1.688096284866333s
Availability | VoID file availability check for OSM Semantic Network took 0.0005965232849121094s
Completeness | Calculation of interlinking completeness for OSM Semantic Network took 0.2922935485839844s
Reputation | Calculation of the PageRank for OSM Semantic Network took 0.020376205444335938s
Interlinking | Calculation of Degree of Connection for OSM Semantic Network took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OSM Semantic Network took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for OSM Semantic Network took 3.337860107421875e-05s
Believability | Calculation of trust value for OSM Semantic Network took 8.106231689453125e-06s
INFO | --- Analysis for osm-semantic-network took 10.269578218460083s
Availability | SPARQL endpoint availability check for Open Transport Map @PSNC took 0.9593677520751953s
Availability | VoID file availability check for Open Transport Map @PSNC took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for Open Transport Map @PSNC took 0.2787783145904541s
Reputation | Calculation of the PageRank for Open Transport Map @PSNC took 0.020417451858520508s
Interlinking | Calculation of Degree of Connection for Open Transport Map @PSNC took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Transport Map @PSNC took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Open Transport Map @PSNC took 3.0279159545898438e-05s
Believability | Calculation of trust value for Open Transport Map @PSNC took 7.3909759521484375e-06s
INFO | --- Analysis for OTM took 5.504382848739624s
Availability | SPARQL endpoint availability check for OUNL DSpace in RDF took 3.933906555175781e-05s
Availability | VoID file availability check for OUNL DSpace in RDF took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for OUNL DSpace in RDF took 0.32179903984069824s
Reputation | Calculation of the PageRank for OUNL DSpace in RDF took 0.020267963409423828s
Interlinking | Calculation of Degree of Connection for OUNL DSpace in RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OUNL DSpace in RDF took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for OUNL DSpace in RDF took 2.9325485229492188e-05s
Believability | Calculation of trust value for OUNL DSpace in RDF took 7.62939453125e-06s
INFO | --- Analysis for ounl-dspace-in-rdf took 3.75744891166687s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 3.9577484130859375e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.00022983551025390625s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.3044743537902832s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.020402908325195312s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 3.0279159545898438e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 6.4373016357421875e-06s
INFO | --- Analysis for ox-ac-uk-catalogue took 3.6696767807006836s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 3.933906555175781e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.288999080657959s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.02053236961364746s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 2.7894973754882812e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 5.7220458984375e-06s
INFO | --- Analysis for ox-ac-uk-catalogue-metadata took 3.7083048820495605s
Availability | SPARQL endpoint availability check for OpenMeters (University of Oxford) took 3.838539123535156e-05s
Availability | VoID file availability check for OpenMeters (University of Oxford) took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for OpenMeters (University of Oxford) took 0.28212881088256836s
Reputation | Calculation of the PageRank for OpenMeters (University of Oxford) took 0.020430803298950195s
Interlinking | Calculation of Degree of Connection for OpenMeters (University of Oxford) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for OpenMeters (University of Oxford) took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for OpenMeters (University of Oxford) took 3.0279159545898438e-05s
Believability | Calculation of trust value for OpenMeters (University of Oxford) took 7.3909759521484375e-06s
INFO | --- Analysis for ox-ac-uk-openmeters took 3.574488401412964s
Availability | SPARQL endpoint availability check for Time-series metadata (University of Oxford) took 4.1961669921875e-05s
Availability | VoID file availability check for Time-series metadata (University of Oxford) took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for Time-series metadata (University of Oxford) took 0.3353304862976074s
Reputation | Calculation of the PageRank for Time-series metadata (University of Oxford) took 0.020534753799438477s
Interlinking | Calculation of Degree of Connection for Time-series metadata (University of Oxford) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Time-series metadata (University of Oxford) took 0.0007836818695068359s
Interlinking | Calculation of Clustering coefficient for Time-series metadata (University of Oxford) took 2.9087066650390625e-05s
Believability | Calculation of trust value for Time-series metadata (University of Oxford) took 6.198883056640625e-06s
INFO | --- Analysis for ox-ac-uk-timeseries took 3.1963984966278076s
Availability | SPARQL endpoint availability check for Vacancies (University of Oxford) took 4.076957702636719e-05s
Availability | VoID file availability check for Vacancies (University of Oxford) took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for Vacancies (University of Oxford) took 0.30268001556396484s
Reputation | Calculation of the PageRank for Vacancies (University of Oxford) took 0.020692110061645508s
Interlinking | Calculation of Degree of Connection for Vacancies (University of Oxford) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Vacancies (University of Oxford) took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Vacancies (University of Oxford) took 3.4332275390625e-05s
Believability | Calculation of trust value for Vacancies (University of Oxford) took 5.9604644775390625e-06s
INFO | --- Analysis for ox-ac-uk-vacancies took 3.2262938022613525s
Availability | SPARQL endpoint availability check for Events calendar for the University (University of Oxford) took 4.029273986816406e-05s
Availability | VoID file availability check for Events calendar for the University (University of Oxford) took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for Events calendar for the University (University of Oxford) took 0.30150580406188965s
Reputation | Calculation of the PageRank for Events calendar for the University (University of Oxford) took 0.02073526382446289s
Interlinking | Calculation of Degree of Connection for Events calendar for the University (University of Oxford) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Events calendar for the University (University of Oxford) took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for Events calendar for the University (University of Oxford) took 3.147125244140625e-05s
Believability | Calculation of trust value for Events calendar for the University (University of Oxford) took 5.9604644775390625e-06s
INFO | --- Analysis for ox-ac-uk-www-ox-ac-uk-events took 3.237560272216797s
Availability | SPARQL endpoint availability check for OxPoints (University of Oxford) took 5.054473876953125e-05s
Availability | VoID file availability check for OxPoints (University of Oxford) took 0.0002288818359375s
Completeness | Calculation of interlinking completeness for OxPoints (University of Oxford) took 0.2861812114715576s
Reputation | Calculation of the PageRank for OxPoints (University of Oxford) took 0.020345449447631836s
Interlinking | Calculation of Degree of Connection for OxPoints (University of Oxford) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OxPoints (University of Oxford) took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for OxPoints (University of Oxford) took 3.0040740966796875e-05s
Believability | Calculation of trust value for OxPoints (University of Oxford) took 6.9141387939453125e-06s
INFO | --- Analysis for oxpoints took 3.2746238708496094s
Availability | SPARQL endpoint availability check for Pali English Lexicon took 1.9590845108032227s
Availability | VoID file availability check for Pali English Lexicon took 0.0006341934204101562s
Completeness | Calculation of interlinking completeness for Pali English Lexicon took 0.2966485023498535s
Reputation | Calculation of the PageRank for Pali English Lexicon took 0.020314455032348633s
Interlinking | Calculation of Degree of Connection for Pali English Lexicon took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Pali English Lexicon took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Pali English Lexicon took 2.9087066650390625e-05s
Believability | Calculation of trust value for Pali English Lexicon took 7.867813110351562e-06s
INFO | --- Analysis for pali-english-lexicon took 7.77776837348938s
Availability | SPARQL endpoint availability check for PanLex took 0.6161458492279053s
Availability | VoID file availability check for PanLex took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for PanLex took 0.2997324466705322s
Reputation | Calculation of the PageRank for PanLex took 0.020311594009399414s
Interlinking | Calculation of Degree of Connection for PanLex took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for PanLex took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for PanLex took 7.343292236328125e-05s
Believability | Calculation of trust value for PanLex took 6.198883056640625e-06s
INFO | --- Analysis for panlex took 3.3312771320343018s
Availability | SPARQL endpoint availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 4.220008850097656e-05s
Availability | VoID file availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0003902912139892578s
Completeness | Calculation of interlinking completeness for Parole/Simple 'lexinfo' Ontology & lexicons took 0.2938089370727539s
Reputation | Calculation of the PageRank for Parole/Simple 'lexinfo' Ontology & lexicons took 0.020587921142578125s
Interlinking | Calculation of Degree of Connection for Parole/Simple 'lexinfo' Ontology & lexicons took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Parole/Simple 'lexinfo' Ontology & lexicons took 3.7670135498046875e-05s
Believability | Calculation of trust value for Parole/Simple 'lexinfo' Ontology & lexicons took 6.9141387939453125e-06s
INFO | --- Analysis for parole-simple-lexinfo-ontology-lexicons took 5.945260524749756s
Availability | SPARQL endpoint availability check for patents.data.gov.uk took 0.07216715812683105s
Availability | VoID file availability check for patents.data.gov.uk took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for patents.data.gov.uk took 0.3016936779022217s
Reputation | Calculation of the PageRank for patents.data.gov.uk took 0.020520925521850586s
Interlinking | Calculation of Degree of Connection for patents.data.gov.uk took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for patents.data.gov.uk took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for patents.data.gov.uk took 4.9591064453125e-05s
Believability | Calculation of trust value for patents.data.gov.uk took 5.7220458984375e-06s
INFO | --- Analysis for patents-data-gov-uk took 2.8571484088897705s
Availability | SPARQL endpoint availability check for PDEV-Lemon took 8.606910705566406e-05s
Availability | VoID file availability check for PDEV-Lemon took 0.0012426376342773438s
Completeness | Calculation of interlinking completeness for PDEV-Lemon took 0.28824329376220703s
Reputation | Calculation of the PageRank for PDEV-Lemon took 0.02069687843322754s
Interlinking | Calculation of Degree of Connection for PDEV-Lemon took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for PDEV-Lemon took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for PDEV-Lemon took 5.602836608886719e-05s
Believability | Calculation of trust value for PDEV-Lemon took 6.67572021484375e-06s
INFO | --- Analysis for pdev-lemon took 4.60630202293396s
Availability | SPARQL endpoint availability check for pdevlemon took 4.1484832763671875e-05s
Availability | VoID file availability check for pdevlemon took 0.0006802082061767578s
Completeness | Calculation of interlinking completeness for pdevlemon took 0.30388307571411133s
Reputation | Calculation of the PageRank for pdevlemon took 0.02047109603881836s
Interlinking | Calculation of Degree of Connection for pdevlemon took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for pdevlemon took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for pdevlemon took 3.0279159545898438e-05s
Believability | Calculation of trust value for pdevlemon took 5.7220458984375e-06s
INFO | --- Analysis for pdevlemon took 3.5845186710357666s
Availability | SPARQL endpoint availability check for PeriodO Period Gazetteer took 7.224082946777344e-05s
Availability | VoID file availability check for PeriodO Period Gazetteer took 0.0009179115295410156s
Completeness | Calculation of interlinking completeness for PeriodO Period Gazetteer took 0.32992076873779297s
Reputation | Calculation of the PageRank for PeriodO Period Gazetteer took 0.02061152458190918s
Interlinking | Calculation of Degree of Connection for PeriodO Period Gazetteer took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for PeriodO Period Gazetteer took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for PeriodO Period Gazetteer took 8.487701416015625e-05s
Believability | Calculation of trust value for PeriodO Period Gazetteer took 7.152557373046875e-06s
INFO | --- Analysis for periodo took 21.306293964385986s
Availability | SPARQL endpoint availability check for Personal_Homepages took 4.220008850097656e-05s
Availability | VoID file availability check for Personal_Homepages took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for Personal_Homepages took 0.3097233772277832s
Reputation | Calculation of the PageRank for Personal_Homepages took 0.020521163940429688s
Interlinking | Calculation of Degree of Connection for Personal_Homepages took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Personal_Homepages took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Personal_Homepages took 0.0004150867462158203s
Believability | Calculation of trust value for Personal_Homepages took 7.62939453125e-06s
INFO | --- Analysis for personal-homepages took 2.7107996940612793s
Availability | SPARQL endpoint availability check for Ontology of University People took 4.1484832763671875e-05s
Availability | VoID file availability check for Ontology of University People took 0.00024962425231933594s
Completeness | Calculation of interlinking completeness for Ontology of University People took 0.7278692722320557s
Reputation | Calculation of the PageRank for Ontology of University People took 0.02089214324951172s
Interlinking | Calculation of Degree of Connection for Ontology of University People took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontology of University People took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for Ontology of University People took 2.9325485229492188e-05s
Believability | Calculation of trust value for Ontology of University People took 5.4836273193359375e-06s
INFO | --- Analysis for PersonOnto took 3.0283899307250977s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 10.54830813407898s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.28278183937072754s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.020356416702270508s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.0967254638671875e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 6.9141387939453125e-06s
INFO | --- Analysis for PFKHS took 17.011856079101562s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 8.191964626312256s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0005512237548828125s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.3021688461303711s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.020221710205078125s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 5.3882598876953125e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.1920928955078125e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 6.4373016357421875e-06s
INFO | --- Analysis for PFRPPH took 14.969476699829102s
Availability | SPARQL endpoint availability check for PGxLOD took 0.4498565196990967s
Availability | VoID file availability check for PGxLOD took 0.0005593299865722656s
Extra | Recovery of all triples for PGxLOD took 1.815093755722046s
Performance | Total latancy measurement for PGxLOD took 0.9090824127197266s
Amount of data | Number of triples check for PGxLOD took 0.8595874309539795s
Interoperability | New terms check for PGxLOD took 1.8459722995758057s
Versatility | Languages check for PGxLOD took 60.2623507976532s
Interpretability | Number of blank nodes check for PGxLOD took 1.6509110927581787s
Interpretability | RDF structures check for PGxLOD took 0.4443817138671875s
Versatility | Serialization formats check for PGxLOD took 0.19272255897521973s
Availability | RDF dump link check for PGxLOD took 58.52689242362976s
License | MR license check for PGxLOD took 0.19624853134155273s
License | HR license check for PGxLOD took 60.26478719711304s
Amount of data | Number of property check for PGxLOD took 0.36901283264160156s
Understandability | Number of label check for PGxLOD took 1.0652365684509277s
Understandability | URI regex check for PGxLOD took 0.6326794624328613s
Understandability | Vocabs check for PGxLOD took 0.36878323554992676s
Verifiability | Authors check for PGxLOD took 0.29967284202575684s
Verifiability | Publishers check for PGxLOD took 0.3268730640411377s
Performance | Throughput check for PGxLOD took 10.99606966972351s
Amount of data | Check the number of entities for PGxLOD took 0.11877560615539551s
Verifiability | Contribs. check for PGxLOD took 0.18350839614868164s
Interlinking | sameAs chians check for PGxLOD took 0.2806069850921631s
Interlinking | skos check for PGxLOD took 0.22048163414001465s
Interlinking | skos check for PGxLOD took 0.24130749702453613s
Timeliness | dataset update frequency check for PGxLOD took 0.22351932525634766s
Currency | Creation date check for PGxLOD took 0.38669896125793457s
Currency | Modification date check for PGxLOD took 0.3601706027984619s
Rep.Conc. | URIs length for PGxLOD took 6.7334723472595215s
Consistency | Deprecated classes/propertiers check for PGxLOD took 0.18413376808166504s
Accuracy | Check Functional Property for PGxLOD took 0.2190084457397461s
Accuracy | Check Inverse Functional Property for PGxLOD took 0.2179417610168457s
Accuracy | Check Empty annotation labels for PGxLOD took 0.8412683010101318s
Accuracy | Check White space in annotation for PGxLOD took 0.038995981216430664s
Accuracy | Check Datatype consistency for PGxLOD took 0.027721881866455078s
Consistency | Disjoint class check for PGxLOD took 0.21296119689941406s
Consistency | Check Misplaced properties for PGxLOD took 7.160157203674316s
Consistency | Misplaced classes for PGxLOD took 0.3420734405517578s
Consistency | Check Ontology hijacking for PGxLOD took 2.189969062805176s
Consistency | Check Invalid usage of undefined classes for PGxLOD took 1.1201062202453613s
Consistency | Check Invalid usage of undefined properties for PGxLOD took 7.05451226234436s
Conciseness | Check Extensional conciseness for PGxLOD took 0.03161358833312988s
Conciseness | Check Intensional conciseness for PGxLOD took 0.28571033477783203s
Security | Sign check for PGxLOD took 0.20213532447814941s
Availability | Check URIs Dereferenciability for PGxLOD took 25106.56086564064s
Completeness | Calculation of interlinking completeness for PGxLOD took 1.2489476203918457s
Reputation | Calculation of the PageRank for PGxLOD took 0.022301197052001953s
Interlinking | Calculation of Degree of Connection for PGxLOD took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for PGxLOD took 0.0007963180541992188s
Interlinking | Calculation of Clustering coefficient for PGxLOD took 0.00011658668518066406s
Believability | Calculation of trust value for PGxLOD took 8.106231689453125e-06s
INFO | --- Analysis for PGxLOD took 224079.7293357849s
Availability | SPARQL endpoint availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 1.1000645160675049s
Availability | VoID file availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0006067752838134766s
Completeness | Calculation of interlinking completeness for Phonetics Information Base and Lexicon (PHOIBLE) took 0.25438642501831055s
Reputation | Calculation of the PageRank for Phonetics Information Base and Lexicon (PHOIBLE) took 0.021183252334594727s
Interlinking | Calculation of Degree of Connection for Phonetics Information Base and Lexicon (PHOIBLE) took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Phonetics Information Base and Lexicon (PHOIBLE) took 3.743171691894531e-05s
Believability | Calculation of trust value for Phonetics Information Base and Lexicon (PHOIBLE) took 6.9141387939453125e-06s
INFO | --- Analysis for phoible took 5.165418386459351s
Availability | SPARQL endpoint availability check for Parallel ice sheet model took 4.458427429199219e-05s
Availability | VoID file availability check for Parallel ice sheet model took 0.0006902217864990234s
Completeness | Calculation of interlinking completeness for Parallel ice sheet model took 0.27152276039123535s
Reputation | Calculation of the PageRank for Parallel ice sheet model took 0.02061319351196289s
Interlinking | Calculation of Degree of Connection for Parallel ice sheet model took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Parallel ice sheet model took 0.0008187294006347656s
Interlinking | Calculation of Clustering coefficient for Parallel ice sheet model took 3.4332275390625e-05s
Believability | Calculation of trust value for Parallel ice sheet model took 5.9604644775390625e-06s
INFO | --- Analysis for PISM took 9.304520845413208s
Availability | SPARQL endpoint availability check for PlanetData Project Wiki took 4.363059997558594e-05s
Availability | VoID file availability check for PlanetData Project Wiki took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for PlanetData Project Wiki took 0.27110981941223145s
Reputation | Calculation of the PageRank for PlanetData Project Wiki took 0.020530223846435547s
Interlinking | Calculation of Degree of Connection for PlanetData Project Wiki took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for PlanetData Project Wiki took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for PlanetData Project Wiki took 8.58306884765625e-05s
Believability | Calculation of trust value for PlanetData Project Wiki took 5.7220458984375e-06s
INFO | --- Analysis for planetdata-project-wiki took 2.8809049129486084s
Availability | SPARQL endpoint availability check for digitized plant specimen took 1.9658331871032715s
Availability | VoID file availability check for digitized plant specimen took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for digitized plant specimen took 0.26006221771240234s
Reputation | Calculation of the PageRank for digitized plant specimen took 0.02050495147705078s
Interlinking | Calculation of Degree of Connection for digitized plant specimen took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for digitized plant specimen took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for digitized plant specimen took 7.009506225585938e-05s
Believability | Calculation of trust value for digitized plant specimen took 5.0067901611328125e-06s
INFO | --- Analysis for plant-specimen took 4.439625263214111s
Availability | SPARQL endpoint availability check for Pleiades took 4.3392181396484375e-05s
Availability | VoID file availability check for Pleiades took 0.00036263465881347656s
Completeness | Calculation of interlinking completeness for Pleiades took 0.26739931106567383s
Reputation | Calculation of the PageRank for Pleiades took 0.020780563354492188s
Interlinking | Calculation of Degree of Connection for Pleiades took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Pleiades took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Pleiades took 8.463859558105469e-05s
Believability | Calculation of trust value for Pleiades took 6.4373016357421875e-06s
INFO | --- Analysis for pleiades took 15.708405494689941s
Availability | SPARQL endpoint availability check for podorozhnyk.com took 4.172325134277344e-05s
Availability | VoID file availability check for podorozhnyk.com took 0.0005426406860351562s
Completeness | Calculation of interlinking completeness for podorozhnyk.com took 0.2707815170288086s
Reputation | Calculation of the PageRank for podorozhnyk.com took 0.02022719383239746s
Interlinking | Calculation of Degree of Connection for podorozhnyk.com took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for podorozhnyk.com took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for podorozhnyk.com took 2.8371810913085938e-05s
Believability | Calculation of trust value for podorozhnyk.com took 6.198883056640625e-06s
INFO | --- Analysis for podorozhnyk took 3.7157833576202393s
Availability | SPARQL endpoint availability check for Poképédia took 5.435943603515625e-05s
Availability | VoID file availability check for Poképédia took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for Poképédia took 0.24579977989196777s
Reputation | Calculation of the PageRank for Poképédia took 0.020172834396362305s
Interlinking | Calculation of Degree of Connection for Poképédia took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Poképédia took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Poképédia took 6.866455078125e-05s
Believability | Calculation of trust value for Poképédia took 5.7220458984375e-06s
INFO | --- Analysis for pokepedia-fr took 3.112175226211548s
Availability | SPARQL endpoint availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 4.267692565917969e-05s
Availability | VoID file availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0006327629089355469s
Completeness | Calculation of interlinking completeness for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.2632937431335449s
Reputation | Calculation of the PageRank for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.020271778106689453s
Interlinking | Calculation of Degree of Connection for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 7.367134094238281e-05s
Believability | Calculation of trust value for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 7.152557373046875e-06s
INFO | --- Analysis for polymath-virtual-library took 5.586810111999512s
Availability | SPARQL endpoint availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.9743709564208984s
Availability | VoID file availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0005977153778076172s
Completeness | Calculation of interlinking completeness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.2730724811553955s
Reputation | Calculation of the PageRank for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.020148038864135742s
Interlinking | Calculation of Degree of Connection for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.2636184692382812e-05s
Believability | Calculation of trust value for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 5.245208740234375e-06s
INFO | --- Analysis for portuguese_prisons_releases took 7.212137699127197s
Availability | SPARQL endpoint availability check for Barley trading volume and wholesale prices took 4.100799560546875e-05s
Availability | VoID file availability check for Barley trading volume and wholesale prices took 0.00023102760314941406s
Completeness | Calculation of interlinking completeness for Barley trading volume and wholesale prices took 0.2724907398223877s
Reputation | Calculation of the PageRank for Barley trading volume and wholesale prices took 0.020298480987548828s
Interlinking | Calculation of Degree of Connection for Barley trading volume and wholesale prices took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Barley trading volume and wholesale prices took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Barley trading volume and wholesale prices took 2.8371810913085938e-05s
Believability | Calculation of trust value for Barley trading volume and wholesale prices took 5.7220458984375e-06s
INFO | --- Analysis for predicting-barley-volume-and-wholesale-prices took 2.9534270763397217s
Availability | SPARQL endpoint availability check for Corn trading volume and wholesale prices took 4.100799560546875e-05s
Availability | VoID file availability check for Corn trading volume and wholesale prices took 0.00021839141845703125s
Completeness | Calculation of interlinking completeness for Corn trading volume and wholesale prices took 0.291278600692749s
Reputation | Calculation of the PageRank for Corn trading volume and wholesale prices took 0.020498275756835938s
Interlinking | Calculation of Degree of Connection for Corn trading volume and wholesale prices took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Corn trading volume and wholesale prices took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Corn trading volume and wholesale prices took 3.0279159545898438e-05s
Believability | Calculation of trust value for Corn trading volume and wholesale prices took 2.9325485229492188e-05s
INFO | --- Analysis for predicting-corn-trading-volume-and-wholesale-prices took 3.0164122581481934s
Availability | SPARQL endpoint availability check for Onion trading volume and wholesale prices took 3.981590270996094e-05s
Availability | VoID file availability check for Onion trading volume and wholesale prices took 0.0002396106719970703s
Completeness | Calculation of interlinking completeness for Onion trading volume and wholesale prices took 0.27365970611572266s
Reputation | Calculation of the PageRank for Onion trading volume and wholesale prices took 0.020288705825805664s
Interlinking | Calculation of Degree of Connection for Onion trading volume and wholesale prices took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Onion trading volume and wholesale prices took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Onion trading volume and wholesale prices took 2.8133392333984375e-05s
Believability | Calculation of trust value for Onion trading volume and wholesale prices took 6.4373016357421875e-06s
INFO | --- Analysis for predicting-onion-volume-and-wholesale-prices took 2.8655803203582764s
Availability | SPARQL endpoint availability check for Potato trading volume and wholesale price took 4.0531158447265625e-05s
Availability | VoID file availability check for Potato trading volume and wholesale price took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for Potato trading volume and wholesale price took 0.2740607261657715s
Reputation | Calculation of the PageRank for Potato trading volume and wholesale price took 0.020235300064086914s
Interlinking | Calculation of Degree of Connection for Potato trading volume and wholesale price took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Potato trading volume and wholesale price took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Potato trading volume and wholesale price took 2.7894973754882812e-05s
Believability | Calculation of trust value for Potato trading volume and wholesale price took 6.67572021484375e-06s
INFO | --- Analysis for predicting-potato-trading-volume-and-wholesale-prices took 2.900331497192383s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of apples took 4.029273986816406e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of apples took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of apples took 0.26185131072998047s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of apples took 0.02039361000061035s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of apples took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of apples took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of apples took 2.6226043701171875e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of apples took 6.9141387939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-apples took 2.955925464630127s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of barley took 4.38690185546875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of barley took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of barley took 0.26120615005493164s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of barley took 0.020937442779541016s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of barley took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of barley took 0.0006883144378662109s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of barley took 3.147125244140625e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of barley took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-barley took 2.905970573425293s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of bean took 4.029273986816406e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of bean took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of bean took 0.2724494934082031s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of bean took 0.02015376091003418s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of bean took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of bean took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of bean took 2.7418136596679688e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of bean took 6.67572021484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-bean took 3.080470561981201s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cabbage took 4.1961669921875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cabbage took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cabbage took 0.2690122127532959s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cabbage took 0.02071237564086914s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cabbage took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cabbage took 0.0008013248443603516s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cabbage took 3.337860107421875e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cabbage took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cabbage took 3.001075029373169s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of corn took 4.076957702636719e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of corn took 0.0002872943878173828s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of corn took 0.2595245838165283s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of corn took 0.02062535285949707s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of corn took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of corn took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of corn took 3.170967102050781e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of corn took 8.821487426757812e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-corn took 2.968357563018799s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of crab took 4.1484832763671875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of crab took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of crab took 0.28089475631713867s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of crab took 0.020450115203857422s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of crab took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of crab took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of crab took 2.8371810913085938e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of crab took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-crab took 2.8643107414245605s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cucumber took 5.435943603515625e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cucumber took 0.0002865791320800781s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cucumber took 0.2559373378753662s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cucumber took 0.020637989044189453s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cucumber took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cucumber took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cucumber took 2.956390380859375e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cucumber took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cucumber took 2.948525905609131s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of lettuce took 4.0531158447265625e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of lettuce took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of lettuce took 0.258472204208374s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of lettuce took 0.020298004150390625s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of lettuce took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of lettuce took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of lettuce took 2.8133392333984375e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of lettuce took 6.67572021484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-lettuce2 took 2.934957265853882s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of onion took 4.076957702636719e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of onion took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of onion took 0.2817549705505371s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of onion took 0.020270586013793945s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of onion took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of onion took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of onion took 2.86102294921875e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of onion took 5.9604644775390625e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-onion took 2.959324359893799s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of oyster mushroom took 4.076957702636719e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of oyster mushroom took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of oyster mushroom took 0.26090216636657715s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of oyster mushroom took 0.020581722259521484s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of oyster mushroom took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of oyster mushroom took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of oyster mushroom took 3.0517578125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of oyster mushroom took 7.62939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-oyster-mushroom took 2.9160008430480957s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of potato took 5.650520324707031e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of potato took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of potato took 0.2727327346801758s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of potato took 0.02034282684326172s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of potato took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of potato took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of potato took 3.170967102050781e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of potato took 7.867813110351562e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-potato took 2.929546594619751s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of radish took 4.076957702636719e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of radish took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of radish took 0.2701230049133301s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of radish took 0.02051711082458496s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of radish took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of radish took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of radish took 3.0279159545898438e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of radish took 8.106231689453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-radish2 took 3.044614315032959s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of rice plant took 3.981590270996094e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of rice plant took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of rice plant took 0.2539236545562744s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of rice plant took 0.02091503143310547s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of rice plant took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of rice plant took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of rice plant took 3.170967102050781e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of rice plant took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-rice-plant took 2.9491147994995117s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of watermelon took 4.0531158447265625e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of watermelon took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of watermelon took 0.2657175064086914s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of watermelon took 0.02041339874267578s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of watermelon took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of watermelon took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of watermelon took 2.8371810913085938e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of watermelon took 7.62939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-watermelon took 2.855339527130127s
Availability | SPARQL endpoint availability check for prefix.cc took 4.100799560546875e-05s
Availability | VoID file availability check for prefix.cc took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for prefix.cc took 0.28061676025390625s
Reputation | Calculation of the PageRank for prefix.cc took 0.020160675048828125s
Interlinking | Calculation of Degree of Connection for prefix.cc took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for prefix.cc took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for prefix.cc took 3.504753112792969e-05s
Believability | Calculation of trust value for prefix.cc took 5.4836273193359375e-06s
INFO | --- Analysis for prefix-cc took 3.2637810707092285s
Availability | SPARQL endpoint availability check for PREJUST4WOMEN Knowledge Graph took 1.8611524105072021s
Availability | VoID file availability check for PREJUST4WOMEN Knowledge Graph took 0.0004248619079589844s
Completeness | Calculation of interlinking completeness for PREJUST4WOMEN Knowledge Graph took 0.2744135856628418s
Reputation | Calculation of the PageRank for PREJUST4WOMEN Knowledge Graph took 0.02051067352294922s
Interlinking | Calculation of Degree of Connection for PREJUST4WOMEN Knowledge Graph took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PREJUST4WOMEN Knowledge Graph took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for PREJUST4WOMEN Knowledge Graph took 5.6743621826171875e-05s
Believability | Calculation of trust value for PREJUST4WOMEN Knowledge Graph took 5.9604644775390625e-06s
INFO | --- Analysis for PREJUST4WOMAN_PROJECT took 8.087328672409058s
Availability | SPARQL endpoint availability check for PreLex took 4.656571388244629s
Availability | VoID file availability check for PreLex took 0.0005702972412109375s
Completeness | Calculation of interlinking completeness for PreLex took 0.2946908473968506s
Reputation | Calculation of the PageRank for PreLex took 0.020749807357788086s
Interlinking | Calculation of Degree of Connection for PreLex took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for PreLex took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for PreLex took 7.200241088867188e-05s
Believability | Calculation of trust value for PreLex took 5.0067901611328125e-06s
INFO | --- Analysis for prelex took 29.039294004440308s
Availability | SPARQL endpoint availability check for Prelinger Archives took 2.631477117538452s
Availability | VoID file availability check for Prelinger Archives took 0.0006773471832275391s
Completeness | Calculation of interlinking completeness for Prelinger Archives took 0.28931307792663574s
Reputation | Calculation of the PageRank for Prelinger Archives took 0.020581960678100586s
Interlinking | Calculation of Degree of Connection for Prelinger Archives took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Prelinger Archives took 0.0007781982421875s
Interlinking | Calculation of Clustering coefficient for Prelinger Archives took 3.266334533691406e-05s
Believability | Calculation of trust value for Prelinger Archives took 7.867813110351562e-06s
INFO | --- Analysis for prelinger_archives took 10.963287591934204s
Availability | SPARQL endpoint availability check for PreMOn (Predicate Model for Ontologies) took 0.22151446342468262s
Availability | VoID file availability check for PreMOn (Predicate Model for Ontologies) took 0.0006270408630371094s
Extra | Recovery of all triples for PreMOn (Predicate Model for Ontologies) took 5.006497383117676s
Performance | Total latancy measurement for PreMOn (Predicate Model for Ontologies) took 0.43970394134521484s
Amount of data | Number of triples check for PreMOn (Predicate Model for Ontologies) took 0.07885885238647461s
Interoperability | New terms check for PreMOn (Predicate Model for Ontologies) took 1.90891432762146s
Versatility | Languages check for PreMOn (Predicate Model for Ontologies) took 59.09727644920349s
Interpretability | Number of blank nodes check for PreMOn (Predicate Model for Ontologies) took 0.0737466812133789s
Security | Check HTTPS for PreMOn (Predicate Model for Ontologies) took 0.07475972175598145s
Interpretability | RDF structures check for PreMOn (Predicate Model for Ontologies) took 0.07883930206298828s
Versatility | Serialization formats check for PreMOn (Predicate Model for Ontologies) took 0.12340927124023438s
Availability | RDF dump link check for PreMOn (Predicate Model for Ontologies) took 0.07815217971801758s
License | MR license check for PreMOn (Predicate Model for Ontologies) took 0.16192317008972168s
License | HR license check for PreMOn (Predicate Model for Ontologies) took 0.7421872615814209s
Amount of data | Number of property check for PreMOn (Predicate Model for Ontologies) took 0.1101539134979248s
Understandability | Number of label check for PreMOn (Predicate Model for Ontologies) took 0.07880902290344238s
Understandability | URI regex check for PreMOn (Predicate Model for Ontologies) took 0.1606593132019043s
Understandability | Vocabs check for PreMOn (Predicate Model for Ontologies) took 0.08436965942382812s
Verifiability | Authors check for PreMOn (Predicate Model for Ontologies) took 0.0783381462097168s
Verifiability | Publishers check for PreMOn (Predicate Model for Ontologies) took 0.15591835975646973s
Performance | Throughput check for PreMOn (Predicate Model for Ontologies) took 10.48291563987732s
Amount of data | Check the number of entities for PreMOn (Predicate Model for Ontologies) took 0.00010371208190917969s
Verifiability | Contribs. check for PreMOn (Predicate Model for Ontologies) took 0.07962918281555176s
Interlinking | sameAs chians check for PreMOn (Predicate Model for Ontologies) took 0.07657361030578613s
Interlinking | skos check for PreMOn (Predicate Model for Ontologies) took 0.08925676345825195s
Interlinking | skos check for PreMOn (Predicate Model for Ontologies) took 0.09587907791137695s
Timeliness | dataset update frequency check for PreMOn (Predicate Model for Ontologies) took 0.08307147026062012s
Currency | Creation date check for PreMOn (Predicate Model for Ontologies) took 0.19626426696777344s
Currency | Modification date check for PreMOn (Predicate Model for Ontologies) took 0.19031023979187012s
Rep.Conc. | URIs length for PreMOn (Predicate Model for Ontologies) took 3.570645809173584s
Interoperability | New vocabularies check for PreMOn (Predicate Model for Ontologies) took 6.67572021484375e-06s
Consistency | Deprecated classes/propertiers check for PreMOn (Predicate Model for Ontologies) took 0.10874247550964355s
Accuracy | Check Empty annotation labels for PreMOn (Predicate Model for Ontologies) took 0.9966928958892822s
Accuracy | Check White space in annotation for PreMOn (Predicate Model for Ontologies) took 0.08456850051879883s
Accuracy | Check Datatype consistency for PreMOn (Predicate Model for Ontologies) took 0.08251428604125977s
Consistency | Disjoint class check for PreMOn (Predicate Model for Ontologies) took 0.10887432098388672s
Consistency | Check Misplaced properties for PreMOn (Predicate Model for Ontologies) took 1.7354695796966553s
Consistency | Misplaced classes for PreMOn (Predicate Model for Ontologies) took 0.362642765045166s
Consistency | Check Ontology hijacking for PreMOn (Predicate Model for Ontologies) took 2.397038221359253s
Consistency | Check Invalid usage of undefined classes for PreMOn (Predicate Model for Ontologies) took 1.175234317779541s
Consistency | Check Invalid usage of undefined properties for PreMOn (Predicate Model for Ontologies) took 2.7677438259124756s
Conciseness | Check Extensional conciseness for PreMOn (Predicate Model for Ontologies) took 0.09223341941833496s
Conciseness | Check Intensional conciseness for PreMOn (Predicate Model for Ontologies) took 0.1094210147857666s
Security | Sign check for PreMOn (Predicate Model for Ontologies) took 0.0481867790222168s
Availability | Check URIs Dereferenciability for PreMOn (Predicate Model for Ontologies) took 871.6355087757111s
Completeness | Calculation of interlinking completeness for PreMOn (Predicate Model for Ontologies) took 0.4629373550415039s
Reputation | Calculation of the PageRank for PreMOn (Predicate Model for Ontologies) took 0.021471261978149414s
Interlinking | Calculation of Degree of Connection for PreMOn (Predicate Model for Ontologies) took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for PreMOn (Predicate Model for Ontologies) took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for PreMOn (Predicate Model for Ontologies) took 5.91278076171875e-05s
Interoperability | Check the re-using of existing vocabs for PreMOn (Predicate Model for Ontologies) took 1.9073486328125e-06s
Believability | Calculation of trust value for PreMOn (Predicate Model for Ontologies) took 8.344650268554688e-06s
INFO | --- Analysis for premon took 986.1643669605255s
Availability | SPARQL endpoint availability check for Previsible took 4.3392181396484375e-05s
Availability | VoID file availability check for Previsible took 0.0002884864807128906s
Completeness | Calculation of interlinking completeness for Previsible took 0.2736480236053467s
Reputation | Calculation of the PageRank for Previsible took 0.020776033401489258s
Interlinking | Calculation of Degree of Connection for Previsible took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Previsible took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Previsible took 1.3589859008789062e-05s
Believability | Calculation of trust value for Previsible took 9.298324584960938e-06s
INFO | --- Analysis for Previsible took 2.8476173877716064s
Availability | SPARQL endpoint availability check for Princeton Library FindingAids took 4.6253204345703125e-05s
Availability | VoID file availability check for Princeton Library FindingAids took 0.0006780624389648438s
Completeness | Calculation of interlinking completeness for Princeton Library FindingAids took 0.27009010314941406s
Reputation | Calculation of the PageRank for Princeton Library FindingAids took 0.020506620407104492s
Interlinking | Calculation of Degree of Connection for Princeton Library FindingAids took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Princeton Library FindingAids took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Princeton Library FindingAids took 5.91278076171875e-05s
Believability | Calculation of trust value for Princeton Library FindingAids took 6.67572021484375e-06s
INFO | --- Analysis for princeton-library-findingaids took 8.799672365188599s
Availability | SPARQL endpoint availability check for PrinParLat in LiLa took 0.584719181060791s
Availability | VoID file availability check for PrinParLat in LiLa took 0.0006256103515625s
Completeness | Calculation of interlinking completeness for PrinParLat in LiLa took 0.2736847400665283s
Reputation | Calculation of the PageRank for PrinParLat in LiLa took 0.020636558532714844s
Interlinking | Calculation of Degree of Connection for PrinParLat in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for PrinParLat in LiLa took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for PrinParLat in LiLa took 3.8623809814453125e-05s
Believability | Calculation of trust value for PrinParLat in LiLa took 6.4373016357421875e-06s
INFO | --- Analysis for PrinParLat took 4.284710884094238s
Availability | SPARQL endpoint availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.3150796890258789s
Availability | VoID file availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.26215577125549316s
Reputation | Calculation of the PageRank for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0206296443939209s
Interlinking | Calculation of Degree of Connection for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 7.843971252441406e-05s
Believability | Calculation of trust value for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 6.9141387939453125e-06s
INFO | --- Analysis for printed-book-auction-catalogues took 3.166752815246582s
Availability | SPARQL endpoint availability check for Prior Panel took 4.410743713378906e-05s
Availability | VoID file availability check for Prior Panel took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for Prior Panel took 0.2518641948699951s
Reputation | Calculation of the PageRank for Prior Panel took 0.020808696746826172s
Interlinking | Calculation of Degree of Connection for Prior Panel took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Prior Panel took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Prior Panel took 3.552436828613281e-05s
Believability | Calculation of trust value for Prior Panel took 7.3909759521484375e-06s
INFO | --- Analysis for Prior_Panel took 2.398991107940674s
Availability | SPARQL endpoint availability check for Procedimientos, trámites y servicios took 7.724761962890625e-05s
Availability | VoID file availability check for Procedimientos, trámites y servicios took 0.0003209114074707031s
Completeness | Calculation of interlinking completeness for Procedimientos, trámites y servicios took 0.2754795551300049s
Reputation | Calculation of the PageRank for Procedimientos, trámites y servicios took 0.02064967155456543s
Interlinking | Calculation of Degree of Connection for Procedimientos, trámites y servicios took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Procedimientos, trámites y servicios took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Procedimientos, trámites y servicios took 3.0517578125e-05s
Believability | Calculation of trust value for Procedimientos, trámites y servicios took 6.67572021484375e-06s
INFO | --- Analysis for procedimientos-tramites-servicios-zaragoza took 2.8902201652526855s
Availability | SPARQL endpoint availability check for Procomún SPARQL took 4.076957702636719e-05s
Availability | VoID file availability check for Procomún SPARQL took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for Procomún SPARQL took 0.2577478885650635s
Reputation | Calculation of the PageRank for Procomún SPARQL took 0.02084803581237793s
Interlinking | Calculation of Degree of Connection for Procomún SPARQL took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Procomún SPARQL took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Procomún SPARQL took 3.1948089599609375e-05s
Believability | Calculation of trust value for Procomún SPARQL took 6.198883056640625e-06s
INFO | --- Analysis for procomun-sparql took 3.0164151191711426s
Availability | SPARQL endpoint availability check for PROD - JISC Project Directory in RDF took 4.100799560546875e-05s
Availability | VoID file availability check for PROD - JISC Project Directory in RDF took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for PROD - JISC Project Directory in RDF took 0.24111175537109375s
Reputation | Calculation of the PageRank for PROD - JISC Project Directory in RDF took 0.020529985427856445s
Interlinking | Calculation of Degree of Connection for PROD - JISC Project Directory in RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PROD - JISC Project Directory in RDF took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for PROD - JISC Project Directory in RDF took 3.218650817871094e-05s
Believability | Calculation of trust value for PROD - JISC Project Directory in RDF took 5.9604644775390625e-06s
INFO | --- Analysis for prod-jisc-project-directory-in-rdf took 2.921382188796997s
Availability | SPARQL endpoint availability check for ProductDB took 1.9458396434783936s
Availability | VoID file availability check for ProductDB took 0.0006661415100097656s
Completeness | Calculation of interlinking completeness for ProductDB took 0.2741060256958008s
Reputation | Calculation of the PageRank for ProductDB took 0.020586013793945312s
Interlinking | Calculation of Degree of Connection for ProductDB took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ProductDB took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for ProductDB took 7.414817810058594e-05s
Believability | Calculation of trust value for ProductDB took 3.409385681152344e-05s
INFO | --- Analysis for productdb took 8.161411762237549s
Availability | SPARQL endpoint availability check for Product Types Ontology took 6.246566772460938e-05s
Availability | VoID file availability check for Product Types Ontology took 0.0003204345703125s
Completeness | Calculation of interlinking completeness for Product Types Ontology took 0.2534506320953369s
Reputation | Calculation of the PageRank for Product Types Ontology took 0.020789623260498047s
Interlinking | Calculation of Degree of Connection for Product Types Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Product Types Ontology took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for Product Types Ontology took 8.177757263183594e-05s
Believability | Calculation of trust value for Product Types Ontology took 7.62939453125e-06s
INFO | --- Analysis for productontology took 3.271397352218628s
Availability | SPARQL endpoint availability check for Prospects and Trends (GNOSS) took 4.267692565917969e-05s
Availability | VoID file availability check for Prospects and Trends (GNOSS) took 0.0005240440368652344s
Completeness | Calculation of interlinking completeness for Prospects and Trends (GNOSS) took 0.29001331329345703s
Reputation | Calculation of the PageRank for Prospects and Trends (GNOSS) took 0.020340919494628906s
Interlinking | Calculation of Degree of Connection for Prospects and Trends (GNOSS) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Prospects and Trends (GNOSS) took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Prospects and Trends (GNOSS) took 0.00010156631469726562s
Believability | Calculation of trust value for Prospects and Trends (GNOSS) took 5.7220458984375e-06s
INFO | --- Analysis for prospects-and-trends-gnoss took 2.9989118576049805s
Availability | SPARQL endpoint availability check for provenanceweb took 0.032784461975097656s
Availability | VoID file availability check for provenanceweb took 0.0002760887145996094s
Completeness | Calculation of interlinking completeness for provenanceweb took 0.26080894470214844s
Reputation | Calculation of the PageRank for provenanceweb took 0.020741701126098633s
Interlinking | Calculation of Degree of Connection for provenanceweb took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for provenanceweb took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for provenanceweb took 7.700920104980469e-05s
Believability | Calculation of trust value for provenanceweb took 6.198883056640625e-06s
INFO | --- Analysis for provenanceweb took 45.97046375274658s
Availability | SPARQL endpoint availability check for Proyecto Apadrina,  Marketing Punto de Venta took 4.57763671875e-05s
Availability | VoID file availability check for Proyecto Apadrina,  Marketing Punto de Venta took 0.0006668567657470703s
Completeness | Calculation of interlinking completeness for Proyecto Apadrina,  Marketing Punto de Venta took 0.2722964286804199s
Reputation | Calculation of the PageRank for Proyecto Apadrina,  Marketing Punto de Venta took 0.02060675621032715s
Interlinking | Calculation of Degree of Connection for Proyecto Apadrina,  Marketing Punto de Venta took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Proyecto Apadrina,  Marketing Punto de Venta took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for Proyecto Apadrina,  Marketing Punto de Venta took 0.0001049041748046875s
Believability | Calculation of trust value for Proyecto Apadrina,  Marketing Punto de Venta took 7.152557373046875e-06s
INFO | --- Analysis for proyectoapadrina took 2.942861795425415s
Availability | SPARQL endpoint availability check for Product Scheme Classifications Catalogue took 25.384315967559814s
Availability | VoID file availability check for Product Scheme Classifications Catalogue took 0.0008976459503173828s
Completeness | Calculation of interlinking completeness for Product Scheme Classifications Catalogue took 0.7137942314147949s
Reputation | Calculation of the PageRank for Product Scheme Classifications Catalogue took 0.021178483963012695s
Interlinking | Calculation of Degree of Connection for Product Scheme Classifications Catalogue took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Product Scheme Classifications Catalogue took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Product Scheme Classifications Catalogue took 4.1484832763671875e-05s
Believability | Calculation of trust value for Product Scheme Classifications Catalogue took 5.245208740234375e-06s
INFO | --- Analysis for pscs-catalogue took 122.00180506706238s
Availability | SPARQL endpoint availability check for Polythematic Structured Subject Heading System took 4.315376281738281e-05s
Availability | VoID file availability check for Polythematic Structured Subject Heading System took 0.0005795955657958984s
Completeness | Calculation of interlinking completeness for Polythematic Structured Subject Heading System took 0.267836332321167s
Reputation | Calculation of the PageRank for Polythematic Structured Subject Heading System took 0.02032756805419922s
Interlinking | Calculation of Degree of Connection for Polythematic Structured Subject Heading System took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Polythematic Structured Subject Heading System took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Polythematic Structured Subject Heading System took 7.414817810058594e-05s
Believability | Calculation of trust value for Polythematic Structured Subject Heading System took 7.867813110351562e-06s
INFO | --- Analysis for psh-subject-headings took 3.42592716217041s
Availability | SPARQL endpoint availability check for Depression took 0.28916382789611816s
Availability | VoID file availability check for Depression took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Depression took 0.2601504325866699s
Reputation | Calculation of the PageRank for Depression took 0.020294904708862305s
Interlinking | Calculation of Degree of Connection for Depression took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Depression took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Depression took 2.8848648071289062e-05s
Believability | Calculation of trust value for Depression took 6.198883056640625e-06s
INFO | --- Analysis for Psychology took 2.7557342052459717s
Availability | SPARQL endpoint availability check for PubChem RDF took 4.172325134277344e-05s
Availability | VoID file availability check for PubChem RDF took 0.0010838508605957031s
Completeness | Calculation of interlinking completeness for PubChem RDF took 0.2695295810699463s
Reputation | Calculation of the PageRank for PubChem RDF took 0.020282506942749023s
Interlinking | Calculation of Degree of Connection for PubChem RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PubChem RDF took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for PubChem RDF took 3.719329833984375e-05s
Believability | Calculation of trust value for PubChem RDF took 6.67572021484375e-06s
INFO | --- Analysis for PubChem_RDF took 5.258853197097778s
Availability | SPARQL endpoint availability check for Public Record Office Victoria Semantic Wiki took 3.933906555175781e-05s
Availability | VoID file availability check for Public Record Office Victoria Semantic Wiki took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for Public Record Office Victoria Semantic Wiki took 0.2695612907409668s
Reputation | Calculation of the PageRank for Public Record Office Victoria Semantic Wiki took 0.02029275894165039s
Interlinking | Calculation of Degree of Connection for Public Record Office Victoria Semantic Wiki took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Public Record Office Victoria Semantic Wiki took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Public Record Office Victoria Semantic Wiki took 2.7894973754882812e-05s
Believability | Calculation of trust value for Public Record Office Victoria Semantic Wiki took 7.152557373046875e-06s
INFO | --- Analysis for public-record-office-victoria-semantic-wiki took 2.997302770614624s
Availability | SPARQL endpoint availability check for Public Spending in Greece took 0.5132942199707031s
Availability | VoID file availability check for Public Spending in Greece took 0.0005757808685302734s
Completeness | Calculation of interlinking completeness for Public Spending in Greece took 0.2619750499725342s
Reputation | Calculation of the PageRank for Public Spending in Greece took 0.020704269409179688s
Interlinking | Calculation of Degree of Connection for Public Spending in Greece took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Public Spending in Greece took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Public Spending in Greece took 8.0108642578125e-05s
Believability | Calculation of trust value for Public Spending in Greece took 7.867813110351562e-06s
INFO | --- Analysis for public-spending-in-greece took 7.722569704055786s
Availability | SPARQL endpoint availability check for Publications of Charles University in Prague took 3.981590270996094e-05s
Availability | VoID file availability check for Publications of Charles University in Prague took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for Publications of Charles University in Prague took 0.26889705657958984s
Reputation | Calculation of the PageRank for Publications of Charles University in Prague took 0.02058577537536621s
Interlinking | Calculation of Degree of Connection for Publications of Charles University in Prague took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Publications of Charles University in Prague took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Publications of Charles University in Prague took 2.9802322387695312e-05s
Believability | Calculation of trust value for Publications of Charles University in Prague took 6.4373016357421875e-06s
INFO | --- Analysis for publications-of-charles-university-in-prague took 3.0331077575683594s
Availability | SPARQL endpoint availability check for Publications Office Authority tables took 0.29503536224365234s
Availability | VoID file availability check for Publications Office Authority tables took 0.0005736351013183594s
Extra | Recovery of all triples for Publications Office Authority tables took 300.0288736820221s
Performance | Total latancy measurement for Publications Office Authority tables took 0.6411807537078857s
Amount of data | Number of triples check for Publications Office Authority tables took 245.32227277755737s
Interoperability | New terms check for Publications Office Authority tables took 166.18344950675964s
Versatility | Languages check for Publications Office Authority tables took 300.04530096054077s
Interpretability | Number of blank nodes check for Publications Office Authority tables took 9.698942184448242s
Security | Check HTTPS for Publications Office Authority tables took 0.32604455947875977s
Interpretability | RDF structures check for Publications Office Authority tables took 0.32889509201049805s
Versatility | Serialization formats check for Publications Office Authority tables took 21.067371129989624s
Availability | RDF dump link check for Publications Office Authority tables took 0.23707914352416992s
License | MR license check for Publications Office Authority tables took 0.24793267250061035s
License | HR license check for Publications Office Authority tables took 300.0173659324646s
Amount of data | Number of property check for Publications Office Authority tables took 0.1900317668914795s
Understandability | Number of label check for Publications Office Authority tables took 5.934430360794067s
Understandability | URI regex check for Publications Office Authority tables took 0.2734229564666748s
Understandability | Vocabs check for Publications Office Authority tables took 0.12102103233337402s
Verifiability | Authors check for Publications Office Authority tables took 0.37566471099853516s
Verifiability | Publishers check for Publications Office Authority tables took 0.22232961654663086s
Performance | Throughput check for Publications Office Authority tables took 10.825490474700928s
Amount of data | Check the number of entities for Publications Office Authority tables took 8.368492126464844e-05s
Verifiability | Contribs. check for Publications Office Authority tables took 0.17703890800476074s
Interlinking | sameAs chians check for Publications Office Authority tables took 12.417234420776367s
Interlinking | skos check for Publications Office Authority tables took 0.6884171962738037s
Interlinking | skos check for Publications Office Authority tables took 0.37441205978393555s
Timeliness | dataset update frequency check for Publications Office Authority tables took 0.2916686534881592s
Currency | Creation date check for Publications Office Authority tables took 0.6607482433319092s
Currency | Modification date check for Publications Office Authority tables took 0.2555880546569824s
Rep.Conc. | URIs length for Publications Office Authority tables took 600.2357134819031s
Interoperability | New vocabularies check for Publications Office Authority tables took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Publications Office Authority tables took 0.18951177597045898s
Accuracy | Check Functional Property for Publications Office Authority tables took 0.1733238697052002s
Accuracy | Check Inverse Functional Property for Publications Office Authority tables took 0.14706754684448242s
Accuracy | Check Empty annotation labels for Publications Office Authority tables took 141.34753251075745s
Accuracy | Check White space in annotation for Publications Office Authority tables took 3.2124080657958984s
Consistency | Disjoint class check for Publications Office Authority tables took 0.22039794921875s
Consistency | Check Misplaced properties for Publications Office Authority tables took 300.91588282585144s
Consistency | Misplaced classes for Publications Office Authority tables took 0.42925500869750977s
Consistency | Check Ontology hijacking for Publications Office Authority tables took 128.65403699874878s
Consistency | Check Invalid usage of undefined properties for Publications Office Authority tables took 301.38901686668396s
Conciseness | Check Extensional conciseness for Publications Office Authority tables took 0.00019025802612304688s
Conciseness | Check Intensional conciseness for Publications Office Authority tables took 0.7746973037719727s
Security | Sign check for Publications Office Authority tables took 0.20585131645202637s
Completeness | Calculation of interlinking completeness for Publications Office Authority tables took 1.736198902130127s
Reputation | Calculation of the PageRank for Publications Office Authority tables took 0.031027793884277344s
Interlinking | Calculation of Degree of Connection for Publications Office Authority tables took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Publications Office Authority tables took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Publications Office Authority tables took 4.673004150390625e-05s
Interoperability | Check the re-using of existing vocabs for Publications Office Authority tables took 1.9073486328125e-06s
Believability | Calculation of trust value for Publications Office Authority tables took 4.76837158203125e-06s
INFO | --- Analysis for publications_office_authority_tables took 16242.948271274567s
Availability | SPARQL endpoint availability check for Publikace Univerzity Karlovy v Praze took 4.744529724121094e-05s
Availability | VoID file availability check for Publikace Univerzity Karlovy v Praze took 0.0002923011779785156s
Completeness | Calculation of interlinking completeness for Publikace Univerzity Karlovy v Praze took 0.28202390670776367s
Reputation | Calculation of the PageRank for Publikace Univerzity Karlovy v Praze took 0.020908117294311523s
Interlinking | Calculation of Degree of Connection for Publikace Univerzity Karlovy v Praze took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Publikace Univerzity Karlovy v Praze took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Publikace Univerzity Karlovy v Praze took 3.0279159545898438e-05s
Believability | Calculation of trust value for Publikace Univerzity Karlovy v Praze took 6.4373016357421875e-06s
INFO | --- Analysis for publikace-univerzity-karlovy-v-praze took 4.721661806106567s
Availability | SPARQL endpoint availability check for QBOAirbase took 4.291534423828125e-05s
Availability | VoID file availability check for QBOAirbase took 0.0008754730224609375s
Completeness | Calculation of interlinking completeness for QBOAirbase took 0.7295777797698975s
Reputation | Calculation of the PageRank for QBOAirbase took 0.020563602447509766s
Interlinking | Calculation of Degree of Connection for QBOAirbase took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for QBOAirbase took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for QBOAirbase took 8.0108642578125e-05s
Believability | Calculation of trust value for QBOAirbase took 9.5367431640625e-06s
INFO | --- Analysis for qboairbase took 139.96419715881348s
Availability | SPARQL endpoint availability check for qualitywebdata.org took 4.0531158447265625e-05s
Availability | VoID file availability check for qualitywebdata.org took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for qualitywebdata.org took 0.7327842712402344s
Reputation | Calculation of the PageRank for qualitywebdata.org took 0.020365238189697266s
Interlinking | Calculation of Degree of Connection for qualitywebdata.org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for qualitywebdata.org took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for qualitywebdata.org took 3.0517578125e-05s
Believability | Calculation of trust value for qualitywebdata.org took 7.3909759521484375e-06s
INFO | --- Analysis for qualitywebdata-org took 5.6063618659973145s
Availability | SPARQL endpoint availability check for Qualité de l'air took 4.1484832763671875e-05s
Availability | VoID file availability check for Qualité de l'air took 0.0005958080291748047s
Completeness | Calculation of interlinking completeness for Qualité de l'air took 0.2763783931732178s
Reputation | Calculation of the PageRank for Qualité de l'air took 0.02075791358947754s
Interlinking | Calculation of Degree of Connection for Qualité de l'air took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Qualité de l'air took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air took 3.2901763916015625e-05s
Believability | Calculation of trust value for Qualité de l'air took 7.62939453125e-06s
INFO | --- Analysis for Qualité_de_l'air took 3.7629785537719727s
Availability | SPARQL endpoint availability check for Qualité de l'air dans le monde took 4.291534423828125e-05s
Availability | VoID file availability check for Qualité de l'air dans le monde took 0.0007016658782958984s
Completeness | Calculation of interlinking completeness for Qualité de l'air dans le monde took 0.26541686058044434s
Reputation | Calculation of the PageRank for Qualité de l'air dans le monde took 0.020584821701049805s
Interlinking | Calculation of Degree of Connection for Qualité de l'air dans le monde took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Qualité de l'air dans le monde took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air dans le monde took 3.1948089599609375e-05s
Believability | Calculation of trust value for Qualité de l'air dans le monde took 7.3909759521484375e-06s
INFO | --- Analysis for Qualité_de_l'air_dans_le_monde took 49.60287928581238s
Availability | SPARQL endpoint availability check for Querolus in LiLa took 0.5964126586914062s
Availability | VoID file availability check for Querolus in LiLa took 0.0007116794586181641s
Completeness | Calculation of interlinking completeness for Querolus in LiLa took 0.2658240795135498s
Reputation | Calculation of the PageRank for Querolus in LiLa took 0.0203549861907959s
Interlinking | Calculation of Degree of Connection for Querolus in LiLa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Querolus in LiLa took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Querolus in LiLa took 3.552436828613281e-05s
Believability | Calculation of trust value for Querolus in LiLa took 6.9141387939453125e-06s
INFO | --- Analysis for Querolus took 4.4551637172698975s
Availability | SPARQL endpoint availability check for Quotations Book took 4.100799560546875e-05s
Availability | VoID file availability check for Quotations Book took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for Quotations Book took 0.265594482421875s
Reputation | Calculation of the PageRank for Quotations Book took 0.02043604850769043s
Interlinking | Calculation of Degree of Connection for Quotations Book took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Quotations Book took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Quotations Book took 3.0279159545898438e-05s
Believability | Calculation of trust value for Quotations Book took 5.9604644775390625e-06s
INFO | --- Analysis for quotations_book took 4.234352111816406s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 5.1975250244140625e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.7388818264007568s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.02026081085205078s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 3.0994415283203125e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 7.62939453125e-06s
INFO | --- Analysis for r4r took 3.935419797897339s
Availability | SPARQL endpoint availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.7619435787200928s
Availability | VoID file availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0005753040313720703s
Completeness | Calculation of interlinking completeness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.25154662132263184s
Reputation | Calculation of the PageRank for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.020290851593017578s
Interlinking | Calculation of Degree of Connection for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.673004150390625e-05s
Believability | Calculation of trust value for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 6.198883056640625e-06s
INFO | --- Analysis for racai-legalnero took 4.007476091384888s
Availability | SPARQL endpoint availability check for Romanian CoRoLa Word Embeddings took 4.291534423828125e-05s
Availability | VoID file availability check for Romanian CoRoLa Word Embeddings took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for Romanian CoRoLa Word Embeddings took 0.24346208572387695s
Reputation | Calculation of the PageRank for Romanian CoRoLa Word Embeddings took 0.0205841064453125s
Interlinking | Calculation of Degree of Connection for Romanian CoRoLa Word Embeddings took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Romanian CoRoLa Word Embeddings took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Romanian CoRoLa Word Embeddings took 2.8371810913085938e-05s
Believability | Calculation of trust value for Romanian CoRoLa Word Embeddings took 5.0067901611328125e-06s
INFO | --- Analysis for racai-llod-corola-we took 2.950406551361084s
Availability | SPARQL endpoint availability check for PARSEME-Ro corpus took 1.8708562850952148s
Availability | VoID file availability check for PARSEME-Ro corpus took 0.0006403923034667969s
Completeness | Calculation of interlinking completeness for PARSEME-Ro corpus took 0.27988553047180176s
Reputation | Calculation of the PageRank for PARSEME-Ro corpus took 0.020281553268432617s
Interlinking | Calculation of Degree of Connection for PARSEME-Ro corpus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for PARSEME-Ro corpus took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for PARSEME-Ro corpus took 2.8371810913085938e-05s
Believability | Calculation of trust value for PARSEME-Ro corpus took 5.9604644775390625e-06s
INFO | --- Analysis for racai-llod-parseme-ro took 4.60775089263916s
Availability | SPARQL endpoint availability check for RoLEX took 1.6258232593536377s
Availability | VoID file availability check for RoLEX took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for RoLEX took 0.27245450019836426s
Reputation | Calculation of the PageRank for RoLEX took 0.020944595336914062s
Interlinking | Calculation of Degree of Connection for RoLEX took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for RoLEX took 0.0009057521820068359s
Interlinking | Calculation of Clustering coefficient for RoLEX took 3.1948089599609375e-05s
Believability | Calculation of trust value for RoLEX took 7.62939453125e-06s
INFO | --- Analysis for racai-llod-rolex took 4.390803813934326s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 5.173683166503906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0010447502136230469s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.2582707405090332s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.020979881286621094s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 2.956390380859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 5.7220458984375e-06s
INFO | --- Analysis for racai-llod-romanian-treebank took 2.653883934020996s
Availability | SPARQL endpoint availability check for JSON Romanian Wordnet took 4.0531158447265625e-05s
Availability | VoID file availability check for JSON Romanian Wordnet took 0.00029587745666503906s
Completeness | Calculation of interlinking completeness for JSON Romanian Wordnet took 0.2661252021789551s
Reputation | Calculation of the PageRank for JSON Romanian Wordnet took 0.020102500915527344s
Interlinking | Calculation of Degree of Connection for JSON Romanian Wordnet took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for JSON Romanian Wordnet took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for JSON Romanian Wordnet took 2.8133392333984375e-05s
Believability | Calculation of trust value for JSON Romanian Wordnet took 7.62939453125e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-json took 2.5212512016296387s
Availability | SPARQL endpoint availability check for LMF Romanian Wordnet took 4.2438507080078125e-05s
Availability | VoID file availability check for LMF Romanian Wordnet took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for LMF Romanian Wordnet took 0.26284146308898926s
Reputation | Calculation of the PageRank for LMF Romanian Wordnet took 0.020223617553710938s
Interlinking | Calculation of Degree of Connection for LMF Romanian Wordnet took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LMF Romanian Wordnet took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for LMF Romanian Wordnet took 2.6226043701171875e-05s
Believability | Calculation of trust value for LMF Romanian Wordnet took 6.198883056640625e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-lmf took 2.515378952026367s
Availability | SPARQL endpoint availability check for Turtle-RDF Romanian Wordnet took 4.100799560546875e-05s
Availability | VoID file availability check for Turtle-RDF Romanian Wordnet took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for Turtle-RDF Romanian Wordnet took 0.25808143615722656s
Reputation | Calculation of the PageRank for Turtle-RDF Romanian Wordnet took 0.020403385162353516s
Interlinking | Calculation of Degree of Connection for Turtle-RDF Romanian Wordnet took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Turtle-RDF Romanian Wordnet took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Turtle-RDF Romanian Wordnet took 2.8133392333984375e-05s
Believability | Calculation of trust value for Turtle-RDF Romanian Wordnet took 7.152557373046875e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-ttl took 2.6157007217407227s
Availability | SPARQL endpoint availability check for ROBIN Technical Acquisition Speech Corpus took 0.2879467010498047s
Availability | VoID file availability check for ROBIN Technical Acquisition Speech Corpus took 0.0006356239318847656s
Completeness | Calculation of interlinking completeness for ROBIN Technical Acquisition Speech Corpus took 0.26749205589294434s
Reputation | Calculation of the PageRank for ROBIN Technical Acquisition Speech Corpus took 0.020370960235595703s
Interlinking | Calculation of Degree of Connection for ROBIN Technical Acquisition Speech Corpus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ROBIN Technical Acquisition Speech Corpus took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for ROBIN Technical Acquisition Speech Corpus took 2.7179718017578125e-05s
Believability | Calculation of trust value for ROBIN Technical Acquisition Speech Corpus took 6.4373016357421875e-06s
INFO | --- Analysis for racai-llod-rtasc took 3.5461583137512207s
Availability | SPARQL endpoint availability check for SiMoNERo - the Romanian medical treebank took 0.2806992530822754s
Availability | VoID file availability check for SiMoNERo - the Romanian medical treebank took 0.0006058216094970703s
Completeness | Calculation of interlinking completeness for SiMoNERo - the Romanian medical treebank took 0.2664029598236084s
Reputation | Calculation of the PageRank for SiMoNERo - the Romanian medical treebank took 0.02025771141052246s
Interlinking | Calculation of Degree of Connection for SiMoNERo - the Romanian medical treebank took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SiMoNERo - the Romanian medical treebank took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for SiMoNERo - the Romanian medical treebank took 2.8371810913085938e-05s
Believability | Calculation of trust value for SiMoNERo - the Romanian medical treebank took 6.67572021484375e-06s
INFO | --- Analysis for racai-llod-simonero took 3.0059354305267334s
Availability | SPARQL endpoint availability check for Rådata nå! took 0.269087553024292s
Availability | VoID file availability check for Rådata nå! took 0.00028777122497558594s
Completeness | Calculation of interlinking completeness for Rådata nå! took 0.2641010284423828s
Reputation | Calculation of the PageRank for Rådata nå! took 0.020224809646606445s
Interlinking | Calculation of Degree of Connection for Rådata nå! took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Rådata nå! took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Rådata nå! took 7.963180541992188e-05s
Believability | Calculation of trust value for Rådata nå! took 5.245208740234375e-06s
INFO | --- Analysis for radatana took 4.52787709236145s
Availability | SPARQL endpoint availability check for "Rainis and Aspazija" Linked Digital Collection took 4.267692565917969e-05s
Availability | VoID file availability check for "Rainis and Aspazija" Linked Digital Collection took 0.0006515979766845703s
Completeness | Calculation of interlinking completeness for "Rainis and Aspazija" Linked Digital Collection took 0.2599375247955322s
Reputation | Calculation of the PageRank for "Rainis and Aspazija" Linked Digital Collection took 0.02012038230895996s
Interlinking | Calculation of Degree of Connection for "Rainis and Aspazija" Linked Digital Collection took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for "Rainis and Aspazija" Linked Digital Collection took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for "Rainis and Aspazija" Linked Digital Collection took 3.600120544433594e-05s
Believability | Calculation of trust value for "Rainis and Aspazija" Linked Digital Collection took 6.198883056640625e-06s
INFO | --- Analysis for rainis-and-aspazija-linked-digital-collection took 16.66467809677124s
Availability | SPARQL endpoint availability check for Raphael Research Resource took 4.00543212890625e-05s
Availability | VoID file availability check for Raphael Research Resource took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for Raphael Research Resource took 0.2713596820831299s
Reputation | Calculation of the PageRank for Raphael Research Resource took 0.02004861831665039s
Interlinking | Calculation of Degree of Connection for Raphael Research Resource took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Raphael Research Resource took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Raphael Research Resource took 3.695487976074219e-05s
Believability | Calculation of trust value for Raphael Research Resource took 7.3909759521484375e-06s
INFO | --- Analysis for raphaelresearchresource took 2.911350965499878s
Availability | SPARQL endpoint availability check for Ravensburg Local Shopping Graph took 10.71238112449646s
Availability | VoID file availability check for Ravensburg Local Shopping Graph took 0.0004436969757080078s
Completeness | Calculation of interlinking completeness for Ravensburg Local Shopping Graph took 0.3034498691558838s
Reputation | Calculation of the PageRank for Ravensburg Local Shopping Graph took 0.02042388916015625s
Interlinking | Calculation of Degree of Connection for Ravensburg Local Shopping Graph took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ravensburg Local Shopping Graph took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Ravensburg Local Shopping Graph took 2.8848648071289062e-05s
Believability | Calculation of trust value for Ravensburg Local Shopping Graph took 7.152557373046875e-06s
INFO | --- Analysis for ravensburg-local-shopping-graph took 25.512882471084595s
Availability | SPARQL endpoint availability check for Polish LGU financial statements took 392.10687613487244s
Availability | VoID file availability check for Polish LGU financial statements took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for Polish LGU financial statements took 0.7065930366516113s
Reputation | Calculation of the PageRank for Polish LGU financial statements took 0.020758628845214844s
Interlinking | Calculation of Degree of Connection for Polish LGU financial statements took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Polish LGU financial statements took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Polish LGU financial statements took 3.814697265625e-05s
Believability | Calculation of trust value for Polish LGU financial statements took 6.67572021484375e-06s
INFO | --- Analysis for Rb_PL_LGU took 667.0774488449097s
Availability | SPARQL endpoint availability check for RCAHMS Archaeological Objects Thesaurus took 5.245208740234375e-05s
Availability | VoID file availability check for RCAHMS Archaeological Objects Thesaurus took 0.00031304359436035156s
Completeness | Calculation of interlinking completeness for RCAHMS Archaeological Objects Thesaurus took 0.6906015872955322s
Reputation | Calculation of the PageRank for RCAHMS Archaeological Objects Thesaurus took 0.0204312801361084s
Interlinking | Calculation of Degree of Connection for RCAHMS Archaeological Objects Thesaurus took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for RCAHMS Archaeological Objects Thesaurus took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for RCAHMS Archaeological Objects Thesaurus took 2.956390380859375e-05s
Believability | Calculation of trust value for RCAHMS Archaeological Objects Thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for rcahms-archaeological-objects-thesaurus took 4.390675783157349s
Availability | SPARQL endpoint availability check for RCAHMS Maritime Craft Thesaurus took 7.581710815429688e-05s
Availability | VoID file availability check for RCAHMS Maritime Craft Thesaurus took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for RCAHMS Maritime Craft Thesaurus took 0.28388500213623047s
Reputation | Calculation of the PageRank for RCAHMS Maritime Craft Thesaurus took 0.020487546920776367s
Interlinking | Calculation of Degree of Connection for RCAHMS Maritime Craft Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RCAHMS Maritime Craft Thesaurus took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for RCAHMS Maritime Craft Thesaurus took 3.6716461181640625e-05s
Believability | Calculation of trust value for RCAHMS Maritime Craft Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for rcahms-maritime-craft-thesaurus took 4.754580020904541s
Availability | SPARQL endpoint availability check for RCAHMS Monument Types Thesaurus took 3.886222839355469e-05s
Availability | VoID file availability check for RCAHMS Monument Types Thesaurus took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for RCAHMS Monument Types Thesaurus took 0.6864287853240967s
Reputation | Calculation of the PageRank for RCAHMS Monument Types Thesaurus took 0.023517131805419922s
Interlinking | Calculation of Degree of Connection for RCAHMS Monument Types Thesaurus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for RCAHMS Monument Types Thesaurus took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for RCAHMS Monument Types Thesaurus took 2.765655517578125e-05s
Believability | Calculation of trust value for RCAHMS Monument Types Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for rcahms-monument-types-thesaurus took 4.687558174133301s
Availability | SPARQL endpoint availability check for RCAHMW Monument Types Thesaurus took 4.6253204345703125e-05s
Availability | VoID file availability check for RCAHMW Monument Types Thesaurus took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for RCAHMW Monument Types Thesaurus took 0.2865486145019531s
Reputation | Calculation of the PageRank for RCAHMW Monument Types Thesaurus took 0.020236492156982422s
Interlinking | Calculation of Degree of Connection for RCAHMW Monument Types Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RCAHMW Monument Types Thesaurus took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for RCAHMW Monument Types Thesaurus took 2.8371810913085938e-05s
Believability | Calculation of trust value for RCAHMW Monument Types Thesaurus took 6.198883056640625e-06s
INFO | --- Analysis for rcahmw-monument-types-thesaurus took 3.4758718013763428s
Availability | SPARQL endpoint availability check for RCAHMW Periods List took 6.651878356933594e-05s
Availability | VoID file availability check for RCAHMW Periods List took 0.0003020763397216797s
Completeness | Calculation of interlinking completeness for RCAHMW Periods List took 0.2593190670013428s
Reputation | Calculation of the PageRank for RCAHMW Periods List took 0.020276308059692383s
Interlinking | Calculation of Degree of Connection for RCAHMW Periods List took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RCAHMW Periods List took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for RCAHMW Periods List took 3.147125244140625e-05s
Believability | Calculation of trust value for RCAHMW Periods List took 5.9604644775390625e-06s
INFO | --- Analysis for rcahmw-periods-list took 3.761456251144409s
Availability | SPARQL endpoint availability check for RDF Book Mashup took 4.410743713378906e-05s
Availability | VoID file availability check for RDF Book Mashup took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for RDF Book Mashup took 0.2813565731048584s
Reputation | Calculation of the PageRank for RDF Book Mashup took 0.020374774932861328s
Interlinking | Calculation of Degree of Connection for RDF Book Mashup took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RDF Book Mashup took 0.0008308887481689453s
Interlinking | Calculation of Clustering coefficient for RDF Book Mashup took 8.797645568847656e-05s
Believability | Calculation of trust value for RDF Book Mashup took 1.5974044799804688e-05s
INFO | --- Analysis for rdf-book-mashup took 3.4832820892333984s
Availability | SPARQL endpoint availability check for Last.FM RDFization of Events, Artists, and Users took 0.0006473064422607422s
Availability | VoID file availability check for Last.FM RDFization of Events, Artists, and Users took 0.00023555755615234375s
Completeness | Calculation of interlinking completeness for Last.FM RDFization of Events, Artists, and Users took 0.2726624011993408s
Reputation | Calculation of the PageRank for Last.FM RDFization of Events, Artists, and Users took 0.02026510238647461s
Interlinking | Calculation of Degree of Connection for Last.FM RDFization of Events, Artists, and Users took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Last.FM RDFization of Events, Artists, and Users took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Last.FM RDFization of Events, Artists, and Users took 9.799003601074219e-05s
Believability | Calculation of trust value for Last.FM RDFization of Events, Artists, and Users took 8.106231689453125e-06s
INFO | --- Analysis for rdfize-lastfm took 2.4200007915496826s
Availability | SPARQL endpoint availability check for RDFLicense took 262.2283501625061s
Availability | VoID file availability check for RDFLicense took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for RDFLicense took 0.7192814350128174s
Reputation | Calculation of the PageRank for RDFLicense took 0.020751476287841797s
Interlinking | Calculation of Degree of Connection for RDFLicense took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for RDFLicense took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for RDFLicense took 3.7670135498046875e-05s
Believability | Calculation of trust value for RDFLicense took 9.059906005859375e-06s
INFO | --- Analysis for rdflicense took 537.1610155105591s
Availability | SPARQL endpoint availability check for RDFohloh took 4.506111145019531e-05s
Availability | VoID file availability check for RDFohloh took 0.00030541419982910156s
Completeness | Calculation of interlinking completeness for RDFohloh took 0.6957371234893799s
Reputation | Calculation of the PageRank for RDFohloh took 0.02038288116455078s
Interlinking | Calculation of Degree of Connection for RDFohloh took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for RDFohloh took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for RDFohloh took 8.726119995117188e-05s
Believability | Calculation of trust value for RDFohloh took 7.3909759521484375e-06s
INFO | --- Analysis for rdfohloh took 9.71634840965271s
Availability | SPARQL endpoint availability check for Reactome RDF took 0.9751942157745361s
Availability | VoID file availability check for Reactome RDF took 0.0004425048828125s
Completeness | Calculation of interlinking completeness for Reactome RDF took 0.2753028869628906s
Reputation | Calculation of the PageRank for Reactome RDF took 0.020237445831298828s
Interlinking | Calculation of Degree of Connection for Reactome RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Reactome RDF took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Reactome RDF took 3.5762786865234375e-05s
Believability | Calculation of trust value for Reactome RDF took 6.9141387939453125e-06s
INFO | --- Analysis for reactome-rdf took 5.36542010307312s
Availability | SPARQL endpoint availability check for Rechtspraak.nl took 0.6418726444244385s
Availability | VoID file availability check for Rechtspraak.nl took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for Rechtspraak.nl took 0.30240964889526367s
Reputation | Calculation of the PageRank for Rechtspraak.nl took 0.020053625106811523s
Interlinking | Calculation of Degree of Connection for Rechtspraak.nl took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Rechtspraak.nl took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Rechtspraak.nl took 8.96453857421875e-05s
Believability | Calculation of trust value for Rechtspraak.nl took 5.0067901611328125e-06s
INFO | --- Analysis for rechtspraak took 4.423440933227539s
Availability | SPARQL endpoint availability check for Red Uno Internacional (Santillana) took 4.267692565917969e-05s
Availability | VoID file availability check for Red Uno Internacional (Santillana) took 0.0006594657897949219s
Completeness | Calculation of interlinking completeness for Red Uno Internacional (Santillana) took 0.2894163131713867s
Reputation | Calculation of the PageRank for Red Uno Internacional (Santillana) took 0.02048015594482422s
Interlinking | Calculation of Degree of Connection for Red Uno Internacional (Santillana) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Red Uno Internacional (Santillana) took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Red Uno Internacional (Santillana) took 0.00010919570922851562s
Believability | Calculation of trust value for Red Uno Internacional (Santillana) took 5.4836273193359375e-06s
INFO | --- Analysis for red-uno-internacional-santillana took 8.650679588317871s
Availability | SPARQL endpoint availability check for reference.data.gov.uk took 0.1441802978515625s
Availability | VoID file availability check for reference.data.gov.uk took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for reference.data.gov.uk took 0.2708091735839844s
Reputation | Calculation of the PageRank for reference.data.gov.uk took 0.020260334014892578s
Interlinking | Calculation of Degree of Connection for reference.data.gov.uk took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for reference.data.gov.uk took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for reference.data.gov.uk took 0.00015497207641601562s
Believability | Calculation of trust value for reference.data.gov.uk took 5.4836273193359375e-06s
INFO | --- Analysis for reference-data-gov-uk took 2.6683220863342285s
Availability | SPARQL endpoint availability check for Regiony took 4.1484832763671875e-05s
Availability | VoID file availability check for Regiony took 0.00022554397583007812s
Completeness | Calculation of interlinking completeness for Regiony took 0.2610034942626953s
Reputation | Calculation of the PageRank for Regiony took 0.02035069465637207s
Interlinking | Calculation of Degree of Connection for Regiony took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Regiony took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Regiony took 3.075599670410156e-05s
Believability | Calculation of trust value for Regiony took 7.152557373046875e-06s
INFO | --- Analysis for regiony took 2.923779249191284s
Availability | SPARQL endpoint availability check for RELD took 262.01849603652954s
Availability | VoID file availability check for RELD took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for RELD took 0.3103904724121094s
Reputation | Calculation of the PageRank for RELD took 0.020558595657348633s
Interlinking | Calculation of Degree of Connection for RELD took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for RELD took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for RELD took 3.600120544433594e-05s
Believability | Calculation of trust value for RELD took 6.198883056640625e-06s
INFO | --- Analysis for RELD took 538.7254846096039s
Availability | SPARQL endpoint availability check for Repository for Linked Open Archival Data took 0.1943070888519287s
Availability | VoID file availability check for Repository for Linked Open Archival Data took 0.0005612373352050781s
Extra | Recovery of all triples for Repository for Linked Open Archival Data took 1.4660768508911133s
Performance | Total latancy measurement for Repository for Linked Open Archival Data took 0.4747183322906494s
Amount of data | Number of triples check for Repository for Linked Open Archival Data took 1.7786505222320557s
Interoperability | New terms check for Repository for Linked Open Archival Data took 1.6469295024871826s
Versatility | Languages check for Repository for Linked Open Archival Data took 28.9712917804718s
Interpretability | Number of blank nodes check for Repository for Linked Open Archival Data took 2.3628146648406982s
Security | Check HTTPS for Repository for Linked Open Archival Data took 0.20440196990966797s
Interpretability | RDF structures check for Repository for Linked Open Archival Data took 0.5512664318084717s
Versatility | Serialization formats check for Repository for Linked Open Archival Data took 0.4629547595977783s
Availability | RDF dump link check for Repository for Linked Open Archival Data took 0.27378273010253906s
License | MR license check for Repository for Linked Open Archival Data took 0.675635576248169s
License | HR license check for Repository for Linked Open Archival Data took 11.857496738433838s
Amount of data | Number of property check for Repository for Linked Open Archival Data took 0.11342763900756836s
Understandability | Number of label check for Repository for Linked Open Archival Data took 1.5888376235961914s
Understandability | URI regex check for Repository for Linked Open Archival Data took 0.6875245571136475s
Understandability | Vocabs check for Repository for Linked Open Archival Data took 0.14125704765319824s
Verifiability | Authors check for Repository for Linked Open Archival Data took 0.23308730125427246s
Verifiability | Publishers check for Repository for Linked Open Archival Data took 0.24605727195739746s
Performance | Throughput check for Repository for Linked Open Archival Data took 10.551522493362427s
Amount of data | Check the number of entities for Repository for Linked Open Archival Data took 7.128715515136719e-05s
Verifiability | Contribs. check for Repository for Linked Open Archival Data took 0.06515216827392578s
Interlinking | sameAs chians check for Repository for Linked Open Archival Data took 0.16889476776123047s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.3883345127105713s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.061347007751464844s
Timeliness | dataset update frequency check for Repository for Linked Open Archival Data took 0.36655116081237793s
Currency | Creation date check for Repository for Linked Open Archival Data took 0.15607094764709473s
Currency | Modification date check for Repository for Linked Open Archival Data took 0.1654665470123291s
Rep.Conc. | URIs length for Repository for Linked Open Archival Data took 3.661179304122925s
Interoperability | New vocabularies check for Repository for Linked Open Archival Data took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Repository for Linked Open Archival Data took 0.08873295783996582s
Accuracy | Check Functional Property for Repository for Linked Open Archival Data took 0.09931778907775879s
Accuracy | Check Inverse Functional Property for Repository for Linked Open Archival Data took 0.07862091064453125s
Accuracy | Check Empty annotation labels for Repository for Linked Open Archival Data took 0.4758002758026123s
Accuracy | Check White space in annotation for Repository for Linked Open Archival Data took 0.028844594955444336s
Accuracy | Check Datatype consistency for Repository for Linked Open Archival Data took 0.028314828872680664s
Consistency | Disjoint class check for Repository for Linked Open Archival Data took 0.2761247158050537s
Consistency | Check Misplaced properties for Repository for Linked Open Archival Data took 2.3994178771972656s
Consistency | Misplaced classes for Repository for Linked Open Archival Data took 0.18048858642578125s
Consistency | Check Ontology hijacking for Repository for Linked Open Archival Data took 1.514007806777954s
Consistency | Check Invalid usage of undefined classes for Repository for Linked Open Archival Data took 1.1542580127716064s
Consistency | Check Invalid usage of undefined properties for Repository for Linked Open Archival Data took 3.7555320262908936s
Conciseness | Check Extensional conciseness for Repository for Linked Open Archival Data took 0.0331416130065918s
Conciseness | Check Intensional conciseness for Repository for Linked Open Archival Data took 0.12591266632080078s
Security | Sign check for Repository for Linked Open Archival Data took 0.864072322845459s
Availability | Check URIs Dereferenciability for Repository for Linked Open Archival Data took 2490.402414083481s
Completeness | Calculation of interlinking completeness for Repository for Linked Open Archival Data took 1.228992223739624s
Reputation | Calculation of the PageRank for Repository for Linked Open Archival Data took 0.02106308937072754s
Interlinking | Calculation of Degree of Connection for Repository for Linked Open Archival Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Repository for Linked Open Archival Data took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Repository for Linked Open Archival Data took 5.221366882324219e-05s
Interoperability | Check the re-using of existing vocabs for Repository for Linked Open Archival Data took 1.430511474609375e-06s
Believability | Calculation of trust value for Repository for Linked Open Archival Data took 1.1920928955078125e-05s
INFO | --- Analysis for reload took 2653.5517404079437s
Availability | SPARQL endpoint availability check for Land use merced dataset took 8.106231689453125e-05s
Availability | VoID file availability check for Land use merced dataset took 0.0007724761962890625s
Completeness | Calculation of interlinking completeness for Land use merced dataset took 0.688286304473877s
Reputation | Calculation of the PageRank for Land use merced dataset took 0.02074122428894043s
Interlinking | Calculation of Degree of Connection for Land use merced dataset took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Land use merced dataset took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Land use merced dataset took 2.956390380859375e-05s
Believability | Calculation of trust value for Land use merced dataset took 6.67572021484375e-06s
INFO | --- Analysis for remote_Sensing took 15.725640773773193s
Availability | SPARQL endpoint availability check for Renewable Energy Generators took 1.6391308307647705s
Availability | VoID file availability check for Renewable Energy Generators took 0.0006537437438964844s
Completeness | Calculation of interlinking completeness for Renewable Energy Generators took 0.7032485008239746s
Reputation | Calculation of the PageRank for Renewable Energy Generators took 0.020537137985229492s
Interlinking | Calculation of Degree of Connection for Renewable Energy Generators took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Renewable Energy Generators took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Renewable Energy Generators took 4.315376281738281e-05s
Believability | Calculation of trust value for Renewable Energy Generators took 4.5299530029296875e-06s
INFO | --- Analysis for renewable_energy_generators took 12.096662998199463s
Availability | SPARQL endpoint availability check for research.data.gov.uk took 0.05192446708679199s
Availability | VoID file availability check for research.data.gov.uk took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for research.data.gov.uk took 0.2534663677215576s
Reputation | Calculation of the PageRank for research.data.gov.uk took 0.0207059383392334s
Interlinking | Calculation of Degree of Connection for research.data.gov.uk took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for research.data.gov.uk took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for research.data.gov.uk took 9.775161743164062e-05s
Believability | Calculation of trust value for research.data.gov.uk took 5.7220458984375e-06s
INFO | --- Analysis for research-data-gov-uk took 4.328474998474121s
Availability | SPARQL endpoint availability check for Research object in Agricolture and Food of the University of Naples took 4.3392181396484375e-05s
Availability | VoID file availability check for Research object in Agricolture and Food of the University of Naples took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for Research object in Agricolture and Food of the University of Naples took 0.25011157989501953s
Reputation | Calculation of the PageRank for Research object in Agricolture and Food of the University of Naples took 0.020545244216918945s
Interlinking | Calculation of Degree of Connection for Research object in Agricolture and Food of the University of Naples took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Research object in Agricolture and Food of the University of Naples took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Research object in Agricolture and Food of the University of Naples took 3.0517578125e-05s
Believability | Calculation of trust value for Research object in Agricolture and Food of the University of Naples took 7.3909759521484375e-06s
INFO | --- Analysis for research-object-in-agricolture-and-food-of-the-university-of-naples took 4.686422109603882s
Availability | SPARQL endpoint availability check for Restaurantes took 4.029273986816406e-05s
Availability | VoID file availability check for Restaurantes took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for Restaurantes took 0.2718470096588135s
Reputation | Calculation of the PageRank for Restaurantes took 0.020598888397216797s
Interlinking | Calculation of Degree of Connection for Restaurantes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Restaurantes took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Restaurantes took 2.86102294921875e-05s
Believability | Calculation of trust value for Restaurantes took 7.3909759521484375e-06s
INFO | --- Analysis for restaurantes-zaragoza took 3.8579416275024414s
Availability | SPARQL endpoint availability check for Reuters-128 NIF NER Corpus took 4.2438507080078125e-05s
Availability | VoID file availability check for Reuters-128 NIF NER Corpus took 0.0005741119384765625s
Completeness | Calculation of interlinking completeness for Reuters-128 NIF NER Corpus took 0.7688958644866943s
Reputation | Calculation of the PageRank for Reuters-128 NIF NER Corpus took 0.020597457885742188s
Interlinking | Calculation of Degree of Connection for Reuters-128 NIF NER Corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Reuters-128 NIF NER Corpus took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Reuters-128 NIF NER Corpus took 6.556510925292969e-05s
Believability | Calculation of trust value for Reuters-128 NIF NER Corpus took 6.198883056640625e-06s
INFO | --- Analysis for reuters-128-nif-ner-corpus took 4.6814563274383545s
Availability | SPARQL endpoint availability check for Revista Excelencias Turísticas took 0.04942178726196289s
Availability | VoID file availability check for Revista Excelencias Turísticas took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for Revista Excelencias Turísticas took 0.2738966941833496s
Reputation | Calculation of the PageRank for Revista Excelencias Turísticas took 0.020358800888061523s
Interlinking | Calculation of Degree of Connection for Revista Excelencias Turísticas took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Revista Excelencias Turísticas took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Revista Excelencias Turísticas took 2.8848648071289062e-05s
Believability | Calculation of trust value for Revista Excelencias Turísticas took 7.867813110351562e-06s
INFO | --- Analysis for revistas_turismo took 3.0366628170013428s
Availability | SPARQL endpoint availability check for Revyu.com - Review Anything took 0.2529489994049072s
Availability | VoID file availability check for Revyu.com - Review Anything took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for Revyu.com - Review Anything took 0.28249239921569824s
Reputation | Calculation of the PageRank for Revyu.com - Review Anything took 0.020725488662719727s
Interlinking | Calculation of Degree of Connection for Revyu.com - Review Anything took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Revyu.com - Review Anything took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Revyu.com - Review Anything took 0.00012135505676269531s
Believability | Calculation of trust value for Revyu.com - Review Anything took 8.58306884765625e-06s
INFO | --- Analysis for revyu took 3.1167800426483154s
Availability | SPARQL endpoint availability check for sdafsadf took 0.28352904319763184s
Availability | VoID file availability check for sdafsadf took 0.00028824806213378906s
Completeness | Calculation of interlinking completeness for sdafsadf took 0.7495052814483643s
Reputation | Calculation of the PageRank for sdafsadf took 0.02030348777770996s
Interlinking | Calculation of Degree of Connection for sdafsadf took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for sdafsadf took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for sdafsadf took 3.0517578125e-05s
Believability | Calculation of trust value for sdafsadf took 6.67572021484375e-06s
INFO | --- Analysis for rgsdfg took 3.5874428749084473s
Availability | SPARQL endpoint availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 4.172325134277344e-05s
Availability | VoID file availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 0.00044465065002441406s
Completeness | Calculation of interlinking completeness for RDFizing and Interlinking the EuroStat Data Set Effort took 0.27614402770996094s
Reputation | Calculation of the PageRank for RDFizing and Interlinking the EuroStat Data Set Effort took 0.02040719985961914s
Interlinking | Calculation of Degree of Connection for RDFizing and Interlinking the EuroStat Data Set Effort took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for RDFizing and Interlinking the EuroStat Data Set Effort took 4.696846008300781e-05s
Believability | Calculation of trust value for RDFizing and Interlinking the EuroStat Data Set Effort took 7.3909759521484375e-06s
INFO | --- Analysis for riese took 2.491121768951416s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection Data took 4.00543212890625e-05s
Availability | VoID file availability check for Rijksmuseum Collection Data took 0.000286102294921875s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection Data took 0.26767897605895996s
Reputation | Calculation of the PageRank for Rijksmuseum Collection Data took 0.020507097244262695s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection Data took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection Data took 2.956390380859375e-05s
Believability | Calculation of trust value for Rijksmuseum Collection Data took 6.198883056640625e-06s
INFO | --- Analysis for rijksmuseum took 2.8900060653686523s
Availability | SPARQL endpoint availability check for Répertoire International des Sources Musicales - RISM took 0.6100702285766602s
Availability | VoID file availability check for Répertoire International des Sources Musicales - RISM took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for Répertoire International des Sources Musicales - RISM took 0.28290700912475586s
Reputation | Calculation of the PageRank for Répertoire International des Sources Musicales - RISM took 0.020241498947143555s
Interlinking | Calculation of Degree of Connection for Répertoire International des Sources Musicales - RISM took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Répertoire International des Sources Musicales - RISM took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Répertoire International des Sources Musicales - RISM took 4.3392181396484375e-05s
Believability | Calculation of trust value for Répertoire International des Sources Musicales - RISM took 8.344650268554688e-06s
INFO | --- Analysis for rism took 4.1188154220581055s
Availability | SPARQL endpoint availability check for RISM Authority data took 0.1783444881439209s
Availability | VoID file availability check for RISM Authority data took 0.0010292530059814453s
Completeness | Calculation of interlinking completeness for RISM Authority data took 0.2591359615325928s
Reputation | Calculation of the PageRank for RISM Authority data took 0.020346879959106445s
Interlinking | Calculation of Degree of Connection for RISM Authority data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for RISM Authority data took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for RISM Authority data took 4.506111145019531e-05s
Believability | Calculation of trust value for RISM Authority data took 5.0067901611328125e-06s
INFO | --- Analysis for rism-authorities took 3.5991902351379395s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.27158522605895996s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.020550251007080078s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 3.170967102050781e-05s
Believability | Calculation of trust value for engineering equipment ontology took 6.4373016357421875e-06s
INFO | --- Analysis for rk took 2.3518927097320557s
Availability | SPARQL endpoint availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.04270172119140625s
Availability | VoID file availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for Association for Computing Machinery (ACM) (RKBExplorer) took 0.25423145294189453s
Reputation | Calculation of the PageRank for Association for Computing Machinery (ACM) (RKBExplorer) took 0.020400524139404297s
Interlinking | Calculation of Degree of Connection for Association for Computing Machinery (ACM) (RKBExplorer) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Association for Computing Machinery (ACM) (RKBExplorer) took 0.00023293495178222656s
Believability | Calculation of trust value for Association for Computing Machinery (ACM) (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-acm took 2.501417875289917s
Availability | SPARQL endpoint availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.05021953582763672s
Availability | VoID file availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.0004343986511230469s
Completeness | Calculation of interlinking completeness for Budapest University of Technology and Economics (RKBExplorer) took 0.26921582221984863s
Reputation | Calculation of the PageRank for Budapest University of Technology and Economics (RKBExplorer) took 0.020775318145751953s
Interlinking | Calculation of Degree of Connection for Budapest University of Technology and Economics (RKBExplorer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Budapest University of Technology and Economics (RKBExplorer) took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Budapest University of Technology and Economics (RKBExplorer) took 0.00014472007751464844s
Believability | Calculation of trust value for Budapest University of Technology and Economics (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-budapest took 2.480863332748413s
Availability | SPARQL endpoint availability check for CiteSeer (Research Index) (RKBExplorer) took 0.06775546073913574s
Availability | VoID file availability check for CiteSeer (Research Index) (RKBExplorer) took 0.0004711151123046875s
Completeness | Calculation of interlinking completeness for CiteSeer (Research Index) (RKBExplorer) took 0.24950194358825684s
Reputation | Calculation of the PageRank for CiteSeer (Research Index) (RKBExplorer) took 0.020473003387451172s
Interlinking | Calculation of Degree of Connection for CiteSeer (Research Index) (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CiteSeer (Research Index) (RKBExplorer) took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for CiteSeer (Research Index) (RKBExplorer) took 0.0002009868621826172s
Believability | Calculation of trust value for CiteSeer (Research Index) (RKBExplorer) took 6.4373016357421875e-06s
INFO | --- Analysis for rkb-explorer-citeseer took 2.5421903133392334s
Availability | SPARQL endpoint availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.04292178153991699s
Availability | VoID file availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.27532958984375s
Reputation | Calculation of the PageRank for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.02062225341796875s
Interlinking | Calculation of Degree of Connection for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0001633167266845703s
Believability | Calculation of trust value for Community R&D Information Service (CORDIS) (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-cordis took 2.55503511428833s
Availability | SPARQL endpoint availability check for Resilient Computing Courseware (RKBExplorer) took 0.0530853271484375s
Availability | VoID file availability check for Resilient Computing Courseware (RKBExplorer) took 0.00042939186096191406s
Completeness | Calculation of interlinking completeness for Resilient Computing Courseware (RKBExplorer) took 0.2767198085784912s
Reputation | Calculation of the PageRank for Resilient Computing Courseware (RKBExplorer) took 0.02056097984313965s
Interlinking | Calculation of Degree of Connection for Resilient Computing Courseware (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Resilient Computing Courseware (RKBExplorer) took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Resilient Computing Courseware (RKBExplorer) took 0.000156402587890625s
Believability | Calculation of trust value for Resilient Computing Courseware (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-courseware took 2.49973201751709s
Availability | SPARQL endpoint availability check for Street level crime reports for England and Wales took 0.05114603042602539s
Availability | VoID file availability check for Street level crime reports for England and Wales took 0.0004639625549316406s
Completeness | Calculation of interlinking completeness for Street level crime reports for England and Wales took 0.2542436122894287s
Reputation | Calculation of the PageRank for Street level crime reports for England and Wales took 0.020764827728271484s
Interlinking | Calculation of Degree of Connection for Street level crime reports for England and Wales took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Street level crime reports for England and Wales took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Street level crime reports for England and Wales took 3.814697265625e-05s
Believability | Calculation of trust value for Street level crime reports for England and Wales took 5.4836273193359375e-06s
INFO | --- Analysis for rkb-explorer-crime took 2.4630727767944336s
Availability | SPARQL endpoint availability check for crm took 4.1961669921875e-05s
Availability | VoID file availability check for crm took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for crm took 0.2601172924041748s
Reputation | Calculation of the PageRank for crm took 0.020421981811523438s
Interlinking | Calculation of Degree of Connection for crm took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for crm took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for crm took 3.0279159545898438e-05s
Believability | Calculation of trust value for crm took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-crm took 2.824354648590088s
Availability | SPARQL endpoint availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0385894775390625s
Availability | VoID file availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.2632317543029785s
Reputation | Calculation of the PageRank for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.020406484603881836s
Interlinking | Calculation of Degree of Connection for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0008654594421386719s
Interlinking | Calculation of Clustering coefficient for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0001342296600341797s
Believability | Calculation of trust value for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-curriculum took 2.3902151584625244s
Availability | SPARQL endpoint availability check for Technische Universität Darmstadt (RKBExplorer) took 0.038725852966308594s
Availability | VoID file availability check for Technische Universität Darmstadt (RKBExplorer) took 0.00022530555725097656s
Completeness | Calculation of interlinking completeness for Technische Universität Darmstadt (RKBExplorer) took 0.25501537322998047s
Reputation | Calculation of the PageRank for Technische Universität Darmstadt (RKBExplorer) took 0.02038097381591797s
Interlinking | Calculation of Degree of Connection for Technische Universität Darmstadt (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Technische Universität Darmstadt (RKBExplorer) took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Technische Universität Darmstadt (RKBExplorer) took 5.0067901611328125e-05s
Believability | Calculation of trust value for Technische Universität Darmstadt (RKBExplorer) took 5.9604644775390625e-06s
INFO | --- Analysis for rkb-explorer-darmstadt took 2.435605764389038s
Availability | SPARQL endpoint availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.04467964172363281s
Availability | VoID file availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for DBLP Computer Science Bibliography (RKBExplorer) took 0.7052924633026123s
Reputation | Calculation of the PageRank for DBLP Computer Science Bibliography (RKBExplorer) took 0.02016139030456543s
Interlinking | Calculation of Degree of Connection for DBLP Computer Science Bibliography (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DBLP Computer Science Bibliography (RKBExplorer) took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for DBLP Computer Science Bibliography (RKBExplorer) took 0.0002346038818359375s
Believability | Calculation of trust value for DBLP Computer Science Bibliography (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-dblp took 2.8843162059783936s
Availability | SPARQL endpoint availability check for Deep Blue (RKBExplorer) took 0.049218177795410156s
Availability | VoID file availability check for Deep Blue (RKBExplorer) took 0.0004558563232421875s
Completeness | Calculation of interlinking completeness for Deep Blue (RKBExplorer) took 0.2736659049987793s
Reputation | Calculation of the PageRank for Deep Blue (RKBExplorer) took 0.020086288452148438s
Interlinking | Calculation of Degree of Connection for Deep Blue (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Deep Blue (RKBExplorer) took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Deep Blue (RKBExplorer) took 7.224082946777344e-05s
Believability | Calculation of trust value for Deep Blue (RKBExplorer) took 5.4836273193359375e-06s
INFO | --- Analysis for rkb-explorer-deepblue took 2.499821662902832s
Availability | SPARQL endpoint availability check for DEPLOY (RKBExplorer) took 0.04932999610900879s
Availability | VoID file availability check for DEPLOY (RKBExplorer) took 0.0004646778106689453s
Completeness | Calculation of interlinking completeness for DEPLOY (RKBExplorer) took 0.2671530246734619s
Reputation | Calculation of the PageRank for DEPLOY (RKBExplorer) took 0.020359277725219727s
Interlinking | Calculation of Degree of Connection for DEPLOY (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DEPLOY (RKBExplorer) took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for DEPLOY (RKBExplorer) took 9.608268737792969e-05s
Believability | Calculation of trust value for DEPLOY (RKBExplorer) took 5.7220458984375e-06s
INFO | --- Analysis for rkb-explorer-deploy took 2.5169129371643066s
Availability | SPARQL endpoint availability check for digitaleconomy took 0.050228118896484375s
Availability | VoID file availability check for digitaleconomy took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for digitaleconomy took 0.27398061752319336s
Reputation | Calculation of the PageRank for digitaleconomy took 0.02048349380493164s
Interlinking | Calculation of Degree of Connection for digitaleconomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for digitaleconomy took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for digitaleconomy took 2.8133392333984375e-05s
Believability | Calculation of trust value for digitaleconomy took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-digitaleconomy took 2.4754953384399414s
Availability | SPARQL endpoint availability check for dotAC (RKBExplorer) took 0.03252530097961426s
Availability | VoID file availability check for dotAC (RKBExplorer) took 0.00034236907958984375s
Completeness | Calculation of interlinking completeness for dotAC (RKBExplorer) took 0.2579355239868164s
Reputation | Calculation of the PageRank for dotAC (RKBExplorer) took 0.020648956298828125s
Interlinking | Calculation of Degree of Connection for dotAC (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for dotAC (RKBExplorer) took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for dotAC (RKBExplorer) took 0.0001461505889892578s
Believability | Calculation of trust value for dotAC (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-dotac took 2.4864115715026855s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 0.04897022247314453s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.2755012512207031s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.02050614356994629s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 4.267692565917969e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-ecs took 2.8845858573913574s
Availability | SPARQL endpoint availability check for enaktingpsi took 3.933906555175781e-05s
Availability | VoID file availability check for enaktingpsi took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for enaktingpsi took 0.2812776565551758s
Reputation | Calculation of the PageRank for enaktingpsi took 0.02120232582092285s
Interlinking | Calculation of Degree of Connection for enaktingpsi took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for enaktingpsi took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for enaktingpsi took 2.9087066650390625e-05s
Believability | Calculation of trust value for enaktingpsi took 5.245208740234375e-06s
INFO | --- Analysis for rkb-explorer-enaktingpsi took 2.9427103996276855s
Availability | SPARQL endpoint availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0484156608581543s
Availability | VoID file availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.00022459030151367188s
Completeness | Calculation of interlinking completeness for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.2550206184387207s
Reputation | Calculation of the PageRank for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.02065896987915039s
Interlinking | Calculation of Degree of Connection for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.00019550323486328125s
Believability | Calculation of trust value for ePrints3 Institutional Archive Collection (RKBExplorer) took 5.0067901611328125e-06s
INFO | --- Analysis for rkb-explorer-eprints took 2.445025682449341s
Availability | SPARQL endpoint availability check for epsrc took 0.038101911544799805s
Availability | VoID file availability check for epsrc took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for epsrc took 0.26123690605163574s
Reputation | Calculation of the PageRank for epsrc took 0.020757198333740234s
Interlinking | Calculation of Degree of Connection for epsrc took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for epsrc took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for epsrc took 5.7697296142578125e-05s
Believability | Calculation of trust value for epsrc took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-epsrc took 2.487518310546875s
Availability | SPARQL endpoint availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.04754900932312012s
Availability | VoID file availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.00044035911560058594s
Completeness | Calculation of interlinking completeness for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.2631521224975586s
Reputation | Calculation of the PageRank for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.02057194709777832s
Interlinking | Calculation of Degree of Connection for ERA - Australian Research Council publication ratings (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for ERA - Australian Research Council publication ratings (RKBExplorer) took 7.939338684082031e-05s
Believability | Calculation of trust value for ERA - Australian Research Council publication ratings (RKBExplorer) took 5.245208740234375e-06s
INFO | --- Analysis for rkb-explorer-era took 2.556034803390503s
Availability | SPARQL endpoint availability check for Institut Eurécom (RKBExplorer) took 0.048272132873535156s
Availability | VoID file availability check for Institut Eurécom (RKBExplorer) took 0.0005447864532470703s
Completeness | Calculation of interlinking completeness for Institut Eurécom (RKBExplorer) took 0.26643896102905273s
Reputation | Calculation of the PageRank for Institut Eurécom (RKBExplorer) took 0.020818471908569336s
Interlinking | Calculation of Degree of Connection for Institut Eurécom (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Institut Eurécom (RKBExplorer) took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Institut Eurécom (RKBExplorer) took 0.00010418891906738281s
Believability | Calculation of trust value for Institut Eurécom (RKBExplorer) took 6.4373016357421875e-06s
INFO | --- Analysis for rkb-explorer-eurecom took 2.578953981399536s
Availability | SPARQL endpoint availability check for rkb-explorer-foreign took 4.00543212890625e-05s
Availability | VoID file availability check for rkb-explorer-foreign took 0.00029540061950683594s
Completeness | Calculation of interlinking completeness for rkb-explorer-foreign took 0.2688560485839844s
Reputation | Calculation of the PageRank for rkb-explorer-foreign took 0.020914077758789062s
Interlinking | Calculation of Degree of Connection for rkb-explorer-foreign took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for rkb-explorer-foreign took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for rkb-explorer-foreign took 3.170967102050781e-05s
Believability | Calculation of trust value for rkb-explorer-foreign took 5.9604644775390625e-06s
INFO | --- Analysis for rkb-explorer-foreign took 2.9950368404388428s
Availability | SPARQL endpoint availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.04821205139160156s
Availability | VoID file availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for France Telecom Recherche et Développement (RKBExplorer) took 0.27089858055114746s
Reputation | Calculation of the PageRank for France Telecom Recherche et Développement (RKBExplorer) took 0.020431995391845703s
Interlinking | Calculation of Degree of Connection for France Telecom Recherche et Développement (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for France Telecom Recherche et Développement (RKBExplorer) took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for France Telecom Recherche et Développement (RKBExplorer) took 9.179115295410156e-05s
Believability | Calculation of trust value for France Telecom Recherche et Développement (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-ft took 2.566215991973877s
Availability | SPARQL endpoint availability check for fun took 0.04872274398803711s
Availability | VoID file availability check for fun took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for fun took 0.3013756275177002s
Reputation | Calculation of the PageRank for fun took 0.021145105361938477s
Interlinking | Calculation of Degree of Connection for fun took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for fun took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for fun took 7.724761962890625e-05s
Believability | Calculation of trust value for fun took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-fun took 2.5514543056488037s
Availability | SPARQL endpoint availability check for gdlc took 0.04722905158996582s
Availability | VoID file availability check for gdlc took 0.0003743171691894531s
Completeness | Calculation of interlinking completeness for gdlc took 0.283311128616333s
Reputation | Calculation of the PageRank for gdlc took 0.020699024200439453s
Interlinking | Calculation of Degree of Connection for gdlc took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for gdlc took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for gdlc took 6.556510925292969e-05s
Believability | Calculation of trust value for gdlc took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-gdlc took 2.455385446548462s
Availability | SPARQL endpoint availability check for IBM Research GmbH (RKBExplorer) took 0.049710750579833984s
Availability | VoID file availability check for IBM Research GmbH (RKBExplorer) took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for IBM Research GmbH (RKBExplorer) took 0.2648303508758545s
Reputation | Calculation of the PageRank for IBM Research GmbH (RKBExplorer) took 0.020525217056274414s
Interlinking | Calculation of Degree of Connection for IBM Research GmbH (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for IBM Research GmbH (RKBExplorer) took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for IBM Research GmbH (RKBExplorer) took 0.00011491775512695312s
Believability | Calculation of trust value for IBM Research GmbH (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-ibm took 2.9067676067352295s
Availability | SPARQL endpoint availability check for IEEE Papers (RKBExplorer) took 0.04450511932373047s
Availability | VoID file availability check for IEEE Papers (RKBExplorer) took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for IEEE Papers (RKBExplorer) took 0.269758939743042s
Reputation | Calculation of the PageRank for IEEE Papers (RKBExplorer) took 0.020407915115356445s
Interlinking | Calculation of Degree of Connection for IEEE Papers (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for IEEE Papers (RKBExplorer) took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for IEEE Papers (RKBExplorer) took 0.0001347064971923828s
Believability | Calculation of trust value for IEEE Papers (RKBExplorer) took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-ieee took 2.484591245651245s
Availability | SPARQL endpoint availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0496065616607666s
Availability | VoID file availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0004134178161621094s
Completeness | Calculation of interlinking completeness for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.2610635757446289s
Reputation | Calculation of the PageRank for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.020587921142578125s
Interlinking | Calculation of Degree of Connection for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.00013899803161621094s
Believability | Calculation of trust value for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-irit took 2.508188009262085s
Availability | SPARQL endpoint availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.050292015075683594s
Availability | VoID file availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0011053085327148438s
Completeness | Calculation of interlinking completeness for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.269256591796875s
Reputation | Calculation of the PageRank for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.020468950271606445s
Interlinking | Calculation of Degree of Connection for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 6.437301635742188e-05s
Believability | Calculation of trust value for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-italy took 2.505605936050415s
Availability | SPARQL endpoint availability check for UK JISC (RKBExplorer) took 0.05215716361999512s
Availability | VoID file availability check for UK JISC (RKBExplorer) took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for UK JISC (RKBExplorer) took 0.27779388427734375s
Reputation | Calculation of the PageRank for UK JISC (RKBExplorer) took 0.02045416831970215s
Interlinking | Calculation of Degree of Connection for UK JISC (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for UK JISC (RKBExplorer) took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for UK JISC (RKBExplorer) took 7.43865966796875e-05s
Believability | Calculation of trust value for UK JISC (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-jisc took 2.981252431869507s
Availability | SPARQL endpoint availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.034963369369506836s
Availability | VoID file availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.25449156761169434s
Reputation | Calculation of the PageRank for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.020264863967895508s
Interlinking | Calculation of Degree of Connection for Vytautas Magnus University, Kaunas (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Vytautas Magnus University, Kaunas (RKBExplorer) took 4.1961669921875e-05s
Believability | Calculation of trust value for Vytautas Magnus University, Kaunas (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-kaunas took 2.474065065383911s
Availability | SPARQL endpoint availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.048632144927978516s
Availability | VoID file availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for Korean Institute of Science Technology and Information (RKBExplorer) took 0.2772984504699707s
Reputation | Calculation of the PageRank for Korean Institute of Science Technology and Information (RKBExplorer) took 0.02045583724975586s
Interlinking | Calculation of Degree of Connection for Korean Institute of Science Technology and Information (RKBExplorer) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0001671314239501953s
Believability | Calculation of trust value for Korean Institute of Science Technology and Information (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-kisti took 2.614628553390503s
Availability | SPARQL endpoint availability check for LAAS-CNRS (RKBExplorer) took 0.046158790588378906s
Availability | VoID file availability check for LAAS-CNRS (RKBExplorer) took 0.0005009174346923828s
Completeness | Calculation of interlinking completeness for LAAS-CNRS (RKBExplorer) took 0.28093504905700684s
Reputation | Calculation of the PageRank for LAAS-CNRS (RKBExplorer) took 0.020364999771118164s
Interlinking | Calculation of Degree of Connection for LAAS-CNRS (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LAAS-CNRS (RKBExplorer) took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for LAAS-CNRS (RKBExplorer) took 0.00014495849609375s
Believability | Calculation of trust value for LAAS-CNRS (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-laas took 2.5001862049102783s
Availability | SPARQL endpoint availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.04689931869506836s
Availability | VoID file availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.26319408416748047s
Reputation | Calculation of the PageRank for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.021319866180419922s
Interlinking | Calculation of Degree of Connection for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 6.723403930664062e-05s
Believability | Calculation of trust value for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-lisbon took 2.444643497467041s
Availability | SPARQL endpoint availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.05321049690246582s
Availability | VoID file availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for University of Newcastle upon Tyne (RKBExplorer) took 0.29741573333740234s
Reputation | Calculation of the PageRank for University of Newcastle upon Tyne (RKBExplorer) took 0.020627260208129883s
Interlinking | Calculation of Degree of Connection for University of Newcastle upon Tyne (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for University of Newcastle upon Tyne (RKBExplorer) took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for University of Newcastle upon Tyne (RKBExplorer) took 0.00015473365783691406s
Believability | Calculation of trust value for University of Newcastle upon Tyne (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-newcastle took 2.5391459465026855s
Availability | SPARQL endpoint availability check for notube took 0.043021440505981445s
Availability | VoID file availability check for notube took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for notube took 0.2599973678588867s
Reputation | Calculation of the PageRank for notube took 0.02067708969116211s
Interlinking | Calculation of Degree of Connection for notube took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for notube took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for notube took 4.315376281738281e-05s
Believability | Calculation of trust value for notube took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-notube took 2.4537272453308105s
Availability | SPARQL endpoint availability check for National Science Foundation (RKBExplorer) took 0.05057883262634277s
Availability | VoID file availability check for National Science Foundation (RKBExplorer) took 0.00045680999755859375s
Completeness | Calculation of interlinking completeness for National Science Foundation (RKBExplorer) took 0.2962355613708496s
Reputation | Calculation of the PageRank for National Science Foundation (RKBExplorer) took 0.0202028751373291s
Interlinking | Calculation of Degree of Connection for National Science Foundation (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for National Science Foundation (RKBExplorer) took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for National Science Foundation (RKBExplorer) took 0.0001323223114013672s
Believability | Calculation of trust value for National Science Foundation (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-nsf took 2.5906083583831787s
Availability | SPARQL endpoint availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.04725527763366699s
Availability | VoID file availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.2910337448120117s
Reputation | Calculation of the PageRank for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.020595788955688477s
Interlinking | Calculation of Degree of Connection for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.00017118453979492188s
Believability | Calculation of trust value for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-oai took 2.5595717430114746s
Availability | SPARQL endpoint availability check for OpenCyc (RKBExplorer) took 4.172325134277344e-05s
Availability | VoID file availability check for OpenCyc (RKBExplorer) took 0.0002789497375488281s
Completeness | Calculation of interlinking completeness for OpenCyc (RKBExplorer) took 0.2468271255493164s
Reputation | Calculation of the PageRank for OpenCyc (RKBExplorer) took 0.020531892776489258s
Interlinking | Calculation of Degree of Connection for OpenCyc (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OpenCyc (RKBExplorer) took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for OpenCyc (RKBExplorer) took 2.9802322387695312e-05s
Believability | Calculation of trust value for OpenCyc (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-opencyc took 2.9096970558166504s
Availability | SPARQL endpoint availability check for Ordnance Survey (RKBExplorer) took 0.04625844955444336s
Availability | VoID file availability check for Ordnance Survey (RKBExplorer) took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for Ordnance Survey (RKBExplorer) took 0.27042102813720703s
Reputation | Calculation of the PageRank for Ordnance Survey (RKBExplorer) took 0.020593881607055664s
Interlinking | Calculation of Degree of Connection for Ordnance Survey (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ordnance Survey (RKBExplorer) took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey (RKBExplorer) took 7.414817810058594e-05s
Believability | Calculation of trust value for Ordnance Survey (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-os took 2.493945360183716s
Availability | SPARQL endpoint availability check for photos took 0.0486757755279541s
Availability | VoID file availability check for photos took 0.0003724098205566406s
Completeness | Calculation of interlinking completeness for photos took 0.25708866119384766s
Reputation | Calculation of the PageRank for photos took 0.0205230712890625s
Interlinking | Calculation of Degree of Connection for photos took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for photos took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for photos took 7.2479248046875e-05s
Believability | Calculation of trust value for photos took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-photos took 2.5154037475585938s
Availability | SPARQL endpoint availability check for Università di Pisa (RKBExplorer) took 0.05222344398498535s
Availability | VoID file availability check for Università di Pisa (RKBExplorer) took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for Università di Pisa (RKBExplorer) took 0.25629115104675293s
Reputation | Calculation of the PageRank for Università di Pisa (RKBExplorer) took 0.02036118507385254s
Interlinking | Calculation of Degree of Connection for Università di Pisa (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Università di Pisa (RKBExplorer) took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Università di Pisa (RKBExplorer) took 0.00011348724365234375s
Believability | Calculation of trust value for Università di Pisa (RKBExplorer) took 5.4836273193359375e-06s
INFO | --- Analysis for rkb-explorer-pisa took 2.6360487937927246s
Availability | SPARQL endpoint availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.04572629928588867s
Availability | VoID file availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for Research Assessment Exercise 2001 (RKBExplorer) took 0.25162529945373535s
Reputation | Calculation of the PageRank for Research Assessment Exercise 2001 (RKBExplorer) took 0.020337343215942383s
Interlinking | Calculation of Degree of Connection for Research Assessment Exercise 2001 (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Research Assessment Exercise 2001 (RKBExplorer) took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Research Assessment Exercise 2001 (RKBExplorer) took 0.0001957416534423828s
Believability | Calculation of trust value for Research Assessment Exercise 2001 (RKBExplorer) took 6.4373016357421875e-06s
INFO | --- Analysis for rkb-explorer-rae2001 took 2.53719425201416s
Availability | SPARQL endpoint availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.04266643524169922s
Availability | VoID file availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.28757667541503906s
Reputation | Calculation of the PageRank for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.020310401916503906s
Interlinking | Calculation of Degree of Connection for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.00013828277587890625s
Believability | Calculation of trust value for ReSIST Resilience Mechanisms (RKBExplorer.com) took 5.4836273193359375e-06s
INFO | --- Analysis for rkb-explorer-resex took 2.431817054748535s
Availability | SPARQL endpoint availability check for RISKS Digest (RKBExplorer) took 0.048909664154052734s
Availability | VoID file availability check for RISKS Digest (RKBExplorer) took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for RISKS Digest (RKBExplorer) took 0.25472521781921387s
Reputation | Calculation of the PageRank for RISKS Digest (RKBExplorer) took 0.0206296443939209s
Interlinking | Calculation of Degree of Connection for RISKS Digest (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for RISKS Digest (RKBExplorer) took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for RISKS Digest (RKBExplorer) took 9.942054748535156e-05s
Believability | Calculation of trust value for RISKS Digest (RKBExplorer) took 6.198883056640625e-06s
INFO | --- Analysis for rkb-explorer-risks took 2.4597318172454834s
Availability | SPARQL endpoint availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.05465888977050781s
Availability | VoID file availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0005195140838623047s
Completeness | Calculation of interlinking completeness for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.27814626693725586s
Reputation | Calculation of the PageRank for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.020415306091308594s
Interlinking | Calculation of Degree of Connection for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.00012183189392089844s
Believability | Calculation of trust value for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 5.9604644775390625e-06s
INFO | --- Analysis for rkb-explorer-roma took 2.526625394821167s
Availability | SPARQL endpoint availability check for roni took 0.05511951446533203s
Availability | VoID file availability check for roni took 0.00037932395935058594s
Completeness | Calculation of interlinking completeness for roni took 0.2756786346435547s
Reputation | Calculation of the PageRank for roni took 0.02046823501586914s
Interlinking | Calculation of Degree of Connection for roni took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for roni took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for roni took 3.0040740966796875e-05s
Believability | Calculation of trust value for roni took 5.7220458984375e-06s
INFO | --- Analysis for rkb-explorer-roni took 2.4745726585388184s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.04271435737609863s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.27596020698547363s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.020667552947998047s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.00022530555725097656s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 5.7220458984375e-06s
INFO | --- Analysis for rkb-explorer-southampton took 2.4756696224212646s
Availability | SPARQL endpoint availability check for Universität Ulm (RKBExplorer) took 0.04408097267150879s
Availability | VoID file availability check for Universität Ulm (RKBExplorer) took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for Universität Ulm (RKBExplorer) took 0.29971885681152344s
Reputation | Calculation of the PageRank for Universität Ulm (RKBExplorer) took 0.0203249454498291s
Interlinking | Calculation of Degree of Connection for Universität Ulm (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universität Ulm (RKBExplorer) took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Universität Ulm (RKBExplorer) took 0.00010538101196289062s
Believability | Calculation of trust value for Universität Ulm (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-ulm took 2.5135347843170166s
Availability | SPARQL endpoint availability check for UN/LOCODE (RKBExplorer) took 0.04295849800109863s
Availability | VoID file availability check for UN/LOCODE (RKBExplorer) took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for UN/LOCODE (RKBExplorer) took 0.2531418800354004s
Reputation | Calculation of the PageRank for UN/LOCODE (RKBExplorer) took 0.02040886878967285s
Interlinking | Calculation of Degree of Connection for UN/LOCODE (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UN/LOCODE (RKBExplorer) took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for UN/LOCODE (RKBExplorer) took 9.965896606445312e-05s
Believability | Calculation of trust value for UN/LOCODE (RKBExplorer) took 5.9604644775390625e-06s
INFO | --- Analysis for rkb-explorer-unlocode took 2.467046022415161s
Availability | SPARQL endpoint availability check for webconf took 0.04294538497924805s
Availability | VoID file availability check for webconf took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for webconf took 0.2692689895629883s
Reputation | Calculation of the PageRank for webconf took 0.020330429077148438s
Interlinking | Calculation of Degree of Connection for webconf took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for webconf took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for webconf took 0.00010132789611816406s
Believability | Calculation of trust value for webconf took 6.4373016357421875e-06s
INFO | --- Analysis for rkb-explorer-webconf took 12.796573162078857s
Availability | SPARQL endpoint availability check for Web Science Conference (RKBExplorer) took 0.05179119110107422s
Availability | VoID file availability check for Web Science Conference (RKBExplorer) took 0.00019931793212890625s
Completeness | Calculation of interlinking completeness for Web Science Conference (RKBExplorer) took 0.2805819511413574s
Reputation | Calculation of the PageRank for Web Science Conference (RKBExplorer) took 0.020653724670410156s
Interlinking | Calculation of Degree of Connection for Web Science Conference (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Web Science Conference (RKBExplorer) took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Web Science Conference (RKBExplorer) took 6.937980651855469e-05s
Believability | Calculation of trust value for Web Science Conference (RKBExplorer) took 5.0067901611328125e-06s
INFO | --- Analysis for rkb-explorer-webscience took 2.4957194328308105s
Availability | SPARQL endpoint availability check for ReSIST Project Wiki (RKBExplorer) took 0.05100607872009277s
Availability | VoID file availability check for ReSIST Project Wiki (RKBExplorer) took 0.00043010711669921875s
Completeness | Calculation of interlinking completeness for ReSIST Project Wiki (RKBExplorer) took 0.2621190547943115s
Reputation | Calculation of the PageRank for ReSIST Project Wiki (RKBExplorer) took 0.020349740982055664s
Interlinking | Calculation of Degree of Connection for ReSIST Project Wiki (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ReSIST Project Wiki (RKBExplorer) took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for ReSIST Project Wiki (RKBExplorer) took 0.00021314620971679688s
Believability | Calculation of trust value for ReSIST Project Wiki (RKBExplorer) took 6.4373016357421875e-06s
INFO | --- Analysis for rkb-explorer-wiki took 2.493360757827759s
Availability | SPARQL endpoint availability check for WordNet (RKBExplorer) took 0.0357365608215332s
Availability | VoID file availability check for WordNet (RKBExplorer) took 0.00042438507080078125s
Completeness | Calculation of interlinking completeness for WordNet (RKBExplorer) took 0.27127575874328613s
Reputation | Calculation of the PageRank for WordNet (RKBExplorer) took 0.020434141159057617s
Interlinking | Calculation of Degree of Connection for WordNet (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for WordNet (RKBExplorer) took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for WordNet (RKBExplorer) took 9.608268737792969e-05s
Believability | Calculation of trust value for WordNet (RKBExplorer) took 5.9604644775390625e-06s
INFO | --- Analysis for rkb-explorer-wordnet took 2.479858160018921s
Availability | SPARQL endpoint availability check for RKB Explorer Data took 4.076957702636719e-05s
Availability | VoID file availability check for RKB Explorer Data took 0.00021910667419433594s
Completeness | Calculation of interlinking completeness for RKB Explorer Data took 0.2884862422943115s
Reputation | Calculation of the PageRank for RKB Explorer Data took 0.020930767059326172s
Interlinking | Calculation of Degree of Connection for RKB Explorer Data took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for RKB Explorer Data took 0.0011115074157714844s
Interlinking | Calculation of Clustering coefficient for RKB Explorer Data took 4.124641418457031e-05s
Believability | Calculation of trust value for RKB Explorer Data took 7.152557373046875e-06s
INFO | --- Analysis for rkb_explorer_data took 2.921403408050537s
Availability | SPARQL endpoint availability check for ROCEEH Out of Africa Database (ROAD) took 0.6401722431182861s
Availability | VoID file availability check for ROCEEH Out of Africa Database (ROAD) took 0.0006451606750488281s
Completeness | Calculation of interlinking completeness for ROCEEH Out of Africa Database (ROAD) took 0.2824218273162842s
Reputation | Calculation of the PageRank for ROCEEH Out of Africa Database (ROAD) took 0.02052927017211914s
Interlinking | Calculation of Degree of Connection for ROCEEH Out of Africa Database (ROAD) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ROCEEH Out of Africa Database (ROAD) took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for ROCEEH Out of Africa Database (ROAD) took 8.130073547363281e-05s
Believability | Calculation of trust value for ROCEEH Out of Africa Database (ROAD) took 5.245208740234375e-06s
INFO | --- Analysis for roceeh-road took 3.7605788707733154s
Availability | SPARQL endpoint availability check for The Rosetta Project took 4.172325134277344e-05s
Availability | VoID file availability check for The Rosetta Project took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for The Rosetta Project took 0.25122547149658203s
Reputation | Calculation of the PageRank for The Rosetta Project took 0.02034592628479004s
Interlinking | Calculation of Degree of Connection for The Rosetta Project took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for The Rosetta Project took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for The Rosetta Project took 2.956390380859375e-05s
Believability | Calculation of trust value for The Rosetta Project took 7.3909759521484375e-06s
INFO | --- Analysis for rosetta-project took 2.9679243564605713s
Availability | SPARQL endpoint availability check for ontology terrorist attack took 4.2438507080078125e-05s
Availability | VoID file availability check for ontology terrorist attack took 0.0006542205810546875s
Completeness | Calculation of interlinking completeness for ontology terrorist attack took 0.2825946807861328s
Reputation | Calculation of the PageRank for ontology terrorist attack took 0.020305156707763672s
Interlinking | Calculation of Degree of Connection for ontology terrorist attack took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ontology terrorist attack took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for ontology terrorist attack took 2.8133392333984375e-05s
Believability | Calculation of trust value for ontology terrorist attack took 5.0067901611328125e-06s
INFO | --- Analysis for ROSHANI took 3.636300802230835s
Availability | SPARQL endpoint availability check for TERRORIST ATTACK ONTOLOGY took 4.1484832763671875e-05s
Availability | VoID file availability check for TERRORIST ATTACK ONTOLOGY took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for TERRORIST ATTACK ONTOLOGY took 0.2519392967224121s
Reputation | Calculation of the PageRank for TERRORIST ATTACK ONTOLOGY took 0.020305156707763672s
Interlinking | Calculation of Degree of Connection for TERRORIST ATTACK ONTOLOGY took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for TERRORIST ATTACK ONTOLOGY took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for TERRORIST ATTACK ONTOLOGY took 3.147125244140625e-05s
Believability | Calculation of trust value for TERRORIST ATTACK ONTOLOGY took 7.152557373046875e-06s
INFO | --- Analysis for ROSHANI_SAHU took 2.3635518550872803s
Availability | SPARQL endpoint availability check for x took 4.1484832763671875e-05s
Availability | VoID file availability check for x took 0.00023937225341796875s
Completeness | Calculation of interlinking completeness for x took 0.25061845779418945s
Reputation | Calculation of the PageRank for x took 0.02049565315246582s
Interlinking | Calculation of Degree of Connection for x took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for x took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for x took 2.7894973754882812e-05s
Believability | Calculation of trust value for x took 7.62939453125e-06s
INFO | --- Analysis for Rozprawa,_artykuł took 2.4191501140594482s
Availability | SPARQL endpoint availability check for Rpm Find took 3.886222839355469e-05s
Availability | VoID file availability check for Rpm Find took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for Rpm Find took 0.26728391647338867s
Reputation | Calculation of the PageRank for Rpm Find took 0.020053625106811523s
Interlinking | Calculation of Degree of Connection for Rpm Find took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Rpm Find took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Rpm Find took 2.8371810913085938e-05s
Believability | Calculation of trust value for Rpm Find took 6.4373016357421875e-06s
INFO | --- Analysis for rpm_find took 2.999220848083496s
Availability | SPARQL endpoint availability check for RSS-500 NIF NER CORPUS took 4.2438507080078125e-05s
Availability | VoID file availability check for RSS-500 NIF NER CORPUS took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for RSS-500 NIF NER CORPUS took 0.27649831771850586s
Reputation | Calculation of the PageRank for RSS-500 NIF NER CORPUS took 0.020348072052001953s
Interlinking | Calculation of Degree of Connection for RSS-500 NIF NER CORPUS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RSS-500 NIF NER CORPUS took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for RSS-500 NIF NER CORPUS took 7.128715515136719e-05s
Believability | Calculation of trust value for RSS-500 NIF NER CORPUS took 7.3909759521484375e-06s
INFO | --- Analysis for rss-500-nif-ner-corpus took 3.6901519298553467s
Availability | SPARQL endpoint availability check for Ruben Taelman's Data took 4.0531158447265625e-05s
Availability | VoID file availability check for Ruben Taelman's Data took 0.0006563663482666016s
Completeness | Calculation of interlinking completeness for Ruben Taelman's Data took 0.26651787757873535s
Reputation | Calculation of the PageRank for Ruben Taelman's Data took 0.020438194274902344s
Interlinking | Calculation of Degree of Connection for Ruben Taelman's Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ruben Taelman's Data took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Ruben Taelman's Data took 7.295608520507812e-05s
Believability | Calculation of trust value for Ruben Taelman's Data took 6.198883056640625e-06s
INFO | --- Analysis for rubentaelman took 2.9031882286071777s
Availability | SPARQL endpoint availability check for Ruben Verborgh's data took 4.1484832763671875e-05s
Availability | VoID file availability check for Ruben Verborgh's data took 0.0006392002105712891s
Completeness | Calculation of interlinking completeness for Ruben Verborgh's data took 0.27295494079589844s
Reputation | Calculation of the PageRank for Ruben Verborgh's data took 0.02046680450439453s
Interlinking | Calculation of Degree of Connection for Ruben Verborgh's data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ruben Verborgh's data took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Ruben Verborgh's data took 8.344650268554688e-05s
Believability | Calculation of trust value for Ruben Verborgh's data took 7.62939453125e-06s
INFO | --- Analysis for rubenverborgh took 3.3861465454101562s
Availability | SPARQL endpoint availability check for Russian Universities Specialities took 393.7582983970642s
Availability | VoID file availability check for Russian Universities Specialities took 0.0007367134094238281s
Completeness | Calculation of interlinking completeness for Russian Universities Specialities took 0.7725095748901367s
Reputation | Calculation of the PageRank for Russian Universities Specialities took 0.020874977111816406s
Interlinking | Calculation of Degree of Connection for Russian Universities Specialities took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Russian Universities Specialities took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Russian Universities Specialities took 4.1961669921875e-05s
Believability | Calculation of trust value for Russian Universities Specialities took 5.9604644775390625e-06s
INFO | --- Analysis for russian-universities-specialities took 678.9532055854797s
Availability | SPARQL endpoint availability check for RuThes Cloud took 4.00543212890625e-05s
Availability | VoID file availability check for RuThes Cloud took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for RuThes Cloud took 0.7018935680389404s
Reputation | Calculation of the PageRank for RuThes Cloud took 0.0259091854095459s
Interlinking | Calculation of Degree of Connection for RuThes Cloud took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for RuThes Cloud took 0.0007946491241455078s
Interlinking | Calculation of Clustering coefficient for RuThes Cloud took 3.0279159545898438e-05s
Believability | Calculation of trust value for RuThes Cloud took 7.867813110351562e-06s
INFO | --- Analysis for ruthes took 5.175460577011108s
Availability | SPARQL endpoint availability check for RxNorm took 4.076957702636719e-05s
Availability | VoID file availability check for RxNorm took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for RxNorm took 0.2477273941040039s
Reputation | Calculation of the PageRank for RxNorm took 0.0205385684967041s
Interlinking | Calculation of Degree of Connection for RxNorm took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for RxNorm took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for RxNorm took 3.695487976074219e-05s
Believability | Calculation of trust value for RxNorm took 9.059906005859375e-06s
INFO | --- Analysis for rxnorm took 5.509130477905273s
Availability | SPARQL endpoint availability check for SADI Semantic Web Services framework registry took 3.0716512203216553s
Availability | VoID file availability check for SADI Semantic Web Services framework registry took 0.0002796649932861328s
Completeness | Calculation of interlinking completeness for SADI Semantic Web Services framework registry took 0.6880471706390381s
Reputation | Calculation of the PageRank for SADI Semantic Web Services framework registry took 0.025803804397583008s
Interlinking | Calculation of Degree of Connection for SADI Semantic Web Services framework registry took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for SADI Semantic Web Services framework registry took 0.0015268325805664062s
Interlinking | Calculation of Clustering coefficient for SADI Semantic Web Services framework registry took 4.649162292480469e-05s
Believability | Calculation of trust value for SADI Semantic Web Services framework registry took 7.3909759521484375e-06s
INFO | --- Analysis for sadi-semantic-web-services-framework-registry took 10.251738786697388s
Availability | SPARQL endpoint availability check for SALDO took 4.649162292480469e-05s
Availability | VoID file availability check for SALDO took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for SALDO took 0.28062963485717773s
Reputation | Calculation of the PageRank for SALDO took 0.020297527313232422s
Interlinking | Calculation of Degree of Connection for SALDO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SALDO took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for SALDO took 2.86102294921875e-05s
Believability | Calculation of trust value for SALDO took 7.3909759521484375e-06s
INFO | --- Analysis for saldo took 4.296984434127808s
Availability | SPARQL endpoint availability check for SALDO-RDF took 1.1199216842651367s
Availability | VoID file availability check for SALDO-RDF took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for SALDO-RDF took 0.2794764041900635s
Reputation | Calculation of the PageRank for SALDO-RDF took 0.020216703414916992s
Interlinking | Calculation of Degree of Connection for SALDO-RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SALDO-RDF took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for SALDO-RDF took 3.3855438232421875e-05s
Believability | Calculation of trust value for SALDO-RDF took 5.9604644775390625e-06s
INFO | --- Analysis for saldo-rdf took 6.5508949756622314s
Availability | SPARQL endpoint availability check for SALDOM-RDF took 0.5909988880157471s
Availability | VoID file availability check for SALDOM-RDF took 0.0005435943603515625s
Completeness | Calculation of interlinking completeness for SALDOM-RDF took 0.6837594509124756s
Reputation | Calculation of the PageRank for SALDOM-RDF took 0.020420074462890625s
Interlinking | Calculation of Degree of Connection for SALDOM-RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for SALDOM-RDF took 0.0007951259613037109s
Interlinking | Calculation of Clustering coefficient for SALDOM-RDF took 3.4809112548828125e-05s
Believability | Calculation of trust value for SALDOM-RDF took 5.4836273193359375e-06s
INFO | --- Analysis for saldom-rdf took 6.096965074539185s
Availability | SPARQL endpoint availability check for Salzburgerland DE took 4.1961669921875e-05s
Availability | VoID file availability check for Salzburgerland DE took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for Salzburgerland DE took 0.27837252616882324s
Reputation | Calculation of the PageRank for Salzburgerland DE took 0.020383119583129883s
Interlinking | Calculation of Degree of Connection for Salzburgerland DE took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Salzburgerland DE took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Salzburgerland DE took 0.00010228157043457031s
Believability | Calculation of trust value for Salzburgerland DE took 7.3909759521484375e-06s
INFO | --- Analysis for salzburgerland-com-de took 3.889094829559326s
Availability | SPARQL endpoint availability check for Salzburgerland EN took 4.1484832763671875e-05s
Availability | VoID file availability check for Salzburgerland EN took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for Salzburgerland EN took 0.24276065826416016s
Reputation | Calculation of the PageRank for Salzburgerland EN took 0.020533323287963867s
Interlinking | Calculation of Degree of Connection for Salzburgerland EN took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Salzburgerland EN took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Salzburgerland EN took 0.00010418891906738281s
Believability | Calculation of trust value for Salzburgerland EN took 7.3909759521484375e-06s
INFO | --- Analysis for salzburgerland-com-en took 3.7688205242156982s
Availability | SPARQL endpoint availability check for Salzburgerland IT took 4.4345855712890625e-05s
Availability | VoID file availability check for Salzburgerland IT took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for Salzburgerland IT took 0.27439403533935547s
Reputation | Calculation of the PageRank for Salzburgerland IT took 0.02026224136352539s
Interlinking | Calculation of Degree of Connection for Salzburgerland IT took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Salzburgerland IT took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Salzburgerland IT took 9.870529174804688e-05s
Believability | Calculation of trust value for Salzburgerland IT took 3.361701965332031e-05s
INFO | --- Analysis for salzburgerland-com-it took 3.2654380798339844s
Availability | SPARQL endpoint availability check for sameAs.org took 6.866455078125e-05s
Availability | VoID file availability check for sameAs.org took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for sameAs.org took 0.2783331871032715s
Reputation | Calculation of the PageRank for sameAs.org took 0.020444869995117188s
Interlinking | Calculation of Degree of Connection for sameAs.org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for sameAs.org took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for sameAs.org took 3.1948089599609375e-05s
Believability | Calculation of trust value for sameAs.org took 6.9141387939453125e-06s
INFO | --- Analysis for sameas-org took 3.289091110229492s
Availability | SPARQL endpoint availability check for sandrart.net took 4.1484832763671875e-05s
Availability | VoID file availability check for sandrart.net took 0.0006527900695800781s
Completeness | Calculation of interlinking completeness for sandrart.net took 0.26736903190612793s
Reputation | Calculation of the PageRank for sandrart.net took 0.02019214630126953s
Interlinking | Calculation of Degree of Connection for sandrart.net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for sandrart.net took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for sandrart.net took 6.413459777832031e-05s
Believability | Calculation of trust value for sandrart.net took 1.5735626220703125e-05s
INFO | --- Analysis for sandrart-net took 3.5049893856048584s
Availability | SPARQL endpoint availability check for Taxons  took 0.19862914085388184s
Availability | VoID file availability check for Taxons  took 0.0004444122314453125s
Extra | Recovery of all triples for Taxons  took 25.081315517425537s
Performance | Total latancy measurement for Taxons  took 0.4097304344177246s
Amount of data | Number of triples check for Taxons  took 2.2895383834838867s
Interoperability | New terms check for Taxons  took 1.7507860660552979s
Versatility | Languages check for Taxons  took 47.49176812171936s
Interpretability | Number of blank nodes check for Taxons  took 1.035667896270752s
Security | Check HTTPS for Taxons  took 0.22613143920898438s
Interpretability | RDF structures check for Taxons  took 1.3157289028167725s
Versatility | Serialization formats check for Taxons  took 0.6832833290100098s
Availability | RDF dump link check for Taxons  took 0.36763644218444824s
License | MR license check for Taxons  took 2.6784005165100098s
License | HR license check for Taxons  took 2.4344751834869385s
Amount of data | Number of property check for Taxons  took 0.11867785453796387s
Understandability | Number of label check for Taxons  took 3.6205191612243652s
Understandability | URI regex check for Taxons  took 0.9363448619842529s
Understandability | Vocabs check for Taxons  took 0.3049137592315674s
Verifiability | Authors check for Taxons  took 0.0892794132232666s
Verifiability | Publishers check for Taxons  took 0.08208584785461426s
Performance | Throughput check for Taxons  took 10.431979894638062s
Amount of data | Check the number of entities for Taxons  took 0.00018072128295898438s
Verifiability | Contribs. check for Taxons  took 0.07837629318237305s
Interlinking | sameAs chians check for Taxons  took 0.15210604667663574s
Interlinking | skos check for Taxons  took 0.15248703956604004s
Interlinking | skos check for Taxons  took 0.08856534957885742s
Timeliness | dataset update frequency check for Taxons  took 0.6059346199035645s
Currency | Creation date check for Taxons  took 0.19884133338928223s
Currency | Modification date check for Taxons  took 0.20916485786437988s
Rep.Conc. | URIs length for Taxons  took 10.104233503341675s
Interoperability | New vocabularies check for Taxons  took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for Taxons  took 0.11548304557800293s
Accuracy | Check Functional Property for Taxons  took 0.717918872833252s
Accuracy | Check Inverse Functional Property for Taxons  took 0.3010556697845459s
Accuracy | Check Empty annotation labels for Taxons  took 4.624869108200073s
Accuracy | Check White space in annotation for Taxons  took 0.31790637969970703s
Accuracy | Check Datatype consistency for Taxons  took 0.2633674144744873s
Consistency | Disjoint class check for Taxons  took 0.13947415351867676s
Consistency | Check Misplaced properties for Taxons  took 4.562768459320068s
Consistency | Misplaced classes for Taxons  took 0.9783098697662354s
Consistency | Check Ontology hijacking for Taxons  took 3.9845900535583496s
Consistency | Check Invalid usage of undefined classes for Taxons  took 1.1781647205352783s
Consistency | Check Invalid usage of undefined properties for Taxons  took 5.864660263061523s
Conciseness | Check Extensional conciseness for Taxons  took 0.2882547378540039s
Conciseness | Check Intensional conciseness for Taxons  took 0.21997356414794922s
Security | Sign check for Taxons  took 1.1351220607757568s
Availability | Check URIs Dereferenciability for Taxons  took 1665.1754236221313s
Completeness | Calculation of interlinking completeness for Taxons  took 1.381941795349121s
Reputation | Calculation of the PageRank for Taxons  took 0.02277684211730957s
Interlinking | Calculation of Degree of Connection for Taxons  took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Taxons  took 0.0008847713470458984s
Interlinking | Calculation of Clustering coefficient for Taxons  took 9.083747863769531e-05s
Interoperability | Check the re-using of existing vocabs for Taxons  took 2.384185791015625e-06s
Believability | Calculation of trust value for Taxons  took 8.344650268554688e-06s
INFO | --- Analysis for sandre took 1853.4477410316467s
Availability | SPARQL endpoint availability check for Sanskrit English Lexicon took 2.0661628246307373s
Availability | VoID file availability check for Sanskrit English Lexicon took 0.0006208419799804688s
Completeness | Calculation of interlinking completeness for Sanskrit English Lexicon took 0.2699863910675049s
Reputation | Calculation of the PageRank for Sanskrit English Lexicon took 0.02047443389892578s
Interlinking | Calculation of Degree of Connection for Sanskrit English Lexicon took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Sanskrit English Lexicon took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Sanskrit English Lexicon took 3.0517578125e-05s
Believability | Calculation of trust value for Sanskrit English Lexicon took 6.67572021484375e-06s
INFO | --- Analysis for sanskrit-english-lexicon took 9.664357662200928s
Availability | SPARQL endpoint availability check for Santillana Guide Dataset took 272.17022609710693s
Availability | VoID file availability check for Santillana Guide Dataset took 0.0007076263427734375s
Completeness | Calculation of interlinking completeness for Santillana Guide Dataset took 1.2276065349578857s
Reputation | Calculation of the PageRank for Santillana Guide Dataset took 0.02102947235107422s
Interlinking | Calculation of Degree of Connection for Santillana Guide Dataset took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Santillana Guide Dataset took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Santillana Guide Dataset took 4.029273986816406e-05s
Believability | Calculation of trust value for Santillana Guide Dataset took 6.9141387939453125e-06s
INFO | --- Analysis for santillana_guide_dataset took 719.1430954933167s
Availability | SPARQL endpoint availability check for SATAR test  took 4.2438507080078125e-05s
Availability | VoID file availability check for SATAR test  took 0.0006024837493896484s
Completeness | Calculation of interlinking completeness for SATAR test  took 0.7076175212860107s
Reputation | Calculation of the PageRank for SATAR test  took 0.0206601619720459s
Interlinking | Calculation of Degree of Connection for SATAR test  took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for SATAR test  took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for SATAR test  took 2.956390380859375e-05s
Believability | Calculation of trust value for SATAR test  took 6.4373016357421875e-06s
INFO | --- Analysis for SATAR_test took 7.920686721801758s
Availability | SPARQL endpoint availability check for SCBG Data took 24.549145221710205s
Availability | VoID file availability check for SCBG Data took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for SCBG Data took 0.2533907890319824s
Reputation | Calculation of the PageRank for SCBG Data took 0.020610332489013672s
Interlinking | Calculation of Degree of Connection for SCBG Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SCBG Data took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for SCBG Data took 7.987022399902344e-05s
Believability | Calculation of trust value for SCBG Data took 7.3909759521484375e-06s
INFO | --- Analysis for SCBG-Data took 59.12901449203491s
Availability | SPARQL endpoint availability check for schema.org took 3.981590270996094e-05s
Availability | VoID file availability check for schema.org took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for schema.org took 0.28917598724365234s
Reputation | Calculation of the PageRank for schema.org took 0.020638227462768555s
Interlinking | Calculation of Degree of Connection for schema.org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for schema.org took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for schema.org took 3.504753112792969e-05s
Believability | Calculation of trust value for schema.org took 8.344650268554688e-06s
INFO | --- Analysis for schema-org took 4.351135492324829s
Availability | SPARQL endpoint availability check for Schemantra took 4.2438507080078125e-05s
Availability | VoID file availability check for Schemantra took 0.00023317337036132812s
Completeness | Calculation of interlinking completeness for Schemantra took 0.7095413208007812s
Reputation | Calculation of the PageRank for Schemantra took 0.020658254623413086s
Interlinking | Calculation of Degree of Connection for Schemantra took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Schemantra took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Schemantra took 3.0994415283203125e-05s
Believability | Calculation of trust value for Schemantra took 6.67572021484375e-06s
INFO | --- Analysis for Schemantra took 3.7202086448669434s
Availability | SPARQL endpoint availability check for Schemapedia: RDF schema compendium took 1.4861376285552979s
Availability | VoID file availability check for Schemapedia: RDF schema compendium took 0.0005650520324707031s
Completeness | Calculation of interlinking completeness for Schemapedia: RDF schema compendium took 0.7026855945587158s
Reputation | Calculation of the PageRank for Schemapedia: RDF schema compendium took 0.02078557014465332s
Interlinking | Calculation of Degree of Connection for Schemapedia: RDF schema compendium took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Schemapedia: RDF schema compendium took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Schemapedia: RDF schema compendium took 3.528594970703125e-05s
Believability | Calculation of trust value for Schemapedia: RDF schema compendium took 6.198883056640625e-06s
INFO | --- Analysis for schemapedia took 5.871371507644653s
Availability | SPARQL endpoint availability check for scholarlydata took 3.9577484130859375e-05s
Availability | VoID file availability check for scholarlydata took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for scholarlydata took 0.2729525566101074s
Reputation | Calculation of the PageRank for scholarlydata took 0.020608901977539062s
Interlinking | Calculation of Degree of Connection for scholarlydata took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for scholarlydata took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for scholarlydata took 2.9325485229492188e-05s
Believability | Calculation of trust value for scholarlydata took 6.198883056640625e-06s
INFO | --- Analysis for scholarlydata took 3.408454656600952s
Availability | SPARQL endpoint availability check for Scholarometer took 4.267692565917969e-05s
Availability | VoID file availability check for Scholarometer took 0.0005867481231689453s
Completeness | Calculation of interlinking completeness for Scholarometer took 0.277620792388916s
Reputation | Calculation of the PageRank for Scholarometer took 0.021422386169433594s
Interlinking | Calculation of Degree of Connection for Scholarometer took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Scholarometer took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Scholarometer took 9.322166442871094e-05s
Believability | Calculation of trust value for Scholarometer took 5.4836273193359375e-06s
INFO | --- Analysis for scholarometer took 8.290924310684204s
Availability | SPARQL endpoint availability check for Science Commons took 4.0531158447265625e-05s
Availability | VoID file availability check for Science Commons took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for Science Commons took 0.2658803462982178s
Reputation | Calculation of the PageRank for Science Commons took 0.02073502540588379s
Interlinking | Calculation of Degree of Connection for Science Commons took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Science Commons took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Science Commons took 2.9087066650390625e-05s
Believability | Calculation of trust value for Science Commons took 6.67572021484375e-06s
INFO | --- Analysis for science_commons took 3.3495562076568604s
Availability | SPARQL endpoint availability check for ScienceWise took 4.00543212890625e-05s
Availability | VoID file availability check for ScienceWise took 0.0003600120544433594s
Completeness | Calculation of interlinking completeness for ScienceWise took 0.2588014602661133s
Reputation | Calculation of the PageRank for ScienceWise took 0.02088189125061035s
Interlinking | Calculation of Degree of Connection for ScienceWise took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ScienceWise took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for ScienceWise took 3.0279159545898438e-05s
Believability | Calculation of trust value for ScienceWise took 7.3909759521484375e-06s
INFO | --- Analysis for sciencewise took 3.259058713912964s
Availability | SPARQL endpoint availability check for The Digital Agenda Scoreboard of the European Commission took 4.887580871582031e-05s
Availability | VoID file availability check for The Digital Agenda Scoreboard of the European Commission took 0.0006279945373535156s
Completeness | Calculation of interlinking completeness for The Digital Agenda Scoreboard of the European Commission took 0.25603580474853516s
Reputation | Calculation of the PageRank for The Digital Agenda Scoreboard of the European Commission took 0.020467042922973633s
Interlinking | Calculation of Degree of Connection for The Digital Agenda Scoreboard of the European Commission took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for The Digital Agenda Scoreboard of the European Commission took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for The Digital Agenda Scoreboard of the European Commission took 3.0040740966796875e-05s
Believability | Calculation of trust value for The Digital Agenda Scoreboard of the European Commission took 4.76837158203125e-06s
INFO | --- Analysis for scoreboard took 4.738789081573486s
Availability | SPARQL endpoint availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 4.100799560546875e-05s
Availability | VoID file availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0008041858673095703s
Completeness | Calculation of interlinking completeness for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.35495424270629883s
Reputation | Calculation of the PageRank for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.020321130752563477s
Interlinking | Calculation of Degree of Connection for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 2.8371810913085938e-05s
Believability | Calculation of trust value for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 7.3909759521484375e-06s
INFO | --- Analysis for SDDEC took 30.404783248901367s
Availability | SPARQL endpoint availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 4.172325134277344e-05s
Availability | VoID file availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0003428459167480469s
Completeness | Calculation of interlinking completeness for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.2852330207824707s
Reputation | Calculation of the PageRank for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.020541667938232422s
Interlinking | Calculation of Degree of Connection for A Knowledge Organization System for the United Nations Sustainable Development Goals took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for A Knowledge Organization System for the United Nations Sustainable Development Goals took 2.8848648071289062e-05s
Believability | Calculation of trust value for A Knowledge Organization System for the United Nations Sustainable Development Goals took 7.152557373046875e-06s
INFO | --- Analysis for SDG took 3.6162989139556885s
Availability | SPARQL endpoint availability check for sears.com took 4.172325134277344e-05s
Availability | VoID file availability check for sears.com took 0.00058746337890625s
Completeness | Calculation of interlinking completeness for sears.com took 0.27121686935424805s
Reputation | Calculation of the PageRank for sears.com took 0.020641088485717773s
Interlinking | Calculation of Degree of Connection for sears.com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for sears.com took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for sears.com took 7.176399230957031e-05s
Believability | Calculation of trust value for sears.com took 6.9141387939453125e-06s
INFO | --- Analysis for sears took 3.925865411758423s
Availability | SPARQL endpoint availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 5.407378911972046s
Availability | VoID file availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0011663436889648438s
Completeness | Calculation of interlinking completeness for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.26232409477233887s
Reputation | Calculation of the PageRank for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.02036142349243164s
Interlinking | Calculation of Degree of Connection for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 8.392333984375e-05s
Believability | Calculation of trust value for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 4.0531158447265625e-06s
INFO | --- Analysis for sec-rdfabout took 15.548160791397095s
Availability | SPARQL endpoint availability check for Source Code Ecosystem Linked Data took 31.41306495666504s
Availability | VoID file availability check for Source Code Ecosystem Linked Data took 0.0007455348968505859s
Completeness | Calculation of interlinking completeness for Source Code Ecosystem Linked Data took 0.26734113693237305s
Reputation | Calculation of the PageRank for Source Code Ecosystem Linked Data took 0.02083110809326172s
Interlinking | Calculation of Degree of Connection for Source Code Ecosystem Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Source Code Ecosystem Linked Data took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Source Code Ecosystem Linked Data took 8.893013000488281e-05s
Believability | Calculation of trust value for Source Code Ecosystem Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for secold took 168.24656772613525s
Availability | SPARQL endpoint availability check for SEEK-AT-WD ICT tools for education - Web-Share took 4.267692565917969e-05s
Availability | VoID file availability check for SEEK-AT-WD ICT tools for education - Web-Share took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for SEEK-AT-WD ICT tools for education - Web-Share took 0.2696268558502197s
Reputation | Calculation of the PageRank for SEEK-AT-WD ICT tools for education - Web-Share took 0.020337343215942383s
Interlinking | Calculation of Degree of Connection for SEEK-AT-WD ICT tools for education - Web-Share took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for SEEK-AT-WD ICT tools for education - Web-Share took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for SEEK-AT-WD ICT tools for education - Web-Share took 2.6226043701171875e-05s
Believability | Calculation of trust value for SEEK-AT-WD ICT tools for education - Web-Share took 6.67572021484375e-06s
INFO | --- Analysis for seek-at-wd-ict-tools-for-education-web-share took 4.65599250793457s
Availability | SPARQL endpoint availability check for semanlink took 4.1484832763671875e-05s
Availability | VoID file availability check for semanlink took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for semanlink took 0.26421523094177246s
Reputation | Calculation of the PageRank for semanlink took 0.020401716232299805s
Interlinking | Calculation of Degree of Connection for semanlink took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for semanlink took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for semanlink took 0.00014448165893554688s
Believability | Calculation of trust value for semanlink took 5.9604644775390625e-06s
INFO | --- Analysis for semanlink took 2.360639810562134s
Availability | SPARQL endpoint availability check for Semantic Library took 3.9577484130859375e-05s
Availability | VoID file availability check for Semantic Library took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for Semantic Library took 0.269878625869751s
Reputation | Calculation of the PageRank for Semantic Library took 0.02039957046508789s
Interlinking | Calculation of Degree of Connection for Semantic Library took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Semantic Library took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Semantic Library took 2.765655517578125e-05s
Believability | Calculation of trust value for Semantic Library took 5.7220458984375e-06s
INFO | --- Analysis for semantic-library took 2.8867669105529785s
Availability | SPARQL endpoint availability check for Semantic Profiling Network took 4.267692565917969e-05s
Availability | VoID file availability check for Semantic Profiling Network took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for Semantic Profiling Network took 0.2584362030029297s
Reputation | Calculation of the PageRank for Semantic Profiling Network took 0.020493507385253906s
Interlinking | Calculation of Degree of Connection for Semantic Profiling Network took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Semantic Profiling Network took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Semantic Profiling Network took 3.0040740966796875e-05s
Believability | Calculation of trust value for Semantic Profiling Network took 7.152557373046875e-06s
INFO | --- Analysis for semantic-profiling-network took 2.8790977001190186s
Availability | SPARQL endpoint availability check for Semantic Universe Data took 0.03393721580505371s
Availability | VoID file availability check for Semantic Universe Data took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for Semantic Universe Data took 0.2801966667175293s
Reputation | Calculation of the PageRank for Semantic Universe Data took 0.02034926414489746s
Interlinking | Calculation of Degree of Connection for Semantic Universe Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Semantic Universe Data took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Semantic Universe Data took 2.8848648071289062e-05s
Believability | Calculation of trust value for Semantic Universe Data took 7.3909759521484375e-06s
INFO | --- Analysis for semantic-universe took 2.531022787094116s
Availability | SPARQL endpoint availability check for Semantic Web Dog Food Corpus took 30.2913556098938s
Availability | VoID file availability check for Semantic Web Dog Food Corpus took 0.0006794929504394531s
Completeness | Calculation of interlinking completeness for Semantic Web Dog Food Corpus took 0.26375246047973633s
Reputation | Calculation of the PageRank for Semantic Web Dog Food Corpus took 0.0256803035736084s
Interlinking | Calculation of Degree of Connection for Semantic Web Dog Food Corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Semantic Web Dog Food Corpus took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Semantic Web Dog Food Corpus took 0.00011706352233886719s
Believability | Calculation of trust value for Semantic Web Dog Food Corpus took 7.3909759521484375e-06s
INFO | --- Analysis for semantic-web-dog-food took 83.84473848342896s
Availability | SPARQL endpoint availability check for semantic-web-grundlagen took 4.100799560546875e-05s
Availability | VoID file availability check for semantic-web-grundlagen took 0.0005662441253662109s
Completeness | Calculation of interlinking completeness for semantic-web-grundlagen took 0.6692187786102295s
Reputation | Calculation of the PageRank for semantic-web-grundlagen took 0.020537376403808594s
Interlinking | Calculation of Degree of Connection for semantic-web-grundlagen took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for semantic-web-grundlagen took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for semantic-web-grundlagen took 4.0531158447265625e-05s
Believability | Calculation of trust value for semantic-web-grundlagen took 5.7220458984375e-06s
INFO | --- Analysis for semantic-web-grundlagen took 3.336505174636841s
Availability | SPARQL endpoint availability check for semantic-web-journal took 4.0531158447265625e-05s
Availability | VoID file availability check for semantic-web-journal took 0.0002257823944091797s
Completeness | Calculation of interlinking completeness for semantic-web-journal took 0.2735424041748047s
Reputation | Calculation of the PageRank for semantic-web-journal took 0.020096302032470703s
Interlinking | Calculation of Degree of Connection for semantic-web-journal took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for semantic-web-journal took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for semantic-web-journal took 2.6702880859375e-05s
Believability | Calculation of trust value for semantic-web-journal took 5.7220458984375e-06s
INFO | --- Analysis for semantic-web-journal took 3.4561400413513184s
Availability | SPARQL endpoint availability check for Semantic XBRL Financial Data took 4.124641418457031e-05s
Availability | VoID file availability check for Semantic XBRL Financial Data took 0.0005652904510498047s
Completeness | Calculation of interlinking completeness for Semantic XBRL Financial Data took 0.24706292152404785s
Reputation | Calculation of the PageRank for Semantic XBRL Financial Data took 0.02019214630126953s
Interlinking | Calculation of Degree of Connection for Semantic XBRL Financial Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Semantic XBRL Financial Data took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Semantic XBRL Financial Data took 7.915496826171875e-05s
Believability | Calculation of trust value for Semantic XBRL Financial Data took 4.76837158203125e-06s
INFO | --- Analysis for semantic-xbrl took 3.3466410636901855s
Availability | SPARQL endpoint availability check for Semantic Bible took 3.886222839355469e-05s
Availability | VoID file availability check for Semantic Bible took 0.00023508071899414062s
Completeness | Calculation of interlinking completeness for Semantic Bible took 0.2756028175354004s
Reputation | Calculation of the PageRank for Semantic Bible took 0.020225048065185547s
Interlinking | Calculation of Degree of Connection for Semantic Bible took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Semantic Bible took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Semantic Bible took 2.6226043701171875e-05s
Believability | Calculation of trust value for Semantic Bible took 7.3909759521484375e-06s
INFO | --- Analysis for semantic_bible took 3.095386505126953s
Availability | SPARQL endpoint availability check for SemanticQuran took 22.087246894836426s
Availability | VoID file availability check for SemanticQuran took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for SemanticQuran took 0.27162957191467285s
Reputation | Calculation of the PageRank for SemanticQuran took 0.02037358283996582s
Interlinking | Calculation of Degree of Connection for SemanticQuran took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SemanticQuran took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for SemanticQuran took 6.890296936035156e-05s
Believability | Calculation of trust value for SemanticQuran took 5.4836273193359375e-06s
INFO | --- Analysis for semanticquran took 34.27329397201538s
Availability | SPARQL endpoint availability check for SemanticTweet took 4.1961669921875e-05s
Availability | VoID file availability check for SemanticTweet took 0.0005860328674316406s
Completeness | Calculation of interlinking completeness for SemanticTweet took 0.29334235191345215s
Reputation | Calculation of the PageRank for SemanticTweet took 0.02038121223449707s
Interlinking | Calculation of Degree of Connection for SemanticTweet took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SemanticTweet took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for SemanticTweet took 5.459785461425781e-05s
Believability | Calculation of trust value for SemanticTweet took 7.867813110351562e-06s
INFO | --- Analysis for semantictweet took 4.430215358734131s
Availability | SPARQL endpoint availability check for semanticweb.org took 4.315376281738281e-05s
Availability | VoID file availability check for semanticweb.org took 0.0007107257843017578s
Completeness | Calculation of interlinking completeness for semanticweb.org took 0.27312517166137695s
Reputation | Calculation of the PageRank for semanticweb.org took 0.02029728889465332s
Interlinking | Calculation of Degree of Connection for semanticweb.org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for semanticweb.org took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for semanticweb.org took 7.605552673339844e-05s
Believability | Calculation of trust value for semanticweb.org took 5.9604644775390625e-06s
INFO | --- Analysis for semanticweb-org took 22.591105222702026s
Availability | SPARQL endpoint availability check for Semantic CrunchBase took 0.06926131248474121s
Availability | VoID file availability check for Semantic CrunchBase took 0.00022125244140625s
Completeness | Calculation of interlinking completeness for Semantic CrunchBase took 0.30020833015441895s
Reputation | Calculation of the PageRank for Semantic CrunchBase took 0.020211458206176758s
Interlinking | Calculation of Degree of Connection for Semantic CrunchBase took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Semantic CrunchBase took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Semantic CrunchBase took 6.461143493652344e-05s
Believability | Calculation of trust value for Semantic CrunchBase took 6.9141387939453125e-06s
INFO | --- Analysis for semsol-crunchbase took 2.5020079612731934s
Availability | SPARQL endpoint availability check for Sensores de IntelliDomo took 3.886222839355469e-05s
Availability | VoID file availability check for Sensores de IntelliDomo took 0.00022745132446289062s
Completeness | Calculation of interlinking completeness for Sensores de IntelliDomo took 0.28719305992126465s
Reputation | Calculation of the PageRank for Sensores de IntelliDomo took 0.020224571228027344s
Interlinking | Calculation of Degree of Connection for Sensores de IntelliDomo took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Sensores de IntelliDomo took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Sensores de IntelliDomo took 2.7894973754882812e-05s
Believability | Calculation of trust value for Sensores de IntelliDomo took 5.9604644775390625e-06s
INFO | --- Analysis for sensores-de-intellidomo took 2.898773670196533s
Availability | SPARQL endpoint availability check for SentimentWortschatz took 0.0823361873626709s
Availability | VoID file availability check for SentimentWortschatz took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for SentimentWortschatz took 0.28243327140808105s
Reputation | Calculation of the PageRank for SentimentWortschatz took 0.020591020584106445s
Interlinking | Calculation of Degree of Connection for SentimentWortschatz took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SentimentWortschatz took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for SentimentWortschatz took 4.100799560546875e-05s
Believability | Calculation of trust value for SentimentWortschatz took 6.67572021484375e-06s
INFO | --- Analysis for sentiws took 3.305428981781006s
Availability | SPARQL endpoint availability check for seoul-bike-data took 30.169309377670288s
Availability | VoID file availability check for seoul-bike-data took 0.0006511211395263672s
Completeness | Calculation of interlinking completeness for seoul-bike-data took 0.2422466278076172s
Reputation | Calculation of the PageRank for seoul-bike-data took 0.02036285400390625s
Interlinking | Calculation of Degree of Connection for seoul-bike-data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for seoul-bike-data took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for seoul-bike-data took 3.0040740966796875e-05s
Believability | Calculation of trust value for seoul-bike-data took 7.867813110351562e-06s
INFO | --- Analysis for seoul-bike-data took 72.70047330856323s
Availability | SPARQL endpoint availability check for Serendipity took 8.336510419845581s
Availability | VoID file availability check for Serendipity took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for Serendipity took 0.2695045471191406s
Reputation | Calculation of the PageRank for Serendipity took 0.02024984359741211s
Interlinking | Calculation of Degree of Connection for Serendipity took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Serendipity took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Serendipity took 7.677078247070312e-05s
Believability | Calculation of trust value for Serendipity took 7.3909759521484375e-06s
INFO | --- Analysis for serendipity took 16.5046706199646s
Availability | SPARQL endpoint availability check for Sherry Wine Vocabulary took 4.267692565917969e-05s
Availability | VoID file availability check for Sherry Wine Vocabulary took 0.0006313323974609375s
Completeness | Calculation of interlinking completeness for Sherry Wine Vocabulary took 0.2923600673675537s
Reputation | Calculation of the PageRank for Sherry Wine Vocabulary took 0.02015089988708496s
Interlinking | Calculation of Degree of Connection for Sherry Wine Vocabulary took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Sherry Wine Vocabulary took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Sherry Wine Vocabulary took 2.7418136596679688e-05s
Believability | Calculation of trust value for Sherry Wine Vocabulary took 6.67572021484375e-06s
INFO | --- Analysis for Sherry_Wine took 13.8368980884552s
Availability | SPARQL endpoint availability check for Sherry Wine took 4.172325134277344e-05s
Availability | VoID file availability check for Sherry Wine took 0.00023317337036132812s
Completeness | Calculation of interlinking completeness for Sherry Wine took 0.2676420211791992s
Reputation | Calculation of the PageRank for Sherry Wine took 0.020226716995239258s
Interlinking | Calculation of Degree of Connection for Sherry Wine took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Sherry Wine took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Sherry Wine took 2.7894973754882812e-05s
Believability | Calculation of trust value for Sherry Wine took 5.9604644775390625e-06s
INFO | --- Analysis for Sherry_Wine_ took 2.42142653465271s
Availability | SPARQL endpoint availability check for Shoah victims? names took 0.19122552871704102s
Availability | VoID file availability check for Shoah victims? names took 0.0004949569702148438s
Extra | Recovery of all triples for Shoah victims? names took 1.351135492324829s
Performance | Total latancy measurement for Shoah victims? names took 0.4313514232635498s
Amount of data | Number of triples check for Shoah victims? names took 1.7270548343658447s
Interoperability | New terms check for Shoah victims? names took 1.5784263610839844s
Versatility | Languages check for Shoah victims? names took 29.508633375167847s
Interpretability | Number of blank nodes check for Shoah victims? names took 2.3177971839904785s
Security | Check HTTPS for Shoah victims? names took 0.21462512016296387s
Interpretability | RDF structures check for Shoah victims? names took 0.31887102127075195s
Versatility | Serialization formats check for Shoah victims? names took 0.5457746982574463s
Availability | RDF dump link check for Shoah victims? names took 0.29169559478759766s
License | MR license check for Shoah victims? names took 0.8073320388793945s
License | HR license check for Shoah victims? names took 13.153879404067993s
Amount of data | Number of property check for Shoah victims? names took 0.1449730396270752s
Understandability | Number of label check for Shoah victims? names took 2.4084320068359375s
Understandability | URI regex check for Shoah victims? names took 0.6994359493255615s
Understandability | Vocabs check for Shoah victims? names took 0.17749476432800293s
Verifiability | Authors check for Shoah victims? names took 0.32105302810668945s
Verifiability | Publishers check for Shoah victims? names took 0.3365321159362793s
Performance | Throughput check for Shoah victims? names took 10.48964810371399s
Amount of data | Check the number of entities for Shoah victims? names took 8.702278137207031e-05s
Verifiability | Contribs. check for Shoah victims? names took 0.05353188514709473s
Interlinking | sameAs chians check for Shoah victims? names took 0.20960545539855957s
Interlinking | skos check for Shoah victims? names took 0.4777870178222656s
Interlinking | skos check for Shoah victims? names took 0.07488155364990234s
Timeliness | dataset update frequency check for Shoah victims? names took 0.637340784072876s
Currency | Creation date check for Shoah victims? names took 0.15821170806884766s
Currency | Modification date check for Shoah victims? names took 0.19452905654907227s
Rep.Conc. | URIs length for Shoah victims? names took 3.4502384662628174s
Interoperability | New vocabularies check for Shoah victims? names took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Shoah victims? names took 0.10101318359375s
Accuracy | Check Functional Property for Shoah victims? names took 0.14571094512939453s
Accuracy | Check Inverse Functional Property for Shoah victims? names took 0.0667729377746582s
Accuracy | Check Empty annotation labels for Shoah victims? names took 0.37255215644836426s
Accuracy | Check White space in annotation for Shoah victims? names took 0.029634714126586914s
Accuracy | Check Datatype consistency for Shoah victims? names took 0.027762174606323242s
Consistency | Disjoint class check for Shoah victims? names took 0.32764577865600586s
Consistency | Check Misplaced properties for Shoah victims? names took 3.0349981784820557s
Consistency | Misplaced classes for Shoah victims? names took 0.2038896083831787s
Consistency | Check Ontology hijacking for Shoah victims? names took 1.509596824645996s
Consistency | Check Invalid usage of undefined classes for Shoah victims? names took 1.1178398132324219s
Consistency | Check Invalid usage of undefined properties for Shoah victims? names took 3.77736234664917s
Conciseness | Check Extensional conciseness for Shoah victims? names took 0.02929377555847168s
Conciseness | Check Intensional conciseness for Shoah victims? names took 0.10362958908081055s
Security | Sign check for Shoah victims? names took 1.1260368824005127s
Availability | Check URIs Dereferenciability for Shoah victims? names took 2498.205753803253s
Completeness | Calculation of interlinking completeness for Shoah victims? names took 0.959618330001831s
Reputation | Calculation of the PageRank for Shoah victims? names took 0.02133011817932129s
Interlinking | Calculation of Degree of Connection for Shoah victims? names took 2.4557113647460938e-05s
Interlinking | Calculation of Centrality for Shoah victims? names took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for Shoah victims? names took 4.553794860839844e-05s
Interoperability | Check the re-using of existing vocabs for Shoah victims? names took 1.9073486328125e-06s
Believability | Calculation of trust value for Shoah victims? names took 5.7220458984375e-06s
INFO | --- Analysis for shoah-victims-names took 2654.4480736255646s
Availability | SPARQL endpoint availability check for Person took 4.38690185546875e-05s
Availability | VoID file availability check for Person took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for Person took 0.2694864273071289s
Reputation | Calculation of the PageRank for Person took 0.02096247673034668s
Interlinking | Calculation of Degree of Connection for Person took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Person took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Person took 2.8848648071289062e-05s
Believability | Calculation of trust value for Person took 5.9604644775390625e-06s
INFO | --- Analysis for Shripriya_Dubey took 3.7076196670532227s
Availability | SPARQL endpoint availability check for Jishnu Raghavan (1976-2016) took 4.363059997558594e-05s
Availability | VoID file availability check for Jishnu Raghavan (1976-2016) took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Jishnu Raghavan (1976-2016) took 0.24952244758605957s
Reputation | Calculation of the PageRank for Jishnu Raghavan (1976-2016) took 0.022995710372924805s
Interlinking | Calculation of Degree of Connection for Jishnu Raghavan (1976-2016) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Jishnu Raghavan (1976-2016) took 0.0010390281677246094s
Interlinking | Calculation of Clustering coefficient for Jishnu Raghavan (1976-2016) took 3.743171691894531e-05s
Believability | Calculation of trust value for Jishnu Raghavan (1976-2016) took 6.9141387939453125e-06s
INFO | --- Analysis for Shutterstock took 3.2170426845550537s
Availability | SPARQL endpoint availability check for SIMILE Data Collection took 3.9577484130859375e-05s
Availability | VoID file availability check for SIMILE Data Collection took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for SIMILE Data Collection took 0.6892364025115967s
Reputation | Calculation of the PageRank for SIMILE Data Collection took 0.02104663848876953s
Interlinking | Calculation of Degree of Connection for SIMILE Data Collection took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SIMILE Data Collection took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for SIMILE Data Collection took 3.4809112548828125e-05s
Believability | Calculation of trust value for SIMILE Data Collection took 6.67572021484375e-06s
INFO | --- Analysis for simile_data_collection took 5.5147624015808105s
Availability | SPARQL endpoint availability check for SIMPLE took 4.863739013671875e-05s
Availability | VoID file availability check for SIMPLE took 0.0008838176727294922s
Completeness | Calculation of interlinking completeness for SIMPLE took 1.65171217918396s
Reputation | Calculation of the PageRank for SIMPLE took 0.023016929626464844s
Interlinking | Calculation of Degree of Connection for SIMPLE took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SIMPLE took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for SIMPLE took 4.506111145019531e-05s
Believability | Calculation of trust value for SIMPLE took 7.152557373046875e-06s
INFO | --- Analysis for simple took 1809.1530759334564s
Availability | SPARQL endpoint availability check for 2019-2022 Analysis of the π Index in China's Life Sciences and Basic Medicine took 0.00010395050048828125s
Availability | VoID file availability check for 2019-2022 Analysis of the π Index in China's Life Sciences and Basic Medicine took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for 2019-2022 Analysis of the π Index in China's Life Sciences and Basic Medicine took 0.6949055194854736s
Reputation | Calculation of the PageRank for 2019-2022 Analysis of the π Index in China's Life Sciences and Basic Medicine took 0.020308494567871094s
Interlinking | Calculation of Degree of Connection for 2019-2022 Analysis of the π Index in China's Life Sciences and Basic Medicine took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for 2019-2022 Analysis of the π Index in China's Life Sciences and Basic Medicine took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for 2019-2022 Analysis of the π Index in China's Life Sciences and Basic Medicine took 1.1444091796875e-05s
Believability | Calculation of trust value for 2019-2022 Analysis of the π Index in China's Life Sciences and Basic Medicine took 6.67572021484375e-06s
INFO | --- Analysis for sinh-CLSPIRData took 4.955424785614014s
Availability | SPARQL endpoint availability check for SITC-V4 took 26.50590944290161s
Availability | VoID file availability check for SITC-V4 took 0.0009369850158691406s
Completeness | Calculation of interlinking completeness for SITC-V4 took 0.27181172370910645s
Reputation | Calculation of the PageRank for SITC-V4 took 0.020408153533935547s
Interlinking | Calculation of Degree of Connection for SITC-V4 took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for SITC-V4 took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for SITC-V4 took 4.3392181396484375e-05s
Believability | Calculation of trust value for SITC-V4 took 5.4836273193359375e-06s
INFO | --- Analysis for sitc-v4 took 122.6765615940094s
Availability | SPARQL endpoint availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 4.172325134277344e-05s
Availability | VoID file availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0006206035614013672s
Completeness | Calculation of interlinking completeness for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.2637333869934082s
Reputation | Calculation of the PageRank for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.020218372344970703s
Interlinking | Calculation of Degree of Connection for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 4.00543212890625e-05s
Believability | Calculation of trust value for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 5.9604644775390625e-06s
INFO | --- Analysis for sli_galnet_rdf took 14.2834632396698s
Availability | SPARQL endpoint availability check for Slideshare2RDF Server took 4.1484832763671875e-05s
Availability | VoID file availability check for Slideshare2RDF Server took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for Slideshare2RDF Server took 0.28971290588378906s
Reputation | Calculation of the PageRank for Slideshare2RDF Server took 0.0266568660736084s
Interlinking | Calculation of Degree of Connection for Slideshare2RDF Server took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Slideshare2RDF Server took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Slideshare2RDF Server took 2.8133392333984375e-05s
Believability | Calculation of trust value for Slideshare2RDF Server took 6.198883056640625e-06s
INFO | --- Analysis for slideshare2rdf took 3.372565507888794s
Availability | SPARQL endpoint availability check for Slidewiki (RDF/SPARQL) took 4.2438507080078125e-05s
Availability | VoID file availability check for Slidewiki (RDF/SPARQL) took 0.0002789497375488281s
Completeness | Calculation of interlinking completeness for Slidewiki (RDF/SPARQL) took 0.24825644493103027s
Reputation | Calculation of the PageRank for Slidewiki (RDF/SPARQL) took 0.020351409912109375s
Interlinking | Calculation of Degree of Connection for Slidewiki (RDF/SPARQL) took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Slidewiki (RDF/SPARQL) took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Slidewiki (RDF/SPARQL) took 3.504753112792969e-05s
Believability | Calculation of trust value for Slidewiki (RDF/SPARQL) took 6.4373016357421875e-06s
INFO | --- Analysis for slidewiki-rdf-sparql took 4.782310724258423s
Availability | SPARQL endpoint availability check for Linked Stage Graph took 0.8154947757720947s
Availability | VoID file availability check for Linked Stage Graph took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for Linked Stage Graph took 0.29008936882019043s
Reputation | Calculation of the PageRank for Linked Stage Graph took 0.020095109939575195s
Interlinking | Calculation of Degree of Connection for Linked Stage Graph took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Stage Graph took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Linked Stage Graph took 4.696846008300781e-05s
Believability | Calculation of trust value for Linked Stage Graph took 6.67572021484375e-06s
INFO | --- Analysis for slod took 4.195168733596802s
Availability | SPARQL endpoint availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 4.076957702636719e-05s
Availability | VoID file availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.00023484230041503906s
Completeness | Calculation of interlinking completeness for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.2693910598754883s
Reputation | Calculation of the PageRank for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.020387649536132812s
Interlinking | Calculation of Degree of Connection for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 2.765655517578125e-05s
Believability | Calculation of trust value for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 6.4373016357421875e-06s
INFO | --- Analysis for slovn-k-cpv-2008---common-procurement-vocabulary-2008 took 3.3854289054870605s
Availability | SPARQL endpoint availability check for Smart Points Of Interest @PSNC took 1.071972370147705s
Availability | VoID file availability check for Smart Points Of Interest @PSNC took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for Smart Points Of Interest @PSNC took 0.6781942844390869s
Reputation | Calculation of the PageRank for Smart Points Of Interest @PSNC took 0.020178556442260742s
Interlinking | Calculation of Degree of Connection for Smart Points Of Interest @PSNC took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Smart Points Of Interest @PSNC took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Smart Points Of Interest @PSNC took 9.441375732421875e-05s
Believability | Calculation of trust value for Smart Points Of Interest @PSNC took 5.245208740234375e-06s
INFO | --- Analysis for Smart_POI_dataset took 5.0589354038238525s
Availability | SPARQL endpoint availability check for SmartLink: Linked Services Non-Functional Properties took 23.480955123901367s
Availability | VoID file availability check for SmartLink: Linked Services Non-Functional Properties took 0.0008046627044677734s
Completeness | Calculation of interlinking completeness for SmartLink: Linked Services Non-Functional Properties took 0.70709228515625s
Reputation | Calculation of the PageRank for SmartLink: Linked Services Non-Functional Properties took 0.021056413650512695s
Interlinking | Calculation of Degree of Connection for SmartLink: Linked Services Non-Functional Properties took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for SmartLink: Linked Services Non-Functional Properties took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for SmartLink: Linked Services Non-Functional Properties took 3.62396240234375e-05s
Believability | Calculation of trust value for SmartLink: Linked Services Non-Functional Properties took 5.7220458984375e-06s
INFO | --- Analysis for smartlink took 53.8028302192688s
Availability | SPARQL endpoint availability check for SNIK took 0.4467735290527344s
Availability | VoID file availability check for SNIK took 0.0006456375122070312s
Extra | Recovery of all triples for SNIK took 2.6889069080352783s
Performance | Total latancy measurement for SNIK took 0.9913432598114014s
Amount of data | Number of triples check for SNIK took 0.19855785369873047s
Interoperability | New terms check for SNIK took 1.4174447059631348s
Versatility | Languages check for SNIK took 0.24289417266845703s
Interpretability | Number of blank nodes check for SNIK took 0.20839524269104004s
Interpretability | RDF structures check for SNIK took 0.18438482284545898s
Versatility | Serialization formats check for SNIK took 0.195939302444458s
Availability | RDF dump link check for SNIK took 0.19717073440551758s
License | MR license check for SNIK took 0.1870558261871338s
License | HR license check for SNIK took 0.22238826751708984s
Amount of data | Number of property check for SNIK took 0.1958932876586914s
Understandability | Number of label check for SNIK took 0.20018982887268066s
Understandability | URI regex check for SNIK took 0.40471529960632324s
Understandability | Vocabs check for SNIK took 0.20877480506896973s
Verifiability | Authors check for SNIK took 0.19546103477478027s
Verifiability | Publishers check for SNIK took 0.18619012832641602s
Performance | Throughput check for SNIK took 11.551926136016846s
Amount of data | Check the number of entities for SNIK took 8.177757263183594e-05s
Verifiability | Contribs. check for SNIK took 0.19725990295410156s
Interlinking | sameAs chians check for SNIK took 0.18409395217895508s
Interlinking | skos check for SNIK took 0.18623709678649902s
Interlinking | skos check for SNIK took 0.20656800270080566s
Timeliness | dataset update frequency check for SNIK took 0.1980729103088379s
Currency | Creation date check for SNIK took 0.4040489196777344s
Currency | Modification date check for SNIK took 0.38550686836242676s
Rep.Conc. | URIs length for SNIK took 1.3871326446533203s
Interoperability | New vocabularies check for SNIK took 5.245208740234375e-06s
Consistency | Deprecated classes/propertiers check for SNIK took 0.1826469898223877s
Accuracy | Check Functional Property for SNIK took 0.19694066047668457s
Accuracy | Check Inverse Functional Property for SNIK took 0.18648433685302734s
Accuracy | Check Empty annotation labels for SNIK took 0.6026511192321777s
Accuracy | Check White space in annotation for SNIK took 0.028165578842163086s
Accuracy | Check Datatype consistency for SNIK took 0.21995997428894043s
Consistency | Disjoint class check for SNIK took 0.19535470008850098s
Consistency | Check Misplaced properties for SNIK took 0.6519863605499268s
Consistency | Misplaced classes for SNIK took 0.6983184814453125s
Consistency | Check Ontology hijacking for SNIK took 1.7134253978729248s
Consistency | Check Invalid usage of undefined classes for SNIK took 1.1666622161865234s
Consistency | Check Invalid usage of undefined properties for SNIK took 1.4545729160308838s
Conciseness | Check Extensional conciseness for SNIK took 0.15272927284240723s
Conciseness | Check Intensional conciseness for SNIK took 0.34583306312561035s
Security | Sign check for SNIK took 0.19528746604919434s
Availability | Check URIs Dereferenciability for SNIK took 664.6575081348419s
Completeness | Calculation of interlinking completeness for SNIK took 1.3091716766357422s
Reputation | Calculation of the PageRank for SNIK took 0.031339406967163086s
Interlinking | Calculation of Degree of Connection for SNIK took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for SNIK took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for SNIK took 9.393692016601562e-05s
Interoperability | Check the re-using of existing vocabs for SNIK took 2.6226043701171875e-06s
Believability | Calculation of trust value for SNIK took 7.3909759521484375e-06s
INFO | --- Analysis for snik took 719.9159524440765s
Availability | SPARQL endpoint availability check for Social Networks and Archival Context Fall 2011 took 4.291534423828125e-05s
Availability | VoID file availability check for Social Networks and Archival Context Fall 2011 took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for Social Networks and Archival Context Fall 2011 took 0.7088747024536133s
Reputation | Calculation of the PageRank for Social Networks and Archival Context Fall 2011 took 0.02060246467590332s
Interlinking | Calculation of Degree of Connection for Social Networks and Archival Context Fall 2011 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Social Networks and Archival Context Fall 2011 took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for Social Networks and Archival Context Fall 2011 took 3.1948089599609375e-05s
Believability | Calculation of trust value for Social Networks and Archival Context Fall 2011 took 7.3909759521484375e-06s
INFO | --- Analysis for social-networks-and-archival-context-fall-2011 took 5.192433834075928s
Availability | SPARQL endpoint availability check for SocialLink took 0.08086180686950684s
Availability | VoID file availability check for SocialLink took 0.0006039142608642578s
Completeness | Calculation of interlinking completeness for SocialLink took 0.2648468017578125s
Reputation | Calculation of the PageRank for SocialLink took 0.020511388778686523s
Interlinking | Calculation of Degree of Connection for SocialLink took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for SocialLink took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for SocialLink took 7.867813110351562e-05s
Believability | Calculation of trust value for SocialLink took 1.33514404296875e-05s
INFO | --- Analysis for SocialLink took 4.206247091293335s
Availability | SPARQL endpoint availability check for SocialLink took 3.9577484130859375e-05s
Availability | VoID file availability check for SocialLink took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for SocialLink took 0.2712671756744385s
Reputation | Calculation of the PageRank for SocialLink took 0.02075934410095215s
Interlinking | Calculation of Degree of Connection for SocialLink took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SocialLink took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for SocialLink took 3.24249267578125e-05s
Believability | Calculation of trust value for SocialLink took 8.821487426757812e-06s
INFO | --- Analysis for sociallink took 4.241365194320679s
Availability | SPARQL endpoint availability check for FamilyRelations as SocialRole took 4.291534423828125e-05s
Availability | VoID file availability check for FamilyRelations as SocialRole took 0.0005991458892822266s
Completeness | Calculation of interlinking completeness for FamilyRelations as SocialRole took 0.6948213577270508s
Reputation | Calculation of the PageRank for FamilyRelations as SocialRole took 0.020441293716430664s
Interlinking | Calculation of Degree of Connection for FamilyRelations as SocialRole took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FamilyRelations as SocialRole took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for FamilyRelations as SocialRole took 3.075599670410156e-05s
Believability | Calculation of trust value for FamilyRelations as SocialRole took 6.198883056640625e-06s
INFO | --- Analysis for SocialRoles took 11.969817161560059s
Availability | SPARQL endpoint availability check for Social Semantic Web Thesaurus took 0.2185359001159668s
Availability | VoID file availability check for Social Semantic Web Thesaurus took 0.0007441043853759766s
Extra | Recovery of all triples for Social Semantic Web Thesaurus took 16.778488636016846s
Performance | Total latancy measurement for Social Semantic Web Thesaurus took 0.5245234966278076s
Amount of data | Number of triples check for Social Semantic Web Thesaurus took 0.22012901306152344s
Interoperability | New terms check for Social Semantic Web Thesaurus took 1.3393268585205078s
Versatility | Languages check for Social Semantic Web Thesaurus took 0.36948251724243164s
Interpretability | Number of blank nodes check for Social Semantic Web Thesaurus took 0.18207716941833496s
Security | Check HTTPS for Social Semantic Web Thesaurus took 0.3015885353088379s
Interpretability | RDF structures check for Social Semantic Web Thesaurus took 0.12566351890563965s
Versatility | Serialization formats check for Social Semantic Web Thesaurus took 0.1366286277770996s
Availability | RDF dump link check for Social Semantic Web Thesaurus took 0.8560755252838135s
License | MR license check for Social Semantic Web Thesaurus took 0.10501837730407715s
License | HR license check for Social Semantic Web Thesaurus took 0.11588740348815918s
Amount of data | Number of property check for Social Semantic Web Thesaurus took 0.13121676445007324s
Understandability | Number of label check for Social Semantic Web Thesaurus took 0.13383054733276367s
Understandability | URI regex check for Social Semantic Web Thesaurus took 0.17274713516235352s
Understandability | Vocabs check for Social Semantic Web Thesaurus took 0.10510444641113281s
Verifiability | Authors check for Social Semantic Web Thesaurus took 0.11069178581237793s
Verifiability | Publishers check for Social Semantic Web Thesaurus took 0.11148881912231445s
Performance | Throughput check for Social Semantic Web Thesaurus took 10.640025854110718s
Amount of data | Check the number of entities for Social Semantic Web Thesaurus took 7.152557373046875e-05s
Verifiability | Contribs. check for Social Semantic Web Thesaurus took 0.11285614967346191s
Interlinking | sameAs chians check for Social Semantic Web Thesaurus took 0.1161189079284668s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.11800026893615723s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.09865593910217285s
Timeliness | dataset update frequency check for Social Semantic Web Thesaurus took 0.10304546356201172s
Currency | Creation date check for Social Semantic Web Thesaurus took 0.18419218063354492s
Currency | Modification date check for Social Semantic Web Thesaurus took 0.25467419624328613s
Rep.Conc. | URIs length for Social Semantic Web Thesaurus took 1.5522096157073975s
Consistency | Deprecated classes/propertiers check for Social Semantic Web Thesaurus took 0.13158273696899414s
Accuracy | Check Functional Property for Social Semantic Web Thesaurus took 0.09972977638244629s
Accuracy | Check Inverse Functional Property for Social Semantic Web Thesaurus took 0.09631228446960449s
Accuracy | Check Empty annotation labels for Social Semantic Web Thesaurus took 0.5387864112854004s
Accuracy | Check White space in annotation for Social Semantic Web Thesaurus took 0.012517690658569336s
Consistency | Disjoint class check for Social Semantic Web Thesaurus took 0.10898780822753906s
Consistency | Check Misplaced properties for Social Semantic Web Thesaurus took 0.3223381042480469s
Consistency | Misplaced classes for Social Semantic Web Thesaurus took 0.10120463371276855s
Consistency | Check Ontology hijacking for Social Semantic Web Thesaurus took 2.046555280685425s
Consistency | Check Invalid usage of undefined properties for Social Semantic Web Thesaurus took 1.3577964305877686s
Conciseness | Check Extensional conciseness for Social Semantic Web Thesaurus took 0.00015664100646972656s
Security | Sign check for Social Semantic Web Thesaurus took 0.10389137268066406s
Availability | Check URIs Dereferenciability for Social Semantic Web Thesaurus took 109.28916645050049s
Completeness | Calculation of interlinking completeness for Social Semantic Web Thesaurus took 0.2555198669433594s
Reputation | Calculation of the PageRank for Social Semantic Web Thesaurus took 0.02279949188232422s
Interlinking | Calculation of Degree of Connection for Social Semantic Web Thesaurus took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Social Semantic Web Thesaurus took 0.0006890296936035156s
Interlinking | Calculation of Clustering coefficient for Social Semantic Web Thesaurus took 8.893013000488281e-05s
Believability | Calculation of trust value for Social Semantic Web Thesaurus took 6.4373016357421875e-06s
INFO | --- Analysis for socialsemweb-thesaurus took 244.49757051467896s
Availability | SPARQL endpoint availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.8530709743499756s
Availability | VoID file availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.00023555755615234375s
Completeness | Calculation of interlinking completeness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.3004734516143799s
Reputation | Calculation of the PageRank for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.020368576049804688s
Interlinking | Calculation of Degree of Connection for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.86102294921875e-05s
Believability | Calculation of trust value for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 5.0067901611328125e-06s
INFO | --- Analysis for Soil_maps took 3.9202775955200195s
Availability | SPARQL endpoint availability check for terrorrist ontology took 4.291534423828125e-05s
Availability | VoID file availability check for terrorrist ontology took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for terrorrist ontology took 0.27820324897766113s
Reputation | Calculation of the PageRank for terrorrist ontology took 0.02048945426940918s
Interlinking | Calculation of Degree of Connection for terrorrist ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for terrorrist ontology took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for terrorrist ontology took 2.86102294921875e-05s
Believability | Calculation of trust value for terrorrist ontology took 6.67572021484375e-06s
INFO | --- Analysis for somya_omer took 2.8541789054870605s
Availability | SPARQL endpoint availability check for Sonclubcx took 4.00543212890625e-05s
Availability | VoID file availability check for Sonclubcx took 0.0005431175231933594s
Completeness | Calculation of interlinking completeness for Sonclubcx took 0.24454712867736816s
Reputation | Calculation of the PageRank for Sonclubcx took 0.020112276077270508s
Interlinking | Calculation of Degree of Connection for Sonclubcx took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Sonclubcx took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Sonclubcx took 1.0728836059570312e-05s
Believability | Calculation of trust value for Sonclubcx took 6.9141387939453125e-06s
INFO | --- Analysis for sonclubcx took 5.190755844116211s
Availability | SPARQL endpoint availability check for SORS took 4.00543212890625e-05s
Availability | VoID file availability check for SORS took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for SORS took 0.26258039474487305s
Reputation | Calculation of the PageRank for SORS took 0.020040273666381836s
Interlinking | Calculation of Degree of Connection for SORS took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SORS took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for SORS took 4.7206878662109375e-05s
Believability | Calculation of trust value for SORS took 4.291534423828125e-06s
INFO | --- Analysis for sors took 3.1516661643981934s
Availability | SPARQL endpoint availability check for Soudy České republiky took 3.981590270996094e-05s
Availability | VoID file availability check for Soudy České republiky took 0.00022029876708984375s
Completeness | Calculation of interlinking completeness for Soudy České republiky took 0.264110803604126s
Reputation | Calculation of the PageRank for Soudy České republiky took 0.020256757736206055s
Interlinking | Calculation of Degree of Connection for Soudy České republiky took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Soudy České republiky took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Soudy České republiky took 2.7418136596679688e-05s
Believability | Calculation of trust value for Soudy České republiky took 5.7220458984375e-06s
INFO | --- Analysis for soudy--esk--republiky took 3.393061876296997s
Availability | SPARQL endpoint availability check for southampton-ac-uk took 4.9591064453125e-05s
Availability | VoID file availability check for southampton-ac-uk took 0.0005993843078613281s
Completeness | Calculation of interlinking completeness for southampton-ac-uk took 0.26633143424987793s
Reputation | Calculation of the PageRank for southampton-ac-uk took 0.020536184310913086s
Interlinking | Calculation of Degree of Connection for southampton-ac-uk took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for southampton-ac-uk took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for southampton-ac-uk took 9.036064147949219e-05s
Believability | Calculation of trust value for southampton-ac-uk took 7.62939453125e-06s
INFO | --- Analysis for southampton-ac-uk took 4.655749320983887s
Availability | SPARQL endpoint availability check for Apps using our data (University of Southampton) took 2.988544225692749s
Availability | VoID file availability check for Apps using our data (University of Southampton) took 0.0005934238433837891s
Completeness | Calculation of interlinking completeness for Apps using our data (University of Southampton) took 0.30979371070861816s
Reputation | Calculation of the PageRank for Apps using our data (University of Southampton) took 0.02043938636779785s
Interlinking | Calculation of Degree of Connection for Apps using our data (University of Southampton) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apps using our data (University of Southampton) took 0.0007960796356201172s
Interlinking | Calculation of Clustering coefficient for Apps using our data (University of Southampton) took 3.0040740966796875e-05s
Believability | Calculation of trust value for Apps using our data (University of Southampton) took 6.198883056640625e-06s
INFO | --- Analysis for southampton-ac-uk-apps took 10.1365487575531s
Availability | SPARQL endpoint availability check for ECS Southampton EPrints took 4.363059997558594e-05s
Availability | VoID file availability check for ECS Southampton EPrints took 0.0005888938903808594s
Completeness | Calculation of interlinking completeness for ECS Southampton EPrints took 0.2861144542694092s
Reputation | Calculation of the PageRank for ECS Southampton EPrints took 0.02026844024658203s
Interlinking | Calculation of Degree of Connection for ECS Southampton EPrints took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ECS Southampton EPrints took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for ECS Southampton EPrints took 0.00010657310485839844s
Believability | Calculation of trust value for ECS Southampton EPrints took 5.7220458984375e-06s
INFO | --- Analysis for southampton-ecs-eprints took 5.148935317993164s
Availability | SPARQL endpoint availability check for Spanish Linguistic Datasets took 0.5600285530090332s
Availability | VoID file availability check for Spanish Linguistic Datasets took 0.0002751350402832031s
Extra | Recovery of all triples for Spanish Linguistic Datasets took 165.44787216186523s
Performance | Total latancy measurement for Spanish Linguistic Datasets took 1.1861095428466797s
Amount of data | Number of triples check for Spanish Linguistic Datasets took 2.1657073497772217s
Interoperability | New terms check for Spanish Linguistic Datasets took 2.96909761428833s
Versatility | Languages check for Spanish Linguistic Datasets took 45.078150033950806s
Interpretability | Number of blank nodes check for Spanish Linguistic Datasets took 1.2525010108947754s
Security | Check HTTPS for Spanish Linguistic Datasets took 0.13633131980895996s
Interpretability | RDF structures check for Spanish Linguistic Datasets took 0.29942798614501953s
Versatility | Serialization formats check for Spanish Linguistic Datasets took 0.28468942642211914s
Availability | RDF dump link check for Spanish Linguistic Datasets took 0.3088107109069824s
License | MR license check for Spanish Linguistic Datasets took 0.28049516677856445s
License | HR license check for Spanish Linguistic Datasets took 0.4053826332092285s
Amount of data | Number of property check for Spanish Linguistic Datasets took 0.3044414520263672s
Understandability | Number of label check for Spanish Linguistic Datasets took 0.3097243309020996s
Understandability | URI regex check for Spanish Linguistic Datasets took 0.562506914138794s
Understandability | Vocabs check for Spanish Linguistic Datasets took 0.30941343307495117s
Verifiability | Authors check for Spanish Linguistic Datasets took 0.3060433864593506s
Verifiability | Publishers check for Spanish Linguistic Datasets took 0.3170602321624756s
Performance | Throughput check for Spanish Linguistic Datasets took 11.196317911148071s
Amount of data | Check the number of entities for Spanish Linguistic Datasets took 7.152557373046875e-05s
Verifiability | Contribs. check for Spanish Linguistic Datasets took 0.2920668125152588s
Interlinking | sameAs chians check for Spanish Linguistic Datasets took 0.28940916061401367s
Interlinking | skos check for Spanish Linguistic Datasets took 0.3118462562561035s
Interlinking | skos check for Spanish Linguistic Datasets took 0.2346968650817871s
Timeliness | dataset update frequency check for Spanish Linguistic Datasets took 0.28917694091796875s
Currency | Creation date check for Spanish Linguistic Datasets took 0.5914158821105957s
Currency | Modification date check for Spanish Linguistic Datasets took 0.5796208381652832s
Rep.Conc. | URIs length for Spanish Linguistic Datasets took 58.518075704574585s
Interoperability | New vocabularies check for Spanish Linguistic Datasets took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Spanish Linguistic Datasets took 0.2728583812713623s
Accuracy | Check Functional Property for Spanish Linguistic Datasets took 0.2800710201263428s
Accuracy | Check Inverse Functional Property for Spanish Linguistic Datasets took 0.2809567451477051s
Accuracy | Check Empty annotation labels for Spanish Linguistic Datasets took 0.9837663173675537s
Accuracy | Check White space in annotation for Spanish Linguistic Datasets took 0.010387897491455078s
Accuracy | Check Datatype consistency for Spanish Linguistic Datasets took 2.6431679725646973s
Consistency | Disjoint class check for Spanish Linguistic Datasets took 0.2920258045196533s
Consistency | Check Misplaced properties for Spanish Linguistic Datasets took 4.5619635581970215s
Consistency | Misplaced classes for Spanish Linguistic Datasets took 8.670674085617065s
Consistency | Check Ontology hijacking for Spanish Linguistic Datasets took 44.17414402961731s
Consistency | Check Invalid usage of undefined classes for Spanish Linguistic Datasets took 1.3216629028320312s
Consistency | Check Invalid usage of undefined properties for Spanish Linguistic Datasets took 5.475930690765381s
Conciseness | Check Extensional conciseness for Spanish Linguistic Datasets took 2.8542206287384033s
Conciseness | Check Intensional conciseness for Spanish Linguistic Datasets took 0.29131436347961426s
Security | Sign check for Spanish Linguistic Datasets took 0.2807776927947998s
Availability | Check URIs Dereferenciability for Spanish Linguistic Datasets took 6.141866445541382s
Completeness | Calculation of interlinking completeness for Spanish Linguistic Datasets took 1.310354232788086s
Reputation | Calculation of the PageRank for Spanish Linguistic Datasets took 0.02170109748840332s
Interlinking | Calculation of Degree of Connection for Spanish Linguistic Datasets took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Spanish Linguistic Datasets took 0.0006747245788574219s
Interlinking | Calculation of Clustering coefficient for Spanish Linguistic Datasets took 2.9802322387695312e-05s
Interoperability | Check the re-using of existing vocabs for Spanish Linguistic Datasets took 1.9073486328125e-06s
Believability | Calculation of trust value for Spanish Linguistic Datasets took 7.867813110351562e-06s
INFO | --- Analysis for spanish-linguistic-datasets took 413.90556716918945s
Availability | SPARQL endpoint availability check for SPARQL Endpoint Status took 0.0698401927947998s
Availability | VoID file availability check for SPARQL Endpoint Status took 0.0002307891845703125s
Completeness | Calculation of interlinking completeness for SPARQL Endpoint Status took 0.25397753715515137s
Reputation | Calculation of the PageRank for SPARQL Endpoint Status took 0.020368576049804688s
Interlinking | Calculation of Degree of Connection for SPARQL Endpoint Status took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SPARQL Endpoint Status took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for SPARQL Endpoint Status took 4.5299530029296875e-05s
Believability | Calculation of trust value for SPARQL Endpoint Status took 6.198883056640625e-06s
INFO | --- Analysis for sparql-endpoint-status took 3.7239136695861816s
Availability | SPARQL endpoint availability check for SPC publikovaná SÚKL took 4.1961669921875e-05s
Availability | VoID file availability check for SPC publikovaná SÚKL took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for SPC publikovaná SÚKL took 0.2657585144042969s
Reputation | Calculation of the PageRank for SPC publikovaná SÚKL took 0.02036142349243164s
Interlinking | Calculation of Degree of Connection for SPC publikovaná SÚKL took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SPC publikovaná SÚKL took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for SPC publikovaná SÚKL took 2.86102294921875e-05s
Believability | Calculation of trust value for SPC publikovaná SÚKL took 5.7220458984375e-06s
INFO | --- Analysis for spc-publikovan--s-kl took 3.358269214630127s
Availability | SPARQL endpoint availability check for SPQR took 7.867813110351562e-05s
Availability | VoID file availability check for SPQR took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for SPQR took 0.6899285316467285s
Reputation | Calculation of the PageRank for SPQR took 0.020215272903442383s
Interlinking | Calculation of Degree of Connection for SPQR took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SPQR took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for SPQR took 2.8371810913085938e-05s
Believability | Calculation of trust value for SPQR took 6.4373016357421875e-06s
INFO | --- Analysis for spqr took 5.090500116348267s
Availability | SPARQL endpoint availability check for Springer Nature SciGraph took 4.363059997558594e-05s
Availability | VoID file availability check for Springer Nature SciGraph took 0.00043082237243652344s
Completeness | Calculation of interlinking completeness for Springer Nature SciGraph took 0.25893163681030273s
Reputation | Calculation of the PageRank for Springer Nature SciGraph took 0.020416259765625s
Interlinking | Calculation of Degree of Connection for Springer Nature SciGraph took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Springer Nature SciGraph took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Springer Nature SciGraph took 8.749961853027344e-05s
Believability | Calculation of trust value for Springer Nature SciGraph took 5.0067901611328125e-06s
INFO | --- Analysis for springernaturescigraph took 2.846191883087158s
Availability | SPARQL endpoint availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 4.291534423828125e-05s
Availability | VoID file availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0005922317504882812s
Completeness | Calculation of interlinking completeness for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.2870619297027588s
Reputation | Calculation of the PageRank for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.02040576934814453s
Interlinking | Calculation of Degree of Connection for Syntactic Reference Corpus of Medieval French (SRCMF) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Syntactic Reference Corpus of Medieval French (SRCMF) took 3.0040740966796875e-05s
Believability | Calculation of trust value for Syntactic Reference Corpus of Medieval French (SRCMF) took 6.67572021484375e-06s
INFO | --- Analysis for srcmf took 6.696335077285767s
Availability | SPARQL endpoint availability check for Lexicon of Syntactic and Semantic Framework took 30.24029278755188s
Availability | VoID file availability check for Lexicon of Syntactic and Semantic Framework took 0.00064849853515625s
Completeness | Calculation of interlinking completeness for Lexicon of Syntactic and Semantic Framework took 0.2756197452545166s
Reputation | Calculation of the PageRank for Lexicon of Syntactic and Semantic Framework took 0.020380735397338867s
Interlinking | Calculation of Degree of Connection for Lexicon of Syntactic and Semantic Framework took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Lexicon of Syntactic and Semantic Framework took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Lexicon of Syntactic and Semantic Framework took 5.14984130859375e-05s
Believability | Calculation of trust value for Lexicon of Syntactic and Semantic Framework took 6.67572021484375e-06s
INFO | --- Analysis for ssf took 84.11514782905579s
Availability | SPARQL endpoint availability check for SSF took 4.76837158203125e-05s
Availability | VoID file availability check for SSF took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for SSF took 0.703284502029419s
Reputation | Calculation of the PageRank for SSF took 0.020393848419189453s
Interlinking | Calculation of Degree of Connection for SSF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SSF took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for SSF took 2.8848648071289062e-05s
Believability | Calculation of trust value for SSF took 6.67572021484375e-06s
INFO | --- Analysis for ssf-lexicon took 4.626028776168823s
Availability | SPARQL endpoint availability check for St. Andrews University Resource Lists took 4.601478576660156e-05s
Availability | VoID file availability check for St. Andrews University Resource Lists took 0.0005950927734375s
Completeness | Calculation of interlinking completeness for St. Andrews University Resource Lists took 0.7052407264709473s
Reputation | Calculation of the PageRank for St. Andrews University Resource Lists took 0.02068018913269043s
Interlinking | Calculation of Degree of Connection for St. Andrews University Resource Lists took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for St. Andrews University Resource Lists took 0.0008962154388427734s
Interlinking | Calculation of Clustering coefficient for St. Andrews University Resource Lists took 4.100799560546875e-05s
Believability | Calculation of trust value for St. Andrews University Resource Lists took 5.4836273193359375e-06s
INFO | --- Analysis for st-andrews-resource-lists took 3.9724175930023193s
Availability | SPARQL endpoint availability check for STAC took 4.1961669921875e-05s
Availability | VoID file availability check for STAC took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for STAC took 0.29018092155456543s
Reputation | Calculation of the PageRank for STAC took 0.0228879451751709s
Interlinking | Calculation of Degree of Connection for STAC took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for STAC took 0.0016858577728271484s
Interlinking | Calculation of Clustering coefficient for STAC took 4.9114227294921875e-05s
Believability | Calculation of trust value for STAC took 7.867813110351562e-06s
INFO | --- Analysis for stac took 2.9607181549072266s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for The Scottish Government took 3.981590270996094e-05s
Availability | VoID file availability check for Organogram and staff pay data for The Scottish Government took 0.00023818016052246094s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for The Scottish Government took 0.24764537811279297s
Reputation | Calculation of the PageRank for Organogram and staff pay data for The Scottish Government took 0.020283222198486328s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for The Scottish Government took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Organogram and staff pay data for The Scottish Government took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for The Scottish Government took 2.86102294921875e-05s
Believability | Calculation of trust value for Organogram and staff pay data for The Scottish Government took 5.4836273193359375e-06s
INFO | --- Analysis for staff-organograms-and-pay-scottish-government took 2.918875217437744s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 4.2438507080078125e-05s
Availability | VoID file availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0005445480346679688s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.2747156620025635s
Reputation | Calculation of the PageRank for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.02025604248046875s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 3.1948089599609375e-05s
Believability | Calculation of trust value for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 4.76837158203125e-06s
INFO | --- Analysis for staff-organograms-and-pay-thurrock-thames-gateway-development-corporation took 5.022097587585449s
Availability | SPARQL endpoint availability check for Stammbuch took 4.100799560546875e-05s
Availability | VoID file availability check for Stammbuch took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for Stammbuch took 0.27680325508117676s
Reputation | Calculation of the PageRank for Stammbuch took 0.020450830459594727s
Interlinking | Calculation of Degree of Connection for Stammbuch took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Stammbuch took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Stammbuch took 2.7894973754882812e-05s
Believability | Calculation of trust value for Stammbuch took 6.4373016357421875e-06s
INFO | --- Analysis for Stammbuch took 3.7581615447998047s
Availability | SPARQL endpoint availability check for statistics.data.gov.uk took 1.5931310653686523s
Availability | VoID file availability check for statistics.data.gov.uk took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for statistics.data.gov.uk took 0.6992650032043457s
Reputation | Calculation of the PageRank for statistics.data.gov.uk took 0.02023625373840332s
Interlinking | Calculation of Degree of Connection for statistics.data.gov.uk took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statistics.data.gov.uk took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for statistics.data.gov.uk took 0.00010204315185546875s
Believability | Calculation of trust value for statistics.data.gov.uk took 4.76837158203125e-06s
INFO | --- Analysis for statistics-data-gov-uk took 4.8599631786346436s
Availability | SPARQL endpoint availability check for Statistics on Fatal Traffic Accidents in greek roads took 4.076957702636719e-05s
Availability | VoID file availability check for Statistics on Fatal Traffic Accidents in greek roads took 0.0002803802490234375s
Completeness | Calculation of interlinking completeness for Statistics on Fatal Traffic Accidents in greek roads took 0.2858750820159912s
Reputation | Calculation of the PageRank for Statistics on Fatal Traffic Accidents in greek roads took 0.020386934280395508s
Interlinking | Calculation of Degree of Connection for Statistics on Fatal Traffic Accidents in greek roads took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Statistics on Fatal Traffic Accidents in greek roads took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Statistics on Fatal Traffic Accidents in greek roads took 2.8848648071289062e-05s
Believability | Calculation of trust value for Statistics on Fatal Traffic Accidents in greek roads took 5.9604644775390625e-06s
INFO | --- Analysis for statistics-on-fatal-traffic-accidents-in-greek-roads took 2.9857077598571777s
Availability | SPARQL endpoint availability check for statusnet-1w6-org took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-1w6-org took 0.0006222724914550781s
Completeness | Calculation of interlinking completeness for statusnet-1w6-org took 0.26036858558654785s
Reputation | Calculation of the PageRank for statusnet-1w6-org took 0.020445585250854492s
Interlinking | Calculation of Degree of Connection for statusnet-1w6-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-1w6-org took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for statusnet-1w6-org took 0.000102996826171875s
Believability | Calculation of trust value for statusnet-1w6-org took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-1w6-org took 2.8369598388671875s
Availability | SPARQL endpoint availability check for statusnet-20100-org took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-20100-org took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for statusnet-20100-org took 0.2762453556060791s
Reputation | Calculation of the PageRank for statusnet-20100-org took 0.0206298828125s
Interlinking | Calculation of Degree of Connection for statusnet-20100-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-20100-org took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for statusnet-20100-org took 6.318092346191406e-05s
Believability | Calculation of trust value for statusnet-20100-org took 5.0067901611328125e-06s
INFO | --- Analysis for statusnet-20100-org took 2.4584364891052246s
Availability | SPARQL endpoint availability check for statusnet-alexandrefranke-com took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-alexandrefranke-com took 0.0004978179931640625s
Completeness | Calculation of interlinking completeness for statusnet-alexandrefranke-com took 0.2718639373779297s
Reputation | Calculation of the PageRank for statusnet-alexandrefranke-com took 0.020575761795043945s
Interlinking | Calculation of Degree of Connection for statusnet-alexandrefranke-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-alexandrefranke-com took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for statusnet-alexandrefranke-com took 7.033348083496094e-05s
Believability | Calculation of trust value for statusnet-alexandrefranke-com took 5.7220458984375e-06s
INFO | --- Analysis for statusnet-alexandrefranke-com took 2.8013105392456055s
Availability | SPARQL endpoint availability check for statusnet-atari-frosch-de took 5.316734313964844e-05s
Availability | VoID file availability check for statusnet-atari-frosch-de took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for statusnet-atari-frosch-de took 0.26937174797058105s
Reputation | Calculation of the PageRank for statusnet-atari-frosch-de took 0.0202789306640625s
Interlinking | Calculation of Degree of Connection for statusnet-atari-frosch-de took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-atari-frosch-de took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for statusnet-atari-frosch-de took 7.987022399902344e-05s
Believability | Calculation of trust value for statusnet-atari-frosch-de took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-atari-frosch-de took 2.3984181880950928s
Availability | SPARQL endpoint availability check for statusnet-belfalas-org took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-belfalas-org took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for statusnet-belfalas-org took 0.2621920108795166s
Reputation | Calculation of the PageRank for statusnet-belfalas-org took 0.020299673080444336s
Interlinking | Calculation of Degree of Connection for statusnet-belfalas-org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-belfalas-org took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for statusnet-belfalas-org took 9.298324584960938e-05s
Believability | Calculation of trust value for statusnet-belfalas-org took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-belfalas-org took 2.455939531326294s
Availability | SPARQL endpoint availability check for statusnet-bka-li took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-bka-li took 0.0005593299865722656s
Completeness | Calculation of interlinking completeness for statusnet-bka-li took 0.27773022651672363s
Reputation | Calculation of the PageRank for statusnet-bka-li took 0.020690202713012695s
Interlinking | Calculation of Degree of Connection for statusnet-bka-li took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-bka-li took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for statusnet-bka-li took 0.00011229515075683594s
Believability | Calculation of trust value for statusnet-bka-li took 5.9604644775390625e-06s
INFO | --- Analysis for statusnet-bka-li took 2.5150880813598633s
Availability | SPARQL endpoint availability check for statusnet-bonifaz-ec took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-bonifaz-ec took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for statusnet-bonifaz-ec took 0.26759934425354004s
Reputation | Calculation of the PageRank for statusnet-bonifaz-ec took 0.02053666114807129s
Interlinking | Calculation of Degree of Connection for statusnet-bonifaz-ec took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-bonifaz-ec took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for statusnet-bonifaz-ec took 4.076957702636719e-05s
Believability | Calculation of trust value for statusnet-bonifaz-ec took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-bonifaz-ec took 3.4570164680480957s
Availability | SPARQL endpoint availability check for statusnet-ced117-net took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-ced117-net took 0.0005977153778076172s
Completeness | Calculation of interlinking completeness for statusnet-ced117-net took 0.2530241012573242s
Reputation | Calculation of the PageRank for statusnet-ced117-net took 0.02057027816772461s
Interlinking | Calculation of Degree of Connection for statusnet-ced117-net took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-ced117-net took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for statusnet-ced117-net took 4.982948303222656e-05s
Believability | Calculation of trust value for statusnet-ced117-net took 5.9604644775390625e-06s
INFO | --- Analysis for statusnet-ced117-net took 3.8560800552368164s
Availability | SPARQL endpoint availability check for statusnet-chickenkiller-com took 4.076957702636719e-05s
Availability | VoID file availability check for statusnet-chickenkiller-com took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for statusnet-chickenkiller-com took 0.25603413581848145s
Reputation | Calculation of the PageRank for statusnet-chickenkiller-com took 0.021048545837402344s
Interlinking | Calculation of Degree of Connection for statusnet-chickenkiller-com took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for statusnet-chickenkiller-com took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for statusnet-chickenkiller-com took 6.270408630371094e-05s
Believability | Calculation of trust value for statusnet-chickenkiller-com took 5.7220458984375e-06s
INFO | --- Analysis for statusnet-chickenkiller-com took 2.568033218383789s
Availability | SPARQL endpoint availability check for statusnet-chromic-org took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-chromic-org took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for statusnet-chromic-org took 0.2837674617767334s
Reputation | Calculation of the PageRank for statusnet-chromic-org took 0.020621061325073242s
Interlinking | Calculation of Degree of Connection for statusnet-chromic-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-chromic-org took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for statusnet-chromic-org took 0.00011038780212402344s
Believability | Calculation of trust value for statusnet-chromic-org took 5.9604644775390625e-06s
INFO | --- Analysis for statusnet-chromic-org took 2.5848472118377686s
Availability | SPARQL endpoint availability check for statusnet-cooleysekula-net took 4.601478576660156e-05s
Availability | VoID file availability check for statusnet-cooleysekula-net took 0.0006017684936523438s
Completeness | Calculation of interlinking completeness for statusnet-cooleysekula-net took 0.2803521156311035s
Reputation | Calculation of the PageRank for statusnet-cooleysekula-net took 0.020668745040893555s
Interlinking | Calculation of Degree of Connection for statusnet-cooleysekula-net took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-cooleysekula-net took 0.0006861686706542969s
Interlinking | Calculation of Clustering coefficient for statusnet-cooleysekula-net took 7.891654968261719e-05s
Believability | Calculation of trust value for statusnet-cooleysekula-net took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-cooleysekula-net took 8.567935228347778s
Availability | SPARQL endpoint availability check for statusnet-coreyavis-com took 4.0531158447265625e-05s
Availability | VoID file availability check for statusnet-coreyavis-com took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for statusnet-coreyavis-com took 0.2857391834259033s
Reputation | Calculation of the PageRank for statusnet-coreyavis-com took 0.020668745040893555s
Interlinking | Calculation of Degree of Connection for statusnet-coreyavis-com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-coreyavis-com took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for statusnet-coreyavis-com took 5.435943603515625e-05s
Believability | Calculation of trust value for statusnet-coreyavis-com took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-coreyavis-com took 2.454530715942383s
Availability | SPARQL endpoint availability check for statusnet-datenfahrt-org took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-datenfahrt-org took 0.000568389892578125s
Completeness | Calculation of interlinking completeness for statusnet-datenfahrt-org took 0.2768688201904297s
Reputation | Calculation of the PageRank for statusnet-datenfahrt-org took 0.020737171173095703s
Interlinking | Calculation of Degree of Connection for statusnet-datenfahrt-org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-datenfahrt-org took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for statusnet-datenfahrt-org took 7.05718994140625e-05s
Believability | Calculation of trust value for statusnet-datenfahrt-org took 5.4836273193359375e-06s
INFO | --- Analysis for statusnet-datenfahrt-org took 3.2920446395874023s
Availability | SPARQL endpoint availability check for statusnet-davidhaberthuer-ch took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-davidhaberthuer-ch took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for statusnet-davidhaberthuer-ch took 0.2512955665588379s
Reputation | Calculation of the PageRank for statusnet-davidhaberthuer-ch took 0.02056097984313965s
Interlinking | Calculation of Degree of Connection for statusnet-davidhaberthuer-ch took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-davidhaberthuer-ch took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for statusnet-davidhaberthuer-ch took 0.00010275840759277344s
Believability | Calculation of trust value for statusnet-davidhaberthuer-ch took 5.245208740234375e-06s
INFO | --- Analysis for statusnet-davidhaberthuer-ch took 2.5002591609954834s
Availability | SPARQL endpoint availability check for statusnet-deuxpi-ca took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-deuxpi-ca took 0.00048828125s
Completeness | Calculation of interlinking completeness for statusnet-deuxpi-ca took 0.2754824161529541s
Reputation | Calculation of the PageRank for statusnet-deuxpi-ca took 0.022447824478149414s
Interlinking | Calculation of Degree of Connection for statusnet-deuxpi-ca took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-deuxpi-ca took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for statusnet-deuxpi-ca took 7.033348083496094e-05s
Believability | Calculation of trust value for statusnet-deuxpi-ca took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-deuxpi-ca took 2.4131131172180176s
Availability | SPARQL endpoint availability check for statusnet-doomicile-de took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-doomicile-de took 0.0006010532379150391s
Completeness | Calculation of interlinking completeness for statusnet-doomicile-de took 0.2668449878692627s
Reputation | Calculation of the PageRank for statusnet-doomicile-de took 0.020793914794921875s
Interlinking | Calculation of Degree of Connection for statusnet-doomicile-de took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-doomicile-de took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for statusnet-doomicile-de took 5.1975250244140625e-05s
Believability | Calculation of trust value for statusnet-doomicile-de took 5.4836273193359375e-06s
INFO | --- Analysis for statusnet-doomicile-de took 3.2422034740448s
Availability | SPARQL endpoint availability check for statusnet-dtdns-net took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-dtdns-net took 0.0005791187286376953s
Completeness | Calculation of interlinking completeness for statusnet-dtdns-net took 0.24968218803405762s
Reputation | Calculation of the PageRank for statusnet-dtdns-net took 0.020385026931762695s
Interlinking | Calculation of Degree of Connection for statusnet-dtdns-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-dtdns-net took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for statusnet-dtdns-net took 5.8650970458984375e-05s
Believability | Calculation of trust value for statusnet-dtdns-net took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-dtdns-net took 6.045783281326294s
Availability | SPARQL endpoint availability check for statusnet-equestriarp-net took 6.747245788574219e-05s
Availability | VoID file availability check for statusnet-equestriarp-net took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for statusnet-equestriarp-net took 0.25331783294677734s
Reputation | Calculation of the PageRank for statusnet-equestriarp-net took 0.020930051803588867s
Interlinking | Calculation of Degree of Connection for statusnet-equestriarp-net took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-equestriarp-net took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for statusnet-equestriarp-net took 3.719329833984375e-05s
Believability | Calculation of trust value for statusnet-equestriarp-net took 5.9604644775390625e-06s
INFO | --- Analysis for statusnet-equestriarp-net took 2.423799514770508s
Availability | SPARQL endpoint availability check for statusnet-exdc-net took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-exdc-net took 0.0007266998291015625s
Completeness | Calculation of interlinking completeness for statusnet-exdc-net took 0.26698732376098633s
Reputation | Calculation of the PageRank for statusnet-exdc-net took 0.020386219024658203s
Interlinking | Calculation of Degree of Connection for statusnet-exdc-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-exdc-net took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for statusnet-exdc-net took 7.367134094238281e-05s
Believability | Calculation of trust value for statusnet-exdc-net took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-exdc-net took 12.710035562515259s
Availability | SPARQL endpoint availability check for statusnet-fcac-com took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-fcac-com took 0.0007390975952148438s
Completeness | Calculation of interlinking completeness for statusnet-fcac-com took 0.2628498077392578s
Reputation | Calculation of the PageRank for statusnet-fcac-com took 0.020699501037597656s
Interlinking | Calculation of Degree of Connection for statusnet-fcac-com took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-fcac-com took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for statusnet-fcac-com took 9.655952453613281e-05s
Believability | Calculation of trust value for statusnet-fcac-com took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-fcac-com took 22.450052738189697s
Availability | SPARQL endpoint availability check for statusnet-fcestrada-com took 4.506111145019531e-05s
Availability | VoID file availability check for statusnet-fcestrada-com took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for statusnet-fcestrada-com took 0.2821846008300781s
Reputation | Calculation of the PageRank for statusnet-fcestrada-com took 0.020877838134765625s
Interlinking | Calculation of Degree of Connection for statusnet-fcestrada-com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-fcestrada-com took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for statusnet-fcestrada-com took 5.53131103515625e-05s
Believability | Calculation of trust value for statusnet-fcestrada-com took 5.245208740234375e-06s
INFO | --- Analysis for statusnet-fcestrada-com took 2.5452165603637695s
Availability | SPARQL endpoint availability check for statusnet-fragdev-com took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-fragdev-com took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for statusnet-fragdev-com took 0.302354097366333s
Reputation | Calculation of the PageRank for statusnet-fragdev-com took 0.02057027816772461s
Interlinking | Calculation of Degree of Connection for statusnet-fragdev-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-fragdev-com took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for statusnet-fragdev-com took 0.00020694732666015625s
Believability | Calculation of trust value for statusnet-fragdev-com took 5.7220458984375e-06s
INFO | --- Analysis for statusnet-fragdev-com took 3.014000177383423s
Availability | SPARQL endpoint availability check for statusnet-freelish-us took 4.0531158447265625e-05s
Availability | VoID file availability check for statusnet-freelish-us took 0.0006406307220458984s
Completeness | Calculation of interlinking completeness for statusnet-freelish-us took 0.2725369930267334s
Reputation | Calculation of the PageRank for statusnet-freelish-us took 0.020672082901000977s
Interlinking | Calculation of Degree of Connection for statusnet-freelish-us took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-freelish-us took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for statusnet-freelish-us took 7.367134094238281e-05s
Believability | Calculation of trust value for statusnet-freelish-us took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-freelish-us took 2.5111160278320312s
Availability | SPARQL endpoint availability check for statusnet-gegeweb-org took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-gegeweb-org took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for statusnet-gegeweb-org took 0.2610294818878174s
Reputation | Calculation of the PageRank for statusnet-gegeweb-org took 0.02053213119506836s
Interlinking | Calculation of Degree of Connection for statusnet-gegeweb-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-gegeweb-org took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for statusnet-gegeweb-org took 0.00010633468627929688s
Believability | Calculation of trust value for statusnet-gegeweb-org took 5.7220458984375e-06s
INFO | --- Analysis for statusnet-gegeweb-org took 2.4600374698638916s
Availability | SPARQL endpoint availability check for statusnet-glou-org took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-glou-org took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for statusnet-glou-org took 0.27303600311279297s
Reputation | Calculation of the PageRank for statusnet-glou-org took 0.02055835723876953s
Interlinking | Calculation of Degree of Connection for statusnet-glou-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-glou-org took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for statusnet-glou-org took 6.365776062011719e-05s
Believability | Calculation of trust value for statusnet-glou-org took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-glou-org took 2.5430068969726562s
Availability | SPARQL endpoint availability check for statusnet-gomertronic-com took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-gomertronic-com took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for statusnet-gomertronic-com took 0.2630913257598877s
Reputation | Calculation of the PageRank for statusnet-gomertronic-com took 0.020716428756713867s
Interlinking | Calculation of Degree of Connection for statusnet-gomertronic-com took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-gomertronic-com took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for statusnet-gomertronic-com took 0.00012493133544921875s
Believability | Calculation of trust value for statusnet-gomertronic-com took 5.245208740234375e-06s
INFO | --- Analysis for statusnet-gomertronic-com took 3.3423495292663574s
Availability | SPARQL endpoint availability check for statusnet-hackerposse-com took 6.985664367675781e-05s
Availability | VoID file availability check for statusnet-hackerposse-com took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for statusnet-hackerposse-com took 0.24632954597473145s
Reputation | Calculation of the PageRank for statusnet-hackerposse-com took 0.020495176315307617s
Interlinking | Calculation of Degree of Connection for statusnet-hackerposse-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-hackerposse-com took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for statusnet-hackerposse-com took 0.00010180473327636719s
Believability | Calculation of trust value for statusnet-hackerposse-com took 5.245208740234375e-06s
INFO | --- Analysis for statusnet-hackerposse-com took 2.8752048015594482s
Availability | SPARQL endpoint availability check for statusnet-hii-co-il took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-hii-co-il took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for statusnet-hii-co-il took 0.2501969337463379s
Reputation | Calculation of the PageRank for statusnet-hii-co-il took 0.020805835723876953s
Interlinking | Calculation of Degree of Connection for statusnet-hii-co-il took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-hii-co-il took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for statusnet-hii-co-il took 4.887580871582031e-05s
Believability | Calculation of trust value for statusnet-hii-co-il took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-hii-co-il took 3.0151779651641846s
Availability | SPARQL endpoint availability check for statusnet-ilikefreedom-ro took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-ilikefreedom-ro took 0.0006723403930664062s
Completeness | Calculation of interlinking completeness for statusnet-ilikefreedom-ro took 0.28932857513427734s
Reputation | Calculation of the PageRank for statusnet-ilikefreedom-ro took 0.020638465881347656s
Interlinking | Calculation of Degree of Connection for statusnet-ilikefreedom-ro took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-ilikefreedom-ro took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for statusnet-ilikefreedom-ro took 9.775161743164062e-05s
Believability | Calculation of trust value for statusnet-ilikefreedom-ro took 7.62939453125e-06s
INFO | --- Analysis for statusnet-ilikefreedom-ro took 3.3393945693969727s
Availability | SPARQL endpoint availability check for statusnet-imirhil-fr took 4.982948303222656e-05s
Availability | VoID file availability check for statusnet-imirhil-fr took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for statusnet-imirhil-fr took 0.24672508239746094s
Reputation | Calculation of the PageRank for statusnet-imirhil-fr took 0.020374536514282227s
Interlinking | Calculation of Degree of Connection for statusnet-imirhil-fr took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-imirhil-fr took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for statusnet-imirhil-fr took 6.103515625e-05s
Believability | Calculation of trust value for statusnet-imirhil-fr took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-imirhil-fr took 2.562417984008789s
Availability | SPARQL endpoint availability check for statusnet-integralblue-com took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-integralblue-com took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for statusnet-integralblue-com took 0.2705843448638916s
Reputation | Calculation of the PageRank for statusnet-integralblue-com took 0.020653724670410156s
Interlinking | Calculation of Degree of Connection for statusnet-integralblue-com took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-integralblue-com took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for statusnet-integralblue-com took 4.029273986816406e-05s
Believability | Calculation of trust value for statusnet-integralblue-com took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-integralblue-com took 2.7024552822113037s
Availability | SPARQL endpoint availability check for statusnet-johndrinkwater-name took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-johndrinkwater-name took 0.0006957054138183594s
Completeness | Calculation of interlinking completeness for statusnet-johndrinkwater-name took 0.2706317901611328s
Reputation | Calculation of the PageRank for statusnet-johndrinkwater-name took 0.020325183868408203s
Interlinking | Calculation of Degree of Connection for statusnet-johndrinkwater-name took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-johndrinkwater-name took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for statusnet-johndrinkwater-name took 5.91278076171875e-05s
Believability | Calculation of trust value for statusnet-johndrinkwater-name took 5.7220458984375e-06s
INFO | --- Analysis for statusnet-johndrinkwater-name took 22.434447288513184s
Availability | SPARQL endpoint availability check for statusnet-jonkman-ca took 4.5299530029296875e-05s
Availability | VoID file availability check for statusnet-jonkman-ca took 0.0007619857788085938s
Completeness | Calculation of interlinking completeness for statusnet-jonkman-ca took 0.26137614250183105s
Reputation | Calculation of the PageRank for statusnet-jonkman-ca took 0.0204164981842041s
Interlinking | Calculation of Degree of Connection for statusnet-jonkman-ca took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-jonkman-ca took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for statusnet-jonkman-ca took 0.00011467933654785156s
Believability | Calculation of trust value for statusnet-jonkman-ca took 5.245208740234375e-06s
INFO | --- Analysis for statusnet-jonkman-ca took 13.015724658966064s
Availability | SPARQL endpoint availability check for statusnet-kaimi-cc took 5.4836273193359375e-05s
Availability | VoID file availability check for statusnet-kaimi-cc took 0.0005919933319091797s
Completeness | Calculation of interlinking completeness for statusnet-kaimi-cc took 0.28931331634521484s
Reputation | Calculation of the PageRank for statusnet-kaimi-cc took 0.020514965057373047s
Interlinking | Calculation of Degree of Connection for statusnet-kaimi-cc took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-kaimi-cc took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for statusnet-kaimi-cc took 9.703636169433594e-05s
Believability | Calculation of trust value for statusnet-kaimi-cc took 7.62939453125e-06s
INFO | --- Analysis for statusnet-kaimi-cc took 2.4816839694976807s
Availability | SPARQL endpoint availability check for statusnet-kathryl-fr took 4.5299530029296875e-05s
Availability | VoID file availability check for statusnet-kathryl-fr took 0.0005035400390625s
Completeness | Calculation of interlinking completeness for statusnet-kathryl-fr took 0.2733182907104492s
Reputation | Calculation of the PageRank for statusnet-kathryl-fr took 0.020551204681396484s
Interlinking | Calculation of Degree of Connection for statusnet-kathryl-fr took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-kathryl-fr took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for statusnet-kathryl-fr took 5.030632019042969e-05s
Believability | Calculation of trust value for statusnet-kathryl-fr took 5.9604644775390625e-06s
INFO | --- Analysis for statusnet-kathryl-fr took 2.4360697269439697s
Availability | SPARQL endpoint availability check for statusnet-kenzoid-com took 5.269050598144531e-05s
Availability | VoID file availability check for statusnet-kenzoid-com took 0.0007414817810058594s
Completeness | Calculation of interlinking completeness for statusnet-kenzoid-com took 0.2668623924255371s
Reputation | Calculation of the PageRank for statusnet-kenzoid-com took 0.02051258087158203s
Interlinking | Calculation of Degree of Connection for statusnet-kenzoid-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-kenzoid-com took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for statusnet-kenzoid-com took 3.814697265625e-05s
Believability | Calculation of trust value for statusnet-kenzoid-com took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-kenzoid-com took 3.2117865085601807s
Availability | SPARQL endpoint availability check for statusnet-keuser-fr took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-keuser-fr took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for statusnet-keuser-fr took 0.2615807056427002s
Reputation | Calculation of the PageRank for statusnet-keuser-fr took 0.02023935317993164s
Interlinking | Calculation of Degree of Connection for statusnet-keuser-fr took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-keuser-fr took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for statusnet-keuser-fr took 6.866455078125e-05s
Believability | Calculation of trust value for statusnet-keuser-fr took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-keuser-fr took 2.4823970794677734s
Availability | SPARQL endpoint availability check for statusnet-ldn-fai-net took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-ldn-fai-net took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for statusnet-ldn-fai-net took 0.2513420581817627s
Reputation | Calculation of the PageRank for statusnet-ldn-fai-net took 0.020489215850830078s
Interlinking | Calculation of Degree of Connection for statusnet-ldn-fai-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-ldn-fai-net took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for statusnet-ldn-fai-net took 4.601478576660156e-05s
Believability | Calculation of trust value for statusnet-ldn-fai-net took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-ldn-fai-net took 2.5383009910583496s
Availability | SPARQL endpoint availability check for statusnet-lebsanft-org took 4.506111145019531e-05s
Availability | VoID file availability check for statusnet-lebsanft-org took 0.0005767345428466797s
Completeness | Calculation of interlinking completeness for statusnet-lebsanft-org took 0.2753269672393799s
Reputation | Calculation of the PageRank for statusnet-lebsanft-org took 0.020119667053222656s
Interlinking | Calculation of Degree of Connection for statusnet-lebsanft-org took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-lebsanft-org took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for statusnet-lebsanft-org took 5.888938903808594e-05s
Believability | Calculation of trust value for statusnet-lebsanft-org took 5.9604644775390625e-06s
INFO | --- Analysis for statusnet-lebsanft-org took 2.590118885040283s
Availability | SPARQL endpoint availability check for statusnet-legadolibre-com-ar took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-legadolibre-com-ar took 0.0010898113250732422s
Completeness | Calculation of interlinking completeness for statusnet-legadolibre-com-ar took 0.28101015090942383s
Reputation | Calculation of the PageRank for statusnet-legadolibre-com-ar took 0.020624876022338867s
Interlinking | Calculation of Degree of Connection for statusnet-legadolibre-com-ar took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-legadolibre-com-ar took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for statusnet-legadolibre-com-ar took 9.274482727050781e-05s
Believability | Calculation of trust value for statusnet-legadolibre-com-ar took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-legadolibre-com-ar took 2.875598907470703s
Availability | SPARQL endpoint availability check for statusnet-linuxwrangling-com took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-linuxwrangling-com took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for statusnet-linuxwrangling-com took 0.26569032669067383s
Reputation | Calculation of the PageRank for statusnet-linuxwrangling-com took 0.020414352416992188s
Interlinking | Calculation of Degree of Connection for statusnet-linuxwrangling-com took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-linuxwrangling-com took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for statusnet-linuxwrangling-com took 0.00011324882507324219s
Believability | Calculation of trust value for statusnet-linuxwrangling-com took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-linuxwrangling-com took 2.77300763130188s
Availability | SPARQL endpoint availability check for statusnet-ludost-net took 4.482269287109375e-05s
Availability | VoID file availability check for statusnet-ludost-net took 0.0005726814270019531s
Completeness | Calculation of interlinking completeness for statusnet-ludost-net took 0.25689077377319336s
Reputation | Calculation of the PageRank for statusnet-ludost-net took 0.02022552490234375s
Interlinking | Calculation of Degree of Connection for statusnet-ludost-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-ludost-net took 0.0006856918334960938s
Interlinking | Calculation of Clustering coefficient for statusnet-ludost-net took 5.984306335449219e-05s
Believability | Calculation of trust value for statusnet-ludost-net took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-ludost-net took 3.4197142124176025s
Availability | SPARQL endpoint availability check for statusnet-lydiastench-com took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-lydiastench-com took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for statusnet-lydiastench-com took 0.28558802604675293s
Reputation | Calculation of the PageRank for statusnet-lydiastench-com took 0.02039933204650879s
Interlinking | Calculation of Degree of Connection for statusnet-lydiastench-com took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for statusnet-lydiastench-com took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for statusnet-lydiastench-com took 9.5367431640625e-05s
Believability | Calculation of trust value for statusnet-lydiastench-com took 5.9604644775390625e-06s
INFO | --- Analysis for statusnet-lydiastench-com took 2.3923487663269043s
Availability | SPARQL endpoint availability check for statusnet-m-kuttner-com took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-m-kuttner-com took 0.0005984306335449219s
Completeness | Calculation of interlinking completeness for statusnet-m-kuttner-com took 0.28337907791137695s
Reputation | Calculation of the PageRank for statusnet-m-kuttner-com took 0.0203702449798584s
Interlinking | Calculation of Degree of Connection for statusnet-m-kuttner-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-m-kuttner-com took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for statusnet-m-kuttner-com took 5.1975250244140625e-05s
Believability | Calculation of trust value for statusnet-m-kuttner-com took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-m-kuttner-com took 3.4391863346099854s
Availability | SPARQL endpoint availability check for statusnet-macno-org took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-macno-org took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for statusnet-macno-org took 0.26933908462524414s
Reputation | Calculation of the PageRank for statusnet-macno-org took 0.02136063575744629s
Interlinking | Calculation of Degree of Connection for statusnet-macno-org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-macno-org took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for statusnet-macno-org took 0.00015306472778320312s
Believability | Calculation of trust value for statusnet-macno-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-macno-org took 2.4202449321746826s
Availability | SPARQL endpoint availability check for statusnet-mamalibre-com-ar took 4.458427429199219e-05s
Availability | VoID file availability check for statusnet-mamalibre-com-ar took 0.0005888938903808594s
Completeness | Calculation of interlinking completeness for statusnet-mamalibre-com-ar took 0.25520801544189453s
Reputation | Calculation of the PageRank for statusnet-mamalibre-com-ar took 0.020458221435546875s
Interlinking | Calculation of Degree of Connection for statusnet-mamalibre-com-ar took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-mamalibre-com-ar took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for statusnet-mamalibre-com-ar took 6.29425048828125e-05s
Believability | Calculation of trust value for statusnet-mamalibre-com-ar took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-mamalibre-com-ar took 3.286787509918213s
Availability | SPARQL endpoint availability check for statusnet-maymay-net took 4.601478576660156e-05s
Availability | VoID file availability check for statusnet-maymay-net took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for statusnet-maymay-net took 0.2538259029388428s
Reputation | Calculation of the PageRank for statusnet-maymay-net took 0.02157735824584961s
Interlinking | Calculation of Degree of Connection for statusnet-maymay-net took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for statusnet-maymay-net took 0.0007946491241455078s
Interlinking | Calculation of Clustering coefficient for statusnet-maymay-net took 8.392333984375e-05s
Believability | Calculation of trust value for statusnet-maymay-net took 5.7220458984375e-06s
INFO | --- Analysis for statusnet-maymay-net took 41.878740549087524s
Availability | SPARQL endpoint availability check for statusnet-morphtown-de took 4.673004150390625e-05s
Availability | VoID file availability check for statusnet-morphtown-de took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for statusnet-morphtown-de took 0.2774393558502197s
Reputation | Calculation of the PageRank for statusnet-morphtown-de took 0.02085280418395996s
Interlinking | Calculation of Degree of Connection for statusnet-morphtown-de took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-morphtown-de took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for statusnet-morphtown-de took 0.0001628398895263672s
Believability | Calculation of trust value for statusnet-morphtown-de took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-morphtown-de took 2.4497547149658203s
Availability | SPARQL endpoint availability check for statusnet-mrblog-nl took 7.486343383789062e-05s
Availability | VoID file availability check for statusnet-mrblog-nl took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for statusnet-mrblog-nl took 0.25628113746643066s
Reputation | Calculation of the PageRank for statusnet-mrblog-nl took 0.02051258087158203s
Interlinking | Calculation of Degree of Connection for statusnet-mrblog-nl took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-mrblog-nl took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for statusnet-mrblog-nl took 9.655952453613281e-05s
Believability | Calculation of trust value for statusnet-mrblog-nl took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-mrblog-nl took 2.4856903553009033s
Availability | SPARQL endpoint availability check for statusnet-mulestable-net took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-mulestable-net took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for statusnet-mulestable-net took 0.28165245056152344s
Reputation | Calculation of the PageRank for statusnet-mulestable-net took 0.020542621612548828s
Interlinking | Calculation of Degree of Connection for statusnet-mulestable-net took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-mulestable-net took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for statusnet-mulestable-net took 5.435943603515625e-05s
Believability | Calculation of trust value for statusnet-mulestable-net took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-mulestable-net took 2.4300825595855713s
Availability | SPARQL endpoint availability check for statusnet-my-status-tk took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-my-status-tk took 0.0005345344543457031s
Completeness | Calculation of interlinking completeness for statusnet-my-status-tk took 0.2585582733154297s
Reputation | Calculation of the PageRank for statusnet-my-status-tk took 0.020382165908813477s
Interlinking | Calculation of Degree of Connection for statusnet-my-status-tk took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-my-status-tk took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for statusnet-my-status-tk took 5.125999450683594e-05s
Believability | Calculation of trust value for statusnet-my-status-tk took 5.7220458984375e-06s
INFO | --- Analysis for statusnet-my-status-tk took 2.580141067504883s
Availability | SPARQL endpoint availability check for statusnet-opensim-chat-eu took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-opensim-chat-eu took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for statusnet-opensim-chat-eu took 0.24976468086242676s
Reputation | Calculation of the PageRank for statusnet-opensim-chat-eu took 0.020630836486816406s
Interlinking | Calculation of Degree of Connection for statusnet-opensim-chat-eu took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-opensim-chat-eu took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for statusnet-opensim-chat-eu took 0.00010943412780761719s
Believability | Calculation of trust value for statusnet-opensim-chat-eu took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-opensim-chat-eu took 2.4060471057891846s
Availability | SPARQL endpoint availability check for statusnet-orangeseeds-org took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-orangeseeds-org took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for statusnet-orangeseeds-org took 0.26046252250671387s
Reputation | Calculation of the PageRank for statusnet-orangeseeds-org took 0.02050948143005371s
Interlinking | Calculation of Degree of Connection for statusnet-orangeseeds-org took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-orangeseeds-org took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for statusnet-orangeseeds-org took 5.7220458984375e-05s
Believability | Calculation of trust value for statusnet-orangeseeds-org took 5.7220458984375e-06s
INFO | --- Analysis for statusnet-orangeseeds-org took 2.5339202880859375s
Availability | SPARQL endpoint availability check for statusnet-otbm-fr took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-otbm-fr took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for statusnet-otbm-fr took 0.27609753608703613s
Reputation | Calculation of the PageRank for statusnet-otbm-fr took 0.020376920700073242s
Interlinking | Calculation of Degree of Connection for statusnet-otbm-fr took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-otbm-fr took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for statusnet-otbm-fr took 6.341934204101562e-05s
Believability | Calculation of trust value for statusnet-otbm-fr took 5.9604644775390625e-06s
INFO | --- Analysis for statusnet-otbm-fr took 2.5249998569488525s
Availability | SPARQL endpoint availability check for statusnet-ourcoffs-org-au took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-ourcoffs-org-au took 0.0005896091461181641s
Completeness | Calculation of interlinking completeness for statusnet-ourcoffs-org-au took 0.28467822074890137s
Reputation | Calculation of the PageRank for statusnet-ourcoffs-org-au took 0.02075052261352539s
Interlinking | Calculation of Degree of Connection for statusnet-ourcoffs-org-au took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-ourcoffs-org-au took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for statusnet-ourcoffs-org-au took 8.726119995117188e-05s
Believability | Calculation of trust value for statusnet-ourcoffs-org-au took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-ourcoffs-org-au took 2.93498158454895s
Availability | SPARQL endpoint availability check for statusnet-panda-id-au took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-panda-id-au took 0.0006210803985595703s
Completeness | Calculation of interlinking completeness for statusnet-panda-id-au took 0.2823145389556885s
Reputation | Calculation of the PageRank for statusnet-panda-id-au took 0.020520687103271484s
Interlinking | Calculation of Degree of Connection for statusnet-panda-id-au took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-panda-id-au took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for statusnet-panda-id-au took 4.9591064453125e-05s
Believability | Calculation of trust value for statusnet-panda-id-au took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-panda-id-au took 4.548739910125732s
Availability | SPARQL endpoint availability check for statusnet-piana-eu took 5.817413330078125e-05s
Availability | VoID file availability check for statusnet-piana-eu took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for statusnet-piana-eu took 0.2557811737060547s
Reputation | Calculation of the PageRank for statusnet-piana-eu took 0.0209200382232666s
Interlinking | Calculation of Degree of Connection for statusnet-piana-eu took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-piana-eu took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for statusnet-piana-eu took 9.393692016601562e-05s
Believability | Calculation of trust value for statusnet-piana-eu took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-piana-eu took 2.4209582805633545s
Availability | SPARQL endpoint availability check for statusnet-planet-libre-org took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-planet-libre-org took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for statusnet-planet-libre-org took 0.27331089973449707s
Reputation | Calculation of the PageRank for statusnet-planet-libre-org took 0.020647764205932617s
Interlinking | Calculation of Degree of Connection for statusnet-planet-libre-org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-planet-libre-org took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for statusnet-planet-libre-org took 7.677078247070312e-05s
Believability | Calculation of trust value for statusnet-planet-libre-org took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-planet-libre-org took 2.441157579421997s
Availability | SPARQL endpoint availability check for statusnet-postblue-info took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-postblue-info took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for statusnet-postblue-info took 0.24292850494384766s
Reputation | Calculation of the PageRank for statusnet-postblue-info took 0.020402193069458008s
Interlinking | Calculation of Degree of Connection for statusnet-postblue-info took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-postblue-info took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for statusnet-postblue-info took 0.00023031234741210938s
Believability | Calculation of trust value for statusnet-postblue-info took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-postblue-info took 2.405972957611084s
Availability | SPARQL endpoint availability check for statusnet-progval-net took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-progval-net took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for statusnet-progval-net took 0.25833630561828613s
Reputation | Calculation of the PageRank for statusnet-progval-net took 0.02064990997314453s
Interlinking | Calculation of Degree of Connection for statusnet-progval-net took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-progval-net took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for statusnet-progval-net took 7.534027099609375e-05s
Believability | Calculation of trust value for statusnet-progval-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-progval-net took 2.470842123031616s
Availability | SPARQL endpoint availability check for statusnet-qdnx-org took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-qdnx-org took 0.0005819797515869141s
Completeness | Calculation of interlinking completeness for statusnet-qdnx-org took 0.28845739364624023s
Reputation | Calculation of the PageRank for statusnet-qdnx-org took 0.0203402042388916s
Interlinking | Calculation of Degree of Connection for statusnet-qdnx-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-qdnx-org took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for statusnet-qdnx-org took 0.0001125335693359375s
Believability | Calculation of trust value for statusnet-qdnx-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-qdnx-org took 2.745952844619751s
Availability | SPARQL endpoint availability check for statusnet-qth-fr took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-qth-fr took 0.0005571842193603516s
Completeness | Calculation of interlinking completeness for statusnet-qth-fr took 0.2523319721221924s
Reputation | Calculation of the PageRank for statusnet-qth-fr took 0.020398616790771484s
Interlinking | Calculation of Degree of Connection for statusnet-qth-fr took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-qth-fr took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for statusnet-qth-fr took 5.8650970458984375e-05s
Believability | Calculation of trust value for statusnet-qth-fr took 5.245208740234375e-06s
INFO | --- Analysis for statusnet-qth-fr took 3.2138872146606445s
Availability | SPARQL endpoint availability check for statusnet-quitter-se took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-quitter-se took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for statusnet-quitter-se took 0.2597012519836426s
Reputation | Calculation of the PageRank for statusnet-quitter-se took 0.020151376724243164s
Interlinking | Calculation of Degree of Connection for statusnet-quitter-se took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-quitter-se took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for statusnet-quitter-se took 0.00021696090698242188s
Believability | Calculation of trust value for statusnet-quitter-se took 5.9604644775390625e-06s
INFO | --- Analysis for statusnet-quitter-se took 2.5728588104248047s
Availability | SPARQL endpoint availability check for statusnet-rainbowdash-net took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-rainbowdash-net took 0.00048089027404785156s
Completeness | Calculation of interlinking completeness for statusnet-rainbowdash-net took 0.25794529914855957s
Reputation | Calculation of the PageRank for statusnet-rainbowdash-net took 0.0203244686126709s
Interlinking | Calculation of Degree of Connection for statusnet-rainbowdash-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-rainbowdash-net took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for statusnet-rainbowdash-net took 9.965896606445312e-05s
Believability | Calculation of trust value for statusnet-rainbowdash-net took 5.9604644775390625e-06s
INFO | --- Analysis for statusnet-rainbowdash-net took 2.5976061820983887s
Availability | SPARQL endpoint availability check for statusnet-recit-org took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-recit-org took 0.0005984306335449219s
Completeness | Calculation of interlinking completeness for statusnet-recit-org took 0.27434706687927246s
Reputation | Calculation of the PageRank for statusnet-recit-org took 0.02034735679626465s
Interlinking | Calculation of Degree of Connection for statusnet-recit-org took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-recit-org took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for statusnet-recit-org took 5.3882598876953125e-05s
Believability | Calculation of trust value for statusnet-recit-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-recit-org took 4.454114198684692s
Availability | SPARQL endpoint availability check for statusnet-russwurm-org took 5.5789947509765625e-05s
Availability | VoID file availability check for statusnet-russwurm-org took 0.0006399154663085938s
Completeness | Calculation of interlinking completeness for statusnet-russwurm-org took 0.28385019302368164s
Reputation | Calculation of the PageRank for statusnet-russwurm-org took 0.020120620727539062s
Interlinking | Calculation of Degree of Connection for statusnet-russwurm-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-russwurm-org took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for statusnet-russwurm-org took 0.00014901161193847656s
Believability | Calculation of trust value for statusnet-russwurm-org took 5.9604644775390625e-06s
INFO | --- Analysis for statusnet-russwurm-org took 12.723239421844482s
Availability | SPARQL endpoint availability check for statusnet-samnoble-org took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-samnoble-org took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for statusnet-samnoble-org took 0.28119325637817383s
Reputation | Calculation of the PageRank for statusnet-samnoble-org took 0.020252704620361328s
Interlinking | Calculation of Degree of Connection for statusnet-samnoble-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-samnoble-org took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for statusnet-samnoble-org took 8.58306884765625e-05s
Believability | Calculation of trust value for statusnet-samnoble-org took 5.0067901611328125e-06s
INFO | --- Analysis for statusnet-samnoble-org took 4.756270170211792s
Availability | SPARQL endpoint availability check for statusnet-schiessle-org took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-schiessle-org took 0.0004515647888183594s
Completeness | Calculation of interlinking completeness for statusnet-schiessle-org took 0.26714205741882324s
Reputation | Calculation of the PageRank for statusnet-schiessle-org took 0.020351171493530273s
Interlinking | Calculation of Degree of Connection for statusnet-schiessle-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-schiessle-org took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for statusnet-schiessle-org took 7.796287536621094e-05s
Believability | Calculation of trust value for statusnet-schiessle-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-schiessle-org took 2.5178961753845215s
Availability | SPARQL endpoint availability check for statusnet-scoffoni-net took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-scoffoni-net took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for statusnet-scoffoni-net took 0.26853084564208984s
Reputation | Calculation of the PageRank for statusnet-scoffoni-net took 0.02015376091003418s
Interlinking | Calculation of Degree of Connection for statusnet-scoffoni-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-scoffoni-net took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for statusnet-scoffoni-net took 9.417533874511719e-05s
Believability | Calculation of trust value for statusnet-scoffoni-net took 5.9604644775390625e-06s
INFO | --- Analysis for statusnet-scoffoni-net took 2.4688408374786377s
Availability | SPARQL endpoint availability check for statusnet-sebseb01-net took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-sebseb01-net took 0.0004532337188720703s
Completeness | Calculation of interlinking completeness for statusnet-sebseb01-net took 0.268007755279541s
Reputation | Calculation of the PageRank for statusnet-sebseb01-net took 0.020604372024536133s
Interlinking | Calculation of Degree of Connection for statusnet-sebseb01-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-sebseb01-net took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for statusnet-sebseb01-net took 6.079673767089844e-05s
Believability | Calculation of trust value for statusnet-sebseb01-net took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-sebseb01-net took 2.508234977722168s
Availability | SPARQL endpoint availability check for statusnet-shnoulle-net took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-shnoulle-net took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for statusnet-shnoulle-net took 0.2737431526184082s
Reputation | Calculation of the PageRank for statusnet-shnoulle-net took 0.020241498947143555s
Interlinking | Calculation of Degree of Connection for statusnet-shnoulle-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-shnoulle-net took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for statusnet-shnoulle-net took 7.224082946777344e-05s
Believability | Calculation of trust value for statusnet-shnoulle-net took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-shnoulle-net took 3.1234514713287354s
Availability | SPARQL endpoint availability check for statusnet-skilledtests-com took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-skilledtests-com took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for statusnet-skilledtests-com took 0.2747337818145752s
Reputation | Calculation of the PageRank for statusnet-skilledtests-com took 0.02016615867614746s
Interlinking | Calculation of Degree of Connection for statusnet-skilledtests-com took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-skilledtests-com took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for statusnet-skilledtests-com took 0.00023698806762695312s
Believability | Calculation of trust value for statusnet-skilledtests-com took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-skilledtests-com took 2.7329518795013428s
Availability | SPARQL endpoint availability check for statusnet-somsants-net took 4.553794860839844e-05s
Availability | VoID file availability check for statusnet-somsants-net took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for statusnet-somsants-net took 0.2599153518676758s
Reputation | Calculation of the PageRank for statusnet-somsants-net took 0.020331621170043945s
Interlinking | Calculation of Degree of Connection for statusnet-somsants-net took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-somsants-net took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for statusnet-somsants-net took 0.00010442733764648438s
Believability | Calculation of trust value for statusnet-somsants-net took 5.9604644775390625e-06s
INFO | --- Analysis for statusnet-somsants-net took 2.433806896209717s
Availability | SPARQL endpoint availability check for statusnet-soucy-cc took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-soucy-cc took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for statusnet-soucy-cc took 0.26393699645996094s
Reputation | Calculation of the PageRank for statusnet-soucy-cc took 0.020436763763427734s
Interlinking | Calculation of Degree of Connection for statusnet-soucy-cc took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-soucy-cc took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for statusnet-soucy-cc took 0.0001354217529296875s
Believability | Calculation of trust value for statusnet-soucy-cc took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-soucy-cc took 2.4328417778015137s
Availability | SPARQL endpoint availability check for statusnet-spip-org took 5.626678466796875e-05s
Availability | VoID file availability check for statusnet-spip-org took 0.0005726814270019531s
Completeness | Calculation of interlinking completeness for statusnet-spip-org took 0.26259350776672363s
Reputation | Calculation of the PageRank for statusnet-spip-org took 0.020316362380981445s
Interlinking | Calculation of Degree of Connection for statusnet-spip-org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-spip-org took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for statusnet-spip-org took 6.031990051269531e-05s
Believability | Calculation of trust value for statusnet-spip-org took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-spip-org took 3.385148525238037s
Availability | SPARQL endpoint availability check for statusnet-spraci-org took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-spraci-org took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for statusnet-spraci-org took 0.2765462398529053s
Reputation | Calculation of the PageRank for statusnet-spraci-org took 0.020344972610473633s
Interlinking | Calculation of Degree of Connection for statusnet-spraci-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-spraci-org took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for statusnet-spraci-org took 6.222724914550781e-05s
Believability | Calculation of trust value for statusnet-spraci-org took 5.245208740234375e-06s
INFO | --- Analysis for statusnet-spraci-org took 2.3880271911621094s
Availability | SPARQL endpoint availability check for statusnet-ssweeny-net took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-ssweeny-net took 0.0005869865417480469s
Completeness | Calculation of interlinking completeness for statusnet-ssweeny-net took 0.2881937026977539s
Reputation | Calculation of the PageRank for statusnet-ssweeny-net took 0.020134687423706055s
Interlinking | Calculation of Degree of Connection for statusnet-ssweeny-net took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-ssweeny-net took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for statusnet-ssweeny-net took 0.0001068115234375s
Believability | Calculation of trust value for statusnet-ssweeny-net took 5.7220458984375e-06s
INFO | --- Analysis for statusnet-ssweeny-net took 4.752769708633423s
Availability | SPARQL endpoint availability check for statusnet-status-net took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-status-net took 0.0005445480346679688s
Completeness | Calculation of interlinking completeness for statusnet-status-net took 0.26097631454467773s
Reputation | Calculation of the PageRank for statusnet-status-net took 0.020214557647705078s
Interlinking | Calculation of Degree of Connection for statusnet-status-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-status-net took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for statusnet-status-net took 0.00022363662719726562s
Believability | Calculation of trust value for statusnet-status-net took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-status-net took 3.6378066539764404s
Availability | SPARQL endpoint availability check for statusnet-sweetiebelle-net took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-sweetiebelle-net took 0.0004715919494628906s
Completeness | Calculation of interlinking completeness for statusnet-sweetiebelle-net took 0.28844594955444336s
Reputation | Calculation of the PageRank for statusnet-sweetiebelle-net took 0.02042531967163086s
Interlinking | Calculation of Degree of Connection for statusnet-sweetiebelle-net took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-sweetiebelle-net took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for statusnet-sweetiebelle-net took 5.412101745605469e-05s
Believability | Calculation of trust value for statusnet-sweetiebelle-net took 5.9604644775390625e-06s
INFO | --- Analysis for statusnet-sweetiebelle-net took 2.431483745574951s
Availability | SPARQL endpoint availability check for statusnet-tekk-com-ar took 4.076957702636719e-05s
Availability | VoID file availability check for statusnet-tekk-com-ar took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for statusnet-tekk-com-ar took 0.24763059616088867s
Reputation | Calculation of the PageRank for statusnet-tekk-com-ar took 0.020316600799560547s
Interlinking | Calculation of Degree of Connection for statusnet-tekk-com-ar took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-tekk-com-ar took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for statusnet-tekk-com-ar took 9.226799011230469e-05s
Believability | Calculation of trust value for statusnet-tekk-com-ar took 9.298324584960938e-06s
INFO | --- Analysis for statusnet-tekk-com-ar took 2.4524428844451904s
Availability | SPARQL endpoint availability check for statusnet-thelovebug-org took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-thelovebug-org took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for statusnet-thelovebug-org took 0.25264811515808105s
Reputation | Calculation of the PageRank for statusnet-thelovebug-org took 0.020198822021484375s
Interlinking | Calculation of Degree of Connection for statusnet-thelovebug-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-thelovebug-org took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for statusnet-thelovebug-org took 0.0001246929168701172s
Believability | Calculation of trust value for statusnet-thelovebug-org took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-thelovebug-org took 2.4032201766967773s
Availability | SPARQL endpoint availability check for statusnet-thornton2-com took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-thornton2-com took 0.0005459785461425781s
Completeness | Calculation of interlinking completeness for statusnet-thornton2-com took 0.2884347438812256s
Reputation | Calculation of the PageRank for statusnet-thornton2-com took 0.020253658294677734s
Interlinking | Calculation of Degree of Connection for statusnet-thornton2-com took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-thornton2-com took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for statusnet-thornton2-com took 7.176399230957031e-05s
Believability | Calculation of trust value for statusnet-thornton2-com took 5.7220458984375e-06s
INFO | --- Analysis for statusnet-thornton2-com took 5.45470118522644s
Availability | SPARQL endpoint availability check for statusnet-timttmy-co-uk took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-timttmy-co-uk took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for statusnet-timttmy-co-uk took 0.2583186626434326s
Reputation | Calculation of the PageRank for statusnet-timttmy-co-uk took 0.02019810676574707s
Interlinking | Calculation of Degree of Connection for statusnet-timttmy-co-uk took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-timttmy-co-uk took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for statusnet-timttmy-co-uk took 0.00010609626770019531s
Believability | Calculation of trust value for statusnet-timttmy-co-uk took 5.7220458984375e-06s
INFO | --- Analysis for statusnet-timttmy-co-uk took 2.7191922664642334s
Availability | SPARQL endpoint availability check for statusnet-tl1n-com took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-tl1n-com took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for statusnet-tl1n-com took 0.2757737636566162s
Reputation | Calculation of the PageRank for statusnet-tl1n-com took 0.02010321617126465s
Interlinking | Calculation of Degree of Connection for statusnet-tl1n-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-tl1n-com took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for statusnet-tl1n-com took 3.7670135498046875e-05s
Believability | Calculation of trust value for statusnet-tl1n-com took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-tl1n-com took 3.5100631713867188s
Availability | SPARQL endpoint availability check for statusnet-tschlotfeldt-de took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-tschlotfeldt-de took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for statusnet-tschlotfeldt-de took 0.26043081283569336s
Reputation | Calculation of the PageRank for statusnet-tschlotfeldt-de took 0.020380258560180664s
Interlinking | Calculation of Degree of Connection for statusnet-tschlotfeldt-de took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-tschlotfeldt-de took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for statusnet-tschlotfeldt-de took 6.628036499023438e-05s
Believability | Calculation of trust value for statusnet-tschlotfeldt-de took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-tschlotfeldt-de took 2.553917407989502s
Availability | SPARQL endpoint availability check for statusnet-uni-siegen-de took 4.0531158447265625e-05s
Availability | VoID file availability check for statusnet-uni-siegen-de took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for statusnet-uni-siegen-de took 0.267183780670166s
Reputation | Calculation of the PageRank for statusnet-uni-siegen-de took 0.020200252532958984s
Interlinking | Calculation of Degree of Connection for statusnet-uni-siegen-de took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-uni-siegen-de took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for statusnet-uni-siegen-de took 3.62396240234375e-05s
Believability | Calculation of trust value for statusnet-uni-siegen-de took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-uni-siegen-de took 2.6322011947631836s
Availability | SPARQL endpoint availability check for Super Terminology System(STEAK) - Linked Open Data took 4.2438507080078125e-05s
Availability | VoID file availability check for Super Terminology System(STEAK) - Linked Open Data took 0.0007088184356689453s
Completeness | Calculation of interlinking completeness for Super Terminology System(STEAK) - Linked Open Data took 0.26866817474365234s
Reputation | Calculation of the PageRank for Super Terminology System(STEAK) - Linked Open Data took 0.020340919494628906s
Interlinking | Calculation of Degree of Connection for Super Terminology System(STEAK) - Linked Open Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Super Terminology System(STEAK) - Linked Open Data took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Super Terminology System(STEAK) - Linked Open Data took 3.075599670410156e-05s
Believability | Calculation of trust value for Super Terminology System(STEAK) - Linked Open Data took 5.4836273193359375e-06s
INFO | --- Analysis for steak took 2.9690122604370117s
Availability | SPARQL endpoint availability check for RAMEAU subject headings (STITCH) took 4.1961669921875e-05s
Availability | VoID file availability check for RAMEAU subject headings (STITCH) took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for RAMEAU subject headings (STITCH) took 0.27924537658691406s
Reputation | Calculation of the PageRank for RAMEAU subject headings (STITCH) took 0.020217180252075195s
Interlinking | Calculation of Degree of Connection for RAMEAU subject headings (STITCH) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for RAMEAU subject headings (STITCH) took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for RAMEAU subject headings (STITCH) took 7.43865966796875e-05s
Believability | Calculation of trust value for RAMEAU subject headings (STITCH) took 5.245208740234375e-06s
INFO | --- Analysis for stitch-rameau took 3.966115951538086s
Availability | SPARQL endpoint availability check for Stone Tech Square took 0.5715856552124023s
Availability | VoID file availability check for Stone Tech Square took 0.0007500648498535156s
Completeness | Calculation of interlinking completeness for Stone Tech Square took 0.25917506217956543s
Reputation | Calculation of the PageRank for Stone Tech Square took 0.020664215087890625s
Interlinking | Calculation of Degree of Connection for Stone Tech Square took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for Stone Tech Square took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for Stone Tech Square took 1.2636184692382812e-05s
Believability | Calculation of trust value for Stone Tech Square took 7.152557373046875e-06s
INFO | --- Analysis for stone-tech-square-data took 4.446065664291382s
Availability | SPARQL endpoint availability check for Strukturované popisy z FDA took 4.315376281738281e-05s
Availability | VoID file availability check for Strukturované popisy z FDA took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for Strukturované popisy z FDA took 0.2678658962249756s
Reputation | Calculation of the PageRank for Strukturované popisy z FDA took 0.020259857177734375s
Interlinking | Calculation of Degree of Connection for Strukturované popisy z FDA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Strukturované popisy z FDA took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Strukturované popisy z FDA took 2.8133392333984375e-05s
Believability | Calculation of trust value for Strukturované popisy z FDA took 5.7220458984375e-06s
INFO | --- Analysis for strukturovan--popisy-z-fda took 2.9344680309295654s
Availability | SPARQL endpoint availability check for STW Thesaurus for Economics took 0.5448009967803955s
Availability | VoID file availability check for STW Thesaurus for Economics took 0.0006585121154785156s
Extra | Recovery of all triples for STW Thesaurus for Economics took 96.7222101688385s
Performance | Total latancy measurement for STW Thesaurus for Economics took 1.3882825374603271s
Amount of data | Number of triples check for STW Thesaurus for Economics took 0.6794254779815674s
Interoperability | New terms check for STW Thesaurus for Economics took 1.4254887104034424s
Versatility | Languages check for STW Thesaurus for Economics took 1.4955618381500244s
Interpretability | Number of blank nodes check for STW Thesaurus for Economics took 0.5794146060943604s
Security | Check HTTPS for STW Thesaurus for Economics took 0.1358199119567871s
Interpretability | RDF structures check for STW Thesaurus for Economics took 0.2626631259918213s
Versatility | Serialization formats check for STW Thesaurus for Economics took 0.2631690502166748s
Availability | RDF dump link check for STW Thesaurus for Economics took 0.24304604530334473s
License | MR license check for STW Thesaurus for Economics took 0.2385563850402832s
License | HR license check for STW Thesaurus for Economics took 2.54960298538208s
Amount of data | Number of property check for STW Thesaurus for Economics took 0.2283787727355957s
Understandability | Number of label check for STW Thesaurus for Economics took 0.6339890956878662s
Understandability | URI regex check for STW Thesaurus for Economics took 0.517228364944458s
Understandability | Vocabs check for STW Thesaurus for Economics took 0.23381471633911133s
Verifiability | Authors check for STW Thesaurus for Economics took 0.24907803535461426s
Verifiability | Publishers check for STW Thesaurus for Economics took 0.23939013481140137s
Performance | Throughput check for STW Thesaurus for Economics took 10.906722784042358s
Amount of data | Check the number of entities for STW Thesaurus for Economics took 0.7397043704986572s
Verifiability | Contribs. check for STW Thesaurus for Economics took 0.2693521976470947s
Interlinking | sameAs chians check for STW Thesaurus for Economics took 0.25459814071655273s
Interlinking | skos check for STW Thesaurus for Economics took 0.35605645179748535s
Interlinking | skos check for STW Thesaurus for Economics took 0.32274913787841797s
Timeliness | dataset update frequency check for STW Thesaurus for Economics took 0.25052738189697266s
Currency | Creation date check for STW Thesaurus for Economics took 0.5225496292114258s
Currency | Modification date check for STW Thesaurus for Economics took 0.5531435012817383s
Rep.Conc. | URIs length for STW Thesaurus for Economics took 7.273451089859009s
Consistency | Deprecated classes/propertiers check for STW Thesaurus for Economics took 0.2509896755218506s
Accuracy | Check Functional Property for STW Thesaurus for Economics took 0.260073184967041s
Accuracy | Check Inverse Functional Property for STW Thesaurus for Economics took 0.24100112915039062s
Accuracy | Check Empty annotation labels for STW Thesaurus for Economics took 22.154403686523438s
Accuracy | Check White space in annotation for STW Thesaurus for Economics took 1.0786941051483154s
Accuracy | Check Datatype consistency for STW Thesaurus for Economics took 2.4554338455200195s
Consistency | Disjoint class check for STW Thesaurus for Economics took 0.28246641159057617s
Consistency | Check Misplaced properties for STW Thesaurus for Economics took 1.2959423065185547s
Consistency | Check Ontology hijacking for STW Thesaurus for Economics took 2.475001811981201s
Consistency | Check Invalid usage of undefined classes for STW Thesaurus for Economics took 1.194730520248413s
Consistency | Check Invalid usage of undefined properties for STW Thesaurus for Economics took 2.283782958984375s
Conciseness | Check Extensional conciseness for STW Thesaurus for Economics took 1.6549172401428223s
Conciseness | Check Intensional conciseness for STW Thesaurus for Economics took 0.2655830383300781s
Security | Sign check for STW Thesaurus for Economics took 0.2715151309967041s
Availability | Check URIs Dereferenciability for STW Thesaurus for Economics took 4976.400598287582s
Completeness | Calculation of interlinking completeness for STW Thesaurus for Economics took 1.5680530071258545s
Reputation | Calculation of the PageRank for STW Thesaurus for Economics took 0.02158975601196289s
Interlinking | Calculation of Degree of Connection for STW Thesaurus for Economics took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for STW Thesaurus for Economics took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for STW Thesaurus for Economics took 0.0001246929168701172s
Believability | Calculation of trust value for STW Thesaurus for Economics took 6.67572021484375e-06s
INFO | --- Analysis for stw-thesaurus-for-economics took 5187.1871020793915s
Availability | SPARQL endpoint availability check for SudershanTech took 4.1961669921875e-05s
Availability | VoID file availability check for SudershanTech took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for SudershanTech took 0.2634694576263428s
Reputation | Calculation of the PageRank for SudershanTech took 0.0201723575592041s
Interlinking | Calculation of Degree of Connection for SudershanTech took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SudershanTech took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for SudershanTech took 2.9802322387695312e-05s
Believability | Calculation of trust value for SudershanTech took 6.67572021484375e-06s
INFO | --- Analysis for SudershanTech took 3.2379114627838135s
Availability | SPARQL endpoint availability check for Sudoc bibliographic data took 0.6089918613433838s
Availability | VoID file availability check for Sudoc bibliographic data took 0.0006284713745117188s
Completeness | Calculation of interlinking completeness for Sudoc bibliographic data took 0.7137393951416016s
Reputation | Calculation of the PageRank for Sudoc bibliographic data took 0.020369529724121094s
Interlinking | Calculation of Degree of Connection for Sudoc bibliographic data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Sudoc bibliographic data took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Sudoc bibliographic data took 4.649162292480469e-05s
Believability | Calculation of trust value for Sudoc bibliographic data took 7.152557373046875e-06s
INFO | --- Analysis for sudocfr took 9.900704622268677s
Availability | SPARQL endpoint availability check for Suface Forestière Mondiale 1990-2016 took 0.9895269870758057s
Availability | VoID file availability check for Suface Forestière Mondiale 1990-2016 took 0.0005960464477539062s
Extra | Recovery of all triples for Suface Forestière Mondiale 1990-2016 took 28.920832633972168s
Performance | Total latancy measurement for Suface Forestière Mondiale 1990-2016 took 2.6176023483276367s
Amount of data | Number of triples check for Suface Forestière Mondiale 1990-2016 took 1.5481586456298828s
Interoperability | New terms check for Suface Forestière Mondiale 1990-2016 took 2.6947362422943115s
Versatility | Languages check for Suface Forestière Mondiale 1990-2016 took 3.27360200881958s
Interpretability | Number of blank nodes check for Suface Forestière Mondiale 1990-2016 took 1.5507032871246338s
Interpretability | RDF structures check for Suface Forestière Mondiale 1990-2016 took 0.5192489624023438s
Versatility | Serialization formats check for Suface Forestière Mondiale 1990-2016 took 0.5476157665252686s
Availability | RDF dump link check for Suface Forestière Mondiale 1990-2016 took 0.5441994667053223s
License | MR license check for Suface Forestière Mondiale 1990-2016 took 0.5416154861450195s
License | HR license check for Suface Forestière Mondiale 1990-2016 took 7.593942403793335s
Amount of data | Number of property check for Suface Forestière Mondiale 1990-2016 took 0.566129207611084s
Understandability | Number of label check for Suface Forestière Mondiale 1990-2016 took 0.694627046585083s
Understandability | URI regex check for Suface Forestière Mondiale 1990-2016 took 1.1521399021148682s
Understandability | Vocabs check for Suface Forestière Mondiale 1990-2016 took 0.5139245986938477s
Verifiability | Authors check for Suface Forestière Mondiale 1990-2016 took 0.5337109565734863s
Verifiability | Publishers check for Suface Forestière Mondiale 1990-2016 took 0.5416073799133301s
Performance | Throughput check for Suface Forestière Mondiale 1990-2016 took 10.769393920898438s
Amount of data | Check the number of entities for Suface Forestière Mondiale 1990-2016 took 7.319450378417969e-05s
Verifiability | Contribs. check for Suface Forestière Mondiale 1990-2016 took 0.5801253318786621s
Interlinking | sameAs chians check for Suface Forestière Mondiale 1990-2016 took 0.5642554759979248s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.6478471755981445s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.5968797206878662s
Timeliness | dataset update frequency check for Suface Forestière Mondiale 1990-2016 took 0.5539491176605225s
Currency | Creation date check for Suface Forestière Mondiale 1990-2016 took 1.1010725498199463s
Currency | Modification date check for Suface Forestière Mondiale 1990-2016 took 1.1100547313690186s
Rep.Conc. | URIs length for Suface Forestière Mondiale 1990-2016 took 22.468453645706177s
Interoperability | New vocabularies check for Suface Forestière Mondiale 1990-2016 took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for Suface Forestière Mondiale 1990-2016 took 0.5335714817047119s
Accuracy | Check Functional Property for Suface Forestière Mondiale 1990-2016 took 0.5057172775268555s
Accuracy | Check Inverse Functional Property for Suface Forestière Mondiale 1990-2016 took 0.5005431175231934s
Accuracy | Check Empty annotation labels for Suface Forestière Mondiale 1990-2016 took 2.829493761062622s
Accuracy | Check White space in annotation for Suface Forestière Mondiale 1990-2016 took 0.36519598960876465s
Consistency | Disjoint class check for Suface Forestière Mondiale 1990-2016 took 0.537189245223999s
Consistency | Check Misplaced properties for Suface Forestière Mondiale 1990-2016 took 11.375471591949463s
Consistency | Misplaced classes for Suface Forestière Mondiale 1990-2016 took 9.45496392250061s
Consistency | Check Ontology hijacking for Suface Forestière Mondiale 1990-2016 took 300.45800518989563s
Consistency | Check Invalid usage of undefined properties for Suface Forestière Mondiale 1990-2016 took 3.310556411743164s
Conciseness | Check Extensional conciseness for Suface Forestière Mondiale 1990-2016 took 2.9537887573242188s
Conciseness | Check Intensional conciseness for Suface Forestière Mondiale 1990-2016 took 1.9237890243530273s
Security | Sign check for Suface Forestière Mondiale 1990-2016 took 0.5758242607116699s
Availability | Check URIs Dereferenciability for Suface Forestière Mondiale 1990-2016 took 4603.390225172043s
Completeness | Calculation of interlinking completeness for Suface Forestière Mondiale 1990-2016 took 1.1166191101074219s
Reputation | Calculation of the PageRank for Suface Forestière Mondiale 1990-2016 took 0.022258520126342773s
Interlinking | Calculation of Degree of Connection for Suface Forestière Mondiale 1990-2016 took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Suface Forestière Mondiale 1990-2016 took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Suface Forestière Mondiale 1990-2016 took 0.0001571178436279297s
Interoperability | Check the re-using of existing vocabs for Suface Forestière Mondiale 1990-2016 took 1.9073486328125e-06s
Believability | Calculation of trust value for Suface Forestière Mondiale 1990-2016 took 8.58306884765625e-06s
INFO | --- Analysis for Suface_Forestière_Mondiale_1990-2016 took 9758.56661438942s
Availability | SPARQL endpoint availability check for Surge Radio took 4.673004150390625e-05s
Availability | VoID file availability check for Surge Radio took 0.0005035400390625s
Completeness | Calculation of interlinking completeness for Surge Radio took 0.7082569599151611s
Reputation | Calculation of the PageRank for Surge Radio took 0.02036118507385254s
Interlinking | Calculation of Degree of Connection for Surge Radio took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Surge Radio took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Surge Radio took 8.893013000488281e-05s
Believability | Calculation of trust value for Surge Radio took 6.4373016357421875e-06s
INFO | --- Analysis for surge-radio took 4.840924978256226s
Availability | SPARQL endpoint availability check for Soil & Water Assessment Tool took 4.124641418457031e-05s
Availability | VoID file availability check for Soil & Water Assessment Tool took 0.0003325939178466797s
Completeness | Calculation of interlinking completeness for Soil & Water Assessment Tool took 0.27789974212646484s
Reputation | Calculation of the PageRank for Soil & Water Assessment Tool took 0.020351171493530273s
Interlinking | Calculation of Degree of Connection for Soil & Water Assessment Tool took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Soil & Water Assessment Tool took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Soil & Water Assessment Tool took 2.8133392333984375e-05s
Believability | Calculation of trust value for Soil & Water Assessment Tool took 7.867813110351562e-06s
INFO | --- Analysis for SWAT took 25.70239520072937s
Availability | SPARQL endpoint availability check for Swedish Open Cultural Heritage took 4.076957702636719e-05s
Availability | VoID file availability check for Swedish Open Cultural Heritage took 0.4087653160095215s
Completeness | Calculation of interlinking completeness for Swedish Open Cultural Heritage took 0.697659969329834s
Reputation | Calculation of the PageRank for Swedish Open Cultural Heritage took 0.020078659057617188s
Interlinking | Calculation of Degree of Connection for Swedish Open Cultural Heritage took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Swedish Open Cultural Heritage took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Swedish Open Cultural Heritage took 6.651878356933594e-05s
Believability | Calculation of trust value for Swedish Open Cultural Heritage took 6.4373016357421875e-06s
INFO | --- Analysis for swedish-open-cultural-heritage took 6.84645676612854s
Availability | SPARQL endpoint availability check for SweFN-RDF took 1.0720202922821045s
Availability | VoID file availability check for SweFN-RDF took 0.00034427642822265625s
Completeness | Calculation of interlinking completeness for SweFN-RDF took 0.27712154388427734s
Reputation | Calculation of the PageRank for SweFN-RDF took 0.020496606826782227s
Interlinking | Calculation of Degree of Connection for SweFN-RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SweFN-RDF took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for SweFN-RDF took 3.24249267578125e-05s
Believability | Calculation of trust value for SweFN-RDF took 7.152557373046875e-06s
INFO | --- Analysis for swefn-rdf took 6.814306735992432s
Availability | SPARQL endpoint availability check for SwetoDblp took 0.00019741058349609375s
Availability | VoID file availability check for SwetoDblp took 0.0006043910980224609s
Completeness | Calculation of interlinking completeness for SwetoDblp took 0.2793593406677246s
Reputation | Calculation of the PageRank for SwetoDblp took 0.020271778106689453s
Interlinking | Calculation of Degree of Connection for SwetoDblp took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for SwetoDblp took 0.0008304119110107422s
Interlinking | Calculation of Clustering coefficient for SwetoDblp took 3.409385681152344e-05s
Believability | Calculation of trust value for SwetoDblp took 6.67572021484375e-06s
INFO | --- Analysis for sweto-dblp took 24.059801816940308s
Availability | SPARQL endpoint availability check for Swift Vocabulary took 5.637287855148315s
Availability | VoID file availability check for Swift Vocabulary took 0.0006067752838134766s
Completeness | Calculation of interlinking completeness for Swift Vocabulary took 0.28694677352905273s
Reputation | Calculation of the PageRank for Swift Vocabulary took 0.020122289657592773s
Interlinking | Calculation of Degree of Connection for Swift Vocabulary took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Swift Vocabulary took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Swift Vocabulary took 6.389617919921875e-05s
Believability | Calculation of trust value for Swift Vocabulary took 5.9604644775390625e-06s
INFO | --- Analysis for Swift took 10.314555644989014s
Availability | SPARQL endpoint availability check for SymbolicData took 3.933906555175781e-05s
Availability | VoID file availability check for SymbolicData took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for SymbolicData took 0.27690625190734863s
Reputation | Calculation of the PageRank for SymbolicData took 0.02023005485534668s
Interlinking | Calculation of Degree of Connection for SymbolicData took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SymbolicData took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for SymbolicData took 2.8371810913085938e-05s
Believability | Calculation of trust value for SymbolicData took 6.67572021484375e-06s
INFO | --- Analysis for symbolicdata took 3.418191432952881s
Availability | SPARQL endpoint availability check for Symptoms in Chinese took 4.124641418457031e-05s
Availability | VoID file availability check for Symptoms in Chinese took 0.001216888427734375s
Completeness | Calculation of interlinking completeness for Symptoms in Chinese took 0.26427149772644043s
Reputation | Calculation of the PageRank for Symptoms in Chinese took 0.020099639892578125s
Interlinking | Calculation of Degree of Connection for Symptoms in Chinese took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Symptoms in Chinese took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Symptoms in Chinese took 4.0531158447265625e-05s
Believability | Calculation of trust value for Symptoms in Chinese took 6.67572021484375e-06s
INFO | --- Analysis for symptoms-in-chinese took 53.59613084793091s
Availability | SPARQL endpoint availability check for National Digital Data Archive of Hungary (partial) took 0.5238785743713379s
Availability | VoID file availability check for National Digital Data Archive of Hungary (partial) took 0.0005941390991210938s
Extra | Recovery of all triples for National Digital Data Archive of Hungary (partial) took 0.5697777271270752s
Performance | Total latancy measurement for National Digital Data Archive of Hungary (partial) took 1.0139641761779785s
Amount of data | Number of triples check for National Digital Data Archive of Hungary (partial) took 51.889230489730835s
Interoperability | New terms check for National Digital Data Archive of Hungary (partial) took 19.09286642074585s
Versatility | Languages check for National Digital Data Archive of Hungary (partial) took 0.21931219100952148s
Interpretability | Number of blank nodes check for National Digital Data Archive of Hungary (partial) took 20.267160415649414s
Security | Check HTTPS for National Digital Data Archive of Hungary (partial) took 0.12499356269836426s
Interpretability | RDF structures check for National Digital Data Archive of Hungary (partial) took 0.6219096183776855s
Versatility | Serialization formats check for National Digital Data Archive of Hungary (partial) took 0.2898094654083252s
Availability | RDF dump link check for National Digital Data Archive of Hungary (partial) took 0.23303818702697754s
License | MR license check for National Digital Data Archive of Hungary (partial) took 0.4012417793273926s
License | HR license check for National Digital Data Archive of Hungary (partial) took 56.17238736152649s
Amount of data | Number of property check for National Digital Data Archive of Hungary (partial) took 0.6541824340820312s
Understandability | Number of label check for National Digital Data Archive of Hungary (partial) took 36.43224048614502s
Understandability | URI regex check for National Digital Data Archive of Hungary (partial) took 0.4390411376953125s
Understandability | Vocabs check for National Digital Data Archive of Hungary (partial) took 0.2577965259552002s
Verifiability | Authors check for National Digital Data Archive of Hungary (partial) took 0.21375489234924316s
Verifiability | Publishers check for National Digital Data Archive of Hungary (partial) took 0.21317505836486816s
Performance | Throughput check for National Digital Data Archive of Hungary (partial) took 13.220315217971802s
Amount of data | Check the number of entities for National Digital Data Archive of Hungary (partial) took 9.012222290039062e-05s
Verifiability | Contribs. check for National Digital Data Archive of Hungary (partial) took 1.7583115100860596s
Interlinking | sameAs chians check for National Digital Data Archive of Hungary (partial) took 1.8757038116455078s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.5166125297546387s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.5069780349731445s
Timeliness | dataset update frequency check for National Digital Data Archive of Hungary (partial) took 1.444035530090332s
Currency | Creation date check for National Digital Data Archive of Hungary (partial) took 0.4019763469696045s
Currency | Modification date check for National Digital Data Archive of Hungary (partial) took 1.7516822814941406s
Rep.Conc. | URIs length for National Digital Data Archive of Hungary (partial) took 66.71789717674255s
Interoperability | New vocabularies check for National Digital Data Archive of Hungary (partial) took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for National Digital Data Archive of Hungary (partial) took 0.22710847854614258s
Accuracy | Check Empty annotation labels for National Digital Data Archive of Hungary (partial) took 0.2792086601257324s
Accuracy | Check White space in annotation for National Digital Data Archive of Hungary (partial) took 0.0027129650115966797s
Accuracy | Check Datatype consistency for National Digital Data Archive of Hungary (partial) took 0.002808094024658203s
Consistency | Disjoint class check for National Digital Data Archive of Hungary (partial) took 0.19274425506591797s
Consistency | Check Misplaced properties for National Digital Data Archive of Hungary (partial) took 47.36105990409851s
Consistency | Misplaced classes for National Digital Data Archive of Hungary (partial) took 0.28888773918151855s
Consistency | Check Ontology hijacking for National Digital Data Archive of Hungary (partial) took 1.4219045639038086s
Consistency | Check Invalid usage of undefined classes for National Digital Data Archive of Hungary (partial) took 1.122666597366333s
Consistency | Check Invalid usage of undefined properties for National Digital Data Archive of Hungary (partial) took 48.86114311218262s
Conciseness | Check Extensional conciseness for National Digital Data Archive of Hungary (partial) took 0.001998424530029297s
Conciseness | Check Intensional conciseness for National Digital Data Archive of Hungary (partial) took 0.29114270210266113s
Security | Sign check for National Digital Data Archive of Hungary (partial) took 0.21894335746765137s
Availability | Check URIs Dereferenciability for National Digital Data Archive of Hungary (partial) took 22.46628737449646s
Completeness | Calculation of interlinking completeness for National Digital Data Archive of Hungary (partial) took 1.2239875793457031s
Reputation | Calculation of the PageRank for National Digital Data Archive of Hungary (partial) took 0.02147817611694336s
Interlinking | Calculation of Degree of Connection for National Digital Data Archive of Hungary (partial) took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for National Digital Data Archive of Hungary (partial) took 0.0010907649993896484s
Interlinking | Calculation of Clustering coefficient for National Digital Data Archive of Hungary (partial) took 0.00011157989501953125s
Interoperability | Check the re-using of existing vocabs for National Digital Data Archive of Hungary (partial) took 2.1457672119140625e-06s
Believability | Calculation of trust value for National Digital Data Archive of Hungary (partial) took 7.3909759521484375e-06s
INFO | --- Analysis for sztaki-lod took 504.6699786186218s
Availability | SPARQL endpoint availability check for Thesaurus for Graphic Materials (t4gm.info) took 4.291534423828125e-05s
Availability | VoID file availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.0007479190826416016s
Completeness | Calculation of interlinking completeness for Thesaurus for Graphic Materials (t4gm.info) took 0.27489471435546875s
Reputation | Calculation of the PageRank for Thesaurus for Graphic Materials (t4gm.info) took 0.020812273025512695s
Interlinking | Calculation of Degree of Connection for Thesaurus for Graphic Materials (t4gm.info) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Thesaurus for Graphic Materials (t4gm.info) took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Thesaurus for Graphic Materials (t4gm.info) took 5.1975250244140625e-05s
Believability | Calculation of trust value for Thesaurus for Graphic Materials (t4gm.info) took 6.9141387939453125e-06s
INFO | --- Analysis for t4gm-info took 6.088906526565552s
Availability | SPARQL endpoint availability check for tags2con delicious took 4.124641418457031e-05s
Availability | VoID file availability check for tags2con delicious took 0.0008206367492675781s
Completeness | Calculation of interlinking completeness for tags2con delicious took 0.3928050994873047s
Reputation | Calculation of the PageRank for tags2con delicious took 0.0213625431060791s
Interlinking | Calculation of Degree of Connection for tags2con delicious took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for tags2con delicious took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for tags2con delicious took 5.936622619628906e-05s
Believability | Calculation of trust value for tags2con delicious took 7.152557373046875e-06s
INFO | --- Analysis for tags2con-delicious took 847.5948874950409s
Availability | SPARQL endpoint availability check for Taiwan geographic names took 262.94207978248596s
Availability | VoID file availability check for Taiwan geographic names took 0.0008022785186767578s
Completeness | Calculation of interlinking completeness for Taiwan geographic names took 0.8555276393890381s
Reputation | Calculation of the PageRank for Taiwan geographic names took 0.02075338363647461s
Interlinking | Calculation of Degree of Connection for Taiwan geographic names took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Taiwan geographic names took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for Taiwan geographic names took 5.9604644775390625e-05s
Believability | Calculation of trust value for Taiwan geographic names took 6.9141387939453125e-06s
INFO | --- Analysis for taiwan-geographic-names took 669.430557012558s
Availability | SPARQL endpoint availability check for Open Library data mirror in the Talis Platform took 8.249282836914062e-05s
Availability | VoID file availability check for Open Library data mirror in the Talis Platform took 0.0006971359252929688s
Completeness | Calculation of interlinking completeness for Open Library data mirror in the Talis Platform took 0.7069392204284668s
Reputation | Calculation of the PageRank for Open Library data mirror in the Talis Platform took 0.020837068557739258s
Interlinking | Calculation of Degree of Connection for Open Library data mirror in the Talis Platform took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open Library data mirror in the Talis Platform took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Open Library data mirror in the Talis Platform took 9.918212890625e-05s
Believability | Calculation of trust value for Open Library data mirror in the Talis Platform took 2.4557113647460938e-05s
INFO | --- Analysis for talis-openlibrary took 7.829241991043091s
Availability | SPARQL endpoint availability check for TalkBank took 4.076957702636719e-05s
Availability | VoID file availability check for TalkBank took 0.00029540061950683594s
Completeness | Calculation of interlinking completeness for TalkBank took 0.2620973587036133s
Reputation | Calculation of the PageRank for TalkBank took 0.020768165588378906s
Interlinking | Calculation of Degree of Connection for TalkBank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for TalkBank took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for TalkBank took 3.0517578125e-05s
Believability | Calculation of trust value for TalkBank took 7.3909759521484375e-06s
INFO | --- Analysis for talkbank took 6.07250189781189s
Availability | SPARQL endpoint availability check for TaxonConcept Knowledge Base took 0.9354767799377441s
Availability | VoID file availability check for TaxonConcept Knowledge Base took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for TaxonConcept Knowledge Base took 0.3508000373840332s
Reputation | Calculation of the PageRank for TaxonConcept Knowledge Base took 0.020657777786254883s
Interlinking | Calculation of Degree of Connection for TaxonConcept Knowledge Base took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for TaxonConcept Knowledge Base took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for TaxonConcept Knowledge Base took 0.00012183189392089844s
Believability | Calculation of trust value for TaxonConcept Knowledge Base took 7.3909759521484375e-06s
INFO | --- Analysis for taxonconcept took 14.875112771987915s
Availability | SPARQL endpoint availability check for taxonconcept-assets took 4.1961669921875e-05s
Availability | VoID file availability check for taxonconcept-assets took 0.0005741119384765625s
Completeness | Calculation of interlinking completeness for taxonconcept-assets took 0.26531410217285156s
Reputation | Calculation of the PageRank for taxonconcept-assets took 0.020711183547973633s
Interlinking | Calculation of Degree of Connection for taxonconcept-assets took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for taxonconcept-assets took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for taxonconcept-assets took 7.843971252441406e-05s
Believability | Calculation of trust value for taxonconcept-assets took 1.5497207641601562e-05s
INFO | --- Analysis for taxonconcept-assets took 2.83113431930542s
Availability | SPARQL endpoint availability check for taxonconcept-occurences took 4.100799560546875e-05s
Availability | VoID file availability check for taxonconcept-occurences took 0.0005402565002441406s
Completeness | Calculation of interlinking completeness for taxonconcept-occurences took 0.2687380313873291s
Reputation | Calculation of the PageRank for taxonconcept-occurences took 0.020631790161132812s
Interlinking | Calculation of Degree of Connection for taxonconcept-occurences took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for taxonconcept-occurences took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for taxonconcept-occurences took 5.0067901611328125e-05s
Believability | Calculation of trust value for taxonconcept-occurences took 6.67572021484375e-06s
INFO | --- Analysis for taxonconcept-occurences took 2.72548770904541s
Availability | SPARQL endpoint availability check for TAXREF-LD: Linked Data French Taxonomic Register took 0.536186695098877s
Availability | VoID file availability check for TAXREF-LD: Linked Data French Taxonomic Register took 0.0006830692291259766s
Completeness | Calculation of interlinking completeness for TAXREF-LD: Linked Data French Taxonomic Register took 0.27071666717529297s
Reputation | Calculation of the PageRank for TAXREF-LD: Linked Data French Taxonomic Register took 0.020768165588378906s
Interlinking | Calculation of Degree of Connection for TAXREF-LD: Linked Data French Taxonomic Register took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for TAXREF-LD: Linked Data French Taxonomic Register took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for TAXREF-LD: Linked Data French Taxonomic Register took 4.863739013671875e-05s
Believability | Calculation of trust value for TAXREF-LD: Linked Data French Taxonomic Register took 6.67572021484375e-06s
INFO | --- Analysis for taxref-ld took 5.901191473007202s
Availability | SPARQL endpoint availability check for The Cancer Genome Atlas took 0.7437412738800049s
Availability | VoID file availability check for The Cancer Genome Atlas took 0.0006310939788818359s
Completeness | Calculation of interlinking completeness for The Cancer Genome Atlas took 0.2665386199951172s
Reputation | Calculation of the PageRank for The Cancer Genome Atlas took 0.020540714263916016s
Interlinking | Calculation of Degree of Connection for The Cancer Genome Atlas took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The Cancer Genome Atlas took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for The Cancer Genome Atlas took 3.075599670410156e-05s
Believability | Calculation of trust value for The Cancer Genome Atlas took 6.4373016357421875e-06s
INFO | --- Analysis for tcga took 8.81834101676941s
Availability | SPARQL endpoint availability check for TCGA Roadmap took 0.3395681381225586s
Availability | VoID file availability check for TCGA Roadmap took 0.0009434223175048828s
Completeness | Calculation of interlinking completeness for TCGA Roadmap took 0.28084731101989746s
Reputation | Calculation of the PageRank for TCGA Roadmap took 0.02037835121154785s
Interlinking | Calculation of Degree of Connection for TCGA Roadmap took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for TCGA Roadmap took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for TCGA Roadmap took 7.271766662597656e-05s
Believability | Calculation of trust value for TCGA Roadmap took 6.198883056640625e-06s
INFO | --- Analysis for tcga-roadmap took 18.53490447998047s
Availability | SPARQL endpoint availability check for TCMGeneDIT Dataset took 1.4572131633758545s
Availability | VoID file availability check for TCMGeneDIT Dataset took 0.0006763935089111328s
Completeness | Calculation of interlinking completeness for TCMGeneDIT Dataset took 0.2655971050262451s
Reputation | Calculation of the PageRank for TCMGeneDIT Dataset took 0.02045297622680664s
Interlinking | Calculation of Degree of Connection for TCMGeneDIT Dataset took 1.52587890625e-05s
Interlinking | Calculation of Centrality for TCMGeneDIT Dataset took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for TCMGeneDIT Dataset took 9.965896606445312e-05s
Believability | Calculation of trust value for TCMGeneDIT Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for tcmgenedit_dataset took 141.99638772010803s
Availability | SPARQL endpoint availability check for TDS took 4.124641418457031e-05s
Availability | VoID file availability check for TDS took 0.0008192062377929688s
Completeness | Calculation of interlinking completeness for TDS took 0.2555570602416992s
Reputation | Calculation of the PageRank for TDS took 0.020398616790771484s
Interlinking | Calculation of Degree of Connection for TDS took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for TDS took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for TDS took 4.3392181396484375e-05s
Believability | Calculation of trust value for TDS took 5.245208740234375e-06s
INFO | --- Analysis for tds took 5.534995079040527s
Availability | SPARQL endpoint availability check for TED Talks took 3.981590270996094e-05s
Availability | VoID file availability check for TED Talks took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for TED Talks took 0.727773904800415s
Reputation | Calculation of the PageRank for TED Talks took 0.020369529724121094s
Interlinking | Calculation of Degree of Connection for TED Talks took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for TED Talks took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for TED Talks took 2.7418136596679688e-05s
Believability | Calculation of trust value for TED Talks took 7.152557373046875e-06s
INFO | --- Analysis for ted-talks took 3.7565464973449707s
Availability | SPARQL endpoint availability check for TEKORD took 4.220008850097656e-05s
Availability | VoID file availability check for TEKORD took 0.0005903244018554688s
Completeness | Calculation of interlinking completeness for TEKORD took 0.27481985092163086s
Reputation | Calculation of the PageRank for TEKORD took 0.025501728057861328s
Interlinking | Calculation of Degree of Connection for TEKORD took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for TEKORD took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for TEKORD took 4.982948303222656e-05s
Believability | Calculation of trust value for TEKORD took 5.9604644775390625e-06s
INFO | --- Analysis for tekord took 5.524899244308472s
Availability | SPARQL endpoint availability check for Telegraphis Linked Data took 1.7807188034057617s
Availability | VoID file availability check for Telegraphis Linked Data took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for Telegraphis Linked Data took 0.2561759948730469s
Reputation | Calculation of the PageRank for Telegraphis Linked Data took 0.020295381546020508s
Interlinking | Calculation of Degree of Connection for Telegraphis Linked Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Telegraphis Linked Data took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Telegraphis Linked Data took 0.00010848045349121094s
Believability | Calculation of trust value for Telegraphis Linked Data took 4.76837158203125e-06s
INFO | --- Analysis for telegraphis took 8.155865669250488s
Availability | SPARQL endpoint availability check for Temple ov thee Lemur took 4.2438507080078125e-05s
Availability | VoID file availability check for Temple ov thee Lemur took 0.0006535053253173828s
Completeness | Calculation of interlinking completeness for Temple ov thee Lemur took 0.691746711730957s
Reputation | Calculation of the PageRank for Temple ov thee Lemur took 0.022310972213745117s
Interlinking | Calculation of Degree of Connection for Temple ov thee Lemur took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Temple ov thee Lemur took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Temple ov thee Lemur took 7.319450378417969e-05s
Believability | Calculation of trust value for Temple ov thee Lemur took 6.67572021484375e-06s
INFO | --- Analysis for temple-ov-thee-lemur-datasets took 15.499190092086792s
Availability | SPARQL endpoint availability check for TERENCE Reading Comprehension Dataset took 4.00543212890625e-05s
Availability | VoID file availability check for TERENCE Reading Comprehension Dataset took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for TERENCE Reading Comprehension Dataset took 0.2649555206298828s
Reputation | Calculation of the PageRank for TERENCE Reading Comprehension Dataset took 0.0271298885345459s
Interlinking | Calculation of Degree of Connection for TERENCE Reading Comprehension Dataset took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for TERENCE Reading Comprehension Dataset took 0.0012221336364746094s
Interlinking | Calculation of Clustering coefficient for TERENCE Reading Comprehension Dataset took 3.552436828613281e-05s
Believability | Calculation of trust value for TERENCE Reading Comprehension Dataset took 6.198883056640625e-06s
INFO | --- Analysis for terence-reading-comprehension-dataset took 2.950409412384033s
Availability | SPARQL endpoint availability check for Terminesp Linked Data took 7.367134094238281e-05s
Availability | VoID file availability check for Terminesp Linked Data took 0.0002353191375732422s
Completeness | Calculation of interlinking completeness for Terminesp Linked Data took 0.2815523147583008s
Reputation | Calculation of the PageRank for Terminesp Linked Data took 0.021044492721557617s
Interlinking | Calculation of Degree of Connection for Terminesp Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Terminesp Linked Data took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Terminesp Linked Data took 2.8133392333984375e-05s
Believability | Calculation of trust value for Terminesp Linked Data took 6.67572021484375e-06s
INFO | --- Analysis for terminesp took 2.9546077251434326s
Availability | SPARQL endpoint availability check for Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Ontology took 0.0005743503570556641s
Completeness | Calculation of interlinking completeness for Ontology took 0.2573390007019043s
Reputation | Calculation of the PageRank for Ontology took 0.020246028900146484s
Interlinking | Calculation of Degree of Connection for Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontology took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Ontology took 2.6464462280273438e-05s
Believability | Calculation of trust value for Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for Terrorist_attack took 2.9497811794281006s
Availability | SPARQL endpoint availability check for Terrorist Attack1 took 4.76837158203125e-05s
Availability | VoID file availability check for Terrorist Attack1 took 0.00028586387634277344s
Completeness | Calculation of interlinking completeness for Terrorist Attack1 took 0.2624518871307373s
Reputation | Calculation of the PageRank for Terrorist Attack1 took 0.020807266235351562s
Interlinking | Calculation of Degree of Connection for Terrorist Attack1 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Terrorist Attack1 took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Terrorist Attack1 took 2.86102294921875e-05s
Believability | Calculation of trust value for Terrorist Attack1 took 6.67572021484375e-06s
INFO | --- Analysis for Terrorist_Attack_1 took 2.4289441108703613s
Availability | SPARQL endpoint availability check for Tesauro materias BUPM took 3.981590270996094e-05s
Availability | VoID file availability check for Tesauro materias BUPM took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for Tesauro materias BUPM took 0.28908586502075195s
Reputation | Calculation of the PageRank for Tesauro materias BUPM took 0.020235300064086914s
Interlinking | Calculation of Degree of Connection for Tesauro materias BUPM took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Tesauro materias BUPM took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Tesauro materias BUPM took 2.6941299438476562e-05s
Believability | Calculation of trust value for Tesauro materias BUPM took 7.867813110351562e-06s
INFO | --- Analysis for tesauro-materias-bupm took 2.8974123001098633s
Availability | SPARQL endpoint availability check for Teseo took 6.866455078125e-05s
Availability | VoID file availability check for Teseo took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for Teseo took 0.257824182510376s
Reputation | Calculation of the PageRank for Teseo took 0.021666288375854492s
Interlinking | Calculation of Degree of Connection for Teseo took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Teseo took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Teseo took 2.9325485229492188e-05s
Believability | Calculation of trust value for Teseo took 6.4373016357421875e-06s
INFO | --- Analysis for teseo took 2.9529435634613037s
Availability | SPARQL endpoint availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 7.200241088867188e-05s
Availability | VoID file availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.000728607177734375s
Completeness | Calculation of interlinking completeness for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.2755470275878906s
Reputation | Calculation of the PageRank for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.020342588424682617s
Interlinking | Calculation of Degree of Connection for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 2.9325485229492188e-05s
Believability | Calculation of trust value for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 5.9604644775390625e-06s
INFO | --- Analysis for Tesla_Deaths took 3.376401424407959s
Availability | SPARQL endpoint availability check for test took 4.1484832763671875e-05s
Availability | VoID file availability check for test took 0.00022745132446289062s
Completeness | Calculation of interlinking completeness for test took 0.2962958812713623s
Reputation | Calculation of the PageRank for test took 0.02021622657775879s
Interlinking | Calculation of Degree of Connection for test took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for test took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for test took 2.8133392333984375e-05s
Believability | Calculation of trust value for test took 6.67572021484375e-06s
INFO | --- Analysis for test took 2.789348840713501s
Availability | SPARQL endpoint availability check for Test took 4.1961669921875e-05s
Availability | VoID file availability check for Test took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for Test took 0.26122593879699707s
Reputation | Calculation of the PageRank for Test took 0.020496129989624023s
Interlinking | Calculation of Degree of Connection for Test took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Test took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Test took 3.457069396972656e-05s
Believability | Calculation of trust value for Test took 6.4373016357421875e-06s
INFO | --- Analysis for Test took 2.3636598587036133s
Availability | SPARQL endpoint availability check for test-svu took 20.189993143081665s
Availability | VoID file availability check for test-svu took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for test-svu took 0.2888040542602539s
Reputation | Calculation of the PageRank for test-svu took 0.02066969871520996s
Interlinking | Calculation of Degree of Connection for test-svu took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for test-svu took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for test-svu took 3.218650817871094e-05s
Believability | Calculation of trust value for test-svu took 7.867813110351562e-06s
INFO | --- Analysis for test-svu took 52.64322018623352s
Availability | SPARQL endpoint availability check for Test took 4.076957702636719e-05s
Availability | VoID file availability check for Test took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for Test took 0.27644920349121094s
Reputation | Calculation of the PageRank for Test took 0.02049565315246582s
Interlinking | Calculation of Degree of Connection for Test took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Test took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Test took 2.86102294921875e-05s
Believability | Calculation of trust value for Test took 8.106231689453125e-06s
INFO | --- Analysis for Test_ took 2.491374969482422s
Availability | SPARQL endpoint availability check for xxxxx took 260.7586410045624s
Availability | VoID file availability check for xxxxx took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for xxxxx took 0.7368824481964111s
Reputation | Calculation of the PageRank for xxxxx took 0.0212705135345459s
Interlinking | Calculation of Degree of Connection for xxxxx took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for xxxxx took 0.0008115768432617188s
Interlinking | Calculation of Clustering coefficient for xxxxx took 4.553794860839844e-05s
Believability | Calculation of trust value for xxxxx took 7.3909759521484375e-06s
INFO | --- Analysis for testee took 799.9226138591766s
Availability | SPARQL endpoint availability check for Texai Lexicon took 4.172325134277344e-05s
Availability | VoID file availability check for Texai Lexicon took 0.00029158592224121094s
Completeness | Calculation of interlinking completeness for Texai Lexicon took 0.308469295501709s
Reputation | Calculation of the PageRank for Texai Lexicon took 0.020748615264892578s
Interlinking | Calculation of Degree of Connection for Texai Lexicon took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Texai Lexicon took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Texai Lexicon took 3.62396240234375e-05s
Believability | Calculation of trust value for Texai Lexicon took 7.3909759521484375e-06s
INFO | --- Analysis for texai_lexicon took 6.525154113769531s
Availability | SPARQL endpoint availability check for tharawat magazine took 4.1484832763671875e-05s
Availability | VoID file availability check for tharawat magazine took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for tharawat magazine took 0.7432732582092285s
Reputation | Calculation of the PageRank for tharawat magazine took 0.02068471908569336s
Interlinking | Calculation of Degree of Connection for tharawat magazine took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for tharawat magazine took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for tharawat magazine took 0.00010657310485839844s
Believability | Calculation of trust value for tharawat magazine took 7.3909759521484375e-06s
INFO | --- Analysis for tharawat-magazine-com took 3.93987774848938s
Availability | SPARQL endpoint availability check for The CIARD RING took 3.9577484130859375e-05s
Availability | VoID file availability check for The CIARD RING took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for The CIARD RING took 0.24500370025634766s
Reputation | Calculation of the PageRank for The CIARD RING took 0.020490646362304688s
Interlinking | Calculation of Degree of Connection for The CIARD RING took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The CIARD RING took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for The CIARD RING took 2.956390380859375e-05s
Believability | Calculation of trust value for The CIARD RING took 8.58306884765625e-06s
INFO | --- Analysis for the-ciard-ring took 3.3097681999206543s
Availability | SPARQL endpoint availability check for The Drug Interaction Knowledge Base took 0.1873159408569336s
Availability | VoID file availability check for The Drug Interaction Knowledge Base took 0.00045180320739746094s
Completeness | Calculation of interlinking completeness for The Drug Interaction Knowledge Base took 0.27091217041015625s
Reputation | Calculation of the PageRank for The Drug Interaction Knowledge Base took 0.020744800567626953s
Interlinking | Calculation of Degree of Connection for The Drug Interaction Knowledge Base took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for The Drug Interaction Knowledge Base took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for The Drug Interaction Knowledge Base took 3.0040740966796875e-05s
Believability | Calculation of trust value for The Drug Interaction Knowledge Base took 5.4836273193359375e-06s
INFO | --- Analysis for the-drug-interaction-knowledge-base took 3.0655951499938965s
Availability | SPARQL endpoint availability check for The European Library Open Dataset took 0.8236515522003174s
Availability | VoID file availability check for The European Library Open Dataset took 0.0007526874542236328s
Extra | Recovery of all triples for The European Library Open Dataset took 1.151064157485962s
Performance | Total latancy measurement for The European Library Open Dataset took 1.435140609741211s
Amount of data | Number of triples check for The European Library Open Dataset took 30.222144842147827s
Versatility | Languages check for The European Library Open Dataset took 0.326829195022583s
Interpretability | Number of blank nodes check for The European Library Open Dataset took 30.207438230514526s
Interpretability | RDF structures check for The European Library Open Dataset took 0.24612784385681152s
Versatility | Serialization formats check for The European Library Open Dataset took 0.23233747482299805s
Availability | RDF dump link check for The European Library Open Dataset took 0.3198201656341553s
License | MR license check for The European Library Open Dataset took 0.3553345203399658s
License | HR license check for The European Library Open Dataset took 0.2624516487121582s
Amount of data | Number of property check for The European Library Open Dataset took 0.24463701248168945s
Understandability | Number of label check for The European Library Open Dataset took 2.1610891819000244s
Understandability | URI regex check for The European Library Open Dataset took 0.49495363235473633s
Understandability | Vocabs check for The European Library Open Dataset took 0.23857474327087402s
Verifiability | Authors check for The European Library Open Dataset took 0.2850368022918701s
Verifiability | Publishers check for The European Library Open Dataset took 0.2544269561767578s
Performance | Throughput check for The European Library Open Dataset took 11.425252676010132s
Amount of data | Check the number of entities for The European Library Open Dataset took 6.747245788574219e-05s
Verifiability | Contribs. check for The European Library Open Dataset took 0.2402818202972412s
Interlinking | sameAs chians check for The European Library Open Dataset took 0.2876319885253906s
Interlinking | skos check for The European Library Open Dataset took 0.26253533363342285s
Interlinking | skos check for The European Library Open Dataset took 0.9403321743011475s
Timeliness | dataset update frequency check for The European Library Open Dataset took 0.2528378963470459s
Currency | Creation date check for The European Library Open Dataset took 2.0654232501983643s
Currency | Modification date check for The European Library Open Dataset took 0.4353606700897217s
Rep.Conc. | URIs length for The European Library Open Dataset took 60.478468894958496s
Interoperability | New vocabularies check for The European Library Open Dataset took 4.5299530029296875e-06s
Consistency | Deprecated classes/propertiers check for The European Library Open Dataset took 0.23375797271728516s
Accuracy | Check Empty annotation labels for The European Library Open Dataset took 2.3525824546813965s
Accuracy | Check White space in annotation for The European Library Open Dataset took 0.030904293060302734s
Accuracy | Check Datatype consistency for The European Library Open Dataset took 0.028857946395874023s
Consistency | Disjoint class check for The European Library Open Dataset took 0.2634544372558594s
Consistency | Check Misplaced properties for The European Library Open Dataset took 30.52740740776062s
Consistency | Misplaced classes for The European Library Open Dataset took 0.3567352294921875s
Consistency | Check Ontology hijacking for The European Library Open Dataset took 1.7112274169921875s
Consistency | Check Invalid usage of undefined classes for The European Library Open Dataset took 1.1679778099060059s
Consistency | Check Invalid usage of undefined properties for The European Library Open Dataset took 31.365057945251465s
Conciseness | Check Extensional conciseness for The European Library Open Dataset took 0.034314632415771484s
Conciseness | Check Intensional conciseness for The European Library Open Dataset took 0.2873528003692627s
Security | Sign check for The European Library Open Dataset took 0.2819995880126953s
Availability | Check URIs Dereferenciability for The European Library Open Dataset took 8.195608615875244s
Completeness | Calculation of interlinking completeness for The European Library Open Dataset took 0.4695582389831543s
Reputation | Calculation of the PageRank for The European Library Open Dataset took 0.020471811294555664s
Interlinking | Calculation of Degree of Connection for The European Library Open Dataset took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for The European Library Open Dataset took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for The European Library Open Dataset took 6.341934204101562e-05s
Interoperability | Check the re-using of existing vocabs for The European Library Open Dataset took 1.9073486328125e-06s
Believability | Calculation of trust value for The European Library Open Dataset took 6.198883056640625e-06s
INFO | --- Analysis for the-european-library-open-dataset took 401.460666179657s
Availability | SPARQL endpoint availability check for The Eurostat Linked Data took 60.03740167617798s
Availability | VoID file availability check for The Eurostat Linked Data took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for The Eurostat Linked Data took 0.7232580184936523s
Reputation | Calculation of the PageRank for The Eurostat Linked Data took 0.020277738571166992s
Interlinking | Calculation of Degree of Connection for The Eurostat Linked Data took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for The Eurostat Linked Data took 0.0008022785186767578s
Interlinking | Calculation of Clustering coefficient for The Eurostat Linked Data took 0.00010204315185546875s
Believability | Calculation of trust value for The Eurostat Linked Data took 5.245208740234375e-06s
INFO | --- Analysis for the-eurostat-linked-data took 244.4459354877472s
Availability | SPARQL endpoint availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 4.00543212890625e-05s
Availability | VoID file availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.7115895748138428s
Reputation | Calculation of the PageRank for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.021405696868896484s
Interlinking | Calculation of Degree of Connection for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 2.8133392333984375e-05s
Believability | Calculation of trust value for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 7.152557373046875e-06s
INFO | --- Analysis for the-kazan-university-museum-as-linked-open-data-in-the-europeana-data-model took 6.084198713302612s
Availability | SPARQL endpoint availability check for The Living LOD Cloud took 4.124641418457031e-05s
Availability | VoID file availability check for The Living LOD Cloud took 0.000743865966796875s
Completeness | Calculation of interlinking completeness for The Living LOD Cloud took 0.7192490100860596s
Reputation | Calculation of the PageRank for The Living LOD Cloud took 0.0206911563873291s
Interlinking | Calculation of Degree of Connection for The Living LOD Cloud took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for The Living LOD Cloud took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for The Living LOD Cloud took 7.009506225585938e-05s
Believability | Calculation of trust value for The Living LOD Cloud took 6.67572021484375e-06s
INFO | --- Analysis for the-living-lod-cloud took 88.81570816040039s
Availability | SPARQL endpoint availability check for The MIDI Linked Data Cloud took 4.124641418457031e-05s
Availability | VoID file availability check for The MIDI Linked Data Cloud took 0.00023746490478515625s
Completeness | Calculation of interlinking completeness for The MIDI Linked Data Cloud took 0.6954600811004639s
Reputation | Calculation of the PageRank for The MIDI Linked Data Cloud took 0.02010941505432129s
Interlinking | Calculation of Degree of Connection for The MIDI Linked Data Cloud took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for The MIDI Linked Data Cloud took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for The MIDI Linked Data Cloud took 2.765655517578125e-05s
Believability | Calculation of trust value for The MIDI Linked Data Cloud took 6.4373016357421875e-06s
INFO | --- Analysis for the-midi-linked-data-cloud took 5.215378046035767s
Availability | SPARQL endpoint availability check for The View From took 0.06273365020751953s
Availability | VoID file availability check for The View From took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for The View From took 0.25443005561828613s
Reputation | Calculation of the PageRank for The View From took 0.020317792892456055s
Interlinking | Calculation of Degree of Connection for The View From took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The View From took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for The View From took 7.891654968261719e-05s
Believability | Calculation of trust value for The View From took 6.4373016357421875e-06s
INFO | --- Analysis for the-view-from took 3.0191168785095215s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.479368209838867s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0006704330444335938s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.26308155059814453s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.020925521850585938s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 2.8848648071289062e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 6.67572021484375e-06s
INFO | --- Analysis for The_Central_Bank_of_the_Republic_of_Uzbekistan took 73.44951033592224s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.27782368659973s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0007004737854003906s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.7270996570587158s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.020460128784179688s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 3.6716461181640625e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 5.9604644775390625e-06s
INFO | --- Analysis for The_Respublic_of_Uzbekistan took 104.5649631023407s
Availability | SPARQL endpoint availability check for The Content Wrangler took 4.1961669921875e-05s
Availability | VoID file availability check for The Content Wrangler took 0.0004923343658447266s
Completeness | Calculation of interlinking completeness for The Content Wrangler took 0.2721848487854004s
Reputation | Calculation of the PageRank for The Content Wrangler took 0.020422935485839844s
Interlinking | Calculation of Degree of Connection for The Content Wrangler took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for The Content Wrangler took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for The Content Wrangler took 0.00010728836059570312s
Believability | Calculation of trust value for The Content Wrangler took 6.67572021484375e-06s
INFO | --- Analysis for thecontentwrangler-com took 3.8721039295196533s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 5.173683166503906e-05s
Availability | VoID file availability check for Thesaurus BNCF took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.2912783622741699s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.020508527755737305s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 2.8371810913085938e-05s
Believability | Calculation of trust value for Thesaurus BNCF took 7.152557373046875e-06s
INFO | --- Analysis for thesaurus-bncf took 3.8214192390441895s
Availability | SPARQL endpoint availability check for Thesaurus Datenwissen took 4.291534423828125e-05s
Availability | VoID file availability check for Thesaurus Datenwissen took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for Thesaurus Datenwissen took 0.26957249641418457s
Reputation | Calculation of the PageRank for Thesaurus Datenwissen took 0.020326614379882812s
Interlinking | Calculation of Degree of Connection for Thesaurus Datenwissen took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Thesaurus Datenwissen took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Thesaurus Datenwissen took 2.8371810913085938e-05s
Believability | Calculation of trust value for Thesaurus Datenwissen took 8.106231689453125e-06s
INFO | --- Analysis for thesaurus-datenwissen took 2.9272501468658447s
Availability | SPARQL endpoint availability check for Thesaurus W for Local Archives took 0.18806171417236328s
Availability | VoID file availability check for Thesaurus W for Local Archives took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for Thesaurus W for Local Archives took 0.2772562503814697s
Reputation | Calculation of the PageRank for Thesaurus W for Local Archives took 0.020276784896850586s
Interlinking | Calculation of Degree of Connection for Thesaurus W for Local Archives took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Thesaurus W for Local Archives took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Thesaurus W for Local Archives took 7.200241088867188e-05s
Believability | Calculation of trust value for Thesaurus W for Local Archives took 7.62939453125e-06s
INFO | --- Analysis for thesaurus-w took 3.5465593338012695s
Availability | SPARQL endpoint availability check for theses.fr took 4.124641418457031e-05s
Availability | VoID file availability check for theses.fr took 0.0007100105285644531s
Completeness | Calculation of interlinking completeness for theses.fr took 0.26586103439331055s
Reputation | Calculation of the PageRank for theses.fr took 0.02031683921813965s
Interlinking | Calculation of Degree of Connection for theses.fr took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for theses.fr took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for theses.fr took 4.458427429199219e-05s
Believability | Calculation of trust value for theses.fr took 7.867813110351562e-06s
INFO | --- Analysis for thesesfr took 4.38913631439209s
Availability | SPARQL endpoint availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 4.363059997558594e-05s
Availability | VoID file availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.28718996047973633s
Reputation | Calculation of the PageRank for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0201568603515625s
Interlinking | Calculation of Degree of Connection for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 3.1948089599609375e-05s
Believability | Calculation of trust value for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 7.3909759521484375e-06s
INFO | --- Analysis for Thinkphile took 2.4119091033935547s
Availability | SPARQL endpoint availability check for ThIST took 264.76041054725647s
Availability | VoID file availability check for ThIST took 0.0010116100311279297s
Completeness | Calculation of interlinking completeness for ThIST took 0.2736475467681885s
Reputation | Calculation of the PageRank for ThIST took 0.021074533462524414s
Interlinking | Calculation of Degree of Connection for ThIST took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for ThIST took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for ThIST took 0.00011181831359863281s
Believability | Calculation of trust value for ThIST took 8.58306884765625e-06s
INFO | --- Analysis for thist took 570.3784935474396s
Availability | SPARQL endpoint availability check for TIP took 40.040828466415405s
Availability | VoID file availability check for TIP took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for TIP took 0.7479572296142578s
Reputation | Calculation of the PageRank for TIP took 0.02076411247253418s
Interlinking | Calculation of Degree of Connection for TIP took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for TIP took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for TIP took 0.00010561943054199219s
Believability | Calculation of trust value for TIP took 7.152557373046875e-06s
INFO | --- Analysis for tip took 105.29349780082703s
Availability | SPARQL endpoint availability check for Topography based Hydrological Model took 4.2438507080078125e-05s
Availability | VoID file availability check for Topography based Hydrological Model took 0.00037550926208496094s
Completeness | Calculation of interlinking completeness for Topography based Hydrological Model took 0.26462793350219727s
Reputation | Calculation of the PageRank for Topography based Hydrological Model took 0.02076864242553711s
Interlinking | Calculation of Degree of Connection for Topography based Hydrological Model took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Topography based Hydrological Model took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Topography based Hydrological Model took 3.0994415283203125e-05s
Believability | Calculation of trust value for Topography based Hydrological Model took 7.867813110351562e-06s
INFO | --- Analysis for TOPMODEL took 21.9634051322937s
Availability | SPARQL endpoint availability check for Tourpedia took 4.0531158447265625e-05s
Availability | VoID file availability check for Tourpedia took 0.0003509521484375s
Completeness | Calculation of interlinking completeness for Tourpedia took 0.2593357563018799s
Reputation | Calculation of the PageRank for Tourpedia took 0.02064371109008789s
Interlinking | Calculation of Degree of Connection for Tourpedia took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Tourpedia took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Tourpedia took 2.8371810913085938e-05s
Believability | Calculation of trust value for Tourpedia took 7.62939453125e-06s
INFO | --- Analysis for tourpedia took 4.609970569610596s
Availability | SPARQL endpoint availability check for Observation dataset of forest ecosystems  took 3.365450382232666s
Availability | VoID file availability check for Observation dataset of forest ecosystems  took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for Observation dataset of forest ecosystems  took 0.29042673110961914s
Reputation | Calculation of the PageRank for Observation dataset of forest ecosystems  took 0.02044367790222168s
Interlinking | Calculation of Degree of Connection for Observation dataset of forest ecosystems  took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Observation dataset of forest ecosystems  took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Observation dataset of forest ecosystems  took 3.170967102050781e-05s
Believability | Calculation of trust value for Observation dataset of forest ecosystems  took 7.3909759521484375e-06s
INFO | --- Analysis for TP-data took 8.077701330184937s
Availability | SPARQL endpoint availability check for True Parents Legacy Teaching Archive took 4.6253204345703125e-05s
Availability | VoID file availability check for True Parents Legacy Teaching Archive took 0.0008063316345214844s
Completeness | Calculation of interlinking completeness for True Parents Legacy Teaching Archive took 0.2673823833465576s
Reputation | Calculation of the PageRank for True Parents Legacy Teaching Archive took 0.020719051361083984s
Interlinking | Calculation of Degree of Connection for True Parents Legacy Teaching Archive took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for True Parents Legacy Teaching Archive took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for True Parents Legacy Teaching Archive took 1.3113021850585938e-05s
Believability | Calculation of trust value for True Parents Legacy Teaching Archive took 7.3909759521484375e-06s
INFO | --- Analysis for tplegacy took 4.091646671295166s
Availability | SPARQL endpoint availability check for Trackloaded Linked Open Data took 2.000612735748291s
Availability | VoID file availability check for Trackloaded Linked Open Data took 0.0006537437438964844s
Completeness | Calculation of interlinking completeness for Trackloaded Linked Open Data took 0.2747650146484375s
Reputation | Calculation of the PageRank for Trackloaded Linked Open Data took 0.02027583122253418s
Interlinking | Calculation of Degree of Connection for Trackloaded Linked Open Data took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Trackloaded Linked Open Data took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Trackloaded Linked Open Data took 1.2636184692382812e-05s
Believability | Calculation of trust value for Trackloaded Linked Open Data took 6.4373016357421875e-06s
INFO | --- Analysis for trackloaded took 15.238241910934448s
Availability | SPARQL endpoint availability check for Traditional Korean Medicine Ontology took 0.5983715057373047s
Availability | VoID file availability check for Traditional Korean Medicine Ontology took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for Traditional Korean Medicine Ontology took 0.2661905288696289s
Reputation | Calculation of the PageRank for Traditional Korean Medicine Ontology took 0.02030658721923828s
Interlinking | Calculation of Degree of Connection for Traditional Korean Medicine Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Traditional Korean Medicine Ontology took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for Traditional Korean Medicine Ontology took 4.100799560546875e-05s
Believability | Calculation of trust value for Traditional Korean Medicine Ontology took 6.198883056640625e-06s
INFO | --- Analysis for traditional-korean-medicine took 4.115250110626221s
Availability | SPARQL endpoint availability check for Traffic Scotland took 10.148482084274292s
Availability | VoID file availability check for Traffic Scotland took 0.0004718303680419922s
Completeness | Calculation of interlinking completeness for Traffic Scotland took 0.2635316848754883s
Reputation | Calculation of the PageRank for Traffic Scotland took 0.020260095596313477s
Interlinking | Calculation of Degree of Connection for Traffic Scotland took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Traffic Scotland took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Traffic Scotland took 3.170967102050781e-05s
Believability | Calculation of trust value for Traffic Scotland took 4.76837158203125e-06s
INFO | --- Analysis for traffic-scotland took 12.656059503555298s
Availability | SPARQL endpoint availability check for Transparency International Linked Data took 0.5064136981964111s
Availability | VoID file availability check for Transparency International Linked Data took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for Transparency International Linked Data took 0.2736365795135498s
Reputation | Calculation of the PageRank for Transparency International Linked Data took 0.0201723575592041s
Interlinking | Calculation of Degree of Connection for Transparency International Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Transparency International Linked Data took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Transparency International Linked Data took 0.00010204315185546875s
Believability | Calculation of trust value for Transparency International Linked Data took 4.76837158203125e-06s
INFO | --- Analysis for transparency-linked-data took 2.958930730819702s
Availability | SPARQL endpoint availability check for transport.data.gov.uk took 0.6823825836181641s
Availability | VoID file availability check for transport.data.gov.uk took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for transport.data.gov.uk took 0.2655375003814697s
Reputation | Calculation of the PageRank for transport.data.gov.uk took 0.020592451095581055s
Interlinking | Calculation of Degree of Connection for transport.data.gov.uk took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for transport.data.gov.uk took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for transport.data.gov.uk took 9.274482727050781e-05s
Believability | Calculation of trust value for transport.data.gov.uk took 4.291534423828125e-06s
INFO | --- Analysis for transport-data-gov-uk took 3.9645349979400635s
Availability | SPARQL endpoint availability check for OpenUpLabs Transport took 4.1484832763671875e-05s
Availability | VoID file availability check for OpenUpLabs Transport took 0.0007953643798828125s
Completeness | Calculation of interlinking completeness for OpenUpLabs Transport took 0.2529182434082031s
Reputation | Calculation of the PageRank for OpenUpLabs Transport took 0.020732879638671875s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Transport took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Transport took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Transport took 3.075599670410156e-05s
Believability | Calculation of trust value for OpenUpLabs Transport took 8.344650268554688e-06s
INFO | --- Analysis for transport-openuplabs took 3.0289697647094727s
Availability | SPARQL endpoint availability check for Trelios took 4.649162292480469e-05s
Availability | VoID file availability check for Trelios took 0.00028777122497558594s
Completeness | Calculation of interlinking completeness for Trelios took 0.29685163497924805s
Reputation | Calculation of the PageRank for Trelios took 0.020700693130493164s
Interlinking | Calculation of Degree of Connection for Trelios took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Trelios took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Trelios took 1.2874603271484375e-05s
Believability | Calculation of trust value for Trelios took 7.867813110351562e-06s
INFO | --- Analysis for Trelios took 2.8822293281555176s
Availability | SPARQL endpoint availability check for Twarql took 10.517160177230835s
Availability | VoID file availability check for Twarql took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for Twarql took 0.27379631996154785s
Reputation | Calculation of the PageRank for Twarql took 0.02025127410888672s
Interlinking | Calculation of Degree of Connection for Twarql took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Twarql took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Twarql took 6.580352783203125e-05s
Believability | Calculation of trust value for Twarql took 7.62939453125e-06s
INFO | --- Analysis for twarql took 12.889708042144775s
Availability | SPARQL endpoint availability check for TWC Data-gov took 4.1484832763671875e-05s
Availability | VoID file availability check for TWC Data-gov took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for TWC Data-gov took 0.27079033851623535s
Reputation | Calculation of the PageRank for TWC Data-gov took 0.021887540817260742s
Interlinking | Calculation of Degree of Connection for TWC Data-gov took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for TWC Data-gov took 0.0009942054748535156s
Interlinking | Calculation of Clustering coefficient for TWC Data-gov took 3.504753112792969e-05s
Believability | Calculation of trust value for TWC Data-gov took 4.76837158203125e-06s
INFO | --- Analysis for twc-data-gov took 2.522186040878296s
Availability | SPARQL endpoint availability check for Tetherless World Constellation Demonstrations took 7.152557373046875e-05s
Availability | VoID file availability check for Tetherless World Constellation Demonstrations took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for Tetherless World Constellation Demonstrations took 0.25203585624694824s
Reputation | Calculation of the PageRank for Tetherless World Constellation Demonstrations took 0.02028656005859375s
Interlinking | Calculation of Degree of Connection for Tetherless World Constellation Demonstrations took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Tetherless World Constellation Demonstrations took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Tetherless World Constellation Demonstrations took 2.7179718017578125e-05s
Believability | Calculation of trust value for Tetherless World Constellation Demonstrations took 7.152557373046875e-06s
INFO | --- Analysis for twc-demos took 3.3753395080566406s
Availability | SPARQL endpoint availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.13898849487304688s
Availability | VoID file availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.0005888938903808594s
Completeness | Calculation of interlinking completeness for HealthData.gov Platform (HDP) on the Semantic Web took 0.2696542739868164s
Reputation | Calculation of the PageRank for HealthData.gov Platform (HDP) on the Semantic Web took 0.02020549774169922s
Interlinking | Calculation of Degree of Connection for HealthData.gov Platform (HDP) on the Semantic Web took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for HealthData.gov Platform (HDP) on the Semantic Web took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for HealthData.gov Platform (HDP) on the Semantic Web took 2.765655517578125e-05s
Believability | Calculation of trust value for HealthData.gov Platform (HDP) on the Semantic Web took 4.5299530029296875e-06s
INFO | --- Analysis for twc-healthdata took 16.932576656341553s
Availability | SPARQL endpoint availability check for Instance Hub (all) took 3.4957709312438965s
Availability | VoID file availability check for Instance Hub (all) took 0.0007033348083496094s
Completeness | Calculation of interlinking completeness for Instance Hub (all) took 0.36916279792785645s
Reputation | Calculation of the PageRank for Instance Hub (all) took 0.021039962768554688s
Interlinking | Calculation of Degree of Connection for Instance Hub (all) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Instance Hub (all) took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Instance Hub (all) took 8.797645568847656e-05s
Believability | Calculation of trust value for Instance Hub (all) took 7.3909759521484375e-06s
INFO | --- Analysis for twc-hub took 98.04122638702393s
Availability | SPARQL endpoint availability check for IEEE VIS Source Data took 0.14075493812561035s
Availability | VoID file availability check for IEEE VIS Source Data took 0.0002849102020263672s
Completeness | Calculation of interlinking completeness for IEEE VIS Source Data took 0.33023619651794434s
Reputation | Calculation of the PageRank for IEEE VIS Source Data took 0.02056884765625s
Interlinking | Calculation of Degree of Connection for IEEE VIS Source Data took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for IEEE VIS Source Data took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for IEEE VIS Source Data took 0.00011348724365234375s
Believability | Calculation of trust value for IEEE VIS Source Data took 7.152557373046875e-06s
INFO | --- Analysis for twc-ieeevis took 159.61447834968567s
Availability | SPARQL endpoint availability check for TWC: Linking Open Government Data took 4.1484832763671875e-05s
Availability | VoID file availability check for TWC: Linking Open Government Data took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for TWC: Linking Open Government Data took 0.2887229919433594s
Reputation | Calculation of the PageRank for TWC: Linking Open Government Data took 0.020451068878173828s
Interlinking | Calculation of Degree of Connection for TWC: Linking Open Government Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for TWC: Linking Open Government Data took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for TWC: Linking Open Government Data took 8.940696716308594e-05s
Believability | Calculation of trust value for TWC: Linking Open Government Data took 5.245208740234375e-06s
INFO | --- Analysis for twc-logd took 3.7784111499786377s
Availability | SPARQL endpoint availability check for twc-opendap took 0.1373133659362793s
Availability | VoID file availability check for twc-opendap took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for twc-opendap took 0.7738862037658691s
Reputation | Calculation of the PageRank for twc-opendap took 0.020375490188598633s
Interlinking | Calculation of Degree of Connection for twc-opendap took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for twc-opendap took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for twc-opendap took 6.556510925292969e-05s
Believability | Calculation of trust value for twc-opendap took 7.152557373046875e-06s
INFO | --- Analysis for twc-opendap took 57.042739152908325s
Availability | SPARQL endpoint availability check for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 3.933906555175781e-05s
Availability | VoID file availability check for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.6561028957366943s
Reputation | Calculation of the PageRank for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.020086288452148438s
Interlinking | Calculation of Degree of Connection for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 2.6464462280273438e-05s
Believability | Calculation of trust value for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 8.58306884765625e-06s
INFO | --- Analysis for tweetskb took 7.2498204708099365s
Availability | SPARQL endpoint availability check for Twitter Linked Data Service took 4.267692565917969e-05s
Availability | VoID file availability check for Twitter Linked Data Service took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for Twitter Linked Data Service took 0.3201780319213867s
Reputation | Calculation of the PageRank for Twitter Linked Data Service took 0.020484209060668945s
Interlinking | Calculation of Degree of Connection for Twitter Linked Data Service took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Twitter Linked Data Service took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Twitter Linked Data Service took 2.8371810913085938e-05s
Believability | Calculation of trust value for Twitter Linked Data Service took 6.9141387939453125e-06s
INFO | --- Analysis for twitter-lids took 4.259681224822998s
Availability | SPARQL endpoint availability check for typepad took 4.076957702636719e-05s
Availability | VoID file availability check for typepad took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for typepad took 0.627469539642334s
Reputation | Calculation of the PageRank for typepad took 0.020612716674804688s
Interlinking | Calculation of Degree of Connection for typepad took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for typepad took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for typepad took 5.054473876953125e-05s
Believability | Calculation of trust value for typepad took 7.62939453125e-06s
INFO | --- Analysis for typepad took 4.483959197998047s
Availability | SPARQL endpoint availability check for Linked Data Service der Universitätsbibliothek Mannheim took 1.0294826030731201s
Availability | VoID file availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.0005910396575927734s
Completeness | Calculation of interlinking completeness for Linked Data Service der Universitätsbibliothek Mannheim took 0.3242788314819336s
Reputation | Calculation of the PageRank for Linked Data Service der Universitätsbibliothek Mannheim took 0.0203702449798584s
Interlinking | Calculation of Degree of Connection for Linked Data Service der Universitätsbibliothek Mannheim took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Linked Data Service der Universitätsbibliothek Mannheim took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Linked Data Service der Universitätsbibliothek Mannheim took 3.9577484130859375e-05s
Believability | Calculation of trust value for Linked Data Service der Universitätsbibliothek Mannheim took 6.4373016357421875e-06s
INFO | --- Analysis for ub-mannheim-linked-data took 9.038173913955688s
Availability | SPARQL endpoint availability check for Uberblic.org took 0.0789942741394043s
Availability | VoID file availability check for Uberblic.org took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for Uberblic.org took 0.3091421127319336s
Reputation | Calculation of the PageRank for Uberblic.org took 0.02067112922668457s
Interlinking | Calculation of Degree of Connection for Uberblic.org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Uberblic.org took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Uberblic.org took 0.00010323524475097656s
Believability | Calculation of trust value for Uberblic.org took 7.62939453125e-06s
INFO | --- Analysis for uberblic took 3.2205240726470947s
Availability | SPARQL endpoint availability check for UDante in LiLa took 0.5718388557434082s
Availability | VoID file availability check for UDante in LiLa took 0.0013096332550048828s
Completeness | Calculation of interlinking completeness for UDante in LiLa took 0.3071269989013672s
Reputation | Calculation of the PageRank for UDante in LiLa took 0.02092719078063965s
Interlinking | Calculation of Degree of Connection for UDante in LiLa took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for UDante in LiLa took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for UDante in LiLa took 3.9577484130859375e-05s
Believability | Calculation of trust value for UDante in LiLa took 6.198883056640625e-06s
INFO | --- Analysis for UDante took 4.520388126373291s
Availability | SPARQL endpoint availability check for Unified Foundational Ontology took 1.2186996936798096s
Availability | VoID file availability check for Unified Foundational Ontology took 0.0006678104400634766s
Completeness | Calculation of interlinking completeness for Unified Foundational Ontology took 0.3250772953033447s
Reputation | Calculation of the PageRank for Unified Foundational Ontology took 0.020420312881469727s
Interlinking | Calculation of Degree of Connection for Unified Foundational Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Unified Foundational Ontology took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Unified Foundational Ontology took 2.9802322387695312e-05s
Believability | Calculation of trust value for Unified Foundational Ontology took 6.67572021484375e-06s
INFO | --- Analysis for ufo took 5.915639638900757s
Availability | SPARQL endpoint availability check for Uganda Disasters took 4.220008850097656e-05s
Availability | VoID file availability check for Uganda Disasters took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for Uganda Disasters took 0.3193063735961914s
Reputation | Calculation of the PageRank for Uganda Disasters took 0.0205838680267334s
Interlinking | Calculation of Degree of Connection for Uganda Disasters took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Uganda Disasters took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Uganda Disasters took 4.673004150390625e-05s
Believability | Calculation of trust value for Uganda Disasters took 7.152557373046875e-06s
INFO | --- Analysis for Uganda-Disasters-rdf-data_ took 4.094713926315308s
Availability | SPARQL endpoint availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.16538310050964355s
Availability | VoID file availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.0004017353057861328s
Completeness | Calculation of interlinking completeness for UNESCO Institute for Statistics (UIS) Linked Data took 0.3237764835357666s
Reputation | Calculation of the PageRank for UNESCO Institute for Statistics (UIS) Linked Data took 0.02082681655883789s
Interlinking | Calculation of Degree of Connection for UNESCO Institute for Statistics (UIS) Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for UNESCO Institute for Statistics (UIS) Linked Data took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for UNESCO Institute for Statistics (UIS) Linked Data took 0.00012731552124023438s
Believability | Calculation of trust value for UNESCO Institute for Statistics (UIS) Linked Data took 9.298324584960938e-06s
INFO | --- Analysis for uis-linked-data took 7.40702223777771s
Availability | SPARQL endpoint availability check for UK Legislation took 4.0531158447265625e-05s
Availability | VoID file availability check for UK Legislation took 0.0010874271392822266s
Completeness | Calculation of interlinking completeness for UK Legislation took 0.31856393814086914s
Reputation | Calculation of the PageRank for UK Legislation took 0.020517826080322266s
Interlinking | Calculation of Degree of Connection for UK Legislation took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UK Legislation took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for UK Legislation took 8.869171142578125e-05s
Believability | Calculation of trust value for UK Legislation took 4.0531158447265625e-06s
INFO | --- Analysis for uk-legislation-api took 3.666651964187622s
Availability | SPARQL endpoint availability check for UK Postcodes took 4.124641418457031e-05s
Availability | VoID file availability check for UK Postcodes took 0.0004298686981201172s
Completeness | Calculation of interlinking completeness for UK Postcodes took 0.2908055782318115s
Reputation | Calculation of the PageRank for UK Postcodes took 0.02020406723022461s
Interlinking | Calculation of Degree of Connection for UK Postcodes took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for UK Postcodes took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for UK Postcodes took 5.435943603515625e-05s
Believability | Calculation of trust value for UK Postcodes took 8.58306884765625e-06s
INFO | --- Analysis for uk-postcodes took 4.427855491638184s
Availability | SPARQL endpoint availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 4.172325134277344e-05s
Availability | VoID file availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0004978179931640625s
Completeness | Calculation of interlinking completeness for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.29081130027770996s
Reputation | Calculation of the PageRank for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.020594120025634766s
Interlinking | Calculation of Degree of Connection for UMBEL (Upper Mapping and Binding Exchange Layer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.00013327598571777344s
Believability | Calculation of trust value for UMBEL (Upper Mapping and Binding Exchange Layer) took 8.106231689453125e-06s
INFO | --- Analysis for umbel took 6.795753479003906s
Availability | SPARQL endpoint availability check for UMTHES took 4.220008850097656e-05s
Availability | VoID file availability check for UMTHES took 0.0003523826599121094s
Completeness | Calculation of interlinking completeness for UMTHES took 1.3544354438781738s
Reputation | Calculation of the PageRank for UMTHES took 0.02096867561340332s
Interlinking | Calculation of Degree of Connection for UMTHES took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for UMTHES took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for UMTHES took 4.2438507080078125e-05s
Believability | Calculation of trust value for UMTHES took 6.4373016357421875e-06s
INFO | --- Analysis for umthes took 5.1666059494018555s
Availability | SPARQL endpoint availability check for UN Hazardous Materials Numbers took 1.6309821605682373s
Availability | VoID file availability check for UN Hazardous Materials Numbers took 0.0007848739624023438s
Completeness | Calculation of interlinking completeness for UN Hazardous Materials Numbers took 0.2861778736114502s
Reputation | Calculation of the PageRank for UN Hazardous Materials Numbers took 0.02056884765625s
Interlinking | Calculation of Degree of Connection for UN Hazardous Materials Numbers took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for UN Hazardous Materials Numbers took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for UN Hazardous Materials Numbers took 3.0517578125e-05s
Believability | Calculation of trust value for UN Hazardous Materials Numbers took 4.76837158203125e-06s
INFO | --- Analysis for un-hazardous-numbers took 9.242838621139526s
Availability | SPARQL endpoint availability check for UNESCO Thesaurus took 3.9577484130859375e-05s
Availability | VoID file availability check for UNESCO Thesaurus took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for UNESCO Thesaurus took 0.3000600337982178s
Reputation | Calculation of the PageRank for UNESCO Thesaurus took 0.020563364028930664s
Interlinking | Calculation of Degree of Connection for UNESCO Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for UNESCO Thesaurus took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for UNESCO Thesaurus took 3.0279159545898438e-05s
Believability | Calculation of trust value for UNESCO Thesaurus took 5.7220458984375e-06s
INFO | --- Analysis for unesco-thesaurus took 5.7386369705200195s
Availability | SPARQL endpoint availability check for UNESCO Thesaurus took 4.124641418457031e-05s
Availability | VoID file availability check for UNESCO Thesaurus took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for UNESCO Thesaurus took 0.2929103374481201s
Reputation | Calculation of the PageRank for UNESCO Thesaurus took 0.02051258087158203s
Interlinking | Calculation of Degree of Connection for UNESCO Thesaurus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for UNESCO Thesaurus took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for UNESCO Thesaurus took 3.0040740966796875e-05s
Believability | Calculation of trust value for UNESCO Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for unescothes took 4.3402862548828125s
Availability | SPARQL endpoint availability check for UniProt took 1.489800214767456s
Availability | VoID file availability check for UniProt took 0.0005745887756347656s
Extra | Recovery of all triples for UniProt took 14.028618335723877s
Performance | Total latancy measurement for UniProt took 2.7053611278533936s
Amount of data | Number of triples check for UniProt took 0.2180938720703125s
Interoperability | New terms check for UniProt took 1.3942582607269287s
Versatility | Languages check for UniProt took 300.1055543422699s
Interpretability | Number of blank nodes check for UniProt took 0.4081263542175293s
Interpretability | RDF structures check for UniProt took 0.14544367790222168s
Versatility | Serialization formats check for UniProt took 0.10924315452575684s
Availability | RDF dump link check for UniProt took 0.08812665939331055s
License | MR license check for UniProt took 0.09962153434753418s
License | HR license check for UniProt took 300.1377339363098s
Amount of data | Number of property check for UniProt took 0.15267610549926758s
Understandability | Number of label check for UniProt took 49.12412977218628s
Understandability | URI regex check for UniProt took 0.18325233459472656s
Understandability | Vocabs check for UniProt took 0.08815264701843262s
Verifiability | Authors check for UniProt took 0.14391350746154785s
Verifiability | Publishers check for UniProt took 0.11573052406311035s
Performance | Throughput check for UniProt took 15.115096092224121s
Amount of data | Check the number of entities for UniProt took 8.058547973632812e-05s
Verifiability | Contribs. check for UniProt took 0.08984756469726562s
Interlinking | sameAs chians check for UniProt took 0.09685325622558594s
Interlinking | skos check for UniProt took 0.14929986000061035s
Interlinking | skos check for UniProt took 0.08474969863891602s
Timeliness | dataset update frequency check for UniProt took 0.10391831398010254s
Currency | Creation date check for UniProt took 0.6015193462371826s
Currency | Modification date check for UniProt took 0.23322272300720215s
Rep.Conc. | URIs length for UniProt took 160.31499695777893s
Interoperability | New vocabularies check for UniProt took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for UniProt took 0.12894058227539062s
Accuracy | Check Functional Property for UniProt took 0.13190102577209473s
Accuracy | Check Inverse Functional Property for UniProt took 0.08980226516723633s
Accuracy | Check Empty annotation labels for UniProt took 16.5560302734375s
Accuracy | Check White space in annotation for UniProt took 2.5022358894348145s
Accuracy | Check Datatype consistency for UniProt took 7.239279270172119s
Consistency | Disjoint class check for UniProt took 0.09162020683288574s
Consistency | Check Misplaced properties for UniProt took 3.5940914154052734s
Consistency | Check Ontology hijacking for UniProt took 7.6591408252716064s
Consistency | Check Invalid usage of undefined classes for UniProt took 19119.897557497025s
Consistency | Check Invalid usage of undefined properties for UniProt took 1.6706485748291016s
Conciseness | Check Extensional conciseness for UniProt took 2.6664955615997314s
Conciseness | Check Intensional conciseness for UniProt took 0.12074780464172363s
Security | Sign check for UniProt took 0.11772751808166504s
Availability | Check URIs Dereferenciability for UniProt took 5.723750829696655s
Completeness | Calculation of interlinking completeness for UniProt took 1.9605627059936523s
Reputation | Calculation of the PageRank for UniProt took 0.021410703659057617s
Interlinking | Calculation of Degree of Connection for UniProt took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for UniProt took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for UniProt took 4.982948303222656e-05s
Interoperability | Check the re-using of existing vocabs for UniProt took 2.6226043701171875e-06s
Believability | Calculation of trust value for UniProt took 7.3909759521484375e-06s
INFO | --- Analysis for UniProt took 20400.433289289474s
Availability | SPARQL endpoint availability check for UniProt took 1.4864041805267334s
Availability | VoID file availability check for UniProt took 0.0006356239318847656s
Extra | Recovery of all triples for UniProt took 15.381278276443481s
Performance | Total latancy measurement for UniProt took 3.729343891143799s
Amount of data | Number of triples check for UniProt took 0.3478548526763916s
Versatility | Languages check for UniProt took 300.3123185634613s
Interpretability | Number of blank nodes check for UniProt took 0.637274980545044s
Security | Check HTTPS for UniProt took 1.3515524864196777s
Interpretability | RDF structures check for UniProt took 0.17904424667358398s
Versatility | Serialization formats check for UniProt took 0.5706453323364258s
Availability | RDF dump link check for UniProt took 0.17360329627990723s
License | MR license check for UniProt took 0.16655468940734863s
License | HR license check for UniProt took 0.1613619327545166s
Amount of data | Number of property check for UniProt took 0.16888904571533203s
Understandability | Number of label check for UniProt took 0.17252302169799805s
Understandability | URI regex check for UniProt took 0.32921409606933594s
Understandability | Vocabs check for UniProt took 0.15741562843322754s
Verifiability | Authors check for UniProt took 0.1751265525817871s
Verifiability | Publishers check for UniProt took 0.171478271484375s
Performance | Throughput check for UniProt took 18.07057023048401s
Amount of data | Check the number of entities for UniProt took 0.00011706352233886719s
Verifiability | Contribs. check for UniProt took 0.17664694786071777s
Interlinking | sameAs chians check for UniProt took 0.15479683876037598s
Interlinking | skos check for UniProt took 0.14899730682373047s
Interlinking | skos check for UniProt took 0.14917349815368652s
Timeliness | dataset update frequency check for UniProt took 0.15203166007995605s
Currency | Creation date check for UniProt took 0.3472592830657959s
Currency | Modification date check for UniProt took 0.33118724822998047s
Rep.Conc. | URIs length for UniProt took 136.44553232192993s
Interoperability | New vocabularies check for UniProt took 2.384185791015625e-07s
Consistency | Deprecated classes/propertiers check for UniProt took 0.1663682460784912s
Accuracy | Check Datatype consistency for UniProt took 7.393269777297974s
Consistency | Disjoint class check for UniProt took 0.16878318786621094s
Consistency | Check Ontology hijacking for UniProt took 0.1656343936920166s
Consistency | Check Invalid usage of undefined properties for UniProt took 1.6423630714416504s
Conciseness | Check Extensional conciseness for UniProt took 2.6937012672424316s
Security | Sign check for UniProt took 0.16816473007202148s
Availability | Check URIs Dereferenciability for UniProt took 3.8519153594970703s
Completeness | Calculation of interlinking completeness for UniProt took 0.8292357921600342s
Reputation | Calculation of the PageRank for UniProt took 0.020867109298706055s
Interlinking | Calculation of Degree of Connection for UniProt took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for UniProt took 4.9591064453125e-05s
Interoperability | Check the re-using of existing vocabs for UniProt took 1.1920928955078125e-06s
Believability | Calculation of trust value for UniProt took 1.2159347534179688e-05s
INFO | --- Analysis for uniprot took 1032.167752981186s
Availability | SPARQL endpoint availability check for UniProt citations took 3.9577484130859375e-05s
Availability | VoID file availability check for UniProt citations took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for UniProt citations took 0.7090082168579102s
Reputation | Calculation of the PageRank for UniProt citations took 0.020845651626586914s
Interlinking | Calculation of Degree of Connection for UniProt citations took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UniProt citations took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for UniProt citations took 3.0040740966796875e-05s
Believability | Calculation of trust value for UniProt citations took 5.9604644775390625e-06s
INFO | --- Analysis for uniprot-citations took 4.701958656311035s
Availability | SPARQL endpoint availability check for UniProt databases took 4.0531158447265625e-05s
Availability | VoID file availability check for UniProt databases took 0.0002346038818359375s
Completeness | Calculation of interlinking completeness for UniProt databases took 0.2699160575866699s
Reputation | Calculation of the PageRank for UniProt databases took 0.02068495750427246s
Interlinking | Calculation of Degree of Connection for UniProt databases took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for UniProt databases took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for UniProt databases took 2.956390380859375e-05s
Believability | Calculation of trust value for UniProt databases took 5.9604644775390625e-06s
INFO | --- Analysis for uniprot-databases took 4.257934093475342s
Availability | SPARQL endpoint availability check for uniprot-metadata took 4.1484832763671875e-05s
Availability | VoID file availability check for uniprot-metadata took 0.0003523826599121094s
Completeness | Calculation of interlinking completeness for uniprot-metadata took 0.2649059295654297s
Reputation | Calculation of the PageRank for uniprot-metadata took 0.02028942108154297s
Interlinking | Calculation of Degree of Connection for uniprot-metadata took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for uniprot-metadata took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for uniprot-metadata took 6.008148193359375e-05s
Believability | Calculation of trust value for uniprot-metadata took 6.4373016357421875e-06s
INFO | --- Analysis for uniprot-metadata took 4.274409294128418s
Availability | SPARQL endpoint availability check for UniProtKB Taxonomy took 4.8160552978515625e-05s
Availability | VoID file availability check for UniProtKB Taxonomy took 0.0002269744873046875s
Completeness | Calculation of interlinking completeness for UniProtKB Taxonomy took 0.25094175338745117s
Reputation | Calculation of the PageRank for UniProtKB Taxonomy took 0.020529985427856445s
Interlinking | Calculation of Degree of Connection for UniProtKB Taxonomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for UniProtKB Taxonomy took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for UniProtKB Taxonomy took 2.86102294921875e-05s
Believability | Calculation of trust value for UniProtKB Taxonomy took 6.9141387939453125e-06s
INFO | --- Analysis for uniprot-taxonomy took 2.852658271789551s
Availability | SPARQL endpoint availability check for UniProt UniParc took 4.076957702636719e-05s
Availability | VoID file availability check for UniProt UniParc took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for UniProt UniParc took 0.24913549423217773s
Reputation | Calculation of the PageRank for UniProt UniParc took 0.020220279693603516s
Interlinking | Calculation of Degree of Connection for UniProt UniParc took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for UniProt UniParc took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for UniProt UniParc took 2.7179718017578125e-05s
Believability | Calculation of trust value for UniProt UniParc took 5.7220458984375e-06s
INFO | --- Analysis for uniprot-uniparc took 2.9456257820129395s
Availability | SPARQL endpoint availability check for UniProt UniPathway took 4.100799560546875e-05s
Availability | VoID file availability check for UniProt UniPathway took 0.00027370452880859375s
Completeness | Calculation of interlinking completeness for UniProt UniPathway took 0.2572309970855713s
Reputation | Calculation of the PageRank for UniProt UniPathway took 0.020517349243164062s
Interlinking | Calculation of Degree of Connection for UniProt UniPathway took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for UniProt UniPathway took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for UniProt UniPathway took 2.765655517578125e-05s
Believability | Calculation of trust value for UniProt UniPathway took 6.4373016357421875e-06s
INFO | --- Analysis for uniprot-unipathway took 3.3792717456817627s
Availability | SPARQL endpoint availability check for UniProtKB took 1.3202803134918213s
Availability | VoID file availability check for UniProtKB took 0.0005776882171630859s
Extra | Recovery of all triples for UniProtKB took 11.761557340621948s
Performance | Total latancy measurement for UniProtKB took 3.210930585861206s
Amount of data | Number of triples check for UniProtKB took 0.17906761169433594s
Interoperability | New terms check for UniProtKB took 1.4461431503295898s
Versatility | Languages check for UniProtKB took 300.1497950553894s
Interpretability | Number of blank nodes check for UniProtKB took 0.40102386474609375s
Interpretability | RDF structures check for UniProtKB took 0.15970730781555176s
Versatility | Serialization formats check for UniProtKB took 0.10191059112548828s
Availability | RDF dump link check for UniProtKB took 0.09116435050964355s
License | MR license check for UniProtKB took 0.1035304069519043s
License | HR license check for UniProtKB took 300.11825227737427s
Amount of data | Number of property check for UniProtKB took 0.19916343688964844s
Understandability | Number of label check for UniProtKB took 45.073078870773315s
Understandability | URI regex check for UniProtKB took 0.17610669136047363s
Understandability | Vocabs check for UniProtKB took 0.15030121803283691s
Verifiability | Authors check for UniProtKB took 0.09652090072631836s
Verifiability | Publishers check for UniProtKB took 0.10237789154052734s
Performance | Throughput check for UniProtKB took 13.854477643966675s
Amount of data | Check the number of entities for UniProtKB took 7.176399230957031e-05s
Verifiability | Contribs. check for UniProtKB took 0.13060379028320312s
Interlinking | sameAs chians check for UniProtKB took 0.08307671546936035s
Interlinking | skos check for UniProtKB took 0.15877294540405273s
Interlinking | skos check for UniProtKB took 0.08519864082336426s
Timeliness | dataset update frequency check for UniProtKB took 0.14924216270446777s
Currency | Creation date check for UniProtKB took 0.19601154327392578s
Currency | Modification date check for UniProtKB took 0.18640565872192383s
Rep.Conc. | URIs length for UniProtKB took 139.00180649757385s
Interoperability | New vocabularies check for UniProtKB took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for UniProtKB took 0.08975481986999512s
Accuracy | Check Functional Property for UniProtKB took 0.08027768135070801s
Accuracy | Check Inverse Functional Property for UniProtKB took 0.09090304374694824s
Accuracy | Check Empty annotation labels for UniProtKB took 18.306391716003418s
Accuracy | Check White space in annotation for UniProtKB took 2.516123056411743s
Accuracy | Check Datatype consistency for UniProtKB took 7.21284818649292s
Consistency | Disjoint class check for UniProtKB took 0.10268902778625488s
Consistency | Check Misplaced properties for UniProtKB took 3.8110508918762207s
Consistency | Check Ontology hijacking for UniProtKB took 8.218812704086304s
Consistency | Check Invalid usage of undefined classes for UniProtKB took 18667.40372776985s
Consistency | Check Invalid usage of undefined properties for UniProtKB took 1.749220371246338s
Conciseness | Check Extensional conciseness for UniProtKB took 2.670562982559204s
Conciseness | Check Intensional conciseness for UniProtKB took 0.16817522048950195s
Security | Sign check for UniProtKB took 0.08679318428039551s
Availability | Check URIs Dereferenciability for UniProtKB took 4.5066728591918945s
Completeness | Calculation of interlinking completeness for UniProtKB took 1.5409464836120605s
Reputation | Calculation of the PageRank for UniProtKB took 0.021077394485473633s
Interlinking | Calculation of Degree of Connection for UniProtKB took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for UniProtKB took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for UniProtKB took 6.723403930664062e-05s
Interoperability | Check the re-using of existing vocabs for UniProtKB took 2.1457672119140625e-06s
Believability | Calculation of trust value for UniProtKB took 7.3909759521484375e-06s
INFO | --- Analysis for uniprotkb took 19925.52190876007s
Availability | SPARQL endpoint availability check for UniProt UniRef took 6.246566772460938e-05s
Availability | VoID file availability check for UniProt UniRef took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for UniProt UniRef took 0.7059438228607178s
Reputation | Calculation of the PageRank for UniProt UniRef took 0.020634889602661133s
Interlinking | Calculation of Degree of Connection for UniProt UniRef took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for UniProt UniRef took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for UniProt UniRef took 3.504753112792969e-05s
Believability | Calculation of trust value for UniProt UniRef took 5.7220458984375e-06s
INFO | --- Analysis for uniref took 6.079731225967407s
Availability | SPARQL endpoint availability check for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 4.124641418457031e-05s
Availability | VoID file availability check for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.00022912025451660156s
Completeness | Calculation of interlinking completeness for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.6902108192443848s
Reputation | Calculation of the PageRank for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.020140886306762695s
Interlinking | Calculation of Degree of Connection for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 2.765655517578125e-05s
Believability | Calculation of trust value for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 6.4373016357421875e-06s
INFO | --- Analysis for unistat-kis-2011-2012-in-rdf-key-information-set-uk-universities took 4.2070472240448s
Availability | SPARQL endpoint availability check for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 4.124641418457031e-05s
Availability | VoID file availability check for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.26937437057495117s
Reputation | Calculation of the PageRank for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.020406007766723633s
Interlinking | Calculation of Degree of Connection for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 2.7179718017578125e-05s
Believability | Calculation of trust value for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 6.198883056640625e-06s
INFO | --- Analysis for unistat-kis-in-rdf-key-information-set-uk-universities took 2.8800158500671387s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek took 0.0006618499755859375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek took 0.24457740783691406s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek took 0.020572900772094727s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek took 3.5762786865234375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek took 5.9604644775390625e-06s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek took 14.294691562652588s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 4.601478576660156e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.000621795654296875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.25844335556030273s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.020259380340576172s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek-PROIEL took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek-PROIEL took 3.719329833984375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek-PROIEL took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek-proiel took 3.5985143184661865s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Arabic took 4.4345855712890625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Arabic took 0.0006403923034667969s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Arabic took 0.24339818954467773s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Arabic took 0.02026844024658203s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Arabic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Arabic took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Arabic took 3.743171691894531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Arabic took 5.7220458984375e-06s
INFO | --- Analysis for universal-dependencies-treebank-arabic took 13.125154733657837s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Basque took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Basque took 0.0008695125579833984s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Basque took 0.2748570442199707s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Basque took 0.0203855037689209s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Basque took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Basque took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Basque took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Basque took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-basque took 13.218415021896362s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Bulgarian took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Bulgarian took 0.0006866455078125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Bulgarian took 0.2935183048248291s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Bulgarian took 0.020294666290283203s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Bulgarian took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Bulgarian took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Bulgarian took 3.743171691894531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Bulgarian took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-bulgarian took 13.233003616333008s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Catalan took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Catalan took 0.0006525516510009766s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Catalan took 0.28690123558044434s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Catalan took 0.02050042152404785s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Catalan took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Catalan took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Catalan took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Catalan took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-catalan took 13.200045108795166s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Chinese took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Chinese took 0.0006375312805175781s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Chinese took 0.27281713485717773s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Chinese took 0.020364046096801758s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Chinese took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Chinese took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Chinese took 3.719329833984375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Chinese took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-chinese took 4.1813390254974365s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Coptic took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Coptic took 0.0006687641143798828s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Coptic took 0.277057409286499s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Coptic took 0.020181655883789062s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Coptic took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Coptic took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Coptic took 3.5762786865234375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Coptic took 6.4373016357421875e-06s
INFO | --- Analysis for universal-dependencies-treebank-coptic took 13.722287893295288s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Croatian took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Croatian took 0.0006246566772460938s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Croatian took 0.25011634826660156s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Croatian took 0.020318031311035156s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Croatian took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Croatian took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Croatian took 3.6716461181640625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Croatian took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-croatian took 13.173933744430542s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech took 0.0006902217864990234s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech took 0.24690580368041992s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech took 0.020793676376342773s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech took 0.0009365081787109375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-czech took 13.864156723022461s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CAC took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CAC took 0.0006375312805175781s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CAC took 0.2650158405303955s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CAC took 0.020316600799560547s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CAC took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CAC took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CAC took 3.695487976074219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CAC took 5.4836273193359375e-06s
INFO | --- Analysis for universal-dependencies-treebank-czech-cac took 12.964607238769531s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CLTT took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CLTT took 0.0007166862487792969s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CLTT took 0.26392078399658203s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CLTT took 0.02069854736328125s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CLTT took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CLTT took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CLTT took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CLTT took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-czech-cltt took 13.054636478424072s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Danish took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Danish took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Danish took 0.27631545066833496s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Danish took 0.031191587448120117s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Danish took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Danish took 0.001508474349975586s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Danish took 6.985664367675781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Danish took 9.5367431640625e-06s
INFO | --- Analysis for universal-dependencies-treebank-danish took 3.604931116104126s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch took 0.0006299018859863281s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch took 0.2703986167907715s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch took 0.0205380916595459s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch took 3.6716461181640625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch took 5.7220458984375e-06s
INFO | --- Analysis for universal-dependencies-treebank-dutch took 13.145194053649902s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch-LassySmall took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch-LassySmall took 0.000759124755859375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch-LassySmall took 0.25200986862182617s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch-LassySmall took 0.020405292510986328s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch-LassySmall took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch-LassySmall took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch-LassySmall took 4.4345855712890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch-LassySmall took 9.298324584960938e-06s
INFO | --- Analysis for universal-dependencies-treebank-dutch-lassysmall took 13.191022157669067s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English took 0.0006432533264160156s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English took 0.27368617057800293s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English took 0.02041172981262207s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-english took 13.257571697235107s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-ESL took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-ESL took 0.00067138671875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-ESL took 0.2629683017730713s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-ESL took 0.020289897918701172s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-ESL took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-ESL took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-ESL took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-ESL took 6.198883056640625e-06s
INFO | --- Analysis for universal-dependencies-treebank-english-esl took 12.964065551757812s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-LinES took 7.128715515136719e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-LinES took 0.0007264614105224609s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-LinES took 0.3472635746002197s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-LinES took 0.02039170265197754s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-LinES took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-LinES took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-LinES took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-LinES took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-english-lines took 13.135451793670654s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Estonian took 4.4345855712890625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Estonian took 0.0007266998291015625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Estonian took 0.2634403705596924s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Estonian took 0.020441293716430664s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Estonian took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Estonian took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Estonian took 4.220008850097656e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Estonian took 6.4373016357421875e-06s
INFO | --- Analysis for universal-dependencies-treebank-estonian took 13.20336627960205s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish took 0.0006282329559326172s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish took 0.2587764263153076s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish took 0.020527362823486328s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-finnish took 4.0791051387786865s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish-FTB took 8.273124694824219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish-FTB took 0.0006766319274902344s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish-FTB took 0.26873302459716797s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish-FTB took 0.020369291305541992s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish-FTB took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish-FTB took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish-FTB took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish-FTB took 5.9604644775390625e-06s
INFO | --- Analysis for universal-dependencies-treebank-finnish-ftb took 13.053041458129883s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank French took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank French took 0.0006577968597412109s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank French took 0.24302911758422852s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank French took 0.020437002182006836s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank French took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank French took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank French took 3.719329833984375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank French took 5.9604644775390625e-06s
INFO | --- Analysis for universal-dependencies-treebank-french took 13.576794624328613s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician took 0.0006604194641113281s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician took 0.27631711959838867s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician took 0.02038884162902832s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-galician took 13.170456886291504s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician-TreeGal took 4.482269287109375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician-TreeGal took 0.0006165504455566406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician-TreeGal took 0.2814328670501709s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician-TreeGal took 0.03080582618713379s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician-TreeGal took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician-TreeGal took 0.0014791488647460938s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician-TreeGal took 5.7697296142578125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician-TreeGal took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-galician-treegal took 3.769822835922241s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank German took 5.221366882324219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank German took 0.00037550926208496094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank German took 0.2762949466705322s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank German took 0.020989418029785156s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank German took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank German took 0.0008256435394287109s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank German took 4.363059997558594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank German took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-german took 3.9403600692749023s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Gothic took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Gothic took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Gothic took 0.307725191116333s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Gothic took 0.020604372024536133s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Gothic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Gothic took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Gothic took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Gothic took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-gothic took 3.542909622192383s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Greek took 4.5299530029296875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Greek took 0.0007562637329101562s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Greek took 0.2634117603302002s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Greek took 0.021459102630615234s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Greek took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Greek took 0.001001596450805664s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Greek took 4.673004150390625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Greek took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-greek took 3.5965075492858887s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hebrew took 4.458427429199219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hebrew took 0.0007786750793457031s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hebrew took 0.2979567050933838s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hebrew took 0.02049541473388672s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hebrew took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hebrew took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hebrew took 3.695487976074219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hebrew took 6.67572021484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-hebrew took 13.197831153869629s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hindi took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hindi took 0.0006964206695556641s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hindi took 0.27989768981933594s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hindi took 0.02034592628479004s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hindi took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hindi took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hindi took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hindi took 5.9604644775390625e-06s
INFO | --- Analysis for universal-dependencies-treebank-hindi took 13.334701776504517s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hungarian took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hungarian took 0.0005664825439453125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hungarian took 0.27881717681884766s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hungarian took 0.021296262741088867s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hungarian took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hungarian took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hungarian took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hungarian took 5.9604644775390625e-06s
INFO | --- Analysis for universal-dependencies-treebank-hungarian took 3.7262423038482666s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Indonesian took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Indonesian took 0.0007274150848388672s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Indonesian took 0.26263952255249023s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Indonesian took 0.020231008529663086s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Indonesian took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Indonesian took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Indonesian took 3.790855407714844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Indonesian took 5.7220458984375e-06s
INFO | --- Analysis for universal-dependencies-treebank-indonesian took 13.237343072891235s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Irish took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Irish took 0.00066375732421875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Irish took 0.27020788192749023s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Irish took 0.02025890350341797s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Irish took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Irish took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Irish took 3.790855407714844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Irish took 6.198883056640625e-06s
INFO | --- Analysis for universal-dependencies-treebank-irish took 3.9309442043304443s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Italian took 4.3392181396484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Italian took 0.0007741451263427734s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Italian took 0.298764705657959s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Italian took 0.020502567291259766s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Italian took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Italian took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Italian took 4.553794860839844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Italian took 5.9604644775390625e-06s
INFO | --- Analysis for universal-dependencies-treebank-italian took 13.29682970046997s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese took 0.0006546974182128906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese took 0.2856152057647705s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese took 0.020374774932861328s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese took 6.4373016357421875e-06s
INFO | --- Analysis for universal-dependencies-treebank-japanese took 13.226056814193726s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese-KTC took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese-KTC took 0.0006525516510009766s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese-KTC took 0.256633996963501s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese-KTC took 0.020318031311035156s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese-KTC took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese-KTC took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese-KTC took 3.790855407714844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese-KTC took 5.9604644775390625e-06s
INFO | --- Analysis for universal-dependencies-treebank-japanese-ktc took 3.8384385108947754s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Kazakh took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Kazakh took 0.0006756782531738281s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Kazakh took 0.2652168273925781s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Kazakh took 0.02039313316345215s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Kazakh took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Kazakh took 0.0007815361022949219s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Kazakh took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Kazakh took 5.9604644775390625e-06s
INFO | --- Analysis for universal-dependencies-treebank-kazakh took 13.214428901672363s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin took 0.2678074836730957s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin took 0.02016162872314453s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin took 3.743171691894531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin took 6.67572021484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin took 3.652106761932373s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-ITTB took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-ITTB took 0.0007169246673583984s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-ITTB took 0.26391172409057617s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-ITTB took 0.020433425903320312s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-ITTB took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-ITTB took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-ITTB took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-ITTB took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin-ittb took 13.032296895980835s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-PROIEL took 4.482269287109375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-PROIEL took 0.0008842945098876953s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-PROIEL took 0.26996803283691406s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-PROIEL took 0.02053093910217285s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-PROIEL took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-PROIEL took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-PROIEL took 4.291534423828125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-PROIEL took 6.198883056640625e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin-proiel took 12.956342935562134s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latvian took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latvian took 0.0007045269012451172s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latvian took 0.26247429847717285s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latvian took 0.02051258087158203s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latvian took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latvian took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latvian took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latvian took 6.4373016357421875e-06s
INFO | --- Analysis for universal-dependencies-treebank-latvian took 13.147355318069458s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Norwegian took 5.6743621826171875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Norwegian took 0.0006990432739257812s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Norwegian took 0.28813982009887695s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Norwegian took 0.020453453063964844s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Norwegian took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Norwegian took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Norwegian took 3.743171691894531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Norwegian took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-norwegian took 13.036283254623413s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Old_Church_Slavonic took 4.3392181396484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Old_Church_Slavonic took 0.0006887912750244141s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Old_Church_Slavonic took 0.25145459175109863s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Old_Church_Slavonic took 0.020508289337158203s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Old_Church_Slavonic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Old_Church_Slavonic took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Old_Church_Slavonic took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Old_Church_Slavonic took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-old-church-slavonic took 13.156605005264282s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Persian took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Persian took 0.0007040500640869141s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Persian took 0.2775566577911377s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Persian took 0.02032613754272461s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Persian took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Persian took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Persian took 4.291534423828125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Persian took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-persian took 3.6915321350097656s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Polish took 6.628036499023438e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Polish took 0.0007729530334472656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Polish took 0.2793850898742676s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Polish took 0.020421266555786133s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Polish took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Polish took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Polish took 3.790855407714844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Polish took 6.67572021484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-polish took 13.28000545501709s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese took 0.00074005126953125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese took 0.2622702121734619s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese took 0.02052164077758789s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese took 3.838539123535156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese took 6.67572021484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese took 12.7382652759552s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-Bosque took 4.458427429199219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-Bosque took 0.0006473064422607422s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-Bosque took 0.268571138381958s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-Bosque took 0.020174264907836914s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-Bosque took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-Bosque took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-Bosque took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-Bosque took 6.4373016357421875e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-bosque took 12.985178709030151s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-BR took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-BR took 0.0007176399230957031s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-BR took 0.24530029296875s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-BR took 0.020424604415893555s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-BR took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-BR took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-BR took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-BR took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-br took 13.108577728271484s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0005726814270019531s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.28997159004211426s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.020467519760131836s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-romanian took 13.144558668136597s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian took 0.0006337165832519531s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian took 0.26331043243408203s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian took 0.020761489868164062s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian took 4.553794860839844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian took 6.198883056640625e-06s
INFO | --- Analysis for universal-dependencies-treebank-russian took 13.601977109909058s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian-SynTagRus took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian-SynTagRus took 0.0006685256958007812s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian-SynTagRus took 0.28366851806640625s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian-SynTagRus took 0.020153522491455078s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian-SynTagRus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian-SynTagRus took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian-SynTagRus took 3.838539123535156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian-SynTagRus took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-russian-syntagrus took 3.5517830848693848s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Sanskrit took 4.1484832763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Sanskrit took 0.0006914138793945312s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Sanskrit took 0.24841666221618652s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Sanskrit took 0.0203402042388916s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Sanskrit took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Sanskrit took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Sanskrit took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Sanskrit took 5.7220458984375e-06s
INFO | --- Analysis for universal-dependencies-treebank-sanskrit took 13.080281257629395s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovak took 5.650520324707031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovak took 0.0007078647613525391s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovak took 0.26897621154785156s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovak took 0.020450115203857422s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovak took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovak took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovak took 3.838539123535156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovak took 5.7220458984375e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovak took 13.173042297363281s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian took 0.0006384849548339844s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian took 0.27231359481811523s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian took 0.02042388916015625s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian took 5.245208740234375e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovenian took 13.279706716537476s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian-SST took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian-SST took 0.0007319450378417969s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian-SST took 0.2711496353149414s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian-SST took 0.02082204818725586s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian-SST took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian-SST took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian-SST took 4.649162292480469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian-SST took 5.7220458984375e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovenian-sst took 13.064302921295166s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish took 0.0006871223449707031s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish took 0.2621769905090332s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish took 0.020346403121948242s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-spanish took 13.20528244972229s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish-AnCora took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish-AnCora took 0.0006783008575439453s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish-AnCora took 0.2782413959503174s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish-AnCora took 0.020510196685791016s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish-AnCora took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish-AnCora took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish-AnCora took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish-AnCora took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-spanish-ancora took 13.260867834091187s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish took 0.0006129741668701172s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish took 0.2465527057647705s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish took 0.02029275894165039s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish took 3.838539123535156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-swedish took 3.5372438430786133s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish-LinES took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish-LinES took 0.0006511211395263672s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish-LinES took 0.26619744300842285s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish-LinES took 0.020435333251953125s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish-LinES took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish-LinES took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish-LinES took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish-LinES took 6.198883056640625e-06s
INFO | --- Analysis for universal-dependencies-treebank-swedish-lines took 3.375354528427124s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish_Sign_Language took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish_Sign_Language took 0.0006685256958007812s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish_Sign_Language took 0.27004456520080566s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish_Sign_Language took 0.020261764526367188s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish_Sign_Language took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish_Sign_Language took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish_Sign_Language took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish_Sign_Language took 5.245208740234375e-06s
INFO | --- Analysis for universal-dependencies-treebank-swedish-sign-language took 13.409347295761108s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Tamil took 4.601478576660156e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Tamil took 0.0007555484771728516s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Tamil took 0.246903657913208s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Tamil took 0.023754119873046875s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Tamil took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Tamil took 0.0016789436340332031s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Tamil took 6.508827209472656e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Tamil took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-tamil took 13.23615550994873s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Turkish took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Turkish took 0.0006506443023681641s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Turkish took 0.2654099464416504s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Turkish took 0.020389795303344727s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Turkish took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Turkish took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Turkish took 3.600120544433594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Turkish took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-turkish took 13.254418134689331s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ukrainian took 4.792213439941406e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ukrainian took 0.0007565021514892578s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ukrainian took 0.2933237552642822s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ukrainian took 0.020599365234375s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ukrainian took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ukrainian took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ukrainian took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ukrainian took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-ukrainian took 13.193138599395752s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Uyghur took 4.4345855712890625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Uyghur took 0.0007016658782958984s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Uyghur took 0.2671024799346924s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Uyghur took 0.02032637596130371s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Uyghur took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Uyghur took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Uyghur took 3.743171691894531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Uyghur took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-uyghur took 13.185768127441406s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Vietnamese took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Vietnamese took 0.0007162094116210938s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Vietnamese took 0.2782111167907715s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Vietnamese took 0.020868301391601562s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Vietnamese took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Vietnamese took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Vietnamese took 4.887580871582031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Vietnamese took 5.4836273193359375e-06s
INFO | --- Analysis for universal-dependencies-treebank-vietnamese took 13.637571573257446s
Availability | SPARQL endpoint availability check for Universidad de Cuenca - LinkedData took 4.363059997558594e-05s
Availability | VoID file availability check for Universidad de Cuenca - LinkedData took 0.0006215572357177734s
Completeness | Calculation of interlinking completeness for Universidad de Cuenca - LinkedData took 0.2897510528564453s
Reputation | Calculation of the PageRank for Universidad de Cuenca - LinkedData took 0.020940780639648438s
Interlinking | Calculation of Degree of Connection for Universidad de Cuenca - LinkedData took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universidad de Cuenca - LinkedData took 0.0008361339569091797s
Interlinking | Calculation of Clustering coefficient for Universidad de Cuenca - LinkedData took 7.128715515136719e-05s
Believability | Calculation of trust value for Universidad de Cuenca - LinkedData took 7.62939453125e-06s
INFO | --- Analysis for universidad-de-cuenca-linkeddata took 6.756901502609253s
Availability | SPARQL endpoint availability check for Universitat Pompeu Fabra - linked data took 5.125999450683594e-05s
Availability | VoID file availability check for Universitat Pompeu Fabra - linked data took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for Universitat Pompeu Fabra - linked data took 0.28974342346191406s
Reputation | Calculation of the PageRank for Universitat Pompeu Fabra - linked data took 0.020611047744750977s
Interlinking | Calculation of Degree of Connection for Universitat Pompeu Fabra - linked data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universitat Pompeu Fabra - linked data took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Universitat Pompeu Fabra - linked data took 2.6464462280273438e-05s
Believability | Calculation of trust value for Universitat Pompeu Fabra - linked data took 1.6927719116210938e-05s
INFO | --- Analysis for universitat-pompeu-fabra-linked-data took 3.013390302658081s
Availability | SPARQL endpoint availability check for University of Bristol took 4.076957702636719e-05s
Availability | VoID file availability check for University of Bristol took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for University of Bristol took 0.25515246391296387s
Reputation | Calculation of the PageRank for University of Bristol took 0.021167278289794922s
Interlinking | Calculation of Degree of Connection for University of Bristol took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for University of Bristol took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for University of Bristol took 3.1948089599609375e-05s
Believability | Calculation of trust value for University of Bristol took 7.3909759521484375e-06s
INFO | --- Analysis for university-of-bristol took 2.955699920654297s
Availability | SPARQL endpoint availability check for University of Plymouth Reading Lists took 4.2438507080078125e-05s
Availability | VoID file availability check for University of Plymouth Reading Lists took 0.0005605220794677734s
Completeness | Calculation of interlinking completeness for University of Plymouth Reading Lists took 0.27112436294555664s
Reputation | Calculation of the PageRank for University of Plymouth Reading Lists took 0.020672082901000977s
Interlinking | Calculation of Degree of Connection for University of Plymouth Reading Lists took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for University of Plymouth Reading Lists took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for University of Plymouth Reading Lists took 4.982948303222656e-05s
Believability | Calculation of trust value for University of Plymouth Reading Lists took 7.152557373046875e-06s
INFO | --- Analysis for university-plymouth-reading-lists took 2.984729766845703s
Availability | SPARQL endpoint availability check for University of Sussex Reading Lists took 4.8160552978515625e-05s
Availability | VoID file availability check for University of Sussex Reading Lists took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for University of Sussex Reading Lists took 0.29090070724487305s
Reputation | Calculation of the PageRank for University of Sussex Reading Lists took 0.02060246467590332s
Interlinking | Calculation of Degree of Connection for University of Sussex Reading Lists took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for University of Sussex Reading Lists took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for University of Sussex Reading Lists took 3.457069396972656e-05s
Believability | Calculation of trust value for University of Sussex Reading Lists took 6.9141387939453125e-06s
INFO | --- Analysis for university-sussex-reading-lists took 2.9901950359344482s
Availability | SPARQL endpoint availability check for UNODC - Statistics on criminal justice took 38.141488552093506s
Availability | VoID file availability check for UNODC - Statistics on criminal justice took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for UNODC - Statistics on criminal justice took 0.6965129375457764s
Reputation | Calculation of the PageRank for UNODC - Statistics on criminal justice took 0.02050614356994629s
Interlinking | Calculation of Degree of Connection for UNODC - Statistics on criminal justice took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UNODC - Statistics on criminal justice took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for UNODC - Statistics on criminal justice took 6.937980651855469e-05s
Believability | Calculation of trust value for UNODC - Statistics on criminal justice took 7.3909759521484375e-06s
INFO | --- Analysis for unodc took 51.705815076828s
Availability | SPARQL endpoint availability check for Super Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Super Ontology took 0.000614166259765625s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.24999356269836426s
Reputation | Calculation of the PageRank for Super Ontology took 0.020593881607055664s
Interlinking | Calculation of Degree of Connection for Super Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 7.963180541992188e-05s
Believability | Calculation of trust value for Super Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for upper-ontology took 13.789454460144043s
Availability | SPARQL endpoint availability check for Sup_Ont: An Upper Ontology took 0.5556609630584717s
Availability | VoID file availability check for Sup_Ont: An Upper Ontology took 0.0002789497375488281s
Completeness | Calculation of interlinking completeness for Sup_Ont: An Upper Ontology took 0.29105043411254883s
Reputation | Calculation of the PageRank for Sup_Ont: An Upper Ontology took 0.0202329158782959s
Interlinking | Calculation of Degree of Connection for Sup_Ont: An Upper Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Sup_Ont: An Upper Ontology took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Sup_Ont: An Upper Ontology took 3.266334533691406e-05s
Believability | Calculation of trust value for Sup_Ont: An Upper Ontology took 7.62939453125e-06s
INFO | --- Analysis for Upper_Ontology took 3.9012560844421387s
Availability | SPARQL endpoint availability check for Urban Atlas dataset took 4.100799560546875e-05s
Availability | VoID file availability check for Urban Atlas dataset took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset took 0.27610111236572266s
Reputation | Calculation of the PageRank for Urban Atlas dataset took 0.02035212516784668s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Urban Atlas dataset took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset took 2.7894973754882812e-05s
Believability | Calculation of trust value for Urban Atlas dataset took 6.4373016357421875e-06s
INFO | --- Analysis for Urban_Atlas_ took 2.4000296592712402s
Availability | SPARQL endpoint availability check for Urban Atlas dataset @PSNC took 0.9459712505340576s
Availability | VoID file availability check for Urban Atlas dataset @PSNC took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset @PSNC took 0.2691376209259033s
Reputation | Calculation of the PageRank for Urban Atlas dataset @PSNC took 0.02021169662475586s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset @PSNC took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset @PSNC took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset @PSNC took 2.7418136596679688e-05s
Believability | Calculation of trust value for Urban Atlas dataset @PSNC took 7.3909759521484375e-06s
INFO | --- Analysis for Urban_Atlas_Dataset took 4.030998229980469s
Availability | SPARQL endpoint availability check for URIBurner took 67.87363624572754s
Availability | VoID file availability check for URIBurner took 0.0005762577056884766s
Extra | Recovery of all triples for URIBurner took 135.60027050971985s
Amount of data | Number of triples check for URIBurner took 10.003429174423218s
Versatility | Languages check for URIBurner took 10.068353176116943s
Interpretability | Number of blank nodes check for URIBurner took 25.624958515167236s
Interpretability | RDF structures check for URIBurner took 6.162654399871826s
Versatility | Serialization formats check for URIBurner took 98.79815220832825s
Availability | RDF dump link check for URIBurner took 41.98348927497864s
License | MR license check for URIBurner took 1.9828083515167236s
License | HR license check for URIBurner took 122.11776423454285s
Amount of data | Number of property check for URIBurner took 10.294311761856079s
Understandability | Number of label check for URIBurner took 36.90872097015381s
Understandability | URI regex check for URIBurner took 33.06974673271179s
Understandability | Vocabs check for URIBurner took 27.419660329818726s
Verifiability | Authors check for URIBurner took 27.867361783981323s
Verifiability | Publishers check for URIBurner took 14.693467378616333s
Performance | Throughput check for URIBurner took 28.10101580619812s
Amount of data | Check the number of entities for URIBurner took 8.726119995117188e-05s
Verifiability | Contribs. check for URIBurner took 0.536017894744873s
Interlinking | sameAs chians check for URIBurner took 1.290863037109375s
Interlinking | skos check for URIBurner took 0.5895960330963135s
Interlinking | skos check for URIBurner took 0.14388108253479004s
Timeliness | dataset update frequency check for URIBurner took 0.5032260417938232s
Currency | Creation date check for URIBurner took 2.5666346549987793s
Currency | Modification date check for URIBurner took 0.3139023780822754s
Rep.Conc. | URIs length for URIBurner took 244.57561826705933s
Consistency | Deprecated classes/propertiers check for URIBurner took 17.60785150527954s
Consistency | Disjoint class check for URIBurner took 28.69488000869751s
Consistency | Check Ontology hijacking for URIBurner took 129.2729790210724s
Consistency | Check Invalid usage of undefined properties for URIBurner took 142.31334805488586s
Conciseness | Check Extensional conciseness for URIBurner took 0.0001690387725830078s
Security | Sign check for URIBurner took 34.79568266868591s
Completeness | Calculation of interlinking completeness for URIBurner took 1.4148309230804443s
Reputation | Calculation of the PageRank for URIBurner took 0.020712614059448242s
Interlinking | Calculation of Degree of Connection for URIBurner took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for URIBurner took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for URIBurner took 0.00010395050048828125s
Believability | Calculation of trust value for URIBurner took 1.1205673217773438e-05s
INFO | --- Analysis for uriburner took 2529.5916171073914s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 4.601478576660156e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0003631114959716797s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.7098453044891357s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.020294189453125s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 3.2901763916015625e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 5.4836273193359375e-06s
INFO | --- Analysis for urn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976 took 3.766103506088257s
Availability | SPARQL endpoint availability check for Legija Stranaca took 6.29425048828125e-05s
Availability | VoID file availability check for Legija Stranaca took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for Legija Stranaca took 0.28894901275634766s
Reputation | Calculation of the PageRank for Legija Stranaca took 0.02021479606628418s
Interlinking | Calculation of Degree of Connection for Legija Stranaca took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Legija Stranaca took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Legija Stranaca took 2.7418136596679688e-05s
Believability | Calculation of trust value for Legija Stranaca took 6.198883056640625e-06s
INFO | --- Analysis for Uros_Legija_Susa took 3.2937023639678955s
Availability | SPARQL endpoint availability check for Legija took 4.315376281738281e-05s
Availability | VoID file availability check for Legija took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for Legija took 0.26017308235168457s
Reputation | Calculation of the PageRank for Legija took 0.02048325538635254s
Interlinking | Calculation of Degree of Connection for Legija took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Legija took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Legija took 2.765655517578125e-05s
Believability | Calculation of trust value for Legija took 6.9141387939453125e-06s
INFO | --- Analysis for Uros_Susa took 3.736023426055908s
Availability | SPARQL endpoint availability check for US Political Violence took 4.1484832763671875e-05s
Availability | VoID file availability check for US Political Violence took 0.00023651123046875s
Completeness | Calculation of interlinking completeness for US Political Violence took 0.2624697685241699s
Reputation | Calculation of the PageRank for US Political Violence took 0.020206689834594727s
Interlinking | Calculation of Degree of Connection for US Political Violence took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for US Political Violence took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for US Political Violence took 2.8371810913085938e-05s
Believability | Calculation of trust value for US Political Violence took 6.67572021484375e-06s
INFO | --- Analysis for us-political-violence took 3.839101791381836s
Availability | SPARQL endpoint availability check for USAGE review corpus took 40.03491735458374s
Availability | VoID file availability check for USAGE review corpus took 0.0007030963897705078s
Completeness | Calculation of interlinking completeness for USAGE review corpus took 0.7434027194976807s
Reputation | Calculation of the PageRank for USAGE review corpus took 0.020224809646606445s
Interlinking | Calculation of Degree of Connection for USAGE review corpus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for USAGE review corpus took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for USAGE review corpus took 2.8371810913085938e-05s
Believability | Calculation of trust value for USAGE review corpus took 7.867813110351562e-06s
INFO | --- Analysis for usage-review-corpus took 164.4903211593628s
Availability | SPARQL endpoint availability check for Universidad Técnica Particular de Loja - Linked Open Data took 3.7118923664093018s
Availability | VoID file availability check for Universidad Técnica Particular de Loja - Linked Open Data took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for Universidad Técnica Particular de Loja - Linked Open Data took 0.26634812355041504s
Reputation | Calculation of the PageRank for Universidad Técnica Particular de Loja - Linked Open Data took 0.02022385597229004s
Interlinking | Calculation of Degree of Connection for Universidad Técnica Particular de Loja - Linked Open Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universidad Técnica Particular de Loja - Linked Open Data took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Universidad Técnica Particular de Loja - Linked Open Data took 7.224082946777344e-05s
Believability | Calculation of trust value for Universidad Técnica Particular de Loja - Linked Open Data took 7.152557373046875e-06s
INFO | --- Analysis for utpl-lod took 10.27331805229187s
Availability | SPARQL endpoint availability check for Výkazy zisku a ztrát obcí ČR took 5.0067901611328125e-05s
Availability | VoID file availability check for Výkazy zisku a ztrát obcí ČR took 0.0002853870391845703s
Completeness | Calculation of interlinking completeness for Výkazy zisku a ztrát obcí ČR took 0.25028038024902344s
Reputation | Calculation of the PageRank for Výkazy zisku a ztrát obcí ČR took 0.020178556442260742s
Interlinking | Calculation of Degree of Connection for Výkazy zisku a ztrát obcí ČR took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Výkazy zisku a ztrát obcí ČR took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Výkazy zisku a ztrát obcí ČR took 2.9087066650390625e-05s
Believability | Calculation of trust value for Výkazy zisku a ztrát obcí ČR took 5.4836273193359375e-06s
INFO | --- Analysis for v-kazy-zisku-a-ztr-t-obc---r took 3.4070017337799072s
Availability | SPARQL endpoint availability check for terrorist attack took 4.363059997558594e-05s
Availability | VoID file availability check for terrorist attack took 0.0005562305450439453s
Completeness | Calculation of interlinking completeness for terrorist attack took 0.7393717765808105s
Reputation | Calculation of the PageRank for terrorist attack took 0.020425796508789062s
Interlinking | Calculation of Degree of Connection for terrorist attack took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for terrorist attack took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for terrorist attack took 3.0279159545898438e-05s
Believability | Calculation of trust value for terrorist attack took 7.3909759521484375e-06s
INFO | --- Analysis for varsha took 3.3932034969329834s
Availability | SPARQL endpoint availability check for VA took 4.458427429199219e-05s
Availability | VoID file availability check for VA took 0.0005497932434082031s
Completeness | Calculation of interlinking completeness for VA took 0.2767064571380615s
Reputation | Calculation of the PageRank for VA took 0.021791934967041016s
Interlinking | Calculation of Degree of Connection for VA took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for VA took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for VA took 3.337860107421875e-05s
Believability | Calculation of trust value for VA took 7.62939453125e-06s
INFO | --- Analysis for Vehicule_Autonome took 2.696272611618042s
Availability | SPARQL endpoint availability check for Velez (1744) Index Totius Artis in LiLa took 0.564502477645874s
Availability | VoID file availability check for Velez (1744) Index Totius Artis in LiLa took 0.0007812976837158203s
Completeness | Calculation of interlinking completeness for Velez (1744) Index Totius Artis in LiLa took 0.26541996002197266s
Reputation | Calculation of the PageRank for Velez (1744) Index Totius Artis in LiLa took 0.020716190338134766s
Interlinking | Calculation of Degree of Connection for Velez (1744) Index Totius Artis in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Velez (1744) Index Totius Artis in LiLa took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Velez (1744) Index Totius Artis in LiLa took 3.933906555175781e-05s
Believability | Calculation of trust value for Velez (1744) Index Totius Artis in LiLa took 7.62939453125e-06s
INFO | --- Analysis for VelezIndexTotiusArtis took 3.972846746444702s
Availability | SPARQL endpoint availability check for Verrijkt Koninkrijk took 1.0880906581878662s
Availability | VoID file availability check for Verrijkt Koninkrijk took 0.0005500316619873047s
Completeness | Calculation of interlinking completeness for Verrijkt Koninkrijk took 0.2643282413482666s
Reputation | Calculation of the PageRank for Verrijkt Koninkrijk took 0.02048468589782715s
Interlinking | Calculation of Degree of Connection for Verrijkt Koninkrijk took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Verrijkt Koninkrijk took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Verrijkt Koninkrijk took 8.416175842285156e-05s
Believability | Calculation of trust value for Verrijkt Koninkrijk took 5.9604644775390625e-06s
INFO | --- Analysis for verrijktkoninkrijk took 9.947904825210571s
Availability | SPARQL endpoint availability check for VIAF: The Virtual International Authority File took 4.696846008300781e-05s
Availability | VoID file availability check for VIAF: The Virtual International Authority File took 0.0005528926849365234s
Completeness | Calculation of interlinking completeness for VIAF: The Virtual International Authority File took 0.285494327545166s
Reputation | Calculation of the PageRank for VIAF: The Virtual International Authority File took 0.02080988883972168s
Interlinking | Calculation of Degree of Connection for VIAF: The Virtual International Authority File took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for VIAF: The Virtual International Authority File took 0.0008542537689208984s
Interlinking | Calculation of Clustering coefficient for VIAF: The Virtual International Authority File took 0.00018644332885742188s
Believability | Calculation of trust value for VIAF: The Virtual International Authority File took 7.867813110351562e-06s
INFO | --- Analysis for viaf took 3.5271623134613037s
Availability | SPARQL endpoint availability check for Vías Públicas de Zaragoza (Localización) took 7.915496826171875e-05s
Availability | VoID file availability check for Vías Públicas de Zaragoza (Localización) took 0.00022935867309570312s
Completeness | Calculation of interlinking completeness for Vías Públicas de Zaragoza (Localización) took 0.27943873405456543s
Reputation | Calculation of the PageRank for Vías Públicas de Zaragoza (Localización) took 0.020588397979736328s
Interlinking | Calculation of Degree of Connection for Vías Públicas de Zaragoza (Localización) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Vías Públicas de Zaragoza (Localización) took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Vías Públicas de Zaragoza (Localización) took 3.075599670410156e-05s
Believability | Calculation of trust value for Vías Públicas de Zaragoza (Localización) took 5.9604644775390625e-06s
INFO | --- Analysis for vias-publicas-zaragoza took 2.9086520671844482s
Availability | SPARQL endpoint availability check for Vihar Exports took 4.315376281738281e-05s
Availability | VoID file availability check for Vihar Exports took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for Vihar Exports took 0.269397497177124s
Reputation | Calculation of the PageRank for Vihar Exports took 0.020463228225708008s
Interlinking | Calculation of Degree of Connection for Vihar Exports took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Vihar Exports took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Vihar Exports took 3.0517578125e-05s
Believability | Calculation of trust value for Vihar Exports took 7.152557373046875e-06s
INFO | --- Analysis for Vihar_Exports took 2.2910568714141846s
Availability | SPARQL endpoint availability check for vimeo.videoobject took 4.0531158447265625e-05s
Availability | VoID file availability check for vimeo.videoobject took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for vimeo.videoobject took 0.27031779289245605s
Reputation | Calculation of the PageRank for vimeo.videoobject took 0.02043890953063965s
Interlinking | Calculation of Degree of Connection for vimeo.videoobject took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for vimeo.videoobject took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for vimeo.videoobject took 3.0279159545898438e-05s
Believability | Calculation of trust value for vimeo.videoobject took 7.152557373046875e-06s
INFO | --- Analysis for vimeo_videoobject took 3.3320775032043457s
Availability | SPARQL endpoint availability check for VIVO took 4.220008850097656e-05s
Availability | VoID file availability check for VIVO took 0.0006940364837646484s
Completeness | Calculation of interlinking completeness for VIVO took 0.28991103172302246s
Reputation | Calculation of the PageRank for VIVO took 0.020563364028930664s
Interlinking | Calculation of Degree of Connection for VIVO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for VIVO took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for VIVO took 6.914138793945312e-05s
Believability | Calculation of trust value for VIVO took 6.4373016357421875e-06s
INFO | --- Analysis for vivo took 4.756144762039185s
Availability | SPARQL endpoint availability check for VIVO Cornell took 4.5299530029296875e-05s
Availability | VoID file availability check for VIVO Cornell took 0.0003190040588378906s
Completeness | Calculation of interlinking completeness for VIVO Cornell took 0.27915310859680176s
Reputation | Calculation of the PageRank for VIVO Cornell took 0.02011704444885254s
Interlinking | Calculation of Degree of Connection for VIVO Cornell took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for VIVO Cornell took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for VIVO Cornell took 7.843971252441406e-05s
Believability | Calculation of trust value for VIVO Cornell took 7.62939453125e-06s
INFO | --- Analysis for vivo-cornell-university took 5.964720249176025s
Availability | SPARQL endpoint availability check for VIVO CU-Boulder took 3.933906555175781e-05s
Availability | VoID file availability check for VIVO CU-Boulder took 0.00022077560424804688s
Completeness | Calculation of interlinking completeness for VIVO CU-Boulder took 0.25933194160461426s
Reputation | Calculation of the PageRank for VIVO CU-Boulder took 0.020437240600585938s
Interlinking | Calculation of Degree of Connection for VIVO CU-Boulder took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for VIVO CU-Boulder took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for VIVO CU-Boulder took 2.8848648071289062e-05s
Believability | Calculation of trust value for VIVO CU-Boulder took 5.9604644775390625e-06s
INFO | --- Analysis for vivo-cu-boulder took 2.9746899604797363s
Availability | SPARQL endpoint availability check for VIVO Indiana took 4.220008850097656e-05s
Availability | VoID file availability check for VIVO Indiana took 0.0005581378936767578s
Completeness | Calculation of interlinking completeness for VIVO Indiana took 0.2955605983734131s
Reputation | Calculation of the PageRank for VIVO Indiana took 0.020552396774291992s
Interlinking | Calculation of Degree of Connection for VIVO Indiana took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for VIVO Indiana took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for VIVO Indiana took 7.987022399902344e-05s
Believability | Calculation of trust value for VIVO Indiana took 6.9141387939453125e-06s
INFO | --- Analysis for vivo-indiana-university took 3.1960227489471436s
Availability | SPARQL endpoint availability check for VIVO Ponce took 4.1484832763671875e-05s
Availability | VoID file availability check for VIVO Ponce took 0.0007138252258300781s
Completeness | Calculation of interlinking completeness for VIVO Ponce took 0.2748103141784668s
Reputation | Calculation of the PageRank for VIVO Ponce took 0.02051067352294922s
Interlinking | Calculation of Degree of Connection for VIVO Ponce took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for VIVO Ponce took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for VIVO Ponce took 3.337860107421875e-05s
Believability | Calculation of trust value for VIVO Ponce took 5.245208740234375e-06s
INFO | --- Analysis for vivo-ponce took 2.8750813007354736s
Availability | SPARQL endpoint availability check for VIVO Scripps Research Institute took 7.319450378417969e-05s
Availability | VoID file availability check for VIVO Scripps Research Institute took 0.0016362667083740234s
Completeness | Calculation of interlinking completeness for VIVO Scripps Research Institute took 0.2546885013580322s
Reputation | Calculation of the PageRank for VIVO Scripps Research Institute took 0.02051401138305664s
Interlinking | Calculation of Degree of Connection for VIVO Scripps Research Institute took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for VIVO Scripps Research Institute took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for VIVO Scripps Research Institute took 3.743171691894531e-05s
Believability | Calculation of trust value for VIVO Scripps Research Institute took 5.245208740234375e-06s
INFO | --- Analysis for vivo-scripps-research-institute took 2.819084882736206s
Availability | SPARQL endpoint availability check for VIVO University of Florida took 7.081031799316406e-05s
Availability | VoID file availability check for VIVO University of Florida took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for VIVO University of Florida took 0.29639506340026855s
Reputation | Calculation of the PageRank for VIVO University of Florida took 0.020495176315307617s
Interlinking | Calculation of Degree of Connection for VIVO University of Florida took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for VIVO University of Florida took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for VIVO University of Florida took 9.322166442871094e-05s
Believability | Calculation of trust value for VIVO University of Florida took 5.4836273193359375e-06s
INFO | --- Analysis for vivo-university-of-florida took 2.6124565601348877s
Availability | SPARQL endpoint availability check for VIVO Weill Cornell Medical College took 4.57763671875e-05s
Availability | VoID file availability check for VIVO Weill Cornell Medical College took 0.0006616115570068359s
Completeness | Calculation of interlinking completeness for VIVO Weill Cornell Medical College took 0.25411081314086914s
Reputation | Calculation of the PageRank for VIVO Weill Cornell Medical College took 0.020606517791748047s
Interlinking | Calculation of Degree of Connection for VIVO Weill Cornell Medical College took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for VIVO Weill Cornell Medical College took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for VIVO Weill Cornell Medical College took 4.029273986816406e-05s
Believability | Calculation of trust value for VIVO Weill Cornell Medical College took 5.7220458984375e-06s
INFO | --- Analysis for vivo-weill-cornell-medical-college took 2.777400016784668s
Availability | SPARQL endpoint availability check for VIVO WUSTL took 4.792213439941406e-05s
Availability | VoID file availability check for VIVO WUSTL took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for VIVO WUSTL took 0.2859327793121338s
Reputation | Calculation of the PageRank for VIVO WUSTL took 0.020751237869262695s
Interlinking | Calculation of Degree of Connection for VIVO WUSTL took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for VIVO WUSTL took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for VIVO WUSTL took 3.504753112792969e-05s
Believability | Calculation of trust value for VIVO WUSTL took 5.4836273193359375e-06s
INFO | --- Analysis for vivo-wustl took 2.792804002761841s
Availability | SPARQL endpoint availability check for vivo2doi took 4.315376281738281e-05s
Availability | VoID file availability check for vivo2doi took 0.0006499290466308594s
Completeness | Calculation of interlinking completeness for vivo2doi took 0.2654852867126465s
Reputation | Calculation of the PageRank for vivo2doi took 0.02024221420288086s
Interlinking | Calculation of Degree of Connection for vivo2doi took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for vivo2doi took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for vivo2doi took 4.172325134277344e-05s
Believability | Calculation of trust value for vivo2doi took 5.7220458984375e-06s
INFO | --- Analysis for vivo2doi took 23.07722806930542s
Availability | SPARQL endpoint availability check for WordNet 3.0 (VU Amsterdam) took 4.172325134277344e-05s
Availability | VoID file availability check for WordNet 3.0 (VU Amsterdam) took 0.0005338191986083984s
Completeness | Calculation of interlinking completeness for WordNet 3.0 (VU Amsterdam) took 0.25949859619140625s
Reputation | Calculation of the PageRank for WordNet 3.0 (VU Amsterdam) took 0.020328521728515625s
Interlinking | Calculation of Degree of Connection for WordNet 3.0 (VU Amsterdam) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for WordNet 3.0 (VU Amsterdam) took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for WordNet 3.0 (VU Amsterdam) took 6.961822509765625e-05s
Believability | Calculation of trust value for WordNet 3.0 (VU Amsterdam) took 6.198883056640625e-06s
INFO | --- Analysis for vu-wordnet took 12.884353876113892s
Availability | SPARQL endpoint availability check for vulnerapedia took 0.2487044334411621s
Availability | VoID file availability check for vulnerapedia took 0.0005614757537841797s
Completeness | Calculation of interlinking completeness for vulnerapedia took 0.26416873931884766s
Reputation | Calculation of the PageRank for vulnerapedia took 0.020223140716552734s
Interlinking | Calculation of Degree of Connection for vulnerapedia took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for vulnerapedia took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for vulnerapedia took 6.461143493652344e-05s
Believability | Calculation of trust value for vulnerapedia took 4.76837158203125e-06s
INFO | --- Analysis for vulnerapedia took 3.1296210289001465s
Availability | SPARQL endpoint availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 4.100799560546875e-05s
Availability | VoID file availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0002181529998779297s
Completeness | Calculation of interlinking completeness for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.2803356647491455s
Reputation | Calculation of the PageRank for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.020236730575561523s
Interlinking | Calculation of Degree of Connection for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.1444091796875e-05s
Believability | Calculation of trust value for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 7.867813110351562e-06s
INFO | --- Analysis for VVASIAK took 2.3875348567962646s
Availability | SPARQL endpoint availability check for Statybu imone - Vyvasta took 4.458427429199219e-05s
Availability | VoID file availability check for Statybu imone - Vyvasta took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for Statybu imone - Vyvasta took 0.2991337776184082s
Reputation | Calculation of the PageRank for Statybu imone - Vyvasta took 0.021408557891845703s
Interlinking | Calculation of Degree of Connection for Statybu imone - Vyvasta took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Statybu imone - Vyvasta took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Statybu imone - Vyvasta took 3.4332275390625e-05s
Believability | Calculation of trust value for Statybu imone - Vyvasta took 6.4373016357421875e-06s
INFO | --- Analysis for Vyvasta took 2.442564010620117s
Availability | SPARQL endpoint availability check for W3C took 4.506111145019531e-05s
Availability | VoID file availability check for W3C took 0.0005733966827392578s
Completeness | Calculation of interlinking completeness for W3C took 0.2562448978424072s
Reputation | Calculation of the PageRank for W3C took 0.020615816116333008s
Interlinking | Calculation of Degree of Connection for W3C took 3.6716461181640625e-05s
Interlinking | Calculation of Centrality for W3C took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for W3C took 0.0001399517059326172s
Believability | Calculation of trust value for W3C took 5.7220458984375e-06s
INFO | --- Analysis for w3c took 2.6727564334869385s
Availability | SPARQL endpoint availability check for W3C Provenance Incubator Group Vocabulary Mappings took 4.1484832763671875e-05s
Availability | VoID file availability check for W3C Provenance Incubator Group Vocabulary Mappings took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for W3C Provenance Incubator Group Vocabulary Mappings took 0.2600107192993164s
Reputation | Calculation of the PageRank for W3C Provenance Incubator Group Vocabulary Mappings took 0.02071094512939453s
Interlinking | Calculation of Degree of Connection for W3C Provenance Incubator Group Vocabulary Mappings took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for W3C Provenance Incubator Group Vocabulary Mappings took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for W3C Provenance Incubator Group Vocabulary Mappings took 3.1948089599609375e-05s
Believability | Calculation of trust value for W3C Provenance Incubator Group Vocabulary Mappings took 7.152557373046875e-06s
INFO | --- Analysis for w3c-provenance-incubator-group-vocabulary-mappings took 2.908191442489624s
Availability | SPARQL endpoint availability check for WordNet 2.0 (W3C) took 4.482269287109375e-05s
Availability | VoID file availability check for WordNet 2.0 (W3C) took 0.0005970001220703125s
Completeness | Calculation of interlinking completeness for WordNet 2.0 (W3C) took 0.26786208152770996s
Reputation | Calculation of the PageRank for WordNet 2.0 (W3C) took 0.02050185203552246s
Interlinking | Calculation of Degree of Connection for WordNet 2.0 (W3C) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for WordNet 2.0 (W3C) took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for WordNet 2.0 (W3C) took 0.00011229515075683594s
Believability | Calculation of trust value for WordNet 2.0 (W3C) took 5.9604644775390625e-06s
INFO | --- Analysis for w3c-wordnet took 3.089305877685547s
Availability | SPARQL endpoint availability check for WarSampo took 0.3663163185119629s
Availability | VoID file availability check for WarSampo took 0.000431060791015625s
Extra | Recovery of all triples for WarSampo took 26.65945839881897s
Performance | Total latancy measurement for WarSampo took 0.7524502277374268s
Amount of data | Number of triples check for WarSampo took 19.621548414230347s
Interoperability | New terms check for WarSampo took 3.831238269805908s
Versatility | Languages check for WarSampo took 53.47016429901123s
Interpretability | Number of blank nodes check for WarSampo took 19.020153760910034s
Security | Check HTTPS for WarSampo took 0.3780958652496338s
Interpretability | RDF structures check for WarSampo took 0.18499493598937988s
Versatility | Serialization formats check for WarSampo took 0.19846820831298828s
Availability | RDF dump link check for WarSampo took 1.1900839805603027s
License | MR license check for WarSampo took 0.21166706085205078s
License | HR license check for WarSampo took 49.23703217506409s
Amount of data | Number of property check for WarSampo took 0.192213773727417s
Understandability | Number of label check for WarSampo took 9.547910213470459s
Understandability | URI regex check for WarSampo took 0.3346102237701416s
Understandability | Vocabs check for WarSampo took 0.15116524696350098s
Verifiability | Authors check for WarSampo took 0.19228076934814453s
Verifiability | Publishers check for WarSampo took 0.1831214427947998s
Performance | Throughput check for WarSampo took 10.563416481018066s
Amount of data | Check the number of entities for WarSampo took 15.88903021812439s
Verifiability | Contribs. check for WarSampo took 0.18471097946166992s
Interlinking | sameAs chians check for WarSampo took 0.19981789588928223s
Interlinking | skos check for WarSampo took 0.19105315208435059s
Interlinking | skos check for WarSampo took 0.13814902305603027s
Timeliness | dataset update frequency check for WarSampo took 0.17715024948120117s
Currency | Creation date check for WarSampo took 0.34983396530151367s
Currency | Modification date check for WarSampo took 0.3692207336425781s
Rep.Conc. | URIs length for WarSampo took 52.23958086967468s
Interoperability | New vocabularies check for WarSampo took 1.1682510375976562e-05s
Consistency | Deprecated classes/propertiers check for WarSampo took 0.16556668281555176s
Accuracy | Check Functional Property for WarSampo took 0.16765642166137695s
Accuracy | Check Inverse Functional Property for WarSampo took 0.15053129196166992s
Accuracy | Check Empty annotation labels for WarSampo took 12.006681203842163s
Accuracy | Check White space in annotation for WarSampo took 2.202316999435425s
Accuracy | Check Datatype consistency for WarSampo took 5.428916931152344s
Consistency | Disjoint class check for WarSampo took 0.18134379386901855s
Consistency | Check Misplaced properties for WarSampo took 20.898542642593384s
Consistency | Check Ontology hijacking for WarSampo took 19.39629030227661s
Consistency | Check Invalid usage of undefined classes for WarSampo took 1.217024803161621s
Consistency | Check Invalid usage of undefined properties for WarSampo took 1.416853666305542s
Conciseness | Check Extensional conciseness for WarSampo took 2.7959911823272705s
Conciseness | Check Intensional conciseness for WarSampo took 0.26738905906677246s
Security | Sign check for WarSampo took 0.15772604942321777s
Availability | Check URIs Dereferenciability for WarSampo took 2.631622552871704s
Completeness | Calculation of interlinking completeness for WarSampo took 1.4070286750793457s
Reputation | Calculation of the PageRank for WarSampo took 0.020839929580688477s
Interlinking | Calculation of Degree of Connection for WarSampo took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for WarSampo took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for WarSampo took 0.00010156631469726562s
Interoperability | Check the re-using of existing vocabs for WarSampo took 1.9073486328125e-06s
Believability | Calculation of trust value for WarSampo took 6.198883056640625e-06s
INFO | --- Analysis for warsampo took 1013.7773134708405s
Availability | SPARQL endpoint availability check for WASABI RDF Knowledge Graph took 20.4263174533844s
Availability | VoID file availability check for WASABI RDF Knowledge Graph took 0.0004181861877441406s
Completeness | Calculation of interlinking completeness for WASABI RDF Knowledge Graph took 0.28455400466918945s
Reputation | Calculation of the PageRank for WASABI RDF Knowledge Graph took 0.02090740203857422s
Interlinking | Calculation of Degree of Connection for WASABI RDF Knowledge Graph took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for WASABI RDF Knowledge Graph took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for WASABI RDF Knowledge Graph took 8.559226989746094e-05s
Believability | Calculation of trust value for WASABI RDF Knowledge Graph took 6.67572021484375e-06s
INFO | --- Analysis for wasabi took 56.16287422180176s
Availability | SPARQL endpoint availability check for FAO water areas classification as linked data @PSNC took 0.8642585277557373s
Availability | VoID file availability check for FAO water areas classification as linked data @PSNC took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for FAO water areas classification as linked data @PSNC took 0.290585994720459s
Reputation | Calculation of the PageRank for FAO water areas classification as linked data @PSNC took 0.022356510162353516s
Interlinking | Calculation of Degree of Connection for FAO water areas classification as linked data @PSNC took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for FAO water areas classification as linked data @PSNC took 0.0009610652923583984s
Interlinking | Calculation of Clustering coefficient for FAO water areas classification as linked data @PSNC took 3.8623809814453125e-05s
Believability | Calculation of trust value for FAO water areas classification as linked data @PSNC took 7.62939453125e-06s
INFO | --- Analysis for Water_Areas_Classification took 5.124226808547974s
Availability | SPARQL endpoint availability check for Water buffer dataset from Czech Republic @PSNC took 0.573693037033081s
Availability | VoID file availability check for Water buffer dataset from Czech Republic @PSNC took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for Water buffer dataset from Czech Republic @PSNC took 0.25803518295288086s
Reputation | Calculation of the PageRank for Water buffer dataset from Czech Republic @PSNC took 0.020621061325073242s
Interlinking | Calculation of Degree of Connection for Water buffer dataset from Czech Republic @PSNC took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Water buffer dataset from Czech Republic @PSNC took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Water buffer dataset from Czech Republic @PSNC took 3.170967102050781e-05s
Believability | Calculation of trust value for Water buffer dataset from Czech Republic @PSNC took 6.9141387939453125e-06s
INFO | --- Analysis for Water_Buffer took 4.4525370597839355s
Availability | SPARQL endpoint availability check for WebIsALOD took 0.2149498462677002s
Availability | VoID file availability check for WebIsALOD took 0.0006670951843261719s
Completeness | Calculation of interlinking completeness for WebIsALOD took 0.7129426002502441s
Reputation | Calculation of the PageRank for WebIsALOD took 0.020587921142578125s
Interlinking | Calculation of Degree of Connection for WebIsALOD took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for WebIsALOD took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for WebIsALOD took 8.130073547363281e-05s
Believability | Calculation of trust value for WebIsALOD took 8.106231689453125e-06s
INFO | --- Analysis for webisalod took 5.225867748260498s
Availability | SPARQL endpoint availability check for webnmasunotraveler took 4.267692565917969e-05s
Availability | VoID file availability check for webnmasunotraveler took 0.0007903575897216797s
Completeness | Calculation of interlinking completeness for webnmasunotraveler took 0.2983064651489258s
Reputation | Calculation of the PageRank for webnmasunotraveler took 0.020752906799316406s
Interlinking | Calculation of Degree of Connection for webnmasunotraveler took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for webnmasunotraveler took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for webnmasunotraveler took 3.8623809814453125e-05s
Believability | Calculation of trust value for webnmasunotraveler took 6.4373016357421875e-06s
INFO | --- Analysis for webnmasunotraveler took 12.68909502029419s
Availability | SPARQL endpoint availability check for Whisky Circle took 5.316734313964844e-05s
Availability | VoID file availability check for Whisky Circle took 0.0007429122924804688s
Completeness | Calculation of interlinking completeness for Whisky Circle took 0.25989460945129395s
Reputation | Calculation of the PageRank for Whisky Circle took 0.020497560501098633s
Interlinking | Calculation of Degree of Connection for Whisky Circle took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Whisky Circle took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Whisky Circle took 0.00010228157043457031s
Believability | Calculation of trust value for Whisky Circle took 5.745887756347656e-05s
INFO | --- Analysis for whisky-circle-info took 3.018465757369995s
Availability | SPARQL endpoint availability check for Corona Virus Infected Cases Ontology took 15.994116067886353s
Availability | VoID file availability check for Corona Virus Infected Cases Ontology took 0.000881195068359375s
Completeness | Calculation of interlinking completeness for Corona Virus Infected Cases Ontology took 0.2598299980163574s
Reputation | Calculation of the PageRank for Corona Virus Infected Cases Ontology took 0.021409988403320312s
Interlinking | Calculation of Degree of Connection for Corona Virus Infected Cases Ontology took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Corona Virus Infected Cases Ontology took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Corona Virus Infected Cases Ontology took 3.695487976074219e-05s
Believability | Calculation of trust value for Corona Virus Infected Cases Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for WHOnto took 34.45092177391052s
Availability | SPARQL endpoint availability check for COvid-19 statistics Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for COvid-19 statistics Ontology took 0.00077056884765625s
Completeness | Calculation of interlinking completeness for COvid-19 statistics Ontology took 0.28968381881713867s
Reputation | Calculation of the PageRank for COvid-19 statistics Ontology took 0.020706892013549805s
Interlinking | Calculation of Degree of Connection for COvid-19 statistics Ontology took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for COvid-19 statistics Ontology took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for COvid-19 statistics Ontology took 3.600120544433594e-05s
Believability | Calculation of trust value for COvid-19 statistics Ontology took 7.867813110351562e-06s
INFO | --- Analysis for whonto took 9.001500129699707s
Availability | SPARQL endpoint availability check for Wikidata took 0.43981027603149414s
Availability | VoID file availability check for Wikidata took 0.0006632804870605469s
Completeness | Calculation of interlinking completeness for Wikidata took 0.3163645267486572s
Reputation | Calculation of the PageRank for Wikidata took 0.020947694778442383s
Interlinking | Calculation of Degree of Connection for Wikidata took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Wikidata took 0.0009903907775878906s
Interlinking | Calculation of Clustering coefficient for Wikidata took 0.00033402442932128906s
Believability | Calculation of trust value for Wikidata took 5.0067901611328125e-06s
INFO | --- Analysis for wikidata took 18.92380928993225s
Availability | SPARQL endpoint availability check for Wikilinks RDF/NIF took 4.4345855712890625e-05s
Availability | VoID file availability check for Wikilinks RDF/NIF took 0.0007011890411376953s
Completeness | Calculation of interlinking completeness for Wikilinks RDF/NIF took 0.2631795406341553s
Reputation | Calculation of the PageRank for Wikilinks RDF/NIF took 0.02052617073059082s
Interlinking | Calculation of Degree of Connection for Wikilinks RDF/NIF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Wikilinks RDF/NIF took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Wikilinks RDF/NIF took 6.818771362304688e-05s
Believability | Calculation of trust value for Wikilinks RDF/NIF took 7.152557373046875e-06s
INFO | --- Analysis for wikilinks-rdf-nif took 3.3483376502990723s
Availability | SPARQL endpoint availability check for WikiPathways took 3.981590270996094e-05s
Availability | VoID file availability check for WikiPathways took 0.0002396106719970703s
Completeness | Calculation of interlinking completeness for WikiPathways took 0.26810383796691895s
Reputation | Calculation of the PageRank for WikiPathways took 0.020343780517578125s
Interlinking | Calculation of Degree of Connection for WikiPathways took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for WikiPathways took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for WikiPathways took 3.0279159545898438e-05s
Believability | Calculation of trust value for WikiPathways took 6.4373016357421875e-06s
INFO | --- Analysis for wikipathways took 4.222096681594849s
Availability | SPARQL endpoint availability check for WikiWord Thesaurus Data took 4.0531158447265625e-05s
Availability | VoID file availability check for WikiWord Thesaurus Data took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for WikiWord Thesaurus Data took 0.28251099586486816s
Reputation | Calculation of the PageRank for WikiWord Thesaurus Data took 0.020265579223632812s
Interlinking | Calculation of Degree of Connection for WikiWord Thesaurus Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for WikiWord Thesaurus Data took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for WikiWord Thesaurus Data took 2.7179718017578125e-05s
Believability | Calculation of trust value for WikiWord Thesaurus Data took 6.9141387939453125e-06s
INFO | --- Analysis for wikiword_thesaurus took 3.3253772258758545s
Availability | SPARQL endpoint availability check for wiktionary.dbpedia.org took 0.2974681854248047s
Availability | VoID file availability check for wiktionary.dbpedia.org took 0.0006232261657714844s
Completeness | Calculation of interlinking completeness for wiktionary.dbpedia.org took 0.2493729591369629s
Reputation | Calculation of the PageRank for wiktionary.dbpedia.org took 0.02079629898071289s
Interlinking | Calculation of Degree of Connection for wiktionary.dbpedia.org took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for wiktionary.dbpedia.org took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for wiktionary.dbpedia.org took 8.296966552734375e-05s
Believability | Calculation of trust value for wiktionary.dbpedia.org took 9.5367431640625e-06s
INFO | --- Analysis for wiktionary-dbpedia-org took 4.42711067199707s
Availability | SPARQL endpoint availability check for Wings workflow provenance dataset took 4.2438507080078125e-05s
Availability | VoID file availability check for Wings workflow provenance dataset took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for Wings workflow provenance dataset took 0.26863574981689453s
Reputation | Calculation of the PageRank for Wings workflow provenance dataset took 0.020881175994873047s
Interlinking | Calculation of Degree of Connection for Wings workflow provenance dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Wings workflow provenance dataset took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for Wings workflow provenance dataset took 3.1948089599609375e-05s
Believability | Calculation of trust value for Wings workflow provenance dataset took 7.3909759521484375e-06s
INFO | --- Analysis for wings-workflow-provenance-dataset took 3.352417469024658s
Availability | SPARQL endpoint availability check for The World Literature Knowledge Graph took 1.281954288482666s
Availability | VoID file availability check for The World Literature Knowledge Graph took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for The World Literature Knowledge Graph took 0.28888392448425293s
Reputation | Calculation of the PageRank for The World Literature Knowledge Graph took 0.020765066146850586s
Interlinking | Calculation of Degree of Connection for The World Literature Knowledge Graph took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The World Literature Knowledge Graph took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for The World Literature Knowledge Graph took 3.361701965332031e-05s
Believability | Calculation of trust value for The World Literature Knowledge Graph took 8.106231689453125e-06s
INFO | --- Analysis for wl-kg took 4.420945405960083s
Availability | SPARQL endpoint availability check for Wordnet-Wikipedia/DBpedia instance mapping took 5.626678466796875e-05s
Availability | VoID file availability check for Wordnet-Wikipedia/DBpedia instance mapping took 0.0007529258728027344s
Completeness | Calculation of interlinking completeness for Wordnet-Wikipedia/DBpedia instance mapping took 0.28610992431640625s
Reputation | Calculation of the PageRank for Wordnet-Wikipedia/DBpedia instance mapping took 0.020193815231323242s
Interlinking | Calculation of Degree of Connection for Wordnet-Wikipedia/DBpedia instance mapping took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Wordnet-Wikipedia/DBpedia instance mapping took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Wordnet-Wikipedia/DBpedia instance mapping took 6.461143493652344e-05s
Believability | Calculation of trust value for Wordnet-Wikipedia/DBpedia instance mapping took 5.9604644775390625e-06s
INFO | --- Analysis for wn-wiki-instances took 3.0749528408050537s
Availability | SPARQL endpoint availability check for World Loanword Database took 0.26672887802124023s
Availability | VoID file availability check for World Loanword Database took 0.0004305839538574219s
Completeness | Calculation of interlinking completeness for World Loanword Database took 0.26033759117126465s
Reputation | Calculation of the PageRank for World Loanword Database took 0.020093917846679688s
Interlinking | Calculation of Degree of Connection for World Loanword Database took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for World Loanword Database took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for World Loanword Database took 6.580352783203125e-05s
Believability | Calculation of trust value for World Loanword Database took 6.4373016357421875e-06s
INFO | --- Analysis for wold took 2.6864235401153564s
Availability | SPARQL endpoint availability check for Wood Trick LLC took 4.3392181396484375e-05s
Availability | VoID file availability check for Wood Trick LLC took 0.0012140274047851562s
Completeness | Calculation of interlinking completeness for Wood Trick LLC took 0.26103639602661133s
Reputation | Calculation of the PageRank for Wood Trick LLC took 0.020308732986450195s
Interlinking | Calculation of Degree of Connection for Wood Trick LLC took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Wood Trick LLC took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Wood Trick LLC took 2.7179718017578125e-05s
Believability | Calculation of trust value for Wood Trick LLC took 6.4373016357421875e-06s
INFO | --- Analysis for woodtrick took 2.8327181339263916s
Availability | SPARQL endpoint availability check for Word Formation Latin (WFL) in LiLa took 0.3680732250213623s
Availability | VoID file availability check for Word Formation Latin (WFL) in LiLa took 0.0005555152893066406s
Completeness | Calculation of interlinking completeness for Word Formation Latin (WFL) in LiLa took 0.26953792572021484s
Reputation | Calculation of the PageRank for Word Formation Latin (WFL) in LiLa took 0.020357131958007812s
Interlinking | Calculation of Degree of Connection for Word Formation Latin (WFL) in LiLa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Word Formation Latin (WFL) in LiLa took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Word Formation Latin (WFL) in LiLa took 3.314018249511719e-05s
Believability | Calculation of trust value for Word Formation Latin (WFL) in LiLa took 5.4836273193359375e-06s
INFO | --- Analysis for WordFormationLatin took 3.674614191055298s
Availability | SPARQL endpoint availability check for WordLift Blog EN took 4.267692565917969e-05s
Availability | VoID file availability check for WordLift Blog EN took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for WordLift Blog EN took 0.2749042510986328s
Reputation | Calculation of the PageRank for WordLift Blog EN took 0.02066493034362793s
Interlinking | Calculation of Degree of Connection for WordLift Blog EN took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for WordLift Blog EN took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for WordLift Blog EN took 0.00010514259338378906s
Believability | Calculation of trust value for WordLift Blog EN took 6.4373016357421875e-06s
INFO | --- Analysis for wordlift-io-blog-en took 2.9395906925201416s
Availability | SPARQL endpoint availability check for WordLift IT took 4.1961669921875e-05s
Availability | VoID file availability check for WordLift IT took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for WordLift IT took 0.30633044242858887s
Reputation | Calculation of the PageRank for WordLift IT took 0.020751953125s
Interlinking | Calculation of Degree of Connection for WordLift IT took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for WordLift IT took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for WordLift IT took 0.00010132789611816406s
Believability | Calculation of trust value for WordLift IT took 5.4836273193359375e-06s
INFO | --- Analysis for wordlift-io-blog-it took 2.9286551475524902s
Availability | SPARQL endpoint availability check for Wordnet took 4.0531158447265625e-05s
Availability | VoID file availability check for Wordnet took 0.0003044605255126953s
Completeness | Calculation of interlinking completeness for Wordnet took 0.2550492286682129s
Reputation | Calculation of the PageRank for Wordnet took 0.020699739456176758s
Interlinking | Calculation of Degree of Connection for Wordnet took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Wordnet took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Wordnet took 4.0531158447265625e-05s
Believability | Calculation of trust value for Wordnet took 8.106231689453125e-06s
INFO | --- Analysis for wordnet took 2.850231647491455s
Availability | SPARQL endpoint availability check for WordNet-RDF took 4.315376281738281e-05s
Availability | VoID file availability check for WordNet-RDF took 0.0005345344543457031s
Completeness | Calculation of interlinking completeness for WordNet-RDF took 0.28693103790283203s
Reputation | Calculation of the PageRank for WordNet-RDF took 0.020572423934936523s
Interlinking | Calculation of Degree of Connection for WordNet-RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for WordNet-RDF took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for WordNet-RDF took 0.00010800361633300781s
Believability | Calculation of trust value for WordNet-RDF took 5.9604644775390625e-06s
INFO | --- Analysis for wordnet-rdf took 2.4515509605407715s
Availability | SPARQL endpoint availability check for wordpress took 4.38690185546875e-05s
Availability | VoID file availability check for wordpress took 0.0005664825439453125s
Completeness | Calculation of interlinking completeness for wordpress took 0.2695274353027344s
Reputation | Calculation of the PageRank for wordpress took 0.020755290985107422s
Interlinking | Calculation of Degree of Connection for wordpress took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for wordpress took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for wordpress took 9.1552734375e-05s
Believability | Calculation of trust value for wordpress took 7.62939453125e-06s
INFO | --- Analysis for wordpress took 2.5992722511291504s
Availability | SPARQL endpoint availability check for wordpress.post took 4.076957702636719e-05s
Availability | VoID file availability check for wordpress.post took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for wordpress.post took 0.2723720073699951s
Reputation | Calculation of the PageRank for wordpress.post took 0.020594358444213867s
Interlinking | Calculation of Degree of Connection for wordpress.post took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for wordpress.post took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for wordpress.post took 3.075599670410156e-05s
Believability | Calculation of trust value for wordpress.post took 6.4373016357421875e-06s
INFO | --- Analysis for wordpress_post took 2.9468905925750732s
Availability | SPARQL endpoint availability check for World Bank Linked Data took 0.5161619186401367s
Availability | VoID file availability check for World Bank Linked Data took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for World Bank Linked Data took 0.26811766624450684s
Reputation | Calculation of the PageRank for World Bank Linked Data took 0.020767927169799805s
Interlinking | Calculation of Degree of Connection for World Bank Linked Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for World Bank Linked Data took 0.0008203983306884766s
Interlinking | Calculation of Clustering coefficient for World Bank Linked Data took 0.00013756752014160156s
Believability | Calculation of trust value for World Bank Linked Data took 5.245208740234375e-06s
INFO | --- Analysis for world-bank-linked-data took 3.0440735816955566s
Availability | SPARQL endpoint availability check for World Factbook (FU Berlin) took 0.936211109161377s
Availability | VoID file availability check for World Factbook (FU Berlin) took 0.0005655288696289062s
Completeness | Calculation of interlinking completeness for World Factbook (FU Berlin) took 0.26954221725463867s
Reputation | Calculation of the PageRank for World Factbook (FU Berlin) took 0.020551204681396484s
Interlinking | Calculation of Degree of Connection for World Factbook (FU Berlin) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for World Factbook (FU Berlin) took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for World Factbook (FU Berlin) took 8.249282836914062e-05s
Believability | Calculation of trust value for World Factbook (FU Berlin) took 5.9604644775390625e-06s
INFO | --- Analysis for world-factbook-fu-berlin took 5.159973382949829s
Availability | SPARQL endpoint availability check for World Wide Web Foundation took 4.1961669921875e-05s
Availability | VoID file availability check for World Wide Web Foundation took 0.0007138252258300781s
Completeness | Calculation of interlinking completeness for World Wide Web Foundation took 0.24794507026672363s
Reputation | Calculation of the PageRank for World Wide Web Foundation took 0.020679235458374023s
Interlinking | Calculation of Degree of Connection for World Wide Web Foundation took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for World Wide Web Foundation took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for World Wide Web Foundation took 8.463859558105469e-05s
Believability | Calculation of trust value for World Wide Web Foundation took 4.5299530029296875e-06s
INFO | --- Analysis for world-wide-web-foundation took 5.5917792320251465s
Availability | SPARQL endpoint availability check for WikiPathways took 4.124641418457031e-05s
Availability | VoID file availability check for WikiPathways took 0.00023508071899414062s
Completeness | Calculation of interlinking completeness for WikiPathways took 0.2614262104034424s
Reputation | Calculation of the PageRank for WikiPathways took 0.02067732810974121s
Interlinking | Calculation of Degree of Connection for WikiPathways took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for WikiPathways took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for WikiPathways took 2.956390380859375e-05s
Believability | Calculation of trust value for WikiPathways took 6.9141387939453125e-06s
INFO | --- Analysis for wp took 3.1213808059692383s
Availability | SPARQL endpoint availability check for wunderground.weatherreport took 4.4345855712890625e-05s
Availability | VoID file availability check for wunderground.weatherreport took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for wunderground.weatherreport took 0.2783358097076416s
Reputation | Calculation of the PageRank for wunderground.weatherreport took 0.020698070526123047s
Interlinking | Calculation of Degree of Connection for wunderground.weatherreport took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for wunderground.weatherreport took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for wunderground.weatherreport took 3.0517578125e-05s
Believability | Calculation of trust value for wunderground.weatherreport took 5.9604644775390625e-06s
INFO | --- Analysis for wunderground_weatherreport took 2.8924736976623535s
Availability | SPARQL endpoint availability check for World War 1 as Linked Open Data took 0.18265557289123535s
Availability | VoID file availability check for World War 1 as Linked Open Data took 0.0005848407745361328s
Extra | Recovery of all triples for World War 1 as Linked Open Data took 3.338113307952881s
Performance | Total latancy measurement for World War 1 as Linked Open Data took 0.7615303993225098s
Amount of data | Number of triples check for World War 1 as Linked Open Data took 0.24060344696044922s
Interoperability | New terms check for World War 1 as Linked Open Data took 3.080167770385742s
Versatility | Languages check for World War 1 as Linked Open Data took 0.45217323303222656s
Interpretability | Number of blank nodes check for World War 1 as Linked Open Data took 0.2198474407196045s
Security | Check HTTPS for World War 1 as Linked Open Data took 0.2148609161376953s
Interpretability | RDF structures check for World War 1 as Linked Open Data took 0.6827630996704102s
Versatility | Serialization formats check for World War 1 as Linked Open Data took 0.17820453643798828s
Availability | RDF dump link check for World War 1 as Linked Open Data took 6.653161525726318s
License | MR license check for World War 1 as Linked Open Data took 0.1736767292022705s
License | HR license check for World War 1 as Linked Open Data took 1.761908769607544s
Amount of data | Number of property check for World War 1 as Linked Open Data took 0.18471288681030273s
Understandability | Number of label check for World War 1 as Linked Open Data took 0.42574357986450195s
Understandability | URI regex check for World War 1 as Linked Open Data took 0.3196554183959961s
Understandability | Vocabs check for World War 1 as Linked Open Data took 0.2068920135498047s
Verifiability | Authors check for World War 1 as Linked Open Data took 0.17247533798217773s
Verifiability | Publishers check for World War 1 as Linked Open Data took 0.1659526824951172s
Performance | Throughput check for World War 1 as Linked Open Data took 10.294352293014526s
Amount of data | Check the number of entities for World War 1 as Linked Open Data took 0.07268691062927246s
Verifiability | Contribs. check for World War 1 as Linked Open Data took 0.1797504425048828s
Interlinking | sameAs chians check for World War 1 as Linked Open Data took 0.41390299797058105s
Interlinking | skos check for World War 1 as Linked Open Data took 0.16725802421569824s
Interlinking | skos check for World War 1 as Linked Open Data took 0.1454014778137207s
Timeliness | dataset update frequency check for World War 1 as Linked Open Data took 0.14092516899108887s
Currency | Creation date check for World War 1 as Linked Open Data took 0.331989049911499s
Currency | Modification date check for World War 1 as Linked Open Data took 0.18250298500061035s
Rep.Conc. | URIs length for World War 1 as Linked Open Data took 2.040536880493164s
Consistency | Deprecated classes/propertiers check for World War 1 as Linked Open Data took 0.16740059852600098s
Accuracy | Check Functional Property for World War 1 as Linked Open Data took 0.18103766441345215s
Accuracy | Check Inverse Functional Property for World War 1 as Linked Open Data took 0.1482088565826416s
Accuracy | Check Empty annotation labels for World War 1 as Linked Open Data took 1.0640504360198975s
Accuracy | Check White space in annotation for World War 1 as Linked Open Data took 0.05150651931762695s
Accuracy | Check Datatype consistency for World War 1 as Linked Open Data took 0.3192410469055176s
Consistency | Disjoint class check for World War 1 as Linked Open Data took 0.18044734001159668s
Consistency | Check Misplaced properties for World War 1 as Linked Open Data took 0.5611307621002197s
Consistency | Check Ontology hijacking for World War 1 as Linked Open Data took 1.9225785732269287s
Consistency | Check Invalid usage of undefined classes for World War 1 as Linked Open Data took 1.202181100845337s
Consistency | Check Invalid usage of undefined properties for World War 1 as Linked Open Data took 1.419917345046997s
Conciseness | Check Extensional conciseness for World War 1 as Linked Open Data took 0.19175457954406738s
Conciseness | Check Intensional conciseness for World War 1 as Linked Open Data took 1.0090527534484863s
Security | Sign check for World War 1 as Linked Open Data took 0.14864468574523926s
Availability | Check URIs Dereferenciability for World War 1 as Linked Open Data took 1769.6545479297638s
Completeness | Calculation of interlinking completeness for World War 1 as Linked Open Data took 1.4486346244812012s
Reputation | Calculation of the PageRank for World War 1 as Linked Open Data took 0.02101755142211914s
Interlinking | Calculation of Degree of Connection for World War 1 as Linked Open Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for World War 1 as Linked Open Data took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for World War 1 as Linked Open Data took 0.00017070770263671875s
Believability | Calculation of trust value for World War 1 as Linked Open Data took 9.059906005859375e-06s
INFO | --- Analysis for ww1lod took 1913.7051734924316s
Availability | SPARQL endpoint availability check for XlendiAmphorae took 4.363059997558594e-05s
Availability | VoID file availability check for XlendiAmphorae took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for XlendiAmphorae took 0.3019437789916992s
Reputation | Calculation of the PageRank for XlendiAmphorae took 0.020481109619140625s
Interlinking | Calculation of Degree of Connection for XlendiAmphorae took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for XlendiAmphorae took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for XlendiAmphorae took 3.337860107421875e-05s
Believability | Calculation of trust value for XlendiAmphorae took 6.4373016357421875e-06s
INFO | --- Analysis for xlendiamphorae took 5.204020261764526s
Availability | SPARQL endpoint availability check for xLiD-Lexica took 0.32364940643310547s
Availability | VoID file availability check for xLiD-Lexica took 0.0005538463592529297s
Completeness | Calculation of interlinking completeness for xLiD-Lexica took 0.28515052795410156s
Reputation | Calculation of the PageRank for xLiD-Lexica took 0.020741939544677734s
Interlinking | Calculation of Degree of Connection for xLiD-Lexica took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for xLiD-Lexica took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for xLiD-Lexica took 7.176399230957031e-05s
Believability | Calculation of trust value for xLiD-Lexica took 6.4373016357421875e-06s
INFO | --- Analysis for xlid-lexica took 4.913149118423462s
Availability | SPARQL endpoint availability check for Open Multilingual Wordnet took 4.38690185546875e-05s
Availability | VoID file availability check for Open Multilingual Wordnet took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for Open Multilingual Wordnet took 0.6954214572906494s
Reputation | Calculation of the PageRank for Open Multilingual Wordnet took 0.02065134048461914s
Interlinking | Calculation of Degree of Connection for Open Multilingual Wordnet took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Multilingual Wordnet took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for Open Multilingual Wordnet took 3.886222839355469e-05s
Believability | Calculation of trust value for Open Multilingual Wordnet took 6.4373016357421875e-06s
INFO | --- Analysis for xwn took 3.9697368144989014s
Availability | SPARQL endpoint availability check for xxx took 4.9114227294921875e-05s
Availability | VoID file availability check for xxx took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for xxx took 0.2918055057525635s
Reputation | Calculation of the PageRank for xxx took 0.020551443099975586s
Interlinking | Calculation of Degree of Connection for xxx took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for xxx took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for xxx took 3.0040740966796875e-05s
Believability | Calculation of trust value for xxx took 7.3909759521484375e-06s
INFO | --- Analysis for xx took 2.547266960144043s
Availability | SPARQL endpoint availability check for YAGO took 4.1961669921875e-05s
Availability | VoID file availability check for YAGO took 0.0006957054138183594s
Completeness | Calculation of interlinking completeness for YAGO took 0.2860989570617676s
Reputation | Calculation of the PageRank for YAGO took 0.020381689071655273s
Interlinking | Calculation of Degree of Connection for YAGO took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for YAGO took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for YAGO took 0.00013494491577148438s
Believability | Calculation of trust value for YAGO took 7.867813110351562e-06s
INFO | --- Analysis for yago took 6.955256938934326s
Availability | SPARQL endpoint availability check for Yahoo Geoplanet RDF took 1.8074367046356201s
Availability | VoID file availability check for Yahoo Geoplanet RDF took 0.00077056884765625s
Completeness | Calculation of interlinking completeness for Yahoo Geoplanet RDF took 0.26164984703063965s
Reputation | Calculation of the PageRank for Yahoo Geoplanet RDF took 0.02062392234802246s
Interlinking | Calculation of Degree of Connection for Yahoo Geoplanet RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Yahoo Geoplanet RDF took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for Yahoo Geoplanet RDF took 7.987022399902344e-05s
Believability | Calculation of trust value for Yahoo Geoplanet RDF took 8.106231689453125e-06s
INFO | --- Analysis for yahoo_geoplanet took 11.713002920150757s
Availability | SPARQL endpoint availability check for Yale Senselab took 0.1831679344177246s
Availability | VoID file availability check for Yale Senselab took 0.000553131103515625s
Completeness | Calculation of interlinking completeness for Yale Senselab took 0.28613758087158203s
Reputation | Calculation of the PageRank for Yale Senselab took 0.020511865615844727s
Interlinking | Calculation of Degree of Connection for Yale Senselab took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Yale Senselab took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Yale Senselab took 3.0279159545898438e-05s
Believability | Calculation of trust value for Yale Senselab took 5.0067901611328125e-06s
INFO | --- Analysis for yale_senselab took 11.118191957473755s
Availability | SPARQL endpoint availability check for test-dapp-2 took 4.1961669921875e-05s
Availability | VoID file availability check for test-dapp-2 took 0.0002334117889404297s
Completeness | Calculation of interlinking completeness for test-dapp-2 took 0.30615758895874023s
Reputation | Calculation of the PageRank for test-dapp-2 took 0.020627737045288086s
Interlinking | Calculation of Degree of Connection for test-dapp-2 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for test-dapp-2 took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for test-dapp-2 took 3.0040740966796875e-05s
Believability | Calculation of trust value for test-dapp-2 took 5.7220458984375e-06s
INFO | --- Analysis for yordhis took 2.481271982192993s
Availability | SPARQL endpoint availability check for Yovisto - academic video search took 0.9961233139038086s
Availability | VoID file availability check for Yovisto - academic video search took 0.0006310939788818359s
Completeness | Calculation of interlinking completeness for Yovisto - academic video search took 0.26685094833374023s
Reputation | Calculation of the PageRank for Yovisto - academic video search took 0.020551443099975586s
Interlinking | Calculation of Degree of Connection for Yovisto - academic video search took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Yovisto - academic video search took 0.0010159015655517578s
Interlinking | Calculation of Clustering coefficient for Yovisto - academic video search took 8.678436279296875e-05s
Believability | Calculation of trust value for Yovisto - academic video search took 5.7220458984375e-06s
INFO | --- Analysis for yovisto took 32.9456844329834s
Availability | SPARQL endpoint availability check for Yleinen suomalainen asiasanasto - YSA took 4.172325134277344e-05s
Availability | VoID file availability check for Yleinen suomalainen asiasanasto - YSA took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for Yleinen suomalainen asiasanasto - YSA took 0.28511548042297363s
Reputation | Calculation of the PageRank for Yleinen suomalainen asiasanasto - YSA took 0.020353317260742188s
Interlinking | Calculation of Degree of Connection for Yleinen suomalainen asiasanasto - YSA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Yleinen suomalainen asiasanasto - YSA took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Yleinen suomalainen asiasanasto - YSA took 3.075599670410156e-05s
Believability | Calculation of trust value for Yleinen suomalainen asiasanasto - YSA took 5.7220458984375e-06s
INFO | --- Analysis for ysa took 3.501805067062378s
Availability | SPARQL endpoint availability check for YSO - General Finnish Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for YSO - General Finnish Ontology took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for YSO - General Finnish Ontology took 0.26370930671691895s
Reputation | Calculation of the PageRank for YSO - General Finnish Ontology took 0.021042585372924805s
Interlinking | Calculation of Degree of Connection for YSO - General Finnish Ontology took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for YSO - General Finnish Ontology took 0.001264810562133789s
Interlinking | Calculation of Clustering coefficient for YSO - General Finnish Ontology took 8.225440979003906e-05s
Believability | Calculation of trust value for YSO - General Finnish Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for yso took 3.807486057281494s
Availability | SPARQL endpoint availability check for yso-fi-allars took 4.696846008300781e-05s
Availability | VoID file availability check for yso-fi-allars took 0.0005464553833007812s
Completeness | Calculation of interlinking completeness for yso-fi-allars took 0.2665822505950928s
Reputation | Calculation of the PageRank for yso-fi-allars took 0.02029561996459961s
Interlinking | Calculation of Degree of Connection for yso-fi-allars took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for yso-fi-allars took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for yso-fi-allars took 3.075599670410156e-05s
Believability | Calculation of trust value for yso-fi-allars took 6.198883056640625e-06s
INFO | --- Analysis for yso-fi-allars took 2.8380703926086426s
Availability | SPARQL endpoint availability check for yso-fi-ysa took 4.2438507080078125e-05s
Availability | VoID file availability check for yso-fi-ysa took 0.0005757808685302734s
Completeness | Calculation of interlinking completeness for yso-fi-ysa took 0.2653391361236572s
Reputation | Calculation of the PageRank for yso-fi-ysa took 0.02033686637878418s
Interlinking | Calculation of Degree of Connection for yso-fi-ysa took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for yso-fi-ysa took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for yso-fi-ysa took 5.364418029785156e-05s
Believability | Calculation of trust value for yso-fi-ysa took 7.3909759521484375e-06s
INFO | --- Analysis for yso-fi-ysa took 3.2226574420928955s
Availability | SPARQL endpoint availability check for YSO places took 2.755342721939087s
Availability | VoID file availability check for YSO places took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for YSO places took 0.27676916122436523s
Reputation | Calculation of the PageRank for YSO places took 0.020140409469604492s
Interlinking | Calculation of Degree of Connection for YSO places took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for YSO places took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for YSO places took 2.7179718017578125e-05s
Believability | Calculation of trust value for YSO places took 6.4373016357421875e-06s
INFO | --- Analysis for yso-paikat took 6.5482892990112305s
Availability | SPARQL endpoint availability check for Datos Abiertos de Zaragoza took 4.172325134277344e-05s
Availability | VoID file availability check for Datos Abiertos de Zaragoza took 0.0005929470062255859s
Completeness | Calculation of interlinking completeness for Datos Abiertos de Zaragoza took 0.25412821769714355s
Reputation | Calculation of the PageRank for Datos Abiertos de Zaragoza took 0.02066636085510254s
Interlinking | Calculation of Degree of Connection for Datos Abiertos de Zaragoza took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Datos Abiertos de Zaragoza took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Datos Abiertos de Zaragoza took 3.2901763916015625e-05s
Believability | Calculation of trust value for Datos Abiertos de Zaragoza took 5.0067901611328125e-06s
INFO | --- Analysis for zaragoza-datosabiertos took 6.683234691619873s
Availability | SPARQL endpoint availability check for zaragoza_turruta took 4.1484832763671875e-05s
Availability | VoID file availability check for zaragoza_turruta took 0.000637054443359375s
Completeness | Calculation of interlinking completeness for zaragoza_turruta took 0.2650890350341797s
Reputation | Calculation of the PageRank for zaragoza_turruta took 0.020273208618164062s
Interlinking | Calculation of Degree of Connection for zaragoza_turruta took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for zaragoza_turruta took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for zaragoza_turruta took 3.337860107421875e-05s
Believability | Calculation of trust value for zaragoza_turruta took 5.9604644775390625e-06s
INFO | --- Analysis for zaragoza_turruta took 2.5833656787872314s
Availability | SPARQL endpoint availability check for ZBW Labs took 4.2438507080078125e-05s
Availability | VoID file availability check for ZBW Labs took 0.0006113052368164062s
Completeness | Calculation of interlinking completeness for ZBW Labs took 0.26477718353271484s
Reputation | Calculation of the PageRank for ZBW Labs took 0.02036595344543457s
Interlinking | Calculation of Degree of Connection for ZBW Labs took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ZBW Labs took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for ZBW Labs took 9.584426879882812e-05s
Believability | Calculation of trust value for ZBW Labs took 5.4836273193359375e-06s
INFO | --- Analysis for zbw-labs took 3.4137721061706543s
Availability | SPARQL endpoint availability check for 20th Century Press Archives took 0.18086576461791992s
Availability | VoID file availability check for 20th Century Press Archives took 0.0005660057067871094s
Extra | Recovery of all triples for 20th Century Press Archives took 633.6210501194s
Performance | Total latancy measurement for 20th Century Press Archives took 0.8566551208496094s
Amount of data | Number of triples check for 20th Century Press Archives took 1.7256050109863281s
Interoperability | New terms check for 20th Century Press Archives took 1.6396400928497314s
Versatility | Languages check for 20th Century Press Archives took 5.557964086532593s
Interpretability | Number of blank nodes check for 20th Century Press Archives took 0.9189932346343994s
Interpretability | RDF structures check for 20th Century Press Archives took 0.16392302513122559s
Versatility | Serialization formats check for 20th Century Press Archives took 0.1567363739013672s
Availability | RDF dump link check for 20th Century Press Archives took 0.1627483367919922s
License | MR license check for 20th Century Press Archives took 0.13066792488098145s
License | HR license check for 20th Century Press Archives took 4.94844388961792s
Amount of data | Number of property check for 20th Century Press Archives took 0.1618349552154541s
Understandability | Number of label check for 20th Century Press Archives took 0.5569629669189453s
Understandability | URI regex check for 20th Century Press Archives took 0.257615327835083s
Understandability | Vocabs check for 20th Century Press Archives took 0.12454652786254883s
Verifiability | Authors check for 20th Century Press Archives took 0.12719082832336426s
Verifiability | Publishers check for 20th Century Press Archives took 0.18086671829223633s
Performance | Throughput check for 20th Century Press Archives took 10.669140338897705s
Amount of data | Check the number of entities for 20th Century Press Archives took 8.487701416015625e-05s
Verifiability | Contribs. check for 20th Century Press Archives took 0.15713763236999512s
Interlinking | sameAs chians check for 20th Century Press Archives took 0.14287805557250977s
Interlinking | skos check for 20th Century Press Archives took 0.1870253086090088s
Interlinking | skos check for 20th Century Press Archives took 0.1751270294189453s
Timeliness | dataset update frequency check for 20th Century Press Archives took 0.1727921962738037s
Currency | Creation date check for 20th Century Press Archives took 0.33275341987609863s
Currency | Modification date check for 20th Century Press Archives took 0.33051085472106934s
Rep.Conc. | URIs length for 20th Century Press Archives took 114.42882823944092s
Interoperability | New vocabularies check for 20th Century Press Archives took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for 20th Century Press Archives took 0.2112598419189453s
Accuracy | Check Functional Property for 20th Century Press Archives took 0.12999439239501953s
Accuracy | Check Inverse Functional Property for 20th Century Press Archives took 0.14278602600097656s
Accuracy | Check Empty annotation labels for 20th Century Press Archives took 53.71295118331909s
Accuracy | Check White space in annotation for 20th Century Press Archives took 0.903400182723999s
Accuracy | Check Datatype consistency for 20th Century Press Archives took 4.113861799240112s
Consistency | Disjoint class check for 20th Century Press Archives took 0.1825542449951172s
Consistency | Check Misplaced properties for 20th Century Press Archives took 2.0931460857391357s
Consistency | Check Ontology hijacking for 20th Century Press Archives took 13.933075428009033s
Consistency | Check Invalid usage of undefined classes for 20th Century Press Archives took 7.377961874008179s
Consistency | Check Invalid usage of undefined properties for 20th Century Press Archives took 3.218921422958374s
Conciseness | Check Extensional conciseness for 20th Century Press Archives took 2.7745070457458496s
Security | Sign check for 20th Century Press Archives took 0.15340113639831543s
Availability | Check URIs Dereferenciability for 20th Century Press Archives took 1013.5885546207428s
Completeness | Calculation of interlinking completeness for 20th Century Press Archives took 0.3094942569732666s
Reputation | Calculation of the PageRank for 20th Century Press Archives took 0.021271228790283203s
Interlinking | Calculation of Degree of Connection for 20th Century Press Archives took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for 20th Century Press Archives took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for 20th Century Press Archives took 0.0001227855682373047s
Interoperability | Check the re-using of existing vocabs for 20th Century Press Archives took 1.9073486328125e-06s
Believability | Calculation of trust value for 20th Century Press Archives took 1.0728836059570312e-05s
INFO | --- Analysis for zbw-pressemappe20 took 1902.2257523536682s
Availability | SPARQL endpoint availability check for zhishi.lemon took 4.363059997558594e-05s
Availability | VoID file availability check for zhishi.lemon took 0.0007495880126953125s
Completeness | Calculation of interlinking completeness for zhishi.lemon took 0.2857859134674072s
Reputation | Calculation of the PageRank for zhishi.lemon took 0.020798444747924805s
Interlinking | Calculation of Degree of Connection for zhishi.lemon took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for zhishi.lemon took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for zhishi.lemon took 5.125999450683594e-05s
Believability | Calculation of trust value for zhishi.lemon took 7.152557373046875e-06s
INFO | --- Analysis for zhishi-lemon took 23.817030429840088s
Availability | SPARQL endpoint availability check for Zhishi.me took 2.5034024715423584s
Availability | VoID file availability check for Zhishi.me took 0.0005331039428710938s
Completeness | Calculation of interlinking completeness for Zhishi.me took 0.26996445655822754s
Reputation | Calculation of the PageRank for Zhishi.me took 0.020799636840820312s
Interlinking | Calculation of Degree of Connection for Zhishi.me took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Zhishi.me took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Zhishi.me took 7.152557373046875e-05s
Believability | Calculation of trust value for Zhishi.me took 7.152557373046875e-06s
INFO | --- Analysis for zhishi-me took 10.977735757827759s
Availability | SPARQL endpoint availability check for MusicBrainz (zitgist.com) took 4.315376281738281e-05s
Availability | VoID file availability check for MusicBrainz (zitgist.com) took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for MusicBrainz (zitgist.com) took 0.272367000579834s
Reputation | Calculation of the PageRank for MusicBrainz (zitgist.com) took 0.02045416831970215s
Interlinking | Calculation of Degree of Connection for MusicBrainz (zitgist.com) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MusicBrainz (zitgist.com) took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for MusicBrainz (zitgist.com) took 5.817413330078125e-05s
Believability | Calculation of trust value for MusicBrainz (zitgist.com) took 7.3909759521484375e-06s
INFO | --- Analysis for zitgist-musicbrainz took 2.8277289867401123s
Availability | SPARQL endpoint availability check for 红色经典歌曲关联数据集 took 4.363059997558594e-05s
Availability | VoID file availability check for 红色经典歌曲关联数据集 took 0.0005905628204345703s
Completeness | Calculation of interlinking completeness for 红色经典歌曲关联数据集 took 0.26082301139831543s
Reputation | Calculation of the PageRank for 红色经典歌曲关联数据集 took 0.02029275894165039s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲关联数据集 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for 红色经典歌曲关联数据集 took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲关联数据集 took 2.956390380859375e-05s
Believability | Calculation of trust value for 红色经典歌曲关联数据集 took 6.9141387939453125e-06s
INFO | --- Analysis for 红色经典歌曲关联数据集 took 2.7098050117492676s
Availability | SPARQL endpoint availability check for performing-arts.ch took 0.25549912452697754s
Availability | VoID file availability check for performing-arts.ch took 0.00029015541076660156s
Extra | Recovery of all triples for performing-arts.ch took 13.349101543426514s
Performance | Total latancy measurement for performing-arts.ch took 0.6127269268035889s
Amount of data | Number of triples check for performing-arts.ch took 25.03792667388916s
Interoperability | New terms check for performing-arts.ch took 1.428006649017334s
Versatility | Languages check for performing-arts.ch took 60.11446166038513s
Interpretability | Number of blank nodes check for performing-arts.ch took 0.10273551940917969s
Interpretability | RDF structures check for performing-arts.ch took 0.1034402847290039s
Versatility | Serialization formats check for performing-arts.ch took 0.10326290130615234s
Availability | RDF dump link check for performing-arts.ch took 0.10604715347290039s
License | MR license check for performing-arts.ch took 0.1195821762084961s
License | HR license check for performing-arts.ch took 0.11457324028015137s
Amount of data | Number of property check for performing-arts.ch took 0.10266423225402832s
Understandability | Number of label check for performing-arts.ch took 0.09231138229370117s
Understandability | URI regex check for performing-arts.ch took 0.19471502304077148s
Understandability | Vocabs check for performing-arts.ch took 0.11522579193115234s
Verifiability | Authors check for performing-arts.ch took 0.10085725784301758s
Verifiability | Publishers check for performing-arts.ch took 0.10253167152404785s
Amount of data | Check the number of entities for performing-arts.ch took 0.0001442432403564453s
Verifiability | Contribs. check for performing-arts.ch took 0.11277174949645996s
Interlinking | sameAs chians check for performing-arts.ch took 0.11439061164855957s
Interlinking | skos check for performing-arts.ch took 0.0922544002532959s
Interlinking | skos check for performing-arts.ch took 0.10227060317993164s
Timeliness | dataset update frequency check for performing-arts.ch took 0.10396313667297363s
Currency | Creation date check for performing-arts.ch took 0.20676445960998535s
Currency | Modification date check for performing-arts.ch took 0.20615887641906738s
Rep.Conc. | URIs length for performing-arts.ch took 3.688800573348999s
Interoperability | New vocabularies check for performing-arts.ch took 2.384185791015625e-07s
Consistency | Deprecated classes/propertiers check for performing-arts.ch took 0.09908533096313477s
Accuracy | Check Datatype consistency for performing-arts.ch took 5.968924283981323s
Consistency | Disjoint class check for performing-arts.ch took 0.10550069808959961s
Consistency | Check Misplaced properties for performing-arts.ch took 0.45279788970947266s
Consistency | Misplaced classes for performing-arts.ch took 8.708206176757812s
Consistency | Check Ontology hijacking for performing-arts.ch took 24.45846939086914s
Consistency | Check Invalid usage of undefined classes for performing-arts.ch took 15947.336240768433s
Consistency | Check Invalid usage of undefined properties for performing-arts.ch took 1.4130408763885498s
Conciseness | Check Extensional conciseness for performing-arts.ch took 2.880096673965454s
Conciseness | Check Intensional conciseness for performing-arts.ch took 0.24408459663391113s
Security | Sign check for performing-arts.ch took 0.12343406677246094s
Availability | Check URIs Dereferenciability for performing-arts.ch took 3.3101444244384766s
Completeness | Calculation of interlinking completeness for performing-arts.ch took 0.3110535144805908s
Reputation | Calculation of the PageRank for performing-arts.ch took 0.020217418670654297s
Interlinking | Calculation of Degree of Connection for performing-arts.ch took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for performing-arts.ch took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for performing-arts.ch took 2.193450927734375e-05s
Interoperability | Check the re-using of existing vocabs for performing-arts.ch took 7.152557373046875e-07s
Believability | Calculation of trust value for performing-arts.ch took 6.198883056640625e-06s
INFO | --- Analysis for performing-arts.ch took 16170.205201864243s
Availability | SPARQL endpoint availability check for The Art & Architecture Thesaurus took 14.409515857696533s
Availability | VoID file availability check for The Art & Architecture Thesaurus took 0.0003635883331298828s
Completeness | Calculation of interlinking completeness for The Art & Architecture Thesaurus took 0.2605781555175781s
Reputation | Calculation of the PageRank for The Art & Architecture Thesaurus took 0.020002365112304688s
Interlinking | Calculation of Degree of Connection for The Art & Architecture Thesaurus took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for The Art & Architecture Thesaurus took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for The Art & Architecture Thesaurus took 1.7404556274414062e-05s
Believability | Calculation of trust value for The Art & Architecture Thesaurus took 6.198883056640625e-06s
INFO | --- Analysis for The-AA-Thesaurus took 42.83845329284668s
Availability | SPARQL endpoint availability check for MiMoTextBase took 1.9206740856170654s
Availability | VoID file availability check for MiMoTextBase took 0.0006895065307617188s
Completeness | Calculation of interlinking completeness for MiMoTextBase took 0.2796173095703125s
Reputation | Calculation of the PageRank for MiMoTextBase took 0.020084857940673828s
Interlinking | Calculation of Degree of Connection for MiMoTextBase took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for MiMoTextBase took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for MiMoTextBase took 1.1205673217773438e-05s
Believability | Calculation of trust value for MiMoTextBase took 6.67572021484375e-06s
INFO | --- Analysis for MiMoTextBase took 6.736733436584473s
Availability | SPARQL endpoint availability check for National Library of Sweden took 0.5849781036376953s
Availability | VoID file availability check for National Library of Sweden took 0.0007109642028808594s
Extra | Recovery of all triples for National Library of Sweden took 5.301034927368164s
Performance | Total latancy measurement for National Library of Sweden took 0.9383275508880615s
Amount of data | Number of triples check for National Library of Sweden took 23.66220760345459s
Interoperability | New terms check for National Library of Sweden took 16.399240016937256s
Versatility | Languages check for National Library of Sweden took 0.21561002731323242s
Interpretability | Number of blank nodes check for National Library of Sweden took 300.1945209503174s
Interpretability | RDF structures check for National Library of Sweden took 0.3281102180480957s
Versatility | Serialization formats check for National Library of Sweden took 0.26752305030822754s
Availability | RDF dump link check for National Library of Sweden took 0.19598603248596191s
License | MR license check for National Library of Sweden took 0.28296732902526855s
License | HR license check for National Library of Sweden took 0.24897527694702148s
Amount of data | Number of property check for National Library of Sweden took 0.20047569274902344s
Understandability | Number of label check for National Library of Sweden took 0.4235405921936035s
Understandability | URI regex check for National Library of Sweden took 0.43604350090026855s
Understandability | Vocabs check for National Library of Sweden took 0.20734310150146484s
Verifiability | Authors check for National Library of Sweden took 0.23154354095458984s
Verifiability | Publishers check for National Library of Sweden took 0.21084308624267578s
Performance | Throughput check for National Library of Sweden took 11.427495002746582s
Amount of data | Check the number of entities for National Library of Sweden took 7.033348083496094e-05s
Verifiability | Contribs. check for National Library of Sweden took 0.2087879180908203s
Interlinking | sameAs chians check for National Library of Sweden took 0.26088428497314453s
Interlinking | skos check for National Library of Sweden took 0.3022301197052002s
Interlinking | skos check for National Library of Sweden took 0.20673441886901855s
Timeliness | dataset update frequency check for National Library of Sweden took 0.2037649154663086s
Currency | Creation date check for National Library of Sweden took 0.3989419937133789s
Currency | Modification date check for National Library of Sweden took 0.40170979499816895s
Rep.Conc. | URIs length for National Library of Sweden took 82.30283427238464s
Interoperability | New vocabularies check for National Library of Sweden took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for National Library of Sweden took 0.18366241455078125s
Accuracy | Check Functional Property for National Library of Sweden took 0.19449687004089355s
Accuracy | Check Inverse Functional Property for National Library of Sweden took 0.2048356533050537s
Accuracy | Check Datatype consistency for National Library of Sweden took 0.26434946060180664s
Consistency | Disjoint class check for National Library of Sweden took 0.20514440536499023s
Consistency | Check Misplaced properties for National Library of Sweden took 62.25720000267029s
Consistency | Misplaced classes for National Library of Sweden took 1.1437397003173828s
Consistency | Check Ontology hijacking for National Library of Sweden took 3.2843403816223145s
Consistency | Check Invalid usage of undefined classes for National Library of Sweden took 1.142284631729126s
Consistency | Check Invalid usage of undefined properties for National Library of Sweden took 63.06784272193909s
Conciseness | Check Extensional conciseness for National Library of Sweden took 0.2750236988067627s
Conciseness | Check Intensional conciseness for National Library of Sweden took 0.3557305335998535s
Security | Sign check for National Library of Sweden took 0.27526187896728516s
Availability | Check URIs Dereferenciability for National Library of Sweden took 5.415603876113892s
Completeness | Calculation of interlinking completeness for National Library of Sweden took 0.2679729461669922s
Reputation | Calculation of the PageRank for National Library of Sweden took 0.01997065544128418s
Interlinking | Calculation of Degree of Connection for National Library of Sweden took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for National Library of Sweden took 0.0006783008575439453s
Interlinking | Calculation of Clustering coefficient for National Library of Sweden took 1.1205673217773438e-05s
Interoperability | Check the re-using of existing vocabs for National Library of Sweden took 1.6689300537109375e-06s
Believability | Calculation of trust value for National Library of Sweden took 1.6927719116210938e-05s
INFO | --- Analysis for NLS took 1354.4374849796295s
Availability | SPARQL endpoint availability check for Japan Search took 1.6497604846954346s
Availability | VoID file availability check for Japan Search took 0.00025725364685058594s
Extra | Recovery of all triples for Japan Search took 3.25593638420105s
Performance | Total latancy measurement for Japan Search took 1.495086431503296s
Amount of data | Number of triples check for Japan Search took 20.982568502426147s
Interoperability | New terms check for Japan Search took 3.30712890625s
Versatility | Languages check for Japan Search took 91.73455238342285s
Interpretability | Number of blank nodes check for Japan Search took 91.46147298812866s
Interpretability | RDF structures check for Japan Search took 1.1594390869140625s
Versatility | Serialization formats check for Japan Search took 0.849370002746582s
Availability | RDF dump link check for Japan Search took 0.5176560878753662s
License | MR license check for Japan Search took 1.4369184970855713s
License | HR license check for Japan Search took 90.94970059394836s
Amount of data | Number of property check for Japan Search took 0.8215630054473877s
Understandability | Number of label check for Japan Search took 5.07412314414978s
Understandability | URI regex check for Japan Search took 0.5951917171478271s
Understandability | Vocabs check for Japan Search took 0.298978328704834s
Verifiability | Authors check for Japan Search took 0.4217722415924072s
Verifiability | Publishers check for Japan Search took 0.31241703033447266s
Performance | Throughput check for Japan Search took 11.324766159057617s
Amount of data | Check the number of entities for Japan Search took 7.367134094238281e-05s
Verifiability | Contribs. check for Japan Search took 0.30032825469970703s
Interlinking | sameAs chians check for Japan Search took 0.270780086517334s
Interlinking | skos check for Japan Search took 0.33458924293518066s
Interlinking | skos check for Japan Search took 0.2698960304260254s
Timeliness | dataset update frequency check for Japan Search took 0.6094295978546143s
Currency | Creation date check for Japan Search took 0.5901961326599121s
Currency | Modification date check for Japan Search took 0.5598254203796387s
Rep.Conc. | URIs length for Japan Search took 31.22884202003479s
Interoperability | New vocabularies check for Japan Search took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for Japan Search took 0.3229482173919678s
Accuracy | Check Functional Property for Japan Search took 0.4615778923034668s
Accuracy | Check Inverse Functional Property for Japan Search took 0.4646761417388916s
Accuracy | Check Empty annotation labels for Japan Search took 2.1344051361083984s
Accuracy | Check White space in annotation for Japan Search took 0.03241276741027832s
Accuracy | Check Datatype consistency for Japan Search took 0.028914451599121094s
Consistency | Disjoint class check for Japan Search took 0.28200769424438477s
Consistency | Check Misplaced properties for Japan Search took 27.93886113166809s
Consistency | Misplaced classes for Japan Search took 0.38361382484436035s
Consistency | Check Ontology hijacking for Japan Search took 1.8605899810791016s
Consistency | Check Invalid usage of undefined classes for Japan Search took 1.294013500213623s
Consistency | Check Invalid usage of undefined properties for Japan Search took 28.980468273162842s
Conciseness | Check Extensional conciseness for Japan Search took 0.03428339958190918s
Conciseness | Check Intensional conciseness for Japan Search took 1.0638511180877686s
Security | Sign check for Japan Search took 0.2947347164154053s
Availability | Check URIs Dereferenciability for Japan Search took 6.578208923339844s
Completeness | Calculation of interlinking completeness for Japan Search took 0.2574944496154785s
Reputation | Calculation of the PageRank for Japan Search took 0.020895957946777344s
Interlinking | Calculation of Degree of Connection for Japan Search took 4.3392181396484375e-05s
Interlinking | Calculation of Centrality for Japan Search took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Japan Search took 1.621246337890625e-05s
Interoperability | Check the re-using of existing vocabs for Japan Search took 1.6689300537109375e-06s
Believability | Calculation of trust value for Japan Search took 6.67572021484375e-06s
INFO | --- Analysis for Japan-Search took 819.6842772960663s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection took 0.7119498252868652s
Availability | VoID file availability check for Rijksmuseum Collection took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection took 0.27506089210510254s
Reputation | Calculation of the PageRank for Rijksmuseum Collection took 0.019968509674072266s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection took 0.0006840229034423828s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection took 1.1920928955078125e-05s
Believability | Calculation of trust value for Rijksmuseum Collection took 7.62939453125e-06s
INFO | --- Analysis for Rijksmuseum took 4.0996575355529785s
Availability | SPARQL endpoint availability check for Finnish Public Libraries took 0.5548434257507324s
Availability | VoID file availability check for Finnish Public Libraries took 0.0010123252868652344s
Completeness | Calculation of interlinking completeness for Finnish Public Libraries took 0.2590341567993164s
Reputation | Calculation of the PageRank for Finnish Public Libraries took 0.020633459091186523s
Interlinking | Calculation of Degree of Connection for Finnish Public Libraries took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Finnish Public Libraries took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Finnish Public Libraries took 1.4543533325195312e-05s
Believability | Calculation of trust value for Finnish Public Libraries took 5.9604644775390625e-06s
INFO | --- Analysis for FI-Library took 4.336244821548462s
Availability | SPARQL endpoint availability check for Shanghai Library Open Data Platform took 3.9210364818573s
Availability | VoID file availability check for Shanghai Library Open Data Platform took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for Shanghai Library Open Data Platform took 0.2580115795135498s
Reputation | Calculation of the PageRank for Shanghai Library Open Data Platform took 0.020298004150390625s
Interlinking | Calculation of Degree of Connection for Shanghai Library Open Data Platform took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Shanghai Library Open Data Platform took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Shanghai Library Open Data Platform took 1.3113021850585938e-05s
Believability | Calculation of trust value for Shanghai Library Open Data Platform took 7.152557373046875e-06s
INFO | --- Analysis for Shanghai-Library-Open-Data-Platform took 9.267908573150635s
Availability | SPARQL endpoint availability check for National Library Netherlands took 1.618088960647583s
Availability | VoID file availability check for National Library Netherlands took 0.0006916522979736328s
Completeness | Calculation of interlinking completeness for National Library Netherlands took 0.2598302364349365s
Reputation | Calculation of the PageRank for National Library Netherlands took 0.020297527313232422s
Interlinking | Calculation of Degree of Connection for National Library Netherlands took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for National Library Netherlands took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for National Library Netherlands took 1.3828277587890625e-05s
Believability | Calculation of trust value for National Library Netherlands took 6.4373016357421875e-06s
INFO | --- Analysis for National-Library-Netherlands took 8.486266136169434s
Availability | SPARQL endpoint availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.7620453834533691s
Availability | VoID file availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0005888938903808594s
Completeness | Calculation of interlinking completeness for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.27942395210266113s
Reputation | Calculation of the PageRank for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.020444631576538086s
Interlinking | Calculation of Degree of Connection for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.3113021850585938e-05s
Believability | Calculation of trust value for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 6.198883056640625e-06s
INFO | --- Analysis for Antique-Renaissance took 5.866804361343384s
Availability | SPARQL endpoint availability check for ARTSDATA.CA took 4.102508306503296s
Availability | VoID file availability check for ARTSDATA.CA took 0.00032067298889160156s
Completeness | Calculation of interlinking completeness for ARTSDATA.CA took 0.2662041187286377s
Reputation | Calculation of the PageRank for ARTSDATA.CA took 0.02033066749572754s
Interlinking | Calculation of Degree of Connection for ARTSDATA.CA took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for ARTSDATA.CA took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for ARTSDATA.CA took 1.1920928955078125e-05s
Believability | Calculation of trust value for ARTSDATA.CA took 5.245208740234375e-06s
INFO | --- Analysis for ARTSDATA-CA took 9.51797342300415s
Availability | SPARQL endpoint availability check for Architecture of Knowledge took 0.10573148727416992s
Availability | VoID file availability check for Architecture of Knowledge took 0.0005161762237548828s
Extra | Recovery of all triples for Architecture of Knowledge took 60.175047159194946s
Performance | Total latancy measurement for Architecture of Knowledge took 0.3758547306060791s
Amount of data | Number of triples check for Architecture of Knowledge took 5.585319519042969s
Interoperability | New terms check for Architecture of Knowledge took 5.291933536529541s
Versatility | Languages check for Architecture of Knowledge took 60.14549970626831s
Interpretability | Number of blank nodes check for Architecture of Knowledge took 0.06974124908447266s
Interpretability | RDF structures check for Architecture of Knowledge took 0.07345008850097656s
Versatility | Serialization formats check for Architecture of Knowledge took 0.07206940650939941s
Availability | RDF dump link check for Architecture of Knowledge took 0.037557125091552734s
License | MR license check for Architecture of Knowledge took 0.143812894821167s
License | HR license check for Architecture of Knowledge took 60.14516639709473s
Amount of data | Number of property check for Architecture of Knowledge took 0.07058978080749512s
Understandability | Number of label check for Architecture of Knowledge took 1.838796615600586s
Understandability | URI regex check for Architecture of Knowledge took 0.07001471519470215s
Understandability | Vocabs check for Architecture of Knowledge took 0.03473353385925293s
Verifiability | Authors check for Architecture of Knowledge took 0.06822538375854492s
Verifiability | Publishers check for Architecture of Knowledge took 0.035529136657714844s
Performance | Throughput check for Architecture of Knowledge took 11.451268196105957s
Amount of data | Check the number of entities for Architecture of Knowledge took 0.00010442733764648438s
Verifiability | Contribs. check for Architecture of Knowledge took 0.12044858932495117s
Interlinking | sameAs chians check for Architecture of Knowledge took 0.07430839538574219s
Interlinking | skos check for Architecture of Knowledge took 0.23648715019226074s
Interlinking | skos check for Architecture of Knowledge took 0.05261731147766113s
Timeliness | dataset update frequency check for Architecture of Knowledge took 0.04211878776550293s
Currency | Creation date check for Architecture of Knowledge took 0.28063440322875977s
Currency | Modification date check for Architecture of Knowledge took 0.24577689170837402s
Rep.Conc. | URIs length for Architecture of Knowledge took 87.98510408401489s
Interoperability | New vocabularies check for Architecture of Knowledge took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Architecture of Knowledge took 0.06902313232421875s
Accuracy | Check Functional Property for Architecture of Knowledge took 0.11852455139160156s
Accuracy | Check Inverse Functional Property for Architecture of Knowledge took 0.08781075477600098s
Accuracy | Check Empty annotation labels for Architecture of Knowledge took 49.13542413711548s
Accuracy | Check White space in annotation for Architecture of Knowledge took 3.1033618450164795s
Consistency | Disjoint class check for Architecture of Knowledge took 0.26155948638916016s
Consistency | Check Misplaced properties for Architecture of Knowledge took 30.41781449317932s
Consistency | Misplaced classes for Architecture of Knowledge took 0.11291003227233887s
Consistency | Check Ontology hijacking for Architecture of Knowledge took 40.529592514038086s
Consistency | Check Invalid usage of undefined properties for Architecture of Knowledge took 30.659857988357544s
Conciseness | Check Extensional conciseness for Architecture of Knowledge took 0.00014781951904296875s
Conciseness | Check Intensional conciseness for Architecture of Knowledge took 0.11840033531188965s
Security | Sign check for Architecture of Knowledge took 0.7458920478820801s
Completeness | Calculation of interlinking completeness for Architecture of Knowledge took 0.3259296417236328s
Reputation | Calculation of the PageRank for Architecture of Knowledge took 0.020901918411254883s
Interlinking | Calculation of Degree of Connection for Architecture of Knowledge took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Architecture of Knowledge took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Architecture of Knowledge took 1.6450881958007812e-05s
Interoperability | Check the re-using of existing vocabs for Architecture of Knowledge took 2.1457672119140625e-06s
Believability | Calculation of trust value for Architecture of Knowledge took 6.67572021484375e-06s
INFO | --- Analysis for ArCo took 689.1491739749908s
Availability | SPARQL endpoint availability check for ConfermentSampo took 0.3720579147338867s
Availability | VoID file availability check for ConfermentSampo took 0.0003008842468261719s
Extra | Recovery of all triples for ConfermentSampo took 22.71953582763672s
Performance | Total latancy measurement for ConfermentSampo took 0.7686021327972412s
Amount of data | Number of triples check for ConfermentSampo took 10.682957410812378s
Interoperability | New terms check for ConfermentSampo took 2.6212453842163086s
Versatility | Languages check for ConfermentSampo took 27.817430019378662s
Interpretability | Number of blank nodes check for ConfermentSampo took 7.950764417648315s
Security | Check HTTPS for ConfermentSampo took 0.390078067779541s
Interpretability | RDF structures check for ConfermentSampo took 0.19468259811401367s
Versatility | Serialization formats check for ConfermentSampo took 0.18835759162902832s
Availability | RDF dump link check for ConfermentSampo took 2.803147554397583s
License | MR license check for ConfermentSampo took 0.18985342979431152s
License | HR license check for ConfermentSampo took 0.3056321144104004s
Amount of data | Number of property check for ConfermentSampo took 0.17223763465881348s
Understandability | Number of label check for ConfermentSampo took 24.60447907447815s
Understandability | URI regex check for ConfermentSampo took 0.34381604194641113s
Understandability | Vocabs check for ConfermentSampo took 0.1567542552947998s
Verifiability | Authors check for ConfermentSampo took 0.18320417404174805s
Verifiability | Publishers check for ConfermentSampo took 0.18241119384765625s
Performance | Throughput check for ConfermentSampo took 10.448858499526978s
Amount of data | Check the number of entities for ConfermentSampo took 3.9489028453826904s
Verifiability | Contribs. check for ConfermentSampo took 0.16064810752868652s
Interlinking | sameAs chians check for ConfermentSampo took 0.648190975189209s
Interlinking | skos check for ConfermentSampo took 0.19851922988891602s
Interlinking | skos check for ConfermentSampo took 0.1449720859527588s
Timeliness | dataset update frequency check for ConfermentSampo took 0.16380691528320312s
Currency | Creation date check for ConfermentSampo took 0.3313572406768799s
Currency | Modification date check for ConfermentSampo took 0.3341939449310303s
Rep.Conc. | URIs length for ConfermentSampo took 34.37915086746216s
Interoperability | New vocabularies check for ConfermentSampo took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for ConfermentSampo took 0.1902170181274414s
Accuracy | Check Functional Property for ConfermentSampo took 0.18031644821166992s
Accuracy | Check Inverse Functional Property for ConfermentSampo took 0.14670085906982422s
Accuracy | Check Empty annotation labels for ConfermentSampo took 15.673945665359497s
Accuracy | Check White space in annotation for ConfermentSampo took 3.074429988861084s
Accuracy | Check Datatype consistency for ConfermentSampo took 5.4124977588653564s
Consistency | Disjoint class check for ConfermentSampo took 0.15395498275756836s
Consistency | Check Misplaced properties for ConfermentSampo took 6.903188228607178s
Consistency | Check Ontology hijacking for ConfermentSampo took 15.405883550643921s
Consistency | Check Invalid usage of undefined classes for ConfermentSampo took 1.3390049934387207s
Consistency | Check Invalid usage of undefined properties for ConfermentSampo took 1.4362852573394775s
Conciseness | Check Extensional conciseness for ConfermentSampo took 2.8085007667541504s
Conciseness | Check Intensional conciseness for ConfermentSampo took 0.1911160945892334s
Security | Sign check for ConfermentSampo took 0.207228422164917s
Availability | Check URIs Dereferenciability for ConfermentSampo took 1302.904887676239s
Completeness | Calculation of interlinking completeness for ConfermentSampo took 0.27718257904052734s
Reputation | Calculation of the PageRank for ConfermentSampo took 0.02113175392150879s
Interlinking | Calculation of Degree of Connection for ConfermentSampo took 1.52587890625e-05s
Interlinking | Calculation of Centrality for ConfermentSampo took 0.00083160400390625s
Interlinking | Calculation of Clustering coefficient for ConfermentSampo took 1.8358230590820312e-05s
Interoperability | Check the re-using of existing vocabs for ConfermentSampo took 2.1457672119140625e-06s
Believability | Calculation of trust value for ConfermentSampo took 8.58306884765625e-06s
INFO | --- Analysis for ConfermentSampo took 1629.9203808307648s
Availability | SPARQL endpoint availability check for Museum Finland took 0.6774303913116455s
Availability | VoID file availability check for Museum Finland took 0.00026535987854003906s
Extra | Recovery of all triples for Museum Finland took 5.1142799854278564s
Performance | Total latancy measurement for Museum Finland took 0.7502350807189941s
Amount of data | Number of triples check for Museum Finland took 0.33512163162231445s
Interoperability | New terms check for Museum Finland took 2.0104949474334717s
Versatility | Languages check for Museum Finland took 0.7103610038757324s
Interpretability | Number of blank nodes check for Museum Finland took 0.3204507827758789s
Security | Check HTTPS for Museum Finland took 0.2326967716217041s
Interpretability | RDF structures check for Museum Finland took 0.46862125396728516s
Versatility | Serialization formats check for Museum Finland took 0.17273640632629395s
Availability | RDF dump link check for Museum Finland took 0.14763140678405762s
License | MR license check for Museum Finland took 0.14893007278442383s
License | HR license check for Museum Finland took 0.3489229679107666s
Amount of data | Number of property check for Museum Finland took 0.17777037620544434s
Understandability | Number of label check for Museum Finland took 0.4528312683105469s
Understandability | URI regex check for Museum Finland took 0.30524754524230957s
Understandability | Vocabs check for Museum Finland took 0.14164161682128906s
Verifiability | Authors check for Museum Finland took 0.14826178550720215s
Verifiability | Publishers check for Museum Finland took 0.14100074768066406s
Performance | Throughput check for Museum Finland took 10.518566608428955s
Amount of data | Check the number of entities for Museum Finland took 8.153915405273438e-05s
Verifiability | Contribs. check for Museum Finland took 0.14852643013000488s
Interlinking | sameAs chians check for Museum Finland took 0.14916706085205078s
Interlinking | skos check for Museum Finland took 0.14928245544433594s
Interlinking | skos check for Museum Finland took 0.1525862216949463s
Timeliness | dataset update frequency check for Museum Finland took 0.15624785423278809s
Currency | Creation date check for Museum Finland took 0.3216283321380615s
Currency | Modification date check for Museum Finland took 0.32154035568237305s
Rep.Conc. | URIs length for Museum Finland took 3.458327531814575s
Interoperability | New vocabularies check for Museum Finland took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for Museum Finland took 0.17969465255737305s
Accuracy | Check Functional Property for Museum Finland took 0.16132831573486328s
Accuracy | Check Inverse Functional Property for Museum Finland took 0.14131617546081543s
Accuracy | Check Empty annotation labels for Museum Finland took 1.0271053314208984s
Accuracy | Check White space in annotation for Museum Finland took 0.06293368339538574s
Accuracy | Check Datatype consistency for Museum Finland took 0.9828746318817139s
Consistency | Disjoint class check for Museum Finland took 0.15647244453430176s
Consistency | Check Misplaced properties for Museum Finland took 0.6545109748840332s
Consistency | Check Ontology hijacking for Museum Finland took 2.209545612335205s
Consistency | Check Invalid usage of undefined classes for Museum Finland took 1.4799458980560303s
Consistency | Check Invalid usage of undefined properties for Museum Finland took 1.7031071186065674s
Conciseness | Check Extensional conciseness for Museum Finland took 0.6515898704528809s
Conciseness | Check Intensional conciseness for Museum Finland took 0.6532371044158936s
Security | Sign check for Museum Finland took 0.14830541610717773s
Availability | Check URIs Dereferenciability for Museum Finland took 2005.4855337142944s
Completeness | Calculation of interlinking completeness for Museum Finland took 0.2754223346710205s
Reputation | Calculation of the PageRank for Museum Finland took 0.020821094512939453s
Interlinking | Calculation of Degree of Connection for Museum Finland took 2.7179718017578125e-05s
Interlinking | Calculation of Centrality for Museum Finland took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Museum Finland took 1.71661376953125e-05s
Interoperability | Check the re-using of existing vocabs for Museum Finland took 1.9073486328125e-06s
Believability | Calculation of trust value for Museum Finland took 1.1444091796875e-05s
INFO | --- Analysis for FI-Museum took 2062.2770318984985s
Availability | SPARQL endpoint availability check for Mapping Manuscript Migrations took 0.18206405639648438s
Availability | VoID file availability check for Mapping Manuscript Migrations took 0.0006134510040283203s
Extra | Recovery of all triples for Mapping Manuscript Migrations took 15.446037292480469s
Performance | Total latancy measurement for Mapping Manuscript Migrations took 0.7613751888275146s
Amount of data | Number of triples check for Mapping Manuscript Migrations took 30.694704055786133s
Interoperability | New terms check for Mapping Manuscript Migrations took 5.102145195007324s
Versatility | Languages check for Mapping Manuscript Migrations took 76.74931931495667s
Interpretability | Number of blank nodes check for Mapping Manuscript Migrations took 29.125675678253174s
Security | Check HTTPS for Mapping Manuscript Migrations took 0.3787569999694824s
Interpretability | RDF structures check for Mapping Manuscript Migrations took 0.1884913444519043s
Versatility | Serialization formats check for Mapping Manuscript Migrations took 0.17934536933898926s
Availability | RDF dump link check for Mapping Manuscript Migrations took 0.15513205528259277s
License | MR license check for Mapping Manuscript Migrations took 0.1792595386505127s
License | HR license check for Mapping Manuscript Migrations took 1.7523603439331055s
Amount of data | Number of property check for Mapping Manuscript Migrations took 0.17752408981323242s
Understandability | Number of label check for Mapping Manuscript Migrations took 125.63280701637268s
Understandability | URI regex check for Mapping Manuscript Migrations took 0.32764410972595215s
Understandability | Vocabs check for Mapping Manuscript Migrations took 0.1565842628479004s
Verifiability | Authors check for Mapping Manuscript Migrations took 0.19054150581359863s
Verifiability | Publishers check for Mapping Manuscript Migrations took 0.17895793914794922s
Performance | Throughput check for Mapping Manuscript Migrations took 10.384183406829834s
Amount of data | Check the number of entities for Mapping Manuscript Migrations took 1.0769023895263672s
Verifiability | Contribs. check for Mapping Manuscript Migrations took 0.1704568862915039s
Interlinking | sameAs chians check for Mapping Manuscript Migrations took 0.5080645084381104s
Interlinking | skos check for Mapping Manuscript Migrations took 0.14242315292358398s
Interlinking | skos check for Mapping Manuscript Migrations took 0.14687418937683105s
Timeliness | dataset update frequency check for Mapping Manuscript Migrations took 0.14815831184387207s
Currency | Creation date check for Mapping Manuscript Migrations took 0.32032155990600586s
Currency | Modification date check for Mapping Manuscript Migrations took 0.22214221954345703s
Rep.Conc. | URIs length for Mapping Manuscript Migrations took 50.52694797515869s
Interoperability | New vocabularies check for Mapping Manuscript Migrations took 1.1920928955078125e-05s
Consistency | Deprecated classes/propertiers check for Mapping Manuscript Migrations took 0.1880803108215332s
Accuracy | Check Functional Property for Mapping Manuscript Migrations took 0.1480116844177246s
Accuracy | Check Inverse Functional Property for Mapping Manuscript Migrations took 0.14295411109924316s
Accuracy | Check Empty annotation labels for Mapping Manuscript Migrations took 10.869695901870728s
Accuracy | Check White space in annotation for Mapping Manuscript Migrations took 2.5073909759521484s
Accuracy | Check Datatype consistency for Mapping Manuscript Migrations took 5.928629636764526s
Consistency | Disjoint class check for Mapping Manuscript Migrations took 0.1712818145751953s
Consistency | Check Misplaced properties for Mapping Manuscript Migrations took 24.14895224571228s
Consistency | Check Ontology hijacking for Mapping Manuscript Migrations took 17.1791090965271s
Consistency | Check Invalid usage of undefined classes for Mapping Manuscript Migrations took 1.6436245441436768s
Consistency | Check Invalid usage of undefined properties for Mapping Manuscript Migrations took 1.6180119514465332s
Conciseness | Check Extensional conciseness for Mapping Manuscript Migrations took 2.8615570068359375s
Conciseness | Check Intensional conciseness for Mapping Manuscript Migrations took 0.17447948455810547s
Security | Sign check for Mapping Manuscript Migrations took 0.1787128448486328s
Availability | Check URIs Dereferenciability for Mapping Manuscript Migrations took 21.573217630386353s
Completeness | Calculation of interlinking completeness for Mapping Manuscript Migrations took 0.6463735103607178s
Reputation | Calculation of the PageRank for Mapping Manuscript Migrations took 0.020599842071533203s
Interlinking | Calculation of Degree of Connection for Mapping Manuscript Migrations took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Mapping Manuscript Migrations took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Mapping Manuscript Migrations took 1.9788742065429688e-05s
Interoperability | Check the re-using of existing vocabs for Mapping Manuscript Migrations took 2.384185791015625e-06s
Believability | Calculation of trust value for Mapping Manuscript Migrations took 7.867813110351562e-06s
INFO | --- Analysis for MMM took 649.0683805942535s
Availability | SPARQL endpoint availability check for Semantic Kalevala took 0.18851399421691895s
Availability | VoID file availability check for Semantic Kalevala took 0.0002551078796386719s
Extra | Recovery of all triples for Semantic Kalevala took 6.692095994949341s
Performance | Total latancy measurement for Semantic Kalevala took 0.7616634368896484s
Amount of data | Number of triples check for Semantic Kalevala took 0.41161537170410156s
Interoperability | New terms check for Semantic Kalevala took 1.7662999629974365s
Versatility | Languages check for Semantic Kalevala took 1.006230354309082s
Interpretability | Number of blank nodes check for Semantic Kalevala took 0.524263858795166s
Security | Check HTTPS for Semantic Kalevala took 0.22784781455993652s
Interpretability | RDF structures check for Semantic Kalevala took 0.18053889274597168s
Versatility | Serialization formats check for Semantic Kalevala took 0.17867517471313477s
Availability | RDF dump link check for Semantic Kalevala took 0.23096394538879395s
License | MR license check for Semantic Kalevala took 0.15358614921569824s
License | HR license check for Semantic Kalevala took 0.989152193069458s
Amount of data | Number of property check for Semantic Kalevala took 0.1702117919921875s
Understandability | Number of label check for Semantic Kalevala took 0.3073103427886963s
Understandability | URI regex check for Semantic Kalevala took 0.2967393398284912s
Understandability | Vocabs check for Semantic Kalevala took 0.14855074882507324s
Verifiability | Authors check for Semantic Kalevala took 0.1412198543548584s
Verifiability | Publishers check for Semantic Kalevala took 0.14892292022705078s
Performance | Throughput check for Semantic Kalevala took 10.313085079193115s
Amount of data | Check the number of entities for Semantic Kalevala took 6.0558319091796875e-05s
Verifiability | Contribs. check for Semantic Kalevala took 0.14110445976257324s
Interlinking | sameAs chians check for Semantic Kalevala took 0.17852139472961426s
Interlinking | skos check for Semantic Kalevala took 0.24078679084777832s
Interlinking | skos check for Semantic Kalevala took 0.13692641258239746s
Timeliness | dataset update frequency check for Semantic Kalevala took 0.14015650749206543s
Currency | Creation date check for Semantic Kalevala took 0.3246617317199707s
Currency | Modification date check for Semantic Kalevala took 0.3294684886932373s
Rep.Conc. | URIs length for Semantic Kalevala took 5.15048885345459s
Interoperability | New vocabularies check for Semantic Kalevala took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Semantic Kalevala took 0.17633605003356934s
Accuracy | Check Functional Property for Semantic Kalevala took 0.15562677383422852s
Accuracy | Check Inverse Functional Property for Semantic Kalevala took 0.14880585670471191s
Accuracy | Check Empty annotation labels for Semantic Kalevala took 1.8402116298675537s
Accuracy | Check White space in annotation for Semantic Kalevala took 0.30288124084472656s
Accuracy | Check Datatype consistency for Semantic Kalevala took 1.429182767868042s
Consistency | Disjoint class check for Semantic Kalevala took 0.17997264862060547s
Consistency | Check Misplaced properties for Semantic Kalevala took 0.8821713924407959s
Consistency | Check Ontology hijacking for Semantic Kalevala took 2.221388816833496s
Consistency | Check Invalid usage of undefined classes for Semantic Kalevala took 1.3960707187652588s
Consistency | Check Invalid usage of undefined properties for Semantic Kalevala took 1.5893585681915283s
Conciseness | Check Extensional conciseness for Semantic Kalevala took 0.8782072067260742s
Conciseness | Check Intensional conciseness for Semantic Kalevala took 0.3294539451599121s
Security | Sign check for Semantic Kalevala took 0.14154052734375s
Availability | Check URIs Dereferenciability for Semantic Kalevala took 812.9850308895111s
Completeness | Calculation of interlinking completeness for Semantic Kalevala took 0.28185486793518066s
Reputation | Calculation of the PageRank for Semantic Kalevala took 0.021197795867919922s
Interlinking | Calculation of Degree of Connection for Semantic Kalevala took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for Semantic Kalevala took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Semantic Kalevala took 7.271766662597656e-05s
Interoperability | Check the re-using of existing vocabs for Semantic Kalevala took 1.6689300537109375e-06s
Believability | Calculation of trust value for Semantic Kalevala took 8.58306884765625e-06s
INFO | --- Analysis for Semantic-Kalevala took 873.7070875167847s
Availability | SPARQL endpoint availability check for Smithsonian American Art Museum took 0.9368994235992432s
Availability | VoID file availability check for Smithsonian American Art Museum took 0.0006284713745117188s
Extra | Recovery of all triples for Smithsonian American Art Museum took 283.71839213371277s
Performance | Total latancy measurement for Smithsonian American Art Museum took 3.0815982818603516s
Amount of data | Number of triples check for Smithsonian American Art Museum took 0.5899295806884766s
Interoperability | New terms check for Smithsonian American Art Museum took 3.035336971282959s
Versatility | Languages check for Smithsonian American Art Museum took 37.90502166748047s
Interpretability | Number of blank nodes check for Smithsonian American Art Museum took 0.594310998916626s
Security | Check HTTPS for Smithsonian American Art Museum took 0.3626847267150879s
Interpretability | RDF structures check for Smithsonian American Art Museum took 0.8912796974182129s
Versatility | Serialization formats check for Smithsonian American Art Museum took 0.7269930839538574s
Availability | RDF dump link check for Smithsonian American Art Museum took 0.6236181259155273s
License | MR license check for Smithsonian American Art Museum took 0.6465768814086914s
License | HR license check for Smithsonian American Art Museum took 18.7717764377594s
Amount of data | Number of property check for Smithsonian American Art Museum took 0.6015815734863281s
Understandability | Number of label check for Smithsonian American Art Museum took 0.6188881397247314s
Understandability | URI regex check for Smithsonian American Art Museum took 1.168903112411499s
Understandability | Vocabs check for Smithsonian American Art Museum took 0.6326067447662354s
Verifiability | Authors check for Smithsonian American Art Museum took 0.6476585865020752s
Verifiability | Publishers check for Smithsonian American Art Museum took 0.5880646705627441s
Performance | Throughput check for Smithsonian American Art Museum took 11.976950645446777s
Amount of data | Check the number of entities for Smithsonian American Art Museum took 8.225440979003906e-05s
Verifiability | Contribs. check for Smithsonian American Art Museum took 0.6177139282226562s
Interlinking | sameAs chians check for Smithsonian American Art Museum took 0.5804200172424316s
Interlinking | skos check for Smithsonian American Art Museum took 0.6038532257080078s
Interlinking | skos check for Smithsonian American Art Museum took 0.5913903713226318s
Timeliness | dataset update frequency check for Smithsonian American Art Museum took 0.6058716773986816s
Currency | Creation date check for Smithsonian American Art Museum took 1.3083884716033936s
Currency | Modification date check for Smithsonian American Art Museum took 1.290722131729126s
Rep.Conc. | URIs length for Smithsonian American Art Museum took 113.54528903961182s
Interoperability | New vocabularies check for Smithsonian American Art Museum took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Smithsonian American Art Museum took 0.587731122970581s
Accuracy | Check Empty annotation labels for Smithsonian American Art Museum took 23.48062753677368s
Accuracy | Check White space in annotation for Smithsonian American Art Museum took 0.5089907646179199s
Accuracy | Check Datatype consistency for Smithsonian American Art Museum took 4.5191731452941895s
Consistency | Disjoint class check for Smithsonian American Art Museum took 0.5863664150238037s
Consistency | Check Misplaced properties for Smithsonian American Art Museum took 5.029326677322388s
Consistency | Check Ontology hijacking for Smithsonian American Art Museum took 96.84427452087402s
Consistency | Check Invalid usage of undefined classes for Smithsonian American Art Museum took 1.6720716953277588s
Consistency | Check Invalid usage of undefined properties for Smithsonian American Art Museum took 5.75514817237854s
Conciseness | Check Extensional conciseness for Smithsonian American Art Museum took 2.9000675678253174s
Conciseness | Check Intensional conciseness for Smithsonian American Art Museum took 0.5893781185150146s
Security | Sign check for Smithsonian American Art Museum took 0.6020019054412842s
Availability | Check URIs Dereferenciability for Smithsonian American Art Museum took 6.469303607940674s
Completeness | Calculation of interlinking completeness for Smithsonian American Art Museum took 0.4173591136932373s
Reputation | Calculation of the PageRank for Smithsonian American Art Museum took 0.020401954650878906s
Interlinking | Calculation of Degree of Connection for Smithsonian American Art Museum took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Smithsonian American Art Museum took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Smithsonian American Art Museum took 2.1457672119140625e-05s
Interoperability | Check the re-using of existing vocabs for Smithsonian American Art Museum took 1.6689300537109375e-06s
Believability | Calculation of trust value for Smithsonian American Art Museum took 7.3909759521484375e-06s
INFO | --- Analysis for Smithsonian took 727.63689661026s
Availability | SPARQL endpoint availability check for Zeri Photo Archive took 0.21393465995788574s
Availability | VoID file availability check for Zeri Photo Archive took 0.0006732940673828125s
Completeness | Calculation of interlinking completeness for Zeri Photo Archive took 0.2731466293334961s
Reputation | Calculation of the PageRank for Zeri Photo Archive took 0.02039170265197754s
Interlinking | Calculation of Degree of Connection for Zeri Photo Archive took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Zeri Photo Archive took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Zeri Photo Archive took 1.3828277587890625e-05s
Believability | Calculation of trust value for Zeri Photo Archive took 4.76837158203125e-06s
INFO | --- Analysis for Zeri-Photo-Archive took 22.777199745178223s
Availability | SPARQL endpoint availability check for Archives Hub took 20.796281099319458s
Availability | VoID file availability check for Archives Hub took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for Archives Hub took 0.27600908279418945s
Reputation | Calculation of the PageRank for Archives Hub took 0.02048015594482422s
Interlinking | Calculation of Degree of Connection for Archives Hub took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Archives Hub took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Archives Hub took 1.33514404296875e-05s
Believability | Calculation of trust value for Archives Hub took 5.9604644775390625e-06s
INFO | --- Analysis for Archives-Hub took 54.00279974937439s
Availability | SPARQL endpoint availability check for Yale centre of British Art took 1.258540153503418s
Availability | VoID file availability check for Yale centre of British Art took 0.000286102294921875s
Completeness | Calculation of interlinking completeness for Yale centre of British Art took 0.26111340522766113s
Reputation | Calculation of the PageRank for Yale centre of British Art took 0.02073073387145996s
Interlinking | Calculation of Degree of Connection for Yale centre of British Art took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Yale centre of British Art took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Yale centre of British Art took 1.239776611328125e-05s
Believability | Calculation of trust value for Yale centre of British Art took 6.67572021484375e-06s
INFO | --- Analysis for Yale took 4.203720331192017s
Availability | SPARQL endpoint availability check for Alexandria Digital Library Gazetteer took 261.8797137737274s
Availability | VoID file availability check for Alexandria Digital Library Gazetteer took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library Gazetteer took 0.28870153427124023s
Reputation | Calculation of the PageRank for Alexandria Digital Library Gazetteer took 0.020864248275756836s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library Gazetteer took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Alexandria Digital Library Gazetteer took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library Gazetteer took 2.8133392333984375e-05s
Believability | Calculation of trust value for Alexandria Digital Library Gazetteer took 6.198883056640625e-06s
INFO | --- Analysis for ADL took 536.8979904651642s
Availability | SPARQL endpoint availability check for MusicKG took 0.9787580966949463s
Availability | VoID file availability check for MusicKG took 0.0007436275482177734s
Completeness | Calculation of interlinking completeness for MusicKG took 0.2628445625305176s
Reputation | Calculation of the PageRank for MusicKG took 0.020792245864868164s
Interlinking | Calculation of Degree of Connection for MusicKG took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for MusicKG took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for MusicKG took 1.3589859008789062e-05s
Believability | Calculation of trust value for MusicKG took 7.152557373046875e-06s
INFO | --- Analysis for MusicKG took 5.224592685699463s
Availability | SPARQL endpoint availability check for CIDOC-CRM took 0.7734901905059814s
Availability | VoID file availability check for CIDOC-CRM took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for CIDOC-CRM took 0.7048244476318359s
Reputation | Calculation of the PageRank for CIDOC-CRM took 0.020947694778442383s
Interlinking | Calculation of Degree of Connection for CIDOC-CRM took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for CIDOC-CRM took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for CIDOC-CRM took 1.2159347534179688e-05s
Believability | Calculation of trust value for CIDOC-CRM took 6.9141387939453125e-06s
INFO | --- Analysis for CIDOC-CRM took 5.6582419872283936s
Availability | SPARQL endpoint availability check for Mondis took 10.622784852981567s
Availability | VoID file availability check for Mondis took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for Mondis took 0.2653625011444092s
Reputation | Calculation of the PageRank for Mondis took 0.020563602447509766s
Interlinking | Calculation of Degree of Connection for Mondis took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Mondis took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Mondis took 1.1205673217773438e-05s
Believability | Calculation of trust value for Mondis took 6.4373016357421875e-06s
INFO | --- Analysis for Mondis took 14.796909809112549s
Availability | SPARQL endpoint availability check for DigitalNZ took 0.21115493774414062s
Availability | VoID file availability check for DigitalNZ took 0.0005514621734619141s
Completeness | Calculation of interlinking completeness for DigitalNZ took 0.2661728858947754s
Reputation | Calculation of the PageRank for DigitalNZ took 0.021288156509399414s
Interlinking | Calculation of Degree of Connection for DigitalNZ took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for DigitalNZ took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for DigitalNZ took 1.3113021850585938e-05s
Believability | Calculation of trust value for DigitalNZ took 7.3909759521484375e-06s
INFO | --- Analysis for DigitalNZ took 4.2372753620147705s
Availability | SPARQL endpoint availability check for Fondazione Zeri took 0.20699310302734375s
Availability | VoID file availability check for Fondazione Zeri took 0.0002789497375488281s
Completeness | Calculation of interlinking completeness for Fondazione Zeri took 0.2870662212371826s
Reputation | Calculation of the PageRank for Fondazione Zeri took 0.02063441276550293s
Interlinking | Calculation of Degree of Connection for Fondazione Zeri took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Fondazione Zeri took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Fondazione Zeri took 1.33514404296875e-05s
Believability | Calculation of trust value for Fondazione Zeri took 6.9141387939453125e-06s
INFO | --- Analysis for Fondazione-Zeri took 3.769310235977173s
Availability | SPARQL endpoint availability check for Digital Public Library of America took 0.275054931640625s
Availability | VoID file availability check for Digital Public Library of America took 0.0006692409515380859s
Completeness | Calculation of interlinking completeness for Digital Public Library of America took 0.27013134956359863s
Reputation | Calculation of the PageRank for Digital Public Library of America took 0.02033209800720215s
Interlinking | Calculation of Degree of Connection for Digital Public Library of America took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Digital Public Library of America took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Digital Public Library of America took 1.2874603271484375e-05s
Believability | Calculation of trust value for Digital Public Library of America took 5.7220458984375e-06s
INFO | --- Analysis for Library-of-America took 4.044400691986084s
Availability | SPARQL endpoint availability check for Auckland Museum took 7.787453889846802s
Availability | VoID file availability check for Auckland Museum took 0.00032019615173339844s
Completeness | Calculation of interlinking completeness for Auckland Museum took 0.2505009174346924s
Reputation | Calculation of the PageRank for Auckland Museum took 0.02034306526184082s
Interlinking | Calculation of Degree of Connection for Auckland Museum took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Auckland Museum took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Auckland Museum took 1.3589859008789062e-05s
Believability | Calculation of trust value for Auckland Museum took 5.7220458984375e-06s
INFO | --- Analysis for Auckland-Museum took 12.77050256729126s
Availability | SPARQL endpoint availability check for National Library of Spain took 1.723789930343628s
Availability | VoID file availability check for National Library of Spain took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for National Library of Spain took 0.23369932174682617s
Reputation | Calculation of the PageRank for National Library of Spain took 0.020623445510864258s
Interlinking | Calculation of Degree of Connection for National Library of Spain took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for National Library of Spain took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for National Library of Spain took 1.2636184692382812e-05s
Believability | Calculation of trust value for National Library of Spain took 6.4373016357421875e-06s
INFO | --- Analysis for BNE took 4.451213121414185s
Availability | SPARQL endpoint availability check for National Library of Korea took 2.5463991165161133s
Availability | VoID file availability check for National Library of Korea took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for National Library of Korea took 0.24381208419799805s
Reputation | Calculation of the PageRank for National Library of Korea took 0.02053666114807129s
Interlinking | Calculation of Degree of Connection for National Library of Korea took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for National Library of Korea took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for National Library of Korea took 1.2636184692382812e-05s
Believability | Calculation of trust value for National Library of Korea took 5.4836273193359375e-06s
INFO | --- Analysis for Korea-Library took 5.35004448890686s
Availability | SPARQL endpoint availability check for The State Russian Museum took 2.0876951217651367s
Availability | VoID file availability check for The State Russian Museum took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for The State Russian Museum took 0.27025794982910156s
Reputation | Calculation of the PageRank for The State Russian Museum took 0.02091836929321289s
Interlinking | Calculation of Degree of Connection for The State Russian Museum took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for The State Russian Museum took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for The State Russian Museum took 1.239776611328125e-05s
Believability | Calculation of trust value for The State Russian Museum took 5.7220458984375e-06s
INFO | --- Analysis for Russian-Museum took 4.995967864990234s
Availability | SPARQL endpoint availability check for National Library of Scotland took 1.6781210899353027s
Availability | VoID file availability check for National Library of Scotland took 0.0007376670837402344s
Completeness | Calculation of interlinking completeness for National Library of Scotland took 0.2879469394683838s
Reputation | Calculation of the PageRank for National Library of Scotland took 0.020712614059448242s
Interlinking | Calculation of Degree of Connection for National Library of Scotland took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for National Library of Scotland took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for National Library of Scotland took 1.3589859008789062e-05s
Believability | Calculation of trust value for National Library of Scotland took 7.3909759521484375e-06s
INFO | --- Analysis for National-Library-of-Scotland took 6.841919183731079s
Availability | SPARQL endpoint availability check for Epigraphic Database Heidelberg took 0.48479294776916504s
Availability | VoID file availability check for Epigraphic Database Heidelberg took 0.0005514621734619141s
Completeness | Calculation of interlinking completeness for Epigraphic Database Heidelberg took 0.2802000045776367s
Reputation | Calculation of the PageRank for Epigraphic Database Heidelberg took 0.020813703536987305s
Interlinking | Calculation of Degree of Connection for Epigraphic Database Heidelberg took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Epigraphic Database Heidelberg took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Epigraphic Database Heidelberg took 1.8835067749023438e-05s
Believability | Calculation of trust value for Epigraphic Database Heidelberg took 7.152557373046875e-06s
INFO | --- Analysis for Epigraphic-Database-Heidelberg took 3.6955997943878174s
Availability | SPARQL endpoint availability check for OntoComedySources took 0.2105245590209961s
Availability | VoID file availability check for OntoComedySources took 0.0006420612335205078s
Completeness | Calculation of interlinking completeness for OntoComedySources took 0.27596259117126465s
Reputation | Calculation of the PageRank for OntoComedySources took 0.02041006088256836s
Interlinking | Calculation of Degree of Connection for OntoComedySources took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for OntoComedySources took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for OntoComedySources took 1.2874603271484375e-05s
Believability | Calculation of trust value for OntoComedySources took 5.7220458984375e-06s
INFO | --- Analysis for OntoComedySources took 4.11868953704834s
Availability | SPARQL endpoint availability check for OntoCeramic 2.0 took 0.19786810874938965s
Availability | VoID file availability check for OntoCeramic 2.0 took 0.0006012916564941406s
Completeness | Calculation of interlinking completeness for OntoCeramic 2.0 took 0.24630427360534668s
Reputation | Calculation of the PageRank for OntoCeramic 2.0 took 0.020882368087768555s
Interlinking | Calculation of Degree of Connection for OntoCeramic 2.0 took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for OntoCeramic 2.0 took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for OntoCeramic 2.0 took 1.3589859008789062e-05s
Believability | Calculation of trust value for OntoCeramic 2.0 took 6.9141387939453125e-06s
INFO | --- Analysis for OntoCeramic-2.0 took 4.6511383056640625s
Availability | SPARQL endpoint availability check for SaintGall Ontology took 0.25403904914855957s
Availability | VoID file availability check for SaintGall Ontology took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for SaintGall Ontology took 0.2637348175048828s
Reputation | Calculation of the PageRank for SaintGall Ontology took 0.020873308181762695s
Interlinking | Calculation of Degree of Connection for SaintGall Ontology took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for SaintGall Ontology took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for SaintGall Ontology took 1.2874603271484375e-05s
Believability | Calculation of trust value for SaintGall Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for SaintGall-Ontology took 3.1755287647247314s
Availability | SPARQL endpoint availability check for Linguistic Phenomena Ontology took 1.0599989891052246s
Availability | VoID file availability check for Linguistic Phenomena Ontology took 0.0005998611450195312s
Completeness | Calculation of interlinking completeness for Linguistic Phenomena Ontology took 0.26776790618896484s
Reputation | Calculation of the PageRank for Linguistic Phenomena Ontology took 0.020661115646362305s
Interlinking | Calculation of Degree of Connection for Linguistic Phenomena Ontology took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Linguistic Phenomena Ontology took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Linguistic Phenomena Ontology took 1.2874603271484375e-05s
Believability | Calculation of trust value for Linguistic Phenomena Ontology took 7.62939453125e-06s
INFO | --- Analysis for Linguistic-Phenomena-Ontology took 4.111100435256958s
Availability | SPARQL endpoint availability check for ICON took 0.31734800338745117s
Availability | VoID file availability check for ICON took 0.0005958080291748047s
Completeness | Calculation of interlinking completeness for ICON took 0.25855588912963867s
Reputation | Calculation of the PageRank for ICON took 0.020429134368896484s
Interlinking | Calculation of Degree of Connection for ICON took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for ICON took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for ICON took 1.239776611328125e-05s
Believability | Calculation of trust value for ICON took 7.3909759521484375e-06s
INFO | --- Analysis for ICON took 4.269699811935425s
Availability | SPARQL endpoint availability check for Polifonia took 0.24553394317626953s
Availability | VoID file availability check for Polifonia took 0.0006420612335205078s
Completeness | Calculation of interlinking completeness for Polifonia took 0.24981093406677246s
Reputation | Calculation of the PageRank for Polifonia took 0.02044200897216797s
Interlinking | Calculation of Degree of Connection for Polifonia took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Polifonia took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Polifonia took 1.1920928955078125e-05s
Believability | Calculation of trust value for Polifonia took 5.245208740234375e-06s
INFO | --- Analysis for Polifonia took 4.899860858917236s
Availability | SPARQL endpoint availability check for Atlas of Paths Ontology - Italian Application Profile took 0.26370882987976074s
Availability | VoID file availability check for Atlas of Paths Ontology - Italian Application Profile took 0.0006902217864990234s
Completeness | Calculation of interlinking completeness for Atlas of Paths Ontology - Italian Application Profile took 0.27919769287109375s
Reputation | Calculation of the PageRank for Atlas of Paths Ontology - Italian Application Profile took 0.020278215408325195s
Interlinking | Calculation of Degree of Connection for Atlas of Paths Ontology - Italian Application Profile took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Atlas of Paths Ontology - Italian Application Profile took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Atlas of Paths Ontology - Italian Application Profile took 1.2874603271484375e-05s
Believability | Calculation of trust value for Atlas of Paths Ontology - Italian Application Profile took 6.9141387939453125e-06s
INFO | --- Analysis for Atlas-of-Paths took 4.074017763137817s
Availability | SPARQL endpoint availability check for Music Note Ontology took 0.21375536918640137s
Availability | VoID file availability check for Music Note Ontology took 0.000400543212890625s
Completeness | Calculation of interlinking completeness for Music Note Ontology took 0.25331711769104004s
Reputation | Calculation of the PageRank for Music Note Ontology took 0.020592689514160156s
Interlinking | Calculation of Degree of Connection for Music Note Ontology took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Music Note Ontology took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Music Note Ontology took 1.1682510375976562e-05s
Believability | Calculation of trust value for Music Note Ontology took 6.67572021484375e-06s
INFO | --- Analysis for Music-Note-Ontology took 8.75043272972107s
Availability | SPARQL endpoint availability check for HaMSE took 0.2349998950958252s
Availability | VoID file availability check for HaMSE took 0.0003504753112792969s
Completeness | Calculation of interlinking completeness for HaMSE took 0.2641758918762207s
Reputation | Calculation of the PageRank for HaMSE took 0.020347118377685547s
Interlinking | Calculation of Degree of Connection for HaMSE took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for HaMSE took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for HaMSE took 1.1205673217773438e-05s
Believability | Calculation of trust value for HaMSE took 7.3909759521484375e-06s
INFO | --- Analysis for HaMSE took 4.560585260391235s
Availability | SPARQL endpoint availability check for FOOD: FOod in Open Data took 0.11833930015563965s
Availability | VoID file availability check for FOOD: FOod in Open Data took 0.0005826950073242188s
Completeness | Calculation of interlinking completeness for FOOD: FOod in Open Data took 0.24752020835876465s
Reputation | Calculation of the PageRank for FOOD: FOod in Open Data took 0.021352767944335938s
Interlinking | Calculation of Degree of Connection for FOOD: FOod in Open Data took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for FOOD: FOod in Open Data took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for FOOD: FOod in Open Data took 1.239776611328125e-05s
Believability | Calculation of trust value for FOOD: FOod in Open Data took 7.3909759521484375e-06s
INFO | --- Analysis for FOod took 3.3772833347320557s
Availability | SPARQL endpoint availability check for The ATLAS of Italian Digital Cultural Heritage took 0.6967968940734863s
Availability | VoID file availability check for The ATLAS of Italian Digital Cultural Heritage took 0.0005931854248046875s
Completeness | Calculation of interlinking completeness for The ATLAS of Italian Digital Cultural Heritage took 0.28330278396606445s
Reputation | Calculation of the PageRank for The ATLAS of Italian Digital Cultural Heritage took 0.02068471908569336s
Interlinking | Calculation of Degree of Connection for The ATLAS of Italian Digital Cultural Heritage took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for The ATLAS of Italian Digital Cultural Heritage took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for The ATLAS of Italian Digital Cultural Heritage took 1.33514404296875e-05s
Believability | Calculation of trust value for The ATLAS of Italian Digital Cultural Heritage took 6.67572021484375e-06s
INFO | --- Analysis for ATLAS-Italian-Digital-CH took 5.352304935455322s
Availability | SPARQL endpoint availability check for ARIADNEplus Knowledge Base took 1.7045996189117432s
Availability | VoID file availability check for ARIADNEplus Knowledge Base took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for ARIADNEplus Knowledge Base took 0.2747836112976074s
Reputation | Calculation of the PageRank for ARIADNEplus Knowledge Base took 0.020335674285888672s
Interlinking | Calculation of Degree of Connection for ARIADNEplus Knowledge Base took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for ARIADNEplus Knowledge Base took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for ARIADNEplus Knowledge Base took 1.239776611328125e-05s
Believability | Calculation of trust value for ARIADNEplus Knowledge Base took 7.152557373046875e-06s
INFO | --- Analysis for ARIADNE took 5.949014902114868s
Availability | SPARQL endpoint availability check for MappingChange took 0.7593514919281006s
Availability | VoID file availability check for MappingChange took 0.0002956390380859375s
Completeness | Calculation of interlinking completeness for MappingChange took 0.28206658363342285s
Reputation | Calculation of the PageRank for MappingChange took 0.02128291130065918s
Interlinking | Calculation of Degree of Connection for MappingChange took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for MappingChange took 0.0010068416595458984s
Interlinking | Calculation of Clustering coefficient for MappingChange took 1.4066696166992188e-05s
Believability | Calculation of trust value for MappingChange took 7.152557373046875e-06s
INFO | --- Analysis for mappingch took 4.115380048751831s
Availability | SPARQL endpoint availability check for Odeuropa Ontology took 0.2947697639465332s
Availability | VoID file availability check for Odeuropa Ontology took 0.00023937225341796875s
Completeness | Calculation of interlinking completeness for Odeuropa Ontology took 0.267672061920166s
Reputation | Calculation of the PageRank for Odeuropa Ontology took 0.020381927490234375s
Interlinking | Calculation of Degree of Connection for Odeuropa Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Odeuropa Ontology took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Odeuropa Ontology took 1.1444091796875e-05s
Believability | Calculation of trust value for Odeuropa Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for Odeuropa took 3.252804756164551s
Availability | SPARQL endpoint availability check for Continental European Books in Early Modern England, 1500-1640 took 0.3709394931793213s
Availability | VoID file availability check for Continental European Books in Early Modern England, 1500-1640 took 0.0002567768096923828s
Extra | Recovery of all triples for Continental European Books in Early Modern England, 1500-1640 took 20.214001655578613s
Performance | Total latancy measurement for Continental European Books in Early Modern England, 1500-1640 took 0.805220365524292s
Amount of data | Number of triples check for Continental European Books in Early Modern England, 1500-1640 took 10.806321144104004s
Interoperability | New terms check for Continental European Books in Early Modern England, 1500-1640 took 3.6199769973754883s
Versatility | Languages check for Continental European Books in Early Modern England, 1500-1640 took 10.573854684829712s
Interpretability | Number of blank nodes check for Continental European Books in Early Modern England, 1500-1640 took 7.660828113555908s
Interpretability | RDF structures check for Continental European Books in Early Modern England, 1500-1640 took 0.34267234802246094s
Versatility | Serialization formats check for Continental European Books in Early Modern England, 1500-1640 took 0.16887998580932617s
Availability | RDF dump link check for Continental European Books in Early Modern England, 1500-1640 took 1.686274528503418s
License | MR license check for Continental European Books in Early Modern England, 1500-1640 took 0.1468062400817871s
License | HR license check for Continental European Books in Early Modern England, 1500-1640 took 0.30761265754699707s
Amount of data | Number of property check for Continental European Books in Early Modern England, 1500-1640 took 0.17111945152282715s
Understandability | Number of label check for Continental European Books in Early Modern England, 1500-1640 took 0.2008371353149414s
Understandability | URI regex check for Continental European Books in Early Modern England, 1500-1640 took 0.2976241111755371s
Understandability | Vocabs check for Continental European Books in Early Modern England, 1500-1640 took 0.15556716918945312s
Verifiability | Authors check for Continental European Books in Early Modern England, 1500-1640 took 0.1611623764038086s
Verifiability | Publishers check for Continental European Books in Early Modern England, 1500-1640 took 0.16132831573486328s
Performance | Throughput check for Continental European Books in Early Modern England, 1500-1640 took 11.169151544570923s
Amount of data | Check the number of entities for Continental European Books in Early Modern England, 1500-1640 took 0.9896159172058105s
Verifiability | Contribs. check for Continental European Books in Early Modern England, 1500-1640 took 0.18572998046875s
Interlinking | sameAs chians check for Continental European Books in Early Modern England, 1500-1640 took 0.17679333686828613s
Interlinking | skos check for Continental European Books in Early Modern England, 1500-1640 took 0.1810445785522461s
Interlinking | skos check for Continental European Books in Early Modern England, 1500-1640 took 0.17581772804260254s
Timeliness | dataset update frequency check for Continental European Books in Early Modern England, 1500-1640 took 0.1539463996887207s
Currency | Creation date check for Continental European Books in Early Modern England, 1500-1640 took 0.31757569313049316s
Currency | Modification date check for Continental European Books in Early Modern England, 1500-1640 took 0.16272664070129395s
Rep.Conc. | URIs length for Continental European Books in Early Modern England, 1500-1640 took 27.273441791534424s
Consistency | Deprecated classes/propertiers check for Continental European Books in Early Modern England, 1500-1640 took 0.16321539878845215s
Accuracy | Check Functional Property for Continental European Books in Early Modern England, 1500-1640 took 0.1593153476715088s
Accuracy | Check Inverse Functional Property for Continental European Books in Early Modern England, 1500-1640 took 0.17109322547912598s
Accuracy | Check Empty annotation labels for Continental European Books in Early Modern England, 1500-1640 took 0.9677183628082275s
Accuracy | Check White space in annotation for Continental European Books in Early Modern England, 1500-1640 took 0.036562204360961914s
Accuracy | Check Datatype consistency for Continental European Books in Early Modern England, 1500-1640 took 4.773172378540039s
Consistency | Disjoint class check for Continental European Books in Early Modern England, 1500-1640 took 0.15944552421569824s
Consistency | Check Misplaced properties for Continental European Books in Early Modern England, 1500-1640 took 6.949636936187744s
Consistency | Check Ontology hijacking for Continental European Books in Early Modern England, 1500-1640 took 8.54718017578125s
Consistency | Check Invalid usage of undefined classes for Continental European Books in Early Modern England, 1500-1640 took 1.3215410709381104s
Consistency | Check Invalid usage of undefined properties for Continental European Books in Early Modern England, 1500-1640 took 7.943893671035767s
Conciseness | Check Extensional conciseness for Continental European Books in Early Modern England, 1500-1640 took 2.790849208831787s
Security | Sign check for Continental European Books in Early Modern England, 1500-1640 took 0.16228556632995605s
Availability | Check URIs Dereferenciability for Continental European Books in Early Modern England, 1500-1640 took 1466.3191833496094s
Completeness | Calculation of interlinking completeness for Continental European Books in Early Modern England, 1500-1640 took 0.830538272857666s
Reputation | Calculation of the PageRank for Continental European Books in Early Modern England, 1500-1640 took 0.022229433059692383s
Interlinking | Calculation of Degree of Connection for Continental European Books in Early Modern England, 1500-1640 took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Continental European Books in Early Modern England, 1500-1640 took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Continental European Books in Early Modern England, 1500-1640 took 8.273124694824219e-05s
Believability | Calculation of trust value for Continental European Books in Early Modern England, 1500-1640 took 1.5020370483398438e-05s
INFO | --- Analysis for CEBEME took 1679.3460528850555s

--- Total time for analysis:660692.9610931873s ---
--- Total time for analysis:183.52582252588536 hours ---