Availability | SPARQL endpoint availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.00013518333435058594s
Availability | VoID file availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.000804901123046875s
Completeness | Calculation of interlinking completeness for Korespondencja Emila Szramka z Janem Kuderą took 0.3126864433288574s
Reputation | Calculation of the PageRank for Korespondencja Emila Szramka z Janem Kuderą took 0.42244768142700195s
Interlinking | Calculation of Degree of Connection for Korespondencja Emila Szramka z Janem Kuderą took 2.5033950805664062e-05s
Interlinking | Calculation of Centrality for Korespondencja Emila Szramka z Janem Kuderą took 0.0008544921875s
Interlinking | Calculation of Clustering coefficient for Korespondencja Emila Szramka z Janem Kuderą took 0.0006160736083984375s
Believability | Calculation of trust value for Korespondencja Emila Szramka z Janem Kuderą took 1.621246337890625e-05s
INFO | --- Analysis for 0080-3626 took 4.634477138519287s
Availability | SPARQL endpoint availability check for 土地利用图 took 0.00010704994201660156s
Availability | VoID file availability check for 土地利用图 took 0.0006496906280517578s
Completeness | Calculation of interlinking completeness for 土地利用图 took 0.2632114887237549s
Reputation | Calculation of the PageRank for 土地利用图 took 0.020769596099853516s
Interlinking | Calculation of Degree of Connection for 土地利用图 took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for 土地利用图 took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for 土地利用图 took 4.482269287109375e-05s
Believability | Calculation of trust value for 土地利用图 took 1.4543533325195312e-05s
INFO | --- Analysis for 10.12041geodata.290864223.ver1.db_ took 2.4830753803253174s
Availability | SPARQL endpoint availability check for 113322 took 0.00015926361083984375s
Availability | VoID file availability check for 113322 took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for 113322 took 0.2618279457092285s
Reputation | Calculation of the PageRank for 113322 took 0.020911455154418945s
Interlinking | Calculation of Degree of Connection for 113322 took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for 113322 took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for 113322 took 4.601478576660156e-05s
Believability | Calculation of trust value for 113322 took 1.621246337890625e-05s
INFO | --- Analysis for 11 took 4.450531482696533s
Availability | SPARQL endpoint availability check for Korepetycje Buki took 9.560585021972656e-05s
Availability | VoID file availability check for Korepetycje Buki took 0.0005948543548583984s
Completeness | Calculation of interlinking completeness for Korepetycje Buki took 0.2711210250854492s
Reputation | Calculation of the PageRank for Korepetycje Buki took 0.02109813690185547s
Interlinking | Calculation of Degree of Connection for Korepetycje Buki took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Korepetycje Buki took 0.0007827281951904297s
Interlinking | Calculation of Clustering coefficient for Korepetycje Buki took 4.6253204345703125e-05s
Believability | Calculation of trust value for Korepetycje Buki took 1.5735626220703125e-05s
INFO | --- Analysis for 12323 took 2.4588892459869385s
Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.04584860801696777s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.0006046295166015625s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.270916223526001s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.02013111114501953s
Interlinking | Calculation of Degree of Connection for 2000 U.S. Census in RDF (rdfabout.com) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for 2000 U.S. Census in RDF (rdfabout.com) took 0.0006864070892333984s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 0.00010085105895996094s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 1.2159347534179688e-05s
INFO | --- Analysis for 2000-us-census-rdf took 2.4880056381225586s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 2.024832010269165s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.0006153583526611328s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.26360034942626953s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.020082712173461914s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 3.719329833984375e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 8.58306884765625e-06s
INFO | --- Analysis for 2001-spanish-census-to-rdf took 6.027023553848267s
Availability | SPARQL endpoint availability check for Open Data Web took 41.755337715148926s
Availability | VoID file availability check for Open Data Web took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.27195215225219727s
Reputation | Calculation of the PageRank for Open Data Web took 0.022481203079223633s
Interlinking | Calculation of Degree of Connection for Open Data Web took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Data Web took 0.0006844997406005859s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 2.956390380859375e-05s
Believability | Calculation of trust value for Open Data Web took 1.1205673217773438e-05s
INFO | --- Analysis for _data.odw.tw took 57.538023948669434s
Availability | SPARQL endpoint availability check for 土地利用 took 4.267692565917969e-05s
Availability | VoID file availability check for 土地利用 took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for 土地利用 took 0.2663853168487549s
Reputation | Calculation of the PageRank for 土地利用 took 0.020122766494750977s
Interlinking | Calculation of Degree of Connection for 土地利用 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for 土地利用 took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for 土地利用 took 3.3855438232421875e-05s
Believability | Calculation of trust value for 土地利用 took 1.2159347534179688e-05s
INFO | --- Analysis for _data1.odw.tw took 2.444105863571167s
Availability | SPARQL endpoint availability check for 土地利用模型 took 9.131431579589844e-05s
Availability | VoID file availability check for 土地利用模型 took 0.0005292892456054688s
Completeness | Calculation of interlinking completeness for 土地利用模型 took 0.26702380180358887s
Reputation | Calculation of the PageRank for 土地利用模型 took 0.02088308334350586s
Interlinking | Calculation of Degree of Connection for 土地利用模型 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for 土地利用模型 took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for 土地利用模型 took 2.8133392333984375e-05s
Believability | Calculation of trust value for 土地利用模型 took 1.0013580322265625e-05s
INFO | --- Analysis for _data2.odw.tw took 4.666274070739746s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.172325134277344e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0006146430969238281s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.26216721534729004s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020030975341796875s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.765655517578125e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.0251998901367188e-05s
INFO | --- Analysis for _https:data.bioontology.orgontologiesBOFdownloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb&download_format=rdf took 3.6539149284362793s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 9.179115295410156e-05s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.26705169677734375s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.020031213760375977s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 2.86102294921875e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 1.049041748046875e-05s
INFO | --- Analysis for a-collection-of-papers-for-lrec2014-and-related-workshops took 3.1293206214904785s
Availability | SPARQL endpoint availability check for ITS TEST DATASET took 8.845329284667969e-05s
Availability | VoID file availability check for ITS TEST DATASET took 0.0007135868072509766s
Completeness | Calculation of interlinking completeness for ITS TEST DATASET took 0.2678258419036865s
Reputation | Calculation of the PageRank for ITS TEST DATASET took 0.020478248596191406s
Interlinking | Calculation of Degree of Connection for ITS TEST DATASET took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for ITS TEST DATASET took 0.0009131431579589844s
Interlinking | Calculation of Clustering coefficient for ITS TEST DATASET took 3.361701965332031e-05s
Believability | Calculation of trust value for ITS TEST DATASET took 9.298324584960938e-06s
INFO | --- Analysis for A1 took 3.3654561042785645s
Availability | SPARQL endpoint availability check for SummerOlympics took 1.828489065170288s
Availability | VoID file availability check for SummerOlympics took 0.0006670951843261719s
Completeness | Calculation of interlinking completeness for SummerOlympics took 0.2666168212890625s
Reputation | Calculation of the PageRank for SummerOlympics took 0.019830942153930664s
Interlinking | Calculation of Degree of Connection for SummerOlympics took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SummerOlympics took 0.0006835460662841797s
Interlinking | Calculation of Clustering coefficient for SummerOlympics took 6.031990051269531e-05s
Believability | Calculation of trust value for SummerOlympics took 1.3828277587890625e-05s
INFO | --- Analysis for abc took 7.8593456745147705s
Availability | SPARQL endpoint availability check for Test_m took 8.940696716308594e-05s
Availability | VoID file availability check for Test_m took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for Test_m took 0.26202917098999023s
Reputation | Calculation of the PageRank for Test_m took 0.020215511322021484s
Interlinking | Calculation of Degree of Connection for Test_m took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Test_m took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Test_m took 2.6941299438476562e-05s
Believability | Calculation of trust value for Test_m took 1.1682510375976562e-05s
INFO | --- Analysis for ABC took 2.3966779708862305s
Availability | SPARQL endpoint availability check for my intro took 9.059906005859375e-05s
Availability | VoID file availability check for my intro took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for my intro took 0.269364595413208s
Reputation | Calculation of the PageRank for my intro took 0.02002573013305664s
Interlinking | Calculation of Degree of Connection for my intro took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for my intro took 0.0006840229034423828s
Interlinking | Calculation of Clustering coefficient for my intro took 2.6941299438476562e-05s
Believability | Calculation of trust value for my intro took 5.9604644775390625e-06s
INFO | --- Analysis for abhay_intro took 2.3949685096740723s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.07668542861938477s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.2656395435333252s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.020845651626586914s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 9.870529174804688e-05s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 1.0967254638671875e-05s
INFO | --- Analysis for abs-linked-data took 2.5197691917419434s
Availability | SPARQL endpoint availability check for AcadOnto took 8.893013000488281e-05s
Availability | VoID file availability check for AcadOnto took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.2723569869995117s
Reputation | Calculation of the PageRank for AcadOnto took 0.020167827606201172s
Interlinking | Calculation of Degree of Connection for AcadOnto took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for AcadOnto took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 2.7418136596679688e-05s
Believability | Calculation of trust value for AcadOnto took 1.239776611328125e-05s
INFO | --- Analysis for acadonto took 3.0311264991760254s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 9.116906642913818s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0006167888641357422s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.2646596431732178s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.02186870574951172s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 4.291534423828125e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 9.5367431640625e-06s
INFO | --- Analysis for acorn-sat took 35.625967025756836s
Availability | SPARQL endpoint availability check for Addgene took 4.291534423828125e-05s
Availability | VoID file availability check for Addgene took 0.0007162094116210938s
Completeness | Calculation of interlinking completeness for Addgene took 0.26868462562561035s
Reputation | Calculation of the PageRank for Addgene took 0.02375054359436035s
Interlinking | Calculation of Degree of Connection for Addgene took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Addgene took 0.0011136531829833984s
Interlinking | Calculation of Clustering coefficient for Addgene took 4.482269287109375e-05s
Believability | Calculation of trust value for Addgene took 1.2636184692382812e-05s
INFO | --- Analysis for addgene took 15.529240608215332s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 8.869171142578125e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.0006971359252929688s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.27801990509033203s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.02185678482055664s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 9.274482727050781e-05s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 1.1682510375976562e-05s
INFO | --- Analysis for aegp-spanish-textile-and-clothing-association took 9.81600284576416s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 0.4533965587615967s
Availability | VoID file availability check for AEMET metereological dataset took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.2682790756225586s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.021967172622680664s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 3.552436828613281e-05s
Believability | Calculation of trust value for AEMET metereological dataset took 1.1920928955078125e-05s
INFO | --- Analysis for aemet took 4.619441747665405s
Availability | SPARQL endpoint availability check for AgriNepalData took 0.03111553192138672s
Availability | VoID file availability check for AgriNepalData took 0.0004661083221435547s
Completeness | Calculation of interlinking completeness for AgriNepalData took 0.28048110008239746s
Reputation | Calculation of the PageRank for AgriNepalData took 0.020898103713989258s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 6.842613220214844e-05s
Believability | Calculation of trust value for AgriNepalData took 1.1920928955078125e-05s
INFO | --- Analysis for agrinepaldata took 2.4864397048950195s
Availability | SPARQL endpoint availability check for AGRIS took 260.6800091266632s
Availability | VoID file availability check for AGRIS took 0.0006368160247802734s
Completeness | Calculation of interlinking completeness for AGRIS took 0.36191439628601074s
Reputation | Calculation of the PageRank for AGRIS took 0.020479917526245117s
Interlinking | Calculation of Degree of Connection for AGRIS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for AGRIS took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for AGRIS took 7.653236389160156e-05s
Believability | Calculation of trust value for AGRIS took 1.0013580322265625e-05s
INFO | --- Analysis for agris took 553.9506168365479s
Availability | SPARQL endpoint availability check for AGROVOC took 0.15465712547302246s
Availability | VoID file availability check for AGROVOC took 0.0006036758422851562s
Extra | Recovery of all triples for AGROVOC took 156.72401642799377s
Performance | Total latancy measurement for AGROVOC took 0.4455752372741699s
Amount of data | Number of triples check for AGROVOC took 300.0718193054199s
Interoperability | New terms check for AGROVOC took 4.960038423538208s
Versatility | Languages check for AGROVOC took 300.0754351615906s
Interpretability | Number of blank nodes check for AGROVOC took 300.0921516418457s
Interpretability | RDF structures check for AGROVOC took 0.08007431030273438s
Versatility | Serialization formats check for AGROVOC took 0.09980344772338867s
Availability | RDF dump link check for AGROVOC took 0.07556676864624023s
License | MR license check for AGROVOC took 0.12035942077636719s
License | HR license check for AGROVOC took 1.2480123043060303s
Amount of data | Number of property check for AGROVOC took 0.07736587524414062s
Understandability | Number of label check for AGROVOC took 196.68683791160583s
Understandability | URI regex check for AGROVOC took 0.15177178382873535s
Understandability | Vocabs check for AGROVOC took 0.07508063316345215s
Verifiability | Authors check for AGROVOC took 0.07715678215026855s
Verifiability | Publishers check for AGROVOC took 0.09489059448242188s
Performance | Throughput check for AGROVOC took 10.404685020446777s
Amount of data | Check the number of entities for AGROVOC took 7.033348083496094e-05s
Verifiability | Contribs. check for AGROVOC took 0.07404351234436035s
Interlinking | sameAs chians check for AGROVOC took 0.07529377937316895s
Interlinking | skos check for AGROVOC took 3.720937728881836s
Interlinking | skos check for AGROVOC took 14.75249457359314s
Timeliness | dataset update frequency check for AGROVOC took 0.1276090145111084s
Currency | Creation date check for AGROVOC took 0.15536761283874512s
Currency | Modification date check for AGROVOC took 0.1559140682220459s
Rep.Conc. | URIs length for AGROVOC took 185.09472179412842s
Interoperability | New vocabularies check for AGROVOC took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for AGROVOC took 0.07558560371398926s
Accuracy | Check Empty annotation labels for AGROVOC took 47.01170468330383s
Accuracy | Check White space in annotation for AGROVOC took 2.9943790435791016s
Accuracy | Check Datatype consistency for AGROVOC took 4.473609924316406s
Consistency | Disjoint class check for AGROVOC took 0.07478952407836914s
Consistency | Check Misplaced properties for AGROVOC took 25.980918645858765s
Consistency | Check Ontology hijacking for AGROVOC took 300.113974571228s
Consistency | Check Invalid usage of undefined properties for AGROVOC took 31.74727201461792s
Conciseness | Check Extensional conciseness for AGROVOC took 2.5542287826538086s
Conciseness | Check Intensional conciseness for AGROVOC took 0.31876587867736816s
Security | Sign check for AGROVOC took 0.22929167747497559s
Availability | Check URIs Dereferenciability for AGROVOC took 3.1286697387695312s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.4432373046875s
Reputation | Calculation of the PageRank for AGROVOC took 0.020868778228759766s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 0.00011348724365234375s
Interoperability | Check the re-using of existing vocabs for AGROVOC took 1.430511474609375e-06s
Believability | Calculation of trust value for AGROVOC took 1.2159347534179688e-05s
INFO | --- Analysis for agrovoc took 2488.5695974826813s
Availability | SPARQL endpoint availability check for Analytics India Magazine took 1.4816787242889404s
Availability | VoID file availability check for Analytics India Magazine took 0.0005316734313964844s
Extra | Recovery of all triples for Analytics India Magazine took 2.7720155715942383s
Performance | Total latancy measurement for Analytics India Magazine took 1.320335865020752s
Amount of data | Number of triples check for Analytics India Magazine took 1.18526291847229s
Versatility | Languages check for Analytics India Magazine took 1.2749454975128174s
Interpretability | Number of blank nodes check for Analytics India Magazine took 1.3221454620361328s
Interpretability | RDF structures check for Analytics India Magazine took 1.3436367511749268s
Versatility | Serialization formats check for Analytics India Magazine took 1.0750839710235596s
Availability | RDF dump link check for Analytics India Magazine took 1.4791615009307861s
License | MR license check for Analytics India Magazine took 1.133970022201538s
License | HR license check for Analytics India Magazine took 1.2922987937927246s
Amount of data | Number of property check for Analytics India Magazine took 1.3720543384552002s
Understandability | Number of label check for Analytics India Magazine took 1.2573351860046387s
Understandability | URI regex check for Analytics India Magazine took 2.436445474624634s
Understandability | Vocabs check for Analytics India Magazine took 1.00569486618042s
Verifiability | Authors check for Analytics India Magazine took 1.7551207542419434s
Verifiability | Publishers check for Analytics India Magazine took 1.0462043285369873s
Performance | Throughput check for Analytics India Magazine took 17.0880184173584s
Amount of data | Check the number of entities for Analytics India Magazine took 9.751319885253906e-05s
Verifiability | Contribs. check for Analytics India Magazine took 1.0478920936584473s
Interlinking | sameAs chians check for Analytics India Magazine took 1.1260275840759277s
Interlinking | skos check for Analytics India Magazine took 1.6977736949920654s
Interlinking | skos check for Analytics India Magazine took 0.10990118980407715s
Timeliness | dataset update frequency check for Analytics India Magazine took 1.2839350700378418s
Currency | Creation date check for Analytics India Magazine took 2.84802508354187s
Currency | Modification date check for Analytics India Magazine took 2.586049795150757s
Rep.Conc. | URIs length for Analytics India Magazine took 2.744547128677368s
Interoperability | New vocabularies check for Analytics India Magazine took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for Analytics India Magazine took 1.387955904006958s
Consistency | Disjoint class check for Analytics India Magazine took 1.1246004104614258s
Consistency | Check Ontology hijacking for Analytics India Magazine took 1.26039719581604s
Consistency | Check Invalid usage of undefined properties for Analytics India Magazine took 2.4357805252075195s
Conciseness | Check Extensional conciseness for Analytics India Magazine took 0.00016164779663085938s
Security | Sign check for Analytics India Magazine took 1.3149285316467285s
Completeness | Calculation of interlinking completeness for Analytics India Magazine took 0.33231472969055176s
Reputation | Calculation of the PageRank for Analytics India Magazine took 0.019971847534179688s
Interlinking | Calculation of Degree of Connection for Analytics India Magazine took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Analytics India Magazine took 0.0006821155548095703s
Interlinking | Calculation of Clustering coefficient for Analytics India Magazine took 2.7894973754882812e-05s
Interoperability | Check the re-using of existing vocabs for Analytics India Magazine took 1.1920928955078125e-06s
Believability | Calculation of trust value for Analytics India Magazine took 1.2159347534179688e-05s
INFO | --- Analysis for AIM took 98.09224653244019s
Availability | SPARQL endpoint availability check for All India Survey of Higher Education took 8.654594421386719e-05s
Availability | VoID file availability check for All India Survey of Higher Education took 0.0005469322204589844s
Completeness | Calculation of interlinking completeness for All India Survey of Higher Education took 0.2652781009674072s
Reputation | Calculation of the PageRank for All India Survey of Higher Education took 0.02052021026611328s
Interlinking | Calculation of Degree of Connection for All India Survey of Higher Education took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for All India Survey of Higher Education took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for All India Survey of Higher Education took 3.1948089599609375e-05s
Believability | Calculation of trust value for All India Survey of Higher Education took 1.2159347534179688e-05s
INFO | --- Analysis for AISHE took 2.4100725650787354s
Availability | SPARQL endpoint availability check for  equipment ontology took 9.059906005859375e-05s
Availability | VoID file availability check for  equipment ontology took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for  equipment ontology took 0.26738691329956055s
Reputation | Calculation of the PageRank for  equipment ontology took 0.02020120620727539s
Interlinking | Calculation of Degree of Connection for  equipment ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for  equipment ontology took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for  equipment ontology took 3.075599670410156e-05s
Believability | Calculation of trust value for  equipment ontology took 1.1682510375976562e-05s
INFO | --- Analysis for akash took 2.3967270851135254s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 0.9487931728363037s
Availability | VoID file availability check for aliada-scanbit-net took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 0.2857975959777832s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.020525693893432617s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.00015425682067871094s
Believability | Calculation of trust value for aliada-scanbit-net took 1.2636184692382812e-05s
INFO | --- Analysis for aliada-scanbit-net took 4.107232093811035s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 18.252209186553955s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.0006940364837646484s
Extra | Recovery of all triples for Allie Abbreviation And Long Form Database in Life Science took 108.7959611415863s
Amount of data | Number of triples check for Allie Abbreviation And Long Form Database in Life Science took 10.096966743469238s
Versatility | Languages check for Allie Abbreviation And Long Form Database in Life Science took 300.083518743515s
Interpretability | Number of blank nodes check for Allie Abbreviation And Long Form Database in Life Science took 107.1346583366394s
Security | Check HTTPS for Allie Abbreviation And Long Form Database in Life Science took 75.57011485099792s
Interpretability | RDF structures check for Allie Abbreviation And Long Form Database in Life Science took 30.56815457344055s
Versatility | Serialization formats check for Allie Abbreviation And Long Form Database in Life Science took 107.70290994644165s
Availability | RDF dump link check for Allie Abbreviation And Long Form Database in Life Science took 10.096786260604858s
License | MR license check for Allie Abbreviation And Long Form Database in Life Science took 10.006468534469604s
License | HR license check for Allie Abbreviation And Long Form Database in Life Science took 166.63105750083923s
Amount of data | Number of property check for Allie Abbreviation And Long Form Database in Life Science took 103.7117669582367s
Understandability | Number of label check for Allie Abbreviation And Long Form Database in Life Science took 4.399519443511963s
Understandability | URI regex check for Allie Abbreviation And Long Form Database in Life Science took 160.94653296470642s
Understandability | Vocabs check for Allie Abbreviation And Long Form Database in Life Science took 14.991582870483398s
Verifiability | Authors check for Allie Abbreviation And Long Form Database in Life Science took 10.014586687088013s
Verifiability | Publishers check for Allie Abbreviation And Long Form Database in Life Science took 33.82579469680786s
Verifiability | Contribs. check for Allie Abbreviation And Long Form Database in Life Science took 45.15494179725647s
Interlinking | sameAs chians check for Allie Abbreviation And Long Form Database in Life Science took 15.583691596984863s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 147.66691875457764s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 10.015913963317871s
Timeliness | dataset update frequency check for Allie Abbreviation And Long Form Database in Life Science took 10.098552942276001s
Currency | Creation date check for Allie Abbreviation And Long Form Database in Life Science took 18.35647439956665s
Currency | Modification date check for Allie Abbreviation And Long Form Database in Life Science took 178.14380359649658s
Rep.Conc. | URIs length for Allie Abbreviation And Long Form Database in Life Science took 75.09974718093872s
Interoperability | New vocabularies check for Allie Abbreviation And Long Form Database in Life Science took 3.6210145950317383s
Consistency | Deprecated classes/propertiers check for Allie Abbreviation And Long Form Database in Life Science took 10.076460838317871s
Accuracy | Check Empty annotation labels for Allie Abbreviation And Long Form Database in Life Science took 61.133668184280396s
Accuracy | Check White space in annotation for Allie Abbreviation And Long Form Database in Life Science took 3.013245105743408s
Consistency | Disjoint class check for Allie Abbreviation And Long Form Database in Life Science took 63.29541635513306s
Consistency | Check Misplaced properties for Allie Abbreviation And Long Form Database in Life Science took 38.42402958869934s
Consistency | Misplaced classes for Allie Abbreviation And Long Form Database in Life Science took 68.6258897781372s
Consistency | Check Ontology hijacking for Allie Abbreviation And Long Form Database in Life Science took 300.10442066192627s
Consistency | Check Invalid usage of undefined properties for Allie Abbreviation And Long Form Database in Life Science took 49.2610080242157s
Conciseness | Check Extensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 0.00016260147094726562s
Conciseness | Check Intensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 229.11590194702148s
Security | Sign check for Allie Abbreviation And Long Form Database in Life Science took 10.10021710395813s
Availability | Check URIs Dereferenciability for Allie Abbreviation And Long Form Database in Life Science took 12754.210056066513s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 0.6176457405090332s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.020901203155517578s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 7.581710815429688e-05s
Interoperability | Check the re-using of existing vocabs for Allie Abbreviation And Long Form Database in Life Science took 4.844965696334839s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 2.5272369384765625e-05s
INFO | --- Analysis for allie-abbreviation-and-long-form-database-in-life-science took 16024.190792322159s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 0.2898414134979248s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.0005657672882080078s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 0.2737886905670166s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.02013850212097168s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 3.695487976074219e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 5.245208740234375e-06s
INFO | --- Analysis for alpino-rdf took 3.6535017490386963s
Availability | SPARQL endpoint availability check for AAT-atawil took 8.702278137207031e-05s
Availability | VoID file availability check for AAT-atawil took 0.0004923343658447266s
Completeness | Calculation of interlinking completeness for AAT-atawil took 0.26557087898254395s
Reputation | Calculation of the PageRank for AAT-atawil took 0.021068334579467773s
Interlinking | Calculation of Degree of Connection for AAT-atawil took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for AAT-atawil took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for AAT-atawil took 2.956390380859375e-05s
Believability | Calculation of trust value for AAT-atawil took 9.775161743164062e-06s
INFO | --- Analysis for Altawil took 2.3895089626312256s
Availability | SPARQL endpoint availability check for Amer Nejma took 4.124641418457031e-05s
Availability | VoID file availability check for Amer Nejma took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for Amer Nejma took 0.26169252395629883s
Reputation | Calculation of the PageRank for Amer Nejma took 0.020220518112182617s
Interlinking | Calculation of Degree of Connection for Amer Nejma took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Amer Nejma took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Amer Nejma took 2.86102294921875e-05s
Believability | Calculation of trust value for Amer Nejma took 1.0251998901367188e-05s
INFO | --- Analysis for Amer_Nejma took 2.421447515487671s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.6938302516937256s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.000698089599609375s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.278104305267334s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.020496606826782227s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 9.894371032714844e-05s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.239776611328125e-05s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 13.86556625366211s
Availability | SPARQL endpoint availability check for Anime Dataset took 4.57763671875e-05s
Availability | VoID file availability check for Anime Dataset took 0.0006983280181884766s
Completeness | Calculation of interlinking completeness for Anime Dataset took 0.2708566188812256s
Reputation | Calculation of the PageRank for Anime Dataset took 0.020382404327392578s
Interlinking | Calculation of Degree of Connection for Anime Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Anime Dataset took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Anime Dataset took 2.9802322387695312e-05s
Believability | Calculation of trust value for Anime Dataset took 1.1920928955078125e-05s
INFO | --- Analysis for Anime took 3.915471076965332s
Availability | SPARQL endpoint availability check for ANNO took 4.124641418457031e-05s
Availability | VoID file availability check for ANNO took 0.0008382797241210938s
Completeness | Calculation of interlinking completeness for ANNO took 0.2730257511138916s
Reputation | Calculation of the PageRank for ANNO took 0.021684885025024414s
Interlinking | Calculation of Degree of Connection for ANNO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ANNO took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for ANNO took 3.4809112548828125e-05s
Believability | Calculation of trust value for ANNO took 1.239776611328125e-05s
INFO | --- Analysis for anno took 7.478172540664673s
Availability | SPARQL endpoint availability check for Antique Cars Collection (Linked Cars) took 4.124641418457031e-05s
Availability | VoID file availability check for Antique Cars Collection (Linked Cars) took 0.0003459453582763672s
Completeness | Calculation of interlinking completeness for Antique Cars Collection (Linked Cars) took 0.271869421005249s
Reputation | Calculation of the PageRank for Antique Cars Collection (Linked Cars) took 0.020498275756835938s
Interlinking | Calculation of Degree of Connection for Antique Cars Collection (Linked Cars) took 1.9073486328125e-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.700920104980469e-05s
Believability | Calculation of trust value for Antique Cars Collection (Linked Cars) took 9.298324584960938e-06s
INFO | --- Analysis for AntiqueCarsCollection took 2.956300735473633s
Availability | SPARQL endpoint availability check for apache took 8.249282836914062e-05s
Availability | VoID file availability check for apache took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for apache took 0.27292656898498535s
Reputation | Calculation of the PageRank for apache took 0.020554542541503906s
Interlinking | Calculation of Degree of Connection for apache took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for apache took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for apache took 5.626678466796875e-05s
Believability | Calculation of trust value for apache took 9.059906005859375e-06s
INFO | --- Analysis for apache took 3.132948637008667s
Availability | SPARQL endpoint availability check for Apertium RDF took 8.368492126464844e-05s
Availability | VoID file availability check for Apertium RDF took 0.0007889270782470703s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.26657700538635254s
Reputation | Calculation of the PageRank for Apertium RDF took 0.020849943161010742s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 4.6253204345703125e-05s
Believability | Calculation of trust value for Apertium RDF took 1.0967254638671875e-05s
INFO | --- Analysis for apertium-rdf took 5.6376731395721436s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 8.749961853027344e-05s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.27069091796875s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.020453214645385742s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 4.38690185546875e-05s
Believability | Calculation of trust value for Apertium RDF CA-IT took 9.059906005859375e-06s
INFO | --- Analysis for apertium-rdf-ca-it took 29.83451533317566s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 8.440017700195312e-05s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.26691341400146484s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.02060246467590332s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 4.673004150390625e-05s
Believability | Calculation of trust value for Apertium RDF EN-CA took 1.1444091796875e-05s
INFO | --- Analysis for apertium-rdf-en-ca took 30.37824583053589s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 8.273124694824219e-05s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.0007920265197753906s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.2647402286529541s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.020293474197387695s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 4.506111145019531e-05s
Believability | Calculation of trust value for Apertium RDF EN-ES took 1.2159347534179688e-05s
INFO | --- Analysis for apertium-rdf-en-es took 6.276751518249512s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 8.559226989746094e-05s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.0006155967712402344s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.26478123664855957s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.02095174789428711s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-GL took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-GL took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 4.649162292480469e-05s
Believability | Calculation of trust value for Apertium RDF EN-GL took 1.049041748046875e-05s
INFO | --- Analysis for apertium-rdf-en-gl took 6.782887935638428s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 8.702278137207031e-05s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.0006089210510253906s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 0.27134037017822266s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.02071380615234375s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 4.673004150390625e-05s
Believability | Calculation of trust value for Apertium RDF EO-CA took 1.0728836059570312e-05s
INFO | --- Analysis for apertium-rdf-eo-ca took 5.357729196548462s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 8.487701416015625e-05s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.00028228759765625s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.28246378898620605s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.020563840866088867s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-EN took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-EN took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 4.553794860839844e-05s
Believability | Calculation of trust value for Apertium RDF EO-EN took 8.58306884765625e-06s
INFO | --- Analysis for apertium-rdf-eo-en took 5.555032968521118s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 6.699562072753906e-05s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.0005750656127929688s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.2657136917114258s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.020412683486938477s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 4.7206878662109375e-05s
Believability | Calculation of trust value for Apertium RDF EO-ES took 1.0728836059570312e-05s
INFO | --- Analysis for apertium-rdf-eo-es took 29.862542629241943s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 8.845329284667969e-05s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.2729206085205078s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.020485639572143555s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 4.5299530029296875e-05s
Believability | Calculation of trust value for Apertium RDF EO-FR took 1.0728836059570312e-05s
INFO | --- Analysis for apertium-rdf-eo-fr took 5.332650661468506s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 8.630752563476562e-05s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.0006034374237060547s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.26537489891052246s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.020311594009399414s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 4.458427429199219e-05s
Believability | Calculation of trust value for Apertium RDF ES-AN took 1.3828277587890625e-05s
INFO | --- Analysis for apertium-rdf-es-an took 29.728336811065674s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 6.365776062011719e-05s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.2699730396270752s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.020467519760131836s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 4.6253204345703125e-05s
Believability | Calculation of trust value for Apertium RDF ES-AST took 9.775161743164062e-06s
INFO | --- Analysis for apertium-rdf-es-ast took 6.774254083633423s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 8.392333984375e-05s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 0.27382707595825195s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.020409345626831055s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 4.4345855712890625e-05s
Believability | Calculation of trust value for Apertium RDF ES-CA took 1.049041748046875e-05s
INFO | --- Analysis for apertium-rdf-es-ca took 9.000477075576782s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 8.7738037109375e-05s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.0007262229919433594s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.2710576057434082s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.020436763763427734s
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.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 5.412101745605469e-05s
Believability | Calculation of trust value for Apertium RDF ES-GL took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-es-gl took 30.176292419433594s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 4.1961669921875e-05s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.35747313499450684s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.020434856414794922s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 4.57763671875e-05s
Believability | Calculation of trust value for Apertium RDF ES-PT took 7.867813110351562e-06s
INFO | --- Analysis for apertium-rdf-es-pt took 29.623152494430542s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 8.869171142578125e-05s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.0006227493286132812s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.27600526809692383s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.020418405532836914s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 5.6743621826171875e-05s
Believability | Calculation of trust value for Apertium RDF ES-RO took 1.1682510375976562e-05s
INFO | --- Analysis for apertium-rdf-es-ro took 30.30502700805664s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 4.315376281738281e-05s
Availability | VoID file availability check for Apertium RDF EU-EN took 0.0005757808685302734s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.2707700729370117s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.020183563232421875s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 1.0967254638671875e-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.291534423828125e-05s
Believability | Calculation of trust value for Apertium RDF EU-EN took 1.3589859008789062e-05s
INFO | --- Analysis for apertium-rdf-eu-en took 8.738717317581177s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 8.654594421386719e-05s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.0006935596466064453s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.26546454429626465s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.020691633224487305s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 5.14984130859375e-05s
Believability | Calculation of trust value for Apertium RDF EU-ES took 9.5367431640625e-06s
INFO | --- Analysis for apertium-rdf-eu-es took 29.596477508544922s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 8.416175842285156e-05s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.0005564689636230469s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.27117323875427246s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.020465373992919922s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 4.57763671875e-05s
Believability | Calculation of trust value for Apertium RDF FR-CA took 9.5367431640625e-06s
INFO | --- Analysis for apertium-rdf-fr-ca took 5.380659103393555s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 4.38690185546875e-05s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.0005533695220947266s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.27373266220092773s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.021857023239135742s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 4.601478576660156e-05s
Believability | Calculation of trust value for Apertium RDF FR-ES took 9.775161743164062e-06s
INFO | --- Analysis for apertium-rdf-fr-es took 7.496177911758423s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 8.869171142578125e-05s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0006031990051269531s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 0.27626562118530273s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.02072620391845703s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 4.410743713378906e-05s
Believability | Calculation of trust value for Apertium RDF OC-CA took 1.0251998901367188e-05s
INFO | --- Analysis for apertium-rdf-oc-ca took 31.127379179000854s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 5.793571472167969e-05s
Availability | VoID file availability check for Apertium RDF OC-ES took 0.0005934238433837891s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 0.2658193111419678s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.02045154571533203s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 4.673004150390625e-05s
Believability | Calculation of trust value for Apertium RDF OC-ES took 1.3828277587890625e-05s
INFO | --- Analysis for apertium-rdf-oc-es took 6.365941286087036s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 4.172325134277344e-05s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.00044035911560058594s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 0.26416778564453125s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.02033090591430664s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0008573532104492188s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 4.935264587402344e-05s
Believability | Calculation of trust value for Apertium RDF PT-CA took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-pt-ca took 8.008941173553467s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 0.00014519691467285156s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.0006589889526367188s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.2648963928222656s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.020568132400512695s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 4.57763671875e-05s
Believability | Calculation of trust value for Apertium RDF PT-GL took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-pt-gl took 5.962284803390503s
Availability | SPARQL endpoint availability check for AragoDBpedia - aragon open data took 0.6682193279266357s
Availability | VoID file availability check for AragoDBpedia - aragon open data took 0.0003523826599121094s
Extra | Recovery of all triples for AragoDBpedia - aragon open data took 2.8698863983154297s
Performance | Total latancy measurement for AragoDBpedia - aragon open data took 1.7506818771362305s
Amount of data | Number of triples check for AragoDBpedia - aragon open data took 0.7614109516143799s
Interoperability | New terms check for AragoDBpedia - aragon open data took 2.1431987285614014s
Versatility | Languages check for AragoDBpedia - aragon open data took 60.4044406414032s
Interpretability | Number of blank nodes check for AragoDBpedia - aragon open data took 4.205389499664307s
Security | Check HTTPS for AragoDBpedia - aragon open data took 0.23259425163269043s
Interpretability | RDF structures check for AragoDBpedia - aragon open data took 0.581268310546875s
Versatility | Serialization formats check for AragoDBpedia - aragon open data took 0.9098222255706787s
Availability | RDF dump link check for AragoDBpedia - aragon open data took 0.4529087543487549s
License | MR license check for AragoDBpedia - aragon open data took 0.5283992290496826s
License | HR license check for AragoDBpedia - aragon open data took 5.585201978683472s
Amount of data | Number of property check for AragoDBpedia - aragon open data took 0.37786364555358887s
Understandability | Number of label check for AragoDBpedia - aragon open data took 0.4867076873779297s
Understandability | URI regex check for AragoDBpedia - aragon open data took 0.8083372116088867s
Understandability | Vocabs check for AragoDBpedia - aragon open data took 0.4156029224395752s
Verifiability | Authors check for AragoDBpedia - aragon open data took 0.44327235221862793s
Verifiability | Publishers check for AragoDBpedia - aragon open data took 0.3844578266143799s
Performance | Throughput check for AragoDBpedia - aragon open data took 10.469235181808472s
Amount of data | Check the number of entities for AragoDBpedia - aragon open data took 6.842613220214844e-05s
Verifiability | Contribs. check for AragoDBpedia - aragon open data took 0.4265768527984619s
Interlinking | sameAs chians check for AragoDBpedia - aragon open data took 0.402951717376709s
Interlinking | skos check for AragoDBpedia - aragon open data took 0.4886503219604492s
Interlinking | skos check for AragoDBpedia - aragon open data took 0.35152268409729004s
Timeliness | dataset update frequency check for AragoDBpedia - aragon open data took 0.42545533180236816s
Currency | Creation date check for AragoDBpedia - aragon open data took 1.152437448501587s
Currency | Modification date check for AragoDBpedia - aragon open data took 0.37477588653564453s
Rep.Conc. | URIs length for AragoDBpedia - aragon open data took 5.966640949249268s
Interoperability | New vocabularies check for AragoDBpedia - aragon open data took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for AragoDBpedia - aragon open data took 0.3718280792236328s
Accuracy | Check Functional Property for AragoDBpedia - aragon open data took 0.4294013977050781s
Accuracy | Check Inverse Functional Property for AragoDBpedia - aragon open data took 0.42926597595214844s
Accuracy | Check Empty annotation labels for AragoDBpedia - aragon open data took 1.177535057067871s
Accuracy | Check White space in annotation for AragoDBpedia - aragon open data took 0.030503034591674805s
Accuracy | Check Datatype consistency for AragoDBpedia - aragon open data took 0.027321338653564453s
Consistency | Disjoint class check for AragoDBpedia - aragon open data took 0.3715496063232422s
Consistency | Check Misplaced properties for AragoDBpedia - aragon open data took 4.395925283432007s
Consistency | Misplaced classes for AragoDBpedia - aragon open data took 0.5891647338867188s
Consistency | Check Ontology hijacking for AragoDBpedia - aragon open data took 2.5265908241271973s
Consistency | Check Invalid usage of undefined classes for AragoDBpedia - aragon open data took 1.3719427585601807s
Consistency | Check Invalid usage of undefined properties for AragoDBpedia - aragon open data took 5.147771835327148s
Conciseness | Check Extensional conciseness for AragoDBpedia - aragon open data took 0.03148221969604492s
Conciseness | Check Intensional conciseness for AragoDBpedia - aragon open data took 0.6089451313018799s
Security | Sign check for AragoDBpedia - aragon open data took 0.5187695026397705s
Availability | Check URIs Dereferenciability for AragoDBpedia - aragon open data took 3007.2449083328247s
Completeness | Calculation of interlinking completeness for AragoDBpedia - aragon open data took 0.6810557842254639s
Reputation | Calculation of the PageRank for AragoDBpedia - aragon open data took 0.020591259002685547s
Interlinking | Calculation of Degree of Connection for AragoDBpedia - aragon open data took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for AragoDBpedia - aragon open data took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for AragoDBpedia - aragon open data took 4.7206878662109375e-05s
Interoperability | Check the re-using of existing vocabs for AragoDBpedia - aragon open data took 1.1920928955078125e-06s
Believability | Calculation of trust value for AragoDBpedia - aragon open data took 4.5299530029296875e-06s
INFO | --- Analysis for aragodbpedia took 3272.8320813179016s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 30.271753549575806s
Availability | VoID file availability check for Archives Hub Linked Data took 0.0006947517395019531s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.2701382637023926s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.0202329158782959s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0006899833679199219s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 5.245208740234375e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 1.2159347534179688e-05s
INFO | --- Analysis for archiveshub-linkeddata took 82.91053199768066s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 4.176147937774658s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 0.27368831634521484s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.02174544334411621s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0009665489196777344s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 4.220008850097656e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 1.33514404296875e-05s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 19.34384059906006s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.8454039096832275s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.000652313232421875s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.29689836502075195s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.020535945892333984s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.9577484130859375e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.0728836059570312e-05s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 16.86922597885132s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 4.38690185546875e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0006165504455566406s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.2657332420349121s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.021755456924438477s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.00010514259338378906s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 9.775161743164062e-06s
INFO | --- Analysis for artenuevosmedios-gnoss took 10.318010330200195s
Availability | SPARQL endpoint availability check for Arthroscopy community took 8.416175842285156e-05s
Availability | VoID file availability check for Arthroscopy community took 0.0005571842193603516s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 0.2644193172454834s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.020609378814697266s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 0.00010251998901367188s
Believability | Calculation of trust value for Arthroscopy community took 9.298324584960938e-06s
INFO | --- Analysis for arthroscopy took 12.445937633514404s
Availability | SPARQL endpoint availability check for Wikidata entry for Art × Science International took 0.8621597290039062s
Availability | VoID file availability check for Wikidata entry for Art × Science International took 0.0005276203155517578s
Extra | Recovery of all triples for Wikidata entry for Art × Science International took 61.77825856208801s
Amount of data | Number of triples check for Wikidata entry for Art × Science International took 65.18674111366272s
Interoperability | New terms check for Wikidata entry for Art × Science International took 2.3992724418640137s
Versatility | Languages check for Wikidata entry for Art × Science International took 65.18666863441467s
Interpretability | Number of blank nodes check for Wikidata entry for Art × Science International took 0.18902945518493652s
Interpretability | RDF structures check for Wikidata entry for Art × Science International took 0.19591903686523438s
Versatility | Serialization formats check for Wikidata entry for Art × Science International took 0.1892709732055664s
Availability | RDF dump link check for Wikidata entry for Art × Science International took 0.20556116104125977s
License | MR license check for Wikidata entry for Art × Science International took 0.19066524505615234s
License | HR license check for Wikidata entry for Art × Science International took 0.18999266624450684s
Amount of data | Number of property check for Wikidata entry for Art × Science International took 0.7351343631744385s
Understandability | Number of label check for Wikidata entry for Art × Science International took 65.19268417358398s
Understandability | URI regex check for Wikidata entry for Art × Science International took 0.7494454383850098s
Understandability | Vocabs check for Wikidata entry for Art × Science International took 0.4423971176147461s
Verifiability | Authors check for Wikidata entry for Art × Science International took 0.38493847846984863s
Verifiability | Publishers check for Wikidata entry for Art × Science International took 0.20440888404846191s
Amount of data | Check the number of entities for Wikidata entry for Art × Science International took 0.00011444091796875s
Verifiability | Contribs. check for Wikidata entry for Art × Science International took 0.2023923397064209s
Interlinking | sameAs chians check for Wikidata entry for Art × Science International took 0.1901850700378418s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.20304441452026367s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.20342302322387695s
Timeliness | dataset update frequency check for Wikidata entry for Art × Science International took 0.1905205249786377s
Currency | Creation date check for Wikidata entry for Art × Science International took 0.7077822685241699s
Currency | Modification date check for Wikidata entry for Art × Science International took 0.49270081520080566s
Rep.Conc. | URIs length for Wikidata entry for Art × Science International took 66.83272099494934s
Interoperability | New vocabularies check for Wikidata entry for Art × Science International took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for Wikidata entry for Art × Science International took 0.20526409149169922s
Accuracy | Check Datatype consistency for Wikidata entry for Art × Science International took 4.579784393310547s
Consistency | Disjoint class check for Wikidata entry for Art × Science International took 0.2286219596862793s
Consistency | Check Misplaced properties for Wikidata entry for Art × Science International took 10.756882429122925s
Consistency | Misplaced classes for Wikidata entry for Art × Science International took 8.936085939407349s
Consistency | Check Ontology hijacking for Wikidata entry for Art × Science International took 49.64187812805176s
Consistency | Check Invalid usage of undefined classes for Wikidata entry for Art × Science International took 1.3477585315704346s
Consistency | Check Invalid usage of undefined properties for Wikidata entry for Art × Science International took 8.177273035049438s
Conciseness | Check Extensional conciseness for Wikidata entry for Art × Science International took 2.775660753250122s
Conciseness | Check Intensional conciseness for Wikidata entry for Art × Science International took 2.0444071292877197s
Security | Sign check for Wikidata entry for Art × Science International took 0.1900012493133545s
Availability | Check URIs Dereferenciability for Wikidata entry for Art × Science International took 8.583662033081055s
Completeness | Calculation of interlinking completeness for Wikidata entry for Art × Science International took 0.34329795837402344s
Reputation | Calculation of the PageRank for Wikidata entry for Art × Science International took 0.0207674503326416s
Interlinking | Calculation of Degree of Connection for Wikidata entry for Art × Science International took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Wikidata entry for Art × Science International took 0.0006749629974365234s
Interlinking | Calculation of Clustering coefficient for Wikidata entry for Art × Science International took 1.3828277587890625e-05s
Interoperability | Check the re-using of existing vocabs for Wikidata entry for Art × Science International took 1.430511474609375e-06s
Believability | Calculation of trust value for Wikidata entry for Art × Science International took 1.0967254638671875e-05s
INFO | --- Analysis for artxscienceinternational-wikidata took 795.0396320819855s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 4.631105422973633s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0006587505340576172s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.2995181083679199s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.01978778839111328s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0006864070892333984s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 7.43865966796875e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.1205673217773438e-05s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 14.70114517211914s
Availability | SPARQL endpoint availability check for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 2.6552464962005615s
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.000598907470703125s
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.27806663513183594s
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.021261215209960938s
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.2636184692382812e-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.0007946491241455078s
Interlinking | Calculation of Clustering coefficient for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 8.058547973632812e-05s
Believability | Calculation of trust value for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 1.239776611328125e-05s
INFO | --- Analysis for ASCDC-AS-NTUE-School-Art-Textbooks took 12.15073299407959s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.653877019882202s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0006573200225830078s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.2654430866241455s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.020456552505493164s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 9.679794311523438e-05s
Believability | Calculation of trust value for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.0967254638671875e-05s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 13.306143999099731s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.6501410007476807s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.0003643035888671875s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 0.26340174674987793s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.020310640335083008s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 4.1961669921875e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 7.152557373046875e-06s
INFO | --- Analysis for ASCDC-CRB took 15.632139921188354s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.6466684341430664s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.00037169456481933594s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.2579493522644043s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.020290613174438477s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.202957153320312e-05s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 6.9141387939453125e-06s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 12.693080186843872s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.6484665870666504s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.0004239082336425781s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 0.25891876220703125s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.02040266990661621s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0007910728454589844s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 3.743171691894531e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 6.9141387939453125e-06s
INFO | --- Analysis for ASCDC-DQOT took 13.7966628074646s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.6544997692108154s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0003662109375s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.2563953399658203s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.02024698257446289s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 7.605552673339844e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 6.4373016357421875e-06s
INFO | --- Analysis for ASCDC-IHP-WCD took 13.848678827285767s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 3.817589521408081s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.00037932395935058594s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 0.2646169662475586s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.020518779754638672s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.0007832050323486328s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 8.797645568847656e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 7.867813110351562e-06s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 16.740060329437256s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.647012948989868s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0003821849822998047s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.27611517906188965s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.020189762115478516s
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.0728836059570312e-05s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 5.316734313964844e-05s
Believability | Calculation of trust value for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 8.821487426757812e-06s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 12.677019834518433s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.649946451187134s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0004076957702636719s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.2602846622467041s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.020237445831298828s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 5.435943603515625e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 7.3909759521484375e-06s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 12.665858507156372s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 4.255824089050293s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.26450061798095703s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.020189285278320312s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 4.38690185546875e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 6.9141387939453125e-06s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 17.406800031661987s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.657311201095581s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0003924369812011719s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.26761770248413086s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.020247220993041992s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 7.367134094238281e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 7.3909759521484375e-06s
INFO | --- Analysis for ASCDC-Tibetan-Audio-Archive took 12.126154661178589s
Availability | SPARQL endpoint availability check for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 2.6582448482513428s
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.0003974437713623047s
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.26230716705322266s
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.020154953002929688s
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.049041748046875e-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.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 7.82012939453125e-05s
Believability | Calculation of trust value for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 7.3909759521484375e-06s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 13.872181177139282s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 2.656869888305664s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 0.26855921745300293s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.020686626434326172s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.001222848892211914s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 8.416175842285156e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 7.3909759521484375e-06s
INFO | --- Analysis for ASCDC_-_DNB took 12.078778982162476s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 4.315376281738281e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 0.2631669044494629s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.020967960357666016s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.0010149478912353516s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 8.320808410644531e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 6.9141387939453125e-06s
INFO | --- Analysis for asit took 7.480107545852661s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 9.036064147949219e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.0005595684051513672s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.26500821113586426s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.020123720169067383s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 3.647804260253906e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 1.0967254638671875e-05s
INFO | --- Analysis for asjp took 4.492589950561523s
Availability | SPARQL endpoint availability check for ASN:US took 1.9717535972595215s
Availability | VoID file availability check for ASN:US took 0.0006165504455566406s
Completeness | Calculation of interlinking completeness for ASN:US took 0.268726110458374s
Reputation | Calculation of the PageRank for ASN:US took 0.020458459854125977s
Interlinking | Calculation of Degree of Connection for ASN:US took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ASN:US took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for ASN:US took 6.508827209472656e-05s
Believability | Calculation of trust value for ASN:US took 8.821487426757812e-06s
INFO | --- Analysis for asn-us took 11.592867851257324s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 9.1552734375e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.0006361007690429688s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.26520872116088867s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.020775556564331055s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.0007843971252441406s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 3.24249267578125e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 8.58306884765625e-06s
INFO | --- Analysis for aspire-mmu took 4.41759729385376s
Availability | SPARQL endpoint availability check for associations took 9.036064147949219e-05s
Availability | VoID file availability check for associations took 0.0006630420684814453s
Completeness | Calculation of interlinking completeness for associations took 0.26845526695251465s
Reputation | Calculation of the PageRank for associations took 0.020320415496826172s
Interlinking | Calculation of Degree of Connection for associations took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for associations took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for associations took 6.723403930664062e-05s
Believability | Calculation of trust value for associations took 1.1205673217773438e-05s
INFO | --- Analysis for associations took 7.035447120666504s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 8.869171142578125e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.0005860328674316406s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 0.2651326656341553s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.020727157592773438s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0008146762847900391s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 9.989738464355469e-05s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 1.1205673217773438e-05s
INFO | --- Analysis for athelia-rfid took 7.813937664031982s
Availability | SPARQL endpoint availability check for Augustini Confessiones in LiLa took 0.5227413177490234s
Availability | VoID file availability check for Augustini Confessiones in LiLa took 0.0003681182861328125s
Completeness | Calculation of interlinking completeness for Augustini Confessiones in LiLa took 0.2654135227203369s
Reputation | Calculation of the PageRank for Augustini Confessiones in LiLa took 0.021955251693725586s
Interlinking | Calculation of Degree of Connection for Augustini Confessiones in LiLa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Augustini Confessiones in LiLa took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Augustini Confessiones in LiLa took 4.9591064453125e-05s
Believability | Calculation of trust value for Augustini Confessiones in LiLa took 1.1205673217773438e-05s
INFO | --- Analysis for AugustiniConfessiones took 4.103806495666504s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 0.4291095733642578s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.0005807876586914062s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.2656416893005371s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.020430326461791992s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Alpine Ski Racers of Austria took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 8.96453857421875e-05s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 1.0967254638671875e-05s
INFO | --- Analysis for austrian_ski_racers took 3.4878604412078857s
Availability | SPARQL endpoint availability check for AVsOnto took 9.703636169433594e-05s
Availability | VoID file availability check for AVsOnto took 0.0005300045013427734s
Completeness | Calculation of interlinking completeness for AVsOnto took 0.26545214653015137s
Reputation | Calculation of the PageRank for AVsOnto took 0.020789623260498047s
Interlinking | Calculation of Degree of Connection for AVsOnto took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for AVsOnto took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for AVsOnto took 3.266334533691406e-05s
Believability | Calculation of trust value for AVsOnto took 1.2636184692382812e-05s
INFO | --- Analysis for AVsOnto took 3.196791887283325s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2506411075592041s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0004343986511230469s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 169.51923608779907s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.4528770446777344s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.044260263443s
Interoperability | New terms check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 277.9887273311615s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.09265327453613s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.1024844646454s
Security | Check HTTPS for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.22152090072631836s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2008199691772461s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.19355344772338867s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10932683944702148s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 45.37608742713928s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.095978975296s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.16462135314941406s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 148.92715740203857s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2384035587310791s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.14495277404785156s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10486245155334473s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.17300844192504883s
Performance | Throughput check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.560166120529175s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.00011134147644042969s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10901331901550293s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0211637020111s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.35053229331970215s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12358570098876953s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1546623706817627s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.24382328987121582s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.347980260848999s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 767.9004454612732s
Interoperability | New vocabularies check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.23724150657653809s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.544415950775146s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.1481921672821045s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.697943687438965s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.18670392036437988s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.1313579082489s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 21.966888904571533s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.2804501056671143s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 301.50314831733704s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.760627269744873s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.14023995399475098s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.9312305450439453s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.7009792327880859s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.022153377532958984s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.963180541992188e-05s
Interoperability | Check the re-using of existing vocabs for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.6689300537109375e-06s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 8.58306884765625e-06s
INFO | --- Analysis for b3kat took 4199.037291526794s
Availability | SPARQL endpoint availability check for BabelNet took 0.5286929607391357s
Availability | VoID file availability check for BabelNet took 0.0012230873107910156s
Completeness | Calculation of interlinking completeness for BabelNet took 0.2719721794128418s
Reputation | Calculation of the PageRank for BabelNet took 0.02129983901977539s
Interlinking | Calculation of Degree of Connection for BabelNet took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BabelNet took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.00016736984252929688s
Believability | Calculation of trust value for BabelNet took 1.1444091796875e-05s
INFO | --- Analysis for babelnet took 4.259903430938721s
Availability | SPARQL endpoint availability check for Bacevicius.lt took 4.363059997558594e-05s
Availability | VoID file availability check for Bacevicius.lt took 0.00046825408935546875s
Completeness | Calculation of interlinking completeness for Bacevicius.lt took 0.27077293395996094s
Reputation | Calculation of the PageRank for Bacevicius.lt took 0.022228240966796875s
Interlinking | Calculation of Degree of Connection for Bacevicius.lt took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bacevicius.lt took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Bacevicius.lt took 2.8133392333984375e-05s
Believability | Calculation of trust value for Bacevicius.lt took 1.1920928955078125e-05s
INFO | --- Analysis for Bacevicius.lt took 2.4089558124542236s
Availability | SPARQL endpoint availability check for Basisregistratie Adressen en Gebouwen took 0.40944790840148926s
Availability | VoID file availability check for Basisregistratie Adressen en Gebouwen took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for Basisregistratie Adressen en Gebouwen took 0.263913631439209s
Reputation | Calculation of the PageRank for Basisregistratie Adressen en Gebouwen took 0.02034759521484375s
Interlinking | Calculation of Degree of Connection for Basisregistratie Adressen en Gebouwen took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Basisregistratie Adressen en Gebouwen took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Basisregistratie Adressen en Gebouwen took 4.458427429199219e-05s
Believability | Calculation of trust value for Basisregistratie Adressen en Gebouwen took 1.239776611328125e-05s
INFO | --- Analysis for bag took 4.011287212371826s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 0.8654003143310547s
Availability | VoID file availability check for 红色经典歌曲 took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.2786879539489746s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020692110061645508s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.218650817871094e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.2874603271484375e-05s
INFO | --- Analysis for baixue took 3.330206871032715s
Availability | SPARQL endpoint availability check for baixue composer took 8.678436279296875e-05s
Availability | VoID file availability check for baixue composer took 0.0006325244903564453s
Completeness | Calculation of interlinking completeness for baixue composer took 0.2678844928741455s
Reputation | Calculation of the PageRank for baixue composer took 0.02071380615234375s
Interlinking | Calculation of Degree of Connection for baixue composer took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for baixue composer took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for baixue composer took 3.2901763916015625e-05s
Believability | Calculation of trust value for baixue composer took 1.2159347534179688e-05s
INFO | --- Analysis for baixue_composer took 3.117800235748291s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 4.57763671875e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.000614166259765625s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.2665069103240967s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.02033209800720215s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0008158683776855469s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.0279159545898438e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.239776611328125e-05s
INFO | --- Analysis for baixue_imagery took 2.772691249847412s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 4.410743713378906e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.2632119655609131s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020888328552246094s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.147125244140625e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.2636184692382812e-05s
INFO | --- Analysis for baixue_imagery1 took 4.117333173751831s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 9.107589721679688e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.0007736682891845703s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 0.2658576965332031s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.020740747451782227s
Interlinking | Calculation of Degree of Connection for Basque EuroWordNet-lemon lexicon (3.0) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Basque EuroWordNet-lemon lexicon (3.0) took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 4.2438507080078125e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 1.1920928955078125e-05s
INFO | --- Analysis for basque-eurowordnet-lemon-lexicon-3-0 took 3.0166923999786377s
Availability | SPARQL endpoint availability check for BBC Music took 0.4606459140777588s
Availability | VoID file availability check for BBC Music took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for BBC Music took 0.26035022735595703s
Reputation | Calculation of the PageRank for BBC Music took 0.021434307098388672s
Interlinking | Calculation of Degree of Connection for BBC Music took 3.600120544433594e-05s
Interlinking | Calculation of Centrality for BBC Music took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.0001289844512939453s
Believability | Calculation of trust value for BBC Music took 1.1920928955078125e-05s
INFO | --- Analysis for bbc-music took 6.246516227722168s
Availability | SPARQL endpoint availability check for BBC Programmes took 1.3496358394622803s
Availability | VoID file availability check for BBC Programmes took 0.0003063678741455078s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.2731659412384033s
Reputation | Calculation of the PageRank for BBC Programmes took 0.022774696350097656s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 0.00010251998901367188s
Believability | Calculation of trust value for BBC Programmes took 1.1444091796875e-05s
INFO | --- Analysis for bbc-programmes took 11.836082458496094s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.223252534866333s
Availability | VoID file availability check for BBC Wildlife Finder took 0.00039577484130859375s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 0.2571101188659668s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.020638465881347656s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 0.00010037422180175781s
Believability | Calculation of trust value for BBC Wildlife Finder took 6.9141387939453125e-06s
INFO | --- Analysis for bbc-wildlife-finder took 9.335839986801147s
Availability | SPARQL endpoint availability check for BBOP took 8.702278137207031e-05s
Availability | VoID file availability check for BBOP took 0.0007402896881103516s
Completeness | Calculation of interlinking completeness for BBOP took 0.26557445526123047s
Reputation | Calculation of the PageRank for BBOP took 0.020941734313964844s
Interlinking | Calculation of Degree of Connection for BBOP took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.0517578125e-05s
Believability | Calculation of trust value for BBOP took 7.62939453125e-06s
INFO | --- Analysis for bbop-selected took 20.139583587646484s
Availability | SPARQL endpoint availability check for Bdgp took 1.0219712257385254s
Availability | VoID file availability check for Bdgp took 0.0003261566162109375s
Completeness | Calculation of interlinking completeness for Bdgp took 0.2562096118927002s
Reputation | Calculation of the PageRank for Bdgp took 0.020431041717529297s
Interlinking | Calculation of Degree of Connection for Bdgp took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bdgp took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Bdgp took 2.9802322387695312e-05s
Believability | Calculation of trust value for Bdgp took 6.67572021484375e-06s
INFO | --- Analysis for bdgp took 4.470582485198975s
Availability | SPARQL endpoint availability check for Bendev Junior took 8.392333984375e-05s
Availability | VoID file availability check for Bendev Junior took 0.0005619525909423828s
Completeness | Calculation of interlinking completeness for Bendev Junior took 0.26630258560180664s
Reputation | Calculation of the PageRank for Bendev Junior took 0.020708084106445312s
Interlinking | Calculation of Degree of Connection for Bendev Junior took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bendev Junior took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Bendev Junior took 2.9325485229492188e-05s
Believability | Calculation of trust value for Bendev Junior took 1.0728836059570312e-05s
INFO | --- Analysis for bendevoficial took 2.95573353767395s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 6.223266363143921s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.0006990432739257812s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.2732863426208496s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.0212557315826416s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 7.200241088867188e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 8.106231689453125e-06s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 17.23910927772522s
Availability | SPARQL endpoint availability check for berlios took 4.1961669921875e-05s
Availability | VoID file availability check for berlios took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for berlios took 0.27992963790893555s
Reputation | Calculation of the PageRank for berlios took 0.022281408309936523s
Interlinking | Calculation of Degree of Connection for berlios took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for berlios took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for berlios took 8.511543273925781e-05s
Believability | Calculation of trust value for berlios took 1.0013580322265625e-05s
INFO | --- Analysis for berlios took 2.7568395137786865s
Availability | SPARQL endpoint availability check for Between Our Worlds took 8.416175842285156e-05s
Availability | VoID file availability check for Between Our Worlds took 0.0005731582641601562s
Completeness | Calculation of interlinking completeness for Between Our Worlds took 0.3115227222442627s
Reputation | Calculation of the PageRank for Between Our Worlds took 0.020441055297851562s
Interlinking | Calculation of Degree of Connection for Between Our Worlds took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Between Our Worlds took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Between Our Worlds took 6.389617919921875e-05s
Believability | Calculation of trust value for Between Our Worlds took 9.059906005859375e-06s
INFO | --- Analysis for betweenourworlds took 8.356280326843262s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.1006162166595459s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.2895991802215576s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.020786523818969727s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 8.893013000488281e-05s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 5.4836273193359375e-06s
INFO | --- Analysis for bfs-linked-data took 2.5623579025268555s
Availability | SPARQL endpoint availability check for BibBase took 0.06438279151916504s
Availability | VoID file availability check for BibBase took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for BibBase took 0.25878095626831055s
Reputation | Calculation of the PageRank for BibBase took 0.021044492721557617s
Interlinking | Calculation of Degree of Connection for BibBase took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for BibBase took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for BibBase took 9.5367431640625e-05s
Believability | Calculation of trust value for BibBase took 1.1205673217773438e-05s
INFO | --- Analysis for bibbase took 2.513875961303711s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 4.673004150390625e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.0007033348083496094s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.2724771499633789s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.02085280418395996s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 0.00012040138244628906s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 9.775161743164062e-06s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 7.642217397689819s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 4.100799560546875e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.0005738735198974609s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.2670133113861084s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.021036148071289062s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 9.822845458984375e-05s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 1.0251998901367188e-05s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 6.575667142868042s
Availability | SPARQL endpoint availability check for BibSonomy - The blue social bookmark and publication sharing system. took 4.076957702636719e-05s
Availability | VoID file availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for BibSonomy - The blue social bookmark and publication sharing system. took 0.2772965431213379s
Reputation | Calculation of the PageRank for BibSonomy - The blue social bookmark and publication sharing system. took 0.020496845245361328s
Interlinking | Calculation of Degree of Connection for BibSonomy - The blue social bookmark and publication sharing system. took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for BibSonomy - The blue social bookmark and publication sharing system. took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for BibSonomy - The blue social bookmark and publication sharing system. took 3.504753112792969e-05s
Believability | Calculation of trust value for BibSonomy - The blue social bookmark and publication sharing system. took 9.5367431640625e-06s
INFO | --- Analysis for BibSonomy took 12.349855661392212s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 8.511543273925781e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.0013115406036376953s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.2614116668701172s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.0203857421875s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 3.647804260253906e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 1.0013580322265625e-05s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 5.368171215057373s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 4.458427429199219e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 0.2618849277496338s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.020673751831054688s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2010 took 3.1948089599609375e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2010 took 1.0013580322265625e-05s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 2.7488675117492676s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 1.3831007480621338s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.0005204677581787109s
Extra | Recovery of all triples for Bio2RDF::Affymetrix took 19.024747610092163s
Performance | Total latancy measurement for Bio2RDF::Affymetrix took 0.47224855422973633s
Amount of data | Number of triples check for Bio2RDF::Affymetrix took 44.68358516693115s
Interoperability | New terms check for Bio2RDF::Affymetrix took 41.80777454376221s
Versatility | Languages check for Bio2RDF::Affymetrix took 60.11216497421265s
Interpretability | Number of blank nodes check for Bio2RDF::Affymetrix took 0.1310558319091797s
Interpretability | RDF structures check for Bio2RDF::Affymetrix took 0.8841707706451416s
Versatility | Serialization formats check for Bio2RDF::Affymetrix took 0.17672300338745117s
Availability | RDF dump link check for Bio2RDF::Affymetrix took 1.9765326976776123s
License | MR license check for Bio2RDF::Affymetrix took 0.3690650463104248s
License | HR license check for Bio2RDF::Affymetrix took 60.08909797668457s
Amount of data | Number of property check for Bio2RDF::Affymetrix took 0.12247037887573242s
Understandability | Number of label check for Bio2RDF::Affymetrix took 9.803207635879517s
Understandability | URI regex check for Bio2RDF::Affymetrix took 0.34960222244262695s
Understandability | Vocabs check for Bio2RDF::Affymetrix took 0.13112401962280273s
Verifiability | Authors check for Bio2RDF::Affymetrix took 0.13828325271606445s
Verifiability | Publishers check for Bio2RDF::Affymetrix took 0.12805724143981934s
Performance | Throughput check for Bio2RDF::Affymetrix took 10.50832200050354s
Amount of data | Check the number of entities for Bio2RDF::Affymetrix took 73.57002902030945s
Verifiability | Contribs. check for Bio2RDF::Affymetrix took 0.6463887691497803s
Interlinking | sameAs chians check for Bio2RDF::Affymetrix took 0.23967432975769043s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.8103961944580078s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.2371828556060791s
Timeliness | dataset update frequency check for Bio2RDF::Affymetrix took 0.0997772216796875s
Currency | Creation date check for Bio2RDF::Affymetrix took 0.23642730712890625s
Currency | Modification date check for Bio2RDF::Affymetrix took 0.21419239044189453s
Rep.Conc. | URIs length for Bio2RDF::Affymetrix took 107.79711890220642s
Interoperability | New vocabularies check for Bio2RDF::Affymetrix took 502.84219336509705s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Affymetrix took 0.7053313255310059s
Accuracy | Check Functional Property for Bio2RDF::Affymetrix took 0.1370706558227539s
Accuracy | Check Inverse Functional Property for Bio2RDF::Affymetrix took 0.11308503150939941s
Accuracy | Check Empty annotation labels for Bio2RDF::Affymetrix took 6.79058575630188s
Accuracy | Check White space in annotation for Bio2RDF::Affymetrix took 0.8831584453582764s
Accuracy | Check Datatype consistency for Bio2RDF::Affymetrix took 0.6466114521026611s
Consistency | Disjoint class check for Bio2RDF::Affymetrix took 0.257183313369751s
Consistency | Check Misplaced properties for Bio2RDF::Affymetrix took 65.01087498664856s
Consistency | Misplaced classes for Bio2RDF::Affymetrix took 2.2242112159729004s
Consistency | Check Ontology hijacking for Bio2RDF::Affymetrix took 6.350940227508545s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Affymetrix took 1.3161962032318115s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Affymetrix took 61.39495348930359s
Conciseness | Check Extensional conciseness for Bio2RDF::Affymetrix took 0.6943149566650391s
Conciseness | Check Intensional conciseness for Bio2RDF::Affymetrix took 0.2989645004272461s
Security | Sign check for Bio2RDF::Affymetrix took 0.10783886909484863s
Availability | Check URIs Dereferenciability for Bio2RDF::Affymetrix took 14.660969495773315s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 0.34991002082824707s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.020592212677001953s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 0.00010013580322265625s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Affymetrix took 881.623387336731s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-affymetrix took 2374.4160764217377s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 1.3864378929138184s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.0006041526794433594s
Extra | Recovery of all triples for Bio2RDF::Biomodels took 19.724644899368286s
Performance | Total latancy measurement for Bio2RDF::Biomodels took 1.144080400466919s
Amount of data | Number of triples check for Bio2RDF::Biomodels took 43.13018178939819s
Interoperability | New terms check for Bio2RDF::Biomodels took 40.59891963005066s
Versatility | Languages check for Bio2RDF::Biomodels took 60.22883868217468s
Interpretability | Number of blank nodes check for Bio2RDF::Biomodels took 0.24823784828186035s
Security | Check HTTPS for Bio2RDF::Biomodels took 0.1516580581665039s
Interpretability | RDF structures check for Bio2RDF::Biomodels took 0.6526463031768799s
Versatility | Serialization formats check for Bio2RDF::Biomodels took 0.2950608730316162s
Availability | RDF dump link check for Bio2RDF::Biomodels took 1.9778969287872314s
License | MR license check for Bio2RDF::Biomodels took 0.4974803924560547s
License | HR license check for Bio2RDF::Biomodels took 60.23022413253784s
Amount of data | Number of property check for Bio2RDF::Biomodels took 0.24115324020385742s
Understandability | Number of label check for Bio2RDF::Biomodels took 10.733672857284546s
Understandability | URI regex check for Bio2RDF::Biomodels took 0.5392622947692871s
Understandability | Vocabs check for Bio2RDF::Biomodels took 0.24226140975952148s
Verifiability | Authors check for Bio2RDF::Biomodels took 0.2378826141357422s
Verifiability | Publishers check for Bio2RDF::Biomodels took 0.23696160316467285s
Performance | Throughput check for Bio2RDF::Biomodels took 11.611910820007324s
Amount of data | Check the number of entities for Bio2RDF::Biomodels took 72.09036612510681s
Verifiability | Contribs. check for Bio2RDF::Biomodels took 0.6915552616119385s
Interlinking | sameAs chians check for Bio2RDF::Biomodels took 0.33818793296813965s
Interlinking | skos check for Bio2RDF::Biomodels took 0.8025832176208496s
Interlinking | skos check for Bio2RDF::Biomodels took 0.32849836349487305s
Timeliness | dataset update frequency check for Bio2RDF::Biomodels took 0.2382197380065918s
Currency | Creation date check for Bio2RDF::Biomodels took 0.4695923328399658s
Currency | Modification date check for Bio2RDF::Biomodels took 0.4761669635772705s
Rep.Conc. | URIs length for Bio2RDF::Biomodels took 107.9266471862793s
Interoperability | New vocabularies check for Bio2RDF::Biomodels took 49.25786089897156s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Biomodels took 0.39427900314331055s
Accuracy | Check Functional Property for Bio2RDF::Biomodels took 0.25316333770751953s
Accuracy | Check Inverse Functional Property for Bio2RDF::Biomodels took 0.25522780418395996s
Accuracy | Check Empty annotation labels for Bio2RDF::Biomodels took 6.547328948974609s
Accuracy | Check White space in annotation for Bio2RDF::Biomodels took 0.8852999210357666s
Accuracy | Check Datatype consistency for Bio2RDF::Biomodels took 0.630751371383667s
Consistency | Disjoint class check for Bio2RDF::Biomodels took 0.3812856674194336s
Consistency | Check Misplaced properties for Bio2RDF::Biomodels took 65.44490885734558s
Consistency | Misplaced classes for Bio2RDF::Biomodels took 2.3023030757904053s
Consistency | Check Ontology hijacking for Bio2RDF::Biomodels took 5.847338676452637s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Biomodels took 1.2513229846954346s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Biomodels took 61.46707081794739s
Conciseness | Check Extensional conciseness for Bio2RDF::Biomodels took 0.6842617988586426s
Conciseness | Check Intensional conciseness for Bio2RDF::Biomodels took 0.6943836212158203s
Security | Sign check for Bio2RDF::Biomodels took 0.25528860092163086s
Availability | Check URIs Dereferenciability for Bio2RDF::Biomodels took 10.063941478729248s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 0.4948859214782715s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.019997358322143555s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0006864070892333984s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.00011014938354492188s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Biomodels took 448.4895133972168s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 6.4373016357421875e-06s
INFO | --- Analysis for bio2rdf-biomodels took 1490.7485151290894s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 0.5578784942626953s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.0006413459777832031s
Extra | Recovery of all triples for Bio2RDF::Bioportal took 19.36389684677124s
Performance | Total latancy measurement for Bio2RDF::Bioportal took 1.1665010452270508s
Amount of data | Number of triples check for Bio2RDF::Bioportal took 43.602277517318726s
Interoperability | New terms check for Bio2RDF::Bioportal took 42.45610475540161s
Versatility | Languages check for Bio2RDF::Bioportal took 60.2287757396698s
Interpretability | Number of blank nodes check for Bio2RDF::Bioportal took 0.24793148040771484s
Security | Check HTTPS for Bio2RDF::Bioportal took 0.14475655555725098s
Interpretability | RDF structures check for Bio2RDF::Bioportal took 0.2428579330444336s
Versatility | Serialization formats check for Bio2RDF::Bioportal took 0.2945573329925537s
Availability | RDF dump link check for Bio2RDF::Bioportal took 1.9365196228027344s
License | MR license check for Bio2RDF::Bioportal took 0.4587132930755615s
License | HR license check for Bio2RDF::Bioportal took 60.23020386695862s
Amount of data | Number of property check for Bio2RDF::Bioportal took 0.24077248573303223s
Understandability | Number of label check for Bio2RDF::Bioportal took 10.18129849433899s
Understandability | URI regex check for Bio2RDF::Bioportal took 0.5413508415222168s
Understandability | Vocabs check for Bio2RDF::Bioportal took 0.23333168029785156s
Verifiability | Authors check for Bio2RDF::Bioportal took 0.2384636402130127s
Verifiability | Publishers check for Bio2RDF::Bioportal took 0.23660778999328613s
Performance | Throughput check for Bio2RDF::Bioportal took 11.554640293121338s
Amount of data | Check the number of entities for Bio2RDF::Bioportal took 73.84339332580566s
Verifiability | Contribs. check for Bio2RDF::Bioportal took 0.682358980178833s
Interlinking | sameAs chians check for Bio2RDF::Bioportal took 0.3641049861907959s
Interlinking | skos check for Bio2RDF::Bioportal took 0.7844336032867432s
Interlinking | skos check for Bio2RDF::Bioportal took 0.32132434844970703s
Timeliness | dataset update frequency check for Bio2RDF::Bioportal took 0.24690723419189453s
Currency | Creation date check for Bio2RDF::Bioportal took 0.47179102897644043s
Currency | Modification date check for Bio2RDF::Bioportal took 0.47039246559143066s
Rep.Conc. | URIs length for Bio2RDF::Bioportal took 107.83155298233032s
Interoperability | New vocabularies check for Bio2RDF::Bioportal took 469.5812051296234s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Bioportal took 0.8364293575286865s
Accuracy | Check Functional Property for Bio2RDF::Bioportal took 0.26540660858154297s
Accuracy | Check Inverse Functional Property for Bio2RDF::Bioportal took 0.26145482063293457s
Accuracy | Check Empty annotation labels for Bio2RDF::Bioportal took 7.454588890075684s
Accuracy | Check White space in annotation for Bio2RDF::Bioportal took 0.878704309463501s
Accuracy | Check Datatype consistency for Bio2RDF::Bioportal took 0.6477634906768799s
Consistency | Disjoint class check for Bio2RDF::Bioportal took 0.45264697074890137s
Consistency | Check Misplaced properties for Bio2RDF::Bioportal took 65.1077606678009s
Consistency | Misplaced classes for Bio2RDF::Bioportal took 2.340259552001953s
Consistency | Check Ontology hijacking for Bio2RDF::Bioportal took 6.190133571624756s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Bioportal took 1.2986526489257812s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Bioportal took 61.51304030418396s
Conciseness | Check Extensional conciseness for Bio2RDF::Bioportal took 0.7197051048278809s
Conciseness | Check Intensional conciseness for Bio2RDF::Bioportal took 0.39940762519836426s
Security | Sign check for Bio2RDF::Bioportal took 0.2581937313079834s
Availability | Check URIs Dereferenciability for Bio2RDF::Bioportal took 10.960051536560059s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 0.5046875476837158s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.02097630500793457s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.0004105567932128906s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Bioportal took 469.6141812801361s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 2.2172927856445312e-05s
INFO | --- Analysis for bio2rdf-bioportal took 1940.7635128498077s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 0.1356968879699707s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.00039958953857421875s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 0.2835988998413086s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.022908687591552734s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.0007824897766113281s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 7.152557373046875e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-chembl took 15.694844245910645s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 0.5715010166168213s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.0003674030303955078s
Extra | Recovery of all triples for Bio2RDF::Clinicaltrials took 18.077547073364258s
Performance | Total latancy measurement for Bio2RDF::Clinicaltrials took 1.172489881515503s
Amount of data | Number of triples check for Bio2RDF::Clinicaltrials took 43.921443700790405s
Interoperability | New terms check for Bio2RDF::Clinicaltrials took 41.1342339515686s
Versatility | Languages check for Bio2RDF::Clinicaltrials took 60.23006868362427s
Interpretability | Number of blank nodes check for Bio2RDF::Clinicaltrials took 0.2504711151123047s
Security | Check HTTPS for Bio2RDF::Clinicaltrials took 0.14417576789855957s
Interpretability | RDF structures check for Bio2RDF::Clinicaltrials took 0.6461122035980225s
Versatility | Serialization formats check for Bio2RDF::Clinicaltrials took 0.29190683364868164s
Availability | RDF dump link check for Bio2RDF::Clinicaltrials took 1.9068858623504639s
License | MR license check for Bio2RDF::Clinicaltrials took 0.4880654811859131s
License | HR license check for Bio2RDF::Clinicaltrials took 60.23149085044861s
Amount of data | Number of property check for Bio2RDF::Clinicaltrials took 0.23374104499816895s
Understandability | Number of label check for Bio2RDF::Clinicaltrials took 10.130295515060425s
Understandability | URI regex check for Bio2RDF::Clinicaltrials took 0.547100305557251s
Understandability | Vocabs check for Bio2RDF::Clinicaltrials took 0.24381661415100098s
Verifiability | Authors check for Bio2RDF::Clinicaltrials took 0.23625993728637695s
Verifiability | Publishers check for Bio2RDF::Clinicaltrials took 0.23566269874572754s
Performance | Throughput check for Bio2RDF::Clinicaltrials took 11.542797803878784s
Amount of data | Check the number of entities for Bio2RDF::Clinicaltrials took 74.58119869232178s
Verifiability | Contribs. check for Bio2RDF::Clinicaltrials took 1.4863743782043457s
Interlinking | sameAs chians check for Bio2RDF::Clinicaltrials took 0.32333874702453613s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.7466611862182617s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.33052849769592285s
Timeliness | dataset update frequency check for Bio2RDF::Clinicaltrials took 0.23569321632385254s
Currency | Creation date check for Bio2RDF::Clinicaltrials took 0.47608184814453125s
Currency | Modification date check for Bio2RDF::Clinicaltrials took 0.4687361717224121s
Rep.Conc. | URIs length for Bio2RDF::Clinicaltrials took 107.59388327598572s
Interoperability | New vocabularies check for Bio2RDF::Clinicaltrials took 105.27618384361267s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Clinicaltrials took 0.39064455032348633s
Accuracy | Check Functional Property for Bio2RDF::Clinicaltrials took 0.25470614433288574s
Accuracy | Check Inverse Functional Property for Bio2RDF::Clinicaltrials took 0.26059794425964355s
Accuracy | Check Empty annotation labels for Bio2RDF::Clinicaltrials took 7.440805912017822s
Accuracy | Check White space in annotation for Bio2RDF::Clinicaltrials took 0.8787379264831543s
Accuracy | Check Datatype consistency for Bio2RDF::Clinicaltrials took 0.6348662376403809s
Consistency | Disjoint class check for Bio2RDF::Clinicaltrials took 0.3950045108795166s
Consistency | Check Misplaced properties for Bio2RDF::Clinicaltrials took 64.94573974609375s
Consistency | Misplaced classes for Bio2RDF::Clinicaltrials took 2.333036184310913s
Consistency | Check Ontology hijacking for Bio2RDF::Clinicaltrials took 5.96196174621582s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Clinicaltrials took 1.3253023624420166s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Clinicaltrials took 61.79316687583923s
Conciseness | Check Extensional conciseness for Bio2RDF::Clinicaltrials took 0.6923673152923584s
Conciseness | Check Intensional conciseness for Bio2RDF::Clinicaltrials took 0.39472174644470215s
Security | Sign check for Bio2RDF::Clinicaltrials took 0.2505192756652832s
Availability | Check URIs Dereferenciability for Bio2RDF::Clinicaltrials took 9.533527135848999s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 0.3048996925354004s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.02088141441345215s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 5.507469177246094e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Clinicaltrials took 463.63856053352356s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 1.8358230590820312e-05s
INFO | --- Analysis for bio2rdf-clinicaltrials took 1564.8959579467773s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 0.5648608207702637s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.0007052421569824219s
Extra | Recovery of all triples for Bio2RDF::Ctd took 18.256033897399902s
Performance | Total latancy measurement for Bio2RDF::Ctd took 1.159562110900879s
Amount of data | Number of triples check for Bio2RDF::Ctd took 43.31156802177429s
Interoperability | New terms check for Bio2RDF::Ctd took 40.991495847702026s
Versatility | Languages check for Bio2RDF::Ctd took 60.23226523399353s
Interpretability | Number of blank nodes check for Bio2RDF::Ctd took 0.24709486961364746s
Security | Check HTTPS for Bio2RDF::Ctd took 0.1455090045928955s
Interpretability | RDF structures check for Bio2RDF::Ctd took 0.6509623527526855s
Versatility | Serialization formats check for Bio2RDF::Ctd took 0.28490710258483887s
Availability | RDF dump link check for Bio2RDF::Ctd took 1.8878750801086426s
License | MR license check for Bio2RDF::Ctd took 0.5200235843658447s
License | HR license check for Bio2RDF::Ctd took 60.230501651763916s
Amount of data | Number of property check for Bio2RDF::Ctd took 0.25900769233703613s
Understandability | Number of label check for Bio2RDF::Ctd took 9.554803371429443s
Understandability | URI regex check for Bio2RDF::Ctd took 0.5392842292785645s
Understandability | Vocabs check for Bio2RDF::Ctd took 0.23792576789855957s
Verifiability | Authors check for Bio2RDF::Ctd took 0.23695921897888184s
Verifiability | Publishers check for Bio2RDF::Ctd took 0.23531889915466309s
Performance | Throughput check for Bio2RDF::Ctd took 11.523245096206665s
Amount of data | Check the number of entities for Bio2RDF::Ctd took 73.40392565727234s
Verifiability | Contribs. check for Bio2RDF::Ctd took 0.6555612087249756s
Interlinking | sameAs chians check for Bio2RDF::Ctd took 0.3575127124786377s
Interlinking | skos check for Bio2RDF::Ctd took 0.8356049060821533s
Interlinking | skos check for Bio2RDF::Ctd took 0.3196539878845215s
Timeliness | dataset update frequency check for Bio2RDF::Ctd took 0.23475146293640137s
Currency | Creation date check for Bio2RDF::Ctd took 0.4647369384765625s
Currency | Modification date check for Bio2RDF::Ctd took 0.47575926780700684s
Rep.Conc. | URIs length for Bio2RDF::Ctd took 107.14811420440674s
Interoperability | New vocabularies check for Bio2RDF::Ctd took 33.228392362594604s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ctd took 0.39353084564208984s
Accuracy | Check Functional Property for Bio2RDF::Ctd took 0.2601127624511719s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ctd took 0.2559051513671875s
Accuracy | Check Empty annotation labels for Bio2RDF::Ctd took 6.844376802444458s
Accuracy | Check White space in annotation for Bio2RDF::Ctd took 0.8896002769470215s
Accuracy | Check Datatype consistency for Bio2RDF::Ctd took 0.6413674354553223s
Consistency | Disjoint class check for Bio2RDF::Ctd took 0.40267229080200195s
Consistency | Check Misplaced properties for Bio2RDF::Ctd took 65.2083888053894s
Consistency | Misplaced classes for Bio2RDF::Ctd took 2.310912847518921s
Consistency | Check Ontology hijacking for Bio2RDF::Ctd took 6.2871599197387695s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ctd took 1.2560322284698486s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ctd took 61.47590517997742s
Conciseness | Check Extensional conciseness for Bio2RDF::Ctd took 0.6852848529815674s
Conciseness | Check Intensional conciseness for Bio2RDF::Ctd took 0.39444613456726074s
Security | Sign check for Bio2RDF::Ctd took 0.24851202964782715s
Availability | Check URIs Dereferenciability for Bio2RDF::Ctd took 19.732449054718018s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 0.36363744735717773s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.0207822322845459s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0008304119110107422s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 6.771087646484375e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ctd took 486.31496024131775s
Believability | Calculation of trust value for Bio2RDF::Ctd took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-ctd took 1524.5265996456146s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 4.267692565917969e-05s
Availability | VoID file availability check for bio2rdf-dataset took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 0.26285624504089355s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.020707130432128906s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 5.1021575927734375e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 1.0013580322265625e-05s
INFO | --- Analysis for bio2rdf-dataset took 2.736222505569458s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 0.5625197887420654s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.0005981922149658203s
Extra | Recovery of all triples for Bio2RDF::Dbsnp took 18.38661217689514s
Performance | Total latancy measurement for Bio2RDF::Dbsnp took 1.1486225128173828s
Amount of data | Number of triples check for Bio2RDF::Dbsnp took 44.67407560348511s
Interoperability | New terms check for Bio2RDF::Dbsnp took 43.87758803367615s
Versatility | Languages check for Bio2RDF::Dbsnp took 60.23067593574524s
Interpretability | Number of blank nodes check for Bio2RDF::Dbsnp took 0.2477102279663086s
Security | Check HTTPS for Bio2RDF::Dbsnp took 0.14545798301696777s
Interpretability | RDF structures check for Bio2RDF::Dbsnp took 0.7418549060821533s
Versatility | Serialization formats check for Bio2RDF::Dbsnp took 0.29773736000061035s
Availability | RDF dump link check for Bio2RDF::Dbsnp took 2.134040117263794s
License | MR license check for Bio2RDF::Dbsnp took 0.48236608505249023s
License | HR license check for Bio2RDF::Dbsnp took 60.22930717468262s
Amount of data | Number of property check for Bio2RDF::Dbsnp took 0.25874900817871094s
Understandability | Number of label check for Bio2RDF::Dbsnp took 9.951099634170532s
Understandability | URI regex check for Bio2RDF::Dbsnp took 0.5383567810058594s
Understandability | Vocabs check for Bio2RDF::Dbsnp took 0.2389237880706787s
Verifiability | Authors check for Bio2RDF::Dbsnp took 0.2375497817993164s
Verifiability | Publishers check for Bio2RDF::Dbsnp took 0.2351527214050293s
Performance | Throughput check for Bio2RDF::Dbsnp took 11.546065330505371s
Amount of data | Check the number of entities for Bio2RDF::Dbsnp took 76.24550271034241s
Verifiability | Contribs. check for Bio2RDF::Dbsnp took 0.6554586887359619s
Interlinking | sameAs chians check for Bio2RDF::Dbsnp took 0.3345503807067871s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.8391628265380859s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.3232591152191162s
Timeliness | dataset update frequency check for Bio2RDF::Dbsnp took 0.2367115020751953s
Currency | Creation date check for Bio2RDF::Dbsnp took 0.46766209602355957s
Currency | Modification date check for Bio2RDF::Dbsnp took 0.46630239486694336s
Rep.Conc. | URIs length for Bio2RDF::Dbsnp took 107.54230046272278s
Interoperability | New vocabularies check for Bio2RDF::Dbsnp took 896.5391373634338s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Dbsnp took 2.2776968479156494s
Accuracy | Check Functional Property for Bio2RDF::Dbsnp took 0.26244521141052246s
Accuracy | Check Inverse Functional Property for Bio2RDF::Dbsnp took 0.2618439197540283s
Accuracy | Check Empty annotation labels for Bio2RDF::Dbsnp took 7.4690258502960205s
Accuracy | Check White space in annotation for Bio2RDF::Dbsnp took 0.8752660751342773s
Accuracy | Check Datatype consistency for Bio2RDF::Dbsnp took 0.6577110290527344s
Consistency | Disjoint class check for Bio2RDF::Dbsnp took 0.42454957962036133s
Consistency | Check Misplaced properties for Bio2RDF::Dbsnp took 64.87370300292969s
Consistency | Misplaced classes for Bio2RDF::Dbsnp took 2.324395179748535s
Consistency | Check Ontology hijacking for Bio2RDF::Dbsnp took 6.61406683921814s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Dbsnp took 1.323087453842163s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Dbsnp took 61.55756950378418s
Conciseness | Check Extensional conciseness for Bio2RDF::Dbsnp took 0.7099494934082031s
Conciseness | Check Intensional conciseness for Bio2RDF::Dbsnp took 0.39351916313171387s
Security | Sign check for Bio2RDF::Dbsnp took 0.24416422843933105s
Availability | Check URIs Dereferenciability for Bio2RDF::Dbsnp took 10.089103698730469s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 0.4501328468322754s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.02088141441345215s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 7.271766662597656e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Dbsnp took 870.3021047115326s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 1.0967254638671875e-05s
INFO | --- Analysis for bio2rdf-dbsnp took 2767.9250586032867s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 0.5633854866027832s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.0006992816925048828s
Extra | Recovery of all triples for Bio2RDF::Drugbank took 19.805046319961548s
Performance | Total latancy measurement for Bio2RDF::Drugbank took 1.1456108093261719s
Amount of data | Number of triples check for Bio2RDF::Drugbank took 43.15599870681763s
Interoperability | New terms check for Bio2RDF::Drugbank took 40.0997416973114s
Versatility | Languages check for Bio2RDF::Drugbank took 60.26303148269653s
Interpretability | Number of blank nodes check for Bio2RDF::Drugbank took 0.2446126937866211s
Security | Check HTTPS for Bio2RDF::Drugbank took 0.14301109313964844s
Interpretability | RDF structures check for Bio2RDF::Drugbank took 0.7779622077941895s
Versatility | Serialization formats check for Bio2RDF::Drugbank took 0.2805135250091553s
Availability | RDF dump link check for Bio2RDF::Drugbank took 1.9183948040008545s
License | MR license check for Bio2RDF::Drugbank took 0.5284039974212646s
License | HR license check for Bio2RDF::Drugbank took 60.23202037811279s
Amount of data | Number of property check for Bio2RDF::Drugbank took 0.2376408576965332s
Understandability | Number of label check for Bio2RDF::Drugbank took 10.539367914199829s
Understandability | URI regex check for Bio2RDF::Drugbank took 0.544497013092041s
Understandability | Vocabs check for Bio2RDF::Drugbank took 0.23894739151000977s
Verifiability | Authors check for Bio2RDF::Drugbank took 0.2358994483947754s
Verifiability | Publishers check for Bio2RDF::Drugbank took 0.2433457374572754s
Performance | Throughput check for Bio2RDF::Drugbank took 11.591480016708374s
Amount of data | Check the number of entities for Bio2RDF::Drugbank took 70.35410594940186s
Verifiability | Contribs. check for Bio2RDF::Drugbank took 0.6654832363128662s
Interlinking | sameAs chians check for Bio2RDF::Drugbank took 0.33722519874572754s
Interlinking | skos check for Bio2RDF::Drugbank took 0.8247463703155518s
Interlinking | skos check for Bio2RDF::Drugbank took 0.33150339126586914s
Timeliness | dataset update frequency check for Bio2RDF::Drugbank took 0.2429332733154297s
Currency | Creation date check for Bio2RDF::Drugbank took 0.4728832244873047s
Currency | Modification date check for Bio2RDF::Drugbank took 0.46749091148376465s
Rep.Conc. | URIs length for Bio2RDF::Drugbank took 107.71933555603027s
Interoperability | New vocabularies check for Bio2RDF::Drugbank took 892.1040372848511s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Drugbank took 0.809769868850708s
Accuracy | Check Functional Property for Bio2RDF::Drugbank took 0.2591416835784912s
Accuracy | Check Inverse Functional Property for Bio2RDF::Drugbank took 0.25332117080688477s
Accuracy | Check Empty annotation labels for Bio2RDF::Drugbank took 6.998489618301392s
Accuracy | Check White space in annotation for Bio2RDF::Drugbank took 0.8811304569244385s
Accuracy | Check Datatype consistency for Bio2RDF::Drugbank took 0.6508810520172119s
Consistency | Disjoint class check for Bio2RDF::Drugbank took 0.3709888458251953s
Consistency | Check Misplaced properties for Bio2RDF::Drugbank took 65.53729701042175s
Consistency | Misplaced classes for Bio2RDF::Drugbank took 2.3203518390655518s
Consistency | Check Ontology hijacking for Bio2RDF::Drugbank took 6.2918009757995605s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Drugbank took 1.2636387348175049s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Drugbank took 61.49330997467041s
Conciseness | Check Extensional conciseness for Bio2RDF::Drugbank took 0.6892879009246826s
Conciseness | Check Intensional conciseness for Bio2RDF::Drugbank took 0.39311981201171875s
Security | Sign check for Bio2RDF::Drugbank took 0.24605226516723633s
Availability | Check URIs Dereferenciability for Bio2RDF::Drugbank took 10.83576774597168s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 0.4650564193725586s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.020348072052001953s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.00012803077697753906s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Drugbank took 501.4556438922882s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-drugbank took 2393.5303103923798s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 0.5706169605255127s
Availability | VoID file availability check for Bio2RDF::Genage took 0.0008852481842041016s
Extra | Recovery of all triples for Bio2RDF::Genage took 17.835160732269287s
Performance | Total latancy measurement for Bio2RDF::Genage took 1.143388271331787s
Amount of data | Number of triples check for Bio2RDF::Genage took 43.824044704437256s
Interoperability | New terms check for Bio2RDF::Genage took 41.43095684051514s
Versatility | Languages check for Bio2RDF::Genage took 60.23042321205139s
Interpretability | Number of blank nodes check for Bio2RDF::Genage took 0.2484734058380127s
Security | Check HTTPS for Bio2RDF::Genage took 0.14442229270935059s
Interpretability | RDF structures check for Bio2RDF::Genage took 0.5744383335113525s
Versatility | Serialization formats check for Bio2RDF::Genage took 0.2882230281829834s
Availability | RDF dump link check for Bio2RDF::Genage took 2.083954095840454s
License | MR license check for Bio2RDF::Genage took 0.4406619071960449s
License | HR license check for Bio2RDF::Genage took 60.23110222816467s
Amount of data | Number of property check for Bio2RDF::Genage took 0.23464226722717285s
Understandability | Number of label check for Bio2RDF::Genage took 10.149219989776611s
Understandability | URI regex check for Bio2RDF::Genage took 0.543316125869751s
Understandability | Vocabs check for Bio2RDF::Genage took 0.2500584125518799s
Verifiability | Authors check for Bio2RDF::Genage took 0.24117136001586914s
Verifiability | Publishers check for Bio2RDF::Genage took 0.23896408081054688s
Performance | Throughput check for Bio2RDF::Genage took 11.702678203582764s
Amount of data | Check the number of entities for Bio2RDF::Genage took 73.13403630256653s
Verifiability | Contribs. check for Bio2RDF::Genage took 0.677666425704956s
Interlinking | sameAs chians check for Bio2RDF::Genage took 0.3250398635864258s
Interlinking | skos check for Bio2RDF::Genage took 0.8769991397857666s
Interlinking | skos check for Bio2RDF::Genage took 0.3184494972229004s
Timeliness | dataset update frequency check for Bio2RDF::Genage took 0.2358253002166748s
Currency | Creation date check for Bio2RDF::Genage took 0.466228723526001s
Currency | Modification date check for Bio2RDF::Genage took 0.4678456783294678s
Rep.Conc. | URIs length for Bio2RDF::Genage took 107.49234819412231s
Interoperability | New vocabularies check for Bio2RDF::Genage took 891.5536115169525s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Genage took 1.767263650894165s
Accuracy | Check Functional Property for Bio2RDF::Genage took 0.258150577545166s
Accuracy | Check Inverse Functional Property for Bio2RDF::Genage took 0.2557342052459717s
Accuracy | Check Empty annotation labels for Bio2RDF::Genage took 7.302058935165405s
Accuracy | Check White space in annotation for Bio2RDF::Genage took 0.882103681564331s
Accuracy | Check Datatype consistency for Bio2RDF::Genage took 0.6465644836425781s
Consistency | Disjoint class check for Bio2RDF::Genage took 0.3763258457183838s
Consistency | Check Misplaced properties for Bio2RDF::Genage took 64.8742778301239s
Consistency | Misplaced classes for Bio2RDF::Genage took 2.355760097503662s
Consistency | Check Ontology hijacking for Bio2RDF::Genage took 6.033523321151733s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Genage took 1.316713571548462s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Genage took 61.479546308517456s
Conciseness | Check Extensional conciseness for Bio2RDF::Genage took 0.71250319480896s
Conciseness | Check Intensional conciseness for Bio2RDF::Genage took 0.3986961841583252s
Security | Sign check for Bio2RDF::Genage took 0.25083327293395996s
Availability | Check URIs Dereferenciability for Bio2RDF::Genage took 21.099517345428467s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 0.7822496891021729s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.020373106002807617s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 5.7220458984375e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Genage took 903.0062968730927s
Believability | Calculation of trust value for Bio2RDF::Genage took 1.1444091796875e-05s
INFO | --- Analysis for bio2rdf-genage took 2801.3652172088623s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 0.5604457855224609s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.0006041526794433594s
Extra | Recovery of all triples for Bio2RDF::Gendr took 18.421415328979492s
Performance | Total latancy measurement for Bio2RDF::Gendr took 1.1659071445465088s
Amount of data | Number of triples check for Bio2RDF::Gendr took 43.82341742515564s
Interoperability | New terms check for Bio2RDF::Gendr took 41.1030752658844s
Versatility | Languages check for Bio2RDF::Gendr took 60.2268545627594s
Interpretability | Number of blank nodes check for Bio2RDF::Gendr took 0.24810290336608887s
Security | Check HTTPS for Bio2RDF::Gendr took 0.14483118057250977s
Interpretability | RDF structures check for Bio2RDF::Gendr took 0.7607498168945312s
Versatility | Serialization formats check for Bio2RDF::Gendr took 0.2922687530517578s
Availability | RDF dump link check for Bio2RDF::Gendr took 2.072360038757324s
License | MR license check for Bio2RDF::Gendr took 0.47002172470092773s
License | HR license check for Bio2RDF::Gendr took 60.23050594329834s
Amount of data | Number of property check for Bio2RDF::Gendr took 0.23615741729736328s
Understandability | Number of label check for Bio2RDF::Gendr took 10.464090585708618s
Understandability | URI regex check for Bio2RDF::Gendr took 0.553063154220581s
Understandability | Vocabs check for Bio2RDF::Gendr took 0.2379319667816162s
Verifiability | Authors check for Bio2RDF::Gendr took 0.23789048194885254s
Verifiability | Publishers check for Bio2RDF::Gendr took 0.23790740966796875s
Performance | Throughput check for Bio2RDF::Gendr took 11.599051713943481s
Amount of data | Check the number of entities for Bio2RDF::Gendr took 71.6925323009491s
Verifiability | Contribs. check for Bio2RDF::Gendr took 0.683706521987915s
Interlinking | sameAs chians check for Bio2RDF::Gendr took 0.34728074073791504s
Interlinking | skos check for Bio2RDF::Gendr took 0.8116950988769531s
Interlinking | skos check for Bio2RDF::Gendr took 0.32903480529785156s
Timeliness | dataset update frequency check for Bio2RDF::Gendr took 0.23769688606262207s
Currency | Creation date check for Bio2RDF::Gendr took 0.4744532108306885s
Currency | Modification date check for Bio2RDF::Gendr took 0.4732232093811035s
Rep.Conc. | URIs length for Bio2RDF::Gendr took 108.09522104263306s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Gendr took 1.0285179615020752s
Accuracy | Check Functional Property for Bio2RDF::Gendr took 0.2671782970428467s
Accuracy | Check Inverse Functional Property for Bio2RDF::Gendr took 0.26668310165405273s
Accuracy | Check Empty annotation labels for Bio2RDF::Gendr took 7.016751766204834s
Accuracy | Check White space in annotation for Bio2RDF::Gendr took 0.88185715675354s
Accuracy | Check Datatype consistency for Bio2RDF::Gendr took 0.6473536491394043s
Consistency | Disjoint class check for Bio2RDF::Gendr took 0.426119327545166s
Consistency | Check Misplaced properties for Bio2RDF::Gendr took 64.86811923980713s
Consistency | Misplaced classes for Bio2RDF::Gendr took 2.333273410797119s
Consistency | Check Ontology hijacking for Bio2RDF::Gendr took 6.480489730834961s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Gendr took 1.30293607711792s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Gendr took 61.522237062454224s
Conciseness | Check Extensional conciseness for Bio2RDF::Gendr took 0.7181675434112549s
Conciseness | Check Intensional conciseness for Bio2RDF::Gendr took 0.395906925201416s
Security | Sign check for Bio2RDF::Gendr took 0.24983525276184082s
Availability | Check URIs Dereferenciability for Bio2RDF::Gendr took 11.672538995742798s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 0.47367191314697266s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.022064208984375s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 5.817413330078125e-05s
Believability | Calculation of trust value for Bio2RDF::Gendr took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-gendr took 2303.5062642097473s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 0.7078402042388916s
Availability | VoID file availability check for Bio2RDF::Goa took 0.0006470680236816406s
Extra | Recovery of all triples for Bio2RDF::Goa took 19.769535303115845s
Performance | Total latancy measurement for Bio2RDF::Goa took 1.1444005966186523s
Amount of data | Number of triples check for Bio2RDF::Goa took 44.55001473426819s
Interoperability | New terms check for Bio2RDF::Goa took 43.69793629646301s
Versatility | Languages check for Bio2RDF::Goa took 60.229039430618286s
Interpretability | Number of blank nodes check for Bio2RDF::Goa took 0.272083044052124s
Security | Check HTTPS for Bio2RDF::Goa took 0.14537930488586426s
Interpretability | RDF structures check for Bio2RDF::Goa took 0.8893609046936035s
Versatility | Serialization formats check for Bio2RDF::Goa took 0.2926328182220459s
Availability | RDF dump link check for Bio2RDF::Goa took 2.021150588989258s
License | MR license check for Bio2RDF::Goa took 0.42336511611938477s
License | HR license check for Bio2RDF::Goa took 60.232945919036865s
Amount of data | Number of property check for Bio2RDF::Goa took 0.23605966567993164s
Understandability | Number of label check for Bio2RDF::Goa took 9.585583448410034s
Understandability | URI regex check for Bio2RDF::Goa took 0.5398130416870117s
Understandability | Vocabs check for Bio2RDF::Goa took 0.23519682884216309s
Verifiability | Authors check for Bio2RDF::Goa took 0.23768234252929688s
Verifiability | Publishers check for Bio2RDF::Goa took 0.2358698844909668s
Performance | Throughput check for Bio2RDF::Goa took 11.542121648788452s
Amount of data | Check the number of entities for Bio2RDF::Goa took 76.09933114051819s
Verifiability | Contribs. check for Bio2RDF::Goa took 0.8141744136810303s
Interlinking | sameAs chians check for Bio2RDF::Goa took 0.3515896797180176s
Interlinking | skos check for Bio2RDF::Goa took 1.0773754119873047s
Interlinking | skos check for Bio2RDF::Goa took 0.33020567893981934s
Timeliness | dataset update frequency check for Bio2RDF::Goa took 0.23790931701660156s
Currency | Creation date check for Bio2RDF::Goa took 0.4724750518798828s
Currency | Modification date check for Bio2RDF::Goa took 0.46744441986083984s
Rep.Conc. | URIs length for Bio2RDF::Goa took 107.1720323562622s
Interoperability | New vocabularies check for Bio2RDF::Goa took 533.698278427124s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Goa took 0.8168845176696777s
Accuracy | Check Functional Property for Bio2RDF::Goa took 0.26142430305480957s
Accuracy | Check Inverse Functional Property for Bio2RDF::Goa took 0.25943446159362793s
Accuracy | Check Empty annotation labels for Bio2RDF::Goa took 7.48966383934021s
Accuracy | Check White space in annotation for Bio2RDF::Goa took 0.8781893253326416s
Accuracy | Check Datatype consistency for Bio2RDF::Goa took 0.6578516960144043s
Consistency | Disjoint class check for Bio2RDF::Goa took 0.5138812065124512s
Consistency | Check Misplaced properties for Bio2RDF::Goa took 65.68925213813782s
Consistency | Misplaced classes for Bio2RDF::Goa took 2.359531879425049s
Consistency | Check Ontology hijacking for Bio2RDF::Goa took 5.874633073806763s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Goa took 1.3028028011322021s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Goa took 61.54558563232422s
Conciseness | Check Extensional conciseness for Bio2RDF::Goa took 0.7233219146728516s
Conciseness | Check Intensional conciseness for Bio2RDF::Goa took 0.3944690227508545s
Security | Sign check for Bio2RDF::Goa took 0.24825286865234375s
Availability | Check URIs Dereferenciability for Bio2RDF::Goa took 10.390123128890991s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 0.5136494636535645s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.02051258087158203s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 6.937980651855469e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Goa took 510.07089352607727s
Believability | Calculation of trust value for Bio2RDF::Goa took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-goa took 2053.576739549637s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 0.5619246959686279s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.0007045269012451172s
Extra | Recovery of all triples for Bio2RDF::Hgnc took 18.58726191520691s
Performance | Total latancy measurement for Bio2RDF::Hgnc took 1.1352055072784424s
Amount of data | Number of triples check for Bio2RDF::Hgnc took 43.620285987854004s
Interoperability | New terms check for Bio2RDF::Hgnc took 40.917964696884155s
Versatility | Languages check for Bio2RDF::Hgnc took 60.230224609375s
Interpretability | Number of blank nodes check for Bio2RDF::Hgnc took 0.25177478790283203s
Security | Check HTTPS for Bio2RDF::Hgnc took 0.1449415683746338s
Interpretability | RDF structures check for Bio2RDF::Hgnc took 0.9152145385742188s
Versatility | Serialization formats check for Bio2RDF::Hgnc took 0.2895991802215576s
Availability | RDF dump link check for Bio2RDF::Hgnc took 1.919524908065796s
License | MR license check for Bio2RDF::Hgnc took 0.6014742851257324s
License | HR license check for Bio2RDF::Hgnc took 60.23028540611267s
Amount of data | Number of property check for Bio2RDF::Hgnc took 0.23379874229431152s
Understandability | Number of label check for Bio2RDF::Hgnc took 9.272990465164185s
Understandability | URI regex check for Bio2RDF::Hgnc took 0.536846399307251s
Understandability | Vocabs check for Bio2RDF::Hgnc took 0.2347869873046875s
Verifiability | Authors check for Bio2RDF::Hgnc took 0.2484588623046875s
Verifiability | Publishers check for Bio2RDF::Hgnc took 0.23602843284606934s
Performance | Throughput check for Bio2RDF::Hgnc took 11.548259973526001s
Amount of data | Check the number of entities for Bio2RDF::Hgnc took 75.64154767990112s
Verifiability | Contribs. check for Bio2RDF::Hgnc took 0.6560313701629639s
Interlinking | sameAs chians check for Bio2RDF::Hgnc took 0.33629727363586426s
Interlinking | skos check for Bio2RDF::Hgnc took 1.0100862979888916s
Interlinking | skos check for Bio2RDF::Hgnc took 0.3503234386444092s
Timeliness | dataset update frequency check for Bio2RDF::Hgnc took 0.2364795207977295s
Currency | Creation date check for Bio2RDF::Hgnc took 0.4664747714996338s
Currency | Modification date check for Bio2RDF::Hgnc took 0.4743771553039551s
Rep.Conc. | URIs length for Bio2RDF::Hgnc took 107.89103484153748s
Interoperability | New vocabularies check for Bio2RDF::Hgnc took 56.63207221031189s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Hgnc took 0.39432215690612793s
Accuracy | Check Functional Property for Bio2RDF::Hgnc took 0.2636222839355469s
Accuracy | Check Inverse Functional Property for Bio2RDF::Hgnc took 0.2597348690032959s
Accuracy | Check Empty annotation labels for Bio2RDF::Hgnc took 7.074197053909302s
Accuracy | Check White space in annotation for Bio2RDF::Hgnc took 0.8780815601348877s
Accuracy | Check Datatype consistency for Bio2RDF::Hgnc took 0.6555218696594238s
Consistency | Disjoint class check for Bio2RDF::Hgnc took 0.4132251739501953s
Consistency | Check Misplaced properties for Bio2RDF::Hgnc took 65.01917338371277s
Consistency | Misplaced classes for Bio2RDF::Hgnc took 2.365394115447998s
Consistency | Check Ontology hijacking for Bio2RDF::Hgnc took 6.216667413711548s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Hgnc took 1.317694902420044s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Hgnc took 61.49183750152588s
Conciseness | Check Extensional conciseness for Bio2RDF::Hgnc took 0.714895486831665s
Conciseness | Check Intensional conciseness for Bio2RDF::Hgnc took 0.6722555160522461s
Security | Sign check for Bio2RDF::Hgnc took 0.24164557456970215s
Availability | Check URIs Dereferenciability for Bio2RDF::Hgnc took 11.558866739273071s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 0.32048869132995605s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.02047896385192871s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.00011277198791503906s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Hgnc took 56.17700457572937s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-hgnc took 1107.9343657493591s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 0.5753574371337891s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.0003514289855957031s
Extra | Recovery of all triples for Bio2RDF::Homologene took 18.582392692565918s
Performance | Total latancy measurement for Bio2RDF::Homologene took 1.1653287410736084s
Amount of data | Number of triples check for Bio2RDF::Homologene took 43.75022339820862s
Interoperability | New terms check for Bio2RDF::Homologene took 40.70503807067871s
Versatility | Languages check for Bio2RDF::Homologene took 60.23374891281128s
Interpretability | Number of blank nodes check for Bio2RDF::Homologene took 0.24672198295593262s
Security | Check HTTPS for Bio2RDF::Homologene took 0.14279937744140625s
Interpretability | RDF structures check for Bio2RDF::Homologene took 0.7086379528045654s
Versatility | Serialization formats check for Bio2RDF::Homologene took 0.28707170486450195s
Availability | RDF dump link check for Bio2RDF::Homologene took 1.8649909496307373s
License | MR license check for Bio2RDF::Homologene took 0.46773195266723633s
License | HR license check for Bio2RDF::Homologene took 60.22821545600891s
Amount of data | Number of property check for Bio2RDF::Homologene took 0.23922395706176758s
Understandability | Number of label check for Bio2RDF::Homologene took 9.768303394317627s
Understandability | URI regex check for Bio2RDF::Homologene took 0.565781831741333s
Understandability | Vocabs check for Bio2RDF::Homologene took 0.2345714569091797s
Verifiability | Authors check for Bio2RDF::Homologene took 0.23534846305847168s
Verifiability | Publishers check for Bio2RDF::Homologene took 0.236281156539917s
Performance | Throughput check for Bio2RDF::Homologene took 11.561414241790771s
Amount of data | Check the number of entities for Bio2RDF::Homologene took 76.5395176410675s
Verifiability | Contribs. check for Bio2RDF::Homologene took 0.7495958805084229s
Interlinking | sameAs chians check for Bio2RDF::Homologene took 0.3451225757598877s
Interlinking | skos check for Bio2RDF::Homologene took 0.7423052787780762s
Interlinking | skos check for Bio2RDF::Homologene took 0.32788753509521484s
Timeliness | dataset update frequency check for Bio2RDF::Homologene took 0.2383279800415039s
Currency | Creation date check for Bio2RDF::Homologene took 0.47589969635009766s
Currency | Modification date check for Bio2RDF::Homologene took 0.4672582149505615s
Rep.Conc. | URIs length for Bio2RDF::Homologene took 108.2136971950531s
Interoperability | New vocabularies check for Bio2RDF::Homologene took 44.14426946640015s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Homologene took 0.4157428741455078s
Accuracy | Check Functional Property for Bio2RDF::Homologene took 0.25991082191467285s
Accuracy | Check Inverse Functional Property for Bio2RDF::Homologene took 0.26175570487976074s
Accuracy | Check Empty annotation labels for Bio2RDF::Homologene took 7.429127216339111s
Accuracy | Check White space in annotation for Bio2RDF::Homologene took 0.8801755905151367s
Accuracy | Check Datatype consistency for Bio2RDF::Homologene took 0.644615888595581s
Consistency | Disjoint class check for Bio2RDF::Homologene took 0.4501779079437256s
Consistency | Check Misplaced properties for Bio2RDF::Homologene took 64.95081186294556s
Consistency | Misplaced classes for Bio2RDF::Homologene took 2.3541135787963867s
Consistency | Check Ontology hijacking for Bio2RDF::Homologene took 6.449523687362671s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Homologene took 1.3165254592895508s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Homologene took 61.47867035865784s
Conciseness | Check Extensional conciseness for Bio2RDF::Homologene took 0.7137954235076904s
Conciseness | Check Intensional conciseness for Bio2RDF::Homologene took 0.6735706329345703s
Security | Sign check for Bio2RDF::Homologene took 0.24744176864624023s
Availability | Check URIs Dereferenciability for Bio2RDF::Homologene took 13.115443468093872s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 0.45430421829223633s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.020627260208129883s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 6.246566772460938e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Homologene took 45.951711654663086s
Believability | Calculation of trust value for Bio2RDF::Homologene took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-homologene took 1090.4741079807281s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 0.5632765293121338s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.0006434917449951172s
Extra | Recovery of all triples for Bio2RDF::Interpro took 17.93341636657715s
Performance | Total latancy measurement for Bio2RDF::Interpro took 1.156033992767334s
Amount of data | Number of triples check for Bio2RDF::Interpro took 43.86137890815735s
Interoperability | New terms check for Bio2RDF::Interpro took 40.93693447113037s
Versatility | Languages check for Bio2RDF::Interpro took 60.26003694534302s
Interpretability | Number of blank nodes check for Bio2RDF::Interpro took 0.2491455078125s
Security | Check HTTPS for Bio2RDF::Interpro took 0.14406442642211914s
Interpretability | RDF structures check for Bio2RDF::Interpro took 0.7536649703979492s
Versatility | Serialization formats check for Bio2RDF::Interpro took 0.2907900810241699s
Availability | RDF dump link check for Bio2RDF::Interpro took 2.061732769012451s
License | MR license check for Bio2RDF::Interpro took 0.47527623176574707s
License | HR license check for Bio2RDF::Interpro took 60.231961727142334s
Amount of data | Number of property check for Bio2RDF::Interpro took 0.23198533058166504s
Understandability | Number of label check for Bio2RDF::Interpro took 10.941471815109253s
Understandability | URI regex check for Bio2RDF::Interpro took 0.5419275760650635s
Understandability | Vocabs check for Bio2RDF::Interpro took 0.24469590187072754s
Verifiability | Authors check for Bio2RDF::Interpro took 0.2358713150024414s
Verifiability | Publishers check for Bio2RDF::Interpro took 0.23460650444030762s
Performance | Throughput check for Bio2RDF::Interpro took 11.616455793380737s
Amount of data | Check the number of entities for Bio2RDF::Interpro took 77.94623279571533s
Verifiability | Contribs. check for Bio2RDF::Interpro took 1.5903935432434082s
Interlinking | sameAs chians check for Bio2RDF::Interpro took 0.34617018699645996s
Interlinking | skos check for Bio2RDF::Interpro took 0.9230020046234131s
Interlinking | skos check for Bio2RDF::Interpro took 0.35321474075317383s
Timeliness | dataset update frequency check for Bio2RDF::Interpro took 0.23788738250732422s
Currency | Creation date check for Bio2RDF::Interpro took 0.4664335250854492s
Currency | Modification date check for Bio2RDF::Interpro took 0.46163320541381836s
Rep.Conc. | URIs length for Bio2RDF::Interpro took 113.68176555633545s
Interoperability | New vocabularies check for Bio2RDF::Interpro took 71.88423275947571s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Interpro took 0.38866591453552246s
Accuracy | Check Functional Property for Bio2RDF::Interpro took 0.25618648529052734s
Accuracy | Check Inverse Functional Property for Bio2RDF::Interpro took 0.2561509609222412s
Accuracy | Check Empty annotation labels for Bio2RDF::Interpro took 7.579176664352417s
Accuracy | Check White space in annotation for Bio2RDF::Interpro took 0.8906521797180176s
Accuracy | Check Datatype consistency for Bio2RDF::Interpro took 0.6703076362609863s
Consistency | Disjoint class check for Bio2RDF::Interpro took 0.3995954990386963s
Consistency | Check Misplaced properties for Bio2RDF::Interpro took 64.91690969467163s
Consistency | Misplaced classes for Bio2RDF::Interpro took 2.3425586223602295s
Consistency | Check Ontology hijacking for Bio2RDF::Interpro took 6.320261716842651s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Interpro took 1.3057489395141602s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Interpro took 61.514145612716675s
Conciseness | Check Extensional conciseness for Bio2RDF::Interpro took 0.7370083332061768s
Conciseness | Check Intensional conciseness for Bio2RDF::Interpro took 0.8183753490447998s
Security | Sign check for Bio2RDF::Interpro took 0.24851608276367188s
Availability | Check URIs Dereferenciability for Bio2RDF::Interpro took 12.40755319595337s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 0.5541014671325684s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.020282506942749023s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 0.00010991096496582031s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Interpro took 46.95675277709961s
Believability | Calculation of trust value for Bio2RDF::Interpro took 1.0967254638671875e-05s
INFO | --- Analysis for bio2rdf-interpro took 1129.007625579834s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 0.1374356746673584s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.0006108283996582031s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 0.26892518997192383s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.022054195404052734s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 7.939338684082031e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-iproclass took 15.414355993270874s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 0.575737714767456s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.0005881786346435547s
Extra | Recovery of all triples for Bio2RDF::Irefindex took 18.41866707801819s
Performance | Total latancy measurement for Bio2RDF::Irefindex took 1.1595776081085205s
Amount of data | Number of triples check for Bio2RDF::Irefindex took 43.89414024353027s
Interoperability | New terms check for Bio2RDF::Irefindex took 43.57428789138794s
Versatility | Languages check for Bio2RDF::Irefindex took 60.22782874107361s
Interpretability | Number of blank nodes check for Bio2RDF::Irefindex took 0.2455906867980957s
Security | Check HTTPS for Bio2RDF::Irefindex took 0.14316010475158691s
Interpretability | RDF structures check for Bio2RDF::Irefindex took 0.8772039413452148s
Versatility | Serialization formats check for Bio2RDF::Irefindex took 0.2870044708251953s
Availability | RDF dump link check for Bio2RDF::Irefindex took 2.045623540878296s
License | MR license check for Bio2RDF::Irefindex took 0.4597926139831543s
License | HR license check for Bio2RDF::Irefindex took 60.232659578323364s
Amount of data | Number of property check for Bio2RDF::Irefindex took 0.27013683319091797s
Understandability | Number of label check for Bio2RDF::Irefindex took 9.557951927185059s
Understandability | URI regex check for Bio2RDF::Irefindex took 0.5419788360595703s
Understandability | Vocabs check for Bio2RDF::Irefindex took 0.23453903198242188s
Verifiability | Authors check for Bio2RDF::Irefindex took 0.23734354972839355s
Verifiability | Publishers check for Bio2RDF::Irefindex took 0.23230743408203125s
Performance | Throughput check for Bio2RDF::Irefindex took 11.524105310440063s
Amount of data | Check the number of entities for Bio2RDF::Irefindex took 75.88704299926758s
Verifiability | Contribs. check for Bio2RDF::Irefindex took 0.6808686256408691s
Interlinking | sameAs chians check for Bio2RDF::Irefindex took 0.34534478187561035s
Interlinking | skos check for Bio2RDF::Irefindex took 0.813399076461792s
Interlinking | skos check for Bio2RDF::Irefindex took 0.329606294631958s
Timeliness | dataset update frequency check for Bio2RDF::Irefindex took 0.24044036865234375s
Currency | Creation date check for Bio2RDF::Irefindex took 0.4646453857421875s
Currency | Modification date check for Bio2RDF::Irefindex took 0.4643089771270752s
Rep.Conc. | URIs length for Bio2RDF::Irefindex took 108.05979585647583s
Interoperability | New vocabularies check for Bio2RDF::Irefindex took 469.23247480392456s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Irefindex took 0.8367812633514404s
Accuracy | Check Functional Property for Bio2RDF::Irefindex took 0.2627537250518799s
Accuracy | Check Inverse Functional Property for Bio2RDF::Irefindex took 0.2552182674407959s
Accuracy | Check Empty annotation labels for Bio2RDF::Irefindex took 6.795322418212891s
Accuracy | Check White space in annotation for Bio2RDF::Irefindex took 0.8818435668945312s
Accuracy | Check Datatype consistency for Bio2RDF::Irefindex took 0.6363704204559326s
Consistency | Disjoint class check for Bio2RDF::Irefindex took 0.39116334915161133s
Consistency | Check Misplaced properties for Bio2RDF::Irefindex took 64.78855586051941s
Consistency | Misplaced classes for Bio2RDF::Irefindex took 2.3142213821411133s
Consistency | Check Ontology hijacking for Bio2RDF::Irefindex took 6.064777612686157s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Irefindex took 1.2882909774780273s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Irefindex took 61.50414204597473s
Conciseness | Check Extensional conciseness for Bio2RDF::Irefindex took 0.6922223567962646s
Conciseness | Check Intensional conciseness for Bio2RDF::Irefindex took 0.3923499584197998s
Security | Sign check for Bio2RDF::Irefindex took 0.24909710884094238s
Availability | Check URIs Dereferenciability for Bio2RDF::Irefindex took 12.482375144958496s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 0.48942995071411133s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.02055191993713379s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0006890296936035156s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 8.344650268554688e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Irefindex took 899.8568732738495s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-irefindex took 2370.9326462745667s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 0.13631844520568848s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.0006451606750488281s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 0.2703425884246826s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.02016305923461914s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 3.314018249511719e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 1.0967254638671875e-05s
INFO | --- Analysis for bio2rdf-linkedspl took 9.237789154052734s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 0.5661423206329346s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.00036787986755371094s
Extra | Recovery of all triples for Bio2RDF::Lsr took 18.7677264213562s
Performance | Total latancy measurement for Bio2RDF::Lsr took 1.1468675136566162s
Amount of data | Number of triples check for Bio2RDF::Lsr took 43.54353094100952s
Interoperability | New terms check for Bio2RDF::Lsr took 41.2388916015625s
Versatility | Languages check for Bio2RDF::Lsr took 60.23011755943298s
Interpretability | Number of blank nodes check for Bio2RDF::Lsr took 0.24944758415222168s
Security | Check HTTPS for Bio2RDF::Lsr took 0.14571428298950195s
Interpretability | RDF structures check for Bio2RDF::Lsr took 0.7884604930877686s
Versatility | Serialization formats check for Bio2RDF::Lsr took 0.2938191890716553s
Availability | RDF dump link check for Bio2RDF::Lsr took 1.9595582485198975s
License | MR license check for Bio2RDF::Lsr took 0.46923232078552246s
License | HR license check for Bio2RDF::Lsr took 60.22835659980774s
Amount of data | Number of property check for Bio2RDF::Lsr took 0.23416900634765625s
Understandability | Number of label check for Bio2RDF::Lsr took 10.226069450378418s
Understandability | URI regex check for Bio2RDF::Lsr took 0.5378420352935791s
Understandability | Vocabs check for Bio2RDF::Lsr took 0.2411496639251709s
Verifiability | Authors check for Bio2RDF::Lsr took 0.2373828887939453s
Verifiability | Publishers check for Bio2RDF::Lsr took 0.23534178733825684s
Performance | Throughput check for Bio2RDF::Lsr took 11.562848329544067s
Amount of data | Check the number of entities for Bio2RDF::Lsr took 75.24419641494751s
Verifiability | Contribs. check for Bio2RDF::Lsr took 0.7546381950378418s
Interlinking | sameAs chians check for Bio2RDF::Lsr took 0.3611621856689453s
Interlinking | skos check for Bio2RDF::Lsr took 1.1685068607330322s
Interlinking | skos check for Bio2RDF::Lsr took 0.3261287212371826s
Timeliness | dataset update frequency check for Bio2RDF::Lsr took 0.23633599281311035s
Currency | Creation date check for Bio2RDF::Lsr took 0.4730057716369629s
Currency | Modification date check for Bio2RDF::Lsr took 0.4677431583404541s
Rep.Conc. | URIs length for Bio2RDF::Lsr took 107.01406645774841s
Interoperability | New vocabularies check for Bio2RDF::Lsr took 902.007580280304s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Lsr took 1.6487455368041992s
Accuracy | Check Functional Property for Bio2RDF::Lsr took 0.25997304916381836s
Accuracy | Check Inverse Functional Property for Bio2RDF::Lsr took 0.2586188316345215s
Accuracy | Check Empty annotation labels for Bio2RDF::Lsr took 7.308624505996704s
Accuracy | Check White space in annotation for Bio2RDF::Lsr took 0.8767855167388916s
Accuracy | Check Datatype consistency for Bio2RDF::Lsr took 0.638714075088501s
Consistency | Disjoint class check for Bio2RDF::Lsr took 0.43058109283447266s
Consistency | Check Misplaced properties for Bio2RDF::Lsr took 64.85690236091614s
Consistency | Misplaced classes for Bio2RDF::Lsr took 2.3516509532928467s
Consistency | Check Ontology hijacking for Bio2RDF::Lsr took 6.060096979141235s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Lsr took 1.317643165588379s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Lsr took 61.49750590324402s
Conciseness | Check Extensional conciseness for Bio2RDF::Lsr took 0.6993019580841064s
Conciseness | Check Intensional conciseness for Bio2RDF::Lsr took 0.40322160720825195s
Security | Sign check for Bio2RDF::Lsr took 0.24984312057495117s
Availability | Check URIs Dereferenciability for Bio2RDF::Lsr took 12.932458400726318s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 0.8042566776275635s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.02193760871887207s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0009403228759765625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 5.173683166503906e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Lsr took 74.16228294372559s
Believability | Calculation of trust value for Bio2RDF::Lsr took 1.4066696166992188e-05s
INFO | --- Analysis for bio2rdf-lsr took 1977.4054379463196s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 0.5629894733428955s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.00061798095703125s
Extra | Recovery of all triples for Bio2RDF::Mesh took 17.68204641342163s
Performance | Total latancy measurement for Bio2RDF::Mesh took 1.1369304656982422s
Amount of data | Number of triples check for Bio2RDF::Mesh took 43.8138382434845s
Interoperability | New terms check for Bio2RDF::Mesh took 40.38546633720398s
Versatility | Languages check for Bio2RDF::Mesh took 60.22949147224426s
Interpretability | Number of blank nodes check for Bio2RDF::Mesh took 0.25172972679138184s
Security | Check HTTPS for Bio2RDF::Mesh took 0.1434159278869629s
Interpretability | RDF structures check for Bio2RDF::Mesh took 0.5420048236846924s
Versatility | Serialization formats check for Bio2RDF::Mesh took 0.2925422191619873s
Availability | RDF dump link check for Bio2RDF::Mesh took 1.91493821144104s
License | MR license check for Bio2RDF::Mesh took 0.4902772903442383s
License | HR license check for Bio2RDF::Mesh took 60.2316837310791s
Amount of data | Number of property check for Bio2RDF::Mesh took 0.24142718315124512s
Understandability | Number of label check for Bio2RDF::Mesh took 9.465476036071777s
Understandability | URI regex check for Bio2RDF::Mesh took 0.5447618961334229s
Understandability | Vocabs check for Bio2RDF::Mesh took 0.237196683883667s
Verifiability | Authors check for Bio2RDF::Mesh took 0.2337172031402588s
Verifiability | Publishers check for Bio2RDF::Mesh took 0.2359628677368164s
Performance | Throughput check for Bio2RDF::Mesh took 11.61249566078186s
Amount of data | Check the number of entities for Bio2RDF::Mesh took 70.68353986740112s
Verifiability | Contribs. check for Bio2RDF::Mesh took 0.6586849689483643s
Interlinking | sameAs chians check for Bio2RDF::Mesh took 0.3424687385559082s
Interlinking | skos check for Bio2RDF::Mesh took 0.8234505653381348s
Interlinking | skos check for Bio2RDF::Mesh took 0.4077870845794678s
Timeliness | dataset update frequency check for Bio2RDF::Mesh took 0.23586082458496094s
Currency | Creation date check for Bio2RDF::Mesh took 0.46726560592651367s
Currency | Modification date check for Bio2RDF::Mesh took 0.465679407119751s
Rep.Conc. | URIs length for Bio2RDF::Mesh took 108.72765064239502s
Interoperability | New vocabularies check for Bio2RDF::Mesh took 61.60860300064087s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mesh took 0.39389991760253906s
Accuracy | Check Functional Property for Bio2RDF::Mesh took 0.2638051509857178s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mesh took 0.26151299476623535s
Accuracy | Check Empty annotation labels for Bio2RDF::Mesh took 7.329965353012085s
Accuracy | Check White space in annotation for Bio2RDF::Mesh took 0.8844645023345947s
Accuracy | Check Datatype consistency for Bio2RDF::Mesh took 0.6481482982635498s
Consistency | Disjoint class check for Bio2RDF::Mesh took 0.43121790885925293s
Consistency | Check Misplaced properties for Bio2RDF::Mesh took 65.02344155311584s
Consistency | Misplaced classes for Bio2RDF::Mesh took 2.3177528381347656s
Consistency | Check Ontology hijacking for Bio2RDF::Mesh took 5.809508323669434s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mesh took 1.2600562572479248s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mesh took 61.51615619659424s
Conciseness | Check Extensional conciseness for Bio2RDF::Mesh took 0.6928369998931885s
Conciseness | Check Intensional conciseness for Bio2RDF::Mesh took 0.6678798198699951s
Security | Sign check for Bio2RDF::Mesh took 0.2585427761077881s
Availability | Check URIs Dereferenciability for Bio2RDF::Mesh took 13.32838487625122s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 0.31844091415405273s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.02071976661682129s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 7.128715515136719e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mesh took 74.23150134086609s
Believability | Calculation of trust value for Bio2RDF::Mesh took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-mesh took 1189.0056250095367s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 0.5662131309509277s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.0005385875701904297s
Extra | Recovery of all triples for Bio2RDF::Mgi took 18.17296075820923s
Performance | Total latancy measurement for Bio2RDF::Mgi took 1.1587693691253662s
Amount of data | Number of triples check for Bio2RDF::Mgi took 43.19934296607971s
Interoperability | New terms check for Bio2RDF::Mgi took 40.37013864517212s
Versatility | Languages check for Bio2RDF::Mgi took 60.22538709640503s
Interpretability | Number of blank nodes check for Bio2RDF::Mgi took 0.24608421325683594s
Security | Check HTTPS for Bio2RDF::Mgi took 0.14387798309326172s
Interpretability | RDF structures check for Bio2RDF::Mgi took 0.8297224044799805s
Versatility | Serialization formats check for Bio2RDF::Mgi took 0.2895948886871338s
Availability | RDF dump link check for Bio2RDF::Mgi took 2.008274555206299s
License | MR license check for Bio2RDF::Mgi took 0.6267983913421631s
License | HR license check for Bio2RDF::Mgi took 60.23105764389038s
Amount of data | Number of property check for Bio2RDF::Mgi took 0.23606348037719727s
Understandability | Number of label check for Bio2RDF::Mgi took 9.778311729431152s
Understandability | URI regex check for Bio2RDF::Mgi took 0.5386483669281006s
Understandability | Vocabs check for Bio2RDF::Mgi took 0.23742270469665527s
Verifiability | Authors check for Bio2RDF::Mgi took 0.23639416694641113s
Verifiability | Publishers check for Bio2RDF::Mgi took 0.23674869537353516s
Performance | Throughput check for Bio2RDF::Mgi took 11.559567213058472s
Amount of data | Check the number of entities for Bio2RDF::Mgi took 75.10489010810852s
Verifiability | Contribs. check for Bio2RDF::Mgi took 0.6901237964630127s
Interlinking | sameAs chians check for Bio2RDF::Mgi took 0.33855700492858887s
Interlinking | skos check for Bio2RDF::Mgi took 1.0430502891540527s
Interlinking | skos check for Bio2RDF::Mgi took 0.3295900821685791s
Timeliness | dataset update frequency check for Bio2RDF::Mgi took 0.2395153045654297s
Currency | Creation date check for Bio2RDF::Mgi took 0.47029900550842285s
Currency | Modification date check for Bio2RDF::Mgi took 0.46842026710510254s
Rep.Conc. | URIs length for Bio2RDF::Mgi took 108.43191409111023s
Interoperability | New vocabularies check for Bio2RDF::Mgi took 997.3589289188385s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mgi took 0.8444077968597412s
Accuracy | Check Functional Property for Bio2RDF::Mgi took 0.26219987869262695s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mgi took 0.26120543479919434s
Accuracy | Check Empty annotation labels for Bio2RDF::Mgi took 7.486583948135376s
Accuracy | Check White space in annotation for Bio2RDF::Mgi took 0.8763077259063721s
Accuracy | Check Datatype consistency for Bio2RDF::Mgi took 0.6377217769622803s
Consistency | Disjoint class check for Bio2RDF::Mgi took 0.4100029468536377s
Consistency | Check Misplaced properties for Bio2RDF::Mgi took 65.10573959350586s
Consistency | Misplaced classes for Bio2RDF::Mgi took 2.322735548019409s
Consistency | Check Ontology hijacking for Bio2RDF::Mgi took 5.994102478027344s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mgi took 1.297145128250122s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mgi took 61.48082685470581s
Conciseness | Check Extensional conciseness for Bio2RDF::Mgi took 0.7116663455963135s
Conciseness | Check Intensional conciseness for Bio2RDF::Mgi took 0.3903496265411377s
Security | Sign check for Bio2RDF::Mgi took 0.24315786361694336s
Availability | Check URIs Dereferenciability for Bio2RDF::Mgi took 14.935396432876587s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 0.47464680671691895s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.02040410041809082s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 8.702278137207031e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mgi took 907.813187122345s
Believability | Calculation of trust value for Bio2RDF::Mgi took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-mgi took 2906.8255553245544s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 0.5622985363006592s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.0003769397735595703s
Extra | Recovery of all triples for Bio2RDF::Ncbigene took 19.31124258041382s
Performance | Total latancy measurement for Bio2RDF::Ncbigene took 1.1409239768981934s
Amount of data | Number of triples check for Bio2RDF::Ncbigene took 43.57670044898987s
Interoperability | New terms check for Bio2RDF::Ncbigene took 40.63785791397095s
Versatility | Languages check for Bio2RDF::Ncbigene took 60.25243377685547s
Interpretability | Number of blank nodes check for Bio2RDF::Ncbigene took 0.2466723918914795s
Security | Check HTTPS for Bio2RDF::Ncbigene took 0.14515471458435059s
Interpretability | RDF structures check for Bio2RDF::Ncbigene took 0.34055566787719727s
Versatility | Serialization formats check for Bio2RDF::Ncbigene took 0.29245829582214355s
Availability | RDF dump link check for Bio2RDF::Ncbigene took 1.9824528694152832s
License | MR license check for Bio2RDF::Ncbigene took 0.4735839366912842s
License | HR license check for Bio2RDF::Ncbigene took 60.229976654052734s
Amount of data | Number of property check for Bio2RDF::Ncbigene took 0.2373065948486328s
Understandability | Number of label check for Bio2RDF::Ncbigene took 9.737285614013672s
Understandability | URI regex check for Bio2RDF::Ncbigene took 0.5398228168487549s
Understandability | Vocabs check for Bio2RDF::Ncbigene took 0.24341440200805664s
Verifiability | Authors check for Bio2RDF::Ncbigene took 0.23611116409301758s
Verifiability | Publishers check for Bio2RDF::Ncbigene took 0.23767757415771484s
Performance | Throughput check for Bio2RDF::Ncbigene took 11.558603763580322s
Amount of data | Check the number of entities for Bio2RDF::Ncbigene took 73.65691661834717s
Verifiability | Contribs. check for Bio2RDF::Ncbigene took 0.6643354892730713s
Interlinking | sameAs chians check for Bio2RDF::Ncbigene took 0.35395121574401855s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.8816137313842773s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.3666107654571533s
Timeliness | dataset update frequency check for Bio2RDF::Ncbigene took 0.23704290390014648s
Currency | Creation date check for Bio2RDF::Ncbigene took 0.4676845073699951s
Currency | Modification date check for Bio2RDF::Ncbigene took 0.46742701530456543s
Rep.Conc. | URIs length for Bio2RDF::Ncbigene took 107.05453085899353s
Interoperability | New vocabularies check for Bio2RDF::Ncbigene took 46.78826332092285s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ncbigene took 0.3908727169036865s
Accuracy | Check Functional Property for Bio2RDF::Ncbigene took 0.2536654472351074s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ncbigene took 0.25820112228393555s
Accuracy | Check Empty annotation labels for Bio2RDF::Ncbigene took 7.253573179244995s
Accuracy | Check White space in annotation for Bio2RDF::Ncbigene took 0.8827319145202637s
Accuracy | Check Datatype consistency for Bio2RDF::Ncbigene took 0.6348004341125488s
Consistency | Disjoint class check for Bio2RDF::Ncbigene took 0.3795328140258789s
Consistency | Check Misplaced properties for Bio2RDF::Ncbigene took 64.99126505851746s
Consistency | Misplaced classes for Bio2RDF::Ncbigene took 2.3046512603759766s
Consistency | Check Ontology hijacking for Bio2RDF::Ncbigene took 6.1170854568481445s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ncbigene took 1.317789077758789s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ncbigene took 61.48345923423767s
Conciseness | Check Extensional conciseness for Bio2RDF::Ncbigene took 0.6983227729797363s
Conciseness | Check Intensional conciseness for Bio2RDF::Ncbigene took 0.8119871616363525s
Security | Sign check for Bio2RDF::Ncbigene took 0.2478322982788086s
Availability | Check URIs Dereferenciability for Bio2RDF::Ncbigene took 21.31782054901123s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 0.5031373500823975s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.020383834838867188s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.00011563301086425781s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ncbigene took 508.80470299720764s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 2.0265579223632812e-05s
INFO | --- Analysis for bio2rdf-ncbigene took 1565.8418295383453s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 0.5643646717071533s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.0005817413330078125s
Extra | Recovery of all triples for Bio2RDF::Ndc took 18.519304037094116s
Performance | Total latancy measurement for Bio2RDF::Ndc took 1.1395583152770996s
Amount of data | Number of triples check for Bio2RDF::Ndc took 43.99619388580322s
Interoperability | New terms check for Bio2RDF::Ndc took 40.802085399627686s
Versatility | Languages check for Bio2RDF::Ndc took 60.229137897491455s
Interpretability | Number of blank nodes check for Bio2RDF::Ndc took 0.24755573272705078s
Security | Check HTTPS for Bio2RDF::Ndc took 0.1446394920349121s
Interpretability | RDF structures check for Bio2RDF::Ndc took 0.7423043251037598s
Versatility | Serialization formats check for Bio2RDF::Ndc took 0.2923469543457031s
Availability | RDF dump link check for Bio2RDF::Ndc took 2.42885160446167s
License | MR license check for Bio2RDF::Ndc took 0.4705479145050049s
License | HR license check for Bio2RDF::Ndc took 60.22969841957092s
Amount of data | Number of property check for Bio2RDF::Ndc took 0.23713421821594238s
Understandability | Number of label check for Bio2RDF::Ndc took 9.870722770690918s
Understandability | URI regex check for Bio2RDF::Ndc took 0.5358920097351074s
Understandability | Vocabs check for Bio2RDF::Ndc took 0.2328932285308838s
Verifiability | Authors check for Bio2RDF::Ndc took 0.23577117919921875s
Verifiability | Publishers check for Bio2RDF::Ndc took 0.23540902137756348s
Performance | Throughput check for Bio2RDF::Ndc took 11.530555248260498s
Amount of data | Check the number of entities for Bio2RDF::Ndc took 74.10246992111206s
Verifiability | Contribs. check for Bio2RDF::Ndc took 0.6878297328948975s
Interlinking | sameAs chians check for Bio2RDF::Ndc took 0.34043431282043457s
Interlinking | skos check for Bio2RDF::Ndc took 0.7705471515655518s
Interlinking | skos check for Bio2RDF::Ndc took 0.3332855701446533s
Timeliness | dataset update frequency check for Bio2RDF::Ndc took 0.23624134063720703s
Currency | Creation date check for Bio2RDF::Ndc took 0.4697089195251465s
Currency | Modification date check for Bio2RDF::Ndc took 0.4686009883880615s
Rep.Conc. | URIs length for Bio2RDF::Ndc took 107.21591639518738s
Interoperability | New vocabularies check for Bio2RDF::Ndc took 482.212872505188s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ndc took 0.8149082660675049s
Accuracy | Check Functional Property for Bio2RDF::Ndc took 0.2501645088195801s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ndc took 0.23169541358947754s
Accuracy | Check Empty annotation labels for Bio2RDF::Ndc took 7.595204591751099s
Accuracy | Check White space in annotation for Bio2RDF::Ndc took 0.8868632316589355s
Accuracy | Check Datatype consistency for Bio2RDF::Ndc took 0.6588540077209473s
Consistency | Disjoint class check for Bio2RDF::Ndc took 0.42919349670410156s
Consistency | Check Misplaced properties for Bio2RDF::Ndc took 65.33482003211975s
Consistency | Misplaced classes for Bio2RDF::Ndc took 2.3525326251983643s
Consistency | Check Ontology hijacking for Bio2RDF::Ndc took 6.140241622924805s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ndc took 1.3036987781524658s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ndc took 61.49766254425049s
Conciseness | Check Extensional conciseness for Bio2RDF::Ndc took 0.7233133316040039s
Conciseness | Check Intensional conciseness for Bio2RDF::Ndc took 0.39577651023864746s
Security | Sign check for Bio2RDF::Ndc took 0.24735689163208008s
Availability | Check URIs Dereferenciability for Bio2RDF::Ndc took 20.52930521965027s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 0.49802708625793457s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.020413637161254883s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 5.650520324707031e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ndc took 940.146546125412s
Believability | Calculation of trust value for Bio2RDF::Ndc took 1.0013580322265625e-05s
INFO | --- Analysis for bio2rdf-ndc took 2428.123445749283s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 0.13087725639343262s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.0007109642028808594s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.29999661445617676s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.021637439727783203s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 3.123283386230469e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-nextprot took 3.4488043785095215s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 1.3624589443206787s
Availability | VoID file availability check for Bio2RDF::Omim took 0.0005819797515869141s
Extra | Recovery of all triples for Bio2RDF::Omim took 17.999289512634277s
Performance | Total latancy measurement for Bio2RDF::Omim took 1.134537935256958s
Amount of data | Number of triples check for Bio2RDF::Omim took 44.403138160705566s
Interoperability | New terms check for Bio2RDF::Omim took 40.64437508583069s
Versatility | Languages check for Bio2RDF::Omim took 60.22978186607361s
Interpretability | Number of blank nodes check for Bio2RDF::Omim took 0.24570560455322266s
Security | Check HTTPS for Bio2RDF::Omim took 0.14428210258483887s
Interpretability | RDF structures check for Bio2RDF::Omim took 0.7968802452087402s
Versatility | Serialization formats check for Bio2RDF::Omim took 0.29209184646606445s
Availability | RDF dump link check for Bio2RDF::Omim took 2.0031020641326904s
License | MR license check for Bio2RDF::Omim took 0.5200240612030029s
License | HR license check for Bio2RDF::Omim took 60.23188376426697s
Amount of data | Number of property check for Bio2RDF::Omim took 0.2395305633544922s
Understandability | Number of label check for Bio2RDF::Omim took 10.301393747329712s
Understandability | URI regex check for Bio2RDF::Omim took 0.540618896484375s
Understandability | Vocabs check for Bio2RDF::Omim took 0.23838496208190918s
Verifiability | Authors check for Bio2RDF::Omim took 0.2369978427886963s
Verifiability | Publishers check for Bio2RDF::Omim took 0.2355184555053711s
Performance | Throughput check for Bio2RDF::Omim took 11.539775609970093s
Amount of data | Check the number of entities for Bio2RDF::Omim took 73.62071228027344s
Verifiability | Contribs. check for Bio2RDF::Omim took 0.7004556655883789s
Interlinking | sameAs chians check for Bio2RDF::Omim took 0.3424341678619385s
Interlinking | skos check for Bio2RDF::Omim took 0.8849039077758789s
Interlinking | skos check for Bio2RDF::Omim took 0.3709144592285156s
Timeliness | dataset update frequency check for Bio2RDF::Omim took 0.23837494850158691s
Currency | Creation date check for Bio2RDF::Omim took 0.46776652336120605s
Currency | Modification date check for Bio2RDF::Omim took 0.47000980377197266s
Rep.Conc. | URIs length for Bio2RDF::Omim took 111.850834608078s
Interoperability | New vocabularies check for Bio2RDF::Omim took 31.421566247940063s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Omim took 0.3946399688720703s
Accuracy | Check Functional Property for Bio2RDF::Omim took 0.26183652877807617s
Accuracy | Check Inverse Functional Property for Bio2RDF::Omim took 0.26139259338378906s
Accuracy | Check Empty annotation labels for Bio2RDF::Omim took 6.473726749420166s
Accuracy | Check White space in annotation for Bio2RDF::Omim took 0.8802742958068848s
Accuracy | Check Datatype consistency for Bio2RDF::Omim took 0.6388843059539795s
Consistency | Disjoint class check for Bio2RDF::Omim took 0.41103291511535645s
Consistency | Check Misplaced properties for Bio2RDF::Omim took 65.27413606643677s
Consistency | Misplaced classes for Bio2RDF::Omim took 2.319852828979492s
Consistency | Check Ontology hijacking for Bio2RDF::Omim took 6.092941761016846s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Omim took 1.2761569023132324s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Omim took 61.49651765823364s
Conciseness | Check Extensional conciseness for Bio2RDF::Omim took 0.6968660354614258s
Conciseness | Check Intensional conciseness for Bio2RDF::Omim took 0.39269018173217773s
Security | Sign check for Bio2RDF::Omim took 0.24796414375305176s
Availability | Check URIs Dereferenciability for Bio2RDF::Omim took 13.02459192276001s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 0.4497854709625244s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.02096080780029297s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0006849765777587891s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.0001323223114013672s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Omim took 438.87237429618835s
Believability | Calculation of trust value for Bio2RDF::Omim took 1.049041748046875e-05s
INFO | --- Analysis for bio2rdf-omim took 1474.7591586112976s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 4.410743713378906e-05s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.0007436275482177734s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.2701754570007324s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.0205538272857666s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 4.220008850097656e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-omim-resources took 2.6591672897338867s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 0.5643899440765381s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.0005869865417480469s
Extra | Recovery of all triples for Bio2RDF::Orphanet took 18.40880298614502s
Performance | Total latancy measurement for Bio2RDF::Orphanet took 1.1399288177490234s
Amount of data | Number of triples check for Bio2RDF::Orphanet took 43.982771158218384s
Interoperability | New terms check for Bio2RDF::Orphanet took 41.75840473175049s
Versatility | Languages check for Bio2RDF::Orphanet took 60.227365493774414s
Interpretability | Number of blank nodes check for Bio2RDF::Orphanet took 0.2458477020263672s
Security | Check HTTPS for Bio2RDF::Orphanet took 0.14411330223083496s
Interpretability | RDF structures check for Bio2RDF::Orphanet took 0.45462703704833984s
Versatility | Serialization formats check for Bio2RDF::Orphanet took 0.2852146625518799s
Availability | RDF dump link check for Bio2RDF::Orphanet took 1.966529369354248s
License | MR license check for Bio2RDF::Orphanet took 0.5489919185638428s
License | HR license check for Bio2RDF::Orphanet took 60.23256158828735s
Amount of data | Number of property check for Bio2RDF::Orphanet took 0.23388981819152832s
Understandability | Number of label check for Bio2RDF::Orphanet took 10.315600633621216s
Understandability | URI regex check for Bio2RDF::Orphanet took 0.5385527610778809s
Understandability | Vocabs check for Bio2RDF::Orphanet took 0.23191094398498535s
Verifiability | Authors check for Bio2RDF::Orphanet took 0.2370445728302002s
Verifiability | Publishers check for Bio2RDF::Orphanet took 0.23771190643310547s
Performance | Throughput check for Bio2RDF::Orphanet took 11.534878492355347s
Amount of data | Check the number of entities for Bio2RDF::Orphanet took 73.53843903541565s
Verifiability | Contribs. check for Bio2RDF::Orphanet took 0.6821575164794922s
Interlinking | sameAs chians check for Bio2RDF::Orphanet took 0.3503427505493164s
Interlinking | skos check for Bio2RDF::Orphanet took 0.7130224704742432s
Interlinking | skos check for Bio2RDF::Orphanet took 0.3738057613372803s
Timeliness | dataset update frequency check for Bio2RDF::Orphanet took 0.2434699535369873s
Currency | Creation date check for Bio2RDF::Orphanet took 0.48460936546325684s
Currency | Modification date check for Bio2RDF::Orphanet took 0.46622729301452637s
Rep.Conc. | URIs length for Bio2RDF::Orphanet took 110.12562680244446s
Interoperability | New vocabularies check for Bio2RDF::Orphanet took 190.3112232685089s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Orphanet took 0.6876547336578369s
Accuracy | Check Functional Property for Bio2RDF::Orphanet took 0.26102781295776367s
Accuracy | Check Inverse Functional Property for Bio2RDF::Orphanet took 0.25917959213256836s
Accuracy | Check Empty annotation labels for Bio2RDF::Orphanet took 7.490270137786865s
Accuracy | Check White space in annotation for Bio2RDF::Orphanet took 0.8765075206756592s
Accuracy | Check Datatype consistency for Bio2RDF::Orphanet took 0.6546299457550049s
Consistency | Disjoint class check for Bio2RDF::Orphanet took 0.5177953243255615s
Consistency | Check Misplaced properties for Bio2RDF::Orphanet took 64.9403862953186s
Consistency | Misplaced classes for Bio2RDF::Orphanet took 2.374112129211426s
Consistency | Check Ontology hijacking for Bio2RDF::Orphanet took 6.211406946182251s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Orphanet took 1.3205523490905762s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Orphanet took 61.512226819992065s
Conciseness | Check Extensional conciseness for Bio2RDF::Orphanet took 0.6955711841583252s
Conciseness | Check Intensional conciseness for Bio2RDF::Orphanet took 0.39801526069641113s
Security | Sign check for Bio2RDF::Orphanet took 0.24968695640563965s
Availability | Check URIs Dereferenciability for Bio2RDF::Orphanet took 13.861671686172485s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 0.3947336673736572s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.020743370056152344s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0008902549743652344s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 9.274482727050781e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Orphanet took 43.764803886413574s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 2.9325485229492188e-05s
INFO | --- Analysis for bio2rdf-orphanet took 1238.7700335979462s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 0.1334073543548584s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.0006320476531982422s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 0.2679922580718994s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.020734786987304688s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0006899833679199219s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 5.054473876953125e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 1.0251998901367188e-05s
INFO | --- Analysis for bio2rdf-pathwaycommons took 8.532085418701172s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 0.5662970542907715s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.0005931854248046875s
Extra | Recovery of all triples for Bio2RDF::Pharmgkb took 19.06722593307495s
Performance | Total latancy measurement for Bio2RDF::Pharmgkb took 1.1547863483428955s
Amount of data | Number of triples check for Bio2RDF::Pharmgkb took 43.485787868499756s
Interoperability | New terms check for Bio2RDF::Pharmgkb took 40.42085933685303s
Versatility | Languages check for Bio2RDF::Pharmgkb took 60.253891706466675s
Interpretability | Number of blank nodes check for Bio2RDF::Pharmgkb took 0.24906134605407715s
Security | Check HTTPS for Bio2RDF::Pharmgkb took 0.1451435089111328s
Interpretability | RDF structures check for Bio2RDF::Pharmgkb took 0.6762251853942871s
Versatility | Serialization formats check for Bio2RDF::Pharmgkb took 0.28727245330810547s
Availability | RDF dump link check for Bio2RDF::Pharmgkb took 2.0045971870422363s
License | MR license check for Bio2RDF::Pharmgkb took 0.47908878326416016s
License | HR license check for Bio2RDF::Pharmgkb took 60.229095220565796s
Amount of data | Number of property check for Bio2RDF::Pharmgkb took 0.23862457275390625s
Understandability | Number of label check for Bio2RDF::Pharmgkb took 9.797609806060791s
Understandability | URI regex check for Bio2RDF::Pharmgkb took 0.5384228229522705s
Understandability | Vocabs check for Bio2RDF::Pharmgkb took 0.24590253829956055s
Verifiability | Authors check for Bio2RDF::Pharmgkb took 0.2413787841796875s
Verifiability | Publishers check for Bio2RDF::Pharmgkb took 0.23583412170410156s
Performance | Throughput check for Bio2RDF::Pharmgkb took 11.56091833114624s
Amount of data | Check the number of entities for Bio2RDF::Pharmgkb took 76.47556781768799s
Verifiability | Contribs. check for Bio2RDF::Pharmgkb took 0.6667170524597168s
Interlinking | sameAs chians check for Bio2RDF::Pharmgkb took 0.3673555850982666s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.8792898654937744s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.33315110206604004s
Timeliness | dataset update frequency check for Bio2RDF::Pharmgkb took 0.24028301239013672s
Currency | Creation date check for Bio2RDF::Pharmgkb took 0.46359777450561523s
Currency | Modification date check for Bio2RDF::Pharmgkb took 0.46280670166015625s
Rep.Conc. | URIs length for Bio2RDF::Pharmgkb took 106.47633790969849s
Interoperability | New vocabularies check for Bio2RDF::Pharmgkb took 509.3125042915344s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pharmgkb took 1.6397888660430908s
Accuracy | Check Functional Property for Bio2RDF::Pharmgkb took 0.26179933547973633s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pharmgkb took 0.26003599166870117s
Accuracy | Check Empty annotation labels for Bio2RDF::Pharmgkb took 7.253375291824341s
Accuracy | Check White space in annotation for Bio2RDF::Pharmgkb took 0.8793468475341797s
Accuracy | Check Datatype consistency for Bio2RDF::Pharmgkb took 0.6524167060852051s
Consistency | Disjoint class check for Bio2RDF::Pharmgkb took 0.4139232635498047s
Consistency | Check Misplaced properties for Bio2RDF::Pharmgkb took 65.33415246009827s
Consistency | Misplaced classes for Bio2RDF::Pharmgkb took 2.3472323417663574s
Consistency | Check Ontology hijacking for Bio2RDF::Pharmgkb took 5.930120229721069s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pharmgkb took 1.2778840065002441s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pharmgkb took 61.547794818878174s
Conciseness | Check Extensional conciseness for Bio2RDF::Pharmgkb took 0.7118775844573975s
Conciseness | Check Intensional conciseness for Bio2RDF::Pharmgkb took 0.39408111572265625s
Security | Sign check for Bio2RDF::Pharmgkb took 0.24427342414855957s
Availability | Check URIs Dereferenciability for Bio2RDF::Pharmgkb took 12.841946840286255s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 0.566401481628418s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.020854711532592773s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 7.414817810058594e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pharmgkb took 488.44871258735657s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-pharmgkb took 2000.6286730766296s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 0.5619170665740967s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.0005681514739990234s
Extra | Recovery of all triples for Bio2RDF::Pubmed took 18.199501991271973s
Performance | Total latancy measurement for Bio2RDF::Pubmed took 1.1464409828186035s
Amount of data | Number of triples check for Bio2RDF::Pubmed took 43.897778034210205s
Interoperability | New terms check for Bio2RDF::Pubmed took 41.46797037124634s
Versatility | Languages check for Bio2RDF::Pubmed took 60.2297477722168s
Interpretability | Number of blank nodes check for Bio2RDF::Pubmed took 0.2479870319366455s
Security | Check HTTPS for Bio2RDF::Pubmed took 0.14519977569580078s
Interpretability | RDF structures check for Bio2RDF::Pubmed took 0.8948943614959717s
Versatility | Serialization formats check for Bio2RDF::Pubmed took 0.28830695152282715s
Availability | RDF dump link check for Bio2RDF::Pubmed took 1.9733014106750488s
License | MR license check for Bio2RDF::Pubmed took 0.47412562370300293s
License | HR license check for Bio2RDF::Pubmed took 60.240482330322266s
Amount of data | Number of property check for Bio2RDF::Pubmed took 0.23509478569030762s
Understandability | Number of label check for Bio2RDF::Pubmed took 9.313836336135864s
Understandability | URI regex check for Bio2RDF::Pubmed took 0.5666427612304688s
Understandability | Vocabs check for Bio2RDF::Pubmed took 0.23564481735229492s
Verifiability | Authors check for Bio2RDF::Pubmed took 0.23848795890808105s
Verifiability | Publishers check for Bio2RDF::Pubmed took 0.24400687217712402s
Performance | Throughput check for Bio2RDF::Pubmed took 11.59115219116211s
Amount of data | Check the number of entities for Bio2RDF::Pubmed took 72.47094464302063s
Verifiability | Contribs. check for Bio2RDF::Pubmed took 0.6562533378601074s
Interlinking | sameAs chians check for Bio2RDF::Pubmed took 0.3264906406402588s
Interlinking | skos check for Bio2RDF::Pubmed took 0.6985447406768799s
Interlinking | skos check for Bio2RDF::Pubmed took 0.32829928398132324s
Timeliness | dataset update frequency check for Bio2RDF::Pubmed took 0.2341785430908203s
Currency | Creation date check for Bio2RDF::Pubmed took 0.4678483009338379s
Currency | Modification date check for Bio2RDF::Pubmed took 0.4721369743347168s
Rep.Conc. | URIs length for Bio2RDF::Pubmed took 109.79029750823975s
Interoperability | New vocabularies check for Bio2RDF::Pubmed took 468.0414595603943s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pubmed took 0.8596179485321045s
Accuracy | Check Functional Property for Bio2RDF::Pubmed took 0.2617068290710449s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pubmed took 0.26135754585266113s
Accuracy | Check Empty annotation labels for Bio2RDF::Pubmed took 6.968908309936523s
Accuracy | Check White space in annotation for Bio2RDF::Pubmed took 0.8897578716278076s
Accuracy | Check Datatype consistency for Bio2RDF::Pubmed took 0.6464700698852539s
Consistency | Disjoint class check for Bio2RDF::Pubmed took 0.43439483642578125s
Consistency | Check Misplaced properties for Bio2RDF::Pubmed took 65.4915509223938s
Consistency | Misplaced classes for Bio2RDF::Pubmed took 2.349879026412964s
Consistency | Check Ontology hijacking for Bio2RDF::Pubmed took 6.402342081069946s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pubmed took 1.2994589805603027s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pubmed took 61.520920753479004s
Conciseness | Check Extensional conciseness for Bio2RDF::Pubmed took 0.698326587677002s
Conciseness | Check Intensional conciseness for Bio2RDF::Pubmed took 0.3952360153198242s
Security | Sign check for Bio2RDF::Pubmed took 0.24911832809448242s
Availability | Check URIs Dereferenciability for Bio2RDF::Pubmed took 13.482825517654419s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 0.38373494148254395s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.020371198654174805s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.0001418590545654297s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pubmed took 57.60454082489014s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 1.5974044799804688e-05s
INFO | --- Analysis for bio2rdf-pubmed took 1527.3014283180237s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 0.13596153259277344s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0006160736083984375s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 0.26332855224609375s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.021806001663208008s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 7.915496826171875e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-sabiork took 8.390278339385986s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 0.5655009746551514s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.0005443096160888672s
Extra | Recovery of all triples for Bio2RDF::Sgd took 18.649045705795288s
Performance | Total latancy measurement for Bio2RDF::Sgd took 1.1682305335998535s
Amount of data | Number of triples check for Bio2RDF::Sgd took 43.51934814453125s
Interoperability | New terms check for Bio2RDF::Sgd took 40.79408931732178s
Versatility | Languages check for Bio2RDF::Sgd took 60.2282509803772s
Interpretability | Number of blank nodes check for Bio2RDF::Sgd took 0.24686837196350098s
Security | Check HTTPS for Bio2RDF::Sgd took 0.14411354064941406s
Interpretability | RDF structures check for Bio2RDF::Sgd took 0.4214651584625244s
Versatility | Serialization formats check for Bio2RDF::Sgd took 0.2898068428039551s
Availability | RDF dump link check for Bio2RDF::Sgd took 2.0174238681793213s
License | MR license check for Bio2RDF::Sgd took 0.4560220241546631s
License | HR license check for Bio2RDF::Sgd took 60.228517055511475s
Amount of data | Number of property check for Bio2RDF::Sgd took 0.2337651252746582s
Understandability | Number of label check for Bio2RDF::Sgd took 9.906316041946411s
Understandability | URI regex check for Bio2RDF::Sgd took 0.5481431484222412s
Understandability | Vocabs check for Bio2RDF::Sgd took 0.23590636253356934s
Verifiability | Authors check for Bio2RDF::Sgd took 0.23605775833129883s
Verifiability | Publishers check for Bio2RDF::Sgd took 0.2362842559814453s
Performance | Throughput check for Bio2RDF::Sgd took 11.572980403900146s
Amount of data | Check the number of entities for Bio2RDF::Sgd took 76.05473136901855s
Verifiability | Contribs. check for Bio2RDF::Sgd took 0.6794161796569824s
Interlinking | sameAs chians check for Bio2RDF::Sgd took 0.3402414321899414s
Interlinking | skos check for Bio2RDF::Sgd took 0.7388629913330078s
Interlinking | skos check for Bio2RDF::Sgd took 0.327756404876709s
Timeliness | dataset update frequency check for Bio2RDF::Sgd took 0.2434394359588623s
Currency | Creation date check for Bio2RDF::Sgd took 0.46652817726135254s
Currency | Modification date check for Bio2RDF::Sgd took 0.46553850173950195s
Rep.Conc. | URIs length for Bio2RDF::Sgd took 107.75516200065613s
Interoperability | New vocabularies check for Bio2RDF::Sgd took 48.88445067405701s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sgd took 0.39273810386657715s
Accuracy | Check Functional Property for Bio2RDF::Sgd took 0.25531625747680664s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sgd took 0.2559795379638672s
Accuracy | Check Empty annotation labels for Bio2RDF::Sgd took 6.4835662841796875s
Accuracy | Check White space in annotation for Bio2RDF::Sgd took 0.8797240257263184s
Accuracy | Check Datatype consistency for Bio2RDF::Sgd took 0.6447055339813232s
Consistency | Disjoint class check for Bio2RDF::Sgd took 0.4131503105163574s
Consistency | Check Misplaced properties for Bio2RDF::Sgd took 64.6585681438446s
Consistency | Misplaced classes for Bio2RDF::Sgd took 2.316113233566284s
Consistency | Check Ontology hijacking for Bio2RDF::Sgd took 5.796199321746826s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sgd took 1.2799043655395508s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sgd took 61.52435851097107s
Conciseness | Check Extensional conciseness for Bio2RDF::Sgd took 0.6993958950042725s
Conciseness | Check Intensional conciseness for Bio2RDF::Sgd took 0.7126271724700928s
Security | Sign check for Bio2RDF::Sgd took 0.2441701889038086s
Availability | Check URIs Dereferenciability for Bio2RDF::Sgd took 12.641793966293335s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 0.49412107467651367s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.020902395248413086s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00010967254638671875s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sgd took 49.042486906051636s
Believability | Calculation of trust value for Bio2RDF::Sgd took 1.0251998901367188e-05s
INFO | --- Analysis for bio2rdf-sgd took 1096.0565378665924s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 4.3392181396484375e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.0005576610565185547s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 0.2847864627838135s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.020342588424682617s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 3.719329833984375e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 1.0967254638671875e-05s
INFO | --- Analysis for bio2rdf-sgd-resources took 2.722635507583618s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 0.5652096271514893s
Availability | VoID file availability check for Bio2RDF::Sider took 0.0006113052368164062s
Extra | Recovery of all triples for Bio2RDF::Sider took 18.172247648239136s
Performance | Total latancy measurement for Bio2RDF::Sider took 1.144162893295288s
Amount of data | Number of triples check for Bio2RDF::Sider took 43.695292949676514s
Interoperability | New terms check for Bio2RDF::Sider took 41.01463007926941s
Versatility | Languages check for Bio2RDF::Sider took 60.2291738986969s
Interpretability | Number of blank nodes check for Bio2RDF::Sider took 0.2456049919128418s
Security | Check HTTPS for Bio2RDF::Sider took 0.14481115341186523s
Interpretability | RDF structures check for Bio2RDF::Sider took 0.7868912220001221s
Versatility | Serialization formats check for Bio2RDF::Sider took 0.2939620018005371s
Availability | RDF dump link check for Bio2RDF::Sider took 2.02482271194458s
License | MR license check for Bio2RDF::Sider took 0.4709508419036865s
License | HR license check for Bio2RDF::Sider took 60.22971320152283s
Amount of data | Number of property check for Bio2RDF::Sider took 0.23492097854614258s
Understandability | Number of label check for Bio2RDF::Sider took 9.636711835861206s
Understandability | URI regex check for Bio2RDF::Sider took 0.565791130065918s
Understandability | Vocabs check for Bio2RDF::Sider took 0.23415493965148926s
Verifiability | Authors check for Bio2RDF::Sider took 0.23483800888061523s
Verifiability | Publishers check for Bio2RDF::Sider took 0.23493051528930664s
Performance | Throughput check for Bio2RDF::Sider took 11.569050312042236s
Amount of data | Check the number of entities for Bio2RDF::Sider took 72.48747277259827s
Verifiability | Contribs. check for Bio2RDF::Sider took 0.8069376945495605s
Interlinking | sameAs chians check for Bio2RDF::Sider took 0.246551513671875s
Interlinking | skos check for Bio2RDF::Sider took 0.8487236499786377s
Interlinking | skos check for Bio2RDF::Sider took 0.3242616653442383s
Timeliness | dataset update frequency check for Bio2RDF::Sider took 0.2340238094329834s
Currency | Creation date check for Bio2RDF::Sider took 0.46431779861450195s
Currency | Modification date check for Bio2RDF::Sider took 0.46427226066589355s
Rep.Conc. | URIs length for Bio2RDF::Sider took 107.9386613368988s
Interoperability | New vocabularies check for Bio2RDF::Sider took 475.03042364120483s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sider took 0.9511432647705078s
Accuracy | Check Functional Property for Bio2RDF::Sider took 0.25844740867614746s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sider took 0.2575571537017822s
Accuracy | Check Empty annotation labels for Bio2RDF::Sider took 6.870307683944702s
Accuracy | Check White space in annotation for Bio2RDF::Sider took 0.878594160079956s
Accuracy | Check Datatype consistency for Bio2RDF::Sider took 0.6399824619293213s
Consistency | Disjoint class check for Bio2RDF::Sider took 0.4060189723968506s
Consistency | Check Misplaced properties for Bio2RDF::Sider took 65.08741497993469s
Consistency | Misplaced classes for Bio2RDF::Sider took 2.385803699493408s
Consistency | Check Ontology hijacking for Bio2RDF::Sider took 5.903076410293579s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sider took 1.2768054008483887s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sider took 61.54343223571777s
Conciseness | Check Extensional conciseness for Bio2RDF::Sider took 0.7154569625854492s
Conciseness | Check Intensional conciseness for Bio2RDF::Sider took 0.3963179588317871s
Security | Sign check for Bio2RDF::Sider took 0.2464287281036377s
Availability | Check URIs Dereferenciability for Bio2RDF::Sider took 13.04353380203247s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 0.5854370594024658s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.02072739601135254s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 4.673004150390625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sider took 82.48820352554321s
Believability | Calculation of trust value for Bio2RDF::Sider took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-sider took 1563.828180551529s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 4.291534423828125e-05s
Availability | VoID file availability check for bio2rdf-taxon took 0.0005865097045898438s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 0.25726771354675293s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.02029585838317871s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 4.315376281738281e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-taxon took 2.5586636066436768s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 0.563169002532959s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.0006840229034423828s
Extra | Recovery of all triples for Bio2RDF::Taxonomy took 18.737515449523926s
Performance | Total latancy measurement for Bio2RDF::Taxonomy took 1.149383783340454s
Amount of data | Number of triples check for Bio2RDF::Taxonomy took 43.39477324485779s
Interoperability | New terms check for Bio2RDF::Taxonomy took 40.06650447845459s
Versatility | Languages check for Bio2RDF::Taxonomy took 60.23279285430908s
Interpretability | Number of blank nodes check for Bio2RDF::Taxonomy took 0.27547192573547363s
Security | Check HTTPS for Bio2RDF::Taxonomy took 0.144301176071167s
Interpretability | RDF structures check for Bio2RDF::Taxonomy took 0.5100193023681641s
Versatility | Serialization formats check for Bio2RDF::Taxonomy took 0.28888869285583496s
Availability | RDF dump link check for Bio2RDF::Taxonomy took 2.0692780017852783s
License | MR license check for Bio2RDF::Taxonomy took 0.4473721981048584s
License | HR license check for Bio2RDF::Taxonomy took 60.23234272003174s
Amount of data | Number of property check for Bio2RDF::Taxonomy took 0.2404463291168213s
Understandability | Number of label check for Bio2RDF::Taxonomy took 9.490161180496216s
Understandability | URI regex check for Bio2RDF::Taxonomy took 0.5357980728149414s
Understandability | Vocabs check for Bio2RDF::Taxonomy took 0.23480534553527832s
Verifiability | Authors check for Bio2RDF::Taxonomy took 0.24321985244750977s
Verifiability | Publishers check for Bio2RDF::Taxonomy took 0.2372267246246338s
Performance | Throughput check for Bio2RDF::Taxonomy took 11.584950685501099s
Amount of data | Check the number of entities for Bio2RDF::Taxonomy took 75.13711428642273s
Verifiability | Contribs. check for Bio2RDF::Taxonomy took 0.6653132438659668s
Interlinking | sameAs chians check for Bio2RDF::Taxonomy took 0.3401155471801758s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.8270668983459473s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.32962512969970703s
Timeliness | dataset update frequency check for Bio2RDF::Taxonomy took 0.23475193977355957s
Currency | Creation date check for Bio2RDF::Taxonomy took 0.4650416374206543s
Currency | Modification date check for Bio2RDF::Taxonomy took 0.471132755279541s
Rep.Conc. | URIs length for Bio2RDF::Taxonomy took 107.32351970672607s
Interoperability | New vocabularies check for Bio2RDF::Taxonomy took 48.25927233695984s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Taxonomy took 0.4194340705871582s
Accuracy | Check Functional Property for Bio2RDF::Taxonomy took 0.25452327728271484s
Accuracy | Check Inverse Functional Property for Bio2RDF::Taxonomy took 0.2538950443267822s
Accuracy | Check Empty annotation labels for Bio2RDF::Taxonomy took 7.332893133163452s
Accuracy | Check White space in annotation for Bio2RDF::Taxonomy took 0.8784239292144775s
Accuracy | Check Datatype consistency for Bio2RDF::Taxonomy took 0.632922887802124s
Consistency | Disjoint class check for Bio2RDF::Taxonomy took 0.3720548152923584s
Consistency | Check Misplaced properties for Bio2RDF::Taxonomy took 64.63061928749084s
Consistency | Misplaced classes for Bio2RDF::Taxonomy took 2.313539743423462s
Consistency | Check Ontology hijacking for Bio2RDF::Taxonomy took 5.883178234100342s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Taxonomy took 1.2790989875793457s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Taxonomy took 61.547415256500244s
Conciseness | Check Extensional conciseness for Bio2RDF::Taxonomy took 0.7105066776275635s
Conciseness | Check Intensional conciseness for Bio2RDF::Taxonomy took 0.6737964153289795s
Security | Sign check for Bio2RDF::Taxonomy took 0.2491922378540039s
Availability | Check URIs Dereferenciability for Bio2RDF::Taxonomy took 10.093276023864746s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 0.38659119606018066s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.020966768264770508s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 0.00010538101196289062s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Taxonomy took 53.25274419784546s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-taxonomy took 1098.6821992397308s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 0.13569235801696777s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.0005953311920166016s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 0.2692699432373047s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.020975589752197266s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 3.0517578125e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 9.298324584960938e-06s
INFO | --- Analysis for bio2rdf-wikipathways took 16.086243629455566s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 0.5640764236450195s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.0006537437438964844s
Extra | Recovery of all triples for Bio2RDF::Wormbase took 18.155915021896362s
Performance | Total latancy measurement for Bio2RDF::Wormbase took 1.139160394668579s
Amount of data | Number of triples check for Bio2RDF::Wormbase took 43.787219285964966s
Interoperability | New terms check for Bio2RDF::Wormbase took 40.22622871398926s
Versatility | Languages check for Bio2RDF::Wormbase took 60.25016140937805s
Interpretability | Number of blank nodes check for Bio2RDF::Wormbase took 0.2463362216949463s
Security | Check HTTPS for Bio2RDF::Wormbase took 0.1448359489440918s
Interpretability | RDF structures check for Bio2RDF::Wormbase took 0.6103367805480957s
Versatility | Serialization formats check for Bio2RDF::Wormbase took 0.29478907585144043s
Availability | RDF dump link check for Bio2RDF::Wormbase took 2.0826408863067627s
License | MR license check for Bio2RDF::Wormbase took 0.4721221923828125s
License | HR license check for Bio2RDF::Wormbase took 60.230780363082886s
Amount of data | Number of property check for Bio2RDF::Wormbase took 0.23769497871398926s
Understandability | Number of label check for Bio2RDF::Wormbase took 9.85874891281128s
Understandability | URI regex check for Bio2RDF::Wormbase took 0.5404343605041504s
Understandability | Vocabs check for Bio2RDF::Wormbase took 0.23466205596923828s
Verifiability | Authors check for Bio2RDF::Wormbase took 0.23771953582763672s
Verifiability | Publishers check for Bio2RDF::Wormbase took 0.23618841171264648s
Performance | Throughput check for Bio2RDF::Wormbase took 11.548352241516113s
Amount of data | Check the number of entities for Bio2RDF::Wormbase took 73.28534746170044s
Verifiability | Contribs. check for Bio2RDF::Wormbase took 0.6560091972351074s
Interlinking | sameAs chians check for Bio2RDF::Wormbase took 0.33617305755615234s
Interlinking | skos check for Bio2RDF::Wormbase took 0.9217572212219238s
Interlinking | skos check for Bio2RDF::Wormbase took 0.32493066787719727s
Timeliness | dataset update frequency check for Bio2RDF::Wormbase took 0.23684954643249512s
Currency | Creation date check for Bio2RDF::Wormbase took 0.4828164577484131s
Currency | Modification date check for Bio2RDF::Wormbase took 0.471172571182251s
Rep.Conc. | URIs length for Bio2RDF::Wormbase took 107.35003662109375s
Interoperability | New vocabularies check for Bio2RDF::Wormbase took 452.553183555603s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Wormbase took 0.8126039505004883s
Accuracy | Check Functional Property for Bio2RDF::Wormbase took 0.2567126750946045s
Accuracy | Check Inverse Functional Property for Bio2RDF::Wormbase took 0.2551605701446533s
Accuracy | Check Empty annotation labels for Bio2RDF::Wormbase took 6.857440948486328s
Accuracy | Check White space in annotation for Bio2RDF::Wormbase took 0.8781375885009766s
Accuracy | Check Datatype consistency for Bio2RDF::Wormbase took 0.63755202293396s
Consistency | Disjoint class check for Bio2RDF::Wormbase took 0.3973395824432373s
Consistency | Check Misplaced properties for Bio2RDF::Wormbase took 64.74039459228516s
Consistency | Misplaced classes for Bio2RDF::Wormbase took 2.337851047515869s
Consistency | Check Ontology hijacking for Bio2RDF::Wormbase took 5.862449884414673s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Wormbase took 1.282942295074463s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Wormbase took 61.54633092880249s
Conciseness | Check Extensional conciseness for Bio2RDF::Wormbase took 0.7179715633392334s
Conciseness | Check Intensional conciseness for Bio2RDF::Wormbase took 0.3973197937011719s
Security | Sign check for Bio2RDF::Wormbase took 0.24849295616149902s
Availability | Check URIs Dereferenciability for Bio2RDF::Wormbase took 9.81353497505188s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 0.4993937015533447s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.02097177505493164s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 8.273124694824219e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Wormbase took 472.5393967628479s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 1.9550323486328125e-05s
INFO | --- Analysis for bio2rdf-wormbase took 1919.4288129806519s
Availability | SPARQL endpoint availability check for Biografías y Vidas took 9.036064147949219e-05s
Availability | VoID file availability check for Biografías y Vidas took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for Biografías y Vidas took 0.26810383796691895s
Reputation | Calculation of the PageRank for Biografías y Vidas took 0.020592451095581055s
Interlinking | Calculation of Degree of Connection for Biografías y Vidas took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Biografías y Vidas took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Biografías y Vidas took 1.1920928955078125e-05s
Believability | Calculation of trust value for Biografías y Vidas took 1.1205673217773438e-05s
INFO | --- Analysis for biografiasyvidas took 2.375807046890259s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 0.5766355991363525s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.0002193450927734375s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 0.2639496326446533s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.020340681076049805s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 8.225440979003906e-05s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 1.0251998901367188e-05s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 2.9932663440704346s
Availability | SPARQL endpoint availability check for BioLOD for Protein Data Bank Japan took 0.00018143653869628906s
Availability | VoID file availability check for BioLOD for Protein Data Bank Japan took 0.0006566047668457031s
Completeness | Calculation of interlinking completeness for BioLOD for Protein Data Bank Japan took 0.2637755870819092s
Reputation | Calculation of the PageRank for BioLOD for Protein Data Bank Japan took 0.02030205726623535s
Interlinking | Calculation of Degree of Connection for BioLOD for Protein Data Bank Japan took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BioLOD for Protein Data Bank Japan took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for BioLOD for Protein Data Bank Japan took 3.886222839355469e-05s
Believability | Calculation of trust value for BioLOD for Protein Data Bank Japan took 1.2159347534179688e-05s
INFO | --- Analysis for biolod-pdb took 8.038804292678833s
Availability | SPARQL endpoint availability check for BioModels RDF took 0.5242042541503906s
Availability | VoID file availability check for BioModels RDF took 0.0005528926849365234s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.27159667015075684s
Reputation | Calculation of the PageRank for BioModels RDF took 0.021239280700683594s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 3.600120544433594e-05s
Believability | Calculation of trust value for BioModels RDF took 1.1444091796875e-05s
INFO | --- Analysis for biomodels-rdf took 3.5905394554138184s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.301229953765869s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0005955696105957031s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.262622594833374s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.020316123962402344s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.956390380859375e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.049041748046875e-05s
INFO | --- Analysis for Biop took 6.041004180908203s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 8.96453857421875e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0005362033843994141s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.26117539405822754s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.020934343338012695s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.743171691894531e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.2159347534179688e-05s
INFO | --- Analysis for Bioportal took 2.488454818725586s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 8.559226989746094e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 0.0007302761077880859s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.2628638744354248s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.02036142349243164s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006239414215087891s
Believability | Calculation of trust value for Amphibian gross anatomy took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-aao took 4.5484299659729s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 4.3392181396484375e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.0007736682891845703s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 0.26346921920776367s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.02054882049560547s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.0003063678741455078s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-aba took 3.9828662872314453s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 8.96453857421875e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.26787519454956055s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.02121448516845703s
Interlinking | Calculation of Degree of Connection for Cancer Research and Management ACGT Master Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Cancer Research and Management ACGT Master Ontology took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0015292167663574219s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-acgt took 4.494084119796753s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 9.107589721679688e-05s
Availability | VoID file availability check for Animal natural history and life history took 0.0007381439208984375s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 0.26157069206237793s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.020409822463989258s
Interlinking | Calculation of Degree of Connection for Animal natural history and life history took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Animal natural history and life history took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.0003352165222167969s
Believability | Calculation of trust value for Animal natural history and life history took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-adw took 4.198476552963257s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 9.655952453613281e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.0006420612335205078s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 0.2664346694946289s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.020397424697875977s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.000499725341796875s
Believability | Calculation of trust value for Anatomical Entity Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-aeo took 4.222337961196899s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 4.8160552978515625e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 0.0007534027099609375s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 0.2624843120574951s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.02101278305053711s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0009837150573730469s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-aero took 4.191953420639038s
Availability | SPARQL endpoint availability check for AI/RHEUM took 8.726119995117188e-05s
Availability | VoID file availability check for AI/RHEUM took 0.0005834102630615234s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 0.2642953395843506s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.0201568603515625s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.00039196014404296875s
Believability | Calculation of trust value for AI/RHEUM took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-air took 4.219717264175415s
Availability | SPARQL endpoint availability check for Amino Acid took 8.58306884765625e-05s
Availability | VoID file availability check for Amino Acid took 0.0006775856018066406s
Completeness | Calculation of interlinking completeness for Amino Acid took 0.26650166511535645s
Reputation | Calculation of the PageRank for Amino Acid took 0.0208585262298584s
Interlinking | Calculation of Degree of Connection for Amino Acid took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Amino Acid took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.0002582073211669922s
Believability | Calculation of trust value for Amino Acid took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-amino-acid took 4.343684673309326s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 8.845329284667969e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.0006086826324462891s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.268751859664917s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.02037358283996582s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.00029659271240234375s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-apo took 4.124756574630737s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 8.463859558105469e-05s
Availability | VoID file availability check for African Traditional Medicine took 0.0006017684936523438s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 0.26052308082580566s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.020244359970092773s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.0002338886260986328s
Believability | Calculation of trust value for African Traditional Medicine took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-atmo took 3.9439780712127686s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 4.1961669921875e-05s
Availability | VoID file availability check for Amphibian taxonomy took 0.00063323974609375s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.2625422477722168s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.020201444625854492s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 8.535385131835938e-05s
Believability | Calculation of trust value for Amphibian taxonomy took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-ato took 3.956146240234375s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 8.988380432128906e-05s
Availability | VoID file availability check for BioAssay Ontology took 0.0008513927459716797s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 0.26301050186157227s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.020624160766601562s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.0013201236724853516s
Believability | Calculation of trust value for BioAssay Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-bao took 4.2775373458862305s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 8.869171142578125e-05s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.0006282329559326172s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 0.26654791831970215s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.02086329460144043s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.0003974437713623047s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 4.492577314376831s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.00060272216796875s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.2663538455963135s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.020482778549194336s
Interlinking | Calculation of Degree of Connection for Breast Cancer Grading Ontology took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Breast Cancer Grading Ontology took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.0003173351287841797s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-bcgo took 4.072172403335571s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 8.797645568847656e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.0006251335144042969s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.3003671169281006s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.02076244354248047s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.001422882080078125s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-bdo took 4.2705981731414795s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 8.678436279296875e-05s
Availability | VoID file availability check for Basic Formal Ontology took 0.0006208419799804688s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.2649657726287842s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.02053236961364746s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0005443096160888672s
Believability | Calculation of trust value for Basic Formal Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-bfo took 4.249298095703125s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 4.267692565917969e-05s
Availability | VoID file availability check for Bleeding History Phenotype took 0.0005910396575927734s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.26330065727233887s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.020843505859375s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0007774829864501953s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0007584095001220703s
Believability | Calculation of trust value for Bleeding History Phenotype took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-bho took 4.079849481582642s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 4.363059997558594e-05s
Availability | VoID file availability check for Bilateria anatomy took 0.0005691051483154297s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.2631642818450928s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.02136993408203125s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.0004436969757080078s
Believability | Calculation of trust value for Bilateria anatomy took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-bila took 3.9706673622131348s
Availability | SPARQL endpoint availability check for BIRNLex took 4.458427429199219e-05s
Availability | VoID file availability check for BIRNLex took 0.0006422996520996094s
Completeness | Calculation of interlinking completeness for BIRNLex took 0.2664499282836914s
Reputation | Calculation of the PageRank for BIRNLex took 0.020554304122924805s
Interlinking | Calculation of Degree of Connection for BIRNLex took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BIRNLex took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.0014739036560058594s
Believability | Calculation of trust value for BIRNLex took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-birnlex took 4.321078538894653s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 7.748603820800781e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0005841255187988281s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.26181578636169434s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.02257847785949707s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0008203983306884766s
Believability | Calculation of trust value for Gene Regulation Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-bootstrep took 3.852644681930542s
Availability | SPARQL endpoint availability check for BioPAX took 8.869171142578125e-05s
Availability | VoID file availability check for BioPAX took 0.0006368160247802734s
Completeness | Calculation of interlinking completeness for BioPAX took 0.2801172733306885s
Reputation | Calculation of the PageRank for BioPAX took 0.02228999137878418s
Interlinking | Calculation of Degree of Connection for BioPAX took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BioPAX took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for BioPAX took 9.465217590332031e-05s
Believability | Calculation of trust value for BioPAX took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-bp took 4.078451871871948s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 8.7738037109375e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.0005960464477539062s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.2607753276824951s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.020188570022583008s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.00031638145446777344s
Believability | Calculation of trust value for Biomedical Resource Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-bro_x1 took 4.092943429946899s
Availability | SPARQL endpoint availability check for Spatial Ontology took 8.654594421386719e-05s
Availability | VoID file availability check for Spatial Ontology took 0.0005972385406494141s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 0.26781153678894043s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.020678043365478516s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.00021529197692871094s
Believability | Calculation of trust value for Spatial Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-bspo took 4.149810791015625s
Availability | SPARQL endpoint availability check for BioTop took 4.887580871582031e-05s
Availability | VoID file availability check for BioTop took 0.0006222724914550781s
Completeness | Calculation of interlinking completeness for BioTop took 0.2654881477355957s
Reputation | Calculation of the PageRank for BioTop took 0.021052837371826172s
Interlinking | Calculation of Degree of Connection for BioTop took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BioTop took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006716251373291016s
Believability | Calculation of trust value for BioTop took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-bt took 4.0536110401153564s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 8.940696716308594e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.0007920265197753906s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.2741701602935791s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.02131938934326172s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for BRENDA tissue / enzyme source took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0008902549743652344s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-bto took 4.047410011291504s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.0005822181701660156s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.3146963119506836s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.02036261558532715s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.001867532730102539s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-canco took 4.3408896923065186s
Availability | SPARQL endpoint availability check for CAO took 4.172325134277344e-05s
Availability | VoID file availability check for CAO took 0.0007569789886474609s
Completeness | Calculation of interlinking completeness for CAO took 0.2680668830871582s
Reputation | Calculation of the PageRank for CAO took 0.02080082893371582s
Interlinking | Calculation of Degree of Connection for CAO took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CAO took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0006077289581298828s
Believability | Calculation of trust value for CAO took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-cao took 4.013498783111572s
Availability | SPARQL endpoint availability check for CareLex took 8.916854858398438e-05s
Availability | VoID file availability check for CareLex took 0.0007255077362060547s
Completeness | Calculation of interlinking completeness for CareLex took 0.2663445472717285s
Reputation | Calculation of the PageRank for CareLex took 0.020596027374267578s
Interlinking | Calculation of Degree of Connection for CareLex took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for CareLex took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for CareLex took 5.340576171875e-05s
Believability | Calculation of trust value for CareLex took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-carelex took 3.8634893894195557s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 8.726119995117188e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 0.0007829666137695312s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.2625865936279297s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.030817031860351562s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.0011696815490722656s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0011982917785644531s
Believability | Calculation of trust value for Cell Cycle Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-cco took 3.8236985206604004s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 9.202957153320312e-05s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 0.0007867813110351562s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.26221203804016113s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.022126436233520508s
Interlinking | Calculation of Degree of Connection for Comparative Data Analysis Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Comparative Data Analysis Ontology took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.000263214111328125s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-cdao took 4.10090184211731s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 8.797645568847656e-05s
Availability | VoID file availability check for Chemical entities of biological interest took 0.0006399154663085938s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.2660226821899414s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.02030491828918457s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.000782012939453125s
Believability | Calculation of trust value for Chemical entities of biological interest took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-chebi took 4.052950859069824s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 4.482269287109375e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.0007829666137695312s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.26575303077697754s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.02093505859375s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.0010519027709960938s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.000362396240234375s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-chem2bio2owl took 4.274622440338135s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 9.632110595703125e-05s
Availability | VoID file availability check for Chemical Information Ontology took 0.0006616115570068359s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.29459166526794434s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.020714759826660156s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0007593631744384766s
Believability | Calculation of trust value for Chemical Information Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-cheminf took 3.859583854675293s
Availability | SPARQL endpoint availability check for Cell type took 8.797645568847656e-05s
Availability | VoID file availability check for Cell type took 0.0007350444793701172s
Completeness | Calculation of interlinking completeness for Cell type took 0.30691957473754883s
Reputation | Calculation of the PageRank for Cell type took 0.02100682258605957s
Interlinking | Calculation of Degree of Connection for Cell type took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Cell type took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.000423431396484375s
Believability | Calculation of trust value for Cell type took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-cl took 3.8777010440826416s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Cell Line Ontology took 0.0006906986236572266s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.26792407035827637s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.021589279174804688s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0008406639099121094s
Believability | Calculation of trust value for Cell Line Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-clo took 4.079410791397095s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 8.7738037109375e-05s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.0005927085876464844s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 0.27697038650512695s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.020236492156982422s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.00017380714416503906s
Believability | Calculation of trust value for Clinical Measurement Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-cmo took 4.114072322845459s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 8.678436279296875e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.0005831718444824219s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 0.2632570266723633s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.020303726196289062s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.00020074844360351562s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-cno took 3.893064260482788s
Availability | SPARQL endpoint availability check for Wheat trait took 0.00022673606872558594s
Availability | VoID file availability check for Wheat trait took 0.0006804466247558594s
Completeness | Calculation of interlinking completeness for Wheat trait took 0.33157992362976074s
Reputation | Calculation of the PageRank for Wheat trait took 0.02047133445739746s
Interlinking | Calculation of Degree of Connection for Wheat trait took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Wheat trait took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 5.435943603515625e-05s
Believability | Calculation of trust value for Wheat trait took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-co_wheat took 4.169753074645996s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 8.702278137207031e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.0006060600280761719s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.2677905559539795s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.021171092987060547s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0008094310760498047s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.0004036426544189453s
Believability | Calculation of trust value for Cognitive Atlas took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-cogat took 4.108188152313232s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 0.00010323524475097656s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.0006999969482421875s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.2608201503753662s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.020328044891357422s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0008535385131835938s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-cogpo took 3.9614014625549316s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 8.845329284667969e-05s
Availability | VoID file availability check for Current Procedural Terminology took 0.0006906986236572266s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.2661292552947998s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.020595788955688477s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.00042438507080078125s
Believability | Calculation of trust value for Current Procedural Terminology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-cpt took 5.222405910491943s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 4.1484832763671875e-05s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.0005652904510498047s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 0.3124270439147949s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.021517515182495117s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.0018150806427001953s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-csp took 4.676395654678345s
Availability | SPARQL endpoint availability check for COSTART took 9.72747802734375e-05s
Availability | VoID file availability check for COSTART took 0.0006821155548095703s
Completeness | Calculation of interlinking completeness for COSTART took 0.26453733444213867s
Reputation | Calculation of the PageRank for COSTART took 0.02098870277404785s
Interlinking | Calculation of Degree of Connection for COSTART took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for COSTART took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0010139942169189453s
Believability | Calculation of trust value for COSTART took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-cst took 4.215017080307007s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 8.845329284667969e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 0.0006947517395019531s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.26440882682800293s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.02214527130126953s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.000530242919921875s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-ctcae took 4.132181882858276s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 8.916854858398438e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.0007457733154296875s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.2632310390472412s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.02091693878173828s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.0004723072052001953s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ctx took 3.9351656436920166s
Availability | SPARQL endpoint availability check for Dendritic cell took 8.916854858398438e-05s
Availability | VoID file availability check for Dendritic cell took 0.00069427490234375s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.2701709270477295s
Reputation | Calculation of the PageRank for Dendritic cell took 0.02022695541381836s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.000293731689453125s
Believability | Calculation of trust value for Dendritic cell took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-dc_cl took 3.9940714836120605s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 4.315376281738281e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.0007395744323730469s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 0.272907018661499s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.020200252532958984s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 8.678436279296875e-05s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ddanat took 3.8929924964904785s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 9.465217590332031e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.00066375732421875s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.2776679992675781s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.020366668701171875s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.0009958744049072266s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-ddi took 4.17099404335022s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 8.988380432128906e-05s
Availability | VoID file availability check for Diagnostic Ontology took 0.0006482601165771484s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.2642178535461426s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.02022719383239746s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 8.416175842285156e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-diagnosticont took 4.373818635940552s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.00038433074951171875s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.27023863792419434s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.020285367965698242s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.00015664100646972656s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-dikb-evidence took 4.336519956588745s
Availability | SPARQL endpoint availability check for Human disease ontology took 9.059906005859375e-05s
Availability | VoID file availability check for Human disease ontology took 0.0006401538848876953s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.2726566791534424s
Reputation | Calculation of the PageRank for Human disease ontology took 0.021201372146606445s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Human disease ontology took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0006175041198730469s
Believability | Calculation of trust value for Human disease ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-doid took 3.78952956199646s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 8.702278137207031e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 0.0007083415985107422s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 0.26681995391845703s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.02241683006286621s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0008149147033691406s
Believability | Calculation of trust value for Electrocardiography Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-ecg took 3.9995980262756348s
Availability | SPARQL endpoint availability check for Evidence codes took 4.220008850097656e-05s
Availability | VoID file availability check for Evidence codes took 0.0007281303405761719s
Completeness | Calculation of interlinking completeness for Evidence codes took 0.2610948085784912s
Reputation | Calculation of the PageRank for Evidence codes took 0.02023625373840332s
Interlinking | Calculation of Degree of Connection for Evidence codes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Evidence codes took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 3.075599670410156e-05s
Believability | Calculation of trust value for Evidence codes took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-eco took 4.071484327316284s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 9.799003601074219e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 0.0006165504455566406s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.31021690368652344s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.02160334587097168s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.000926971435546875s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.0018892288208007812s
Believability | Calculation of trust value for Experimental Factor Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-efo took 4.545367479324341s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 0.000110626220703125s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.0006172657012939453s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 0.2671995162963867s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.020243406295776367s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.0011522769927978516s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ehda took 3.981940984725952s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 4.267692565917969e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.0006766319274902344s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.26520371437072754s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.020446300506591797s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007190704345703125s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ehdaa took 4.178998231887817s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 8.416175842285156e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.0006260871887207031s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.26883888244628906s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.020449161529541016s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version, v2 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version, v2 took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0005316734313964844s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-ehdaa2 took 4.087093114852905s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 4.363059997558594e-05s
Availability | VoID file availability check for Mouse gross anatomy and development took 0.0008435249328613281s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 0.27108120918273926s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.023040294647216797s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 3.457069396972656e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-emap took 4.060178518295288s
Availability | SPARQL endpoint availability check for Environment Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Environment Ontology took 0.0013740062713623047s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.2567145824432373s
Reputation | Calculation of the PageRank for Environment Ontology took 0.02010822296142578s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.0003974437713623047s
Believability | Calculation of trust value for Environment Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-envo took 4.284956216812134s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 4.291534423828125e-05s
Availability | VoID file availability check for Plant environmental conditions took 0.0006821155548095703s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.2633390426635742s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.02024388313293457s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.00028824806213378906s
Believability | Calculation of trust value for Plant environmental conditions took 7.62939453125e-06s
INFO | --- Analysis for bioportal-eo took 4.028669834136963s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.0003657341003417969s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.2579507827758789s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.020211458206176758s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.0012106895446777344s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-ep took 4.246294736862183s
Availability | SPARQL endpoint availability check for Epilepsy took 0.0001404285430908203s
Availability | VoID file availability check for Epilepsy took 0.0006375312805175781s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.26653456687927246s
Reputation | Calculation of the PageRank for Epilepsy took 0.020547866821289062s
Interlinking | Calculation of Degree of Connection for Epilepsy took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Epilepsy took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.00012922286987304688s
Believability | Calculation of trust value for Epilepsy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-epileponto took 3.983370780944824s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 4.291534423828125e-05s
Availability | VoID file availability check for eagle-i research resource ontology took 0.0008561611175537109s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.2791874408721924s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.021236658096313477s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.0011477470397949219s
Believability | Calculation of trust value for eagle-i research resource ontology took 3.814697265625e-06s
INFO | --- Analysis for bioportal-ero took 4.002080678939819s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 4.220008850097656e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 0.26056957244873047s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.020191669464111328s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.0011386871337890625s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ev took 3.953043222427368s
Availability | SPARQL endpoint availability check for ExO took 5.817413330078125e-05s
Availability | VoID file availability check for ExO took 0.0004451274871826172s
Completeness | Calculation of interlinking completeness for ExO took 0.25934481620788574s
Reputation | Calculation of the PageRank for ExO took 0.02016592025756836s
Interlinking | Calculation of Degree of Connection for ExO took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ExO took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for ExO took 0.00023412704467773438s
Believability | Calculation of trust value for ExO took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-exo took 4.071741819381714s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 7.390975952148438e-05s
Availability | VoID file availability check for Fungal gross anatomy took 0.00029969215393066406s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 0.2633328437805176s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.02080702781677246s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.00011301040649414062s
Believability | Calculation of trust value for Fungal gross anatomy took 7.62939453125e-06s
INFO | --- Analysis for bioportal-fao took 4.013345956802368s
Availability | SPARQL endpoint availability check for Biological imaging methods took 4.38690185546875e-05s
Availability | VoID file availability check for Biological imaging methods took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.26151514053344727s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.020623445510864258s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.00018906593322753906s
Believability | Calculation of trust value for Biological imaging methods took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-fbbi took 4.023101329803467s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 8.58306884765625e-05s
Availability | VoID file availability check for Drosophila gross anatomy took 0.0005753040313720703s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 0.265439510345459s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.02093791961669922s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0006999969482421875s
Believability | Calculation of trust value for Drosophila gross anatomy took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-fbbt took 4.044362783432007s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 8.893013000488281e-05s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.0005676746368408203s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.2659437656402588s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.020699262619018555s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.0004227161407470703s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-fbcv took 3.7893431186676025s
Availability | SPARQL endpoint availability check for Drosophila development took 4.482269287109375e-05s
Availability | VoID file availability check for Drosophila development took 0.0006270408630371094s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.2681889533996582s
Reputation | Calculation of the PageRank for Drosophila development took 0.020682096481323242s
Interlinking | Calculation of Degree of Connection for Drosophila development took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Drosophila development took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.4345855712890625e-05s
Believability | Calculation of trust value for Drosophila development took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-fbdv took 4.109112501144409s
Availability | SPARQL endpoint availability check for Fly taxonomy took 8.678436279296875e-05s
Availability | VoID file availability check for Fly taxonomy took 0.00036215782165527344s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.26169657707214355s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.02059626579284668s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.0004029273986816406s
Believability | Calculation of trust value for Fly taxonomy took 3.814697265625e-06s
INFO | --- Analysis for bioportal-fbsp took 4.189763069152832s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 8.845329284667969e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.0006308555603027344s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.26187825202941895s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.021945714950561523s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0008478164672851562s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.00025272369384765625s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-fda-meddevice took 4.373972654342651s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Family Health History Ontology took 0.0006806850433349609s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 0.2643778324127197s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.020676136016845703s
Interlinking | Calculation of Degree of Connection for Family Health History Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Family Health History Ontology took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.00039958953857421875s
Believability | Calculation of trust value for Family Health History Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-fhho took 3.952279806137085s
Availability | SPARQL endpoint availability check for Influenza Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Influenza Ontology took 0.0007486343383789062s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.3421480655670166s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.02018260955810547s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.001055002212524414s
Believability | Calculation of trust value for Influenza Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-flu took 3.947692394256592s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 4.3392181396484375e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.0006792545318603516s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.27457451820373535s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.02022576332092285s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 6.29425048828125e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-fma took 4.067206621170044s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 4.792213439941406e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 0.0006465911865234375s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 0.26340579986572266s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.02019047737121582s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.0001316070556640625s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-fypo took 4.0373921394348145s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 8.606910705566406e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 0.0006697177886962891s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.2663381099700928s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.02017664909362793s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 8.58306884765625e-05s
Believability | Calculation of trust value for GeoSpecies Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-geospecies took 4.071526765823364s
Availability | SPARQL endpoint availability check for General Formal Ontology took 8.58306884765625e-05s
Availability | VoID file availability check for General Formal Ontology took 0.0007033348083496094s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.2655003070831299s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.021018266677856445s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.00015878677368164062s
Believability | Calculation of trust value for General Formal Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-gfo took 3.905520439147949s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 4.1961669921875e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.0006477832794189453s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.26625704765319824s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.020937681198120117s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.0005998611450195312s
Believability | Calculation of trust value for General Formal Ontology: Biology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-gfo-bio took 4.337360858917236s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 8.940696716308594e-05s
Availability | VoID file availability check for Gene Ontology Extension took 0.0006799697875976562s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 0.26607227325439453s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.020274877548217773s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0008490085601806641s
Believability | Calculation of trust value for Gene Ontology Extension took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-go_x1 took 4.10477614402771s
Availability | SPARQL endpoint availability check for Gene Ontology took 8.869171142578125e-05s
Availability | VoID file availability check for Gene Ontology took 0.0006442070007324219s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.26977992057800293s
Reputation | Calculation of the PageRank for Gene Ontology took 0.020631074905395508s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0008392333984375s
Believability | Calculation of trust value for Gene Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-go_x2 took 4.05170464515686s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 8.916854858398438e-05s
Availability | VoID file availability check for Cereal Plant Development took 0.0007052421569824219s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 0.26154088973999023s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.020611286163330078s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 3.218650817871094e-05s
Believability | Calculation of trust value for Cereal Plant Development took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-gro took 3.9732565879821777s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 4.315376281738281e-05s
Availability | VoID file availability check for Cereal plant gross anatomy took 0.0005650520324707031s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 0.2725186347961426s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.020368576049804688s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.0004360675811767578s
Believability | Calculation of trust value for Cereal plant gross anatomy took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-gro_x1 took 4.154407024383545s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0007290840148925781s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.2969965934753418s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.02033257484436035s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007495880126953125s
Believability | Calculation of trust value for Gene Regulation Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-gro_x2 took 4.187004804611206s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 8.416175842285156e-05s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.0005941390991210938s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.2664620876312256s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.02032613754272461s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0005686283111572266s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-hao took 4.235380411148071s
Availability | SPARQL endpoint availability check for HCPCS took 4.863739013671875e-05s
Availability | VoID file availability check for HCPCS took 0.0006990432739257812s
Completeness | Calculation of interlinking completeness for HCPCS took 0.2663445472717285s
Reputation | Calculation of the PageRank for HCPCS took 0.020075321197509766s
Interlinking | Calculation of Degree of Connection for HCPCS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for HCPCS took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.0002162456512451172s
Believability | Calculation of trust value for HCPCS took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-hcpcs took 4.172303676605225s
Availability | SPARQL endpoint availability check for Health Level Seven took 0.00011086463928222656s
Availability | VoID file availability check for Health Level Seven took 0.0006959438323974609s
Completeness | Calculation of interlinking completeness for Health Level Seven took 0.268604040145874s
Reputation | Calculation of the PageRank for Health Level Seven took 0.020467281341552734s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.001300811767578125s
Believability | Calculation of trust value for Health Level Seven took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-hl7 took 4.152918577194214s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 9.34600830078125e-05s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.0006053447723388672s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.2618882656097412s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.0204617977142334s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.0003440380096435547s
Believability | Calculation of trust value for HEALTH_INDICATORS took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-hlth_indics took 4.491295576095581s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 8.916854858398438e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.0006356239318847656s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.26688313484191895s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.021511077880859375s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 3.123283386230469e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-hom took 4.212424278259277s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 4.2438507080078125e-05s
Availability | VoID file availability check for HOM-HARVARD took 0.0006823539733886719s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 0.26360535621643066s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.020435094833374023s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 3.0040740966796875e-05s
Believability | Calculation of trust value for HOM-HARVARD took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-hom_harvard took 4.151784420013428s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 5.53131103515625e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 0.0006153583526611328s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.26189184188842773s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.02053546905517578s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0006682872772216797s
Believability | Calculation of trust value for Human Phenotype Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-hp_x1 took 3.871340036392212s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 0.2644829750061035s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.020802021026611328s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.0010433197021484375s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-hpio took 3.9685862064361572s
Availability | SPARQL endpoint availability check for HUGO took 4.267692565917969e-05s
Availability | VoID file availability check for HUGO took 0.0007078647613525391s
Completeness | Calculation of interlinking completeness for HUGO took 0.26720309257507324s
Reputation | Calculation of the PageRank for HUGO took 0.020451068878173828s
Interlinking | Calculation of Degree of Connection for HUGO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for HUGO took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for HUGO took 7.915496826171875e-05s
Believability | Calculation of trust value for HUGO took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-hugo took 4.229258298873901s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 8.630752563476562e-05s
Availability | VoID file availability check for Information Artifact Ontology took 0.0006575584411621094s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 0.26468706130981445s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.020194530487060547s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0006570816040039062s
Believability | Calculation of trust value for Information Artifact Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-iao took 4.066070318222046s
Availability | SPARQL endpoint availability check for ICD10 took 8.535385131835938e-05s
Availability | VoID file availability check for ICD10 took 0.0006284713745117188s
Completeness | Calculation of interlinking completeness for ICD10 took 0.26146554946899414s
Reputation | Calculation of the PageRank for ICD10 took 0.020317554473876953s
Interlinking | Calculation of Degree of Connection for ICD10 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ICD10 took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.0008141994476318359s
Believability | Calculation of trust value for ICD10 took 7.62939453125e-06s
INFO | --- Analysis for bioportal-icd10 took 4.012345314025879s
Availability | SPARQL endpoint availability check for ICD10CM took 8.702278137207031e-05s
Availability | VoID file availability check for ICD10CM took 0.0006756782531738281s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.2666628360748291s
Reputation | Calculation of the PageRank for ICD10CM took 0.020724058151245117s
Interlinking | Calculation of Degree of Connection for ICD10CM took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ICD10CM took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0006084442138671875s
Believability | Calculation of trust value for ICD10CM took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-icd10cm took 4.168327331542969s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 4.506111145019531e-05s
Availability | VoID file availability check for ICD-10-PCS took 0.0007197856903076172s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 0.26703786849975586s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.02139115333557129s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.0001513957977294922s
Believability | Calculation of trust value for ICD-10-PCS took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-icd10pcs took 3.898094415664673s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 5.173683166503906e-05s
Availability | VoID file availability check for International Classification of Diseases took 0.0006580352783203125s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 0.2618682384490967s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.020730972290039062s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0006601810455322266s
Believability | Calculation of trust value for International Classification of Diseases took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-icd9cm took 3.830601453781128s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 4.3392181396484375e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.0007433891296386719s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.2684030532836914s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.02047276496887207s
Interlinking | Calculation of Degree of Connection for International Classification of Functioning, Disability and Health (ICF) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for International Classification of Functioning, Disability and Health (ICF) took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.0004417896270751953s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-icf_x1 took 4.083930969238281s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 4.220008850097656e-05s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.0007824897766113281s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 0.26712489128112793s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.021558046340942383s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.0012307167053222656s
Believability | Calculation of trust value for International Classification for Nursing Practice took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-icnp took 4.049484729766846s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 9.775161743164062e-05s
Availability | VoID file availability check for International Classification of Primary Care took 0.0007042884826660156s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 0.3099501132965088s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.020374536514282227s
Interlinking | Calculation of Degree of Connection for International Classification of Primary Care took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for International Classification of Primary Care took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.000446319580078125s
Believability | Calculation of trust value for International Classification of Primary Care took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-icpc took 4.311659097671509s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 8.96453857421875e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 0.0005555152893066406s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.2653639316558838s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.020755767822265625s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0009152889251708984s
Believability | Calculation of trust value for ICPC-2 PLUS took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-icpc2p took 4.461189031600952s
Availability | SPARQL endpoint availability check for ICPS Network took 9.083747863769531e-05s
Availability | VoID file availability check for ICPS Network took 0.000690460205078125s
Completeness | Calculation of interlinking completeness for ICPS Network took 0.2881433963775635s
Reputation | Calculation of the PageRank for ICPS Network took 0.022125244140625s
Interlinking | Calculation of Degree of Connection for ICPS Network took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ICPS Network took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.00021529197692871094s
Believability | Calculation of trust value for ICPS Network took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-icps took 4.140043020248413s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 8.654594421386719e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.26741552352905273s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.02217268943786621s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0008542537689208984s
Believability | Calculation of trust value for Infectious Disease Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-ido took 4.183838844299316s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 0.0001239776611328125s
Availability | VoID file availability check for Brucellosis Ontology took 0.0007073879241943359s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.2730844020843506s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.021137237548828125s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0011305809020996094s
Believability | Calculation of trust value for Brucellosis Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-idobru took 3.961982011795044s
Availability | SPARQL endpoint availability check for Malaria Ontology took 9.107589721679688e-05s
Availability | VoID file availability check for Malaria Ontology took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.2655973434448242s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.020523548126220703s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.0012969970703125s
Believability | Calculation of trust value for Malaria Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-idomal took 4.216033697128296s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 4.315376281738281e-05s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 0.30023837089538574s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.022132158279418945s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.00030159950256347656s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-iev took 4.132796287536621s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 4.7206878662109375e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.0007638931274414062s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.26354217529296875s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.021179676055908203s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.00015497207641601562s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-imgt took 5.893756628036499s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 4.506111145019531e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.0006985664367675781s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.26360464096069336s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.020091533660888672s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0005145072937011719s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-imr took 4.129652500152588s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 4.506111145019531e-05s
Availability | VoID file availability check for Interaction Network Ontology took 0.0006456375122070312s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.2661130428314209s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.02198481559753418s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0007793903350830078s
Believability | Calculation of trust value for Interaction Network Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ino took 4.173561096191406s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 0.00013017654418945312s
Availability | VoID file availability check for Hewan Invertebrata took 0.0008318424224853516s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.2619764804840088s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.020691394805908203s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 3.2901763916015625e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-invertebrata took 4.2377073764801025s
Availability | SPARQL endpoint availability check for IxnO took 8.726119995117188e-05s
Availability | VoID file availability check for IxnO took 0.0006861686706542969s
Completeness | Calculation of interlinking completeness for IxnO took 0.2664177417755127s
Reputation | Calculation of the PageRank for IxnO took 0.021570920944213867s
Interlinking | Calculation of Degree of Connection for IxnO took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for IxnO took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.00018596649169921875s
Believability | Calculation of trust value for IxnO took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-ixno took 3.986002206802368s
Availability | SPARQL endpoint availability check for SysMO-JERM took 9.202957153320312e-05s
Availability | VoID file availability check for SysMO-JERM took 0.0006542205810546875s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 0.2835688591003418s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.0221405029296875s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.00037288665771484375s
Believability | Calculation of trust value for SysMO-JERM took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-jerm took 4.041773319244385s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 8.678436279296875e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.0006358623504638672s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.26438021659851074s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.021882057189941406s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 3.6716461181640625e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-kisao took 3.9346508979797363s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 4.553794860839844e-05s
Availability | VoID file availability check for Loggerhead nesting took 0.0006754398345947266s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.2645559310913086s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.020974159240722656s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.00019812583923339844s
Believability | Calculation of trust value for Loggerhead nesting took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-lhn took 3.9527792930603027s
Availability | SPARQL endpoint availability check for Lipid Ontology took 0.00010824203491210938s
Availability | VoID file availability check for Lipid Ontology took 0.0006227493286132812s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 0.26166462898254395s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.020548343658447266s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.0002002716064453125s
Believability | Calculation of trust value for Lipid Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-lipro took 4.141881465911865s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 8.559226989746094e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.0006847381591796875s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.31371021270751953s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.021627187728881836s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.0018634796142578125s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-lnc took 5.107524156570435s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 8.988380432128906e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.0006301403045654297s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 0.2622411251068115s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.020494699478149414s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0006842613220214844s
Believability | Calculation of trust value for Mouse adult gross anatomy took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-ma took 4.423709392547607s
Availability | SPARQL endpoint availability check for Multiple alignment took 8.58306884765625e-05s
Availability | VoID file availability check for Multiple alignment took 0.0006415843963623047s
Completeness | Calculation of interlinking completeness for Multiple alignment took 0.2689194679260254s
Reputation | Calculation of the PageRank for Multiple alignment took 0.02053356170654297s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.0002009868621826172s
Believability | Calculation of trust value for Multiple alignment took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-mao took 3.963381767272949s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 9.179115295410156e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 0.0006830692291259766s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 0.2662513256072998s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.021880388259887695s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0006914138793945312s
Believability | Calculation of trust value for Minimal anatomical terminology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-mat took 4.011566638946533s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 8.7738037109375e-05s
Availability | VoID file availability check for Breast tissue cell lines took 0.0006725788116455078s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.2753727436065674s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.020403146743774414s
Interlinking | Calculation of Degree of Connection for Breast tissue cell lines took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Breast tissue cell lines took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.00042438507080078125s
Believability | Calculation of trust value for Breast tissue cell lines took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mcbcc took 4.037694692611694s
Availability | SPARQL endpoint availability check for Cell line ontology took 8.726119995117188e-05s
Availability | VoID file availability check for Cell line ontology took 0.0006864070892333984s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.2664470672607422s
Reputation | Calculation of the PageRank for Cell line ontology took 0.022133588790893555s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0007448196411132812s
Believability | Calculation of trust value for Cell line ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-mccl took 4.273441314697266s
Availability | SPARQL endpoint availability check for Cell line ontology took 9.012222290039062e-05s
Availability | VoID file availability check for Cell line ontology took 0.0006899833679199219s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.2658839225769043s
Reputation | Calculation of the PageRank for Cell line ontology took 0.021095991134643555s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0014367103576660156s
Believability | Calculation of trust value for Cell line ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-mccl_x1 took 4.268195390701294s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 5.8650970458984375e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.0006926059722900391s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.26299452781677246s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.021730422973632812s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.0002338886260986328s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mcv took 4.041466474533081s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 9.012222290039062e-05s
Availability | VoID file availability check for Master Drug Data Base took 0.0007269382476806641s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 0.2679727077484131s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.020260095596313477s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.0001709461212158203s
Believability | Calculation of trust value for Master Drug Data Base took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mddb took 4.033296585083008s
Availability | SPARQL endpoint availability check for MedDRA took 9.131431579589844e-05s
Availability | VoID file availability check for MedDRA took 0.0006837844848632812s
Completeness | Calculation of interlinking completeness for MedDRA took 0.2701537609100342s
Reputation | Calculation of the PageRank for MedDRA took 0.020606040954589844s
Interlinking | Calculation of Degree of Connection for MedDRA took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for MedDRA took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.001218557357788086s
Believability | Calculation of trust value for MedDRA took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-mdr took 4.151437520980835s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 4.2438507080078125e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.0006952285766601562s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.2654271125793457s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.02034139633178711s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0008866786956787109s
Believability | Calculation of trust value for MedlinePlus Health Topics took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-medlineplus took 3.8958332538604736s
Availability | SPARQL endpoint availability check for MeGO took 9.226799011230469e-05s
Availability | VoID file availability check for MeGO took 0.0007951259613037109s
Completeness | Calculation of interlinking completeness for MeGO took 0.2636244297027588s
Reputation | Calculation of the PageRank for MeGO took 0.02032637596130371s
Interlinking | Calculation of Degree of Connection for MeGO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MeGO took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.00014281272888183594s
Believability | Calculation of trust value for MeGO took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-mego took 4.2328197956085205s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 8.96453857421875e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 0.0007226467132568359s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 0.31278038024902344s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.021817684173583984s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.0018243789672851562s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mesh-owl took 4.375586271286011s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 0.0006062984466552734s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 0.26337575912475586s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.020206689834594727s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0006425380706787109s
Believability | Calculation of trust value for Mental Functioning Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-mf took 3.9877212047576904s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 4.1961669921875e-05s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 0.2638559341430664s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.02230668067932129s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0005686283111572266s
Believability | Calculation of trust value for Medaka fish anatomy and development took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-mfo took 4.0122668743133545s
Availability | SPARQL endpoint availability check for Emotion Ontology took 8.606910705566406e-05s
Availability | VoID file availability check for Emotion Ontology took 0.0006563663482666016s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 0.2670896053314209s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.02151012420654297s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0007612705230712891s
Believability | Calculation of trust value for Emotion Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-mfoem took 3.7469351291656494s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.0006878376007080078s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.2694284915924072s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.020475387573242188s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.00010347366333007812s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-mhc took 4.016896486282349s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 8.368492126464844e-05s
Availability | VoID file availability check for Protein-protein interaction took 0.0007159709930419922s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.2657020092010498s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.020457983016967773s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0006763935089111328s
Believability | Calculation of trust value for Protein-protein interaction took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-mi took 4.058188438415527s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 4.076957702636719e-05s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.0005631446838378906s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.25992298126220703s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.020430564880371094s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0007655620574951172s
Believability | Calculation of trust value for Mosquito insecticide resistance took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-miro took 4.064600944519043s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 8.654594421386719e-05s
Availability | VoID file availability check for Measurement Method Ontology took 0.0005810260772705078s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.2677009105682373s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.020566940307617188s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.00013518333435058594s
Believability | Calculation of trust value for Measurement Method Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-mmo took 3.992246627807617s
Availability | SPARQL endpoint availability check for MGED Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for MGED Ontology took 0.0006072521209716797s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.27005553245544434s
Reputation | Calculation of the PageRank for MGED Ontology took 0.021030187606811523s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.00037550926208496094s
Believability | Calculation of trust value for MGED Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-mo took 4.064294099807739s
Availability | SPARQL endpoint availability check for Protein modification took 4.3392181396484375e-05s
Availability | VoID file availability check for Protein modification took 0.0007131099700927734s
Completeness | Calculation of interlinking completeness for Protein modification took 0.27156543731689453s
Reputation | Calculation of the PageRank for Protein modification took 0.021518707275390625s
Interlinking | Calculation of Degree of Connection for Protein modification took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Protein modification took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.00021767616271972656s
Believability | Calculation of trust value for Protein modification took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-mod took 4.060949325561523s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 4.315376281738281e-05s
Availability | VoID file availability check for Mammalian phenotype took 0.0006151199340820312s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 0.2704181671142578s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.0201113224029541s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0006866455078125s
Believability | Calculation of trust value for Mammalian phenotype took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-mp took 4.082554817199707s
Availability | SPARQL endpoint availability check for Mouse pathology took 4.1484832763671875e-05s
Availability | VoID file availability check for Mouse pathology took 0.000583648681640625s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.26486849784851074s
Reputation | Calculation of the PageRank for Mouse pathology took 0.0207521915435791s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.00047087669372558594s
Believability | Calculation of trust value for Mouse pathology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-mpath took 4.174945116043091s
Availability | SPARQL endpoint availability check for Mass spectrometry took 4.792213439941406e-05s
Availability | VoID file availability check for Mass spectrometry took 0.0006089210510253906s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.2680635452270508s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.020412445068359375s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.000354766845703125s
Believability | Calculation of trust value for Mass spectrometry took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ms took 4.174688100814819s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 4.315376281738281e-05s
Availability | VoID file availability check for Medical Subject Headings took 0.0009281635284423828s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.311969518661499s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.021601438522338867s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.0018978118896484375s
Believability | Calculation of trust value for Medical Subject Headings took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-msh took 4.740109920501709s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 5.340576171875e-05s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 0.0006003379821777344s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.2624626159667969s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.020603418350219727s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.00018286705017089844s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-mthch took 3.8683876991271973s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 8.678436279296875e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.0006432533264160156s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 0.3026559352874756s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.020340919494628906s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0007839202880859375s
Believability | Calculation of trust value for Natural Products Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-natpro took 4.157987356185913s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 4.124641418457031e-05s
Availability | VoID file availability check for NCBI organismal classification took 0.0005781650543212891s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.26653265953063965s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.022072315216064453s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0008065700531005859s
Believability | Calculation of trust value for NCBI organismal classification took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-ncbitaxon took 4.066042184829712s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 4.38690185546875e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0007348060607910156s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.31342434883117676s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.020632505416870117s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.0020537376403808594s
Believability | Calculation of trust value for NCI Thesaurus took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ncit took 4.35564398765564s
Availability | SPARQL endpoint availability check for National Drug Data File took 8.988380432128906e-05s
Availability | VoID file availability check for National Drug Data File took 0.0007550716400146484s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.266679048538208s
Reputation | Calculation of the PageRank for National Drug Data File took 0.02112603187561035s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for National Drug Data File took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0006184577941894531s
Believability | Calculation of trust value for National Drug Data File took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-nddf took 4.20168399810791s
Availability | SPARQL endpoint availability check for National Drug File took 8.559226989746094e-05s
Availability | VoID file availability check for National Drug File took 0.0007452964782714844s
Completeness | Calculation of interlinking completeness for National Drug File took 0.2651023864746094s
Reputation | Calculation of the PageRank for National Drug File took 0.021811485290527344s
Interlinking | Calculation of Degree of Connection for National Drug File took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for National Drug File took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.0012400150299072266s
Believability | Calculation of trust value for National Drug File took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ndfrt took 3.8747658729553223s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 4.1961669921875e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.0007038116455078125s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.2795898914337158s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.020198822021484375s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.0011525154113769531s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-nemo_x1 took 3.8470847606658936s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 8.392333984375e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.26299262046813965s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.020431995391845703s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer Ontology took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0006606578826904297s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-neomark took 4.23434853553772s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 0.26674842834472656s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.02034282684326172s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.00012159347534179688s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-neomarkontology took 4.222388744354248s
Availability | SPARQL endpoint availability check for NIFSTD took 8.893013000488281e-05s
Availability | VoID file availability check for NIFSTD took 0.0005772113800048828s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.31131410598754883s
Reputation | Calculation of the PageRank for NIFSTD took 0.021948814392089844s
Interlinking | Calculation of Degree of Connection for NIFSTD took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for NIFSTD took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.001894235610961914s
Believability | Calculation of trust value for NIFSTD took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-nif took 4.492494821548462s
Availability | SPARQL endpoint availability check for NIF Cell took 8.726119995117188e-05s
Availability | VoID file availability check for NIF Cell took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.2645843029022217s
Reputation | Calculation of the PageRank for NIF Cell took 0.020456314086914062s
Interlinking | Calculation of Degree of Connection for NIF Cell took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NIF Cell took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.0013668537139892578s
Believability | Calculation of trust value for NIF Cell took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-nif_cell took 4.031674385070801s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 4.076957702636719e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.0006730556488037109s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.26316404342651367s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.020566225051879883s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.0013885498046875s
Believability | Calculation of trust value for NIF Dysfunction took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-nif_dysfunction took 4.023826599121094s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.000675201416015625s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.26792168617248535s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.02044844627380371s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0005795955657958984s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-nigo took 4.1095805168151855s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 8.845329284667969e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 0.0006074905395507812s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.2632458209991455s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.020559310913085938s
Interlinking | Calculation of Degree of Connection for NMR-instrument specific component of metabolomics investigations took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for NMR-instrument specific component of metabolomics investigations took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0005447864532470703s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-nmr took 4.00100564956665s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 0.0005559921264648438s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.26610422134399414s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.020292043685913086s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.00010824203491210938s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-nonrctontology took 4.333092927932739s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 8.630752563476562e-05s
Availability | VoID file availability check for NanoParticle Ontology took 0.0005590915679931641s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.26515793800354004s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.02205634117126465s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.0011949539184570312s
Believability | Calculation of trust value for NanoParticle Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-npo took 3.883582830429077s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 8.845329284667969e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 0.0005877017974853516s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.26378440856933594s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.02036285400390625s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0007359981536865234s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-oae took 3.881117582321167s
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.0005669593811035156s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 0.2704918384552002s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.021132707595825195s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.001598358154296875s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-obi took 4.215878486633301s
Availability | SPARQL endpoint availability check for OBOE took 4.124641418457031e-05s
Availability | VoID file availability check for OBOE took 0.0005435943603515625s
Completeness | Calculation of interlinking completeness for OBOE took 0.3094792366027832s
Reputation | Calculation of the PageRank for OBOE took 0.02125859260559082s
Interlinking | Calculation of Degree of Connection for OBOE took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OBOE took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.00010943412780761719s
Believability | Calculation of trust value for OBOE took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-oboe took 4.042324542999268s
Availability | SPARQL endpoint availability check for OBOE SBC took 8.606910705566406e-05s
Availability | VoID file availability check for OBOE SBC took 0.0005953311920166016s
Completeness | Calculation of interlinking completeness for OBOE SBC took 0.2634241580963135s
Reputation | Calculation of the PageRank for OBOE SBC took 0.021693944931030273s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0007786750793457031s
Believability | Calculation of trust value for OBOE SBC took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-oboe-sbc took 3.959584951400757s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 4.267692565917969e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 0.0006372928619384766s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 0.2684037685394287s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.02050042152404785s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0005960464477539062s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-ocre took 4.063310623168945s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 0.00010824203491210938s
Availability | VoID file availability check for Ontology for disease genetic investigation took 0.0006461143493652344s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 0.26624250411987305s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.020880460739135742s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0008654594421386719s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-odgi took 3.8557283878326416s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 8.797645568847656e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 0.0006337165832519531s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 0.2665696144104004s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.020473718643188477s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0008776187896728516s
Believability | Calculation of trust value for Ontology for Genetic Interval took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-ogi took 4.4262285232543945s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 8.702278137207031e-05s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 0.0005393028259277344s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 0.2673037052154541s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.02043628692626953s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.00028634071350097656s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-ogmd took 3.8666322231292725s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 8.630752563476562e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 0.0006763935089111328s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.26988792419433594s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.02120065689086914s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0006759166717529297s
Believability | Calculation of trust value for Ontology for General Medical Science took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-ogms took 4.08503794670105s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 8.893013000488281e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.2675797939300537s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.020406723022460938s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.0011467933654785156s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-omim took 3.85943341255188s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 8.630752563476562e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 0.0006520748138427734s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.2686138153076172s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.02122187614440918s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.0003783702850341797s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-omit took 3.8460729122161865s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 9.059906005859375e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.0005714893341064453s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.2635045051574707s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.022018909454345703s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.0010929107666015625s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0007121562957763672s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-omrse took 2.384523391723633s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 4.172325134277344e-05s
Availability | VoID file availability check for Ontology of Data Mining took 0.0007519721984863281s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.2658042907714844s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.020363330841064453s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.0007755756378173828s
Believability | Calculation of trust value for Ontology of Data Mining took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ontodm took 4.286621570587158s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 4.2438507080078125e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 0.2758824825286865s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.020484447479248047s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.00024199485778808594s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-ontodt took 4.370273113250732s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 4.7206878662109375e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.0008146762847900391s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.26920247077941895s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.02023458480834961s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.0006136894226074219s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-ontoorpha took 3.9076931476593018s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 7.462501525878906e-05s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 0.0003857612609863281s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 0.2632637023925781s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.020223617553710938s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0009086132049560547s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-opl took 3.8570339679718018s
Availability | SPARQL endpoint availability check for Phenotypic quality took 4.124641418457031e-05s
Availability | VoID file availability check for Phenotypic quality took 0.0005896091461181641s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.26213908195495605s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.020311594009399414s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0008664131164550781s
Believability | Calculation of trust value for Phenotypic quality took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-pato took 4.004963159561157s
Availability | SPARQL endpoint availability check for Physician Data Query took 9.942054748535156e-05s
Availability | VoID file availability check for Physician Data Query took 0.0006701946258544922s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.2650585174560547s
Reputation | Calculation of the PageRank for Physician Data Query took 0.020509004592895508s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Physician Data Query took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0008091926574707031s
Believability | Calculation of trust value for Physician Data Query took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-pdq took 3.849743127822876s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 8.797645568847656e-05s
Availability | VoID file availability check for Pediatric Terminology took 0.0005910396575927734s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.2610156536102295s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.02032184600830078s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0007872581481933594s
Believability | Calculation of trust value for Pediatric Terminology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-pedterm took 3.993210792541504s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 8.845329284667969e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.0005600452423095703s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 0.2647085189819336s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.020257234573364258s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.00019168853759765625s
Believability | Calculation of trust value for Parasite Experiment Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-peo took 4.117089748382568s
Availability | SPARQL endpoint availability check for PHARE took 4.267692565917969e-05s
Availability | VoID file availability check for PHARE took 0.0003638267517089844s
Completeness | Calculation of interlinking completeness for PHARE took 0.25866031646728516s
Reputation | Calculation of the PageRank for PHARE took 0.020116806030273438s
Interlinking | Calculation of Degree of Connection for PHARE took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for PHARE took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006291866302490234s
Believability | Calculation of trust value for PHARE took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-phare took 3.9971096515655518s
Availability | SPARQL endpoint availability check for PKO_Re took 4.2438507080078125e-05s
Availability | VoID file availability check for PKO_Re took 0.0003769397735595703s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.26113104820251465s
Reputation | Calculation of the PageRank for PKO_Re took 0.020142793655395508s
Interlinking | Calculation of Degree of Connection for PKO_Re took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PKO_Re took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.00016236305236816406s
Believability | Calculation of trust value for PKO_Re took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-pko took 4.220367431640625s
Availability | SPARQL endpoint availability check for PMA 2010 took 7.843971252441406e-05s
Availability | VoID file availability check for PMA 2010 took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.26097702980041504s
Reputation | Calculation of the PageRank for PMA 2010 took 0.02020883560180664s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0009202957153320312s
Believability | Calculation of trust value for PMA 2010 took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-pma took 3.996525287628174s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 4.076957702636719e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.0003044605255126953s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.2595345973968506s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.02011704444885254s
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.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.00016236305236816406s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-pmr took 4.080198526382446s
Availability | SPARQL endpoint availability check for Plant Anatomy took 4.0531158447265625e-05s
Availability | VoID file availability check for Plant Anatomy took 0.0002989768981933594s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.25840163230895996s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.022134065628051758s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.00037741661071777344s
Believability | Calculation of trust value for Plant Anatomy took 3.814697265625e-06s
INFO | --- Analysis for bioportal-po took 4.05873966217041s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 4.220008850097656e-05s
Availability | VoID file availability check for Plant Growth and Development Stage took 0.00030684471130371094s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.26724696159362793s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.02226114273071289s
Interlinking | Calculation of Degree of Connection for Plant Growth and Development Stage took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Plant Growth and Development Stage took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 7.534027099609375e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-po_x1 took 4.179673910140991s
Availability | SPARQL endpoint availability check for Plant Ontology took 8.559226989746094e-05s
Availability | VoID file availability check for Plant Ontology took 0.00037980079650878906s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.26563382148742676s
Reputation | Calculation of the PageRank for Plant Ontology took 0.02237391471862793s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.0004401206970214844s
Believability | Calculation of trust value for Plant Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-po_x2 took 4.060817718505859s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 8.654594421386719e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.0004260540008544922s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.26323652267456055s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.020176410675048828s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0006847381591796875s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-pr took 4.00700306892395s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 4.267692565917969e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 0.0005891323089599609s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 0.26825642585754395s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.020456314086914062s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.0002503395080566406s
Believability | Calculation of trust value for Proteomics data and process provenance took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-propreo took 3.9037251472473145s
Availability | SPARQL endpoint availability check for Pathway ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Pathway ontology took 0.0006613731384277344s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.2616562843322754s
Reputation | Calculation of the PageRank for Pathway ontology took 0.02060675621032715s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Pathway ontology took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.00012183189392089844s
Believability | Calculation of trust value for Pathway ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-pw took 4.173477411270142s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.00045680999755859375s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.264117956161499s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.020967721939086914s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 3.123283386230469e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-qibo took 4.131854295730591s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 4.5299530029296875e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0004229545593261719s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.3366873264312744s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.020376205444335938s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0018146038055419922s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-rcd took 4.776033163070679s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 9.012222290039062e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 0.0006396770477294922s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.26041221618652344s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.020422697067260742s
Interlinking | Calculation of Degree of Connection for Randomized Controlled Trials (RCT) Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Randomized Controlled Trials (RCT) Ontology took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.0001266002655029297s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-rctontology took 3.919814109802246s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 8.916854858398438e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 0.0004405975341796875s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.26322245597839355s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.02003955841064453s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 9.369850158691406e-05s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-repo took 4.076178789138794s
Availability | SPARQL endpoint availability check for Physico-chemical process took 4.1484832763671875e-05s
Availability | VoID file availability check for Physico-chemical process took 0.0006923675537109375s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.2674875259399414s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.02056884765625s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.00019216537475585938s
Believability | Calculation of trust value for Physico-chemical process took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-rex took 4.509042024612427s
Availability | SPARQL endpoint availability check for RadLex took 8.7738037109375e-05s
Availability | VoID file availability check for RadLex took 0.0006926059722900391s
Completeness | Calculation of interlinking completeness for RadLex took 0.27388882637023926s
Reputation | Calculation of the PageRank for RadLex took 0.02190685272216797s
Interlinking | Calculation of Degree of Connection for RadLex took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for RadLex took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.0015187263488769531s
Believability | Calculation of trust value for RadLex took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-rid took 3.9770421981811523s
Availability | SPARQL endpoint availability check for RNA ontology took 4.172325134277344e-05s
Availability | VoID file availability check for RNA ontology took 0.0006620883941650391s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.2650001049041748s
Reputation | Calculation of the PageRank for RNA ontology took 0.020716190338134766s
Interlinking | Calculation of Degree of Connection for RNA ontology took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for RNA ontology took 0.0011377334594726562s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0006744861602783203s
Believability | Calculation of trust value for RNA ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-rnao took 4.116102457046509s
Availability | SPARQL endpoint availability check for Role Ontology took 8.273124694824219e-05s
Availability | VoID file availability check for Role Ontology took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for Role Ontology took 0.2645244598388672s
Reputation | Calculation of the PageRank for Role Ontology took 0.02077341079711914s
Interlinking | Calculation of Degree of Connection for Role Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Role Ontology took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.00018453598022460938s
Believability | Calculation of trust value for Role Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-roleo took 4.12824559211731s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 8.320808410644531e-05s
Availability | VoID file availability check for Rat Strain Ontology took 0.0006039142608642578s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.2650299072265625s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.020154714584350586s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.000171661376953125s
Believability | Calculation of trust value for Rat Strain Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-rs took 3.9247732162475586s
Availability | SPARQL endpoint availability check for RxNORM took 4.4345855712890625e-05s
Availability | VoID file availability check for RxNORM took 0.0006489753723144531s
Completeness | Calculation of interlinking completeness for RxNORM took 0.3119237422943115s
Reputation | Calculation of the PageRank for RxNORM took 0.021097898483276367s
Interlinking | Calculation of Degree of Connection for RxNORM took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for RxNORM took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0006060600280761719s
Believability | Calculation of trust value for RxNORM took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-rxnorm took 4.018672704696655s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 8.678436279296875e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.0008215904235839844s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.26273345947265625s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.020285367965698242s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.0010488033294677734s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-sao took 4.152288913726807s
Availability | SPARQL endpoint availability check for Systems Biology took 8.678436279296875e-05s
Availability | VoID file availability check for Systems Biology took 0.0006451606750488281s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.2643754482269287s
Reputation | Calculation of the PageRank for Systems Biology took 0.020256757736206055s
Interlinking | Calculation of Degree of Connection for Systems Biology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Systems Biology took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.0004458427429199219s
Believability | Calculation of trust value for Systems Biology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-sbo took 3.8213045597076416s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 9.942054748535156e-05s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.0006060600280761719s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.26543617248535156s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.020743608474731445s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.00010418891906738281s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-sbro took 4.1514153480529785s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 8.606910705566406e-05s
Availability | VoID file availability check for Sleep Domain Ontology took 0.0007832050323486328s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.2654249668121338s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.020601511001586914s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.0013301372528076172s
Believability | Calculation of trust value for Sleep Domain Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-sdo took 4.279186248779297s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 8.58306884765625e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.0006506443023681641s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.26659250259399414s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.021470308303833008s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.00033020973205566406s
Believability | Calculation of trust value for Sample processing and separation techniques took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-sep took 4.602189064025879s
Availability | SPARQL endpoint availability check for Student Health Record took 8.845329284667969e-05s
Availability | VoID file availability check for Student Health Record took 0.0008184909820556641s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.2655911445617676s
Reputation | Calculation of the PageRank for Student Health Record took 0.020571470260620117s
Interlinking | Calculation of Degree of Connection for Student Health Record took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Student Health Record took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.00045609474182128906s
Believability | Calculation of trust value for Student Health Record took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-shr took 4.222572326660156s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.0006949901580810547s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 0.2686023712158203s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.021970272064208984s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.0012621879577636719s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-sio took 5.049472808837891s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 8.7738037109375e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.0006937980651855469s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 0.2648005485534668s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.021494150161743164s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.0001952648162841797s
Believability | Calculation of trust value for Situation-Based Access Control took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-sitbac took 4.048067569732666s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 4.291534423828125e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.0007643699645996094s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.3130624294281006s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.020509719848632812s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.001958131790161133s
Believability | Calculation of trust value for SNOMED Clinical Terms took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-snomedct took 4.46981954574585s
Availability | SPARQL endpoint availability check for SNP-Ontology took 4.935264587402344e-05s
Availability | VoID file availability check for SNP-Ontology took 0.0006308555603027344s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.267625093460083s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.02063131332397461s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0006744861602783203s
Believability | Calculation of trust value for SNP-Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-snpo took 4.221754312515259s
Availability | SPARQL endpoint availability check for Sequence types and features took 8.749961853027344e-05s
Availability | VoID file availability check for Sequence types and features took 0.0006945133209228516s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.2793724536895752s
Reputation | Calculation of the PageRank for Sequence types and features took 0.020276546478271484s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Sequence types and features took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0005695819854736328s
Believability | Calculation of trust value for Sequence types and features took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-so_x1 took 4.220996856689453s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 8.511543273925781e-05s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 0.000606536865234375s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.30911970138549805s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.02173018455505371s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.0015676021575927734s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-sopharm took 4.436074256896973s
Availability | SPARQL endpoint availability check for SoyOntology took 6.365776062011719e-05s
Availability | VoID file availability check for SoyOntology took 0.0006270408630371094s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.2646059989929199s
Reputation | Calculation of the PageRank for SoyOntology took 0.020603418350219727s
Interlinking | Calculation of Degree of Connection for SoyOntology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SoyOntology took 0.0008082389831542969s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.00012636184692382812s
Believability | Calculation of trust value for SoyOntology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-soy took 3.8941993713378906s
Availability | SPARQL endpoint availability check for Spider Ontology took 0.00010991096496582031s
Availability | VoID file availability check for Spider Ontology took 0.0006811618804931641s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.2632112503051758s
Reputation | Calculation of the PageRank for Spider Ontology took 0.02022719383239746s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.0003161430358886719s
Believability | Calculation of trust value for Spider Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-spd took 4.382359504699707s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 8.606910705566406e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.0005710124969482422s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.2646059989929199s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.02055954933166504s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.0002789497375488281s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-spto took 5.753458499908447s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.0007767677307128906s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.26372241973876953s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.021067142486572266s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.00046372413635253906s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-sso took 4.460561990737915s
Availability | SPARQL endpoint availability check for Software Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Software Ontology took 0.0006833076477050781s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.26379966735839844s
Reputation | Calculation of the PageRank for Software Ontology took 0.020416736602783203s
Interlinking | Calculation of Degree of Connection for Software Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Software Ontology took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.0004131793975830078s
Believability | Calculation of trust value for Software Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-swo took 3.788121223449707s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 8.916854858398438e-05s
Availability | VoID file availability check for Tick gross anatomy took 0.0005733966827392578s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.2649857997894287s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.020790576934814453s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.00024247169494628906s
Believability | Calculation of trust value for Tick gross anatomy took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-tads took 3.907491683959961s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 8.893013000488281e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.26270294189453125s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.020572662353515625s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.000911712646484375s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-tao took 3.7910923957824707s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 8.678436279296875e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.0006148815155029297s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.2657918930053711s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.021143674850463867s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 9.226799011230469e-05s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-taxrank took 3.9774489402770996s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 8.535385131835938e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 0.0006570816040039062s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.26471614837646484s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.0208590030670166s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 8.177757263183594e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-teddy took 4.427494525909424s
Availability | SPARQL endpoint availability check for Time Event Ontology took 8.916854858398438e-05s
Availability | VoID file availability check for Time Event Ontology took 0.0007891654968261719s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.27127861976623535s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.02163219451904297s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0008144378662109375s
Believability | Calculation of trust value for Time Event Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-teo took 3.821568489074707s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 8.797645568847656e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 0.0007574558258056641s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.2658565044403076s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.020751476287841797s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.0004189014434814453s
Believability | Calculation of trust value for Mosquito gross anatomy took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-tgma took 4.079806804656982s
Availability | SPARQL endpoint availability check for thesaurus took 4.506111145019531e-05s
Availability | VoID file availability check for thesaurus took 0.0007357597351074219s
Completeness | Calculation of interlinking completeness for thesaurus took 0.26531410217285156s
Reputation | Calculation of the PageRank for thesaurus took 0.02194499969482422s
Interlinking | Calculation of Degree of Connection for thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for thesaurus took 0.0008153915405273438s
Interlinking | Calculation of Clustering coefficient for thesaurus took 7.271766662597656e-05s
Believability | Calculation of trust value for thesaurus took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-thesaurus took 4.183068513870239s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 0.00010704994201660156s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.0007717609405517578s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.265949010848999s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.021236658096313477s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.000985860824584961s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.0004181861877441406s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 4.320630788803101s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Translational Medicine Ontology took 0.0005817413330078125s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.2608664035797119s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.029815673828125s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0011031627655029297s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0011284351348876953s
Believability | Calculation of trust value for Translational Medicine Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-tmo took 3.854811906814575s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 8.749961853027344e-05s
Availability | VoID file availability check for Plant Trait Ontology took 0.0007393360137939453s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 0.2630453109741211s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.020498037338256836s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.00015306472778320312s
Believability | Calculation of trust value for Plant Trait Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-to took 4.058218479156494s
Availability | SPARQL endpoint availability check for TOK_Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for TOK_Ontology took 0.000583648681640625s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 0.2643101215362549s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.02028942108154297s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.00018024444580078125s
Believability | Calculation of trust value for TOK_Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-tok took 4.102918863296509s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 4.2438507080078125e-05s
Availability | VoID file availability check for Teleost taxonomy took 0.000698089599609375s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 0.26552796363830566s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.020538806915283203s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.00019097328186035156s
Believability | Calculation of trust value for Teleost taxonomy took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-tto took 3.9722683429718018s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Uber anatomy ontology took 0.0008840560913085938s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.2699313163757324s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.020488977432250977s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.001028299331665039s
Believability | Calculation of trust value for Uber anatomy ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-uberon took 5.311968803405762s
Availability | SPARQL endpoint availability check for Units Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Units Ontology took 0.0006840229034423828s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.2665274143218994s
Reputation | Calculation of the PageRank for Units Ontology took 0.020421981811523438s
Interlinking | Calculation of Degree of Connection for Units Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Units Ontology took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.00022125244140625s
Believability | Calculation of trust value for Units Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-unitsontology took 3.964221715927124s
Availability | SPARQL endpoint availability check for Units of measurement took 4.410743713378906e-05s
Availability | VoID file availability check for Units of measurement took 0.0004146099090576172s
Completeness | Calculation of interlinking completeness for Units of measurement took 0.25635576248168945s
Reputation | Calculation of the PageRank for Units of measurement took 0.020253896713256836s
Interlinking | Calculation of Degree of Connection for Units of measurement took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Units of measurement took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.00029277801513671875s
Believability | Calculation of trust value for Units of measurement took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-uo took 3.9925377368927s
Availability | SPARQL endpoint availability check for VANDF took 8.58306884765625e-05s
Availability | VoID file availability check for VANDF took 0.0005867481231689453s
Completeness | Calculation of interlinking completeness for VANDF took 0.26796865463256836s
Reputation | Calculation of the PageRank for VANDF took 0.021208524703979492s
Interlinking | Calculation of Degree of Connection for VANDF took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for VANDF took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0006840229034423828s
Believability | Calculation of trust value for VANDF took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-vandf took 3.9769492149353027s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.0005936622619628906s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 0.2714962959289551s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.02213883399963379s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.00042939186096191406s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-vao took 4.069045305252075s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 4.458427429199219e-05s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 0.0006566047668457031s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 0.26676368713378906s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.020520925521850586s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0006213188171386719s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-vhog took 3.9673919677734375s
Availability | SPARQL endpoint availability check for VIVO took 8.630752563476562e-05s
Availability | VoID file availability check for VIVO took 0.0007240772247314453s
Completeness | Calculation of interlinking completeness for VIVO took 0.26271533966064453s
Reputation | Calculation of the PageRank for VIVO took 0.02073049545288086s
Interlinking | Calculation of Degree of Connection for VIVO took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for VIVO took 0.0009872913360595703s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.0004239082336425781s
Believability | Calculation of trust value for VIVO took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-vivo took 4.217857599258423s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Vaccine Ontology took 0.0006566047668457031s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.2637672424316406s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.02063918113708496s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.0012390613555908203s
Believability | Calculation of trust value for Vaccine Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-vo took 3.9289727210998535s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 9.036064147949219e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.00063323974609375s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.26473236083984375s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.020880699157714844s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0009746551513671875s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.00026297569274902344s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-vt took 4.096160173416138s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 8.749961853027344e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 0.0007915496826171875s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.2638673782348633s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.020720958709716797s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.0005192756652832031s
Believability | Calculation of trust value for C. elegans gross anatomy took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-wbbt took 4.089449644088745s
Availability | SPARQL endpoint availability check for C. elegans development took 4.100799560546875e-05s
Availability | VoID file availability check for C. elegans development took 0.0005571842193603516s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.25896644592285156s
Reputation | Calculation of the PageRank for C. elegans development took 0.020441293716430664s
Interlinking | Calculation of Degree of Connection for C. elegans development took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for C. elegans development took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 4.506111145019531e-05s
Believability | Calculation of trust value for C. elegans development took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-wbls took 4.379492998123169s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 8.678436279296875e-05s
Availability | VoID file availability check for C. elegans phenotype took 0.0009007453918457031s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.36849427223205566s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.021638154983520508s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0008797645568847656s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 0.00010967254638671875s
Believability | Calculation of trust value for C. elegans phenotype took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-wbphenotype took 4.051175117492676s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 0.000156402587890625s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.0006313323974609375s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.26976442337036133s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.020874738693237305s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0010242462158203125s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0007388591766357422s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-who took 4.120761156082153s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 8.726119995117188e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 0.0006029605865478516s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.2654001712799072s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.020852088928222656s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.0006780624389648438s
Believability | Calculation of trust value for Xenopus anatomy and development took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-xao took 4.045789957046509s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 8.606910705566406e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.0006110668182373047s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.26358628273010254s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.02040719985961914s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.0002300739288330078s
Believability | Calculation of trust value for Experimental Conditions Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-xco took 3.991032123565674s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 8.654594421386719e-05s
Availability | VoID file availability check for Yeast phenotypes took 0.0006263256072998047s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 0.2667725086212158s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.020464658737182617s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.00026154518127441406s
Believability | Calculation of trust value for Yeast phenotypes took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ypo took 4.100377082824707s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 8.511543273925781e-05s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.0006453990936279297s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 0.27213525772094727s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.020267963409423828s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.0007569789886474609s
Believability | Calculation of trust value for Zebrafish anatomy and development took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-zfa took 4.441941738128662s
Availability | SPARQL endpoint availability check for Indian Terrorism Ontology (InTO) took 9.393692016601562e-05s
Availability | VoID file availability check for Indian Terrorism Ontology (InTO) took 0.0007734298706054688s
Completeness | Calculation of interlinking completeness for Indian Terrorism Ontology (InTO) took 0.26412320137023926s
Reputation | Calculation of the PageRank for Indian Terrorism Ontology (InTO) took 0.020587682723999023s
Interlinking | Calculation of Degree of Connection for Indian Terrorism Ontology (InTO) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Indian Terrorism Ontology (InTO) took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Indian Terrorism Ontology (InTO) took 3.1948089599609375e-05s
Believability | Calculation of trust value for Indian Terrorism Ontology (InTO) took 5.0067901611328125e-06s
INFO | --- Analysis for Bioportal_link took 3.3879024982452393s
Availability | SPARQL endpoint availability check for BioSamples RDF took 0.3467283248901367s
Availability | VoID file availability check for BioSamples RDF took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.2645111083984375s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.020406007766723633s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 3.170967102050781e-05s
Believability | Calculation of trust value for BioSamples RDF took 1.2159347534179688e-05s
INFO | --- Analysis for biosamples-rdf took 78.32451033592224s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 0.08095359802246094s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.0004534721374511719s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 0.27004575729370117s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.020283222198486328s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.00011110305786132812s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 1.2636184692382812e-05s
INFO | --- Analysis for bis-linked-data took 2.5063352584838867s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.00014090538024902344s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0006239414215087891s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.2677152156829834s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.02049541473388672s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.124641418457031e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 1.239776611328125e-05s
INFO | --- Analysis for bll-thesaurus took 3.4698126316070557s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 1.2593488693237305s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.0006296634674072266s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 0.27100229263305664s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.020516157150268555s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 6.532669067382812e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 1.2159347534179688e-05s
INFO | --- Analysis for bluk-bnb took 12.550439357757568s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.28861546516418457s
Availability | VoID file availability check for Thesaurus BNCF took 0.0007653236389160156s
Extra | Recovery of all triples for Thesaurus BNCF took 42.258113384246826s
Performance | Total latancy measurement for Thesaurus BNCF took 0.6039834022521973s
Amount of data | Number of triples check for Thesaurus BNCF took 0.6681773662567139s
Interoperability | New terms check for Thesaurus BNCF took 1.4845550060272217s
Versatility | Languages check for Thesaurus BNCF took 6.5356903076171875s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 0.8565630912780762s
Security | Check HTTPS for Thesaurus BNCF took 0.08793139457702637s
Interpretability | RDF structures check for Thesaurus BNCF took 0.10365533828735352s
Versatility | Serialization formats check for Thesaurus BNCF took 0.11289119720458984s
Availability | RDF dump link check for Thesaurus BNCF took 0.10105443000793457s
License | MR license check for Thesaurus BNCF took 0.1059122085571289s
License | HR license check for Thesaurus BNCF took 0.17800188064575195s
Amount of data | Number of property check for Thesaurus BNCF took 0.10233712196350098s
Understandability | Number of label check for Thesaurus BNCF took 0.24892044067382812s
Understandability | URI regex check for Thesaurus BNCF took 0.21428823471069336s
Understandability | Vocabs check for Thesaurus BNCF took 0.1063849925994873s
Verifiability | Authors check for Thesaurus BNCF took 0.10794949531555176s
Verifiability | Publishers check for Thesaurus BNCF took 0.10615277290344238s
Performance | Throughput check for Thesaurus BNCF took 10.572161674499512s
Amount of data | Check the number of entities for Thesaurus BNCF took 6.747245788574219e-05s
Verifiability | Contribs. check for Thesaurus BNCF took 0.10735082626342773s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.11077189445495605s
Interlinking | skos check for Thesaurus BNCF took 0.16865015029907227s
Interlinking | skos check for Thesaurus BNCF took 0.14029526710510254s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.10873222351074219s
Currency | Creation date check for Thesaurus BNCF took 0.22320556640625s
Currency | Modification date check for Thesaurus BNCF took 0.21863770484924316s
Rep.Conc. | URIs length for Thesaurus BNCF took 24.21874690055847s
Interoperability | New vocabularies check for Thesaurus BNCF took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.1105661392211914s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.10190439224243164s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.10958743095397949s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 11.443173170089722s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.4838981628417969s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 3.76303768157959s
Consistency | Disjoint class check for Thesaurus BNCF took 0.11392331123352051s
Consistency | Check Misplaced properties for Thesaurus BNCF took 0.8949885368347168s
Consistency | Misplaced classes for Thesaurus BNCF took 6.581195831298828s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 7.188585042953491s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.3954639434814453s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.1934216022491455s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.3317275047302246s
Security | Sign check for Thesaurus BNCF took 0.1237788200378418s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 21.11643362045288s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.35457324981689453s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.020587682723999023s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 7.224082946777344e-05s
Interoperability | Check the re-using of existing vocabs for Thesaurus BNCF took 3.5762786865234375e-06s
Believability | Calculation of trust value for Thesaurus BNCF took 1.239776611328125e-05s
INFO | --- Analysis for bncf-ns took 174.3770158290863s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7362453937530518s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0007641315460205078s
Extra | Recovery of all triples for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.6985929012298584s
Performance | Total latancy measurement for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.701080083847046s
Amount of data | Number of triples check for BPR ? Bibliography of the Italian Parliament and electoral studies took 6.436530351638794s
Interoperability | New terms check for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.045410394668579s
Versatility | Languages check for BPR ? Bibliography of the Italian Parliament and electoral studies took 58.19878387451172s
Interpretability | Number of blank nodes check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.3534815311431885s
Security | Check HTTPS for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.2702326774597168s
Interpretability | RDF structures check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.433089017868042s
Versatility | Serialization formats check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5486571788787842s
Availability | RDF dump link check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.515960693359375s
License | MR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.35742759704589844s
License | HR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 58.22501564025879s
Amount of data | Number of property check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.36129140853881836s
Understandability | Number of label check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.0314383506774902s
Understandability | URI regex check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6827802658081055s
Understandability | Vocabs check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5022954940795898s
Verifiability | Authors check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.33530426025390625s
Verifiability | Publishers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3342702388763428s
Performance | Throughput check for BPR ? Bibliography of the Italian Parliament and electoral studies took 11.362892389297485s
Amount of data | Check the number of entities for BPR ? Bibliography of the Italian Parliament and electoral studies took 6.771087646484375e-05s
Verifiability | Contribs. check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.342987060546875s
Interlinking | sameAs chians check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.37609124183654785s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3568449020385742s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.35840654373168945s
Timeliness | dataset update frequency check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.49662256240844727s
Currency | Creation date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7120707035064697s
Currency | Modification date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.34045910835266113s
Rep.Conc. | URIs length for BPR ? Bibliography of the Italian Parliament and electoral studies took 16.627689123153687s
Interoperability | New vocabularies check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3396883010864258s
Accuracy | Check Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.37400174140930176s
Accuracy | Check Inverse Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3628849983215332s
Accuracy | Check Empty annotation labels for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6928622722625732s
Accuracy | Check White space in annotation for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0306093692779541s
Accuracy | Check Datatype consistency for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.028604745864868164s
Consistency | Disjoint class check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3346233367919922s
Consistency | Check Misplaced properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 12.679104328155518s
Consistency | Misplaced classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.43191099166870117s
Consistency | Check Ontology hijacking for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.202759027481079s
Consistency | Check Invalid usage of undefined classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.5239050388336182s
Consistency | Check Invalid usage of undefined properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 14.037843227386475s
Conciseness | Check Extensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.03141641616821289s
Conciseness | Check Intensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3626556396484375s
Security | Sign check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3375532627105713s
Availability | Check URIs Dereferenciability for BPR ? Bibliography of the Italian Parliament and electoral studies took 23.153950691223145s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3288722038269043s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.02097630500793457s
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.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 5.435943603515625e-05s
Interoperability | Check the re-using of existing vocabs for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.430511474609375e-06s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.239776611328125e-05s
INFO | --- Analysis for bpr took 414.39486479759216s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 8.893013000488281e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.270768404006958s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.02075672149658203s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 7.009506225585938e-05s
Believability | Calculation of trust value for Brazilian Politicians took 8.344650268554688e-06s
INFO | --- Analysis for brazilian-politicians took 2.467833995819092s
Availability | SPARQL endpoint availability check for Bricklink took 1.4449381828308105s
Availability | VoID file availability check for Bricklink took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for Bricklink took 0.2655317783355713s
Reputation | Calculation of the PageRank for Bricklink took 0.020509719848632812s
Interlinking | Calculation of Degree of Connection for Bricklink took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bricklink took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Bricklink took 7.081031799316406e-05s
Believability | Calculation of trust value for Bricklink took 1.0967254638671875e-05s
INFO | --- Analysis for bricklink took 9.25618577003479s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.23003125190735s
Availability | VoID file availability check for British Museum Collection took 0.0007798671722412109s
Completeness | Calculation of interlinking completeness for British Museum Collection took 0.2664010524749756s
Reputation | Calculation of the PageRank for British Museum Collection took 0.02080559730529785s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for British Museum Collection took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 3.2901763916015625e-05s
Believability | Calculation of trust value for British Museum Collection took 1.0728836059570312e-05s
INFO | --- Analysis for british-museum-collection took 72.7616696357727s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 5.459785461425781e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.26697587966918945s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.02081894874572754s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 4.1961669921875e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 1.0967254638671875e-05s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 2.5446360111236572s
Availability | SPARQL endpoint availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.25520777702331543s
Availability | VoID file availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0005829334259033203s
Extra | Recovery of all triples for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 15.319626331329346s
Performance | Total latancy measurement for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.5766291618347168s
Amount of data | Number of triples check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.736668586730957s
Interoperability | New terms check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.8500590324401855s
Versatility | Languages check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 6.327040195465088s
Interpretability | Number of blank nodes check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.9461417198181152s
Interpretability | RDF structures check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11957144737243652s
Versatility | Serialization formats check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11920428276062012s
Availability | RDF dump link check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11466336250305176s
License | MR license check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11664938926696777s
License | HR license check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 22.37735652923584s
Amount of data | Number of property check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11565995216369629s
Understandability | Number of label check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.2599315643310547s
Understandability | URI regex check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.24354052543640137s
Understandability | Vocabs check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11885237693786621s
Verifiability | Authors check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.14281058311462402s
Verifiability | Publishers check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11613273620605469s
Performance | Throughput check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 10.46525764465332s
Amount of data | Check the number of entities for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 7.176399230957031e-05s
Verifiability | Contribs. check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.13229703903198242s
Interlinking | sameAs chians check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12708640098571777s
Interlinking | skos check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11432313919067383s
Interlinking | skos check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11406302452087402s
Timeliness | dataset update frequency check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1142892837524414s
Currency | Creation date check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.2599802017211914s
Currency | Modification date check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.24403667449951172s
Rep.Conc. | URIs length for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 10.985892057418823s
Interoperability | New vocabularies check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11568689346313477s
Accuracy | Check Functional Property for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11224007606506348s
Accuracy | Check Inverse Functional Property for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11295485496520996s
Accuracy | Check Empty annotation labels for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.154888391494751s
Accuracy | Check White space in annotation for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.245589017868042s
Accuracy | Check Datatype consistency for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 4.5709521770477295s
Consistency | Disjoint class check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11425018310546875s
Consistency | Check Misplaced properties for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.159043788909912s
Consistency | Check Ontology hijacking for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 5.242077589035034s
Consistency | Check Invalid usage of undefined classes for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.2766492366790771s
Consistency | Check Invalid usage of undefined properties for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 3.3792498111724854s
Conciseness | Check Extensional conciseness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.7087981700897217s
Security | Sign check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11264228820800781s
Availability | Check URIs Dereferenciability for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 3509.6136724948883s
Completeness | Calculation of interlinking completeness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.7254564762115479s
Reputation | Calculation of the PageRank for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.021628141403198242s
Interlinking | Calculation of Degree of Connection for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.2649765014648438e-05s
Interoperability | Check the re-using of existing vocabs for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.6689300537109375e-06s
Believability | Calculation of trust value for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.2636184692382812e-05s
INFO | --- Analysis for bulgarian_admissions_to_correctional_facilities took 3626.9347076416016s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 0.18601036071777344s
Availability | VoID file availability check for business.data.gov.uk took 0.0006201267242431641s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 0.2691471576690674s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.020366907119750977s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 5.054473876953125e-05s
Believability | Calculation of trust value for business.data.gov.uk took 1.049041748046875e-05s
INFO | --- Analysis for business-data-gov-uk took 2.7730698585510254s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 0.489412784576416s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.0005953311920166016s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 2.0361897945404053s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 1.3582217693328857s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 0.39830946922302246s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 1.634291648864746s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 44.20591926574707s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 0.2843508720397949s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.1717085838317871s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 0.4755377769470215s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 0.27308201789855957s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 0.26328086853027344s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 0.4161946773529053s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 20.677656173706055s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 0.30565500259399414s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 0.35302281379699707s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 0.549973726272583s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.26630711555480957s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 0.27349019050598145s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.2689518928527832s
Performance | Throughput check for Biblioteca Virtual Miguel de Cervantes took 11.919628858566284s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 7.081031799316406e-05s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 1.3638474941253662s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 0.2850937843322754s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.2795600891113281s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.2628955841064453s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 0.27600622177124023s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 0.5466618537902832s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 0.5502767562866211s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 2.9392826557159424s
Interoperability | New vocabularies check for Biblioteca Virtual Miguel de Cervantes took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Biblioteca Virtual Miguel de Cervantes took 0.2731201648712158s
Accuracy | Check Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.4115283489227295s
Accuracy | Check Inverse Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.43401288986206055s
Accuracy | Check Empty annotation labels for Biblioteca Virtual Miguel de Cervantes took 1.05588960647583s
Accuracy | Check White space in annotation for Biblioteca Virtual Miguel de Cervantes took 0.033612966537475586s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.02895665168762207s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 0.31028223037719727s
Consistency | Check Misplaced properties for Biblioteca Virtual Miguel de Cervantes took 1.3981924057006836s
Consistency | Misplaced classes for Biblioteca Virtual Miguel de Cervantes took 0.35593748092651367s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 2.1710026264190674s
Consistency | Check Invalid usage of undefined classes for Biblioteca Virtual Miguel de Cervantes took 1.2994663715362549s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 2.489794969558716s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.03229117393493652s
Conciseness | Check Intensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.2734341621398926s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 0.28310489654541016s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 1482.8185560703278s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 0.344287633895874s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.02111029624938965s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 3.314018249511719e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.0010564327239990234s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 6.127357482910156e-05s
Interoperability | Check the re-using of existing vocabs for Biblioteca Virtual Miguel de Cervantes took 2.1457672119140625e-06s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes took 7.867813110351562e-06s
INFO | --- Analysis for BVMC took 1614.4022347927094s
Availability | SPARQL endpoint availability check for cablegate took 1.3297691345214844s
Availability | VoID file availability check for cablegate took 0.0007941722869873047s
Completeness | Calculation of interlinking completeness for cablegate took 0.2645533084869385s
Reputation | Calculation of the PageRank for cablegate took 0.0205533504486084s
Interlinking | Calculation of Degree of Connection for cablegate took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for cablegate took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for cablegate took 6.842613220214844e-05s
Believability | Calculation of trust value for cablegate took 1.0728836059570312e-05s
INFO | --- Analysis for cablegate took 16.086876392364502s
Availability | SPARQL endpoint availability check for Calames took 0.00015997886657714844s
Availability | VoID file availability check for Calames took 0.0007979869842529297s
Completeness | Calculation of interlinking completeness for Calames took 0.2621169090270996s
Reputation | Calculation of the PageRank for Calames took 0.020507335662841797s
Interlinking | Calculation of Degree of Connection for Calames took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Calames took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Calames took 3.600120544433594e-05s
Believability | Calculation of trust value for Calames took 6.9141387939453125e-06s
INFO | --- Analysis for calames took 3.9576849937438965s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.3533930778503418s
Availability | VoID file availability check for CaLiGraph took 0.0005176067352294922s
Extra | Recovery of all triples for CaLiGraph took 1.34354567527771s
Performance | Total latancy measurement for CaLiGraph took 0.9508578777313232s
Amount of data | Number of triples check for CaLiGraph took 13.614102363586426s
Interoperability | New terms check for CaLiGraph took 1.8056480884552002s
Versatility | Languages check for CaLiGraph took 60.205852031707764s
Interpretability | Number of blank nodes check for CaLiGraph took 0.22814273834228516s
Security | Check HTTPS for CaLiGraph took 0.11152291297912598s
Interpretability | RDF structures check for CaLiGraph took 0.26317501068115234s
Versatility | Serialization formats check for CaLiGraph took 0.2885599136352539s
Availability | RDF dump link check for CaLiGraph took 0.23007822036743164s
License | MR license check for CaLiGraph took 0.3500995635986328s
License | HR license check for CaLiGraph took 60.26239848136902s
Amount of data | Number of property check for CaLiGraph took 0.22159337997436523s
Understandability | Number of label check for CaLiGraph took 3.643193483352661s
Understandability | URI regex check for CaLiGraph took 0.472423791885376s
Understandability | Vocabs check for CaLiGraph took 0.2567274570465088s
Verifiability | Authors check for CaLiGraph took 0.2227029800415039s
Verifiability | Publishers check for CaLiGraph took 0.21015143394470215s
Performance | Throughput check for CaLiGraph took 10.927435636520386s
Amount of data | Check the number of entities for CaLiGraph took 0.015436410903930664s
Verifiability | Contribs. check for CaLiGraph took 0.22170543670654297s
Interlinking | sameAs chians check for CaLiGraph took 0.6864461898803711s
Interlinking | skos check for CaLiGraph took 0.4163703918457031s
Interlinking | skos check for CaLiGraph took 0.18340563774108887s
Timeliness | dataset update frequency check for CaLiGraph took 0.25865840911865234s
Currency | Creation date check for CaLiGraph took 0.4853355884552002s
Currency | Modification date check for CaLiGraph took 0.42236852645874023s
Rep.Conc. | URIs length for CaLiGraph took 60.87741994857788s
Interoperability | New vocabularies check for CaLiGraph took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.21503663063049316s
Accuracy | Check Functional Property for CaLiGraph took 0.2719881534576416s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.2660977840423584s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.4969334602355957s
Accuracy | Check White space in annotation for CaLiGraph took 0.02593255043029785s
Accuracy | Check Datatype consistency for CaLiGraph took 0.049936532974243164s
Consistency | Disjoint class check for CaLiGraph took 0.21132588386535645s
Consistency | Check Misplaced properties for CaLiGraph took 60.76871967315674s
Consistency | Misplaced classes for CaLiGraph took 0.42397475242614746s
Consistency | Check Ontology hijacking for CaLiGraph took 1.9029805660247803s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.3041656017303467s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.56068730354309s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.03385734558105469s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.3884928226470947s
Security | Sign check for CaLiGraph took 0.4324324131011963s
Availability | Check URIs Dereferenciability for CaLiGraph took 9.455142259597778s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.4646294116973877s
Reputation | Calculation of the PageRank for CaLiGraph took 0.02099156379699707s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.52587890625e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 3.62396240234375e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.1920928955078125e-06s
Believability | Calculation of trust value for CaLiGraph took 1.1444091796875e-05s
INFO | --- Analysis for CaLiGraph took 1256.7040722370148s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.20716071128845215s
Availability | VoID file availability check for CaLiGraph took 0.0006160736083984375s
Extra | Recovery of all triples for CaLiGraph took 1.7120025157928467s
Performance | Total latancy measurement for CaLiGraph took 0.9312477111816406s
Amount of data | Number of triples check for CaLiGraph took 13.556275367736816s
Interoperability | New terms check for CaLiGraph took 1.7987332344055176s
Versatility | Languages check for CaLiGraph took 60.263312578201294s
Interpretability | Number of blank nodes check for CaLiGraph took 0.2070772647857666s
Security | Check HTTPS for CaLiGraph took 0.11140275001525879s
Interpretability | RDF structures check for CaLiGraph took 0.20957660675048828s
Versatility | Serialization formats check for CaLiGraph took 0.21704387664794922s
Availability | RDF dump link check for CaLiGraph took 0.20569419860839844s
License | MR license check for CaLiGraph took 0.23889684677124023s
License | HR license check for CaLiGraph took 60.23612308502197s
Amount of data | Number of property check for CaLiGraph took 0.21408510208129883s
Understandability | Number of label check for CaLiGraph took 3.2541050910949707s
Understandability | URI regex check for CaLiGraph took 0.41463565826416016s
Understandability | Vocabs check for CaLiGraph took 0.21130132675170898s
Verifiability | Authors check for CaLiGraph took 0.21210384368896484s
Verifiability | Publishers check for CaLiGraph took 0.20934152603149414s
Performance | Throughput check for CaLiGraph took 11.031403303146362s
Amount of data | Check the number of entities for CaLiGraph took 0.017265796661376953s
Verifiability | Contribs. check for CaLiGraph took 0.20810651779174805s
Interlinking | sameAs chians check for CaLiGraph took 0.6343469619750977s
Interlinking | skos check for CaLiGraph took 0.21379733085632324s
Interlinking | skos check for CaLiGraph took 0.18540573120117188s
Timeliness | dataset update frequency check for CaLiGraph took 0.2142186164855957s
Currency | Creation date check for CaLiGraph took 0.41927576065063477s
Currency | Modification date check for CaLiGraph took 0.4227793216705322s
Rep.Conc. | URIs length for CaLiGraph took 60.87568473815918s
Interoperability | New vocabularies check for CaLiGraph took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.21338295936584473s
Accuracy | Check Functional Property for CaLiGraph took 0.2073976993560791s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.2079770565032959s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.49403929710388184s
Accuracy | Check White space in annotation for CaLiGraph took 0.0260622501373291s
Accuracy | Check Datatype consistency for CaLiGraph took 0.04867386817932129s
Consistency | Disjoint class check for CaLiGraph took 0.2194526195526123s
Consistency | Check Misplaced properties for CaLiGraph took 60.728039264678955s
Consistency | Misplaced classes for CaLiGraph took 0.419327974319458s
Consistency | Check Ontology hijacking for CaLiGraph took 1.9073209762573242s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.304502248764038s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.552250385284424s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.029976367950439453s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.3891878128051758s
Security | Sign check for CaLiGraph took 0.2175769805908203s
Availability | Check URIs Dereferenciability for CaLiGraph took 9.99516224861145s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.35710930824279785s
Reputation | Calculation of the PageRank for CaLiGraph took 0.020251989364624023s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 0.00013589859008789062s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.6689300537109375e-06s
Believability | Calculation of trust value for CaLiGraph took 1.0013580322265625e-05s
INFO | --- Analysis for caligraph took 1653.1837813854218s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 0.05320906639099121s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.26323533058166504s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.0205080509185791s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 3.0517578125e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 1.0013580322265625e-05s
INFO | --- Analysis for cap-italy-rdf took 2.507838010787964s
Availability | SPARQL endpoint availability check for person took 4.267692565917969e-05s
Availability | VoID file availability check for person took 0.0004394054412841797s
Completeness | Calculation of interlinking completeness for person took 0.26470422744750977s
Reputation | Calculation of the PageRank for person took 0.02225041389465332s
Interlinking | Calculation of Degree of Connection for person took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for person took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for person took 3.0279159545898438e-05s
Believability | Calculation of trust value for person took 1.239776611328125e-05s
INFO | --- Analysis for card took 2.3956379890441895s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 4.220008850097656e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 0.000392913818359375s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 0.2604069709777832s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.02133488655090332s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 4.3392181396484375e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 1.2874603271484375e-05s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 2.880770444869995s
Availability | SPARQL endpoint availability check for Norway catch records dataset @PSNC took 60.0625433921814s
Availability | VoID file availability check for Norway catch records dataset @PSNC took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for Norway catch records dataset @PSNC took 0.2629716396331787s
Reputation | Calculation of the PageRank for Norway catch records dataset @PSNC took 0.020552396774291992s
Interlinking | Calculation of Degree of Connection for Norway catch records dataset @PSNC took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Norway catch records dataset @PSNC took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Norway catch records dataset @PSNC took 4.315376281738281e-05s
Believability | Calculation of trust value for Norway catch records dataset @PSNC took 6.9141387939453125e-06s
INFO | --- Analysis for Catch_Record_(2014-_2019) took 122.51347231864929s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 4.363059997558594e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0005393028259277344s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.2677006721496582s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.020862340927124023s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.00010418891906738281s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.049041748046875e-05s
INFO | --- Analysis for ce4r took 16.18923568725586s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4929032325744629s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.0002357959747314453s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 1.0138561725616455s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 1.0432837009429932s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.5029182434082031s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 1.671013355255127s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 58.14237070083618s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17749667167663574s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3530404567718506s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17350316047668457s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.19319415092468262s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2604348659515381s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3378322124481201s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.14468979835510254s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.28054332733154297s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.37758803367614746s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16185688972473145s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1899092197418213s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1962134838104248s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 10.856905221939087s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 7.390975952148438e-05s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.28294968605041504s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1587831974029541s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.6110587120056152s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.14159464836120605s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1572587490081787s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.7119553089141846s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4581918716430664s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 2.1073355674743652s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15398693084716797s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 0.590092658996582s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.028173208236694336s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.0278317928314209s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.395188570022583s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.2245979309082031s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 1.9044225215911865s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 1.2988626956939697s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.4812047481536865s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.03251194953918457s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.21670174598693848s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.14479374885559082s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 2828.896628141403s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 0.4880952835083008s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.02142930030822754s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 4.887580871582031e-05s
Interoperability | Check the re-using of existing vocabs for Linked Data Cultural Heritage Agency of the Netherlands took 1.430511474609375e-06s
Believability | Calculation of trust value for Linked Data Cultural Heritage Agency of the Netherlands took 1.7642974853515625e-05s
INFO | --- Analysis for ceo took 2951.783697128296s
Availability | SPARQL endpoint availability check for Chat Game corpus took 6.341934204101562e-05s
Availability | VoID file availability check for Chat Game corpus took 0.0007646083831787109s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 0.26723146438598633s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.02069997787475586s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 3.62396240234375e-05s
Believability | Calculation of trust value for Chat Game corpus took 1.2636184692382812e-05s
INFO | --- Analysis for chat-game-corpus took 12.694555282592773s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 8.845329284667969e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.00072479248046875s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 0.2673771381378174s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.02050638198852539s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 5.53131103515625e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 6.151199340820312e-05s
INFO | --- Analysis for chem2bio2rdf took 132.80416202545166s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 0.4686472415924072s
Availability | VoID file availability check for ChEMBL RDF took 0.0004711151123046875s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.2620065212249756s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.020307540893554688s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 5.0067901611328125e-05s
Believability | Calculation of trust value for ChEMBL RDF took 1.1444091796875e-05s
INFO | --- Analysis for chembl-rdf took 3.4759907722473145s
Availability | SPARQL endpoint availability check for chemdb  dataset took 1.0195446014404297s
Availability | VoID file availability check for chemdb  dataset took 0.0005025863647460938s
Extra | Recovery of all triples for chemdb  dataset took 4.9405083656311035s
Performance | Total latancy measurement for chemdb  dataset took 2.4550609588623047s
Amount of data | Number of triples check for chemdb  dataset took 0.5472562313079834s
Interoperability | New terms check for chemdb  dataset took 3.390481948852539s
Versatility | Languages check for chemdb  dataset took 27.656152963638306s
Interpretability | Number of blank nodes check for chemdb  dataset took 0.5253207683563232s
Interpretability | RDF structures check for chemdb  dataset took 1.7838139533996582s
Versatility | Serialization formats check for chemdb  dataset took 1.47031831741333s
Availability | RDF dump link check for chemdb  dataset took 0.7714366912841797s
License | MR license check for chemdb  dataset took 2.6558547019958496s
License | HR license check for chemdb  dataset took 3.683049440383911s
Amount of data | Number of property check for chemdb  dataset took 0.5317683219909668s
Understandability | Number of label check for chemdb  dataset took 4.722643852233887s
Understandability | URI regex check for chemdb  dataset took 1.8042361736297607s
Understandability | Vocabs check for chemdb  dataset took 0.7627928256988525s
Verifiability | Authors check for chemdb  dataset took 1.0389938354492188s
Verifiability | Publishers check for chemdb  dataset took 0.7592782974243164s
Performance | Throughput check for chemdb  dataset took 14.226181507110596s
Amount of data | Check the number of entities for chemdb  dataset took 3.719329833984375e-05s
Verifiability | Contribs. check for chemdb  dataset took 0.7485675811767578s
Interlinking | sameAs chians check for chemdb  dataset took 1.0261309146881104s
Interlinking | skos check for chemdb  dataset took 1.9928557872772217s
Interlinking | skos check for chemdb  dataset took 0.4858887195587158s
Timeliness | dataset update frequency check for chemdb  dataset took 1.0449421405792236s
Currency | Creation date check for chemdb  dataset took 1.2885990142822266s
Currency | Modification date check for chemdb  dataset took 1.0033438205718994s
Rep.Conc. | URIs length for chemdb  dataset took 6.7091898918151855s
Interoperability | New vocabularies check for chemdb  dataset took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for chemdb  dataset took 0.5061843395233154s
Accuracy | Check Functional Property for chemdb  dataset took 0.7562820911407471s
Accuracy | Check Inverse Functional Property for chemdb  dataset took 0.7359602451324463s
Accuracy | Check Empty annotation labels for chemdb  dataset took 4.91548752784729s
Accuracy | Check White space in annotation for chemdb  dataset took 0.030347585678100586s
Accuracy | Check Datatype consistency for chemdb  dataset took 0.03248476982116699s
Consistency | Disjoint class check for chemdb  dataset took 0.7513511180877686s
Consistency | Check Misplaced properties for chemdb  dataset took 1.2189013957977295s
Consistency | Misplaced classes for chemdb  dataset took 0.6070358753204346s
Consistency | Check Ontology hijacking for chemdb  dataset took 5.656175374984741s
Consistency | Check Invalid usage of undefined classes for chemdb  dataset took 1.2445976734161377s
Consistency | Check Invalid usage of undefined properties for chemdb  dataset took 1.9401473999023438s
Conciseness | Check Extensional conciseness for chemdb  dataset took 0.031551361083984375s
Conciseness | Check Intensional conciseness for chemdb  dataset took 0.5147895812988281s
Security | Sign check for chemdb  dataset took 1.6117463111877441s
Availability | Check URIs Dereferenciability for chemdb  dataset took 2636.377894639969s
Completeness | Calculation of interlinking completeness for chemdb  dataset took 0.702582836151123s
Reputation | Calculation of the PageRank for chemdb  dataset took 0.0219728946685791s
Interlinking | Calculation of Degree of Connection for chemdb  dataset took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for chemdb  dataset took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for chemdb  dataset took 7.462501525878906e-05s
Interoperability | Check the re-using of existing vocabs for chemdb  dataset took 1.1920928955078125e-06s
Believability | Calculation of trust value for chemdb  dataset took 9.059906005859375e-06s
INFO | --- Analysis for chemdb-basicInfo took 4616.396949529648s
Availability | SPARQL endpoint availability check for chemdb estimated properties dataset took 0.5161826610565186s
Availability | VoID file availability check for chemdb estimated properties dataset took 0.0005733966827392578s
Extra | Recovery of all triples for chemdb estimated properties dataset took 13.18671202659607s
Performance | Total latancy measurement for chemdb estimated properties dataset took 2.457106590270996s
Amount of data | Number of triples check for chemdb estimated properties dataset took 0.533292293548584s
Interoperability | New terms check for chemdb estimated properties dataset took 3.8797919750213623s
Versatility | Languages check for chemdb estimated properties dataset took 25.986034870147705s
Interpretability | Number of blank nodes check for chemdb estimated properties dataset took 0.5150434970855713s
Interpretability | RDF structures check for chemdb estimated properties dataset took 0.5159695148468018s
Versatility | Serialization formats check for chemdb estimated properties dataset took 1.3541221618652344s
Availability | RDF dump link check for chemdb estimated properties dataset took 0.774193525314331s
License | MR license check for chemdb estimated properties dataset took 2.8221874237060547s
License | HR license check for chemdb estimated properties dataset took 3.786073684692383s
Amount of data | Number of property check for chemdb estimated properties dataset took 0.5094497203826904s
Understandability | Number of label check for chemdb estimated properties dataset took 4.79996395111084s
Understandability | URI regex check for chemdb estimated properties dataset took 1.8795981407165527s
Understandability | Vocabs check for chemdb estimated properties dataset took 0.7923109531402588s
Verifiability | Authors check for chemdb estimated properties dataset took 1.1024768352508545s
Verifiability | Publishers check for chemdb estimated properties dataset took 0.7668325901031494s
Performance | Throughput check for chemdb estimated properties dataset took 15.153936386108398s
Amount of data | Check the number of entities for chemdb estimated properties dataset took 7.271766662597656e-05s
Verifiability | Contribs. check for chemdb estimated properties dataset took 0.7671301364898682s
Interlinking | sameAs chians check for chemdb estimated properties dataset took 1.0655062198638916s
Interlinking | skos check for chemdb estimated properties dataset took 1.8365459442138672s
Interlinking | skos check for chemdb estimated properties dataset took 0.49576735496520996s
Timeliness | dataset update frequency check for chemdb estimated properties dataset took 1.0489985942840576s
Currency | Creation date check for chemdb estimated properties dataset took 1.295130729675293s
Currency | Modification date check for chemdb estimated properties dataset took 0.9999701976776123s
Rep.Conc. | URIs length for chemdb estimated properties dataset took 3.3668787479400635s
Interoperability | New vocabularies check for chemdb estimated properties dataset took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for chemdb estimated properties dataset took 0.49456000328063965s
Accuracy | Check Functional Property for chemdb estimated properties dataset took 0.7672016620635986s
Accuracy | Check Inverse Functional Property for chemdb estimated properties dataset took 0.7685372829437256s
Accuracy | Check Empty annotation labels for chemdb estimated properties dataset took 3.1939496994018555s
Accuracy | Check White space in annotation for chemdb estimated properties dataset took 0.029886484146118164s
Accuracy | Check Datatype consistency for chemdb estimated properties dataset took 0.033233642578125s
Consistency | Disjoint class check for chemdb estimated properties dataset took 0.7711448669433594s
Consistency | Check Misplaced properties for chemdb estimated properties dataset took 1.2080967426300049s
Consistency | Misplaced classes for chemdb estimated properties dataset took 0.5906658172607422s
Consistency | Check Ontology hijacking for chemdb estimated properties dataset took 3.8477983474731445s
Consistency | Check Invalid usage of undefined classes for chemdb estimated properties dataset took 1.2490029335021973s
Consistency | Check Invalid usage of undefined properties for chemdb estimated properties dataset took 1.9446015357971191s
Conciseness | Check Extensional conciseness for chemdb estimated properties dataset took 0.03243899345397949s
Conciseness | Check Intensional conciseness for chemdb estimated properties dataset took 0.5168781280517578s
Security | Sign check for chemdb estimated properties dataset took 1.6870207786560059s
Availability | Check URIs Dereferenciability for chemdb estimated properties dataset took 2620.060063123703s
Completeness | Calculation of interlinking completeness for chemdb estimated properties dataset took 0.7054369449615479s
Reputation | Calculation of the PageRank for chemdb estimated properties dataset took 0.02107524871826172s
Interlinking | Calculation of Degree of Connection for chemdb estimated properties dataset took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for chemdb estimated properties dataset took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for chemdb estimated properties dataset took 4.506111145019531e-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 9.298324584960938e-06s
INFO | --- Analysis for chemdb-estimatedProperties took 4601.754190206528s
Availability | SPARQL endpoint availability check for chemdb phase transition dataset took 0.5157620906829834s
Availability | VoID file availability check for chemdb phase transition dataset took 0.0004925727844238281s
Extra | Recovery of all triples for chemdb phase transition dataset took 9.07514476776123s
Performance | Total latancy measurement for chemdb phase transition dataset took 2.4695444107055664s
Amount of data | Number of triples check for chemdb phase transition dataset took 0.5320451259613037s
Interoperability | New terms check for chemdb phase transition dataset took 3.835374116897583s
Versatility | Languages check for chemdb phase transition dataset took 26.03970694541931s
Interpretability | Number of blank nodes check for chemdb phase transition dataset took 0.523076057434082s
Interpretability | RDF structures check for chemdb phase transition dataset took 0.5105657577514648s
Versatility | Serialization formats check for chemdb phase transition dataset took 1.4049890041351318s
Availability | RDF dump link check for chemdb phase transition dataset took 0.8065669536590576s
License | MR license check for chemdb phase transition dataset took 2.6713316440582275s
License | HR license check for chemdb phase transition dataset took 3.9748501777648926s
Amount of data | Number of property check for chemdb phase transition dataset took 0.509552001953125s
Understandability | Number of label check for chemdb phase transition dataset took 4.802188158035278s
Understandability | URI regex check for chemdb phase transition dataset took 1.881917953491211s
Understandability | Vocabs check for chemdb phase transition dataset took 0.7962808609008789s
Verifiability | Authors check for chemdb phase transition dataset took 1.092320442199707s
Verifiability | Publishers check for chemdb phase transition dataset took 0.7966177463531494s
Performance | Throughput check for chemdb phase transition dataset took 14.12937593460083s
Amount of data | Check the number of entities for chemdb phase transition dataset took 0.00011563301086425781s
Verifiability | Contribs. check for chemdb phase transition dataset took 0.8174018859863281s
Interlinking | sameAs chians check for chemdb phase transition dataset took 1.106860876083374s
Interlinking | skos check for chemdb phase transition dataset took 1.9734957218170166s
Interlinking | skos check for chemdb phase transition dataset took 0.49543333053588867s
Timeliness | dataset update frequency check for chemdb phase transition dataset took 1.0706310272216797s
Currency | Creation date check for chemdb phase transition dataset took 1.29844069480896s
Currency | Modification date check for chemdb phase transition dataset took 1.0030467510223389s
Rep.Conc. | URIs length for chemdb phase transition dataset took 3.3656656742095947s
Interoperability | New vocabularies check for chemdb phase transition dataset took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for chemdb phase transition dataset took 0.48171353340148926s
Accuracy | Check Functional Property for chemdb phase transition dataset took 0.7632367610931396s
Accuracy | Check Inverse Functional Property for chemdb phase transition dataset took 0.7498767375946045s
Accuracy | Check Empty annotation labels for chemdb phase transition dataset took 2.837575912475586s
Accuracy | Check White space in annotation for chemdb phase transition dataset took 0.03022599220275879s
Accuracy | Check Datatype consistency for chemdb phase transition dataset took 0.03266429901123047s
Consistency | Disjoint class check for chemdb phase transition dataset took 0.7815215587615967s
Consistency | Check Misplaced properties for chemdb phase transition dataset took 1.2171788215637207s
Consistency | Misplaced classes for chemdb phase transition dataset took 0.6038358211517334s
Consistency | Check Ontology hijacking for chemdb phase transition dataset took 3.839815378189087s
Consistency | Check Invalid usage of undefined classes for chemdb phase transition dataset took 1.2668898105621338s
Consistency | Check Invalid usage of undefined properties for chemdb phase transition dataset took 1.9386658668518066s
Conciseness | Check Extensional conciseness for chemdb phase transition dataset took 0.032308101654052734s
Conciseness | Check Intensional conciseness for chemdb phase transition dataset took 0.5229454040527344s
Security | Sign check for chemdb phase transition dataset took 1.7940309047698975s
Availability | Check URIs Dereferenciability for chemdb phase transition dataset took 2614.5667340755463s
Completeness | Calculation of interlinking completeness for chemdb phase transition dataset took 0.7737371921539307s
Reputation | Calculation of the PageRank for chemdb phase transition dataset took 0.021342992782592773s
Interlinking | Calculation of Degree of Connection for chemdb phase transition dataset took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for chemdb phase transition dataset took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for chemdb phase transition dataset took 4.7206878662109375e-05s
Interoperability | Check the re-using of existing vocabs for chemdb phase transition dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for chemdb phase transition dataset took 1.1205673217773438e-05s
INFO | --- Analysis for chemdb-phaseTransition took 4599.5541162490845s
Availability | SPARQL endpoint availability check for chemdb thermochemistry dataset took 0.5180540084838867s
Availability | VoID file availability check for chemdb thermochemistry dataset took 0.0005052089691162109s
Extra | Recovery of all triples for chemdb thermochemistry dataset took 9.032737731933594s
Performance | Total latancy measurement for chemdb thermochemistry dataset took 2.458559036254883s
Amount of data | Number of triples check for chemdb thermochemistry dataset took 0.5323944091796875s
Interoperability | New terms check for chemdb thermochemistry dataset took 3.8482210636138916s
Versatility | Languages check for chemdb thermochemistry dataset took 27.487672328948975s
Interpretability | Number of blank nodes check for chemdb thermochemistry dataset took 0.5171406269073486s
Interpretability | RDF structures check for chemdb thermochemistry dataset took 0.5245518684387207s
Versatility | Serialization formats check for chemdb thermochemistry dataset took 1.4497976303100586s
Availability | RDF dump link check for chemdb thermochemistry dataset took 0.8272762298583984s
License | MR license check for chemdb thermochemistry dataset took 3.098027467727661s
License | HR license check for chemdb thermochemistry dataset took 4.118878364562988s
Amount of data | Number of property check for chemdb thermochemistry dataset took 0.5228145122528076s
Understandability | Number of label check for chemdb thermochemistry dataset took 5.409484624862671s
Understandability | URI regex check for chemdb thermochemistry dataset took 1.9527690410614014s
Understandability | Vocabs check for chemdb thermochemistry dataset took 0.8022029399871826s
Verifiability | Authors check for chemdb thermochemistry dataset took 1.1138396263122559s
Verifiability | Publishers check for chemdb thermochemistry dataset took 0.8006150722503662s
Performance | Throughput check for chemdb thermochemistry dataset took 14.613327026367188s
Amount of data | Check the number of entities for chemdb thermochemistry dataset took 7.700920104980469e-05s
Verifiability | Contribs. check for chemdb thermochemistry dataset took 0.8150079250335693s
Interlinking | sameAs chians check for chemdb thermochemistry dataset took 1.125563383102417s
Interlinking | skos check for chemdb thermochemistry dataset took 2.001464366912842s
Interlinking | skos check for chemdb thermochemistry dataset took 0.5017416477203369s
Timeliness | dataset update frequency check for chemdb thermochemistry dataset took 1.1439805030822754s
Currency | Creation date check for chemdb thermochemistry dataset took 1.3224725723266602s
Currency | Modification date check for chemdb thermochemistry dataset took 1.0117394924163818s
Rep.Conc. | URIs length for chemdb thermochemistry dataset took 3.363743543624878s
Interoperability | New vocabularies check for chemdb thermochemistry dataset took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for chemdb thermochemistry dataset took 0.5010724067687988s
Accuracy | Check Functional Property for chemdb thermochemistry dataset took 0.7856130599975586s
Accuracy | Check Inverse Functional Property for chemdb thermochemistry dataset took 0.774409294128418s
Accuracy | Check Empty annotation labels for chemdb thermochemistry dataset took 2.840641975402832s
Accuracy | Check White space in annotation for chemdb thermochemistry dataset took 0.030011415481567383s
Accuracy | Check Datatype consistency for chemdb thermochemistry dataset took 0.033789873123168945s
Consistency | Disjoint class check for chemdb thermochemistry dataset took 0.8190069198608398s
Consistency | Check Misplaced properties for chemdb thermochemistry dataset took 1.2087721824645996s
Consistency | Misplaced classes for chemdb thermochemistry dataset took 0.5983180999755859s
Consistency | Check Ontology hijacking for chemdb thermochemistry dataset took 3.8967418670654297s
Consistency | Check Invalid usage of undefined classes for chemdb thermochemistry dataset took 1.2935335636138916s
Consistency | Check Invalid usage of undefined properties for chemdb thermochemistry dataset took 1.990056037902832s
Conciseness | Check Extensional conciseness for chemdb thermochemistry dataset took 0.03610873222351074s
Conciseness | Check Intensional conciseness for chemdb thermochemistry dataset took 0.5231971740722656s
Security | Sign check for chemdb thermochemistry dataset took 1.612701416015625s
Availability | Check URIs Dereferenciability for chemdb thermochemistry dataset took 2604.966380596161s
Completeness | Calculation of interlinking completeness for chemdb thermochemistry dataset took 0.7075090408325195s
Reputation | Calculation of the PageRank for chemdb thermochemistry dataset took 0.02116680145263672s
Interlinking | Calculation of Degree of Connection for chemdb thermochemistry dataset took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for chemdb thermochemistry dataset took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for chemdb thermochemistry dataset took 7.224082946777344e-05s
Interoperability | Check the re-using of existing vocabs for chemdb thermochemistry dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for chemdb thermochemistry dataset took 5.4836273193359375e-06s
INFO | --- Analysis for chemdb-thermochemistry took 4648.419382095337s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 9.012222290039062e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.0007719993591308594s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 0.2712099552154541s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.020801544189453125s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 3.2901763916015625e-05s
Believability | Calculation of trust value for ChemPedia RDF took 1.1920928955078125e-05s
INFO | --- Analysis for chempedia-rdf took 9.037562131881714s
Availability | SPARQL endpoint availability check for Chiman Maru took 8.440017700195312e-05s
Availability | VoID file availability check for Chiman Maru took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for Chiman Maru took 0.26107358932495117s
Reputation | Calculation of the PageRank for Chiman Maru took 0.023571014404296875s
Interlinking | Calculation of Degree of Connection for Chiman Maru took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Chiman Maru took 0.0011134147644042969s
Interlinking | Calculation of Clustering coefficient for Chiman Maru took 4.267692565917969e-05s
Believability | Calculation of trust value for Chiman Maru took 1.239776611328125e-05s
INFO | --- Analysis for ChimanMaru_Entrepreneur took 2.408113479614258s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 392.0601990222931s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.0007083415985107422s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 0.26901721954345703s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.02472400665283203s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 6.413459777832031e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 3.504753112792969e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 9.298324584960938e-06s
INFO | --- Analysis for Chinese_Red_Classic_Song_Linked_Data_Dataset took 798.0992133617401s
Availability | SPARQL endpoint availability check for Chronicling America took 8.940696716308594e-05s
Availability | VoID file availability check for Chronicling America took 0.0007634162902832031s
Completeness | Calculation of interlinking completeness for Chronicling America took 0.2671678066253662s
Reputation | Calculation of the PageRank for Chronicling America took 0.020705223083496094s
Interlinking | Calculation of Degree of Connection for Chronicling America took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Chronicling America took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 9.989738464355469e-05s
Believability | Calculation of trust value for Chronicling America took 1.1682510375976562e-05s
INFO | --- Analysis for chronicling-america took 6.631711721420288s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.564727783203125s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.0006389617919921875s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 81.48041820526123s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.3488795757293701s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 0.5803689956665039s
Interoperability | New terms check for Cultural Heritage Thesaurus took 2.847421169281006s
Versatility | Languages check for Cultural Heritage Thesaurus took 1.6199471950531006s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 0.5507292747497559s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.2767293453216553s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.2744770050048828s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 7.552414417266846s
License | MR license check for Cultural Heritage Thesaurus took 0.2789425849914551s
License | HR license check for Cultural Heritage Thesaurus took 0.33386874198913574s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.2624695301055908s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.29643726348876953s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.5218520164489746s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.2664778232574463s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.2614154815673828s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.27407050132751465s
Performance | Throughput check for Cultural Heritage Thesaurus took 10.734987497329712s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 8.106231689453125e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.2662472724914551s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.2745530605316162s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.28673672676086426s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.28087878227233887s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.26299500465393066s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.528616189956665s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.5432271957397461s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 27.907249927520752s
Interoperability | New vocabularies check for Cultural Heritage Thesaurus took 2.2383623123168945s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.27695226669311523s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.26041436195373535s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.2684061527252197s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 6.212630748748779s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.21736454963684082s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.25974607467651367s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 0.9575405120849609s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.2673001289367676s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 6.622524738311768s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 2.5145161151885986s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.00017023086547851562s
Security | Sign check for Cultural Heritage Thesaurus took 0.2696988582611084s
Availability | Check URIs Dereferenciability for Cultural Heritage Thesaurus took 273.1865518093109s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 0.3845837116241455s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.14523720741271973s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 4.220008850097656e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0015673637390136719s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 0.0001995563507080078s
Interoperability | Check the re-using of existing vocabs for Cultural Heritage Thesaurus took 2.1081764698028564s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 1.2636184692382812e-05s
INFO | --- Analysis for cht took 463.29048585891724s
Availability | SPARQL endpoint availability check for ciard-ring took 9.250640869140625e-05s
Availability | VoID file availability check for ciard-ring took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.2625999450683594s
Reputation | Calculation of the PageRank for ciard-ring took 0.020659923553466797s
Interlinking | Calculation of Degree of Connection for ciard-ring took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for ciard-ring took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 4.982948303222656e-05s
Believability | Calculation of trust value for ciard-ring took 1.049041748046875e-05s
INFO | --- Analysis for ciard-ring took 12.114752531051636s
Availability | SPARQL endpoint availability check for Cine Figure took 8.606910705566406e-05s
Availability | VoID file availability check for Cine Figure took 0.00042557716369628906s
Completeness | Calculation of interlinking completeness for Cine Figure took 0.2641596794128418s
Reputation | Calculation of the PageRank for Cine Figure took 0.02206254005432129s
Interlinking | Calculation of Degree of Connection for Cine Figure took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Cine Figure took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Cine Figure took 4.7206878662109375e-05s
Believability | Calculation of trust value for Cine Figure took 1.1920928955078125e-05s
INFO | --- Analysis for Cine_Figure took 2.445068597793579s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 2.903261184692383s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.2768380641937256s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.0207216739654541s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 4.458427429199219e-05s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 1.0251998901367188e-05s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 18.3864803314209s
Availability | SPARQL endpoint availability check for CIPFA took 4.3392181396484375e-05s
Availability | VoID file availability check for CIPFA took 0.00029468536376953125s
Completeness | Calculation of interlinking completeness for CIPFA took 0.2576260566711426s
Reputation | Calculation of the PageRank for CIPFA took 0.020920515060424805s
Interlinking | Calculation of Degree of Connection for CIPFA took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for CIPFA took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for CIPFA took 3.8623809814453125e-05s
Believability | Calculation of trust value for CIPFA took 4.5299530029296875e-06s
INFO | --- Analysis for cipfa took 2.524886131286621s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 60.04538106918335s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.0006506443023681641s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.2661478519439697s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.020961761474609375s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.00041031837463378906s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 1.0013580322265625e-05s
INFO | --- Analysis for ckan took 262.59061098098755s
Availability | SPARQL endpoint availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.5836350917816162s
Availability | VoID file availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.26402711868286133s
Reputation | Calculation of the PageRank for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.020711421966552734s
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.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 3.7670135498046875e-05s
Believability | Calculation of trust value for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.0013580322265625e-05s
INFO | --- Analysis for CLaSSES took 4.322162866592407s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 8.440017700195312e-05s
Availability | VoID file availability check for Temples of the Classical World took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 0.26625967025756836s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.020337343215942383s
Interlinking | Calculation of Degree of Connection for Temples of the Classical World took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Temples of the Classical World took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 3.123283386230469e-05s
Believability | Calculation of trust value for Temples of the Classical World took 9.5367431640625e-06s
INFO | --- Analysis for classical_temples took 4.21470832824707s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 1.9201455116271973s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.0005483627319335938s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 0.265317440032959s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.020411968231201172s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 8.416175842285156e-05s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 8.344650268554688e-06s
INFO | --- Analysis for clean-energy-data-reegle took 17.17723774909973s
Availability | SPARQL endpoint availability check for CLLD-afbo took 5.078315734863281e-05s
Availability | VoID file availability check for CLLD-afbo took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.2669675350189209s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.02087569236755371s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 7.987022399902344e-05s
Believability | Calculation of trust value for CLLD-afbo took 1.1205673217773438e-05s
INFO | --- Analysis for clld-afbo took 3.336784839630127s
Availability | SPARQL endpoint availability check for CLLD-APICS took 0.000102996826171875s
Availability | VoID file availability check for CLLD-APICS took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 0.2611069679260254s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.020757675170898438s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 7.891654968261719e-05s
Believability | Calculation of trust value for CLLD-APICS took 9.059906005859375e-06s
INFO | --- Analysis for clld-apics took 3.5515894889831543s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 8.225440979003906e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.26493191719055176s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.022048234939575195s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 4.482269287109375e-05s
Believability | Calculation of trust value for CLLD-EWAVE took 1.0013580322265625e-05s
INFO | --- Analysis for clld-ewave took 3.586205244064331s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 4.1961669921875e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 0.2604827880859375s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.020665645599365234s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 0.00010085105895996094s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 1.0013580322265625e-05s
INFO | --- Analysis for clld-glottolog took 3.385164976119995s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 0.00018286705017089844s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.0006649494171142578s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.264585018157959s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.02145862579345703s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 8.630752563476562e-05s
Believability | Calculation of trust value for CLLD-PHOIBLE took 1.239776611328125e-05s
INFO | --- Analysis for clld-phoible took 4.564564943313599s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 8.273124694824219e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 0.2641153335571289s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.020938634872436523s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 7.843971252441406e-05s
Believability | Calculation of trust value for CLLD-SAILS took 1.2159347534179688e-05s
INFO | --- Analysis for clld-sails took 3.486114978790283s
Availability | SPARQL endpoint availability check for CLLD-WALS took 4.458427429199219e-05s
Availability | VoID file availability check for CLLD-WALS took 0.0005657672882080078s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.2648303508758545s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.021328449249267578s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 8.153915405273438e-05s
Believability | Calculation of trust value for CLLD-WALS took 1.0967254638671875e-05s
INFO | --- Analysis for clld-wals took 3.584604024887085s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 8.249282836914062e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.0007009506225585938s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 0.27131056785583496s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.020450830459594727s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 7.939338684082031e-05s
Believability | Calculation of trust value for CLLD-WOLD took 1.2159347534179688e-05s
INFO | --- Analysis for clld-wold took 3.4475977420806885s
Availability | SPARQL endpoint availability check for Cooperation Databank took 0.1396641731262207s
Availability | VoID file availability check for Cooperation Databank took 0.0004551410675048828s
Completeness | Calculation of interlinking completeness for Cooperation Databank took 0.2612495422363281s
Reputation | Calculation of the PageRank for Cooperation Databank took 0.020798206329345703s
Interlinking | Calculation of Degree of Connection for Cooperation Databank took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Cooperation Databank took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Cooperation Databank took 3.838539123535156e-05s
Believability | Calculation of trust value for Cooperation Databank took 9.298324584960938e-06s
INFO | --- Analysis for CoDa took 2.5742218494415283s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 1.027024269104004s
Availability | VoID file availability check for OpenUpLabs COINS took 0.00044846534729003906s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.26337361335754395s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.0206148624420166s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 3.218650817871094e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 7.62939453125e-06s
INFO | --- Analysis for coins-openuplabs took 3.5078330039978027s
Availability | SPARQL endpoint availability check for Catalogue of Life in China 2003 Edition took 3.9817142486572266s
Availability | VoID file availability check for Catalogue of Life in China 2003 Edition took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for Catalogue of Life in China 2003 Edition took 0.2618277072906494s
Reputation | Calculation of the PageRank for Catalogue of Life in China 2003 Edition took 0.020371437072753906s
Interlinking | Calculation of Degree of Connection for Catalogue of Life in China 2003 Edition took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Catalogue of Life in China 2003 Edition took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Catalogue of Life in China 2003 Edition took 7.867813110351562e-05s
Believability | Calculation of trust value for Catalogue of Life in China 2003 Edition took 9.5367431640625e-06s
INFO | --- Analysis for CoLChina_sp2000 took 7.839366674423218s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 0.04897713661193848s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 0.26275634765625s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.02075028419494629s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0008177757263183594s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 4.1961669921875e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 1.1205673217773438e-05s
INFO | --- Analysis for colinda took 2.5924510955810547s
Availability | SPARQL endpoint availability check for CN  2012 took 25.23011827468872s
Availability | VoID file availability check for CN  2012 took 0.0010225772857666016s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.39046168327331543s
Reputation | Calculation of the PageRank for CN  2012 took 0.021065711975097656s
Interlinking | Calculation of Degree of Connection for CN  2012 took 2.384185791015625e-05s
Interlinking | Calculation of Centrality for CN  2012 took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 4.076957702636719e-05s
Believability | Calculation of trust value for CN  2012 took 8.344650268554688e-06s
INFO | --- Analysis for combined-nomenclature-2012 took 123.71760964393616s
Availability | SPARQL endpoint availability check for Computational Historical Semantics in LiLa took 0.3947300910949707s
Availability | VoID file availability check for Computational Historical Semantics in LiLa took 0.0006315708160400391s
Completeness | Calculation of interlinking completeness for Computational Historical Semantics in LiLa took 0.287280797958374s
Reputation | Calculation of the PageRank for Computational Historical Semantics in LiLa took 0.02029109001159668s
Interlinking | Calculation of Degree of Connection for Computational Historical Semantics in LiLa took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Computational Historical Semantics in LiLa took 0.0008566379547119141s
Interlinking | Calculation of Clustering coefficient for Computational Historical Semantics in LiLa took 4.0531158447265625e-05s
Believability | Calculation of trust value for Computational Historical Semantics in LiLa took 1.2874603271484375e-05s
INFO | --- Analysis for CompHistSem took 3.9182915687561035s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 1.7156546115875244s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.0002856254577636719s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 0.25696587562561035s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.02017521858215332s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 3.504753112792969e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 4.76837158203125e-06s
INFO | --- Analysis for comsode-d3-2 took 6.971365690231323s
Availability | SPARQL endpoint availability check for 2011 US Congress People took 5.030632019042969e-05s
Availability | VoID file availability check for 2011 US Congress People took 0.0002338886260986328s
Completeness | Calculation of interlinking completeness for 2011 US Congress People took 0.2607383728027344s
Reputation | Calculation of the PageRank for 2011 US Congress People took 0.020279645919799805s
Interlinking | Calculation of Degree of Connection for 2011 US Congress People took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 2011 US Congress People took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for 2011 US Congress People took 8.130073547363281e-05s
Believability | Calculation of trust value for 2011 US Congress People took 8.344650268554688e-06s
INFO | --- Analysis for congresspeople took 2.97568941116333s
Availability | SPARQL endpoint availability check for MIMO took 0.28452134132385254s
Availability | VoID file availability check for MIMO took 0.0008962154388427734s
Completeness | Calculation of interlinking completeness for MIMO took 0.269376277923584s
Reputation | Calculation of the PageRank for MIMO took 0.020918607711791992s
Interlinking | Calculation of Degree of Connection for MIMO took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for MIMO took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for MIMO took 1.811981201171875e-05s
Believability | Calculation of trust value for MIMO took 7.3909759521484375e-06s
INFO | --- Analysis for CONNECTED took 3.884429454803467s
Availability | SPARQL endpoint availability check for Copyright Free Music took 9.083747863769531e-05s
Availability | VoID file availability check for Copyright Free Music took 0.0006628036499023438s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 0.3708055019378662s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.02079010009765625s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 3.4332275390625e-05s
Believability | Calculation of trust value for Copyright Free Music took 7.867813110351562e-06s
INFO | --- Analysis for Copyright_Free_Music took 3.440885066986084s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 0.00014400482177734375s
Availability | VoID file availability check for CopyrightTermBank took 0.0005857944488525391s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 0.2719736099243164s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.020628929138183594s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0010068416595458984s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 9.059906005859375e-05s
Believability | Calculation of trust value for CopyrightTermBank took 1.2874603271484375e-05s
INFO | --- Analysis for copyrighttermbank took 4.7432637214660645s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 115.55310106277466s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.2718846797943115s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.020381927490234375s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 4.9591064453125e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 1.0013580322265625e-05s
INFO | --- Analysis for core took 120.54955744743347s
Availability | SPARQL endpoint availability check for Corine linked dataset @PSNC took 0.5120596885681152s
Availability | VoID file availability check for Corine linked dataset @PSNC took 0.0005133152008056641s
Extra | Recovery of all triples for Corine linked dataset @PSNC took 118.13468432426453s
Performance | Total latancy measurement for Corine linked dataset @PSNC took 0.8868677616119385s
Amount of data | Number of triples check for Corine linked dataset @PSNC took 10.524044036865234s
Interoperability | New terms check for Corine linked dataset @PSNC took 14.104710102081299s
Versatility | Languages check for Corine linked dataset @PSNC took 300.2376570701599s
Interpretability | Number of blank nodes check for Corine linked dataset @PSNC took 1.8915088176727295s
Interpretability | RDF structures check for Corine linked dataset @PSNC took 0.24487733840942383s
Versatility | Serialization formats check for Corine linked dataset @PSNC took 11.582707643508911s
Availability | RDF dump link check for Corine linked dataset @PSNC took 0.279996395111084s
License | MR license check for Corine linked dataset @PSNC took 0.536207914352417s
License | HR license check for Corine linked dataset @PSNC took 300.2245674133301s
Amount of data | Number of property check for Corine linked dataset @PSNC took 0.1898486614227295s
Understandability | Number of label check for Corine linked dataset @PSNC took 2.0184779167175293s
Understandability | URI regex check for Corine linked dataset @PSNC took 0.704246997833252s
Understandability | Vocabs check for Corine linked dataset @PSNC took 0.387819766998291s
Verifiability | Authors check for Corine linked dataset @PSNC took 0.18507122993469238s
Verifiability | Publishers check for Corine linked dataset @PSNC took 0.23081517219543457s
Performance | Throughput check for Corine linked dataset @PSNC took 10.905570983886719s
Amount of data | Check the number of entities for Corine linked dataset @PSNC took 7.319450378417969e-05s
Verifiability | Contribs. check for Corine linked dataset @PSNC took 0.1897726058959961s
Interlinking | sameAs chians check for Corine linked dataset @PSNC took 0.1927027702331543s
Interlinking | skos check for Corine linked dataset @PSNC took 0.4873166084289551s
Interlinking | skos check for Corine linked dataset @PSNC took 0.4221065044403076s
Timeliness | dataset update frequency check for Corine linked dataset @PSNC took 5.814630746841431s
Currency | Creation date check for Corine linked dataset @PSNC took 0.45224857330322266s
Currency | Modification date check for Corine linked dataset @PSNC took 0.22212696075439453s
Rep.Conc. | URIs length for Corine linked dataset @PSNC took 156.7003674507141s
Interoperability | New vocabularies check for Corine linked dataset @PSNC took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Corine linked dataset @PSNC took 0.18097615242004395s
Accuracy | Check Functional Property for Corine linked dataset @PSNC took 0.3591194152832031s
Accuracy | Check Inverse Functional Property for Corine linked dataset @PSNC took 0.37534070014953613s
Accuracy | Check Empty annotation labels for Corine linked dataset @PSNC took 37.60033655166626s
Accuracy | Check White space in annotation for Corine linked dataset @PSNC took 2.6611855030059814s
Accuracy | Check Datatype consistency for Corine linked dataset @PSNC took 2.5613389015197754s
Consistency | Disjoint class check for Corine linked dataset @PSNC took 0.18511033058166504s
Consistency | Check Misplaced properties for Corine linked dataset @PSNC took 86.59242010116577s
Consistency | Misplaced classes for Corine linked dataset @PSNC took 8.35190200805664s
Consistency | Check Ontology hijacking for Corine linked dataset @PSNC took 41.50095009803772s
Consistency | Check Invalid usage of undefined classes for Corine linked dataset @PSNC took 1.3245799541473389s
Consistency | Check Invalid usage of undefined properties for Corine linked dataset @PSNC took 87.38648700714111s
Conciseness | Check Extensional conciseness for Corine linked dataset @PSNC took 2.7295093536376953s
Conciseness | Check Intensional conciseness for Corine linked dataset @PSNC took 0.5093345642089844s
Security | Sign check for Corine linked dataset @PSNC took 0.8628075122833252s
Availability | Check URIs Dereferenciability for Corine linked dataset @PSNC took 10.067693948745728s
Completeness | Calculation of interlinking completeness for Corine linked dataset @PSNC took 0.3612372875213623s
Reputation | Calculation of the PageRank for Corine linked dataset @PSNC took 0.02246260643005371s
Interlinking | Calculation of Degree of Connection for Corine linked dataset @PSNC took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Corine linked dataset @PSNC took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Corine linked dataset @PSNC took 3.314018249511719e-05s
Interoperability | Check the re-using of existing vocabs for Corine linked dataset @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Corine linked dataset @PSNC took 1.2159347534179688e-05s
INFO | --- Analysis for Corine_linked_dataset took 2266.9627640247345s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 8.821487426757812e-05s
Availability | VoID file availability check for Cornetto1.2 took 0.0005931854248046875s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.26655006408691406s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.0219118595123291s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 5.650520324707031e-05s
Believability | Calculation of trust value for Cornetto1.2 took 7.867813110351562e-06s
INFO | --- Analysis for cornetto took 12.806559085845947s
Availability | SPARQL endpoint availability check for Corporate Body Named Authority List  took 0.14546680450439453s
Availability | VoID file availability check for Corporate Body Named Authority List  took 0.0005898475646972656s
Extra | Recovery of all triples for Corporate Body Named Authority List  took 225.8841896057129s
Performance | Total latancy measurement for Corporate Body Named Authority List  took 0.550389289855957s
Amount of data | Number of triples check for Corporate Body Named Authority List  took 104.65833163261414s
Interoperability | New terms check for Corporate Body Named Authority List  took 64.75740098953247s
Versatility | Languages check for Corporate Body Named Authority List  took 300.11819863319397s
Interpretability | Number of blank nodes check for Corporate Body Named Authority List  took 19.947250843048096s
Security | Check HTTPS for Corporate Body Named Authority List  took 0.31125426292419434s
Interpretability | RDF structures check for Corporate Body Named Authority List  took 0.5481789112091064s
Versatility | Serialization formats check for Corporate Body Named Authority List  took 4.4153783321380615s
Availability | RDF dump link check for Corporate Body Named Authority List  took 0.20111370086669922s
License | MR license check for Corporate Body Named Authority List  took 0.42762279510498047s
License | HR license check for Corporate Body Named Authority List  took 300.06031131744385s
Amount of data | Number of property check for Corporate Body Named Authority List  took 0.14461016654968262s
Understandability | Number of label check for Corporate Body Named Authority List  took 2.070340871810913s
Understandability | URI regex check for Corporate Body Named Authority List  took 0.42287254333496094s
Understandability | Vocabs check for Corporate Body Named Authority List  took 0.09649944305419922s
Verifiability | Authors check for Corporate Body Named Authority List  took 0.1913454532623291s
Verifiability | Publishers check for Corporate Body Named Authority List  took 0.19443202018737793s
Performance | Throughput check for Corporate Body Named Authority List  took 10.517871141433716s
Amount of data | Check the number of entities for Corporate Body Named Authority List  took 6.914138793945312e-05s
Verifiability | Contribs. check for Corporate Body Named Authority List  took 0.2053227424621582s
Interlinking | sameAs chians check for Corporate Body Named Authority List  took 7.859135389328003s
Interlinking | skos check for Corporate Body Named Authority List  took 0.32525086402893066s
Interlinking | skos check for Corporate Body Named Authority List  took 0.1633601188659668s
Timeliness | dataset update frequency check for Corporate Body Named Authority List  took 0.2799372673034668s
Currency | Creation date check for Corporate Body Named Authority List  took 0.4802260398864746s
Currency | Modification date check for Corporate Body Named Authority List  took 0.1453719139099121s
Rep.Conc. | URIs length for Corporate Body Named Authority List  took 432.6523597240448s
Interoperability | New vocabularies check for Corporate Body Named Authority List  took 6.198883056640625e-06s
Consistency | Deprecated classes/propertiers check for Corporate Body Named Authority List  took 0.20765900611877441s
Accuracy | Check Functional Property for Corporate Body Named Authority List  took 0.23325562477111816s
Accuracy | Check Inverse Functional Property for Corporate Body Named Authority List  took 0.1602177619934082s
Accuracy | Check Empty annotation labels for Corporate Body Named Authority List  took 48.02754282951355s
Accuracy | Check White space in annotation for Corporate Body Named Authority List  took 3.200652599334717s
Accuracy | Check Datatype consistency for Corporate Body Named Authority List  took 2.615001678466797s
Consistency | Disjoint class check for Corporate Body Named Authority List  took 0.1616060733795166s
Consistency | Check Misplaced properties for Corporate Body Named Authority List  took 300.44986939430237s
Consistency | Misplaced classes for Corporate Body Named Authority List  took 8.492940664291382s
Consistency | Check Ontology hijacking for Corporate Body Named Authority List  took 53.50465798377991s
Consistency | Check Invalid usage of undefined classes for Corporate Body Named Authority List  took 1.7382662296295166s
Consistency | Check Invalid usage of undefined properties for Corporate Body Named Authority List  took 301.5020172595978s
Conciseness | Check Extensional conciseness for Corporate Body Named Authority List  took 2.9939050674438477s
Conciseness | Check Intensional conciseness for Corporate Body Named Authority List  took 0.3687601089477539s
Security | Sign check for Corporate Body Named Authority List  took 0.19369959831237793s
Availability | Check URIs Dereferenciability for Corporate Body Named Authority List  took 19.090898275375366s
Completeness | Calculation of interlinking completeness for Corporate Body Named Authority List  took 1.4444553852081299s
Reputation | Calculation of the PageRank for Corporate Body Named Authority List  took 0.020841360092163086s
Interlinking | Calculation of Degree of Connection for Corporate Body Named Authority List  took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Corporate Body Named Authority List  took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Corporate Body Named Authority List  took 6.341934204101562e-05s
Interoperability | Check the re-using of existing vocabs for Corporate Body Named Authority List  took 1.430511474609375e-06s
Believability | Calculation of trust value for Corporate Body Named Authority List  took 1.0728836059570312e-05s
INFO | --- Analysis for corporate-body took 14342.071923494339s
Availability | SPARQL endpoint availability check for Corpus Fibonacci in LiLa took 0.513739824295044s
Availability | VoID file availability check for Corpus Fibonacci in LiLa took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for Corpus Fibonacci in LiLa took 0.2675938606262207s
Reputation | Calculation of the PageRank for Corpus Fibonacci in LiLa took 0.020844697952270508s
Interlinking | Calculation of Degree of Connection for Corpus Fibonacci in LiLa took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Corpus Fibonacci in LiLa took 0.0007922649383544922s
Interlinking | Calculation of Clustering coefficient for Corpus Fibonacci in LiLa took 5.0067901611328125e-05s
Believability | Calculation of trust value for Corpus Fibonacci in LiLa took 1.1205673217773438e-05s
INFO | --- Analysis for CorpusFibonacci took 4.002506971359253s
Availability | SPARQL endpoint availability check for Country Name Authority List took 0.12301802635192871s
Availability | VoID file availability check for Country Name Authority List took 0.0007123947143554688s
Extra | Recovery of all triples for Country Name Authority List took 201.08295249938965s
Performance | Total latancy measurement for Country Name Authority List took 0.5175952911376953s
Amount of data | Number of triples check for Country Name Authority List took 45.691758155822754s
Interoperability | New terms check for Country Name Authority List took 63.77903938293457s
Versatility | Languages check for Country Name Authority List took 300.06461215019226s
Interpretability | Number of blank nodes check for Country Name Authority List took 16.979968309402466s
Security | Check HTTPS for Country Name Authority List took 0.30515050888061523s
Interpretability | RDF structures check for Country Name Authority List took 0.49876999855041504s
Versatility | Serialization formats check for Country Name Authority List took 8.03596806526184s
Availability | RDF dump link check for Country Name Authority List took 0.17444872856140137s
License | MR license check for Country Name Authority List took 0.3635120391845703s
License | HR license check for Country Name Authority List took 300.02710700035095s
Amount of data | Number of property check for Country Name Authority List took 0.14844202995300293s
Understandability | Number of label check for Country Name Authority List took 1.9558043479919434s
Understandability | URI regex check for Country Name Authority List took 0.406355619430542s
Understandability | Vocabs check for Country Name Authority List took 0.09756755828857422s
Verifiability | Authors check for Country Name Authority List took 0.2735555171966553s
Verifiability | Publishers check for Country Name Authority List took 0.169569730758667s
Performance | Throughput check for Country Name Authority List took 10.544707775115967s
Amount of data | Check the number of entities for Country Name Authority List took 6.937980651855469e-05s
Verifiability | Contribs. check for Country Name Authority List took 0.221940279006958s
Interlinking | sameAs chians check for Country Name Authority List took 6.123274087905884s
Interlinking | skos check for Country Name Authority List took 0.42744922637939453s
Interlinking | skos check for Country Name Authority List took 0.31623315811157227s
Timeliness | dataset update frequency check for Country Name Authority List took 0.24329566955566406s
Currency | Creation date check for Country Name Authority List took 0.29876255989074707s
Currency | Modification date check for Country Name Authority List took 0.14058208465576172s
Rep.Conc. | URIs length for Country Name Authority List took 439.1708002090454s
Interoperability | New vocabularies check for Country Name Authority List took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for Country Name Authority List took 0.14837312698364258s
Accuracy | Check Functional Property for Country Name Authority List took 0.22081303596496582s
Accuracy | Check Inverse Functional Property for Country Name Authority List took 0.14988231658935547s
Accuracy | Check Empty annotation labels for Country Name Authority List took 46.43248438835144s
Accuracy | Check White space in annotation for Country Name Authority List took 3.066926956176758s
Accuracy | Check Datatype consistency for Country Name Authority List took 2.555861234664917s
Consistency | Disjoint class check for Country Name Authority List took 0.15760064125061035s
Consistency | Check Misplaced properties for Country Name Authority List took 300.63561177253723s
Consistency | Misplaced classes for Country Name Authority List took 8.39418888092041s
Consistency | Check Ontology hijacking for Country Name Authority List took 93.2708637714386s
Consistency | Check Invalid usage of undefined classes for Country Name Authority List took 1.6739375591278076s
Consistency | Check Invalid usage of undefined properties for Country Name Authority List took 301.5902919769287s
Conciseness | Check Extensional conciseness for Country Name Authority List took 3.0528297424316406s
Conciseness | Check Intensional conciseness for Country Name Authority List took 0.42852044105529785s
Security | Sign check for Country Name Authority List took 0.11679887771606445s
Availability | Check URIs Dereferenciability for Country Name Authority List took 10.87019681930542s
Completeness | Calculation of interlinking completeness for Country Name Authority List took 0.5905234813690186s
Reputation | Calculation of the PageRank for Country Name Authority List took 0.020560026168823242s
Interlinking | Calculation of Degree of Connection for Country Name Authority List took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Country Name Authority List took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Country Name Authority List took 5.555152893066406e-05s
Interoperability | Check the re-using of existing vocabs for Country Name Authority List took 2.1457672119140625e-06s
Believability | Calculation of trust value for Country Name Authority List took 1.1205673217773438e-05s
INFO | --- Analysis for country-authority-list took 14314.48709654808s
Availability | SPARQL endpoint availability check for Courts thesaurus took 0.07091164588928223s
Availability | VoID file availability check for Courts thesaurus took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 0.27403712272644043s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.020770788192749023s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 6.67572021484375e-05s
Believability | Calculation of trust value for Courts thesaurus took 1.1682510375976562e-05s
INFO | --- Analysis for courts-thesaurus took 2.599865436553955s
Availability | SPARQL endpoint availability check for Covid-on-the-Web Dataset took 20.487377166748047s
Availability | VoID file availability check for Covid-on-the-Web Dataset took 0.0006775856018066406s
Completeness | Calculation of interlinking completeness for Covid-on-the-Web Dataset took 0.26578569412231445s
Reputation | Calculation of the PageRank for Covid-on-the-Web Dataset took 0.020596981048583984s
Interlinking | Calculation of Degree of Connection for Covid-on-the-Web Dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Covid-on-the-Web Dataset took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Covid-on-the-Web Dataset took 7.987022399902344e-05s
Believability | Calculation of trust value for Covid-on-the-Web Dataset took 1.049041748046875e-05s
INFO | --- Analysis for Covid-on-the-Web took 54.802024602890015s
Availability | SPARQL endpoint availability check for CPA 2008 took 25.88698410987854s
Availability | VoID file availability check for CPA 2008 took 0.0007328987121582031s
Completeness | Calculation of interlinking completeness for CPA 2008 took 0.26601719856262207s
Reputation | Calculation of the PageRank for CPA 2008 took 0.020299673080444336s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CPA 2008 took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 3.600120544433594e-05s
Believability | Calculation of trust value for CPA 2008 took 8.58306884765625e-06s
INFO | --- Analysis for cpa-2008 took 125.57199740409851s
Availability | SPARQL endpoint availability check for Cooperative Patent Classification took 0.29082560539245605s
Availability | VoID file availability check for Cooperative Patent Classification took 0.0005710124969482422s
Extra | Recovery of all triples for Cooperative Patent Classification took 38.20694160461426s
Performance | Total latancy measurement for Cooperative Patent Classification took 1.0785820484161377s
Amount of data | Number of triples check for Cooperative Patent Classification took 90.24808955192566s
Versatility | Languages check for Cooperative Patent Classification took 100.20454549789429s
Interpretability | Number of blank nodes check for Cooperative Patent Classification took 90.25303936004639s
Interpretability | RDF structures check for Cooperative Patent Classification took 0.26424741744995117s
Versatility | Serialization formats check for Cooperative Patent Classification took 0.21215391159057617s
Availability | RDF dump link check for Cooperative Patent Classification took 0.17933440208435059s
License | MR license check for Cooperative Patent Classification took 0.25011253356933594s
License | HR license check for Cooperative Patent Classification took 90.15351915359497s
Amount of data | Number of property check for Cooperative Patent Classification took 0.20890164375305176s
Understandability | Number of label check for Cooperative Patent Classification took 90.21178412437439s
Understandability | URI regex check for Cooperative Patent Classification took 0.3269991874694824s
Understandability | Vocabs check for Cooperative Patent Classification took 0.20806527137756348s
Verifiability | Authors check for Cooperative Patent Classification took 0.20409393310546875s
Verifiability | Publishers check for Cooperative Patent Classification took 0.21552038192749023s
Performance | Throughput check for Cooperative Patent Classification took 11.071154832839966s
Amount of data | Check the number of entities for Cooperative Patent Classification took 7.581710815429688e-05s
Verifiability | Contribs. check for Cooperative Patent Classification took 0.18322968482971191s
Interlinking | sameAs chians check for Cooperative Patent Classification took 0.1835496425628662s
Interlinking | skos check for Cooperative Patent Classification took 0.1682877540588379s
Interlinking | skos check for Cooperative Patent Classification took 0.17152714729309082s
Timeliness | dataset update frequency check for Cooperative Patent Classification took 0.27396702766418457s
Currency | Creation date check for Cooperative Patent Classification took 0.3756272792816162s
Currency | Modification date check for Cooperative Patent Classification took 0.3555591106414795s
Rep.Conc. | URIs length for Cooperative Patent Classification took 132.09949684143066s
Interoperability | New vocabularies check for Cooperative Patent Classification took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for Cooperative Patent Classification took 0.22382259368896484s
Accuracy | Check Empty annotation labels for Cooperative Patent Classification took 18.340636491775513s
Accuracy | Check White space in annotation for Cooperative Patent Classification took 2.9402401447296143s
Accuracy | Check Datatype consistency for Cooperative Patent Classification took 4.839755296707153s
Consistency | Disjoint class check for Cooperative Patent Classification took 0.26547956466674805s
Consistency | Check Misplaced properties for Cooperative Patent Classification took 100.46113157272339s
Consistency | Check Ontology hijacking for Cooperative Patent Classification took 22.79394769668579s
Consistency | Check Invalid usage of undefined classes for Cooperative Patent Classification took 1.61848783493042s
Consistency | Check Invalid usage of undefined properties for Cooperative Patent Classification took 101.61784195899963s
Conciseness | Check Extensional conciseness for Cooperative Patent Classification took 2.8038153648376465s
Conciseness | Check Intensional conciseness for Cooperative Patent Classification took 0.28159642219543457s
Security | Sign check for Cooperative Patent Classification took 0.2248392105102539s
Availability | Check URIs Dereferenciability for Cooperative Patent Classification took 1.7840168476104736s
Completeness | Calculation of interlinking completeness for Cooperative Patent Classification took 0.41696834564208984s
Reputation | Calculation of the PageRank for Cooperative Patent Classification took 0.02129983901977539s
Interlinking | Calculation of Degree of Connection for Cooperative Patent Classification took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Cooperative Patent Classification took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Cooperative Patent Classification took 4.673004150390625e-05s
Interoperability | Check the re-using of existing vocabs for Cooperative Patent Classification took 1.430511474609375e-06s
Believability | Calculation of trust value for Cooperative Patent Classification took 1.1682510375976562e-05s
INFO | --- Analysis for CPC took 1200.911200761795s
Availability | SPARQL endpoint availability check for CPC 2008 took 26.420083045959473s
Availability | VoID file availability check for CPC 2008 took 0.0008695125579833984s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.27866125106811523s
Reputation | Calculation of the PageRank for CPC 2008 took 0.020709991455078125s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 5.555152893066406e-05s
Believability | Calculation of trust value for CPC 2008 took 5.7220458984375e-06s
INFO | --- Analysis for cpc-2008 took 124.81136131286621s
Availability | SPARQL endpoint availability check for CPV  2003 took 21.663612842559814s
Availability | VoID file availability check for CPV  2003 took 0.0008220672607421875s
Completeness | Calculation of interlinking completeness for CPV  2003 took 0.3621690273284912s
Reputation | Calculation of the PageRank for CPV  2003 took 0.022014617919921875s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 3.457069396972656e-05s
Believability | Calculation of trust value for CPV  2003 took 9.5367431640625e-06s
INFO | --- Analysis for cpv-2003 took 115.04868769645691s
Availability | SPARQL endpoint availability check for CPV 2008 took 25.749597311019897s
Availability | VoID file availability check for CPV 2008 took 0.0009200572967529297s
Completeness | Calculation of interlinking completeness for CPV 2008 took 0.27312135696411133s
Reputation | Calculation of the PageRank for CPV 2008 took 0.021872282028198242s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 4.839897155761719e-05s
Believability | Calculation of trust value for CPV 2008 took 9.298324584960938e-06s
INFO | --- Analysis for cpv-2008 took 124.57223749160767s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 266.4333438873291s
Availability | VoID file availability check for crowdsourcing-fb took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 0.30618810653686523s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.020452260971069336s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 4.482269287109375e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 1.239776611328125e-05s
INFO | --- Analysis for crowdsourcing-fb took 539.2662246227264s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 6.786573886871338s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.0006351470947265625s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 0.2892467975616455s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.02140021324157715s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 4.673004150390625e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 1.0251998901367188e-05s
INFO | --- Analysis for ctic-public-dataset took 43.78966021537781s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 0.6274960041046143s
Availability | VoID file availability check for CulturaLinkedData took 0.0004620552062988281s
Extra | Recovery of all triples for CulturaLinkedData took 152.0952730178833s
Performance | Total latancy measurement for CulturaLinkedData took 4.86571192741394s
Amount of data | Number of triples check for CulturaLinkedData took 2.67577862739563s
Interoperability | New terms check for CulturaLinkedData took 2.310580253601074s
Versatility | Languages check for CulturaLinkedData took 63.23427677154541s
Interpretability | Number of blank nodes check for CulturaLinkedData took 2.096759796142578s
Interpretability | RDF structures check for CulturaLinkedData took 0.4073619842529297s
Versatility | Serialization formats check for CulturaLinkedData took 0.43838071823120117s
Availability | RDF dump link check for CulturaLinkedData took 2.160801887512207s
License | MR license check for CulturaLinkedData took 0.7205824851989746s
License | HR license check for CulturaLinkedData took 61.322589635849s
Amount of data | Number of property check for CulturaLinkedData took 2.1339223384857178s
Understandability | Number of label check for CulturaLinkedData took 3.155391216278076s
Understandability | URI regex check for CulturaLinkedData took 2.5365397930145264s
Understandability | Vocabs check for CulturaLinkedData took 2.2037534713745117s
Verifiability | Authors check for CulturaLinkedData took 2.219322443008423s
Verifiability | Publishers check for CulturaLinkedData took 0.29587459564208984s
Performance | Throughput check for CulturaLinkedData took 22.623642683029175s
Amount of data | Check the number of entities for CulturaLinkedData took 7.2479248046875e-05s
Verifiability | Contribs. check for CulturaLinkedData took 0.29752516746520996s
Interlinking | sameAs chians check for CulturaLinkedData took 0.384279727935791s
Interlinking | skos check for CulturaLinkedData took 2.3724870681762695s
Interlinking | skos check for CulturaLinkedData took 0.22780990600585938s
Timeliness | dataset update frequency check for CulturaLinkedData took 0.33009886741638184s
Currency | Creation date check for CulturaLinkedData took 2.38014554977417s
Currency | Modification date check for CulturaLinkedData took 0.4375121593475342s
Rep.Conc. | URIs length for CulturaLinkedData took 65.28085613250732s
Interoperability | New vocabularies check for CulturaLinkedData took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for CulturaLinkedData took 0.2259988784790039s
Accuracy | Check Functional Property for CulturaLinkedData took 2.147101640701294s
Accuracy | Check Inverse Functional Property for CulturaLinkedData took 0.22614717483520508s
Accuracy | Check Empty annotation labels for CulturaLinkedData took 48.76706337928772s
Accuracy | Check White space in annotation for CulturaLinkedData took 1.5986518859863281s
Accuracy | Check Datatype consistency for CulturaLinkedData took 1.2579345703125s
Consistency | Disjoint class check for CulturaLinkedData took 2.1906912326812744s
Consistency | Check Misplaced properties for CulturaLinkedData took 10.932318687438965s
Consistency | Misplaced classes for CulturaLinkedData took 4.159975051879883s
Consistency | Check Ontology hijacking for CulturaLinkedData took 48.73749017715454s
Consistency | Check Invalid usage of undefined classes for CulturaLinkedData took 1.2748818397521973s
Consistency | Check Invalid usage of undefined properties for CulturaLinkedData took 11.87243103981018s
Conciseness | Check Extensional conciseness for CulturaLinkedData took 1.3708858489990234s
Conciseness | Check Intensional conciseness for CulturaLinkedData took 2.2201437950134277s
Security | Sign check for CulturaLinkedData took 2.9356586933135986s
Availability | Check URIs Dereferenciability for CulturaLinkedData took 9.921629905700684s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 0.3462197780609131s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.02077007293701172s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 3.8623809814453125e-05s
Interoperability | Check the re-using of existing vocabs for CulturaLinkedData took 1.6689300537109375e-06s
Believability | Calculation of trust value for CulturaLinkedData took 1.0728836059570312e-05s
INFO | --- Analysis for culturalinkeddata took 661.4407958984375s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.20374679565429688s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.26299071311950684s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.020427465438842773s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0008037090301513672s
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 8.821487426757812e-06s
INFO | --- Analysis for cz-ares-or took 2.8157401084899902s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.10039019584655762s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0007674694061279297s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.33161330223083496s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.022380828857421875s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0008962154388427734s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 3.9577484130859375e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 9.059906005859375e-06s
INFO | --- Analysis for cz-ares-rzp took 2.8289706707000732s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 0.09983396530151367s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.2680368423461914s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.02004075050354004s
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.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 3.218650817871094e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 9.298324584960938e-06s
INFO | --- Analysis for cz-cenia-irz-chemicals took 2.907613754272461s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 0.09961938858032227s
Availability | VoID file availability check for Integrated pollution registry took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.26842617988586426s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.020254135131835938s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 3.600120544433594e-05s
Believability | Calculation of trust value for Integrated pollution registry took 9.059906005859375e-06s
INFO | --- Analysis for cz-cenia-pollution took 2.7992470264434814s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 0.09945011138916016s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.0005326271057128906s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.2677114009857178s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.02022528648376465s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Contracts took 3.218650817871094e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Contracts took 8.821487426757812e-06s
INFO | --- Analysis for cz-contracts took 2.7430431842803955s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 0.10751724243164062s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.2645397186279297s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.020370960235595703s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 3.457069396972656e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 8.821487426757812e-06s
INFO | --- Analysis for cz-ctia-bans took 6.413388013839722s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 0.09975767135620117s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.0008997917175292969s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 0.2633819580078125s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.022007226943969727s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0008208751678466797s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 3.8623809814453125e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 9.5367431640625e-06s
INFO | --- Analysis for cz-ctia-confiscations took 2.706256628036499s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.11346054077148438s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.2639327049255371s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.02319049835205078s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 2.6226043701171875e-05s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 3.337860107421875e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 9.059906005859375e-06s
INFO | --- Analysis for cz-ctia-focus took 2.7814574241638184s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 0.10001683235168457s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.0007538795471191406s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 0.2622816562652588s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.020124435424804688s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 3.981590270996094e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 9.059906005859375e-06s
INFO | --- Analysis for cz-ctia-inspections took 2.7174909114837646s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 0.104339599609375s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.0007560253143310547s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.2634291648864746s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.02026200294494629s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 3.3855438232421875e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 8.344650268554688e-06s
INFO | --- Analysis for cz-ctia-sanctions took 5.9394965171813965s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 0.1926894187927246s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.27555131912231445s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.020107746124267578s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 4.172325134277344e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 8.58306884765625e-06s
INFO | --- Analysis for cz-cuzk-cadastre-offices took 2.844348430633545s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 0.09998822212219238s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.0007290840148925781s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.2656104564666748s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.020180940628051758s
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.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 3.314018249511719e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 8.344650268554688e-06s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 2.822878837585449s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 0.6273105144500732s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.2648301124572754s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.0213925838470459s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 4.744529724121094e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 8.344650268554688e-06s
INFO | --- Analysis for cz-czso-average-salaries took 3.4790749549865723s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 0.3182847499847412s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 0.26608753204345703s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.02025127410888672s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 3.6716461181640625e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 9.059906005859375e-06s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 3.150270938873291s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.3164193630218506s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.2639303207397461s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.02022075653076172s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 3.790855407714844e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 8.821487426757812e-06s
INFO | --- Analysis for cz-czso-demography-in-regions-czech-republic-age-categories took 3.1368677616119385s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 0.31571388244628906s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.26305723190307617s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.020330190658569336s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 3.695487976074219e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 9.775161743164062e-06s
INFO | --- Analysis for cz-czso-job-applicants took 3.171337842941284s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.3175086975097656s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.28906774520874023s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.020288705825805664s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 3.7670135498046875e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 8.106231689453125e-06s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 3.1660728454589844s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.3172729015350342s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007669925689697266s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.2619342803955078s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.020720243453979492s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 3.409385681152344e-05s
Believability | Calculation of trust value for Structure of regions of Czech Republic according to Czech Statistical Office took 8.821487426757812e-06s
INFO | --- Analysis for cz-czso-regions took 2.9553792476654053s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 0.3181030750274658s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.00022745132446289062s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 0.26300859451293945s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.021365642547607422s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 3.695487976074219e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 8.821487426757812e-06s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 3.1570792198181152s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 0.31928563117980957s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.0004951953887939453s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.26358509063720703s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.020758867263793945s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 3.933906555175781e-05s
Believability | Calculation of trust value for Social service facilities and nursing in districts of Czech republic took 8.821487426757812e-06s
INFO | --- Analysis for cz-czso-social-service-facilities took 3.1476686000823975s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 0.31593823432922363s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.2719130516052246s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.02185201644897461s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 3.910064697265625e-05s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 9.059906005859375e-06s
INFO | --- Analysis for cz-czso-unemployment-rate took 3.1538171768188477s
Availability | SPARQL endpoint availability check for ATC groups took 0.09970808029174805s
Availability | VoID file availability check for ATC groups took 0.0005564689636230469s
Completeness | Calculation of interlinking completeness for ATC groups took 0.2664604187011719s
Reputation | Calculation of the PageRank for ATC groups took 0.021321773529052734s
Interlinking | Calculation of Degree of Connection for ATC groups took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for ATC groups took 7.05718994140625e-05s
Believability | Calculation of trust value for ATC groups took 1.239776611328125e-05s
INFO | --- Analysis for cz-eh-1-atc took 2.7384915351867676s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.09928011894226074s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.281801700592041s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.02049565315246582s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Financial fulfillments took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 3.6716461181640625e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 8.58306884765625e-06s
INFO | --- Analysis for cz-fulfillments took 2.72990345954895s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 0.03257894515991211s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.26340508460998535s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.020233631134033203s
Interlinking | Calculation of Degree of Connection for Czech Business Entity identification numbers and names took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Czech Business Entity identification numbers and names took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 4.5299530029296875e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 7.867813110351562e-06s
INFO | --- Analysis for cz-ic took 3.056755304336548s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 0.10868000984191895s
Availability | VoID file availability check for List of Czech data boxes took 0.0006031990051269531s
Extra | Recovery of all triples for List of Czech data boxes took 207.6612033843994s
Performance | Total latancy measurement for List of Czech data boxes took 0.5315036773681641s
Amount of data | Number of triples check for List of Czech data boxes took 9.522145986557007s
Interoperability | New terms check for List of Czech data boxes took 10.987552642822266s
Versatility | Languages check for List of Czech data boxes took 300.1888461112976s
Interpretability | Number of blank nodes check for List of Czech data boxes took 1.259814739227295s
Interpretability | RDF structures check for List of Czech data boxes took 0.15742802619934082s
Versatility | Serialization formats check for List of Czech data boxes took 0.15433716773986816s
Availability | RDF dump link check for List of Czech data boxes took 13.452481508255005s
License | MR license check for List of Czech data boxes took 0.5572037696838379s
License | HR license check for List of Czech data boxes took 55.342368602752686s
Amount of data | Number of property check for List of Czech data boxes took 0.11006402969360352s
Understandability | Number of label check for List of Czech data boxes took 1.3985261917114258s
Understandability | URI regex check for List of Czech data boxes took 0.4305272102355957s
Understandability | Vocabs check for List of Czech data boxes took 0.10403561592102051s
Verifiability | Authors check for List of Czech data boxes took 0.12003111839294434s
Verifiability | Publishers check for List of Czech data boxes took 0.1270456314086914s
Performance | Throughput check for List of Czech data boxes took 10.467942714691162s
Amount of data | Check the number of entities for List of Czech data boxes took 2.938978910446167s
Verifiability | Contribs. check for List of Czech data boxes took 0.10578656196594238s
Interlinking | sameAs chians check for List of Czech data boxes took 0.41722750663757324s
Interlinking | skos check for List of Czech data boxes took 0.17619729042053223s
Interlinking | skos check for List of Czech data boxes took 0.105621337890625s
Timeliness | dataset update frequency check for List of Czech data boxes took 0.2153019905090332s
Currency | Creation date check for List of Czech data boxes took 0.2191295623779297s
Currency | Modification date check for List of Czech data boxes took 0.10565543174743652s
Rep.Conc. | URIs length for List of Czech data boxes took 142.27368545532227s
Interoperability | New vocabularies check for List of Czech data boxes took 990.1733365058899s
Consistency | Deprecated classes/propertiers check for List of Czech data boxes took 0.44462108612060547s
Accuracy | Check Functional Property for List of Czech data boxes took 0.20267510414123535s
Accuracy | Check Inverse Functional Property for List of Czech data boxes took 0.19515657424926758s
Accuracy | Check Empty annotation labels for List of Czech data boxes took 49.97450494766235s
Accuracy | Check White space in annotation for List of Czech data boxes took 3.036081075668335s
Accuracy | Check Datatype consistency for List of Czech data boxes took 2.5741078853607178s
Consistency | Disjoint class check for List of Czech data boxes took 0.10624122619628906s
Consistency | Check Misplaced properties for List of Czech data boxes took 73.13309693336487s
Consistency | Misplaced classes for List of Czech data boxes took 7.47370982170105s
Consistency | Check Ontology hijacking for List of Czech data boxes took 69.17834544181824s
Consistency | Check Invalid usage of undefined classes for List of Czech data boxes took 1.3482060432434082s
Consistency | Check Invalid usage of undefined properties for List of Czech data boxes took 64.03945183753967s
Conciseness | Check Extensional conciseness for List of Czech data boxes took 2.630831003189087s
Conciseness | Check Intensional conciseness for List of Czech data boxes took 0.320925235748291s
Security | Sign check for List of Czech data boxes took 0.13452410697937012s
Availability | Check URIs Dereferenciability for List of Czech data boxes took 332.2428059577942s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 0.7208962440490723s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.02209305763244629s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 8.940696716308594e-05s
Believability | Calculation of trust value for List of Czech data boxes took 1.7404556274414062e-05s
INFO | --- Analysis for cz-list-of-databoxes took 3163.1310131549835s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10893702507019043s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0006067752838134766s
Extra | Recovery of all triples for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 156.45935988426208s
Performance | Total latancy measurement for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.5066723823547363s
Amount of data | Number of triples check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 9.666638135910034s
Interoperability | New terms check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.961897611618042s
Versatility | Languages check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 300.1688051223755s
Interpretability | Number of blank nodes check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.2108604907989502s
Interpretability | RDF structures check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.123504638671875s
Versatility | Serialization formats check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.15816617012023926s
Availability | RDF dump link check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 13.081697225570679s
License | MR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.4832017421722412s
License | HR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 55.41085195541382s
Amount of data | Number of property check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11122751235961914s
Understandability | Number of label check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.45088529586792s
Understandability | URI regex check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.48497462272644043s
Understandability | Vocabs check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11383247375488281s
Verifiability | Authors check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11348700523376465s
Verifiability | Publishers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11101126670837402s
Performance | Throughput check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.723047971725464s
Amount of data | Check the number of entities for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.122138261795044s
Verifiability | Contribs. check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.17236757278442383s
Interlinking | sameAs chians check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.46311354637145996s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.19545698165893555s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10136651992797852s
Timeliness | dataset update frequency check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.23798727989196777s
Currency | Creation date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.21531295776367188s
Currency | Modification date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10446357727050781s
Rep.Conc. | URIs length for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 115.36171054840088s
Interoperability | New vocabularies check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 545.5160987377167s
Consistency | Deprecated classes/propertiers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.39977502822875977s
Accuracy | Check Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.2398691177368164s
Accuracy | Check Inverse Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.25550222396850586s
Accuracy | Check Empty annotation labels for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 31.96552348136902s
Accuracy | Check White space in annotation for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.0417802333831787s
Accuracy | Check Datatype consistency for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.633009195327759s
Consistency | Disjoint class check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10824275016784668s
Consistency | Check Misplaced properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 69.98076510429382s
Consistency | Misplaced classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 7.503344774246216s
Consistency | Check Ontology hijacking for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 32.287285804748535s
Consistency | Check Invalid usage of undefined classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.394989013671875s
Consistency | Check Invalid usage of undefined properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 63.62356400489807s
Conciseness | Check Extensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.672508478164673s
Conciseness | Check Intensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.3289647102355957s
Security | Sign check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.15190577507019043s
Availability | Check URIs Dereferenciability for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 332.2593286037445s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.4614737033843994s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.021152496337890625s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.504753112792969e-05s
Interoperability | Check the re-using of existing vocabs for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 899.2037360668182s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 8.821487426757812e-06s
INFO | --- Analysis for cz-nace took 3004.713618516922s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.2843334674835205s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.00046563148498535156s
Extra | Recovery of all triples for Czech National Open Data Catalog in DCAT-AP v1.1 took 447.07437658309937s
Performance | Total latancy measurement for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.7641863822937012s
Amount of data | Number of triples check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.49133896827697754s
Interoperability | New terms check for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.71563458442688s
Versatility | Languages check for Czech National Open Data Catalog in DCAT-AP v1.1 took 300.16488242149353s
Interpretability | Number of blank nodes check for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.2859675884246826s
Interpretability | RDF structures check for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.0523557662963867s
Versatility | Serialization formats check for Czech National Open Data Catalog in DCAT-AP v1.1 took 7.03495979309082s
Availability | RDF dump link check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.3286161422729492s
License | MR license check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.7239201068878174s
License | HR license check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.9603042602539062s
Amount of data | Number of property check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.15439963340759277s
Understandability | Number of label check for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.3881449699401855s
Understandability | URI regex check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.45147204399108887s
Understandability | Vocabs check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.22719454765319824s
Verifiability | Authors check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.3570876121520996s
Verifiability | Publishers check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.2845325469970703s
Performance | Throughput check for Czech National Open Data Catalog in DCAT-AP v1.1 took 10.741163969039917s
Amount of data | Check the number of entities for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.24249267578125e-05s
Verifiability | Contribs. check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.20423531532287598s
Interlinking | sameAs chians check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.2021346092224121s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.48254942893981934s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.15387630462646484s
Timeliness | dataset update frequency check for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.43538761138916s
Currency | Creation date check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.518761396408081s
Currency | Modification date check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.39992284774780273s
Rep.Conc. | URIs length for Czech National Open Data Catalog in DCAT-AP v1.1 took 91.70239186286926s
Interoperability | New vocabularies check for Czech National Open Data Catalog in DCAT-AP v1.1 took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.15327048301696777s
Accuracy | Check Functional Property for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.3800501823425293s
Accuracy | Check Inverse Functional Property for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.3811187744140625s
Accuracy | Check Empty annotation labels for Czech National Open Data Catalog in DCAT-AP v1.1 took 70.85784649848938s
Accuracy | Check White space in annotation for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.3930275440216064s
Accuracy | Check Datatype consistency for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.5893640518188477s
Consistency | Disjoint class check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.2033705711364746s
Consistency | Check Misplaced properties for Czech National Open Data Catalog in DCAT-AP v1.1 took 4.665796518325806s
Consistency | Misplaced classes for Czech National Open Data Catalog in DCAT-AP v1.1 took 8.018695831298828s
Consistency | Check Ontology hijacking for Czech National Open Data Catalog in DCAT-AP v1.1 took 77.68246603012085s
Consistency | Check Invalid usage of undefined classes for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.8324542045593262s
Consistency | Check Invalid usage of undefined properties for Czech National Open Data Catalog in DCAT-AP v1.1 took 5.986912488937378s
Conciseness | Check Extensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.1628262996673584s
Conciseness | Check Intensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.27315402030944824s
Security | Sign check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.33416152000427246s
Availability | Check URIs Dereferenciability for Czech National Open Data Catalog in DCAT-AP v1.1 took 917.9136147499084s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.1 took 5.818203926086426s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.021411418914794922s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.790855407714844e-05s
Interoperability | Check the re-using of existing vocabs for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.6689300537109375e-06s
Believability | Calculation of trust value for Czech National Open Data Catalog in DCAT-AP v1.1 took 9.059906005859375e-06s
INFO | --- Analysis for cz-nkod took 33944.565220594406s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 0.19407439231872559s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 0.26317620277404785s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.020463228225708008s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Orders took 3.910064697265625e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Orders took 6.198883056640625e-06s
INFO | --- Analysis for cz-orders took 2.8206822872161865s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 0.16595244407653809s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.0005929470062255859s
Extra | Recovery of all triples for Institutions of public power of the Czech Republic took 145.03914380073547s
Performance | Total latancy measurement for Institutions of public power of the Czech Republic took 0.524803876876831s
Amount of data | Number of triples check for Institutions of public power of the Czech Republic took 9.34183406829834s
Interoperability | New terms check for Institutions of public power of the Czech Republic took 10.875458240509033s
Versatility | Languages check for Institutions of public power of the Czech Republic took 300.15558528900146s
Interpretability | Number of blank nodes check for Institutions of public power of the Czech Republic took 1.253812313079834s
Interpretability | RDF structures check for Institutions of public power of the Czech Republic took 0.13216590881347656s
Versatility | Serialization formats check for Institutions of public power of the Czech Republic took 0.16092801094055176s
Availability | RDF dump link check for Institutions of public power of the Czech Republic took 13.08858871459961s
License | MR license check for Institutions of public power of the Czech Republic took 0.40146613121032715s
License | HR license check for Institutions of public power of the Czech Republic took 53.358811140060425s
Amount of data | Number of property check for Institutions of public power of the Czech Republic took 0.11490941047668457s
Understandability | Number of label check for Institutions of public power of the Czech Republic took 1.328190565109253s
Understandability | URI regex check for Institutions of public power of the Czech Republic took 0.4314541816711426s
Understandability | Vocabs check for Institutions of public power of the Czech Republic took 0.10418081283569336s
Verifiability | Authors check for Institutions of public power of the Czech Republic took 0.11620712280273438s
Verifiability | Publishers check for Institutions of public power of the Czech Republic took 0.10410928726196289s
Performance | Throughput check for Institutions of public power of the Czech Republic took 10.687249422073364s
Amount of data | Check the number of entities for Institutions of public power of the Czech Republic took 3.0409128665924072s
Verifiability | Contribs. check for Institutions of public power of the Czech Republic took 0.10372805595397949s
Interlinking | sameAs chians check for Institutions of public power of the Czech Republic took 0.39369893074035645s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.1785123348236084s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.10090517997741699s
Timeliness | dataset update frequency check for Institutions of public power of the Czech Republic took 0.20372700691223145s
Currency | Creation date check for Institutions of public power of the Czech Republic took 0.22417402267456055s
Currency | Modification date check for Institutions of public power of the Czech Republic took 0.10454273223876953s
Rep.Conc. | URIs length for Institutions of public power of the Czech Republic took 112.84615921974182s
Interoperability | New vocabularies check for Institutions of public power of the Czech Republic took 877.6697225570679s
Consistency | Deprecated classes/propertiers check for Institutions of public power of the Czech Republic took 0.35928964614868164s
Accuracy | Check Functional Property for Institutions of public power of the Czech Republic took 0.1560962200164795s
Accuracy | Check Inverse Functional Property for Institutions of public power of the Czech Republic took 0.15220046043395996s
Accuracy | Check Empty annotation labels for Institutions of public power of the Czech Republic took 30.88258194923401s
Accuracy | Check White space in annotation for Institutions of public power of the Czech Republic took 3.021632671356201s
Accuracy | Check Datatype consistency for Institutions of public power of the Czech Republic took 2.5871129035949707s
Consistency | Disjoint class check for Institutions of public power of the Czech Republic took 0.1082906723022461s
Consistency | Check Misplaced properties for Institutions of public power of the Czech Republic took 69.61860489845276s
Consistency | Misplaced classes for Institutions of public power of the Czech Republic took 7.471783638000488s
Consistency | Check Ontology hijacking for Institutions of public power of the Czech Republic took 31.542949199676514s
Consistency | Check Invalid usage of undefined classes for Institutions of public power of the Czech Republic took 1.3963828086853027s
Consistency | Check Invalid usage of undefined properties for Institutions of public power of the Czech Republic took 65.12093257904053s
Conciseness | Check Extensional conciseness for Institutions of public power of the Czech Republic took 2.628216028213501s
Conciseness | Check Intensional conciseness for Institutions of public power of the Czech Republic took 0.33618760108947754s
Security | Sign check for Institutions of public power of the Czech Republic took 0.1643373966217041s
Availability | Check URIs Dereferenciability for Institutions of public power of the Czech Republic took 330.860759973526s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 0.48973941802978516s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.022214412689208984s
Interlinking | Calculation of Degree of Connection for Institutions of public power of the Czech Republic took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Institutions of public power of the Czech Republic took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 0.00010633468627929688s
Interoperability | Check the re-using of existing vocabs for Institutions of public power of the Czech Republic took 960.6172623634338s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 1.049041748046875e-05s
INFO | --- Analysis for cz-ovm took 3383.463479042053s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 0.09923934936523438s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 0.2630183696746826s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.020671367645263672s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 3.790855407714844e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 7.867813110351562e-06s
INFO | --- Analysis for cz-ovm-agendas took 2.7613677978515625s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.16478967666625977s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0006220340728759766s
Extra | Recovery of all triples for Registry of territorial identification, addresses and real estate of the Czech Republic took 57.99213266372681s
Performance | Total latancy measurement for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.4975612163543701s
Amount of data | Number of triples check for Registry of territorial identification, addresses and real estate of the Czech Republic took 37.62088322639465s
Interoperability | New terms check for Registry of territorial identification, addresses and real estate of the Czech Republic took 33.37093138694763s
Versatility | Languages check for Registry of territorial identification, addresses and real estate of the Czech Republic took 300.08323192596436s
Interpretability | Number of blank nodes check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.22562122344970703s
Interpretability | RDF structures check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.3769848346710205s
Versatility | Serialization formats check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1268465518951416s
Availability | RDF dump link check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.7052936553955078s
License | MR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12224674224853516s
License | HR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10205769538879395s
Amount of data | Number of property check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10226297378540039s
Understandability | Number of label check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.9047973155975342s
Understandability | URI regex check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.20190024375915527s
Understandability | Vocabs check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11122441291809082s
Verifiability | Authors check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.14379382133483887s
Verifiability | Publishers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10197997093200684s
Performance | Throughput check for Registry of territorial identification, addresses and real estate of the Czech Republic took 10.131583452224731s
Amount of data | Check the number of entities for Registry of territorial identification, addresses and real estate of the Czech Republic took 6.771087646484375e-05s
Verifiability | Contribs. check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10248470306396484s
Interlinking | sameAs chians check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10187458992004395s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11229562759399414s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10135674476623535s
Timeliness | dataset update frequency check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10482144355773926s
Currency | Creation date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.20454049110412598s
Currency | Modification date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10321903228759766s
Rep.Conc. | URIs length for Registry of territorial identification, addresses and real estate of the Czech Republic took 221.78277206420898s
Interoperability | New vocabularies check for Registry of territorial identification, addresses and real estate of the Czech Republic took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.09949445724487305s
Accuracy | Check Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10674738883972168s
Accuracy | Check Inverse Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10779666900634766s
Accuracy | Check Empty annotation labels for Registry of territorial identification, addresses and real estate of the Czech Republic took 13.153652429580688s
Accuracy | Check White space in annotation for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.1683175563812256s
Accuracy | Check Datatype consistency for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.594601631164551s
Consistency | Disjoint class check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11076068878173828s
Consistency | Check Misplaced properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 167.77990102767944s
Consistency | Misplaced classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 8.24874234199524s
Consistency | Check Ontology hijacking for Registry of territorial identification, addresses and real estate of the Czech Republic took 17.636731386184692s
Consistency | Check Invalid usage of undefined classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.3171823024749756s
Consistency | Check Invalid usage of undefined properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 168.8791675567627s
Conciseness | Check Extensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.893745183944702s
Conciseness | Check Intensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.22999072074890137s
Security | Sign check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10157895088195801s
Availability | Check URIs Dereferenciability for Registry of territorial identification, addresses and real estate of the Czech Republic took 9.882333755493164s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.7094871997833252s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.022440195083618164s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 8.034706115722656e-05s
Interoperability | Check the re-using of existing vocabs for Registry of territorial identification, addresses and real estate of the Czech Republic took 5.245208740234375e-06s
Believability | Calculation of trust value for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.0251998901367188e-05s
INFO | --- Analysis for cz-ruian took 1554.4715838432312s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.6350605487823486s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.2645890712738037s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.020528554916381836s
Interlinking | Calculation of Degree of Connection for Audited subjects of Supreme Audit Office of the Czech Republic took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 7.867813110351562e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 9.5367431640625e-06s
INFO | --- Analysis for cz-sao-audited-subjects took 3.617225170135498s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.43859004974365234s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.0007011890411376953s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 0.30591750144958496s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.0225827693939209s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.0007834434509277344s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 4.649162292480469e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 9.298324584960938e-06s
INFO | --- Analysis for cz-sao-check-actions took 3.5096592903137207s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 0.41846132278442383s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.0003173351287841797s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 0.26757264137268066s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.029923677444458008s
Interlinking | Calculation of Degree of Connection for List of laws used in inspection reports of SAO took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for List of laws used in inspection reports of SAO took 0.0010764598846435547s
Interlinking | Calculation of Clustering coefficient for List of laws used in inspection reports of SAO took 3.886222839355469e-05s
Believability | Calculation of trust value for List of laws used in inspection reports of SAO took 8.106231689453125e-06s
INFO | --- Analysis for cz-sao-check-actions-law took 3.468435764312744s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 0.10565638542175293s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 0.2668955326080322s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.020525217056274414s
Interlinking | Calculation of Degree of Connection for Active ingredients of medicinal products available in Czech Republic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Active ingredients of medicinal products available in Czech Republic took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 3.981590270996094e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 9.5367431640625e-06s
INFO | --- Analysis for cz-sidc-drug-ingredients took 2.7715635299682617s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.10418462753295898s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0007419586181640625s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 0.26496028900146484s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.020244598388671875s
Interlinking | Calculation of Degree of Connection for List of prices of reimbursed medicinal products marketed in Czech republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 3.409385681152344e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 7.62939453125e-06s
INFO | --- Analysis for cz-sidc-drug-prices took 3.0254945755004883s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 0.11234807968139648s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 0.2622864246368408s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.020940780639648438s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 3.814697265625e-05s
Believability | Calculation of trust value for Medicinal products marketed in Czech Republic took 1.2874603271484375e-05s
INFO | --- Analysis for cz-sidc-drugs took 2.981139898300171s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 0.17367196083068848s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.0007102489471435547s
Extra | Recovery of all triples for Summary types of Czech institutions of public power took 142.35895228385925s
Performance | Total latancy measurement for Summary types of Czech institutions of public power took 0.5088205337524414s
Amount of data | Number of triples check for Summary types of Czech institutions of public power took 9.349626302719116s
Interoperability | New terms check for Summary types of Czech institutions of public power took 10.776803970336914s
Versatility | Languages check for Summary types of Czech institutions of public power took 300.1114513874054s
Interpretability | Number of blank nodes check for Summary types of Czech institutions of public power took 1.1951568126678467s
Interpretability | RDF structures check for Summary types of Czech institutions of public power took 0.12407684326171875s
Versatility | Serialization formats check for Summary types of Czech institutions of public power took 0.1553800106048584s
Availability | RDF dump link check for Summary types of Czech institutions of public power took 13.134663343429565s
License | MR license check for Summary types of Czech institutions of public power took 0.5527694225311279s
License | HR license check for Summary types of Czech institutions of public power took 56.932610750198364s
Amount of data | Number of property check for Summary types of Czech institutions of public power took 0.11238265037536621s
Understandability | Number of label check for Summary types of Czech institutions of public power took 1.7318651676177979s
Understandability | URI regex check for Summary types of Czech institutions of public power took 0.6419339179992676s
Understandability | Vocabs check for Summary types of Czech institutions of public power took 0.11659836769104004s
Verifiability | Authors check for Summary types of Czech institutions of public power took 0.11685466766357422s
Verifiability | Publishers check for Summary types of Czech institutions of public power took 0.10829567909240723s
Performance | Throughput check for Summary types of Czech institutions of public power took 10.713850021362305s
Amount of data | Check the number of entities for Summary types of Czech institutions of public power took 2.980907678604126s
Verifiability | Contribs. check for Summary types of Czech institutions of public power took 0.10324788093566895s
Interlinking | sameAs chians check for Summary types of Czech institutions of public power took 0.4686291217803955s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.20814228057861328s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.10579442977905273s
Timeliness | dataset update frequency check for Summary types of Czech institutions of public power took 0.2521235942840576s
Currency | Creation date check for Summary types of Czech institutions of public power took 0.2301332950592041s
Currency | Modification date check for Summary types of Czech institutions of public power took 0.10613465309143066s
Rep.Conc. | URIs length for Summary types of Czech institutions of public power took 110.88529849052429s
Interoperability | New vocabularies check for Summary types of Czech institutions of public power took 108.94988179206848s
Consistency | Deprecated classes/propertiers check for Summary types of Czech institutions of public power took 0.341372013092041s
Accuracy | Check Functional Property for Summary types of Czech institutions of public power took 0.17203879356384277s
Accuracy | Check Inverse Functional Property for Summary types of Czech institutions of public power took 0.17350077629089355s
Accuracy | Check Empty annotation labels for Summary types of Czech institutions of public power took 30.568055629730225s
Accuracy | Check White space in annotation for Summary types of Czech institutions of public power took 3.040005683898926s
Accuracy | Check Datatype consistency for Summary types of Czech institutions of public power took 2.5504331588745117s
Consistency | Disjoint class check for Summary types of Czech institutions of public power took 0.10769104957580566s
Consistency | Check Misplaced properties for Summary types of Czech institutions of public power took 69.15229344367981s
Consistency | Misplaced classes for Summary types of Czech institutions of public power took 7.416055917739868s
Consistency | Check Ontology hijacking for Summary types of Czech institutions of public power took 30.71382999420166s
Consistency | Check Invalid usage of undefined classes for Summary types of Czech institutions of public power took 1.2547340393066406s
Consistency | Check Invalid usage of undefined properties for Summary types of Czech institutions of public power took 62.57249879837036s
Conciseness | Check Extensional conciseness for Summary types of Czech institutions of public power took 2.615905284881592s
Conciseness | Check Intensional conciseness for Summary types of Czech institutions of public power took 0.33101844787597656s
Security | Sign check for Summary types of Czech institutions of public power took 0.14128422737121582s
Availability | Check URIs Dereferenciability for Summary types of Czech institutions of public power took 331.5535423755646s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 0.352618932723999s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.021751880645751953s
Interlinking | Calculation of Degree of Connection for Summary types of Czech institutions of public power took 6.461143493652344e-05s
Interlinking | Calculation of Centrality for Summary types of Czech institutions of public power took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 5.5789947509765625e-05s
Interoperability | Check the re-using of existing vocabs for Summary types of Czech institutions of public power took 463.0356647968292s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 5.9604644775390625e-06s
INFO | --- Analysis for cz-souhrnne-typy-ovm took 2113.6436891555786s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 0.10076141357421875s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 0.3083207607269287s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.020385026931762695s
Interlinking | Calculation of Degree of Connection for Evaluation of VaVaI results for 2013 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Evaluation of VaVaI results for 2013 took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 3.314018249511719e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 7.152557373046875e-06s
INFO | --- Analysis for cz-vavai-evaluation-2013 took 2.8361740112304688s
Availability | SPARQL endpoint availability check for State funding providers took 0.10032153129577637s
Availability | VoID file availability check for State funding providers took 0.0004398822784423828s
Completeness | Calculation of interlinking completeness for State funding providers took 0.26711344718933105s
Reputation | Calculation of the PageRank for State funding providers took 0.020570993423461914s
Interlinking | Calculation of Degree of Connection for State funding providers took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for State funding providers took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for State funding providers took 3.933906555175781e-05s
Believability | Calculation of trust value for State funding providers took 8.106231689453125e-06s
INFO | --- Analysis for cz-vavai-funding-providers took 2.74611759185791s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 0.09896731376647949s
Availability | VoID file availability check for Organizations active in R&D took 0.00044536590576171875s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 0.26510047912597656s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.02062511444091797s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 4.076957702636719e-05s
Believability | Calculation of trust value for Organizations active in R&D took 9.298324584960938e-06s
INFO | --- Analysis for cz-vavai-organizations took 2.902223825454712s
Availability | SPARQL endpoint availability check for R&D Programmes took 0.0984039306640625s
Availability | VoID file availability check for R&D Programmes took 0.000438690185546875s
Completeness | Calculation of interlinking completeness for R&D Programmes took 0.26592397689819336s
Reputation | Calculation of the PageRank for R&D Programmes took 0.020453453063964844s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for R&D Programmes took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 3.838539123535156e-05s
Believability | Calculation of trust value for R&D Programmes took 7.62939453125e-06s
INFO | --- Analysis for cz-vavai-programmes took 2.7517271041870117s
Availability | SPARQL endpoint availability check for R&D Projects took 0.09915018081665039s
Availability | VoID file availability check for R&D Projects took 0.0010974407196044922s
Completeness | Calculation of interlinking completeness for R&D Projects took 0.26409173011779785s
Reputation | Calculation of the PageRank for R&D Projects took 0.02028656005859375s
Interlinking | Calculation of Degree of Connection for R&D Projects took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for R&D Projects took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 3.790855407714844e-05s
Believability | Calculation of trust value for R&D Projects took 7.3909759521484375e-06s
INFO | --- Analysis for cz-vavai-projects took 2.8087518215179443s
Availability | SPARQL endpoint availability check for Institutional research plans took 0.0989692211151123s
Availability | VoID file availability check for Institutional research plans took 0.0007886886596679688s
Completeness | Calculation of interlinking completeness for Institutional research plans took 0.26367712020874023s
Reputation | Calculation of the PageRank for Institutional research plans took 0.02059197425842285s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Institutional research plans took 0.0009412765502929688s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 4.792213439941406e-05s
Believability | Calculation of trust value for Institutional research plans took 8.821487426757812e-06s
INFO | --- Analysis for cz-vavai-research-plans took 2.764338731765747s
Availability | SPARQL endpoint availability check for Results of R&D took 0.09967780113220215s
Availability | VoID file availability check for Results of R&D took 0.0004298686981201172s
Completeness | Calculation of interlinking completeness for Results of R&D took 0.260089635848999s
Reputation | Calculation of the PageRank for Results of R&D took 0.022948741912841797s
Interlinking | Calculation of Degree of Connection for Results of R&D took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Results of R&D took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 3.981590270996094e-05s
Believability | Calculation of trust value for Results of R&D took 7.867813110351562e-06s
INFO | --- Analysis for cz-vavai-results took 2.7292990684509277s
Availability | SPARQL endpoint availability check for Tenders in R&D took 0.09962940216064453s
Availability | VoID file availability check for Tenders in R&D took 0.0007994174957275391s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.26670050621032715s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.020731687545776367s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Tenders in R&D took 3.8623809814453125e-05s
Believability | Calculation of trust value for Tenders in R&D took 8.106231689453125e-06s
INFO | --- Analysis for cz-vavai-tenders took 2.7580504417419434s
Availability | SPARQL endpoint availability check for Czech addresses – Adresy v České republice took 4.649162292480469e-05s
Availability | VoID file availability check for Czech addresses – Adresy v České republice took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for Czech addresses – Adresy v České republice took 0.26877379417419434s
Reputation | Calculation of the PageRank for Czech addresses – Adresy v České republice took 0.020849227905273438s
Interlinking | Calculation of Degree of Connection for Czech addresses – Adresy v České republice took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Czech addresses – Adresy v České republice took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Czech addresses – Adresy v České republice took 3.552436828613281e-05s
Believability | Calculation of trust value for Czech addresses – Adresy v České republice took 9.298324584960938e-06s
INFO | --- Analysis for czech_addresses took 3.805934429168701s
Availability | SPARQL endpoint availability check for Dante Latin Loanwords in LiLa took 0.5703244209289551s
Availability | VoID file availability check for Dante Latin Loanwords in LiLa took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for Dante Latin Loanwords in LiLa took 0.26852917671203613s
Reputation | Calculation of the PageRank for Dante Latin Loanwords in LiLa took 0.024069547653198242s
Interlinking | Calculation of Degree of Connection for Dante Latin Loanwords in LiLa took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Dante Latin Loanwords in LiLa took 0.001256704330444336s
Interlinking | Calculation of Clustering coefficient for Dante Latin Loanwords in LiLa took 5.3882598876953125e-05s
Believability | Calculation of trust value for Dante Latin Loanwords in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for DanteLatinLoanwords took 4.116072177886963s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.33751583099365234s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.0005295276641845703s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 122.48126435279846s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 0.930426836013794s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 7.753189325332642s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 4.18021821975708s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 120.24001908302307s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 0.2165215015411377s
Security | Check HTTPS for data.bnf.fr - Bibliothèque nationale de France took 0.10578060150146484s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 0.33986759185791016s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 0.22623181343078613s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.20293903350830078s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 0.24837231636047363s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 120.29274702072144s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.2124180793762207s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 1.9008448123931885s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 0.4149453639984131s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.20640778541564941s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 0.528252363204956s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 0.21889925003051758s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 10.407866716384888s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 7.176399230957031e-05s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 0.20020365715026855s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 0.5127530097961426s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 1.313483476638794s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.2125556468963623s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.21529769897460938s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 1.1360447406768799s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 0.4078099727630615s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 85.88546538352966s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.19646787643432617s
Accuracy | Check Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.2519817352294922s
Accuracy | Check Inverse Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.3908660411834717s
Accuracy | Check Empty annotation labels for data.bnf.fr - Bibliothèque nationale de France took 37.35283374786377s
Accuracy | Check White space in annotation for data.bnf.fr - Bibliothèque nationale de France took 3.096001625061035s
Accuracy | Check Datatype consistency for data.bnf.fr - Bibliothèque nationale de France took 2.531283140182495s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 0.25341153144836426s
Consistency | Check Misplaced properties for data.bnf.fr - Bibliothèque nationale de France took 21.867122411727905s
Consistency | Misplaced classes for data.bnf.fr - Bibliothèque nationale de France took 8.313001871109009s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 43.50380754470825s
Consistency | Check Invalid usage of undefined classes for data.bnf.fr - Bibliothèque nationale de France took 1.3639228343963623s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 22.95280957221985s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 2.786334753036499s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.21129798889160156s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 0.22822070121765137s
Availability | Check URIs Dereferenciability for data.bnf.fr - Bibliothèque nationale de France took 8.92857551574707s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 0.376939058303833s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.021229028701782227s
Interlinking | Calculation of Degree of Connection for data.bnf.fr - Bibliothèque nationale de France took 7.772445678710938e-05s
Interlinking | Calculation of Centrality for data.bnf.fr - Bibliothèque nationale de France took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.00014352798461914062s
Interoperability | Check the re-using of existing vocabs for data.bnf.fr - Bibliothèque nationale de France took 1.6689300537109375e-06s
Believability | Calculation of trust value for data.bnf.fr - Bibliothèque nationale de France took 1.1920928955078125e-05s
INFO | --- Analysis for data-bnf-fr took 811.6852867603302s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 0.3094351291656494s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 0.2616124153137207s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.02046370506286621s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 6.556510925292969e-05s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 9.298324584960938e-06s
INFO | --- Analysis for data-cnr-it took 3.5141544342041016s
Availability | SPARQL endpoint availability check for Data.gov took 1.3458311557769775s
Availability | VoID file availability check for Data.gov took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for Data.gov took 0.2680356502532959s
Reputation | Calculation of the PageRank for Data.gov took 0.02081465721130371s
Interlinking | Calculation of Degree of Connection for Data.gov took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Data.gov took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Data.gov took 3.218650817871094e-05s
Believability | Calculation of trust value for Data.gov took 7.867813110351562e-06s
INFO | --- Analysis for data-gov took 17.06004548072815s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 0.032994747161865234s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.0004277229309082031s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 0.26786255836486816s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.02117443084716797s
Interlinking | Calculation of Degree of Connection for DataGovIE - Irish Government Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DataGovIE - Irish Government Data took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 7.009506225585938e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 9.059906005859375e-06s
INFO | --- Analysis for data-gov-ie took 2.5065042972564697s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 8.749961853027344e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 0.00041484832763671875s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 0.26178598403930664s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.02068161964416504s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for data.gov.uk Time Intervals took 7.2479248046875e-05s
Believability | Calculation of trust value for data.gov.uk Time Intervals took 7.62939453125e-06s
INFO | --- Analysis for data-gov-uk-time-intervals took 2.477545738220215s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 21.988414764404297s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.0006535053253173828s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 0.26550769805908203s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.020652055740356445s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 6.008148193359375e-05s
Believability | Calculation of trust value for data-hnm-hu - Hungarian National Museum Datasets took 1.1444091796875e-05s
INFO | --- Analysis for data-hnm-hu took 164.99424076080322s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.12484431266784668s
Availability | VoID file availability check for Climb Dataincubator took 0.0004658699035644531s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.2669041156768799s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.020574569702148438s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 7.081031799316406e-05s
Believability | Calculation of trust value for Climb Dataincubator took 1.2159347534179688e-05s
INFO | --- Analysis for data-incubator-climb took 2.5318655967712402s
Availability | SPARQL endpoint availability check for Discogs in RDF took 8.416175842285156e-05s
Availability | VoID file availability check for Discogs in RDF took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.26596713066101074s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.021750450134277344s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 9.107589721679688e-05s
Believability | Calculation of trust value for Discogs in RDF took 9.5367431640625e-06s
INFO | --- Analysis for data-incubator-discogs took 4.606979131698608s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 0.04532670974731445s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.0007154941558837891s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 0.2749323844909668s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.021524429321289062s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 5.53131103515625e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 8.344650268554688e-06s
INFO | --- Analysis for data-incubator-metoffice took 5.48774528503418s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.046571969985961914s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.0007278919219970703s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 0.27593111991882324s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.020312070846557617s
Interlinking | Calculation of Degree of Connection for Moseley Folk Festival Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Moseley Folk Festival Data took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 8.96453857421875e-05s
Believability | Calculation of trust value for Moseley Folk Festival Data took 1.1444091796875e-05s
INFO | --- Analysis for data-incubator-moseley took 7.471804618835449s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.04528975486755371s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.00040149688720703125s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 0.26410388946533203s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.020399808883666992s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 8.940696716308594e-05s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 9.298324584960938e-06s
INFO | --- Analysis for data-incubator-musicbrainz took 2.4881093502044678s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 2.4619252681732178s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.000606536865234375s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 0.26373791694641113s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.022265911102294922s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for NASA Space Flight & Astronaut data in RDF took 8.225440979003906e-05s
Believability | Calculation of trust value for NASA Space Flight & Astronaut data in RDF took 9.5367431640625e-06s
INFO | --- Analysis for data-incubator-nasa took 29.033071041107178s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 0.050588130950927734s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 0.26308465003967285s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.021033048629760742s
Interlinking | Calculation of Degree of Connection for Airport data from Our Airports published as RDF took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for Airport data from Our Airports published as RDF took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 8.58306884765625e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 9.298324584960938e-06s
INFO | --- Analysis for data-incubator-our-airports took 2.46592378616333s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 0.04790234565734863s
Availability | VoID file availability check for Pokedex data in RDF took 0.0006825923919677734s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 0.26831722259521484s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.021620512008666992s
Interlinking | Calculation of Degree of Connection for Pokedex data in RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Pokedex data in RDF took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 9.298324584960938e-05s
Believability | Calculation of trust value for Pokedex data in RDF took 1.1205673217773438e-05s
INFO | --- Analysis for data-incubator-pokedex took 3.2815980911254883s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.04481911659240723s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 0.26148223876953125s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.021754980087280273s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 8.7738037109375e-05s
Believability | Calculation of trust value for Scottish Mountaineering Council Journals Issues 1-36 took 1.1444091796875e-05s
INFO | --- Analysis for data-incubator-smcjournals took 2.4887259006500244s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 0.5830469131469727s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.0005395412445068359s
Extra | Recovery of all triples for data.open.ac.uk, Linked Data from the Open University took 15.845578908920288s
Performance | Total latancy measurement for data.open.ac.uk, Linked Data from the Open University took 1.2314565181732178s
Amount of data | Number of triples check for data.open.ac.uk, Linked Data from the Open University took 20.492933750152588s
Interoperability | New terms check for data.open.ac.uk, Linked Data from the Open University took 1.4971706867218018s
Versatility | Languages check for data.open.ac.uk, Linked Data from the Open University took 30.28875994682312s
Interpretability | Number of blank nodes check for data.open.ac.uk, Linked Data from the Open University took 30.286816835403442s
Security | Check HTTPS for data.open.ac.uk, Linked Data from the Open University took 0.21889233589172363s
Interpretability | RDF structures check for data.open.ac.uk, Linked Data from the Open University took 0.5371692180633545s
Versatility | Serialization formats check for data.open.ac.uk, Linked Data from the Open University took 0.3681449890136719s
Availability | RDF dump link check for data.open.ac.uk, Linked Data from the Open University took 0.3175628185272217s
License | MR license check for data.open.ac.uk, Linked Data from the Open University took 0.39371752738952637s
License | HR license check for data.open.ac.uk, Linked Data from the Open University took 30.305668592453003s
Amount of data | Number of property check for data.open.ac.uk, Linked Data from the Open University took 0.9303836822509766s
Understandability | Number of label check for data.open.ac.uk, Linked Data from the Open University took 22.58336305618286s
Understandability | URI regex check for data.open.ac.uk, Linked Data from the Open University took 1.1698002815246582s
Understandability | Vocabs check for data.open.ac.uk, Linked Data from the Open University took 0.33545398712158203s
Verifiability | Authors check for data.open.ac.uk, Linked Data from the Open University took 0.7030127048492432s
Verifiability | Publishers check for data.open.ac.uk, Linked Data from the Open University took 0.35393428802490234s
Performance | Throughput check for data.open.ac.uk, Linked Data from the Open University took 12.333887815475464s
Amount of data | Check the number of entities for data.open.ac.uk, Linked Data from the Open University took 6.985664367675781e-05s
Verifiability | Contribs. check for data.open.ac.uk, Linked Data from the Open University took 0.3890976905822754s
Interlinking | sameAs chians check for data.open.ac.uk, Linked Data from the Open University took 12.872275352478027s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.4131355285644531s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.37600088119506836s
Timeliness | dataset update frequency check for data.open.ac.uk, Linked Data from the Open University took 0.5788543224334717s
Currency | Creation date check for data.open.ac.uk, Linked Data from the Open University took 1.0828566551208496s
Currency | Modification date check for data.open.ac.uk, Linked Data from the Open University took 0.9372663497924805s
Rep.Conc. | URIs length for data.open.ac.uk, Linked Data from the Open University took 36.41123843193054s
Interoperability | New vocabularies check for data.open.ac.uk, Linked Data from the Open University took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for data.open.ac.uk, Linked Data from the Open University took 0.3973658084869385s
Accuracy | Check Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.32170939445495605s
Accuracy | Check Inverse Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.3855922222137451s
Accuracy | Check Empty annotation labels for data.open.ac.uk, Linked Data from the Open University took 34.768425941467285s
Accuracy | Check White space in annotation for data.open.ac.uk, Linked Data from the Open University took 2.924129009246826s
Accuracy | Check Datatype consistency for data.open.ac.uk, Linked Data from the Open University took 5.03915548324585s
Consistency | Disjoint class check for data.open.ac.uk, Linked Data from the Open University took 0.672875165939331s
Consistency | Check Misplaced properties for data.open.ac.uk, Linked Data from the Open University took 0.9013516902923584s
Consistency | Misplaced classes for data.open.ac.uk, Linked Data from the Open University took 7.823470830917358s
Consistency | Check Ontology hijacking for data.open.ac.uk, Linked Data from the Open University took 25.201034545898438s
Consistency | Check Invalid usage of undefined classes for data.open.ac.uk, Linked Data from the Open University took 1.3234515190124512s
Consistency | Check Invalid usage of undefined properties for data.open.ac.uk, Linked Data from the Open University took 1.6545727252960205s
Conciseness | Check Extensional conciseness for data.open.ac.uk, Linked Data from the Open University took 2.8183016777038574s
Conciseness | Check Intensional conciseness for data.open.ac.uk, Linked Data from the Open University took 0.5520505905151367s
Security | Sign check for data.open.ac.uk, Linked Data from the Open University took 0.3195171356201172s
Availability | Check URIs Dereferenciability for data.open.ac.uk, Linked Data from the Open University took 0.08066320419311523s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 0.5414178371429443s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.020563602447509766s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 6.699562072753906e-05s
Interoperability | Check the re-using of existing vocabs for data.open.ac.uk, Linked Data from the Open University took 1.6689300537109375e-06s
Believability | Calculation of trust value for data.open.ac.uk, Linked Data from the Open University took 6.9141387939453125e-06s
INFO | --- Analysis for data-open-ac-uk took 668.5463864803314s
Availability | SPARQL endpoint availability check for Persée in RDF took 0.72495436668396s
Availability | VoID file availability check for Persée in RDF took 0.0007433891296386719s
Extra | Recovery of all triples for Persée in RDF took 1.1669397354125977s
Performance | Total latancy measurement for Persée in RDF took 0.5899934768676758s
Amount of data | Number of triples check for Persée in RDF took 1.1194713115692139s
Interoperability | New terms check for Persée in RDF took 1.8759582042694092s
Versatility | Languages check for Persée in RDF took 120.30660033226013s
Interpretability | Number of blank nodes check for Persée in RDF took 0.5285415649414062s
Interpretability | RDF structures check for Persée in RDF took 0.918687105178833s
Versatility | Serialization formats check for Persée in RDF took 1.1958303451538086s
Availability | RDF dump link check for Persée in RDF took 0.3629636764526367s
License | MR license check for Persée in RDF took 1.927234172821045s
License | HR license check for Persée in RDF took 38.350056171417236s
Amount of data | Number of property check for Persée in RDF took 0.1783583164215088s
Understandability | Number of label check for Persée in RDF took 2.343864917755127s
Understandability | URI regex check for Persée in RDF took 1.1738803386688232s
Understandability | Vocabs check for Persée in RDF took 1.0563244819641113s
Verifiability | Authors check for Persée in RDF took 0.3310885429382324s
Verifiability | Publishers check for Persée in RDF took 0.17656302452087402s
Performance | Throughput check for Persée in RDF took 12.277605772018433s
Amount of data | Check the number of entities for Persée in RDF took 7.319450378417969e-05s
Verifiability | Contribs. check for Persée in RDF took 0.359879732131958s
Interlinking | sameAs chians check for Persée in RDF took 0.2851104736328125s
Interlinking | skos check for Persée in RDF took 1.0887374877929688s
Interlinking | skos check for Persée in RDF took 0.26366233825683594s
Timeliness | dataset update frequency check for Persée in RDF took 1.042771339416504s
Currency | Creation date check for Persée in RDF took 0.9325966835021973s
Currency | Modification date check for Persée in RDF took 0.5500335693359375s
Rep.Conc. | URIs length for Persée in RDF took 6.715926647186279s
Interoperability | New vocabularies check for Persée in RDF took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Persée in RDF took 0.31038737297058105s
Accuracy | Check Functional Property for Persée in RDF took 0.5058028697967529s
Accuracy | Check Inverse Functional Property for Persée in RDF took 0.4507906436920166s
Accuracy | Check Empty annotation labels for Persée in RDF took 3.4721200466156006s
Accuracy | Check White space in annotation for Persée in RDF took 0.038419485092163086s
Accuracy | Check Datatype consistency for Persée in RDF took 0.026705265045166016s
Consistency | Disjoint class check for Persée in RDF took 1.5347926616668701s
Consistency | Check Misplaced properties for Persée in RDF took 3.0111207962036133s
Consistency | Misplaced classes for Persée in RDF took 0.4064912796020508s
Consistency | Check Ontology hijacking for Persée in RDF took 6.885827541351318s
Consistency | Check Invalid usage of undefined classes for Persée in RDF took 1.316749095916748s
Consistency | Check Invalid usage of undefined properties for Persée in RDF took 3.9454028606414795s
Conciseness | Check Extensional conciseness for Persée in RDF took 0.03274035453796387s
Conciseness | Check Intensional conciseness for Persée in RDF took 0.13527917861938477s
Security | Sign check for Persée in RDF took 1.1179306507110596s
Availability | Check URIs Dereferenciability for Persée in RDF took 1316.8070542812347s
Completeness | Calculation of interlinking completeness for Persée in RDF took 0.3589463233947754s
Reputation | Calculation of the PageRank for Persée in RDF took 0.02126002311706543s
Interlinking | Calculation of Degree of Connection for Persée in RDF took 6.937980651855469e-05s
Interlinking | Calculation of Centrality for Persée in RDF took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 0.00010991096496582031s
Interoperability | Check the re-using of existing vocabs for Persée in RDF took 1.6689300537109375e-06s
Believability | Calculation of trust value for Persée in RDF took 1.1444091796875e-05s
INFO | --- Analysis for data-persee-fr took 1580.9420976638794s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 0.993466854095459s
Availability | VoID file availability check for data-szepmuveszeti-hu took 0.0005817413330078125s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 0.2877192497253418s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.020635366439819336s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.00011444091796875s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 1.049041748046875e-05s
INFO | --- Analysis for data-szepmuveszeti-hu took 87.56780624389648s
Availability | SPARQL endpoint availability check for Open Data Web took 100.37183356285095s
Availability | VoID file availability check for Open Data Web took 0.0005326271057128906s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.2670712471008301s
Reputation | Calculation of the PageRank for Open Data Web took 0.020254850387573242s
Interlinking | Calculation of Degree of Connection for Open Data Web took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.2901763916015625e-05s
Believability | Calculation of trust value for Open Data Web took 9.5367431640625e-06s
INFO | --- Analysis for data.odw.tw took 151.1177740097046s
Availability | SPARQL endpoint availability check for datahub took 8.96453857421875e-05s
Availability | VoID file availability check for datahub took 0.0006089210510253906s
Completeness | Calculation of interlinking completeness for datahub took 0.26964664459228516s
Reputation | Calculation of the PageRank for datahub took 0.021813154220581055s
Interlinking | Calculation of Degree of Connection for datahub took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for datahub took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for datahub took 4.649162292480469e-05s
Believability | Calculation of trust value for datahub took 1.1205673217773438e-05s
INFO | --- Analysis for datahub took 3.8243303298950195s
Availability | SPARQL endpoint availability check for Open Datasets in South Korea took 4.618593215942383s
Availability | VoID file availability check for Open Datasets in South Korea took 0.0006208419799804688s
Completeness | Calculation of interlinking completeness for Open Datasets in South Korea took 0.2631382942199707s
Reputation | Calculation of the PageRank for Open Datasets in South Korea took 0.020355224609375s
Interlinking | Calculation of Degree of Connection for Open Datasets in South Korea took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Datasets in South Korea took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Open Datasets in South Korea took 2.9802322387695312e-05s
Believability | Calculation of trust value for Open Datasets in South Korea took 7.3909759521484375e-06s
INFO | --- Analysis for datahub-kr-datamap took 13.095072984695435s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.31507158279418945s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0005397796630859375s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.27069735527038574s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.02146458625793457s
Interlinking | Calculation of Degree of Connection for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 6.723403930664062e-05s
Believability | Calculation of trust value for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.1920928955078125e-05s
INFO | --- Analysis for dataturcyl-lod-for-tourists-in-castilla-y-leon-spain took 4.815937042236328s
Availability | SPARQL endpoint availability check for datos-artium-org took 21.1825954914093s
Availability | VoID file availability check for datos-artium-org took 0.0006971359252929688s
Completeness | Calculation of interlinking completeness for datos-artium-org took 0.2726876735687256s
Reputation | Calculation of the PageRank for datos-artium-org took 0.02183985710144043s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for datos-artium-org took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.00011658668518066406s
Believability | Calculation of trust value for datos-artium-org took 1.1920928955078125e-05s
INFO | --- Analysis for datos-artium-org took 247.48741006851196s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 1.7321419715881348s
Availability | VoID file availability check for Datos.bcn.cl took 0.0003743171691894531s
Extra | Recovery of all triples for Datos.bcn.cl took 28.112945318222046s
Performance | Total latancy measurement for Datos.bcn.cl took 6.0964343547821045s
Amount of data | Number of triples check for Datos.bcn.cl took 4.512376546859741s
Interoperability | New terms check for Datos.bcn.cl took 3.8591229915618896s
Versatility | Languages check for Datos.bcn.cl took 288.67188358306885s
Interpretability | Number of blank nodes check for Datos.bcn.cl took 1.2329862117767334s
Security | Check HTTPS for Datos.bcn.cl took 0.7270982265472412s
Interpretability | RDF structures check for Datos.bcn.cl took 1.317253828048706s
Versatility | Serialization formats check for Datos.bcn.cl took 1.3448233604431152s
Availability | RDF dump link check for Datos.bcn.cl took 1.1978764533996582s
License | MR license check for Datos.bcn.cl took 1.210340976715088s
License | HR license check for Datos.bcn.cl took 32.72362661361694s
Amount of data | Number of property check for Datos.bcn.cl took 1.2240259647369385s
Understandability | Number of label check for Datos.bcn.cl took 1.5071427822113037s
Understandability | URI regex check for Datos.bcn.cl took 2.3932363986968994s
Understandability | Vocabs check for Datos.bcn.cl took 1.1886627674102783s
Verifiability | Authors check for Datos.bcn.cl took 1.3415915966033936s
Verifiability | Publishers check for Datos.bcn.cl took 1.1945443153381348s
Performance | Throughput check for Datos.bcn.cl took 12.110135793685913s
Amount of data | Check the number of entities for Datos.bcn.cl took 7.009506225585938e-05s
Verifiability | Contribs. check for Datos.bcn.cl took 1.1893219947814941s
Interlinking | sameAs chians check for Datos.bcn.cl took 1.2195258140563965s
Interlinking | skos check for Datos.bcn.cl took 1.2137460708618164s
Interlinking | skos check for Datos.bcn.cl took 1.2056488990783691s
Timeliness | dataset update frequency check for Datos.bcn.cl took 1.2050230503082275s
Currency | Creation date check for Datos.bcn.cl took 2.536543369293213s
Currency | Modification date check for Datos.bcn.cl took 1.206862211227417s
Rep.Conc. | URIs length for Datos.bcn.cl took 24.698092937469482s
Interoperability | New vocabularies check for Datos.bcn.cl took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for Datos.bcn.cl took 1.2889504432678223s
Accuracy | Check Functional Property for Datos.bcn.cl took 1.3243012428283691s
Accuracy | Check Inverse Functional Property for Datos.bcn.cl took 1.1911320686340332s
Accuracy | Check Empty annotation labels for Datos.bcn.cl took 11.184107303619385s
Accuracy | Check White space in annotation for Datos.bcn.cl took 0.3207559585571289s
Accuracy | Check Datatype consistency for Datos.bcn.cl took 0.26304173469543457s
Consistency | Disjoint class check for Datos.bcn.cl took 1.1922101974487305s
Consistency | Check Misplaced properties for Datos.bcn.cl took 7.605212688446045s
Consistency | Misplaced classes for Datos.bcn.cl took 2.037135601043701s
Consistency | Check Ontology hijacking for Datos.bcn.cl took 8.645115613937378s
Consistency | Check Invalid usage of undefined classes for Datos.bcn.cl took 1.3875722885131836s
Consistency | Check Invalid usage of undefined properties for Datos.bcn.cl took 7.29206109046936s
Conciseness | Check Extensional conciseness for Datos.bcn.cl took 0.29842162132263184s
Conciseness | Check Intensional conciseness for Datos.bcn.cl took 1.5294501781463623s
Security | Sign check for Datos.bcn.cl took 1.3400299549102783s
Availability | Check URIs Dereferenciability for Datos.bcn.cl took 7944.825870037079s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 0.6762917041778564s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.021447420120239258s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 9.894371032714844e-05s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 0.000141143798828125s
Interoperability | Check the re-using of existing vocabs for Datos.bcn.cl took 1.9073486328125e-06s
Believability | Calculation of trust value for Datos.bcn.cl took 1.0013580322265625e-05s
INFO | --- Analysis for datos-bcn-cl took 8733.793962717056s
Availability | SPARQL endpoint availability check for datos.bne.es took 0.7135715484619141s
Availability | VoID file availability check for datos.bne.es took 0.0006883144378662109s
Extra | Recovery of all triples for datos.bne.es took 156.7184021472931s
Performance | Total latancy measurement for datos.bne.es took 5.314583778381348s
Amount of data | Number of triples check for datos.bne.es took 2.8197412490844727s
Interoperability | New terms check for datos.bne.es took 4.351321697235107s
Versatility | Languages check for datos.bne.es took 60.97728490829468s
Interpretability | Number of blank nodes check for datos.bne.es took 2.239001750946045s
Security | Check HTTPS for datos.bne.es took 2.0781798362731934s
Interpretability | RDF structures check for datos.bne.es took 2.360525608062744s
Versatility | Serialization formats check for datos.bne.es took 0.5705568790435791s
Availability | RDF dump link check for datos.bne.es took 0.43024396896362305s
License | MR license check for datos.bne.es took 2.609194040298462s
License | HR license check for datos.bne.es took 61.97811269760132s
Amount of data | Number of property check for datos.bne.es took 2.241426706314087s
Understandability | Number of label check for datos.bne.es took 1.3128013610839844s
Understandability | URI regex check for datos.bne.es took 2.7795422077178955s
Understandability | Vocabs check for datos.bne.es took 2.292295455932617s
Verifiability | Authors check for datos.bne.es took 2.362067699432373s
Verifiability | Publishers check for datos.bne.es took 0.42240476608276367s
Performance | Throughput check for datos.bne.es took 23.949129819869995s
Amount of data | Check the number of entities for datos.bne.es took 6.842613220214844e-05s
Verifiability | Contribs. check for datos.bne.es took 2.2047383785247803s
Interlinking | sameAs chians check for datos.bne.es took 0.4558064937591553s
Interlinking | skos check for datos.bne.es took 0.5412085056304932s
Interlinking | skos check for datos.bne.es took 2.1659553050994873s
Timeliness | dataset update frequency check for datos.bne.es took 0.4660351276397705s
Currency | Creation date check for datos.bne.es took 2.6153628826141357s
Currency | Modification date check for datos.bne.es took 4.521161794662476s
Rep.Conc. | URIs length for datos.bne.es took 65.19463539123535s
Interoperability | New vocabularies check for datos.bne.es took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for datos.bne.es took 2.236992835998535s
Accuracy | Check Functional Property for datos.bne.es took 0.3496108055114746s
Accuracy | Check Inverse Functional Property for datos.bne.es took 0.35205864906311035s
Accuracy | Check Empty annotation labels for datos.bne.es took 52.89469861984253s
Accuracy | Check White space in annotation for datos.bne.es took 1.6041374206542969s
Accuracy | Check Datatype consistency for datos.bne.es took 1.2808716297149658s
Consistency | Disjoint class check for datos.bne.es took 0.3943502902984619s
Consistency | Check Misplaced properties for datos.bne.es took 10.534996271133423s
Consistency | Misplaced classes for datos.bne.es took 4.404810428619385s
Consistency | Check Ontology hijacking for datos.bne.es took 49.387288331985474s
Consistency | Check Invalid usage of undefined classes for datos.bne.es took 1.315478801727295s
Consistency | Check Invalid usage of undefined properties for datos.bne.es took 9.580045461654663s
Conciseness | Check Extensional conciseness for datos.bne.es took 1.3760690689086914s
Conciseness | Check Intensional conciseness for datos.bne.es took 0.38402533531188965s
Security | Sign check for datos.bne.es took 3.0524730682373047s
Availability | Check URIs Dereferenciability for datos.bne.es took 9.731042861938477s
Completeness | Calculation of interlinking completeness for datos.bne.es took 0.4723525047302246s
Reputation | Calculation of the PageRank for datos.bne.es took 0.02074718475341797s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for datos.bne.es took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.00011801719665527344s
Interoperability | Check the re-using of existing vocabs for datos.bne.es took 1.9073486328125e-06s
Believability | Calculation of trust value for datos.bne.es took 1.1444091796875e-05s
INFO | --- Analysis for datos-bne-es took 704.3400361537933s
Availability | SPARQL endpoint availability check for dbacademic took 0.05052971839904785s
Availability | VoID file availability check for dbacademic took 0.0005035400390625s
Completeness | Calculation of interlinking completeness for dbacademic took 0.27395153045654297s
Reputation | Calculation of the PageRank for dbacademic took 0.02265453338623047s
Interlinking | Calculation of Degree of Connection for dbacademic took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for dbacademic took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for dbacademic took 3.0994415283203125e-05s
Believability | Calculation of trust value for dbacademic took 3.814697265625e-06s
INFO | --- Analysis for dbacademic took 2.504842519760132s
Availability | SPARQL endpoint availability check for DBkWik took 97.82824230194092s
Availability | VoID file availability check for DBkWik took 0.0006535053253173828s
Extra | Recovery of all triples for DBkWik took 2.1738061904907227s
Performance | Total latancy measurement for DBkWik took 0.418820858001709s
Amount of data | Number of triples check for DBkWik took 5.884391784667969s
Interoperability | New terms check for DBkWik took 4.790500640869141s
Versatility | Languages check for DBkWik took 60.47512602806091s
Interpretability | Number of blank nodes check for DBkWik took 10.077956438064575s
Interpretability | RDF structures check for DBkWik took 3.125800609588623s
Versatility | Serialization formats check for DBkWik took 0.7270193099975586s
Availability | RDF dump link check for DBkWik took 2.634387254714966s
License | MR license check for DBkWik took 0.5258123874664307s
License | HR license check for DBkWik took 61.00214242935181s
Amount of data | Number of property check for DBkWik took 0.15898990631103516s
Understandability | Number of label check for DBkWik took 2.3795976638793945s
Understandability | URI regex check for DBkWik took 1.7338917255401611s
Understandability | Vocabs check for DBkWik took 0.10359907150268555s
Verifiability | Authors check for DBkWik took 0.10709762573242188s
Verifiability | Publishers check for DBkWik took 0.08403372764587402s
Performance | Throughput check for DBkWik took 105.98698997497559s
Amount of data | Check the number of entities for DBkWik took 7.2479248046875e-05s
Verifiability | Contribs. check for DBkWik took 0.10883545875549316s
Interlinking | sameAs chians check for DBkWik took 0.42026758193969727s
Interlinking | skos check for DBkWik took 0.49976110458374023s
Interlinking | skos check for DBkWik took 0.07592654228210449s
Timeliness | dataset update frequency check for DBkWik took 0.2319505214691162s
Currency | Creation date check for DBkWik took 0.468242883682251s
Currency | Modification date check for DBkWik took 0.26508307456970215s
Rep.Conc. | URIs length for DBkWik took 11.357643604278564s
Interoperability | New vocabularies check for DBkWik took 52.097946882247925s
Consistency | Deprecated classes/propertiers check for DBkWik took 10.054301023483276s
Accuracy | Check Datatype consistency for DBkWik took 0.040200233459472656s
Consistency | Disjoint class check for DBkWik took 1.5874083042144775s
Consistency | Check Misplaced properties for DBkWik took 11.783443450927734s
Consistency | Misplaced classes for DBkWik took 1.8166086673736572s
Consistency | Check Ontology hijacking for DBkWik took 1.8712434768676758s
Consistency | Check Invalid usage of undefined classes for DBkWik took 1.311034917831421s
Consistency | Check Invalid usage of undefined properties for DBkWik took 12.113101243972778s
Conciseness | Check Extensional conciseness for DBkWik took 0.034540653228759766s
Conciseness | Check Intensional conciseness for DBkWik took 95.23142862319946s
Security | Sign check for DBkWik took 0.9148321151733398s
Availability | Check URIs Dereferenciability for DBkWik took 9.745003700256348s
Completeness | Calculation of interlinking completeness for DBkWik took 0.30989766120910645s
Reputation | Calculation of the PageRank for DBkWik took 0.020456790924072266s
Interlinking | Calculation of Degree of Connection for DBkWik took 2.3365020751953125e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for DBkWik took 6.794929504394531e-05s
Interoperability | Check the re-using of existing vocabs for DBkWik took 13.046151876449585s
Believability | Calculation of trust value for DBkWik took 1.1920928955078125e-05s
INFO | --- Analysis for dbkwik took 5479.71780872345s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 8.916854858398438e-05s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 0.2650585174560547s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.0206453800201416s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.00011682510375976562s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 1.0967254638671875e-05s
INFO | --- Analysis for dblp-deusto-gnoss took 5.602530241012573s
Availability | SPARQL endpoint availability check for dblp Knowledge Graph took 0.2976245880126953s
Availability | VoID file availability check for dblp Knowledge Graph took 0.0006570816040039062s
Extra | Recovery of all triples for dblp Knowledge Graph took 56.82182216644287s
Performance | Total latancy measurement for dblp Knowledge Graph took 0.7278416156768799s
Amount of data | Number of triples check for dblp Knowledge Graph took 0.1431899070739746s
Interoperability | New terms check for dblp Knowledge Graph took 1.8655731678009033s
Versatility | Languages check for dblp Knowledge Graph took 0.2844858169555664s
Interpretability | Number of blank nodes check for dblp Knowledge Graph took 3.622753620147705s
Interpretability | RDF structures check for dblp Knowledge Graph took 0.14801406860351562s
Versatility | Serialization formats check for dblp Knowledge Graph took 0.17170262336730957s
Availability | RDF dump link check for dblp Knowledge Graph took 0.13097596168518066s
License | MR license check for dblp Knowledge Graph took 0.1596517562866211s
License | HR license check for dblp Knowledge Graph took 30.12715482711792s
Amount of data | Number of property check for dblp Knowledge Graph took 0.1259629726409912s
Understandability | Number of label check for dblp Knowledge Graph took 0.4639763832092285s
Understandability | URI regex check for dblp Knowledge Graph took 0.26566123962402344s
Understandability | Vocabs check for dblp Knowledge Graph took 0.14339065551757812s
Verifiability | Authors check for dblp Knowledge Graph took 0.14876914024353027s
Verifiability | Publishers check for dblp Knowledge Graph took 0.1575164794921875s
Performance | Throughput check for dblp Knowledge Graph took 10.355619430541992s
Amount of data | Check the number of entities for dblp Knowledge Graph took 6.723403930664062e-05s
Verifiability | Contribs. check for dblp Knowledge Graph took 0.1459336280822754s
Interlinking | sameAs chians check for dblp Knowledge Graph took 0.20873045921325684s
Interlinking | skos check for dblp Knowledge Graph took 0.1329493522644043s
Interlinking | skos check for dblp Knowledge Graph took 0.1367785930633545s
Timeliness | dataset update frequency check for dblp Knowledge Graph took 0.14844298362731934s
Currency | Creation date check for dblp Knowledge Graph took 0.2676239013671875s
Currency | Modification date check for dblp Knowledge Graph took 0.3043694496154785s
Rep.Conc. | URIs length for dblp Knowledge Graph took 27.583417654037476s
Interoperability | New vocabularies check for dblp Knowledge Graph took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for dblp Knowledge Graph took 0.12032818794250488s
Accuracy | Check Functional Property for dblp Knowledge Graph took 0.11857819557189941s
Accuracy | Check Inverse Functional Property for dblp Knowledge Graph took 0.11814713478088379s
Accuracy | Check Empty annotation labels for dblp Knowledge Graph took 17.29960036277771s
Accuracy | Check White space in annotation for dblp Knowledge Graph took 3.0000498294830322s
Accuracy | Check Datatype consistency for dblp Knowledge Graph took 5.985049486160278s
Consistency | Disjoint class check for dblp Knowledge Graph took 0.11774349212646484s
Consistency | Check Misplaced properties for dblp Knowledge Graph took 0.24544262886047363s
Consistency | Check Ontology hijacking for dblp Knowledge Graph took 18.214513301849365s
Consistency | Check Invalid usage of undefined classes for dblp Knowledge Graph took 17821.665687561035s
Consistency | Check Invalid usage of undefined properties for dblp Knowledge Graph took 3.837601661682129s
Conciseness | Check Extensional conciseness for dblp Knowledge Graph took 2.690859079360962s
Conciseness | Check Intensional conciseness for dblp Knowledge Graph took 0.1837759017944336s
Security | Sign check for dblp Knowledge Graph took 0.1434943675994873s
Availability | Check URIs Dereferenciability for dblp Knowledge Graph took 3.030082941055298s
Completeness | Calculation of interlinking completeness for dblp Knowledge Graph took 0.698462724685669s
Reputation | Calculation of the PageRank for dblp Knowledge Graph took 0.020886898040771484s
Interlinking | Calculation of Degree of Connection for dblp Knowledge Graph took 2.384185791015625e-05s
Interlinking | Calculation of Centrality for dblp Knowledge Graph took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for dblp Knowledge Graph took 2.8133392333984375e-05s
Interoperability | Check the re-using of existing vocabs for dblp Knowledge Graph took 1.9073486328125e-06s
Believability | Calculation of trust value for dblp Knowledge Graph took 1.049041748046875e-05s
INFO | --- Analysis for dblp-kg took 18228.931309223175s
Availability | SPARQL endpoint availability check for DBnary took 0.2410888671875s
Availability | VoID file availability check for DBnary took 0.00041413307189941406s
Extra | Recovery of all triples for DBnary took 2.271947145462036s
Performance | Total latancy measurement for DBnary took 0.3691129684448242s
Amount of data | Number of triples check for DBnary took 1.217050313949585s
Interoperability | New terms check for DBnary took 3.6327402591705322s
Versatility | Languages check for DBnary took 62.35444736480713s
Interpretability | Number of blank nodes check for DBnary took 3.7693307399749756s
Security | Check HTTPS for DBnary took 0.1471097469329834s
Interpretability | RDF structures check for DBnary took 0.09941864013671875s
Versatility | Serialization formats check for DBnary took 0.34694790840148926s
Availability | RDF dump link check for DBnary took 0.06339669227600098s
License | MR license check for DBnary took 0.10345077514648438s
License | HR license check for DBnary took 61.27960729598999s
Amount of data | Number of property check for DBnary took 0.09331679344177246s
Understandability | Number of label check for DBnary took 0.8488702774047852s
Understandability | URI regex check for DBnary took 0.13567900657653809s
Understandability | Vocabs check for DBnary took 0.24405956268310547s
Verifiability | Authors check for DBnary took 0.06595897674560547s
Verifiability | Publishers check for DBnary took 0.06250929832458496s
Performance | Throughput check for DBnary took 10.321704387664795s
Amount of data | Check the number of entities for DBnary took 6.031990051269531e-05s
Verifiability | Contribs. check for DBnary took 0.0627443790435791s
Interlinking | sameAs chians check for DBnary took 0.09066414833068848s
Interlinking | skos check for DBnary took 0.41002988815307617s
Interlinking | skos check for DBnary took 0.062364816665649414s
Timeliness | dataset update frequency check for DBnary took 0.11610555648803711s
Currency | Creation date check for DBnary took 0.14963030815124512s
Currency | Modification date check for DBnary took 0.1524512767791748s
Rep.Conc. | URIs length for DBnary took 11.04657244682312s
Interoperability | New vocabularies check for DBnary took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for DBnary took 0.08641648292541504s
Accuracy | Check Functional Property for DBnary took 0.25006985664367676s
Accuracy | Check Inverse Functional Property for DBnary took 0.2048964500427246s
Accuracy | Check Empty annotation labels for DBnary took 0.4305093288421631s
Accuracy | Check White space in annotation for DBnary took 0.03024744987487793s
Accuracy | Check Datatype consistency for DBnary took 0.027417659759521484s
Consistency | Disjoint class check for DBnary took 0.08423781394958496s
Consistency | Check Misplaced properties for DBnary took 8.615588665008545s
Consistency | Misplaced classes for DBnary took 0.21193552017211914s
Consistency | Check Ontology hijacking for DBnary took 1.8227384090423584s
Consistency | Check Invalid usage of undefined classes for DBnary took 1.3998146057128906s
Consistency | Check Invalid usage of undefined properties for DBnary took 9.775458574295044s
Conciseness | Check Extensional conciseness for DBnary took 0.03603100776672363s
Conciseness | Check Intensional conciseness for DBnary took 0.1566929817199707s
Security | Sign check for DBnary took 0.08251357078552246s
Availability | Check URIs Dereferenciability for DBnary took 10.476742029190063s
Completeness | Calculation of interlinking completeness for DBnary took 0.2699875831604004s
Reputation | Calculation of the PageRank for DBnary took 0.020742416381835938s
Interlinking | Calculation of Degree of Connection for DBnary took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBnary took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for DBnary took 6.0558319091796875e-05s
Interoperability | Check the re-using of existing vocabs for DBnary took 1.6689300537109375e-06s
Believability | Calculation of trust value for DBnary took 1.2159347534179688e-05s
INFO | --- Analysis for dbnary took 294.4020254611969s
Availability | SPARQL endpoint availability check for DBpedia took 0.8909621238708496s
Availability | VoID file availability check for DBpedia took 0.0013310909271240234s
Extra | Recovery of all triples for DBpedia took 3.7387826442718506s
Performance | Total latancy measurement for DBpedia took 2.6873910427093506s
Amount of data | Number of triples check for DBpedia took 0.9669322967529297s
Interoperability | New terms check for DBpedia took 5.469032526016235s
Versatility | Languages check for DBpedia took 32.08725905418396s
Interpretability | Number of blank nodes check for DBpedia took 0.543015718460083s
Security | Check HTTPS for DBpedia took 0.32326269149780273s
Interpretability | RDF structures check for DBpedia took 0.8074448108673096s
Versatility | Serialization formats check for DBpedia took 0.6308689117431641s
Availability | RDF dump link check for DBpedia took 0.5515556335449219s
License | MR license check for DBpedia took 1.1999516487121582s
License | HR license check for DBpedia took 32.302557706832886s
Amount of data | Number of property check for DBpedia took 0.5569431781768799s
Understandability | Number of label check for DBpedia took 4.8234336376190186s
Understandability | URI regex check for DBpedia took 1.0844907760620117s
Understandability | Vocabs check for DBpedia took 0.6018707752227783s
Verifiability | Authors check for DBpedia took 0.6030972003936768s
Verifiability | Publishers check for DBpedia took 0.5766685009002686s
Performance | Throughput check for DBpedia took 10.732999086380005s
Amount of data | Check the number of entities for DBpedia took 6.699562072753906e-05s
Verifiability | Contribs. check for DBpedia took 0.5599443912506104s
Interlinking | sameAs chians check for DBpedia took 2.7260375022888184s
Interlinking | skos check for DBpedia took 0.8894751071929932s
Interlinking | skos check for DBpedia took 0.5374374389648438s
Timeliness | dataset update frequency check for DBpedia took 0.5590314865112305s
Currency | Creation date check for DBpedia took 1.1368424892425537s
Currency | Modification date check for DBpedia took 1.1178312301635742s
Rep.Conc. | URIs length for DBpedia took 35.55160212516785s
Interoperability | New vocabularies check for DBpedia took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for DBpedia took 0.5407350063323975s
Accuracy | Check Functional Property for DBpedia took 0.550133466720581s
Accuracy | Check Inverse Functional Property for DBpedia took 0.5490562915802002s
Accuracy | Check Empty annotation labels for DBpedia took 2.8969879150390625s
Accuracy | Check White space in annotation for DBpedia took 0.029395580291748047s
Accuracy | Check Datatype consistency for DBpedia took 0.027477502822875977s
Consistency | Disjoint class check for DBpedia took 0.5411794185638428s
Consistency | Check Misplaced properties for DBpedia took 31.61486315727234s
Consistency | Misplaced classes for DBpedia took 2.858367681503296s
Consistency | Check Ontology hijacking for DBpedia took 3.190948009490967s
Consistency | Check Invalid usage of undefined classes for DBpedia took 1.3049373626708984s
Consistency | Check Invalid usage of undefined properties for DBpedia took 2.8460853099823s
Conciseness | Check Extensional conciseness for DBpedia took 0.03246045112609863s
Conciseness | Check Intensional conciseness for DBpedia took 2.5204977989196777s
Security | Sign check for DBpedia took 0.5546455383300781s
Availability | Check URIs Dereferenciability for DBpedia took 4224.797193288803s
Completeness | Calculation of interlinking completeness for DBpedia took 0.623018741607666s
Reputation | Calculation of the PageRank for DBpedia took 0.021294116973876953s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.0008981227874755859s
Interoperability | Check the re-using of existing vocabs for DBpedia took 1.1920928955078125e-06s
Believability | Calculation of trust value for DBpedia took 1.0728836059570312e-05s
INFO | --- Analysis for dbpedia took 7859.724640369415s
Availability | SPARQL endpoint availability check for DBpedia abstract corpus took 9.083747863769531e-05s
Availability | VoID file availability check for DBpedia abstract corpus took 0.0006167888641357422s
Completeness | Calculation of interlinking completeness for DBpedia abstract corpus took 0.26511716842651367s
Reputation | Calculation of the PageRank for DBpedia abstract corpus took 0.02119135856628418s
Interlinking | Calculation of Degree of Connection for DBpedia abstract corpus took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for DBpedia abstract corpus took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for DBpedia abstract corpus took 7.224082946777344e-05s
Believability | Calculation of trust value for DBpedia abstract corpus took 1.049041748046875e-05s
INFO | --- Analysis for dbpedia-abstract-corpus took 7.0577991008758545s
Availability | SPARQL endpoint availability check for DBpedia Commons took 6.160018444061279s
Availability | VoID file availability check for DBpedia Commons took 0.0004534721374511719s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.26135778427124023s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.020337581634521484s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 7.152557373046875e-05s
Believability | Calculation of trust value for DBpedia Commons took 1.0013580322265625e-05s
INFO | --- Analysis for dbpedia-commons took 16.41791868209839s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 0.8434181213378906s
Availability | VoID file availability check for DBpedia in Greek took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 0.2808237075805664s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.020516633987426758s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.00018978118896484375s
Believability | Calculation of trust value for DBpedia in Greek took 8.106231689453125e-06s
INFO | --- Analysis for dbpedia-el took 6.791640520095825s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 0.40845656394958496s
Availability | VoID file availability check for DBpedia in Spanish took 0.0005033016204833984s
Extra | Recovery of all triples for DBpedia in Spanish took 2.607370376586914s
Performance | Total latancy measurement for DBpedia in Spanish took 42.669536113739014s
Amount of data | Number of triples check for DBpedia in Spanish took 2.0076255798339844s
Interoperability | New terms check for DBpedia in Spanish took 2.880563259124756s
Versatility | Languages check for DBpedia in Spanish took 62.13360905647278s
Interpretability | Number of blank nodes check for DBpedia in Spanish took 0.32892465591430664s
Security | Check HTTPS for DBpedia in Spanish took 0.13886499404907227s
Interpretability | RDF structures check for DBpedia in Spanish took 0.8261599540710449s
Versatility | Serialization formats check for DBpedia in Spanish took 0.5340051651000977s
Availability | RDF dump link check for DBpedia in Spanish took 0.3450660705566406s
License | MR license check for DBpedia in Spanish took 0.6924676895141602s
License | HR license check for DBpedia in Spanish took 64.84786605834961s
Amount of data | Number of property check for DBpedia in Spanish took 0.2724936008453369s
Understandability | Number of label check for DBpedia in Spanish took 1.2728841304779053s
Understandability | URI regex check for DBpedia in Spanish took 2.1361031532287598s
Understandability | Vocabs check for DBpedia in Spanish took 0.38373470306396484s
Verifiability | Authors check for DBpedia in Spanish took 0.2711958885192871s
Verifiability | Publishers check for DBpedia in Spanish took 0.26092100143432617s
Performance | Throughput check for DBpedia in Spanish took 68.68372821807861s
Amount of data | Check the number of entities for DBpedia in Spanish took 6.771087646484375e-05s
Verifiability | Contribs. check for DBpedia in Spanish took 0.26883578300476074s
Interlinking | sameAs chians check for DBpedia in Spanish took 0.6188552379608154s
Interlinking | skos check for DBpedia in Spanish took 0.4635927677154541s
Interlinking | skos check for DBpedia in Spanish took 0.20927810668945312s
Timeliness | dataset update frequency check for DBpedia in Spanish took 0.41170597076416016s
Currency | Creation date check for DBpedia in Spanish took 0.5421249866485596s
Currency | Modification date check for DBpedia in Spanish took 0.5321247577667236s
Rep.Conc. | URIs length for DBpedia in Spanish took 13.411048412322998s
Interoperability | New vocabularies check for DBpedia in Spanish took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Spanish took 10.833622455596924s
Accuracy | Check Functional Property for DBpedia in Spanish took 0.43321990966796875s
Accuracy | Check Inverse Functional Property for DBpedia in Spanish took 0.9043624401092529s
Accuracy | Check Datatype consistency for DBpedia in Spanish took 0.031662940979003906s
Consistency | Disjoint class check for DBpedia in Spanish took 0.718745231628418s
Consistency | Check Misplaced properties for DBpedia in Spanish took 26.394218683242798s
Consistency | Misplaced classes for DBpedia in Spanish took 1.2602488994598389s
Consistency | Check Ontology hijacking for DBpedia in Spanish took 2.6828787326812744s
Consistency | Check Invalid usage of undefined classes for DBpedia in Spanish took 1.3064823150634766s
Consistency | Check Invalid usage of undefined properties for DBpedia in Spanish took 12.726056098937988s
Conciseness | Check Extensional conciseness for DBpedia in Spanish took 0.03493690490722656s
Conciseness | Check Intensional conciseness for DBpedia in Spanish took 1.488163948059082s
Security | Sign check for DBpedia in Spanish took 0.44220638275146484s
Availability | Check URIs Dereferenciability for DBpedia in Spanish took 13.843190908432007s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 0.7239804267883301s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.021042823791503906s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 0.00010776519775390625s
Interoperability | Check the re-using of existing vocabs for DBpedia in Spanish took 9.5367431640625e-07s
Believability | Calculation of trust value for DBpedia in Spanish took 9.298324584960938e-06s
INFO | --- Analysis for dbpedia-es took 6580.972213506699s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 1.1349356174468994s
Availability | VoID file availability check for DBpedia in Basque took 0.0009961128234863281s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.26425981521606445s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.02134394645690918s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 3.075599670410156e-05s
Believability | Calculation of trust value for DBpedia in Basque took 9.298324584960938e-06s
INFO | --- Analysis for dbpedia-eu took 6.505028247833252s
Availability | SPARQL endpoint availability check for DBpedia in French took 0.13403058052062988s
Availability | VoID file availability check for DBpedia in French took 0.0005245208740234375s
Extra | Recovery of all triples for DBpedia in French took 83.59127926826477s
Performance | Total latancy measurement for DBpedia in French took 0.37270283699035645s
Amount of data | Number of triples check for DBpedia in French took 1.7711212635040283s
Interoperability | New terms check for DBpedia in French took 2.071070909500122s
Versatility | Languages check for DBpedia in French took 300.0299587249756s
Interpretability | Number of blank nodes check for DBpedia in French took 0.1418452262878418s
Security | Check HTTPS for DBpedia in French took 0.1706399917602539s
Interpretability | RDF structures check for DBpedia in French took 0.3928701877593994s
Versatility | Serialization formats check for DBpedia in French took 0.36828064918518066s
Availability | RDF dump link check for DBpedia in French took 6.128515243530273s
License | MR license check for DBpedia in French took 1.7900176048278809s
License | HR license check for DBpedia in French took 85.1326048374176s
Amount of data | Number of property check for DBpedia in French took 0.0963287353515625s
Understandability | Number of label check for DBpedia in French took 1.7355446815490723s
Understandability | URI regex check for DBpedia in French took 0.2931981086730957s
Understandability | Vocabs check for DBpedia in French took 0.15012121200561523s
Verifiability | Authors check for DBpedia in French took 0.2918813228607178s
Verifiability | Publishers check for DBpedia in French took 0.15137028694152832s
Performance | Throughput check for DBpedia in French took 10.358181715011597s
Amount of data | Check the number of entities for DBpedia in French took 2.021056890487671s
Verifiability | Contribs. check for DBpedia in French took 0.14709830284118652s
Interlinking | sameAs chians check for DBpedia in French took 0.5019004344940186s
Interlinking | skos check for DBpedia in French took 0.3307688236236572s
Interlinking | skos check for DBpedia in French took 0.07516360282897949s
Timeliness | dataset update frequency check for DBpedia in French took 0.49689722061157227s
Currency | Creation date check for DBpedia in French took 0.29349470138549805s
Currency | Modification date check for DBpedia in French took 0.19860506057739258s
Rep.Conc. | URIs length for DBpedia in French took 38.788310527801514s
Interoperability | New vocabularies check for DBpedia in French took 28.08033299446106s
Consistency | Deprecated classes/propertiers check for DBpedia in French took 0.09495973587036133s
Accuracy | Check Functional Property for DBpedia in French took 0.14843010902404785s
Accuracy | Check Inverse Functional Property for DBpedia in French took 0.11737847328186035s
Accuracy | Check Empty annotation labels for DBpedia in French took 26.1220543384552s
Accuracy | Check White space in annotation for DBpedia in French took 3.0372278690338135s
Accuracy | Check Datatype consistency for DBpedia in French took 2.617577314376831s
Consistency | Disjoint class check for DBpedia in French took 0.17527008056640625s
Consistency | Check Misplaced properties for DBpedia in French took 7.723257541656494s
Consistency | Misplaced classes for DBpedia in French took 9.10897970199585s
Consistency | Check Ontology hijacking for DBpedia in French took 22.032601594924927s
Consistency | Check Invalid usage of undefined classes for DBpedia in French took 1.3777997493743896s
Consistency | Check Invalid usage of undefined properties for DBpedia in French took 7.896729230880737s
Conciseness | Check Extensional conciseness for DBpedia in French took 2.9678869247436523s
Conciseness | Check Intensional conciseness for DBpedia in French took 1.9559054374694824s
Security | Sign check for DBpedia in French took 0.09764480590820312s
Availability | Check URIs Dereferenciability for DBpedia in French took 814.0440680980682s
Completeness | Calculation of interlinking completeness for DBpedia in French took 0.49095726013183594s
Reputation | Calculation of the PageRank for DBpedia in French took 0.023270845413208008s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0006880760192871094s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 9.512901306152344e-05s
Interoperability | Check the re-using of existing vocabs for DBpedia in French took 19.060673236846924s
Believability | Calculation of trust value for DBpedia in French took 1.0013580322265625e-05s
INFO | --- Analysis for dbpedia-fr took 1697.3273096084595s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 1.866579532623291s
Availability | VoID file availability check for DBpedia in Japanese took 4.026139497756958s
Extra | Recovery of all triples for DBpedia in Japanese took 5.446849346160889s
Performance | Total latancy measurement for DBpedia in Japanese took 6.5218188762664795s
Amount of data | Number of triples check for DBpedia in Japanese took 27.820838928222656s
Interoperability | New terms check for DBpedia in Japanese took 17.50307011604309s
Versatility | Languages check for DBpedia in Japanese took 1.3056819438934326s
Interpretability | Number of blank nodes check for DBpedia in Japanese took 1.3081698417663574s
Security | Check HTTPS for DBpedia in Japanese took 0.7866942882537842s
Interpretability | RDF structures check for DBpedia in Japanese took 1.354383945465088s
Versatility | Serialization formats check for DBpedia in Japanese took 1.3265740871429443s
Availability | RDF dump link check for DBpedia in Japanese took 1.3099443912506104s
License | MR license check for DBpedia in Japanese took 1.3415699005126953s
License | HR license check for DBpedia in Japanese took 61.30352711677551s
Amount of data | Number of property check for DBpedia in Japanese took 1.324920654296875s
Understandability | Number of label check for DBpedia in Japanese took 1.3030359745025635s
Understandability | URI regex check for DBpedia in Japanese took 34.04852747917175s
Understandability | Vocabs check for DBpedia in Japanese took 1.3133296966552734s
Verifiability | Authors check for DBpedia in Japanese took 1.3210175037384033s
Verifiability | Publishers check for DBpedia in Japanese took 1.3081908226013184s
Performance | Throughput check for DBpedia in Japanese took 13.044971466064453s
Amount of data | Check the number of entities for DBpedia in Japanese took 7.2479248046875e-05s
Verifiability | Contribs. check for DBpedia in Japanese took 1.3126299381256104s
Interlinking | sameAs chians check for DBpedia in Japanese took 2.8659543991088867s
Interlinking | skos check for DBpedia in Japanese took 1.313342571258545s
Interlinking | skos check for DBpedia in Japanese took 1.3079133033752441s
Timeliness | dataset update frequency check for DBpedia in Japanese took 1.3209919929504395s
Currency | Creation date check for DBpedia in Japanese took 2.7190067768096924s
Currency | Modification date check for DBpedia in Japanese took 2.6191565990448s
Rep.Conc. | URIs length for DBpedia in Japanese took 110.63391876220703s
Interoperability | New vocabularies check for DBpedia in Japanese took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Japanese took 1.3074331283569336s
Accuracy | Check Functional Property for DBpedia in Japanese took 1.3257334232330322s
Accuracy | Check Inverse Functional Property for DBpedia in Japanese took 1.328385591506958s
Accuracy | Check Empty annotation labels for DBpedia in Japanese took 3.238370418548584s
Accuracy | Check White space in annotation for DBpedia in Japanese took 0.024719953536987305s
Accuracy | Check Datatype consistency for DBpedia in Japanese took 0.02795124053955078s
Consistency | Disjoint class check for DBpedia in Japanese took 1.4564142227172852s
Consistency | Check Misplaced properties for DBpedia in Japanese took 62.615522146224976s
Consistency | Check Ontology hijacking for DBpedia in Japanese took 1.3023219108581543s
Consistency | Check Invalid usage of undefined properties for DBpedia in Japanese took 2.7352042198181152s
Conciseness | Check Extensional conciseness for DBpedia in Japanese took 0.03437662124633789s
Security | Sign check for DBpedia in Japanese took 1.3011081218719482s
Availability | Check URIs Dereferenciability for DBpedia in Japanese took 11.585049629211426s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 0.30266547203063965s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.020663976669311523s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 0.00010514259338378906s
Interoperability | Check the re-using of existing vocabs for DBpedia in Japanese took 1.1920928955078125e-06s
Believability | Calculation of trust value for DBpedia in Japanese took 5.4836273193359375e-06s
INFO | --- Analysis for dbpedia-ja took 963.4712698459625s
Availability | SPARQL endpoint availability check for dbpedia lite took 8.702278137207031e-05s
Availability | VoID file availability check for dbpedia lite took 0.0006449222564697266s
Completeness | Calculation of interlinking completeness for dbpedia lite took 0.2702445983886719s
Reputation | Calculation of the PageRank for dbpedia lite took 0.020687341690063477s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for dbpedia lite took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 0.00010371208190917969s
Believability | Calculation of trust value for dbpedia lite took 9.775161743164062e-06s
INFO | --- Analysis for dbpedia-lite took 6.2864251136779785s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 0.22073149681091309s
Availability | VoID file availability check for DBpedia in Dutch took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 0.2678954601287842s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.020909547805786133s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.0001709461212158203s
Believability | Calculation of trust value for DBpedia in Dutch took 1.0967254638671875e-05s
INFO | --- Analysis for dbpedia-nl took 3.202441453933716s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 8.25454330444336s
Availability | VoID file availability check for DBpedia in Portuguese took 0.0006413459777832031s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 0.27806687355041504s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.022092819213867188s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 8.106231689453125e-05s
Believability | Calculation of trust value for DBpedia in Portuguese took 1.1444091796875e-05s
INFO | --- Analysis for dbpedia-pt took 20.753934383392334s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 8.869171142578125e-05s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 0.0006418228149414062s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 0.27291154861450195s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.020385026931762695s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight NIF NER Corpus took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight NIF NER Corpus took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight NIF NER Corpus took 6.771087646484375e-05s
Believability | Calculation of trust value for DBpedia Spotlight NIF NER Corpus took 9.5367431640625e-06s
INFO | --- Analysis for dbpedia-spotlight-nif-ner-corpus took 13.655347347259521s
Availability | SPARQL endpoint availability check for DBTropes took 8.296966552734375e-05s
Availability | VoID file availability check for DBTropes took 0.0006022453308105469s
Completeness | Calculation of interlinking completeness for DBTropes took 0.27151942253112793s
Reputation | Calculation of the PageRank for DBTropes took 0.020843029022216797s
Interlinking | Calculation of Degree of Connection for DBTropes took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DBTropes took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for DBTropes took 0.0001010894775390625s
Believability | Calculation of trust value for DBTropes took 1.2636184692382812e-05s
INFO | --- Analysis for dbtropes took 3.31819486618042s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 8.821487426757812e-05s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 0.28470683097839355s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.020484209060668945s
Interlinking | Calculation of Degree of Connection for DBTune.org Artists: Last.fm took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBTune.org Artists: Last.fm took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 5.602836608886719e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 9.059906005859375e-06s
INFO | --- Analysis for dbtune-artists-last-fm took 2.7230868339538574s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 4.482269287109375e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.0005578994750976562s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 0.27467823028564453s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.02073073387145996s
Interlinking | Calculation of Degree of Connection for DBTune.org AudioScrobbler RDF Service took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for DBTune.org AudioScrobbler RDF Service took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for DBTune.org AudioScrobbler RDF Service took 3.504753112792969e-05s
Believability | Calculation of trust value for DBTune.org AudioScrobbler RDF Service took 1.1920928955078125e-05s
INFO | --- Analysis for dbtune-audioscrobbler took 2.6412506103515625s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 5.5209972858428955s
Availability | VoID file availability check for DBTune.org/classical took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.26174187660217285s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.02055191993713379s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 7.772445678710938e-05s
Believability | Calculation of trust value for DBTune.org/classical took 1.0013580322265625e-05s
INFO | --- Analysis for dbtune-classical took 8.63715672492981s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 5.5599753856658936s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.0007529258728027344s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.29444241523742676s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.020471572875976562s
Interlinking | Calculation of Degree of Connection for DBTune.org John Peel sessions RDF server took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for DBTune.org John Peel sessions RDF server took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 6.818771362304688e-05s
Believability | Calculation of trust value for DBTune.org John Peel sessions RDF server took 1.3589859008789062e-05s
INFO | --- Analysis for dbtune-john-peel-sessions took 11.155292749404907s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 5.501575946807861s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.0006711483001708984s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.263765811920166s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.02164006233215332s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.0007853507995605469s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 8.7738037109375e-05s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 1.2636184692382812e-05s
INFO | --- Analysis for dbtune-magnatune took 9.69361686706543s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 180.38652563095093s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.000705718994140625s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 0.36078596115112305s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.021746158599853516s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 2.5510787963867188e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.00011610984802246094s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 1.1205673217773438e-05s
INFO | --- Analysis for dbtune-musicbrainz took 433.457777261734s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 0.29647397994995117s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 0.27335309982299805s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.02041792869567871s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 5.14984130859375e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 1.049041748046875e-05s
INFO | --- Analysis for dbtune-myspace took 2.984402894973755s
Availability | SPARQL endpoint availability check for data.dcs took 7.534027099609375e-05s
Availability | VoID file availability check for data.dcs took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for data.dcs took 0.26476550102233887s
Reputation | Calculation of the PageRank for data.dcs took 0.021436691284179688s
Interlinking | Calculation of Degree of Connection for data.dcs took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for data.dcs took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for data.dcs took 6.937980651855469e-05s
Believability | Calculation of trust value for data.dcs took 1.1920928955078125e-05s
INFO | --- Analysis for dcs-sheffield took 2.514538049697876s
Availability | SPARQL endpoint availability check for de-gaap-ontology-lexicon took 4.291534423828125e-05s
Availability | VoID file availability check for de-gaap-ontology-lexicon took 0.0006203651428222656s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 0.2624185085296631s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.02037525177001953s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 3.7670135498046875e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 1.1444091796875e-05s
INFO | --- Analysis for de-gaap-ontology-lexicon took 4.665333271026611s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 8.678436279296875e-05s
Availability | VoID file availability check for Debian Package Tracking System took 0.0007698535919189453s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 0.272122859954834s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.020272016525268555s
Interlinking | Calculation of Degree of Connection for Debian Package Tracking System took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Debian Package Tracking System took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 4.363059997558594e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 1.2159347534179688e-05s
INFO | --- Analysis for debian-package-tracking-system took 4.523005485534668s
Availability | SPARQL endpoint availability check for Projeto Desaparecidos took 9.560585021972656e-05s
Availability | VoID file availability check for Projeto Desaparecidos took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for Projeto Desaparecidos took 0.26384568214416504s
Reputation | Calculation of the PageRank for Projeto Desaparecidos took 0.021617412567138672s
Interlinking | Calculation of Degree of Connection for Projeto Desaparecidos took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Projeto Desaparecidos took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Projeto Desaparecidos took 3.457069396972656e-05s
Believability | Calculation of trust value for Projeto Desaparecidos took 1.0728836059570312e-05s
INFO | --- Analysis for desaparecidos took 3.0456912517547607s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 8.749961853027344e-05s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.0006506443023681641s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 0.26444339752197266s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.02013564109802246s
Interlinking | Calculation of Degree of Connection for Deusto Entrepreneurship: sharing business knowledge took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Deusto Entrepreneurship: sharing business knowledge took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 9.72747802734375e-05s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 1.2874603271484375e-05s
INFO | --- Analysis for deustoentrepreneurship took 6.1917383670806885s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 0.00010275840759277344s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 0.0007047653198242188s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 0.27321624755859375s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.02102971076965332s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.00010251998901367188s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 1.0967254638671875e-05s
INFO | --- Analysis for deustotech took 4.555362939834595s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 1.3094582557678223s
Availability | VoID file availability check for Deutsche Biographie took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 0.29035472869873047s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.021169662475585938s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 3.5762786865234375e-05s
Believability | Calculation of trust value for Deutsche Biographie took 1.1682510375976562e-05s
INFO | --- Analysis for deutsche-biographie took 4.17227578163147s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 8.726119995117188e-05s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 0.2765371799468994s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.020351409912109375s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 5.4836273193359375e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 1.1682510375976562e-05s
INFO | --- Analysis for deutsche-nationalbibliografie-dnb took 6.07445502281189s
Availability | SPARQL endpoint availability check for dev8d took 8.749961853027344e-05s
Availability | VoID file availability check for dev8d took 0.0005993843078613281s
Completeness | Calculation of interlinking completeness for dev8d took 0.30645275115966797s
Reputation | Calculation of the PageRank for dev8d took 0.021876811981201172s
Interlinking | Calculation of Degree of Connection for dev8d took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for dev8d took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for dev8d took 6.508827209472656e-05s
Believability | Calculation of trust value for dev8d took 1.1682510375976562e-05s
INFO | --- Analysis for dev8d took 3.498286247253418s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 30.131443738937378s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 0.0006964206695556641s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 0.2754344940185547s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.020775794982910156s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Dewey Decimal Classification (DDC) took 6.175041198730469e-05s
Believability | Calculation of trust value for Dewey Decimal Classification (DDC) took 1.0967254638671875e-05s
INFO | --- Analysis for dewey_decimal_classification took 92.8847873210907s
Availability | SPARQL endpoint availability check for Distributed Hydrology Soil Vegetation Model took 9.560585021972656e-05s
Availability | VoID file availability check for Distributed Hydrology Soil Vegetation Model took 0.0007367134094238281s
Completeness | Calculation of interlinking completeness for Distributed Hydrology Soil Vegetation Model took 0.27766942977905273s
Reputation | Calculation of the PageRank for Distributed Hydrology Soil Vegetation Model took 0.020734548568725586s
Interlinking | Calculation of Degree of Connection for Distributed Hydrology Soil Vegetation Model took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Distributed Hydrology Soil Vegetation Model took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Distributed Hydrology Soil Vegetation Model took 3.647804260253906e-05s
Believability | Calculation of trust value for Distributed Hydrology Soil Vegetation Model took 1.239776611328125e-05s
INFO | --- Analysis for DHSVM took 21.756536960601807s
Availability | SPARQL endpoint availability check for Diavgeia took 9.560585021972656e-05s
Availability | VoID file availability check for Diavgeia took 0.0007154941558837891s
Completeness | Calculation of interlinking completeness for Diavgeia took 0.2739090919494629s
Reputation | Calculation of the PageRank for Diavgeia took 0.0220949649810791s
Interlinking | Calculation of Degree of Connection for Diavgeia took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Diavgeia took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 0.00010371208190917969s
Believability | Calculation of trust value for Diavgeia took 8.58306884765625e-06s
INFO | --- Analysis for diavgeia took 5.346816778182983s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 4.601478576660156e-05s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0006802082061767578s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.35802149772644043s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.020447254180908203s
Interlinking | Calculation of Degree of Connection for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00012612342834472656s
Believability | Calculation of trust value for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.1444091796875e-05s
INFO | --- Analysis for didactalia took 12.736256837844849s
Availability | SPARQL endpoint availability check for DisGeNET took 1.5620782375335693s
Availability | VoID file availability check for DisGeNET took 0.0007388591766357422s
Completeness | Calculation of interlinking completeness for DisGeNET took 0.270374059677124s
Reputation | Calculation of the PageRank for DisGeNET took 0.021855831146240234s
Interlinking | Calculation of Degree of Connection for DisGeNET took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for DisGeNET took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.00015163421630859375s
Believability | Calculation of trust value for DisGeNET took 1.1682510375976562e-05s
INFO | --- Analysis for disgenet took 7.19511866569519s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 4.3392181396484375e-05s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 0.0004496574401855469s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 0.2698502540588379s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.020707368850708008s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 3.0517578125e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 1.1205673217773438e-05s
INFO | --- Analysis for dkh-deusto-knowledge-hub took 7.408964395523071s
Availability | SPARQL endpoint availability check for DM2E took 8.893013000488281e-05s
Availability | VoID file availability check for DM2E took 0.0008444786071777344s
Completeness | Calculation of interlinking completeness for DM2E took 0.27958154678344727s
Reputation | Calculation of the PageRank for DM2E took 0.020960330963134766s
Interlinking | Calculation of Degree of Connection for DM2E took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for DM2E took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.00011515617370605469s
Believability | Calculation of trust value for DM2E took 1.2636184692382812e-05s
INFO | --- Analysis for dm2e took 3.355607509613037s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 8.749961853027344e-05s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.0005588531494140625s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 0.3166158199310303s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.02062678337097168s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.0001513957977294922s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 1.1444091796875e-05s
INFO | --- Analysis for dnb-gemeinsame-normdatei took 7.076651334762573s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 8.58306884765625e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 0.0007805824279785156s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 0.27288389205932617s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.020715713500976562s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 6.318092346191406e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 9.298324584960938e-06s
INFO | --- Analysis for doi took 7.15241551399231s
Availability | SPARQL endpoint availability check for Driggu Florentino took 8.726119995117188e-05s
Availability | VoID file availability check for Driggu Florentino took 0.0012865066528320312s
Completeness | Calculation of interlinking completeness for Driggu Florentino took 0.263047456741333s
Reputation | Calculation of the PageRank for Driggu Florentino took 0.02051234245300293s
Interlinking | Calculation of Degree of Connection for Driggu Florentino took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Driggu Florentino took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Driggu Florentino took 2.9087066650390625e-05s
Believability | Calculation of trust value for Driggu Florentino took 1.0728836059570312e-05s
INFO | --- Analysis for Driggu took 3.3396058082580566s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 1.9289941787719727s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.0005686283111572266s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 0.26813769340515137s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.021732091903686523s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 3.838539123535156e-05s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 1.239776611328125e-05s
INFO | --- Analysis for drug-data-hifm took 16.93132495880127s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 271.9681136608124s
Availability | VoID file availability check for MetaLex Document Server took 0.0006668567657470703s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.2741661071777344s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.020724058151245117s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 2.8371810913085938e-05s
Believability | Calculation of trust value for MetaLex Document Server took 9.059906005859375e-06s
INFO | --- Analysis for dutch-national-regulations-metalex took 555.3352162837982s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 2.239161729812622s
Availability | VoID file availability check for Dutch Ships and Sailors took 0.0007345676422119141s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 0.2728002071380615s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.020981788635253906s
Interlinking | Calculation of Degree of Connection for Dutch Ships and Sailors took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Dutch Ships and Sailors took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 4.00543212890625e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 1.1920928955078125e-05s
INFO | --- Analysis for dutch-ships-and-sailors took 13.43960952758789s
Availability | SPARQL endpoint availability check for DWS-Group took 4.601478576660156e-05s
Availability | VoID file availability check for DWS-Group took 0.0005381107330322266s
Completeness | Calculation of interlinking completeness for DWS-Group took 0.270294189453125s
Reputation | Calculation of the PageRank for DWS-Group took 0.022050142288208008s
Interlinking | Calculation of Degree of Connection for DWS-Group took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for DWS-Group took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 0.00010275840759277344s
Believability | Calculation of trust value for DWS-Group took 1.2159347534179688e-05s
INFO | --- Analysis for dws-group took 2.5023272037506104s
Availability | SPARQL endpoint availability check for E1 - Nuvem dados took 8.559226989746094e-05s
Availability | VoID file availability check for E1 - Nuvem dados took 0.0005445480346679688s
Completeness | Calculation of interlinking completeness for E1 - Nuvem dados took 0.33875322341918945s
Reputation | Calculation of the PageRank for E1 - Nuvem dados took 0.020678043365478516s
Interlinking | Calculation of Degree of Connection for E1 - Nuvem dados took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for E1 - Nuvem dados took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for E1 - Nuvem dados took 3.314018249511719e-05s
Believability | Calculation of trust value for E1 - Nuvem dados took 1.0251998901367188e-05s
INFO | --- Analysis for E1 took 4.269184350967407s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 0.05182528495788574s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 0.26052403450012207s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.020716428756713867s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Alaska Fairbanks took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Alaska Fairbanks took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.00011301040649414062s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 1.2874603271484375e-05s
INFO | --- Analysis for eagle-i-alaska took 2.509319305419922s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 0.031409263610839844s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 0.2594931125640869s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.020626544952392578s
Interlinking | Calculation of Degree of Connection for eagle-i @ Clark Atlanta University took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Clark Atlanta University took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 5.6743621826171875e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 1.4781951904296875e-05s
INFO | --- Analysis for eagle-i-cau took 2.470533847808838s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 0.03183293342590332s
Availability | VoID file availability check for eagle-i @ The City College of New York took 0.00045490264892578125s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.26746416091918945s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.021987199783325195s
Interlinking | Calculation of Degree of Connection for eagle-i @ The City College of New York took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for eagle-i @ The City College of New York took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 6.318092346191406e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 1.0967254638671875e-05s
INFO | --- Analysis for eagle-i-ccny-cuny took 2.493112564086914s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 0.032642364501953125s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 0.2853972911834717s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.02049708366394043s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 9.870529174804688e-05s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 1.3113021850585938e-05s
INFO | --- Analysis for eagle-i-cdrewu took 2.5333893299102783s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 0.031172752380371094s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.2710554599761963s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.020333051681518555s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.00013136863708496094s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 1.239776611328125e-05s
INFO | --- Analysis for eagle-i-dartmouth took 2.496330738067627s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.03177070617675781s
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.2725849151611328s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.02060556411743164s
Interlinking | Calculation of Degree of Connection for eagle-i @ Florida Agricultural and Mechanical University took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for eagle-i @ Florida Agricultural and Mechanical University took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 8.58306884765625e-05s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 1.1205673217773438e-05s
INFO | --- Analysis for eagle-i-famu took 2.5205273628234863s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 0.03230595588684082s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.00045371055603027344s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.2652420997619629s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.020736217498779297s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.00012755393981933594s
Believability | Calculation of trust value for eagle-i @ Harvard University took 1.2874603271484375e-05s
INFO | --- Analysis for eagle-i-harvard took 2.5221807956695557s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 0.032070159912109375s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 0.2655305862426758s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.020345211029052734s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Hawai’i at Mānoa took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Hawai’i at Mānoa took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.00012421607971191406s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 1.1444091796875e-05s
INFO | --- Analysis for eagle-i-hawaii took 2.4891600608825684s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 0.031164169311523438s
Availability | VoID file availability check for eagle-i @ Howard University took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 0.26798152923583984s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.02168726921081543s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 6.699562072753906e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i-howard took 2.4906160831451416s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 0.03105449676513672s
Availability | VoID file availability check for eagle-i @ Hunter College took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 0.26959872245788574s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.020740509033203125s
Interlinking | Calculation of Degree of Connection for eagle-i @ Hunter College took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Hunter College took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 7.033348083496094e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 1.4066696166992188e-05s
INFO | --- Analysis for eagle-i-hunter-cuny took 2.477731704711914s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 0.03412055969238281s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 0.26259589195251465s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.020550251007080078s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.0008656978607177734s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.00011706352233886719s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 1.1444091796875e-05s
INFO | --- Analysis for eagle-i-jsu took 2.5202033519744873s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 0.032685041427612305s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 0.26915669441223145s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.02051258087158203s
Interlinking | Calculation of Degree of Connection for eagle-i @ Meharry Medical College took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for eagle-i @ Meharry Medical College took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 3.933906555175781e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 1.1205673217773438e-05s
INFO | --- Analysis for eagle-i-meharry took 2.477372407913208s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 0.03213047981262207s
Availability | VoID file availability check for eagle-i @ Montana State University took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 0.26728367805480957s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.02304840087890625s
Interlinking | Calculation of Degree of Connection for eagle-i @ Montana State University took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for eagle-i @ Montana State University took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 0.000102996826171875s
Believability | Calculation of trust value for eagle-i @ Montana State University took 1.2636184692382812e-05s
INFO | --- Analysis for eagle-i-montana took 2.493581771850586s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 0.03303647041320801s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.0004494190216064453s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 0.2777364253997803s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.020636320114135742s
Interlinking | Calculation of Degree of Connection for eagle-i @ Morehouse School of Medicine took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for eagle-i @ Morehouse School of Medicine took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 9.703636169433594e-05s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 1.2159347534179688e-05s
INFO | --- Analysis for eagle-i-msm took 2.5135858058929443s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 0.036422014236450195s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 0.2924036979675293s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.020214557647705078s
Interlinking | Calculation of Degree of Connection for eagle-i @ Oregon Health and Science University took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for eagle-i @ Oregon Health and Science University took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.0001304149627685547s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 1.1444091796875e-05s
INFO | --- Analysis for eagle-i-ohsu took 2.631608486175537s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 0.031471967697143555s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.00044536590576171875s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 0.27372026443481445s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.022290468215942383s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0010161399841308594s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 8.368492126464844e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 1.1682510375976562e-05s
INFO | --- Analysis for eagle-i-psm took 2.524038076400757s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 0.03152298927307129s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.0004572868347167969s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 0.2641749382019043s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.022515296936035156s
Interlinking | Calculation of Degree of Connection for eagle-i @ Texas Southern University took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Texas Southern University took 0.0009691715240478516s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Texas Southern University took 7.867813110351562e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 1.2159347534179688e-05s
INFO | --- Analysis for eagle-i-tsu took 2.5552854537963867s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 0.03298640251159668s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.00048041343688964844s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 0.2693212032318115s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.023206710815429688s
Interlinking | Calculation of Degree of Connection for eagle-i @ Tuskegee University took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Tuskegee University took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 7.009506225585938e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 1.1205673217773438e-05s
INFO | --- Analysis for eagle-i-tuskegee took 2.5333666801452637s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 0.031520843505859375s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 0.26905035972595215s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.02341461181640625s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.0012042522430419922s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 0.0001385211944580078s
Believability | Calculation of trust value for eagle-i @ Universidad Central del Caribe took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i-uccaribe took 2.490253448486328s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.03137350082397461s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.296433687210083s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.021071195602416992s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0011594295501708984s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.000164031982421875s
Believability | Calculation of trust value for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.2874603271484375e-05s
INFO | --- Analysis for eagle-i-upr took 2.5374412536621094s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 0.032068729400634766s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.0004279613494873047s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 0.28366661071777344s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.02043771743774414s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at El Paso took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at El Paso took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 5.9604644775390625e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 1.0013580322265625e-05s
INFO | --- Analysis for eagle-i-utep took 2.488281488418579s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 0.0317692756652832s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 0.0004239082336425781s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 0.27349257469177246s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.02073955535888672s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 7.081031799316406e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i-utsa took 2.4763712882995605s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 0.15415740013122559s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.0004258155822753906s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 0.2779877185821533s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.020677804946899414s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 9.393692016601562e-05s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 1.0251998901367188e-05s
INFO | --- Analysis for eagle-i-vanderbilt took 2.6236236095428467s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 0.044397592544555664s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.00041604042053222656s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 0.2719302177429199s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.02034592628479004s
Interlinking | Calculation of Degree of Connection for eagle-i @ Xavier University of Louisiana took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Xavier University of Louisiana took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 7.43865966796875e-05s
Believability | Calculation of trust value for eagle-i @ Xavier University of Louisiana took 9.5367431640625e-06s
INFO | --- Analysis for eagle-i-xula took 2.5445971488952637s
Availability | SPARQL endpoint availability check for Emergency situation took 0.5789690017700195s
Availability | VoID file availability check for Emergency situation took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for Emergency situation took 0.26668548583984375s
Reputation | Calculation of the PageRank for Emergency situation took 0.020604848861694336s
Interlinking | Calculation of Degree of Connection for Emergency situation took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Emergency situation took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Emergency situation took 4.887580871582031e-05s
Believability | Calculation of trust value for Emergency situation took 1.1444091796875e-05s
INFO | --- Analysis for Earthquake took 3.61506724357605s
Availability | SPARQL endpoint availability check for ESO took 0.48331761360168457s
Availability | VoID file availability check for ESO took 0.0008137226104736328s
Completeness | Calculation of interlinking completeness for ESO took 0.26979780197143555s
Reputation | Calculation of the PageRank for ESO took 0.020843982696533203s
Interlinking | Calculation of Degree of Connection for ESO took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for ESO took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for ESO took 8.654594421386719e-05s
Believability | Calculation of trust value for ESO took 1.2159347534179688e-05s
INFO | --- Analysis for Earthquake_case took 3.8729355335235596s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 0.08656001091003418s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 0.2757384777069092s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.020755529403686523s
Interlinking | Calculation of Degree of Connection for European Central Bank (ECB) Linked Data took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for European Central Bank (ECB) Linked Data took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 0.00010061264038085938s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 9.5367431640625e-06s
INFO | --- Analysis for ecb-linked-data took 2.56595516204834s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 6.2659876346588135s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 0.0006732940673828125s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 0.27179741859436035s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.020360469818115234s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 3.409385681152344e-05s
Believability | Calculation of trust value for European Central Bank Statistics (PublicData.eu) took 7.867813110351562e-06s
INFO | --- Analysis for ecb-statistics-linked-data took 14.946424961090088s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 1.484618902206421s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 0.27132606506347656s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.020569562911987305s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 6.985664367675781e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 9.5367431640625e-06s
INFO | --- Analysis for ecco-tcp-linked-data took 6.289413213729858s
Availability | SPARQL endpoint availability check for ECLAP took 20.56456208229065s
Availability | VoID file availability check for ECLAP took 0.0004582405090332031s
Completeness | Calculation of interlinking completeness for ECLAP took 0.262972354888916s
Reputation | Calculation of the PageRank for ECLAP took 0.02043938636779785s
Interlinking | Calculation of Degree of Connection for ECLAP took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for ECLAP took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for ECLAP took 3.886222839355469e-05s
Believability | Calculation of trust value for ECLAP took 1.0728836059570312e-05s
INFO | --- Analysis for eclap took 53.13967967033386s
Availability | SPARQL endpoint availability check for 《老子》译本传播知识图谱 took 8.916854858398438e-05s
Availability | VoID file availability check for 《老子》译本传播知识图谱 took 0.0007183551788330078s
Completeness | Calculation of interlinking completeness for 《老子》译本传播知识图谱 took 0.2707509994506836s
Reputation | Calculation of the PageRank for 《老子》译本传播知识图谱 took 0.021375656127929688s
Interlinking | Calculation of Degree of Connection for 《老子》译本传播知识图谱 took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for 《老子》译本传播知识图谱 took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for 《老子》译本传播知识图谱 took 1.2159347534179688e-05s
Believability | Calculation of trust value for 《老子》译本传播知识图谱 took 1.2159347534179688e-05s
INFO | --- Analysis for ECNU-GISer took 3.907323122024536s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 4.601478576660156e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0005598068237304688s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.26296448707580566s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.021643400192260742s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007901191711425781s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 6.0558319091796875e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 1.1205673217773438e-05s
INFO | --- Analysis for ecs took 2.5937864780426025s
Availability | SPARQL endpoint availability check for Edublogs took 0.00012135505676269531s
Availability | VoID file availability check for Edublogs took 0.0007719993591308594s
Completeness | Calculation of interlinking completeness for Edublogs took 0.2771477699279785s
Reputation | Calculation of the PageRank for Edublogs took 0.020709514617919922s
Interlinking | Calculation of Degree of Connection for Edublogs took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Edublogs took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Edublogs took 0.00010728836059570312s
Believability | Calculation of trust value for Edublogs took 1.1444091796875e-05s
INFO | --- Analysis for edublogs took 62.468629598617554s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 0.36345839500427246s
Availability | VoID file availability check for education.data.gov.uk took 0.00055694580078125s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 0.26837873458862305s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.02042102813720703s
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.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 9.584426879882812e-05s
Believability | Calculation of trust value for education.data.gov.uk took 1.0013580322265625e-05s
INFO | --- Analysis for education-data-gov-uk took 4.1521735191345215s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 392.1522762775421s
Availability | VoID file availability check for Educational programs - SISVU took 0.0015795230865478516s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 0.4613206386566162s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.020541667938232422s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 5.5789947509765625e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 1.239776611328125e-05s
INFO | --- Analysis for educationalprograms_sisvu took 1320.4187037944794s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 2.516700267791748s
Availability | VoID file availability check for European Environment Agency Published Products took 0.0006554126739501953s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 0.2702343463897705s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.022273540496826172s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.0012600421905517578s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 5.793571472167969e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 9.775161743164062e-06s
INFO | --- Analysis for eea took 10.787816047668457s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 0.48075199127197266s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 0.27011775970458984s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.020294666290283203s
Interlinking | Calculation of Degree of Connection for EEA Reporting Obligations Database took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EEA Reporting Obligations Database took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 5.2928924560546875e-05s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 9.059906005859375e-06s
INFO | --- Analysis for eea-rod took 5.058624029159546s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 0.15599966049194336s
Availability | VoID file availability check for EEA Vocabularies took 0.0005590915679931641s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 0.2656831741333008s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.02040386199951172s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 8.0108642578125e-05s
Believability | Calculation of trust value for EEA Vocabularies took 1.1205673217773438e-05s
INFO | --- Analysis for eea-vocabularies took 4.7942399978637695s
Availability | SPARQL endpoint availability check for E-Government Ontology took 1.889481544494629s
Availability | VoID file availability check for E-Government Ontology took 0.0006256103515625s
Completeness | Calculation of interlinking completeness for E-Government Ontology took 0.2644381523132324s
Reputation | Calculation of the PageRank for E-Government Ontology took 0.02083897590637207s
Interlinking | Calculation of Degree of Connection for E-Government Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for E-Government Ontology took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for E-Government Ontology took 3.0994415283203125e-05s
Believability | Calculation of trust value for E-Government Ontology took 1.2159347534179688e-05s
INFO | --- Analysis for EGovOntology took 5.409449100494385s
Availability | SPARQL endpoint availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5044474601745605s
Availability | VoID file availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0006229877471923828s
Extra | Recovery of all triples for Aragon Interoperable Information Structure EI2A - aragon open data took 2.9020533561706543s
Performance | Total latancy measurement for Aragon Interoperable Information Structure EI2A - aragon open data took 1.1581387519836426s
Amount of data | Number of triples check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.8065850734710693s
Interoperability | New terms check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.8913238048553467s
Versatility | Languages check for Aragon Interoperable Information Structure EI2A - aragon open data took 60.30992579460144s
Interpretability | Number of blank nodes check for Aragon Interoperable Information Structure EI2A - aragon open data took 4.561214923858643s
Interpretability | RDF structures check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.7510128021240234s
Versatility | Serialization formats check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.8630356788635254s
Availability | RDF dump link check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.24311351776123047s
License | MR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5157418251037598s
License | HR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 6.7105958461761475s
Amount of data | Number of property check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.23955082893371582s
Understandability | Number of label check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4348788261413574s
Understandability | URI regex check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5892586708068848s
Understandability | Vocabs check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2959873676300049s
Verifiability | Authors check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.343902587890625s
Verifiability | Publishers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.24706244468688965s
Performance | Throughput check for Aragon Interoperable Information Structure EI2A - aragon open data took 11.582515239715576s
Amount of data | Check the number of entities for Aragon Interoperable Information Structure EI2A - aragon open data took 6.747245788574219e-05s
Verifiability | Contribs. check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.33719348907470703s
Interlinking | sameAs chians check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.27593159675598145s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4524707794189453s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.23205780982971191s
Timeliness | dataset update frequency check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.32361507415771484s
Currency | Creation date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.9868197441101074s
Currency | Modification date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.24110770225524902s
Rep.Conc. | URIs length for Aragon Interoperable Information Structure EI2A - aragon open data took 5.811223268508911s
Interoperability | New vocabularies check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.23474884033203125s
Accuracy | Check Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2926301956176758s
Accuracy | Check Inverse Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.29532551765441895s
Accuracy | Check Empty annotation labels for Aragon Interoperable Information Structure EI2A - aragon open data took 1.2516143321990967s
Accuracy | Check White space in annotation for Aragon Interoperable Information Structure EI2A - aragon open data took 0.030065059661865234s
Accuracy | Check Datatype consistency for Aragon Interoperable Information Structure EI2A - aragon open data took 0.027417659759521484s
Consistency | Disjoint class check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.22693967819213867s
Consistency | Check Misplaced properties for Aragon Interoperable Information Structure EI2A - aragon open data took 4.096302270889282s
Consistency | Misplaced classes for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4487931728363037s
Consistency | Check Ontology hijacking for Aragon Interoperable Information Structure EI2A - aragon open data took 2.3186733722686768s
Consistency | Check Invalid usage of undefined classes for Aragon Interoperable Information Structure EI2A - aragon open data took 1.2568726539611816s
Consistency | Check Invalid usage of undefined properties for Aragon Interoperable Information Structure EI2A - aragon open data took 5.071159839630127s
Conciseness | Check Extensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.03330206871032715s
Conciseness | Check Intensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.37950754165649414s
Security | Sign check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.41488051414489746s
Availability | Check URIs Dereferenciability for Aragon Interoperable Information Structure EI2A - aragon open data took 2945.7816684246063s
Completeness | Calculation of interlinking completeness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6048269271850586s
Reputation | Calculation of the PageRank for Aragon Interoperable Information Structure EI2A - aragon open data took 0.021329402923583984s
Interlinking | Calculation of Degree of Connection for Aragon Interoperable Information Structure EI2A - aragon open data took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Aragon Interoperable Information Structure EI2A - aragon open data took 5.6743621826171875e-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 1.239776611328125e-05s
INFO | --- Analysis for ei2a took 3178.1002719402313s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 8.726119995117188e-05s
Availability | VoID file availability check for EIONET RDF Data took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 0.26620054244995117s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.021329402923583984s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.0001125335693359375s
Believability | Calculation of trust value for EIONET RDF Data took 7.62939453125e-06s
INFO | --- Analysis for eionet-rdf took 2.966358184814453s
Availability | SPARQL endpoint availability check for Google’s Easter Egg i took 8.702278137207031e-05s
Availability | VoID file availability check for Google’s Easter Egg i took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for Google’s Easter Egg i took 0.2640953063964844s
Reputation | Calculation of the PageRank for Google’s Easter Egg i took 0.02181220054626465s
Interlinking | Calculation of Degree of Connection for Google’s Easter Egg i took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Google’s Easter Egg i took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Google’s Easter Egg i took 3.24249267578125e-05s
Believability | Calculation of trust value for Google’s Easter Egg i took 1.2159347534179688e-05s
INFO | --- Analysis for ElgooG_ took 2.4201087951660156s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 9.156790018081665s
Availability | VoID file availability check for El Viajero's tourism dataset took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for El Viajero's tourism dataset took 0.2737700939178467s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.0203094482421875s
Interlinking | Calculation of Degree of Connection for El Viajero's tourism dataset took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for El Viajero's tourism dataset took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 7.152557373046875e-05s
Believability | Calculation of trust value for El Viajero's tourism dataset took 1.2636184692382812e-05s
INFO | --- Analysis for elviajero took 27.768799781799316s
Availability | SPARQL endpoint availability check for EMN took 0.00011396408081054688s
Availability | VoID file availability check for EMN took 0.0005457401275634766s
Completeness | Calculation of interlinking completeness for EMN took 0.26439714431762695s
Reputation | Calculation of the PageRank for EMN took 0.020984649658203125s
Interlinking | Calculation of Degree of Connection for EMN took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EMN took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for EMN took 3.8623809814453125e-05s
Believability | Calculation of trust value for EMN took 1.1920928955078125e-05s
INFO | --- Analysis for emn took 2.680292844772339s
Availability | SPARQL endpoint availability check for EnAKTing CO2 Emission Dataset took 4.267692565917969e-05s
Availability | VoID file availability check for EnAKTing CO2 Emission Dataset took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 0.26622486114501953s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.02059626579284668s
Interlinking | Calculation of Degree of Connection for EnAKTing CO2 Emission Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EnAKTing CO2 Emission Dataset took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 5.078315734863281e-05s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 8.58306884765625e-06s
INFO | --- Analysis for enakting-co2emission took 2.480343818664551s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 8.559226989746094e-05s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 0.2743802070617676s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.021335601806640625s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 4.0531158447265625e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 9.059906005859375e-06s
INFO | --- Analysis for enakting-crime took 2.4656972885131836s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 8.440017700195312e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.00042128562927246094s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 0.29225683212280273s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.02040243148803711s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 3.0040740966796875e-05s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 3.695487976074219e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 8.821487426757812e-06s
INFO | --- Analysis for enakting-energy took 2.7348735332489014s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 8.463859558105469e-05s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.0004467964172363281s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 0.26125550270080566s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.020520925521850586s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 8.869171142578125e-05s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 9.5367431640625e-06s
INFO | --- Analysis for enakting-mortality took 2.4568707942962646s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 0.00010848045349121094s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 0.2769312858581543s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.0205686092376709s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 3.933906555175781e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 8.58306884765625e-06s
INFO | --- Analysis for enakting-nhs took 2.5566368103027344s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 4.3392181396484375e-05s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 0.2727971076965332s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.020572185516357422s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 5.316734313964844e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 5.0067901611328125e-06s
INFO | --- Analysis for enakting-population took 2.444629192352295s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 0.6646995544433594s
Availability | VoID file availability check for English Heritage Periods List took 0.0007183551788330078s
Extra | Recovery of all triples for English Heritage Periods List took 0.3088698387145996s
Performance | Total latancy measurement for English Heritage Periods List took 1.4296751022338867s
Amount of data | Number of triples check for English Heritage Periods List took 0.44263219833374023s
Versatility | Languages check for English Heritage Periods List took 0.24389410018920898s
Interpretability | Number of blank nodes check for English Heritage Periods List took 0.4476466178894043s
Security | Check HTTPS for English Heritage Periods List took 0.18465042114257812s
Interpretability | RDF structures check for English Heritage Periods List took 0.24718117713928223s
Versatility | Serialization formats check for English Heritage Periods List took 0.5646877288818359s
Availability | RDF dump link check for English Heritage Periods List took 0.2936370372772217s
License | MR license check for English Heritage Periods List took 0.3761484622955322s
License | HR license check for English Heritage Periods List took 0.3187839984893799s
Amount of data | Number of property check for English Heritage Periods List took 0.33304309844970703s
Understandability | Number of label check for English Heritage Periods List took 0.4100766181945801s
Understandability | URI regex check for English Heritage Periods List took 0.5732660293579102s
Understandability | Vocabs check for English Heritage Periods List took 0.3086235523223877s
Verifiability | Authors check for English Heritage Periods List took 0.3390316963195801s
Verifiability | Publishers check for English Heritage Periods List took 0.31566667556762695s
Performance | Throughput check for English Heritage Periods List took 11.41657042503357s
Amount of data | Check the number of entities for English Heritage Periods List took 6.914138793945312e-05s
Verifiability | Contribs. check for English Heritage Periods List took 0.3838479518890381s
Interlinking | sameAs chians check for English Heritage Periods List took 0.36387014389038086s
Interlinking | skos check for English Heritage Periods List took 0.32226014137268066s
Interlinking | skos check for English Heritage Periods List took 0.3335568904876709s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.38942861557006836s
Currency | Creation date check for English Heritage Periods List took 0.6133050918579102s
Currency | Modification date check for English Heritage Periods List took 0.6967759132385254s
Rep.Conc. | URIs length for English Heritage Periods List took 0.5869688987731934s
Interoperability | New vocabularies check for English Heritage Periods List took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Periods List took 0.302661657333374s
Accuracy | Check Functional Property for English Heritage Periods List took 0.3806278705596924s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.29802680015563965s
Consistency | Disjoint class check for English Heritage Periods List took 0.2817418575286865s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.299405574798584s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.6492030620574951s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.0001614093780517578s
Security | Sign check for English Heritage Periods List took 0.31885576248168945s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 0.27604150772094727s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.020529985427856445s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 3.266334533691406e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Periods List took 9.5367431640625e-07s
Believability | Calculation of trust value for English Heritage Periods List took 1.33514404296875e-05s
INFO | --- Analysis for english-heritage-periods-list took 50.984346866607666s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 0.37422823905944824s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.0006797313690185547s
Extra | Recovery of all triples for English Index of Multiple Deprivation Ranking 2010 took 1.4522130489349365s
Performance | Total latancy measurement for English Index of Multiple Deprivation Ranking 2010 took 1.130603313446045s
Amount of data | Number of triples check for English Index of Multiple Deprivation Ranking 2010 took 0.2808506488800049s
Interoperability | New terms check for English Index of Multiple Deprivation Ranking 2010 took 1.569753646850586s
Versatility | Languages check for English Index of Multiple Deprivation Ranking 2010 took 0.4764590263366699s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Ranking 2010 took 30.159721612930298s
Security | Check HTTPS for English Index of Multiple Deprivation Ranking 2010 took 0.0917356014251709s
Interpretability | RDF structures check for English Index of Multiple Deprivation Ranking 2010 took 0.2593116760253906s
Versatility | Serialization formats check for English Index of Multiple Deprivation Ranking 2010 took 0.5322675704956055s
Availability | RDF dump link check for English Index of Multiple Deprivation Ranking 2010 took 45.4914915561676s
License | MR license check for English Index of Multiple Deprivation Ranking 2010 took 0.22618317604064941s
License | HR license check for English Index of Multiple Deprivation Ranking 2010 took 30.15283751487732s
Amount of data | Number of property check for English Index of Multiple Deprivation Ranking 2010 took 0.1300067901611328s
Understandability | Number of label check for English Index of Multiple Deprivation Ranking 2010 took 0.32764315605163574s
Understandability | URI regex check for English Index of Multiple Deprivation Ranking 2010 took 0.3685128688812256s
Understandability | Vocabs check for English Index of Multiple Deprivation Ranking 2010 took 0.18550729751586914s
Verifiability | Authors check for English Index of Multiple Deprivation Ranking 2010 took 0.5199391841888428s
Verifiability | Publishers check for English Index of Multiple Deprivation Ranking 2010 took 0.33263611793518066s
Performance | Throughput check for English Index of Multiple Deprivation Ranking 2010 took 11.351012468338013s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Ranking 2010 took 6.937980651855469e-05s
Verifiability | Contribs. check for English Index of Multiple Deprivation Ranking 2010 took 0.14708685874938965s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Ranking 2010 took 0.34392547607421875s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.3178274631500244s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.12497782707214355s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Ranking 2010 took 0.1870405673980713s
Currency | Creation date check for English Index of Multiple Deprivation Ranking 2010 took 0.5292243957519531s
Currency | Modification date check for English Index of Multiple Deprivation Ranking 2010 took 1.1784801483154297s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Ranking 2010 took 2.2477595806121826s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Ranking 2010 took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Ranking 2010 took 0.22787237167358398s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.1467876434326172s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.1377546787261963s
Consistency | Disjoint class check for English Index of Multiple Deprivation Ranking 2010 took 0.4245007038116455s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Ranking 2010 took 0.7792966365814209s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Ranking 2010 took 3.8521504402160645s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Ranking 2010 took 1.5345959663391113s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.0001723766326904297s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.6017544269561768s
Security | Sign check for English Index of Multiple Deprivation Ranking 2010 took 0.1430373191833496s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 0.35356760025024414s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.020444154739379883s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 3.886222839355469e-05s
Interoperability | Check the re-using of existing vocabs for English Index of Multiple Deprivation Ranking 2010 took 1.1920928955078125e-06s
Believability | Calculation of trust value for English Index of Multiple Deprivation Ranking 2010 took 9.059906005859375e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-ranking-2010 took 269.71892166137695s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Score 2010 took 0.1319742202758789s
Availability | VoID file availability check for English Index of Multiple Deprivation Score 2010 took 0.0006515979766845703s
Extra | Recovery of all triples for English Index of Multiple Deprivation Score 2010 took 1.2098875045776367s
Performance | Total latancy measurement for English Index of Multiple Deprivation Score 2010 took 0.8906698226928711s
Amount of data | Number of triples check for English Index of Multiple Deprivation Score 2010 took 0.12508368492126465s
Interoperability | New terms check for English Index of Multiple Deprivation Score 2010 took 1.5583281517028809s
Versatility | Languages check for English Index of Multiple Deprivation Score 2010 took 0.32111692428588867s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Score 2010 took 30.26606845855713s
Security | Check HTTPS for English Index of Multiple Deprivation Score 2010 took 0.10740232467651367s
Interpretability | RDF structures check for English Index of Multiple Deprivation Score 2010 took 0.19155502319335938s
Versatility | Serialization formats check for English Index of Multiple Deprivation Score 2010 took 0.1891040802001953s
Availability | RDF dump link check for English Index of Multiple Deprivation Score 2010 took 41.11255669593811s
License | MR license check for English Index of Multiple Deprivation Score 2010 took 0.1280660629272461s
License | HR license check for English Index of Multiple Deprivation Score 2010 took 30.126370906829834s
Amount of data | Number of property check for English Index of Multiple Deprivation Score 2010 took 0.20073771476745605s
Understandability | Number of label check for English Index of Multiple Deprivation Score 2010 took 0.12003326416015625s
Understandability | URI regex check for English Index of Multiple Deprivation Score 2010 took 0.3705325126647949s
Understandability | Vocabs check for English Index of Multiple Deprivation Score 2010 took 0.17970585823059082s
Verifiability | Authors check for English Index of Multiple Deprivation Score 2010 took 0.4916231632232666s
Verifiability | Publishers check for English Index of Multiple Deprivation Score 2010 took 0.18514657020568848s
Performance | Throughput check for English Index of Multiple Deprivation Score 2010 took 10.950802564620972s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Score 2010 took 7.128715515136719e-05s
Verifiability | Contribs. check for English Index of Multiple Deprivation Score 2010 took 0.1222531795501709s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Score 2010 took 0.18764615058898926s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.11788225173950195s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.12030696868896484s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Score 2010 took 0.11931800842285156s
Currency | Creation date check for English Index of Multiple Deprivation Score 2010 took 0.30976343154907227s
Currency | Modification date check for English Index of Multiple Deprivation Score 2010 took 0.18135595321655273s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Score 2010 took 1.9806444644927979s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Score 2010 took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Score 2010 took 0.12145805358886719s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Score 2010 took 0.11857342720031738s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Score 2010 took 0.18036270141601562s
Consistency | Disjoint class check for English Index of Multiple Deprivation Score 2010 took 0.18820953369140625s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Score 2010 took 0.32762861251831055s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Score 2010 took 1.3215999603271484s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Score 2010 took 1.5079503059387207s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.00016188621520996094s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.18754982948303223s
Security | Sign check for English Index of Multiple Deprivation Score 2010 took 0.1816394329071045s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Score 2010 took 0.275280237197876s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Score 2010 took 0.020780563354492188s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Score 2010 took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Score 2010 took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Score 2010 took 3.62396240234375e-05s
Interoperability | Check the re-using of existing vocabs for English Index of Multiple Deprivation Score 2010 took 1.1920928955078125e-06s
Believability | Calculation of trust value for English Index of Multiple Deprivation Score 2010 took 8.344650268554688e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-score-2010 took 250.23004293441772s
Availability | SPARQL endpoint availability check for English WordNet took 8.749961853027344e-05s
Availability | VoID file availability check for English WordNet took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for English WordNet took 0.29362964630126953s
Reputation | Calculation of the PageRank for English WordNet took 0.020737171173095703s
Interlinking | Calculation of Degree of Connection for English WordNet took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for English WordNet took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for English WordNet took 3.4332275390625e-05s
Believability | Calculation of trust value for English WordNet took 1.1682510375976562e-05s
INFO | --- Analysis for english-wordnet took 3.160472869873047s
Availability | SPARQL endpoint availability check for Enipedia - Energy Industry Data took 0.07131719589233398s
Availability | VoID file availability check for Enipedia - Energy Industry Data took 0.0004303455352783203s
Completeness | Calculation of interlinking completeness for Enipedia - Energy Industry Data took 0.2973299026489258s
Reputation | Calculation of the PageRank for Enipedia - Energy Industry Data took 0.020606517791748047s
Interlinking | Calculation of Degree of Connection for Enipedia - Energy Industry Data took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Enipedia - Energy Industry Data took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Enipedia - Energy Industry Data took 9.846687316894531e-05s
Believability | Calculation of trust value for Enipedia - Energy Industry Data took 1.1682510375976562e-05s
INFO | --- Analysis for enipedia took 2.599728584289551s
Availability | SPARQL endpoint availability check for Enslaved.org took 8.869171142578125e-05s
Availability | VoID file availability check for Enslaved.org took 0.000583648681640625s
Completeness | Calculation of interlinking completeness for Enslaved.org took 0.2948415279388428s
Reputation | Calculation of the PageRank for Enslaved.org took 0.022608280181884766s
Interlinking | Calculation of Degree of Connection for Enslaved.org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Enslaved.org took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Enslaved.org took 3.123283386230469e-05s
Believability | Calculation of trust value for Enslaved.org took 1.1682510375976562e-05s
INFO | --- Analysis for enslaved.org took 4.843018054962158s
Availability | SPARQL endpoint availability check for ENTICE Educational Episodes Knowledge Graph took 0.34242725372314453s
Availability | VoID file availability check for ENTICE Educational Episodes Knowledge Graph took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for ENTICE Educational Episodes Knowledge Graph took 0.26958799362182617s
Reputation | Calculation of the PageRank for ENTICE Educational Episodes Knowledge Graph took 0.020987510681152344s
Interlinking | Calculation of Degree of Connection for ENTICE Educational Episodes Knowledge Graph took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for ENTICE Educational Episodes Knowledge Graph took 0.0007259845733642578s
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 1.0967254638671875e-05s
INFO | --- Analysis for entice-graph took 2.9930074214935303s
Availability | SPARQL endpoint availability check for Entrez Gene took 8.487701416015625e-05s
Availability | VoID file availability check for Entrez Gene took 0.0008349418640136719s
Completeness | Calculation of interlinking completeness for Entrez Gene took 0.26877260208129883s
Reputation | Calculation of the PageRank for Entrez Gene took 0.021902084350585938s
Interlinking | Calculation of Degree of Connection for Entrez Gene took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Entrez Gene took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Entrez Gene took 3.719329833984375e-05s
Believability | Calculation of trust value for Entrez Gene took 1.0251998901367188e-05s
INFO | --- Analysis for entrez_gene took 26.849773168563843s
Availability | SPARQL endpoint availability check for Environment Agency Bathing Water Quality took 0.9562540054321289s
Availability | VoID file availability check for Environment Agency Bathing Water Quality took 0.0006613731384277344s
Completeness | Calculation of interlinking completeness for Environment Agency Bathing Water Quality took 0.2664055824279785s
Reputation | Calculation of the PageRank for Environment Agency Bathing Water Quality took 0.02270364761352539s
Interlinking | Calculation of Degree of Connection for Environment Agency Bathing Water Quality took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Environment Agency Bathing Water Quality took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Environment Agency Bathing Water Quality took 5.030632019042969e-05s
Believability | Calculation of trust value for Environment Agency Bathing Water Quality took 9.298324584960938e-06s
INFO | --- Analysis for environment-agency-bathing-water-quality took 10.851809024810791s
Availability | SPARQL endpoint availability check for environment.data.gov.uk took 0.261462926864624s
Availability | VoID file availability check for environment.data.gov.uk took 0.0006778240203857422s
Completeness | Calculation of interlinking completeness for environment.data.gov.uk took 0.2832062244415283s
Reputation | Calculation of the PageRank for environment.data.gov.uk took 0.020797252655029297s
Interlinking | Calculation of Degree of Connection for environment.data.gov.uk took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for environment.data.gov.uk took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for environment.data.gov.uk took 5.3882598876953125e-05s
Believability | Calculation of trust value for environment.data.gov.uk took 8.821487426757812e-06s
INFO | --- Analysis for environment-data-gov-uk took 9.400168418884277s
Availability | SPARQL endpoint availability check for EARTh took 272.204549074173s
Availability | VoID file availability check for EARTh took 0.0004382133483886719s
Completeness | Calculation of interlinking completeness for EARTh took 0.29084062576293945s
Reputation | Calculation of the PageRank for EARTh took 0.020570993423461914s
Interlinking | Calculation of Degree of Connection for EARTh took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for EARTh took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for EARTh took 9.560585021972656e-05s
Believability | Calculation of trust value for EARTh took 7.152557373046875e-06s
INFO | --- Analysis for environmental-applications-reference-thesaurus took 563.7587249279022s
Availability | SPARQL endpoint availability check for Micka (EO metadata) @PSNC took 0.5818910598754883s
Availability | VoID file availability check for Micka (EO metadata) @PSNC took 0.0004947185516357422s
Extra | Recovery of all triples for Micka (EO metadata) @PSNC took 111.06434726715088s
Performance | Total latancy measurement for Micka (EO metadata) @PSNC took 0.8868298530578613s
Amount of data | Number of triples check for Micka (EO metadata) @PSNC took 9.430655241012573s
Interoperability | New terms check for Micka (EO metadata) @PSNC took 14.060350179672241s
Versatility | Languages check for Micka (EO metadata) @PSNC took 300.19444823265076s
Interpretability | Number of blank nodes check for Micka (EO metadata) @PSNC took 2.05600643157959s
Interpretability | RDF structures check for Micka (EO metadata) @PSNC took 0.24799346923828125s
Versatility | Serialization formats check for Micka (EO metadata) @PSNC took 8.28539514541626s
Availability | RDF dump link check for Micka (EO metadata) @PSNC took 0.2359774112701416s
License | MR license check for Micka (EO metadata) @PSNC took 0.44760870933532715s
License | HR license check for Micka (EO metadata) @PSNC took 300.20900559425354s
Amount of data | Number of property check for Micka (EO metadata) @PSNC took 0.1898484230041504s
Understandability | Number of label check for Micka (EO metadata) @PSNC took 1.556889295578003s
Understandability | URI regex check for Micka (EO metadata) @PSNC took 0.5206871032714844s
Understandability | Vocabs check for Micka (EO metadata) @PSNC took 0.4160020351409912s
Verifiability | Authors check for Micka (EO metadata) @PSNC took 0.1800837516784668s
Verifiability | Publishers check for Micka (EO metadata) @PSNC took 0.224700927734375s
Performance | Throughput check for Micka (EO metadata) @PSNC took 10.590140104293823s
Amount of data | Check the number of entities for Micka (EO metadata) @PSNC took 0.0001430511474609375s
Verifiability | Contribs. check for Micka (EO metadata) @PSNC took 0.17638039588928223s
Interlinking | sameAs chians check for Micka (EO metadata) @PSNC took 0.18068432807922363s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.4647181034088135s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.3942594528198242s
Timeliness | dataset update frequency check for Micka (EO metadata) @PSNC took 5.135983943939209s
Currency | Creation date check for Micka (EO metadata) @PSNC took 0.43903207778930664s
Currency | Modification date check for Micka (EO metadata) @PSNC took 0.23734283447265625s
Rep.Conc. | URIs length for Micka (EO metadata) @PSNC took 153.38279914855957s
Interoperability | New vocabularies check for Micka (EO metadata) @PSNC took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Micka (EO metadata) @PSNC took 0.1813349723815918s
Accuracy | Check Functional Property for Micka (EO metadata) @PSNC took 0.3704562187194824s
Accuracy | Check Inverse Functional Property for Micka (EO metadata) @PSNC took 0.3194620609283447s
Accuracy | Check Empty annotation labels for Micka (EO metadata) @PSNC took 33.61762595176697s
Accuracy | Check White space in annotation for Micka (EO metadata) @PSNC took 2.6155216693878174s
Accuracy | Check Datatype consistency for Micka (EO metadata) @PSNC took 2.529689311981201s
Consistency | Disjoint class check for Micka (EO metadata) @PSNC took 0.17342519760131836s
Consistency | Check Misplaced properties for Micka (EO metadata) @PSNC took 85.93564057350159s
Consistency | Misplaced classes for Micka (EO metadata) @PSNC took 8.13170599937439s
Consistency | Check Ontology hijacking for Micka (EO metadata) @PSNC took 36.56415343284607s
Consistency | Check Invalid usage of undefined classes for Micka (EO metadata) @PSNC took 1.3946120738983154s
Consistency | Check Invalid usage of undefined properties for Micka (EO metadata) @PSNC took 88.05097723007202s
Conciseness | Check Extensional conciseness for Micka (EO metadata) @PSNC took 2.695713520050049s
Conciseness | Check Intensional conciseness for Micka (EO metadata) @PSNC took 0.6615564823150635s
Security | Sign check for Micka (EO metadata) @PSNC took 0.8681294918060303s
Availability | Check URIs Dereferenciability for Micka (EO metadata) @PSNC took 10.232503414154053s
Completeness | Calculation of interlinking completeness for Micka (EO metadata) @PSNC took 0.49158763885498047s
Reputation | Calculation of the PageRank for Micka (EO metadata) @PSNC took 0.02080702781677246s
Interlinking | Calculation of Degree of Connection for Micka (EO metadata) @PSNC took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Micka (EO metadata) @PSNC took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Micka (EO metadata) @PSNC took 4.029273986816406e-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 6.4373016357421875e-06s
INFO | --- Analysis for EO_metadata took 2224.247414588928s
Availability | SPARQL endpoint availability check for Earth Observation Knowledge Packages took 9.298324584960938e-05s
Availability | VoID file availability check for Earth Observation Knowledge Packages took 0.0007612705230712891s
Completeness | Calculation of interlinking completeness for Earth Observation Knowledge Packages took 0.2750577926635742s
Reputation | Calculation of the PageRank for Earth Observation Knowledge Packages took 0.021539688110351562s
Interlinking | Calculation of Degree of Connection for Earth Observation Knowledge Packages took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Earth Observation Knowledge Packages took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Earth Observation Knowledge Packages took 3.337860107421875e-05s
Believability | Calculation of trust value for Earth Observation Knowledge Packages took 1.239776611328125e-05s
INFO | --- Analysis for EOKP-Datasets took 3.1542279720306396s
Availability | SPARQL endpoint availability check for EPA-CDR took 0.000152587890625s
Availability | VoID file availability check for EPA-CDR took 0.0007658004760742188s
Completeness | Calculation of interlinking completeness for EPA-CDR took 0.27405858039855957s
Reputation | Calculation of the PageRank for EPA-CDR took 0.020612478256225586s
Interlinking | Calculation of Degree of Connection for EPA-CDR took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EPA-CDR took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for EPA-CDR took 3.528594970703125e-05s
Believability | Calculation of trust value for EPA-CDR took 8.106231689453125e-06s
INFO | --- Analysis for epa-cdr took 6.523724317550659s
Availability | SPARQL endpoint availability check for EPA-FRS took 4.172325134277344e-05s
Availability | VoID file availability check for EPA-FRS took 0.001255035400390625s
Completeness | Calculation of interlinking completeness for EPA-FRS took 0.27540063858032227s
Reputation | Calculation of the PageRank for EPA-FRS took 0.02064990997314453s
Interlinking | Calculation of Degree of Connection for EPA-FRS took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EPA-FRS took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for EPA-FRS took 7.152557373046875e-05s
Believability | Calculation of trust value for EPA-FRS took 8.106231689453125e-06s
INFO | --- Analysis for epa-frs took 6.942777633666992s
Availability | SPARQL endpoint availability check for EPA-RCRA took 8.487701416015625e-05s
Availability | VoID file availability check for EPA-RCRA took 0.0005140304565429688s
Completeness | Calculation of interlinking completeness for EPA-RCRA took 0.26749300956726074s
Reputation | Calculation of the PageRank for EPA-RCRA took 0.020674943923950195s
Interlinking | Calculation of Degree of Connection for EPA-RCRA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EPA-RCRA took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for EPA-RCRA took 3.361701965332031e-05s
Believability | Calculation of trust value for EPA-RCRA took 3.814697265625e-06s
INFO | --- Analysis for epa-rcra took 5.6567137241363525s
Availability | SPARQL endpoint availability check for EPA-SRS took 8.559226989746094e-05s
Availability | VoID file availability check for EPA-SRS took 0.0007605552673339844s
Completeness | Calculation of interlinking completeness for EPA-SRS took 0.27277565002441406s
Reputation | Calculation of the PageRank for EPA-SRS took 0.020392417907714844s
Interlinking | Calculation of Degree of Connection for EPA-SRS took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EPA-SRS took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for EPA-SRS took 8.130073547363281e-05s
Believability | Calculation of trust value for EPA-SRS took 5.245208740234375e-06s
INFO | --- Analysis for epa-srs took 6.981462478637695s
Availability | SPARQL endpoint availability check for EPA-TRI took 4.220008850097656e-05s
Availability | VoID file availability check for EPA-TRI took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for EPA-TRI took 0.2695138454437256s
Reputation | Calculation of the PageRank for EPA-TRI took 0.021753311157226562s
Interlinking | Calculation of Degree of Connection for EPA-TRI took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for EPA-TRI took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for EPA-TRI took 3.4332275390625e-05s
Believability | Calculation of trust value for EPA-TRI took 9.775161743164062e-06s
INFO | --- Analysis for epa-tri took 5.650700569152832s
Availability | SPARQL endpoint availability check for ePrints Harvest (RKBExplorer) took 0.023457050323486328s
Availability | VoID file availability check for ePrints Harvest (RKBExplorer) took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for ePrints Harvest (RKBExplorer) took 0.26972270011901855s
Reputation | Calculation of the PageRank for ePrints Harvest (RKBExplorer) took 0.02069830894470215s
Interlinking | Calculation of Degree of Connection for ePrints Harvest (RKBExplorer) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for ePrints Harvest (RKBExplorer) took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for ePrints Harvest (RKBExplorer) took 0.00013780593872070312s
Believability | Calculation of trust value for ePrints Harvest (RKBExplorer) took 1.049041748046875e-05s
INFO | --- Analysis for eprints-harvest-rkbexplorer took 2.6215944290161133s
Availability | SPARQL endpoint availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.33489418029785156s
Availability | VoID file availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.0005567073822021484s
Completeness | Calculation of interlinking completeness for European Pollutant Release and Transfer Register (E-PRTR) took 0.27268409729003906s
Reputation | Calculation of the PageRank for European Pollutant Release and Transfer Register (E-PRTR) took 0.022324323654174805s
Interlinking | Calculation of Degree of Connection for European Pollutant Release and Transfer Register (E-PRTR) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for European Pollutant Release and Transfer Register (E-PRTR) took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for European Pollutant Release and Transfer Register (E-PRTR) took 8.082389831542969e-05s
Believability | Calculation of trust value for European Pollutant Release and Transfer Register (E-PRTR) took 9.5367431640625e-06s
INFO | --- Analysis for eprtr took 3.612130880355835s
Availability | SPARQL endpoint availability check for Railway Infrastructure KG took 0.48552489280700684s
Availability | VoID file availability check for Railway Infrastructure KG took 0.0005545616149902344s
Extra | Recovery of all triples for Railway Infrastructure KG took 59.199652910232544s
Performance | Total latancy measurement for Railway Infrastructure KG took 1.0513184070587158s
Amount of data | Number of triples check for Railway Infrastructure KG took 0.22344183921813965s
Interoperability | New terms check for Railway Infrastructure KG took 1.6553447246551514s
Versatility | Languages check for Railway Infrastructure KG took 81.28857350349426s
Interpretability | Number of blank nodes check for Railway Infrastructure KG took 0.22144365310668945s
Interpretability | RDF structures check for Railway Infrastructure KG took 0.37749791145324707s
Versatility | Serialization formats check for Railway Infrastructure KG took 0.2615358829498291s
Availability | RDF dump link check for Railway Infrastructure KG took 0.22192049026489258s
License | MR license check for Railway Infrastructure KG took 0.30682802200317383s
License | HR license check for Railway Infrastructure KG took 65.31234049797058s
Amount of data | Number of property check for Railway Infrastructure KG took 0.22764921188354492s
Understandability | Number of label check for Railway Infrastructure KG took 0.41584157943725586s
Understandability | URI regex check for Railway Infrastructure KG took 0.4477362632751465s
Understandability | Vocabs check for Railway Infrastructure KG took 0.21675348281860352s
Verifiability | Authors check for Railway Infrastructure KG took 0.28165578842163086s
Verifiability | Publishers check for Railway Infrastructure KG took 0.2047429084777832s
Performance | Throughput check for Railway Infrastructure KG took 10.390367031097412s
Verifiability | Contribs. check for Railway Infrastructure KG took 0.2959151268005371s
Interlinking | sameAs chians check for Railway Infrastructure KG took 0.22196102142333984s
Interlinking | skos check for Railway Infrastructure KG took 0.253521203994751s
Interlinking | skos check for Railway Infrastructure KG took 0.2569084167480469s
Timeliness | dataset update frequency check for Railway Infrastructure KG took 0.20438885688781738s
Currency | Creation date check for Railway Infrastructure KG took 0.4468390941619873s
Currency | Modification date check for Railway Infrastructure KG took 0.21620416641235352s
Rep.Conc. | URIs length for Railway Infrastructure KG took 22.159449100494385s
Consistency | Deprecated classes/propertiers check for Railway Infrastructure KG took 0.206895112991333s
Accuracy | Check Functional Property for Railway Infrastructure KG took 0.2055525779724121s
Accuracy | Check Inverse Functional Property for Railway Infrastructure KG took 0.2175436019897461s
Accuracy | Check Empty annotation labels for Railway Infrastructure KG took 13.98884892463684s
Accuracy | Check White space in annotation for Railway Infrastructure KG took 2.6662774085998535s
Accuracy | Check Datatype consistency for Railway Infrastructure KG took 2.5335159301757812s
Consistency | Disjoint class check for Railway Infrastructure KG took 0.24851560592651367s
Consistency | Check Misplaced properties for Railway Infrastructure KG took 1.6919221878051758s
Consistency | Misplaced classes for Railway Infrastructure KG took 8.120126485824585s
Consistency | Check Ontology hijacking for Railway Infrastructure KG took 18.251253843307495s
Consistency | Check Invalid usage of undefined classes for Railway Infrastructure KG took 1.486487865447998s
Consistency | Check Invalid usage of undefined properties for Railway Infrastructure KG took 2.835932493209839s
Conciseness | Check Extensional conciseness for Railway Infrastructure KG took 2.883892297744751s
Conciseness | Check Intensional conciseness for Railway Infrastructure KG took 0.34071922302246094s
Security | Sign check for Railway Infrastructure KG took 0.6363849639892578s
Availability | Check URIs Dereferenciability for Railway Infrastructure KG took 2158.6205866336823s
Completeness | Calculation of interlinking completeness for Railway Infrastructure KG took 0.615936279296875s
Reputation | Calculation of the PageRank for Railway Infrastructure KG took 0.02259993553161621s
Interlinking | Calculation of Degree of Connection for Railway Infrastructure KG took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Railway Infrastructure KG took 0.0008065700531005859s
Interlinking | Calculation of Clustering coefficient for Railway Infrastructure KG took 8.535385131835938e-05s
Interoperability | Check the re-using of existing vocabs for Railway Infrastructure KG took 459.12352228164673s
Believability | Calculation of trust value for Railway Infrastructure KG took 1.1920928955078125e-05s
INFO | --- Analysis for ERAKG took 3034.359783887863s
Availability | SPARQL endpoint availability check for reg took 8.368492126464844e-05s
Availability | VoID file availability check for reg took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for reg took 0.2642991542816162s
Reputation | Calculation of the PageRank for reg took 0.0203702449798584s
Interlinking | Calculation of Degree of Connection for reg took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for reg took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for reg took 1.1920928955078125e-05s
Believability | Calculation of trust value for reg took 1.2159347534179688e-05s
INFO | --- Analysis for erg took 2.3878366947174072s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.2100238800048828s
Availability | VoID file availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Kingdom of Spain took 0.2807745933532715s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Kingdom of Spain took 0.020569801330566406s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Kingdom of Spain took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Kingdom of Spain took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Kingdom of Spain took 3.218650817871094e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Kingdom of Spain took 8.106231689453125e-06s
INFO | --- Analysis for es-msssi-drug-prices took 2.9103918075561523s
Availability | SPARQL endpoint availability check for ESD Standards: Controlled lists for the UK public sector took 9.059906005859375e-05s
Availability | VoID file availability check for ESD Standards: Controlled lists for the UK public sector took 0.0009300708770751953s
Completeness | Calculation of interlinking completeness for ESD Standards: Controlled lists for the UK public sector took 0.272777795791626s
Reputation | Calculation of the PageRank for ESD Standards: Controlled lists for the UK public sector took 0.02054452896118164s
Interlinking | Calculation of Degree of Connection for ESD Standards: Controlled lists for the UK public sector took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ESD Standards: Controlled lists for the UK public sector took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for ESD Standards: Controlled lists for the UK public sector took 8.463859558105469e-05s
Believability | Calculation of trust value for ESD Standards: Controlled lists for the UK public sector took 1.0251998901367188e-05s
INFO | --- Analysis for esd-standards took 4.0823259353637695s
Availability | SPARQL endpoint availability check for ESD-Toolkit took 9.202957153320312e-05s
Availability | VoID file availability check for ESD-Toolkit took 0.0006110668182373047s
Completeness | Calculation of interlinking completeness for ESD-Toolkit took 0.2994997501373291s
Reputation | Calculation of the PageRank for ESD-Toolkit took 0.020874738693237305s
Interlinking | Calculation of Degree of Connection for ESD-Toolkit took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ESD-Toolkit took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for ESD-Toolkit took 7.081031799316406e-05s
Believability | Calculation of trust value for ESD-Toolkit took 9.5367431640625e-06s
INFO | --- Analysis for esd-toolkit took 3.1504693031311035s
Availability | SPARQL endpoint availability check for Dataset Esis took 8.654594421386719e-05s
Availability | VoID file availability check for Dataset Esis took 0.0005428791046142578s
Completeness | Calculation of interlinking completeness for Dataset Esis took 0.27057909965515137s
Reputation | Calculation of the PageRank for Dataset Esis took 0.021630525588989258s
Interlinking | Calculation of Degree of Connection for Dataset Esis took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Dataset Esis took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Dataset Esis took 3.457069396972656e-05s
Believability | Calculation of trust value for Dataset Esis took 1.2159347534179688e-05s
INFO | --- Analysis for esislearning took 2.815244674682617s
Availability | SPARQL endpoint availability check for The European Science Vocabulary (EuroSciVoc) took 9.036064147949219e-05s
Availability | VoID file availability check for The European Science Vocabulary (EuroSciVoc) took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for The European Science Vocabulary (EuroSciVoc) took 0.2678370475769043s
Reputation | Calculation of the PageRank for The European Science Vocabulary (EuroSciVoc) took 0.02120375633239746s
Interlinking | Calculation of Degree of Connection for The European Science Vocabulary (EuroSciVoc) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for The European Science Vocabulary (EuroSciVoc) took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for The European Science Vocabulary (EuroSciVoc) took 3.0040740966796875e-05s
Believability | Calculation of trust value for The European Science Vocabulary (EuroSciVoc) took 1.0967254638671875e-05s
INFO | --- Analysis for ESV took 4.163402557373047s
Availability | SPARQL endpoint availability check for Etymological Dictionary of Latin in LiLa took 0.6158084869384766s
Availability | VoID file availability check for Etymological Dictionary of Latin in LiLa took 0.0006160736083984375s
Completeness | Calculation of interlinking completeness for Etymological Dictionary of Latin in LiLa took 0.27961206436157227s
Reputation | Calculation of the PageRank for Etymological Dictionary of Latin in LiLa took 0.022378921508789062s
Interlinking | Calculation of Degree of Connection for Etymological Dictionary of Latin in LiLa took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Etymological Dictionary of Latin in LiLa took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Etymological Dictionary of Latin in LiLa took 4.5299530029296875e-05s
Believability | Calculation of trust value for Etymological Dictionary of Latin in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for EtymologicalDictionaryofLatin took 4.269371271133423s
Availability | SPARQL endpoint availability check for EU Agencies and decentralized bodies (Agencies) took 7.250699758529663s
Availability | VoID file availability check for EU Agencies and decentralized bodies (Agencies) took 0.0005674362182617188s
Completeness | Calculation of interlinking completeness for EU Agencies and decentralized bodies (Agencies) took 0.262434720993042s
Reputation | Calculation of the PageRank for EU Agencies and decentralized bodies (Agencies) took 0.020207881927490234s
Interlinking | Calculation of Degree of Connection for EU Agencies and decentralized bodies (Agencies) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EU Agencies and decentralized bodies (Agencies) took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for EU Agencies and decentralized bodies (Agencies) took 7.176399230957031e-05s
Believability | Calculation of trust value for EU Agencies and decentralized bodies (Agencies) took 1.0013580322265625e-05s
INFO | --- Analysis for eu-agencies-bodies took 20.555455923080444s
Availability | SPARQL endpoint availability check for Institutions and Bodies of the European Union took 4.1484832763671875e-05s
Availability | VoID file availability check for Institutions and Bodies of the European Union took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for Institutions and Bodies of the European Union took 0.2880098819732666s
Reputation | Calculation of the PageRank for Institutions and Bodies of the European Union took 0.020995616912841797s
Interlinking | Calculation of Degree of Connection for Institutions and Bodies of the European Union took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Institutions and Bodies of the European Union took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Institutions and Bodies of the European Union took 6.794929504394531e-05s
Believability | Calculation of trust value for Institutions and Bodies of the European Union took 7.62939453125e-06s
INFO | --- Analysis for eu-institutions took 8.372596502304077s
Availability | SPARQL endpoint availability check for EU Parliament Media Library took 1.2300105094909668s
Availability | VoID file availability check for EU Parliament Media Library took 0.0005650520324707031s
Completeness | Calculation of interlinking completeness for EU Parliament Media Library took 0.2678799629211426s
Reputation | Calculation of the PageRank for EU Parliament Media Library took 0.02035832405090332s
Interlinking | Calculation of Degree of Connection for EU Parliament Media Library took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EU Parliament Media Library took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for EU Parliament Media Library took 3.1948089599609375e-05s
Believability | Calculation of trust value for EU Parliament Media Library took 7.867813110351562e-06s
INFO | --- Analysis for eu-parliament-media took 9.481805801391602s
Availability | SPARQL endpoint availability check for EU Who Is Who took 1.3505558967590332s
Availability | VoID file availability check for EU Who Is Who took 0.0006234645843505859s
Completeness | Calculation of interlinking completeness for EU Who Is Who took 0.27219271659851074s
Reputation | Calculation of the PageRank for EU Who Is Who took 0.020451784133911133s
Interlinking | Calculation of Degree of Connection for EU Who Is Who took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for EU Who Is Who took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for EU Who Is Who took 3.4332275390625e-05s
Believability | Calculation of trust value for EU Who Is Who took 9.298324584960938e-06s
INFO | --- Analysis for eu-who-is-who took 14.297930002212524s
Availability | SPARQL endpoint availability check for EUMIDA as Linked Data took 1.212756872177124s
Availability | VoID file availability check for EUMIDA as Linked Data took 0.0005640983581542969s
Completeness | Calculation of interlinking completeness for EUMIDA as Linked Data took 0.27262425422668457s
Reputation | Calculation of the PageRank for EUMIDA as Linked Data took 0.020613908767700195s
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.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for EUMIDA as Linked Data took 4.076957702636719e-05s
Believability | Calculation of trust value for EUMIDA as Linked Data took 8.106231689453125e-06s
INFO | --- Analysis for eumida-linked-data took 11.775323152542114s
Availability | SPARQL endpoint availability check for European Nature Information System took 0.3150629997253418s
Availability | VoID file availability check for European Nature Information System took 0.0005583763122558594s
Completeness | Calculation of interlinking completeness for European Nature Information System took 0.27151989936828613s
Reputation | Calculation of the PageRank for European Nature Information System took 0.020625591278076172s
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.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for European Nature Information System took 0.00010347366333007812s
Believability | Calculation of trust value for European Nature Information System took 1.1444091796875e-05s
INFO | --- Analysis for eunis took 4.113950967788696s
Availability | SPARQL endpoint availability check for EUR-Lex as Linked Data took 7.359606027603149s
Availability | VoID file availability check for EUR-Lex as Linked Data took 0.0007178783416748047s
Completeness | Calculation of interlinking completeness for EUR-Lex as Linked Data took 0.27140021324157715s
Reputation | Calculation of the PageRank for EUR-Lex as Linked Data took 0.02046656608581543s
Interlinking | Calculation of Degree of Connection for EUR-Lex as Linked Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for EUR-Lex as Linked Data took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for EUR-Lex as Linked Data took 7.128715515136719e-05s
Believability | Calculation of trust value for EUR-Lex as Linked Data took 1.239776611328125e-05s
INFO | --- Analysis for eur-lex-rdf took 19.08930253982544s
Availability | SPARQL endpoint availability check for Standard Eurobarometer took 1.2653765678405762s
Availability | VoID file availability check for Standard Eurobarometer took 0.00036215782165527344s
Completeness | Calculation of interlinking completeness for Standard Eurobarometer took 0.2690308094024658s
Reputation | Calculation of the PageRank for Standard Eurobarometer took 0.020332813262939453s
Interlinking | Calculation of Degree of Connection for Standard Eurobarometer took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Standard Eurobarometer took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Standard Eurobarometer took 3.8623809814453125e-05s
Believability | Calculation of trust value for Standard Eurobarometer took 8.106231689453125e-06s
INFO | --- Analysis for eurobarometer-standard took 11.087493419647217s
Availability | SPARQL endpoint availability check for European Election Results took 1.1174170970916748s
Availability | VoID file availability check for European Election Results took 0.0007026195526123047s
Completeness | Calculation of interlinking completeness for European Election Results took 0.2668910026550293s
Reputation | Calculation of the PageRank for European Election Results took 0.0206301212310791s
Interlinking | Calculation of Degree of Connection for European Election Results took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for European Election Results took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for European Election Results took 4.1961669921875e-05s
Believability | Calculation of trust value for European Election Results took 9.775161743164062e-06s
INFO | --- Analysis for european-election-results took 11.157596826553345s
Availability | SPARQL endpoint availability check for EPO patents took 0.34721803665161133s
Availability | VoID file availability check for EPO patents took 0.0006690025329589844s
Extra | Recovery of all triples for EPO patents took 27.304700136184692s
Performance | Total latancy measurement for EPO patents took 1.0227234363555908s
Amount of data | Number of triples check for EPO patents took 90.23479628562927s
Versatility | Languages check for EPO patents took 100.18882441520691s
Interpretability | Number of blank nodes check for EPO patents took 90.24065160751343s
Interpretability | RDF structures check for EPO patents took 0.26363444328308105s
Versatility | Serialization formats check for EPO patents took 0.23928236961364746s
Availability | RDF dump link check for EPO patents took 0.15549468994140625s
License | MR license check for EPO patents took 0.23797297477722168s
License | HR license check for EPO patents took 90.2625024318695s
Amount of data | Number of property check for EPO patents took 0.23186063766479492s
Understandability | Number of label check for EPO patents took 90.30332636833191s
Understandability | URI regex check for EPO patents took 0.462266206741333s
Understandability | Vocabs check for EPO patents took 0.22537589073181152s
Verifiability | Authors check for EPO patents took 0.22836589813232422s
Verifiability | Publishers check for EPO patents took 0.19277191162109375s
Performance | Throughput check for EPO patents took 11.083154201507568s
Amount of data | Check the number of entities for EPO patents took 7.581710815429688e-05s
Verifiability | Contribs. check for EPO patents took 0.17321467399597168s
Interlinking | sameAs chians check for EPO patents took 0.1721494197845459s
Interlinking | skos check for EPO patents took 0.1780099868774414s
Interlinking | skos check for EPO patents took 0.14764809608459473s
Timeliness | dataset update frequency check for EPO patents took 0.1575155258178711s
Currency | Creation date check for EPO patents took 0.36026644706726074s
Currency | Modification date check for EPO patents took 0.3412926197052002s
Rep.Conc. | URIs length for EPO patents took 133.95061779022217s
Interoperability | New vocabularies check for EPO patents took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for EPO patents took 0.2381289005279541s
Accuracy | Check Empty annotation labels for EPO patents took 18.47886610031128s
Accuracy | Check White space in annotation for EPO patents took 2.9217774868011475s
Accuracy | Check Datatype consistency for EPO patents took 4.773123264312744s
Consistency | Disjoint class check for EPO patents took 0.2732396125793457s
Consistency | Check Misplaced properties for EPO patents took 100.36885333061218s
Consistency | Check Ontology hijacking for EPO patents took 21.914563417434692s
Consistency | Check Invalid usage of undefined classes for EPO patents took 1.569817304611206s
Consistency | Check Invalid usage of undefined properties for EPO patents took 101.64296507835388s
Conciseness | Check Extensional conciseness for EPO patents took 2.793696403503418s
Conciseness | Check Intensional conciseness for EPO patents took 0.3467710018157959s
Security | Sign check for EPO patents took 0.3531818389892578s
Availability | Check URIs Dereferenciability for EPO patents took 1.959338665008545s
Completeness | Calculation of interlinking completeness for EPO patents took 0.4440736770629883s
Reputation | Calculation of the PageRank for EPO patents took 0.02144169807434082s
Interlinking | Calculation of Degree of Connection for EPO patents took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for EPO patents took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for EPO patents took 5.555152893066406e-05s
Interoperability | Check the re-using of existing vocabs for EPO patents took 1.6689300537109375e-06s
Believability | Calculation of trust value for EPO patents took 8.344650268554688e-06s
INFO | --- Analysis for European_Patent_Information took 1191.680584192276s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data V1.0 took 0.00010848045349121094s
Availability | VoID file availability check for Europeana Linked Open Data V1.0 took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data V1.0 took 0.3124356269836426s
Reputation | Calculation of the PageRank for Europeana Linked Open Data V1.0 took 0.020908355712890625s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data V1.0 took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data V1.0 took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data V1.0 took 0.00010037422180175781s
Believability | Calculation of trust value for Europeana Linked Open Data V1.0 took 1.239776611328125e-05s
INFO | --- Analysis for europeana-lod-v1 took 6.795126438140869s
Availability | SPARQL endpoint availability check for Europeana SPARQL took 0.34751439094543457s
Availability | VoID file availability check for Europeana SPARQL took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for Europeana SPARQL took 0.263110876083374s
Reputation | Calculation of the PageRank for Europeana SPARQL took 0.020472049713134766s
Interlinking | Calculation of Degree of Connection for Europeana SPARQL took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Europeana SPARQL took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Europeana SPARQL took 4.935264587402344e-05s
Believability | Calculation of trust value for Europeana SPARQL took 1.239776611328125e-05s
INFO | --- Analysis for europeana-sparql took 6.084842920303345s
Availability | SPARQL endpoint availability check for EuroSentiment took 0.10149359703063965s
Availability | VoID file availability check for EuroSentiment took 0.0004622936248779297s
Completeness | Calculation of interlinking completeness for EuroSentiment took 0.31459784507751465s
Reputation | Calculation of the PageRank for EuroSentiment took 0.022208213806152344s
Interlinking | Calculation of Degree of Connection for EuroSentiment took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EuroSentiment took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for EuroSentiment took 3.528594970703125e-05s
Believability | Calculation of trust value for EuroSentiment took 1.1920928955078125e-05s
INFO | --- Analysis for eurosentiment took 3.180468797683716s
Availability | SPARQL endpoint availability check for Eurostat RDF datasets took 4.220008850097656e-05s
Availability | VoID file availability check for Eurostat RDF datasets took 0.0005953311920166016s
Completeness | Calculation of interlinking completeness for Eurostat RDF datasets took 0.27399182319641113s
Reputation | Calculation of the PageRank for Eurostat RDF datasets took 0.020340919494628906s
Interlinking | Calculation of Degree of Connection for Eurostat RDF datasets took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Eurostat RDF datasets took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Eurostat RDF datasets took 8.058547973632812e-05s
Believability | Calculation of trust value for Eurostat RDF datasets took 8.58306884765625e-06s
INFO | --- Analysis for eurostat-rdf took 11.127671718597412s
Availability | SPARQL endpoint availability check for EuroVoc took 0.17853569984436035s
Availability | VoID file availability check for EuroVoc took 0.000431060791015625s
Extra | Recovery of all triples for EuroVoc took 176.62133526802063s
Performance | Total latancy measurement for EuroVoc took 0.5658366680145264s
Amount of data | Number of triples check for EuroVoc took 151.64629459381104s
Interoperability | New terms check for EuroVoc took 63.71670579910278s
Versatility | Languages check for EuroVoc took 300.0548765659332s
Interpretability | Number of blank nodes check for EuroVoc took 18.67914581298828s
Security | Check HTTPS for EuroVoc took 0.30954408645629883s
Interpretability | RDF structures check for EuroVoc took 0.8733971118927002s
Versatility | Serialization formats check for EuroVoc took 3.0584375858306885s
Availability | RDF dump link check for EuroVoc took 0.22647356986999512s
License | MR license check for EuroVoc took 0.3707144260406494s
License | HR license check for EuroVoc took 300.07445216178894s
Amount of data | Number of property check for EuroVoc took 0.17378711700439453s
Understandability | Number of label check for EuroVoc took 2.3583662509918213s
Understandability | URI regex check for EuroVoc took 0.3759167194366455s
Understandability | Vocabs check for EuroVoc took 0.09481573104858398s
Verifiability | Authors check for EuroVoc took 0.24807238578796387s
Verifiability | Publishers check for EuroVoc took 0.24852728843688965s
Performance | Throughput check for EuroVoc took 10.525504350662231s
Amount of data | Check the number of entities for EuroVoc took 0.00016760826110839844s
Verifiability | Contribs. check for EuroVoc took 0.18935036659240723s
Interlinking | sameAs chians check for EuroVoc took 7.159480333328247s
Interlinking | skos check for EuroVoc took 0.34682250022888184s
Interlinking | skos check for EuroVoc took 0.12810707092285156s
Timeliness | dataset update frequency check for EuroVoc took 0.23090624809265137s
Currency | Creation date check for EuroVoc took 0.43217921257019043s
Currency | Modification date check for EuroVoc took 0.2772960662841797s
Rep.Conc. | URIs length for EuroVoc took 484.970342874527s
Interoperability | New vocabularies check for EuroVoc took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for EuroVoc took 0.169144868850708s
Accuracy | Check Functional Property for EuroVoc took 0.24989032745361328s
Accuracy | Check Inverse Functional Property for EuroVoc took 0.16107678413391113s
Accuracy | Check Empty annotation labels for EuroVoc took 40.95196771621704s
Accuracy | Check White space in annotation for EuroVoc took 3.12091326713562s
Accuracy | Check Datatype consistency for EuroVoc took 2.604508638381958s
Consistency | Disjoint class check for EuroVoc took 0.14929771423339844s
Consistency | Check Misplaced properties for EuroVoc took 300.41628670692444s
Consistency | Misplaced classes for EuroVoc took 8.393225193023682s
Consistency | Check Ontology hijacking for EuroVoc took 68.84619569778442s
Consistency | Check Invalid usage of undefined classes for EuroVoc took 1.6924667358398438s
Consistency | Check Invalid usage of undefined properties for EuroVoc took 301.52780866622925s
Conciseness | Check Extensional conciseness for EuroVoc took 3.013488292694092s
Conciseness | Check Intensional conciseness for EuroVoc took 0.5055084228515625s
Security | Sign check for EuroVoc took 0.14368319511413574s
Availability | Check URIs Dereferenciability for EuroVoc took 11.153978824615479s
Completeness | Calculation of interlinking completeness for EuroVoc took 0.8145792484283447s
Reputation | Calculation of the PageRank for EuroVoc took 0.021132469177246094s
Interlinking | Calculation of Degree of Connection for EuroVoc took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for EuroVoc took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for EuroVoc took 9.369850158691406e-05s
Interoperability | Check the re-using of existing vocabs for EuroVoc took 1.1920928955078125e-06s
Believability | Calculation of trust value for EuroVoc took 1.2636184692382812e-05s
INFO | --- Analysis for eurovoc took 14311.657757997513s
Availability | SPARQL endpoint availability check for Farmacias en Euskadi took 4.38690185546875e-05s
Availability | VoID file availability check for Farmacias en Euskadi took 0.00033545494079589844s
Completeness | Calculation of interlinking completeness for Farmacias en Euskadi took 0.28428149223327637s
Reputation | Calculation of the PageRank for Farmacias en Euskadi took 0.02051830291748047s
Interlinking | Calculation of Degree of Connection for Farmacias en Euskadi took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Farmacias en Euskadi took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Farmacias en Euskadi took 4.7206878662109375e-05s
Believability | Calculation of trust value for Farmacias en Euskadi took 8.58306884765625e-06s
INFO | --- Analysis for euskadi-farmacias took 5.0342793464660645s
Availability | SPARQL endpoint availability check for Research outputs of Eastern University Sri Lanka took 0.7718007564544678s
Availability | VoID file availability check for Research outputs of Eastern University Sri Lanka took 0.0005819797515869141s
Completeness | Calculation of interlinking completeness for Research outputs of Eastern University Sri Lanka took 0.275282621383667s
Reputation | Calculation of the PageRank for Research outputs of Eastern University Sri Lanka took 0.020683765411376953s
Interlinking | Calculation of Degree of Connection for Research outputs of Eastern University Sri Lanka took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Research outputs of Eastern University Sri Lanka took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Research outputs of Eastern University Sri Lanka took 3.218650817871094e-05s
Believability | Calculation of trust value for Research outputs of Eastern University Sri Lanka took 1.0013580322265625e-05s
INFO | --- Analysis for EUSL-Research-Data-Sri_Lanka took 4.490694046020508s
Availability | SPARQL endpoint availability check for Edinburgh University Theatre Company Productions took 0.26097989082336426s
Availability | VoID file availability check for Edinburgh University Theatre Company Productions took 0.0008594989776611328s
Completeness | Calculation of interlinking completeness for Edinburgh University Theatre Company Productions took 0.2747383117675781s
Reputation | Calculation of the PageRank for Edinburgh University Theatre Company Productions took 0.0214998722076416s
Interlinking | Calculation of Degree of Connection for Edinburgh University Theatre Company Productions took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Edinburgh University Theatre Company Productions took 0.0010144710540771484s
Interlinking | Calculation of Clustering coefficient for Edinburgh University Theatre Company Productions took 0.00010204315185546875s
Believability | Calculation of trust value for Edinburgh University Theatre Company Productions took 7.3909759521484375e-06s
INFO | --- Analysis for eutc-productions took 5.995405673980713s
Availability | SPARQL endpoint availability check for EventMedia took 0.31908655166625977s
Availability | VoID file availability check for EventMedia took 0.0003845691680908203s
Completeness | Calculation of interlinking completeness for EventMedia took 0.2706930637359619s
Reputation | Calculation of the PageRank for EventMedia took 0.02042531967163086s
Interlinking | Calculation of Degree of Connection for EventMedia took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EventMedia took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for EventMedia took 0.00010800361633300781s
Believability | Calculation of trust value for EventMedia took 6.9141387939453125e-06s
INFO | --- Analysis for event-media took 19.04323649406433s
Availability | SPARQL endpoint availability check for EventKG took 4.220008850097656e-05s
Availability | VoID file availability check for EventKG took 0.0007123947143554688s
Completeness | Calculation of interlinking completeness for EventKG took 0.26340150833129883s
Reputation | Calculation of the PageRank for EventKG took 0.021060705184936523s
Interlinking | Calculation of Degree of Connection for EventKG took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EventKG took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for EventKG took 8.535385131835938e-05s
Believability | Calculation of trust value for EventKG took 1.1444091796875e-05s
INFO | --- Analysis for eventkg took 4.6537535190582275s
Availability | SPARQL endpoint availability check for Eventseer took 6.255423069000244s
Availability | VoID file availability check for Eventseer took 0.0005071163177490234s
Completeness | Calculation of interlinking completeness for Eventseer took 0.2803456783294678s
Reputation | Calculation of the PageRank for Eventseer took 0.020697355270385742s
Interlinking | Calculation of Degree of Connection for Eventseer took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Eventseer took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Eventseer took 5.221366882324219e-05s
Believability | Calculation of trust value for Eventseer took 9.5367431640625e-06s
INFO | --- Analysis for eventseer took 8.748311758041382s
Availability | SPARQL endpoint availability check for Face Link took 9.036064147949219e-05s
Availability | VoID file availability check for Face Link took 0.0005278587341308594s
Completeness | Calculation of interlinking completeness for Face Link took 0.2701535224914551s
Reputation | Calculation of the PageRank for Face Link took 0.02097296714782715s
Interlinking | Calculation of Degree of Connection for Face Link took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Face Link took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Face Link took 3.528594970703125e-05s
Believability | Calculation of trust value for Face Link took 1.1920928955078125e-05s
INFO | --- Analysis for Face_Link took 2.4521219730377197s
Availability | SPARQL endpoint availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5554568767547607s
Availability | VoID file availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0004889965057373047s
Extra | Recovery of all triples for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 145.48622632026672s
Performance | Total latancy measurement for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.9108569622039795s
Amount of data | Number of triples check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 9.644290685653687s
Interoperability | New terms check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 14.200839281082153s
Versatility | Languages check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.22924757003784s
Interpretability | Number of blank nodes check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.0805702209472656s
Interpretability | RDF structures check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.2238931655883789s
Versatility | Serialization formats check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 10.249503374099731s
Availability | RDF dump link check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.2214365005493164s
License | MR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.3583407402038574s
License | HR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.2340602874756s
Amount of data | Number of property check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.1847076416015625s
Understandability | Number of label check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.3703725337982178s
Understandability | URI regex check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.7287998199462891s
Understandability | Vocabs check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.25461268424987793s
Verifiability | Authors check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.18572306632995605s
Verifiability | Publishers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.22762060165405273s
Performance | Throughput check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 10.73929238319397s
Amount of data | Check the number of entities for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.00014734268188476562s
Verifiability | Contribs. check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.1783590316772461s
Interlinking | sameAs chians check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.1827554702758789s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4819803237915039s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.3975098133087158s
Timeliness | dataset update frequency check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 5.4602508544921875s
Currency | Creation date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.43336915969848633s
Currency | Modification date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.23347854614257812s
Rep.Conc. | URIs length for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 156.7324869632721s
Interoperability | New vocabularies check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.17755746841430664s
Accuracy | Check Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.3250129222869873s
Accuracy | Check Inverse Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.36420106887817383s
Accuracy | Check Empty annotation labels for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 33.34055423736572s
Accuracy | Check White space in annotation for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.640369176864624s
Accuracy | Check Datatype consistency for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.553745746612549s
Consistency | Disjoint class check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.17632341384887695s
Consistency | Check Misplaced properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 86.8402807712555s
Consistency | Misplaced classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.214050054550171s
Consistency | Check Ontology hijacking for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 35.46072506904602s
Consistency | Check Invalid usage of undefined classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.3460626602172852s
Consistency | Check Invalid usage of undefined properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 87.2205581665039s
Conciseness | Check Extensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.7166073322296143s
Conciseness | Check Intensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5093131065368652s
Security | Sign check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.9883408546447754s
Availability | Check URIs Dereferenciability for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.981171131134033s
Completeness | Calculation of interlinking completeness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5106704235076904s
Reputation | Calculation of the PageRank for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.02112603187561035s
Interlinking | Calculation of Degree of Connection for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.00010156631469726562s
Interoperability | Check the re-using of existing vocabs for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.2874603271484375e-05s
INFO | --- Analysis for FADN_(2019) took 2264.5570216178894s
Availability | SPARQL endpoint availability check for FAMEData took 8.869171142578125e-05s
Availability | VoID file availability check for FAMEData took 0.0007326602935791016s
Completeness | Calculation of interlinking completeness for FAMEData took 0.2705965042114258s
Reputation | Calculation of the PageRank for FAMEData took 0.020628929138183594s
Interlinking | Calculation of Degree of Connection for FAMEData took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for FAMEData took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for FAMEData took 3.266334533691406e-05s
Believability | Calculation of trust value for FAMEData took 1.239776611328125e-05s
INFO | --- Analysis for famedata took 5.759317874908447s
Availability | SPARQL endpoint availability check for FAO geopolitical ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for FAO geopolitical ontology took 0.0006849765777587891s
Completeness | Calculation of interlinking completeness for FAO geopolitical ontology took 0.26433300971984863s
Reputation | Calculation of the PageRank for FAO geopolitical ontology took 0.020302534103393555s
Interlinking | Calculation of Degree of Connection for FAO geopolitical ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for FAO geopolitical ontology took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for FAO geopolitical ontology took 0.00010323524475097656s
Believability | Calculation of trust value for FAO geopolitical ontology took 9.298324584960938e-06s
INFO | --- Analysis for fao-geopolitical-ontology took 10.036953926086426s
Availability | SPARQL endpoint availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.09060001373291016s
Availability | VoID file availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.00036716461181640625s
Completeness | Calculation of interlinking completeness for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.26578283309936523s
Reputation | Calculation of the PageRank for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.02226996421813965s
Interlinking | Calculation of Degree of Connection for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 9.799003601074219e-05s
Believability | Calculation of trust value for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 9.298324584960938e-06s
INFO | --- Analysis for fao-linked-data took 2.6069607734680176s
Availability | SPARQL endpoint availability check for FAO ASFIS classification of biological entities @PSNC took 9.775161743164062e-05s
Availability | VoID file availability check for FAO ASFIS classification of biological entities @PSNC took 0.000331878662109375s
Completeness | Calculation of interlinking completeness for FAO ASFIS classification of biological entities @PSNC took 0.26129698753356934s
Reputation | Calculation of the PageRank for FAO ASFIS classification of biological entities @PSNC took 0.020741939544677734s
Interlinking | Calculation of Degree of Connection for FAO ASFIS classification of biological entities @PSNC took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for FAO ASFIS classification of biological entities @PSNC took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for FAO ASFIS classification of biological entities @PSNC took 3.0040740966796875e-05s
Believability | Calculation of trust value for FAO ASFIS classification of biological entities @PSNC took 1.1444091796875e-05s
INFO | --- Analysis for FAO_species took 2.4201300144195557s
Availability | SPARQL endpoint availability check for ChEMBL-RDF (@ Uppsala University) took 20.4809091091156s
Availability | VoID file availability check for ChEMBL-RDF (@ Uppsala University) took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for ChEMBL-RDF (@ Uppsala University) took 0.2728588581085205s
Reputation | Calculation of the PageRank for ChEMBL-RDF (@ Uppsala University) took 0.020648479461669922s
Interlinking | Calculation of Degree of Connection for ChEMBL-RDF (@ Uppsala University) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for ChEMBL-RDF (@ Uppsala University) took 0.0009038448333740234s
Interlinking | Calculation of Clustering coefficient for ChEMBL-RDF (@ Uppsala University) took 6.127357482910156e-05s
Believability | Calculation of trust value for ChEMBL-RDF (@ Uppsala University) took 1.1444091796875e-05s
INFO | --- Analysis for farmbio-chembl took 67.13334369659424s
Availability | SPARQL endpoint availability check for I4.0-Onto took 4.8160552978515625e-05s
Availability | VoID file availability check for I4.0-Onto took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for I4.0-Onto took 0.2738194465637207s
Reputation | Calculation of the PageRank for I4.0-Onto took 0.02030634880065918s
Interlinking | Calculation of Degree of Connection for I4.0-Onto took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for I4.0-Onto took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for I4.0-Onto took 2.8133392333984375e-05s
Believability | Calculation of trust value for I4.0-Onto took 1.1920928955078125e-05s
INFO | --- Analysis for fatimazahra took 2.4835305213928223s
Availability | SPARQL endpoint availability check for FHIR STU3 took 4.482269287109375e-05s
Availability | VoID file availability check for FHIR STU3 took 0.0006091594696044922s
Completeness | Calculation of interlinking completeness for FHIR STU3 took 0.2598423957824707s
Reputation | Calculation of the PageRank for FHIR STU3 took 0.020279407501220703s
Interlinking | Calculation of Degree of Connection for FHIR STU3 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FHIR STU3 took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for FHIR STU3 took 2.8848648071289062e-05s
Believability | Calculation of trust value for FHIR STU3 took 6.4373016357421875e-06s
INFO | --- Analysis for FHIR_STU3 took 2.747438907623291s
Availability | SPARQL endpoint availability check for FiESTA took 8.559226989746094e-05s
Availability | VoID file availability check for FiESTA took 0.0008015632629394531s
Completeness | Calculation of interlinking completeness for FiESTA took 0.3068411350250244s
Reputation | Calculation of the PageRank for FiESTA took 0.02192378044128418s
Interlinking | Calculation of Degree of Connection for FiESTA took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for FiESTA took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for FiESTA took 4.2438507080078125e-05s
Believability | Calculation of trust value for FiESTA took 1.0251998901367188e-05s
INFO | --- Analysis for fiesta took 12.70527458190918s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 8.630752563476562e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.26668667793273926s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.020688533782958984s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 3.0517578125e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.0251998901367188e-05s
INFO | --- Analysis for file:C:UsersaDesktopurn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976.owl took 2.4432373046875s
Availability | SPARQL endpoint availability check for Finnish municipalities and regional classifications took 5.078315734863281e-05s
Availability | VoID file availability check for Finnish municipalities and regional classifications took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for Finnish municipalities and regional classifications took 0.27257251739501953s
Reputation | Calculation of the PageRank for Finnish municipalities and regional classifications took 0.02092146873474121s
Interlinking | Calculation of Degree of Connection for Finnish municipalities and regional classifications took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Finnish municipalities and regional classifications took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Finnish municipalities and regional classifications took 6.818771362304688e-05s
Believability | Calculation of trust value for Finnish municipalities and regional classifications took 8.106231689453125e-06s
INFO | --- Analysis for finnish-municipalities took 3.6855669021606445s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset @PSNC took 0.18082618713378906s
Availability | VoID file availability check for Norway fishery stocks dataset @PSNC took 0.0005147457122802734s
Extra | Recovery of all triples for Norway fishery stocks dataset @PSNC took 113.30364060401917s
Performance | Total latancy measurement for Norway fishery stocks dataset @PSNC took 0.8985981941223145s
Amount of data | Number of triples check for Norway fishery stocks dataset @PSNC took 8.871663808822632s
Interoperability | New terms check for Norway fishery stocks dataset @PSNC took 13.955368280410767s
Versatility | Languages check for Norway fishery stocks dataset @PSNC took 300.25171184539795s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset @PSNC took 2.189027786254883s
Interpretability | RDF structures check for Norway fishery stocks dataset @PSNC took 0.18001580238342285s
Versatility | Serialization formats check for Norway fishery stocks dataset @PSNC took 9.627413034439087s
Availability | RDF dump link check for Norway fishery stocks dataset @PSNC took 0.2954554557800293s
License | MR license check for Norway fishery stocks dataset @PSNC took 0.18223047256469727s
License | HR license check for Norway fishery stocks dataset @PSNC took 300.2213704586029s
Amount of data | Number of property check for Norway fishery stocks dataset @PSNC took 0.18089795112609863s
Understandability | Number of label check for Norway fishery stocks dataset @PSNC took 2.0208370685577393s
Understandability | URI regex check for Norway fishery stocks dataset @PSNC took 0.8698527812957764s
Understandability | Vocabs check for Norway fishery stocks dataset @PSNC took 0.177687406539917s
Verifiability | Authors check for Norway fishery stocks dataset @PSNC took 0.17923426628112793s
Verifiability | Publishers check for Norway fishery stocks dataset @PSNC took 0.23848772048950195s
Performance | Throughput check for Norway fishery stocks dataset @PSNC took 10.761099576950073s
Amount of data | Check the number of entities for Norway fishery stocks dataset @PSNC took 3.266334533691406e-05s
Verifiability | Contribs. check for Norway fishery stocks dataset @PSNC took 0.1815948486328125s
Interlinking | sameAs chians check for Norway fishery stocks dataset @PSNC took 0.1827406883239746s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.4296696186065674s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.40562891960144043s
Timeliness | dataset update frequency check for Norway fishery stocks dataset @PSNC took 7.6699230670928955s
Currency | Creation date check for Norway fishery stocks dataset @PSNC took 0.4219799041748047s
Currency | Modification date check for Norway fishery stocks dataset @PSNC took 0.2262721061706543s
Rep.Conc. | URIs length for Norway fishery stocks dataset @PSNC took 172.7098159790039s
Interoperability | New vocabularies check for Norway fishery stocks dataset @PSNC took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset @PSNC took 0.17958927154541016s
Accuracy | Check Functional Property for Norway fishery stocks dataset @PSNC took 0.353330135345459s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset @PSNC took 0.35230207443237305s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset @PSNC took 46.43546223640442s
Accuracy | Check White space in annotation for Norway fishery stocks dataset @PSNC took 2.630908250808716s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset @PSNC took 2.618429660797119s
Consistency | Disjoint class check for Norway fishery stocks dataset @PSNC took 0.17861080169677734s
Consistency | Check Misplaced properties for Norway fishery stocks dataset @PSNC took 88.74250793457031s
Consistency | Misplaced classes for Norway fishery stocks dataset @PSNC took 8.251326084136963s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset @PSNC took 55.06634163856506s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset @PSNC took 1.3200318813323975s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset @PSNC took 86.97202706336975s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset @PSNC took 2.6923069953918457s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset @PSNC took 0.5846462249755859s
Security | Sign check for Norway fishery stocks dataset @PSNC took 0.8746013641357422s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset @PSNC took 10.161954164505005s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset @PSNC took 0.6151885986328125s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset @PSNC took 0.02109503746032715s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset @PSNC took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset @PSNC took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset @PSNC took 3.886222839355469e-05s
Interoperability | Check the re-using of existing vocabs for Norway fishery stocks dataset @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Norway fishery stocks dataset @PSNC took 1.1682510375976562e-05s
INFO | --- Analysis for Fishery_Stock_Dataset took 2276.9381082057953s
Availability | SPARQL endpoint availability check for Fishes of Texas took 9.107589721679688e-05s
Availability | VoID file availability check for Fishes of Texas took 0.0005321502685546875s
Completeness | Calculation of interlinking completeness for Fishes of Texas took 0.2666325569152832s
Reputation | Calculation of the PageRank for Fishes of Texas took 0.02091360092163086s
Interlinking | Calculation of Degree of Connection for Fishes of Texas took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Fishes of Texas took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Fishes of Texas took 8.893013000488281e-05s
Believability | Calculation of trust value for Fishes of Texas took 1.2874603271484375e-05s
INFO | --- Analysis for fishes-of-texas took 2.918630361557007s
Availability | SPARQL endpoint availability check for flickr? wrappr took 0.00010323524475097656s
Availability | VoID file availability check for flickr? wrappr took 0.0005402565002441406s
Completeness | Calculation of interlinking completeness for flickr? wrappr took 0.28116321563720703s
Reputation | Calculation of the PageRank for flickr? wrappr took 0.020943164825439453s
Interlinking | Calculation of Degree of Connection for flickr? wrappr took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for flickr? wrappr took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for flickr? wrappr took 9.34600830078125e-05s
Believability | Calculation of trust value for flickr? wrappr took 1.0728836059570312e-05s
INFO | --- Analysis for flickr-wrappr took 3.4343504905700684s
Availability | SPARQL endpoint availability check for Future land use simulation model took 8.416175842285156e-05s
Availability | VoID file availability check for Future land use simulation model took 0.0006890296936035156s
Completeness | Calculation of interlinking completeness for Future land use simulation model took 0.27457380294799805s
Reputation | Calculation of the PageRank for Future land use simulation model took 0.02075481414794922s
Interlinking | Calculation of Degree of Connection for Future land use simulation model took 2.4080276489257812e-05s
Interlinking | Calculation of Centrality for Future land use simulation model took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Future land use simulation model took 3.838539123535156e-05s
Believability | Calculation of trust value for Future land use simulation model took 1.049041748046875e-05s
INFO | --- Analysis for FLUS took 126.89356231689453s
Availability | SPARQL endpoint availability check for Flybase took 1.3660709857940674s
Availability | VoID file availability check for Flybase took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for Flybase took 0.27578091621398926s
Reputation | Calculation of the PageRank for Flybase took 0.02058863639831543s
Interlinking | Calculation of Degree of Connection for Flybase took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Flybase took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Flybase took 3.504753112792969e-05s
Believability | Calculation of trust value for Flybase took 1.049041748046875e-05s
INFO | --- Analysis for flybase took 5.294320106506348s
Availability | SPARQL endpoint availability check for Flyted took 0.8635733127593994s
Availability | VoID file availability check for Flyted took 0.0005283355712890625s
Completeness | Calculation of interlinking completeness for Flyted took 0.2737894058227539s
Reputation | Calculation of the PageRank for Flyted took 0.022233963012695312s
Interlinking | Calculation of Degree of Connection for Flyted took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Flyted took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Flyted took 3.075599670410156e-05s
Believability | Calculation of trust value for Flyted took 1.1682510375976562e-05s
INFO | --- Analysis for flyted took 5.051065921783447s
Availability | SPARQL endpoint availability check for Foodista took 2.4084103107452393s
Availability | VoID file availability check for Foodista took 0.0007557868957519531s
Completeness | Calculation of interlinking completeness for Foodista took 0.26688456535339355s
Reputation | Calculation of the PageRank for Foodista took 0.02055525779724121s
Interlinking | Calculation of Degree of Connection for Foodista took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Foodista took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Foodista took 3.0517578125e-05s
Believability | Calculation of trust value for Foodista took 1.239776611328125e-05s
INFO | --- Analysis for foodista took 32.70388388633728s
Availability | SPARQL endpoint availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.16666007041931152s
Availability | VoID file availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.272493839263916s
Reputation | Calculation of the PageRank for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.021562814712524414s
Interlinking | Calculation of Degree of Connection for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 6.914138793945312e-05s
Believability | Calculation of trust value for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.3113021850585938e-05s
INFO | --- Analysis for foodpedia took 2.667548179626465s
Availability | SPARQL endpoint availability check for FrameBase schema took 9.489059448242188e-05s
Availability | VoID file availability check for FrameBase schema took 0.0005903244018554688s
Completeness | Calculation of interlinking completeness for FrameBase schema took 0.2625725269317627s
Reputation | Calculation of the PageRank for FrameBase schema took 0.020701169967651367s
Interlinking | Calculation of Degree of Connection for FrameBase schema took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for FrameBase schema took 0.000988006591796875s
Interlinking | Calculation of Clustering coefficient for FrameBase schema took 5.4836273193359375e-05s
Believability | Calculation of trust value for FrameBase schema took 1.1444091796875e-05s
INFO | --- Analysis for framebase-schema took 3.034724235534668s
Availability | SPARQL endpoint availability check for Framester took 8.58306884765625e-05s
Availability | VoID file availability check for Framester took 0.000324249267578125s
Completeness | Calculation of interlinking completeness for Framester took 0.26754236221313477s
Reputation | Calculation of the PageRank for Framester took 0.020447731018066406s
Interlinking | Calculation of Degree of Connection for Framester took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Framester took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Framester took 7.271766662597656e-05s
Believability | Calculation of trust value for Framester took 1.33514404296875e-05s
INFO | --- Analysis for framester took 3.7658255100250244s
Availability | SPARQL endpoint availability check for Federal Reserve Board (FRB) Linked Data took 0.05658674240112305s
Availability | VoID file availability check for Federal Reserve Board (FRB) Linked Data took 0.0005431175231933594s
Completeness | Calculation of interlinking completeness for Federal Reserve Board (FRB) Linked Data took 0.28926825523376465s
Reputation | Calculation of the PageRank for Federal Reserve Board (FRB) Linked Data took 0.020828962326049805s
Interlinking | Calculation of Degree of Connection for Federal Reserve Board (FRB) Linked Data took 1.2636184692382812e-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 8.440017700195312e-05s
Believability | Calculation of trust value for Federal Reserve Board (FRB) Linked Data took 1.239776611328125e-05s
INFO | --- Analysis for frb-linked-data took 2.648343086242676s
Availability | SPARQL endpoint availability check for 1989shack Inc. E-Commerce  took 9.465217590332031e-05s
Availability | VoID file availability check for 1989shack Inc. E-Commerce  took 0.0005621910095214844s
Completeness | Calculation of interlinking completeness for 1989shack Inc. E-Commerce  took 0.2655506134033203s
Reputation | Calculation of the PageRank for 1989shack Inc. E-Commerce  took 0.0215761661529541s
Interlinking | Calculation of Degree of Connection for 1989shack Inc. E-Commerce  took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for 1989shack Inc. E-Commerce  took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for 1989shack Inc. E-Commerce  took 0.0002734661102294922s
Believability | Calculation of trust value for 1989shack Inc. E-Commerce  took 1.3113021850585938e-05s
INFO | --- Analysis for freebase took 3.8707189559936523s
Availability | SPARQL endpoint availability check for Freeyork took 8.416175842285156e-05s
Availability | VoID file availability check for Freeyork took 0.0005211830139160156s
Completeness | Calculation of interlinking completeness for Freeyork took 0.28588032722473145s
Reputation | Calculation of the PageRank for Freeyork took 0.020598411560058594s
Interlinking | Calculation of Degree of Connection for Freeyork took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Freeyork took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Freeyork took 0.0001068115234375s
Believability | Calculation of trust value for Freeyork took 1.2159347534179688e-05s
INFO | --- Analysis for freeyork-org took 2.9876794815063477s
Availability | SPARQL endpoint availability check for Community Research and Development Information Service (CORDIS) took 0.6752395629882812s
Availability | VoID file availability check for Community Research and Development Information Service (CORDIS) took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for Community Research and Development Information Service (CORDIS) took 0.25760674476623535s
Reputation | Calculation of the PageRank for Community Research and Development Information Service (CORDIS) took 0.02052903175354004s
Interlinking | Calculation of Degree of Connection for Community Research and Development Information Service (CORDIS) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Community Research and Development Information Service (CORDIS) took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Community Research and Development Information Service (CORDIS) took 7.128715515136719e-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.198001146316528s
Availability | SPARQL endpoint availability check for DailyMed took 0.6398844718933105s
Availability | VoID file availability check for DailyMed took 0.00037550926208496094s
Completeness | Calculation of interlinking completeness for DailyMed took 0.25865912437438965s
Reputation | Calculation of the PageRank for DailyMed took 0.020412683486938477s
Interlinking | Calculation of Degree of Connection for DailyMed took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for DailyMed took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for DailyMed took 9.417533874511719e-05s
Believability | Calculation of trust value for DailyMed took 7.3909759521484375e-06s
INFO | --- Analysis for fu-berlin-dailymed took 5.25053858757019s
Availability | SPARQL endpoint availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.6405017375946045s
Availability | VoID file availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.0005676746368408203s
Completeness | Calculation of interlinking completeness for DBLP Bibliography Database in RDF (FU Berlin) took 0.25859665870666504s
Reputation | Calculation of the PageRank for DBLP Bibliography Database in RDF (FU Berlin) took 0.02210688591003418s
Interlinking | Calculation of Degree of Connection for DBLP Bibliography Database in RDF (FU Berlin) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBLP Bibliography Database in RDF (FU Berlin) took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for DBLP Bibliography Database in RDF (FU Berlin) took 8.392333984375e-05s
Believability | Calculation of trust value for DBLP Bibliography Database in RDF (FU Berlin) took 1.1920928955078125e-05s
INFO | --- Analysis for fu-berlin-dblp took 4.215349197387695s
Availability | SPARQL endpoint availability check for Diseasome took 0.6441621780395508s
Availability | VoID file availability check for Diseasome took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for Diseasome took 0.271014928817749s
Reputation | Calculation of the PageRank for Diseasome took 0.020733118057250977s
Interlinking | Calculation of Degree of Connection for Diseasome took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Diseasome took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Diseasome took 0.00011038780212402344s
Believability | Calculation of trust value for Diseasome took 1.2159347534179688e-05s
INFO | --- Analysis for fu-berlin-diseasome took 5.382178068161011s
Availability | SPARQL endpoint availability check for DrugBank took 0.6413655281066895s
Availability | VoID file availability check for DrugBank took 0.000644683837890625s
Completeness | Calculation of interlinking completeness for DrugBank took 0.2762429714202881s
Reputation | Calculation of the PageRank for DrugBank took 0.020457983016967773s
Interlinking | Calculation of Degree of Connection for DrugBank took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DrugBank took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for DrugBank took 0.00011324882507324219s
Believability | Calculation of trust value for DrugBank took 1.1920928955078125e-05s
INFO | --- Analysis for fu-berlin-drugbank took 7.014233112335205s
Availability | SPARQL endpoint availability check for European Commission Competition data set (FU Berlin) took 1.6392741203308105s
Availability | VoID file availability check for European Commission Competition data set (FU Berlin) took 0.0005674362182617188s
Completeness | Calculation of interlinking completeness for European Commission Competition data set (FU Berlin) took 0.2869563102722168s
Reputation | Calculation of the PageRank for European Commission Competition data set (FU Berlin) took 0.020662784576416016s
Interlinking | Calculation of Degree of Connection for European Commission Competition data set (FU Berlin) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for European Commission Competition data set (FU Berlin) took 0.0007038116455078125s
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 1.1920928955078125e-05s
INFO | --- Analysis for fu-berlin-ec-competition took 5.340665102005005s
Availability | SPARQL endpoint availability check for EURAXESS - Researchers in Motion took 0.6310596466064453s
Availability | VoID file availability check for EURAXESS - Researchers in Motion took 0.0004439353942871094s
Completeness | Calculation of interlinking completeness for EURAXESS - Researchers in Motion took 0.26204657554626465s
Reputation | Calculation of the PageRank for EURAXESS - Researchers in Motion took 0.0223846435546875s
Interlinking | Calculation of Degree of Connection for EURAXESS - Researchers in Motion took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EURAXESS - Researchers in Motion took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for EURAXESS - Researchers in Motion took 8.678436279296875e-05s
Believability | Calculation of trust value for EURAXESS - Researchers in Motion took 8.344650268554688e-06s
INFO | --- Analysis for fu-berlin-euraxess took 4.219354629516602s
Availability | SPARQL endpoint availability check for European Employment Services (EURES) took 0.6389343738555908s
Availability | VoID file availability check for European Employment Services (EURES) took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for European Employment Services (EURES) took 0.2710916996002197s
Reputation | Calculation of the PageRank for European Employment Services (EURES) took 0.02174687385559082s
Interlinking | Calculation of Degree of Connection for European Employment Services (EURES) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for European Employment Services (EURES) took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for European Employment Services (EURES) took 7.367134094238281e-05s
Believability | Calculation of trust value for European Employment Services (EURES) took 9.059906005859375e-06s
INFO | --- Analysis for fu-berlin-eures took 4.254679203033447s
Availability | SPARQL endpoint availability check for Eurostat in RDF (FU Berlin) took 0.6413552761077881s
Availability | VoID file availability check for Eurostat in RDF (FU Berlin) took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for Eurostat in RDF (FU Berlin) took 0.2660844326019287s
Reputation | Calculation of the PageRank for Eurostat in RDF (FU Berlin) took 0.021271467208862305s
Interlinking | Calculation of Degree of Connection for Eurostat in RDF (FU Berlin) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Eurostat in RDF (FU Berlin) took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Eurostat in RDF (FU Berlin) took 9.5367431640625e-05s
Believability | Calculation of trust value for Eurostat in RDF (FU Berlin) took 9.298324584960938e-06s
INFO | --- Analysis for fu-berlin-eurostat took 4.804342031478882s
Availability | SPARQL endpoint availability check for MediCare took 0.6461989879608154s
Availability | VoID file availability check for MediCare took 0.0005283355712890625s
Completeness | Calculation of interlinking completeness for MediCare took 0.27525830268859863s
Reputation | Calculation of the PageRank for MediCare took 0.020933866500854492s
Interlinking | Calculation of Degree of Connection for MediCare took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for MediCare took 0.0008313655853271484s
Interlinking | Calculation of Clustering coefficient for MediCare took 4.76837158203125e-05s
Believability | Calculation of trust value for MediCare took 1.2159347534179688e-05s
INFO | --- Analysis for fu-berlin-medicare took 4.815654516220093s
Availability | SPARQL endpoint availability check for Project Gutenberg in RDF (FU Berlin) took 0.6337192058563232s
Availability | VoID file availability check for Project Gutenberg in RDF (FU Berlin) took 0.0004584789276123047s
Completeness | Calculation of interlinking completeness for Project Gutenberg in RDF (FU Berlin) took 0.27326035499572754s
Reputation | Calculation of the PageRank for Project Gutenberg in RDF (FU Berlin) took 0.02063131332397461s
Interlinking | Calculation of Degree of Connection for Project Gutenberg in RDF (FU Berlin) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Project Gutenberg in RDF (FU Berlin) took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg in RDF (FU Berlin) took 7.724761962890625e-05s
Believability | Calculation of trust value for Project Gutenberg in RDF (FU Berlin) took 1.33514404296875e-05s
INFO | --- Analysis for fu-berlin-project-gutenberg took 4.2804319858551025s
Availability | SPARQL endpoint availability check for SIDER: Side Effect Resource took 0.6360292434692383s
Availability | VoID file availability check for SIDER: Side Effect Resource took 0.000518798828125s
Completeness | Calculation of interlinking completeness for SIDER: Side Effect Resource took 0.263411283493042s
Reputation | Calculation of the PageRank for SIDER: Side Effect Resource took 0.020721912384033203s
Interlinking | Calculation of Degree of Connection for SIDER: Side Effect Resource took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for SIDER: Side Effect Resource took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for SIDER: Side Effect Resource took 9.131431579589844e-05s
Believability | Calculation of trust value for SIDER: Side Effect Resource took 1.239776611328125e-05s
INFO | --- Analysis for fu-berlin-sider took 4.7588725090026855s
Availability | SPARQL endpoint availability check for STITCH: Chemical-Protein Interactions took 0.6433603763580322s
Availability | VoID file availability check for STITCH: Chemical-Protein Interactions took 0.0006177425384521484s
Completeness | Calculation of interlinking completeness for STITCH: Chemical-Protein Interactions took 0.28196072578430176s
Reputation | Calculation of the PageRank for STITCH: Chemical-Protein Interactions took 0.02161097526550293s
Interlinking | Calculation of Degree of Connection for STITCH: Chemical-Protein Interactions took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for STITCH: Chemical-Protein Interactions took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for STITCH: Chemical-Protein Interactions took 7.724761962890625e-05s
Believability | Calculation of trust value for STITCH: Chemical-Protein Interactions took 1.33514404296875e-05s
INFO | --- Analysis for fu-berlin-stitch took 4.285708665847778s
Availability | SPARQL endpoint availability check for fvdb took 4.482269287109375e-05s
Availability | VoID file availability check for fvdb took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for fvdb took 0.26359033584594727s
Reputation | Calculation of the PageRank for fvdb took 0.020663738250732422s
Interlinking | Calculation of Degree of Connection for fvdb took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for fvdb took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for fvdb took 3.0517578125e-05s
Believability | Calculation of trust value for fvdb took 1.2159347534179688e-05s
INFO | --- Analysis for fv took 12.454074144363403s
Availability | SPARQL endpoint availability check for Global Agricultural Concept Space took 9.870529174804688e-05s
Availability | VoID file availability check for Global Agricultural Concept Space took 0.0007061958312988281s
Completeness | Calculation of interlinking completeness for Global Agricultural Concept Space took 0.26272106170654297s
Reputation | Calculation of the PageRank for Global Agricultural Concept Space took 0.020493268966674805s
Interlinking | Calculation of Degree of Connection for Global Agricultural Concept Space took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Global Agricultural Concept Space took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Global Agricultural Concept Space took 2.9802322387695312e-05s
Believability | Calculation of trust value for Global Agricultural Concept Space took 1.1205673217773438e-05s
INFO | --- Analysis for GACS took 2.981445550918579s
Availability | SPARQL endpoint availability check for Galician EuroWordNet-lemon lexicon (3.0) took 8.96453857421875e-05s
Availability | VoID file availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.0006287097930908203s
Completeness | Calculation of interlinking completeness for Galician EuroWordNet-lemon lexicon (3.0) took 0.2889845371246338s
Reputation | Calculation of the PageRank for Galician EuroWordNet-lemon lexicon (3.0) took 0.022565364837646484s
Interlinking | Calculation of Degree of Connection for Galician EuroWordNet-lemon lexicon (3.0) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Galician EuroWordNet-lemon lexicon (3.0) took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Galician EuroWordNet-lemon lexicon (3.0) took 4.029273986816406e-05s
Believability | Calculation of trust value for Galician EuroWordNet-lemon lexicon (3.0) took 6.4373016357421875e-06s
INFO | --- Analysis for galician-eurowordnet-lemon-lexicon-3-0 took 5.138475179672241s
Availability | SPARQL endpoint availability check for Garnica Plywood Catalogue took 8.511543273925781e-05s
Availability | VoID file availability check for Garnica Plywood Catalogue took 0.0007355213165283203s
Completeness | Calculation of interlinking completeness for Garnica Plywood Catalogue took 0.2727501392364502s
Reputation | Calculation of the PageRank for Garnica Plywood Catalogue took 0.021809816360473633s
Interlinking | Calculation of Degree of Connection for Garnica Plywood Catalogue took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Garnica Plywood Catalogue took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Garnica Plywood Catalogue took 0.00010347366333007812s
Believability | Calculation of trust value for Garnica Plywood Catalogue took 1.0013580322265625e-05s
INFO | --- Analysis for garnicaplywood took 5.408294677734375s
Availability | SPARQL endpoint availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 9.059906005859375e-05s
Availability | VoID file availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0005865097045898438s
Completeness | Calculation of interlinking completeness for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.26682257652282715s
Reputation | Calculation of the PageRank for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.021086692810058594s
Interlinking | Calculation of Degree of Connection for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 9.679794311523438e-05s
Believability | Calculation of trust value for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.0251998901367188e-05s
INFO | --- Analysis for gemeenschappelijke-thesaurus-audiovisuele-archieven took 7.252227544784546s
Availability | SPARQL endpoint availability check for GEneral Multilingual Environmental Thesaurus took 0.2839651107788086s
Availability | VoID file availability check for GEneral Multilingual Environmental Thesaurus took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for GEneral Multilingual Environmental Thesaurus took 0.2968614101409912s
Reputation | Calculation of the PageRank for GEneral Multilingual Environmental Thesaurus took 0.02084207534790039s
Interlinking | Calculation of Degree of Connection for GEneral Multilingual Environmental Thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for GEneral Multilingual Environmental Thesaurus took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for GEneral Multilingual Environmental Thesaurus took 8.988380432128906e-05s
Believability | Calculation of trust value for GEneral Multilingual Environmental Thesaurus took 1.0967254638671875e-05s
INFO | --- Analysis for gemet took 4.737218141555786s
Availability | SPARQL endpoint availability check for gemet-annotated took 4.291534423828125e-05s
Availability | VoID file availability check for gemet-annotated took 0.0005710124969482422s
Completeness | Calculation of interlinking completeness for gemet-annotated took 0.26852846145629883s
Reputation | Calculation of the PageRank for gemet-annotated took 0.021019697189331055s
Interlinking | Calculation of Degree of Connection for gemet-annotated took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for gemet-annotated took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for gemet-annotated took 3.743171691894531e-05s
Believability | Calculation of trust value for gemet-annotated took 1.1920928955078125e-05s
INFO | --- Analysis for gemet-annotated took 2.965233564376831s
Availability | SPARQL endpoint availability check for Gene Expression Atlas RDF took 0.7286825180053711s
Availability | VoID file availability check for Gene Expression Atlas RDF took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for Gene Expression Atlas RDF took 0.27146291732788086s
Reputation | Calculation of the PageRank for Gene Expression Atlas RDF took 0.021197080612182617s
Interlinking | Calculation of Degree of Connection for Gene Expression Atlas RDF took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Gene Expression Atlas RDF took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Gene Expression Atlas RDF took 3.933906555175781e-05s
Believability | Calculation of trust value for Gene Expression Atlas RDF took 1.1920928955078125e-05s
INFO | --- Analysis for gene-expression-atlas-rdf took 4.2796056270599365s
Availability | SPARQL endpoint availability check for Super Ontology took 1.384953260421753s
Availability | VoID file availability check for Super Ontology took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.2686002254486084s
Reputation | Calculation of the PageRank for Super Ontology took 0.02068471908569336s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 3.218650817871094e-05s
Believability | Calculation of trust value for Super Ontology took 1.049041748046875e-05s
INFO | --- Analysis for Generalized_Super_Ontology took 4.710716247558594s
Availability | SPARQL endpoint availability check for Geographic detector model took 8.869171142578125e-05s
Availability | VoID file availability check for Geographic detector model took 0.0005745887756347656s
Completeness | Calculation of interlinking completeness for Geographic detector model took 0.28840112686157227s
Reputation | Calculation of the PageRank for Geographic detector model took 0.022513628005981445s
Interlinking | Calculation of Degree of Connection for Geographic detector model took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Geographic detector model took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Geographic detector model took 3.170967102050781e-05s
Believability | Calculation of trust value for Geographic detector model took 1.1205673217773438e-05s
INFO | --- Analysis for GeoDetector took 18.26871657371521s
Availability | SPARQL endpoint availability check for geodomainwn took 8.654594421386719e-05s
Availability | VoID file availability check for geodomainwn took 0.0006134510040283203s
Completeness | Calculation of interlinking completeness for geodomainwn took 0.2676858901977539s
Reputation | Calculation of the PageRank for geodomainwn took 0.02068042755126953s
Interlinking | Calculation of Degree of Connection for geodomainwn took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for geodomainwn took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for geodomainwn took 4.792213439941406e-05s
Believability | Calculation of trust value for geodomainwn took 1.2159347534179688e-05s
INFO | --- Analysis for geodomainwn took 6.698907375335693s
Availability | SPARQL endpoint availability check for GeoEcuador took 8.654594421386719e-05s
Availability | VoID file availability check for GeoEcuador took 0.0007417201995849609s
Completeness | Calculation of interlinking completeness for GeoEcuador took 0.2706263065338135s
Reputation | Calculation of the PageRank for GeoEcuador took 0.020883798599243164s
Interlinking | Calculation of Degree of Connection for GeoEcuador took 2.5987625122070312e-05s
Interlinking | Calculation of Centrality for GeoEcuador took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for GeoEcuador took 7.128715515136719e-05s
Believability | Calculation of trust value for GeoEcuador took 1.0728836059570312e-05s
INFO | --- Analysis for geoecuador took 12.498587846755981s
Availability | SPARQL endpoint availability check for Geographic Names Information System (GNIS) took 3.1324567794799805s
Availability | VoID file availability check for Geographic Names Information System (GNIS) took 0.0007481575012207031s
Completeness | Calculation of interlinking completeness for Geographic Names Information System (GNIS) took 0.26885294914245605s
Reputation | Calculation of the PageRank for Geographic Names Information System (GNIS) took 0.0205535888671875s
Interlinking | Calculation of Degree of Connection for Geographic Names Information System (GNIS) took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Geographic Names Information System (GNIS) took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Geographic Names Information System (GNIS) took 6.628036499023438e-05s
Believability | Calculation of trust value for Geographic Names Information System (GNIS) took 1.0728836059570312e-05s
INFO | --- Analysis for geographic-names-information-system-gnis took 49.39151358604431s
Availability | SPARQL endpoint availability check for GeoLinkedData took 4.965548515319824s
Availability | VoID file availability check for GeoLinkedData took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for GeoLinkedData took 0.26353931427001953s
Reputation | Calculation of the PageRank for GeoLinkedData took 0.0205690860748291s
Interlinking | Calculation of Degree of Connection for GeoLinkedData took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for GeoLinkedData took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for GeoLinkedData took 8.344650268554688e-05s
Believability | Calculation of trust value for GeoLinkedData took 8.344650268554688e-06s
INFO | --- Analysis for geolinkeddata took 17.273956537246704s
Availability | SPARQL endpoint availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.18500256538391113s
Availability | VoID file availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.0005085468292236328s
Extra | Recovery of all triples for Geological Survey of Austria (GBA) - Thesaurus took 8.878365993499756s
Performance | Total latancy measurement for Geological Survey of Austria (GBA) - Thesaurus took 0.3362855911254883s
Amount of data | Number of triples check for Geological Survey of Austria (GBA) - Thesaurus took 0.12907886505126953s
Interoperability | New terms check for Geological Survey of Austria (GBA) - Thesaurus took 1.4402117729187012s
Versatility | Languages check for Geological Survey of Austria (GBA) - Thesaurus took 0.22941875457763672s
Interpretability | Number of blank nodes check for Geological Survey of Austria (GBA) - Thesaurus took 0.15273332595825195s
Security | Check HTTPS for Geological Survey of Austria (GBA) - Thesaurus took 0.18054842948913574s
Interpretability | RDF structures check for Geological Survey of Austria (GBA) - Thesaurus took 0.08617091178894043s
Versatility | Serialization formats check for Geological Survey of Austria (GBA) - Thesaurus took 0.08750772476196289s
Availability | RDF dump link check for Geological Survey of Austria (GBA) - Thesaurus took 0.06703305244445801s
License | MR license check for Geological Survey of Austria (GBA) - Thesaurus took 0.08486747741699219s
License | HR license check for Geological Survey of Austria (GBA) - Thesaurus took 1.8613817691802979s
Amount of data | Number of property check for Geological Survey of Austria (GBA) - Thesaurus took 0.08590292930603027s
Understandability | Number of label check for Geological Survey of Austria (GBA) - Thesaurus took 0.09055185317993164s
Understandability | URI regex check for Geological Survey of Austria (GBA) - Thesaurus took 0.13531804084777832s
Understandability | Vocabs check for Geological Survey of Austria (GBA) - Thesaurus took 0.08516716957092285s
Verifiability | Authors check for Geological Survey of Austria (GBA) - Thesaurus took 0.06354522705078125s
Verifiability | Publishers check for Geological Survey of Austria (GBA) - Thesaurus took 0.08795046806335449s
Performance | Throughput check for Geological Survey of Austria (GBA) - Thesaurus took 10.213173389434814s
Amount of data | Check the number of entities for Geological Survey of Austria (GBA) - Thesaurus took 3.24249267578125e-05s
Verifiability | Contribs. check for Geological Survey of Austria (GBA) - Thesaurus took 0.06047987937927246s
Interlinking | sameAs chians check for Geological Survey of Austria (GBA) - Thesaurus took 0.05954861640930176s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.08389520645141602s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.06064796447753906s
Timeliness | dataset update frequency check for Geological Survey of Austria (GBA) - Thesaurus took 0.05991029739379883s
Currency | Creation date check for Geological Survey of Austria (GBA) - Thesaurus took 0.14199352264404297s
Currency | Modification date check for Geological Survey of Austria (GBA) - Thesaurus took 0.14488840103149414s
Rep.Conc. | URIs length for Geological Survey of Austria (GBA) - Thesaurus took 1.2573864459991455s
Interoperability | New vocabularies check for Geological Survey of Austria (GBA) - Thesaurus took 1.074350118637085s
Consistency | Deprecated classes/propertiers check for Geological Survey of Austria (GBA) - Thesaurus took 0.08542346954345703s
Accuracy | Check Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.06088852882385254s
Accuracy | Check Inverse Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.06055879592895508s
Accuracy | Check Empty annotation labels for Geological Survey of Austria (GBA) - Thesaurus took 0.2873110771179199s
Accuracy | Check White space in annotation for Geological Survey of Austria (GBA) - Thesaurus took 0.007149457931518555s
Accuracy | Check Datatype consistency for Geological Survey of Austria (GBA) - Thesaurus took 0.22739744186401367s
Consistency | Disjoint class check for Geological Survey of Austria (GBA) - Thesaurus took 0.06057167053222656s
Consistency | Check Misplaced properties for Geological Survey of Austria (GBA) - Thesaurus took 0.2147514820098877s
Consistency | Misplaced classes for Geological Survey of Austria (GBA) - Thesaurus took 0.5121850967407227s
Consistency | Check Ontology hijacking for Geological Survey of Austria (GBA) - Thesaurus took 3.2339541912078857s
Consistency | Check Invalid usage of undefined classes for Geological Survey of Austria (GBA) - Thesaurus took 1.5366547107696533s
Consistency | Check Invalid usage of undefined properties for Geological Survey of Austria (GBA) - Thesaurus took 1.6812281608581543s
Conciseness | Check Extensional conciseness for Geological Survey of Austria (GBA) - Thesaurus took 0.17701196670532227s
Security | Sign check for Geological Survey of Austria (GBA) - Thesaurus took 0.06012129783630371s
Availability | Check URIs Dereferenciability for Geological Survey of Austria (GBA) - Thesaurus took 0.9462807178497314s
Completeness | Calculation of interlinking completeness for Geological Survey of Austria (GBA) - Thesaurus took 0.2757837772369385s
Reputation | Calculation of the PageRank for Geological Survey of Austria (GBA) - Thesaurus took 0.020350217819213867s
Interlinking | Calculation of Degree of Connection for Geological Survey of Austria (GBA) - Thesaurus took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Geological Survey of Austria (GBA) - Thesaurus took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for Geological Survey of Austria (GBA) - Thesaurus took 8.988380432128906e-05s
Interoperability | Check the re-using of existing vocabs for Geological Survey of Austria (GBA) - Thesaurus took 433.3276879787445s
Believability | Calculation of trust value for Geological Survey of Austria (GBA) - Thesaurus took 1.52587890625e-05s
INFO | --- Analysis for geological-survey-of-austria-thesaurus took 544.5267946720123s
Availability | SPARQL endpoint availability check for GeoNames Semantic Web took 4.172325134277344e-05s
Availability | VoID file availability check for GeoNames Semantic Web took 0.00039505958557128906s
Completeness | Calculation of interlinking completeness for GeoNames Semantic Web took 0.27831029891967773s
Reputation | Calculation of the PageRank for GeoNames Semantic Web took 0.02167654037475586s
Interlinking | Calculation of Degree of Connection for GeoNames Semantic Web took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GeoNames Semantic Web took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for GeoNames Semantic Web took 0.0004611015319824219s
Believability | Calculation of trust value for GeoNames Semantic Web took 9.775161743164062e-06s
INFO | --- Analysis for geonames-semantic-web took 3.194923162460327s
Availability | SPARQL endpoint availability check for Geospatial World  took 9.799003601074219e-05s
Availability | VoID file availability check for Geospatial World  took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for Geospatial World  took 0.2825345993041992s
Reputation | Calculation of the PageRank for Geospatial World  took 0.02018141746520996s
Interlinking | Calculation of Degree of Connection for Geospatial World  took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Geospatial World  took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Geospatial World  took 0.000102996826171875s
Believability | Calculation of trust value for Geospatial World  took 9.775161743164062e-06s
INFO | --- Analysis for geospatialworld-net took 3.122957468032837s
Availability | SPARQL endpoint availability check for GeoSpecies Knowledge Base took 0.5155518054962158s
Availability | VoID file availability check for GeoSpecies Knowledge Base took 0.0005614757537841797s
Completeness | Calculation of interlinking completeness for GeoSpecies Knowledge Base took 0.273115873336792s
Reputation | Calculation of the PageRank for GeoSpecies Knowledge Base took 0.020204782485961914s
Interlinking | Calculation of Degree of Connection for GeoSpecies Knowledge Base took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GeoSpecies Knowledge Base took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Knowledge Base took 0.00013399124145507812s
Believability | Calculation of trust value for GeoSpecies Knowledge Base took 1.049041748046875e-05s
INFO | --- Analysis for geospecies took 5.976152658462524s
Availability | SPARQL endpoint availability check for GeoWordNet took 5.269050598144531e-05s
Availability | VoID file availability check for GeoWordNet took 0.0004429817199707031s
Completeness | Calculation of interlinking completeness for GeoWordNet took 0.2922539710998535s
Reputation | Calculation of the PageRank for GeoWordNet took 0.020229578018188477s
Interlinking | Calculation of Degree of Connection for GeoWordNet took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GeoWordNet took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for GeoWordNet took 4.6253204345703125e-05s
Believability | Calculation of trust value for GeoWordNet took 1.049041748046875e-05s
INFO | --- Analysis for geowordnet took 7.60206151008606s
Availability | SPARQL endpoint availability check for German labor law thesaurus took 0.08111572265625s
Availability | VoID file availability check for German labor law thesaurus took 0.00021195411682128906s
Completeness | Calculation of interlinking completeness for German labor law thesaurus took 0.2683143615722656s
Reputation | Calculation of the PageRank for German labor law thesaurus took 0.021456480026245117s
Interlinking | Calculation of Degree of Connection for German labor law thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for German labor law thesaurus took 0.0007903575897216797s
Interlinking | Calculation of Clustering coefficient for German labor law thesaurus took 8.082389831542969e-05s
Believability | Calculation of trust value for German labor law thesaurus took 9.298324584960938e-06s
INFO | --- Analysis for german-labor-law-thesaurus took 2.590712070465088s
Availability | SPARQL endpoint availability check for Linked Old Germanic Dictionaries took 8.797645568847656e-05s
Availability | VoID file availability check for Linked Old Germanic Dictionaries took 0.0005669593811035156s
Completeness | Calculation of interlinking completeness for Linked Old Germanic Dictionaries took 0.2687506675720215s
Reputation | Calculation of the PageRank for Linked Old Germanic Dictionaries took 0.023145675659179688s
Interlinking | Calculation of Degree of Connection for Linked Old Germanic Dictionaries took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Old Germanic Dictionaries took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Linked Old Germanic Dictionaries took 4.649162292480469e-05s
Believability | Calculation of trust value for Linked Old Germanic Dictionaries took 1.1920928955078125e-05s
INFO | --- Analysis for germlex took 2.878081798553467s
Availability | SPARQL endpoint availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.2824132442474365s
Availability | VoID file availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.21244311332702637s
Completeness | Calculation of interlinking completeness for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.26686859130859375s
Reputation | Calculation of the PageRank for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.020174026489257812s
Interlinking | Calculation of Degree of Connection for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for TheSoz Thesaurus for the Social Sciences (GESIS) took 8.606910705566406e-05s
Believability | Calculation of trust value for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.0728836059570312e-05s
INFO | --- Analysis for gesis-thesoz took 6.700341701507568s
Availability | SPARQL endpoint availability check for Art & Architecture Thesaurus took 2.7558226585388184s
Availability | VoID file availability check for Art & Architecture Thesaurus took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for Art & Architecture Thesaurus took 0.26475954055786133s
Reputation | Calculation of the PageRank for Art & Architecture Thesaurus took 0.02178192138671875s
Interlinking | Calculation of Degree of Connection for Art & Architecture Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Art & Architecture Thesaurus took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Art & Architecture Thesaurus took 7.319450378417969e-05s
Believability | Calculation of trust value for Art & Architecture Thesaurus took 1.1920928955078125e-05s
INFO | --- Analysis for getty-aat took 15.871403217315674s
Availability | SPARQL endpoint availability check for The Getty Thesaurus of Geographic Names took 1.307471513748169s
Availability | VoID file availability check for The Getty Thesaurus of Geographic Names took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for The Getty Thesaurus of Geographic Names took 0.2686879634857178s
Reputation | Calculation of the PageRank for The Getty Thesaurus of Geographic Names took 0.020312786102294922s
Interlinking | Calculation of Degree of Connection for The Getty Thesaurus of Geographic Names took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The Getty Thesaurus of Geographic Names took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for The Getty Thesaurus of Geographic Names took 4.9591064453125e-05s
Believability | Calculation of trust value for The Getty Thesaurus of Geographic Names took 1.0967254638671875e-05s
INFO | --- Analysis for getty-tgn took 12.476472616195679s
Availability | SPARQL endpoint availability check for Gipuzkoa Demografia took 14.352272272109985s
Availability | VoID file availability check for Gipuzkoa Demografia took 0.0006842613220214844s
Completeness | Calculation of interlinking completeness for Gipuzkoa Demografia took 0.27115964889526367s
Reputation | Calculation of the PageRank for Gipuzkoa Demografia took 0.02142500877380371s
Interlinking | Calculation of Degree of Connection for Gipuzkoa Demografia took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Gipuzkoa Demografia took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for Gipuzkoa Demografia took 3.075599670410156e-05s
Believability | Calculation of trust value for Gipuzkoa Demografia took 9.059906005859375e-06s
INFO | --- Analysis for gipuzkoademografia took 37.65234565734863s
Availability | SPARQL endpoint availability check for Glastonbury 2011 Programme took 8.225440979003906e-05s
Availability | VoID file availability check for Glastonbury 2011 Programme took 0.0005791187286376953s
Completeness | Calculation of interlinking completeness for Glastonbury 2011 Programme took 0.2762465476989746s
Reputation | Calculation of the PageRank for Glastonbury 2011 Programme took 0.02162456512451172s
Interlinking | Calculation of Degree of Connection for Glastonbury 2011 Programme took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Glastonbury 2011 Programme took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Glastonbury 2011 Programme took 3.170967102050781e-05s
Believability | Calculation of trust value for Glastonbury 2011 Programme took 9.775161743164062e-06s
INFO | --- Analysis for glastonbury-2011 took 5.230564594268799s
Availability | SPARQL endpoint availability check for Global Hunger Index (2011) took 8.320808410644531e-05s
Availability | VoID file availability check for Global Hunger Index (2011) took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for Global Hunger Index (2011) took 0.353165864944458s
Reputation | Calculation of the PageRank for Global Hunger Index (2011) took 0.020596027374267578s
Interlinking | Calculation of Degree of Connection for Global Hunger Index (2011) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Global Hunger Index (2011) took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Global Hunger Index (2011) took 7.557868957519531e-05s
Believability | Calculation of trust value for Global Hunger Index (2011) took 5.7220458984375e-06s
INFO | --- Analysis for global-hunger-index-2011 took 4.872302293777466s
Availability | SPARQL endpoint availability check for Glottolog took 8.511543273925781e-05s
Availability | VoID file availability check for Glottolog took 0.0007405281066894531s
Completeness | Calculation of interlinking completeness for Glottolog took 0.5221564769744873s
Reputation | Calculation of the PageRank for Glottolog took 0.0227358341217041s
Interlinking | Calculation of Degree of Connection for Glottolog took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Glottolog took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Glottolog took 5.078315734863281e-05s
Believability | Calculation of trust value for Glottolog took 1.2159347534179688e-05s
INFO | --- Analysis for glottolog took 16.114349842071533s
Availability | SPARQL endpoint availability check for GNOSS.com, a Social and Semantic Platform took 0.00010085105895996094s
Availability | VoID file availability check for GNOSS.com, a Social and Semantic Platform took 0.0005788803100585938s
Completeness | Calculation of interlinking completeness for GNOSS.com, a Social and Semantic Platform took 0.2684593200683594s
Reputation | Calculation of the PageRank for GNOSS.com, a Social and Semantic Platform took 0.02064347267150879s
Interlinking | Calculation of Degree of Connection for GNOSS.com, a Social and Semantic Platform took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for GNOSS.com, a Social and Semantic Platform took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for GNOSS.com, a Social and Semantic Platform took 0.00010514259338378906s
Believability | Calculation of trust value for GNOSS.com, a Social and Semantic Platform took 9.5367431640625e-06s
INFO | --- Analysis for gnoss-com-a-social-and-semantic-platform took 12.44273829460144s
Availability | SPARQL endpoint availability check for 1121 took 8.416175842285156e-05s
Availability | VoID file availability check for 1121 took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for 1121 took 0.27228522300720215s
Reputation | Calculation of the PageRank for 1121 took 0.02093505859375s
Interlinking | Calculation of Degree of Connection for 1121 took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for 1121 took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for 1121 took 3.314018249511719e-05s
Believability | Calculation of trust value for 1121 took 1.1205673217773438e-05s
INFO | --- Analysis for God_ took 2.9545576572418213s
Availability | SPARQL endpoint availability check for General Ontology of Linguistic Description took 8.654594421386719e-05s
Availability | VoID file availability check for General Ontology of Linguistic Description took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for General Ontology of Linguistic Description took 0.2669975757598877s
Reputation | Calculation of the PageRank for General Ontology of Linguistic Description took 0.020685195922851562s
Interlinking | Calculation of Degree of Connection for General Ontology of Linguistic Description took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for General Ontology of Linguistic Description took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for General Ontology of Linguistic Description took 5.435943603515625e-05s
Believability | Calculation of trust value for General Ontology of Linguistic Description took 1.1682510375976562e-05s
INFO | --- Analysis for gold took 4.503535985946655s
Availability | SPARQL endpoint availability check for GoogleArt wrapper took 9.107589721679688e-05s
Availability | VoID file availability check for GoogleArt wrapper took 0.0005500316619873047s
Completeness | Calculation of interlinking completeness for GoogleArt wrapper took 0.287320613861084s
Reputation | Calculation of the PageRank for GoogleArt wrapper took 0.0202639102935791s
Interlinking | Calculation of Degree of Connection for GoogleArt wrapper took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for GoogleArt wrapper took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for GoogleArt wrapper took 6.794929504394531e-05s
Believability | Calculation of trust value for GoogleArt wrapper took 1.0013580322265625e-05s
INFO | --- Analysis for googleart-wrapper took 3.162757635116577s
Availability | SPARQL endpoint availability check for GovAgriBus Denmark took 0.08833146095275879s
Availability | VoID file availability check for GovAgriBus Denmark took 0.0005633831024169922s
Completeness | Calculation of interlinking completeness for GovAgriBus Denmark took 0.2731194496154785s
Reputation | Calculation of the PageRank for GovAgriBus Denmark took 0.02106618881225586s
Interlinking | Calculation of Degree of Connection for GovAgriBus Denmark took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for GovAgriBus Denmark took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for GovAgriBus Denmark took 3.457069396972656e-05s
Believability | Calculation of trust value for GovAgriBus Denmark took 1.0013580322265625e-05s
INFO | --- Analysis for govagribus-denmark took 34.61911225318909s
Availability | SPARQL endpoint availability check for GovWILD - Government Web Integration for Linked Data took 3.4876015186309814s
Availability | VoID file availability check for GovWILD - Government Web Integration for Linked Data took 0.0005819797515869141s
Completeness | Calculation of interlinking completeness for GovWILD - Government Web Integration for Linked Data took 0.26609182357788086s
Reputation | Calculation of the PageRank for GovWILD - Government Web Integration for Linked Data took 0.020497560501098633s
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.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for GovWILD - Government Web Integration for Linked Data took 8.416175842285156e-05s
Believability | Calculation of trust value for GovWILD - Government Web Integration for Linked Data took 1.0967254638671875e-05s
INFO | --- Analysis for government-web-integration-for-linked-data took 24.06758975982666s
Availability | SPARQL endpoint availability check for GovTrack.us U.S Congress Legislative Data took 0.8616576194763184s
Availability | VoID file availability check for GovTrack.us U.S Congress Legislative Data took 0.0005211830139160156s
Completeness | Calculation of interlinking completeness for GovTrack.us U.S Congress Legislative Data took 0.2921922206878662s
Reputation | Calculation of the PageRank for GovTrack.us U.S Congress Legislative Data took 0.020588397979736328s
Interlinking | Calculation of Degree of Connection for GovTrack.us U.S Congress Legislative Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for GovTrack.us U.S Congress Legislative Data took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for GovTrack.us U.S Congress Legislative Data took 8.940696716308594e-05s
Believability | Calculation of trust value for GovTrack.us U.S Congress Legislative Data took 1.049041748046875e-05s
INFO | --- Analysis for govtrack took 3.5570149421691895s
Availability | SPARQL endpoint availability check for greek-administrative-geography took 4.363059997558594e-05s
Availability | VoID file availability check for greek-administrative-geography took 0.0005559921264648438s
Completeness | Calculation of interlinking completeness for greek-administrative-geography took 0.26504063606262207s
Reputation | Calculation of the PageRank for greek-administrative-geography took 0.020870208740234375s
Interlinking | Calculation of Degree of Connection for greek-administrative-geography took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for greek-administrative-geography took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for greek-administrative-geography took 6.031990051269531e-05s
Believability | Calculation of trust value for greek-administrative-geography took 1.2636184692382812e-05s
INFO | --- Analysis for greek-administrative-geography took 2.4910333156585693s
Availability | SPARQL endpoint availability check for Greek Wordnet took 0.13993287086486816s
Availability | VoID file availability check for Greek Wordnet took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for Greek Wordnet took 0.2725353240966797s
Reputation | Calculation of the PageRank for Greek Wordnet took 0.020619630813598633s
Interlinking | Calculation of Degree of Connection for Greek Wordnet took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Greek Wordnet took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Greek Wordnet took 4.172325134277344e-05s
Believability | Calculation of trust value for Greek Wordnet took 1.239776611328125e-05s
INFO | --- Analysis for greek-wordnet took 2.6326613426208496s
Availability | SPARQL endpoint availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.24344229698181152s
Availability | VoID file availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.0006074905395507812s
Extra | Recovery of all triples for Greek prisons releases Jan 2018 - Dec 2023 took 25.743894815444946s
Performance | Total latancy measurement for Greek prisons releases Jan 2018 - Dec 2023 took 0.5722732543945312s
Amount of data | Number of triples check for Greek prisons releases Jan 2018 - Dec 2023 took 0.6062071323394775s
Interoperability | New terms check for Greek prisons releases Jan 2018 - Dec 2023 took 1.6567964553833008s
Versatility | Languages check for Greek prisons releases Jan 2018 - Dec 2023 took 1.7592270374298096s
Interpretability | Number of blank nodes check for Greek prisons releases Jan 2018 - Dec 2023 took 0.46634697914123535s
Interpretability | RDF structures check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11982154846191406s
Versatility | Serialization formats check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11693906784057617s
Availability | RDF dump link check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12007284164428711s
License | MR license check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12071681022644043s
License | HR license check for Greek prisons releases Jan 2018 - Dec 2023 took 0.5270636081695557s
Amount of data | Number of property check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11413240432739258s
Understandability | Number of label check for Greek prisons releases Jan 2018 - Dec 2023 took 0.17528128623962402s
Understandability | URI regex check for Greek prisons releases Jan 2018 - Dec 2023 took 0.23060202598571777s
Understandability | Vocabs check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11460614204406738s
Verifiability | Authors check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11406588554382324s
Verifiability | Publishers check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11341404914855957s
Performance | Throughput check for Greek prisons releases Jan 2018 - Dec 2023 took 10.454787731170654s
Amount of data | Check the number of entities for Greek prisons releases Jan 2018 - Dec 2023 took 6.914138793945312e-05s
Verifiability | Contribs. check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11342024803161621s
Interlinking | sameAs chians check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11341691017150879s
Interlinking | skos check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11812543869018555s
Interlinking | skos check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11422443389892578s
Timeliness | dataset update frequency check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12010431289672852s
Currency | Creation date check for Greek prisons releases Jan 2018 - Dec 2023 took 0.22899293899536133s
Currency | Modification date check for Greek prisons releases Jan 2018 - Dec 2023 took 0.2282848358154297s
Rep.Conc. | URIs length for Greek prisons releases Jan 2018 - Dec 2023 took 7.634778738021851s
Interoperability | New vocabularies check for Greek prisons releases Jan 2018 - Dec 2023 took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11687135696411133s
Accuracy | Check Functional Property for Greek prisons releases Jan 2018 - Dec 2023 took 0.11868166923522949s
Accuracy | Check Inverse Functional Property for Greek prisons releases Jan 2018 - Dec 2023 took 0.11406135559082031s
Accuracy | Check Empty annotation labels for Greek prisons releases Jan 2018 - Dec 2023 took 3.27575421333313s
Accuracy | Check White space in annotation for Greek prisons releases Jan 2018 - Dec 2023 took 0.29805493354797363s
Accuracy | Check Datatype consistency for Greek prisons releases Jan 2018 - Dec 2023 took 4.742919921875s
Consistency | Disjoint class check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12110614776611328s
Consistency | Check Misplaced properties for Greek prisons releases Jan 2018 - Dec 2023 took 1.6806743144989014s
Consistency | Check Ontology hijacking for Greek prisons releases Jan 2018 - Dec 2023 took 4.047636270523071s
Consistency | Check Invalid usage of undefined classes for Greek prisons releases Jan 2018 - Dec 2023 took 1.3146703243255615s
Consistency | Check Invalid usage of undefined properties for Greek prisons releases Jan 2018 - Dec 2023 took 2.5172510147094727s
Conciseness | Check Extensional conciseness for Greek prisons releases Jan 2018 - Dec 2023 took 2.8677618503570557s
Security | Sign check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12569332122802734s
Availability | Check URIs Dereferenciability for Greek prisons releases Jan 2018 - Dec 2023 took 4683.758473157883s
Completeness | Calculation of interlinking completeness for Greek prisons releases Jan 2018 - Dec 2023 took 0.7569339275360107s
Reputation | Calculation of the PageRank for Greek prisons releases Jan 2018 - Dec 2023 took 0.021060705184936523s
Interlinking | Calculation of Degree of Connection for Greek prisons releases Jan 2018 - Dec 2023 took 2.6464462280273438e-05s
Interlinking | Calculation of Centrality for Greek prisons releases Jan 2018 - Dec 2023 took 0.0009613037109375s
Interlinking | Calculation of Clustering coefficient for Greek prisons releases Jan 2018 - Dec 2023 took 2.4557113647460938e-05s
Interoperability | Check the re-using of existing vocabs for Greek prisons releases Jan 2018 - Dec 2023 took 2.1457672119140625e-06s
Believability | Calculation of trust value for Greek prisons releases Jan 2018 - Dec 2023 took 8.58306884765625e-06s
INFO | --- Analysis for greek_prisons_releases took 4775.9452612400055s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 0.6887211799621582s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.26419949531555176s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.020205974578857422s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 9.393692016601562e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 1.0728836059570312e-05s
INFO | --- Analysis for greekchildrensartmuseum took 4.286987543106079s
Availability | SPARQL endpoint availability check for Green Competitiveness (GNOSS) took 8.678436279296875e-05s
Availability | VoID file availability check for Green Competitiveness (GNOSS) took 0.0006139278411865234s
Completeness | Calculation of interlinking completeness for Green Competitiveness (GNOSS) took 0.26769328117370605s
Reputation | Calculation of the PageRank for Green Competitiveness (GNOSS) took 0.02037954330444336s
Interlinking | Calculation of Degree of Connection for Green Competitiveness (GNOSS) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Green Competitiveness (GNOSS) took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Green Competitiveness (GNOSS) took 9.989738464355469e-05s
Believability | Calculation of trust value for Green Competitiveness (GNOSS) took 1.0967254638671875e-05s
INFO | --- Analysis for green-competitiveness-gnoss took 12.552413702011108s
Availability | SPARQL endpoint availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.36285829544067383s
Availability | VoID file availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for Accommodations in Piedmont (LinkedOpenData.it) took 0.2640817165374756s
Reputation | Calculation of the PageRank for Accommodations in Piedmont (LinkedOpenData.it) took 0.020368099212646484s
Interlinking | Calculation of Degree of Connection for Accommodations in Piedmont (LinkedOpenData.it) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Accommodations in Piedmont (LinkedOpenData.it) took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Accommodations in Piedmont (LinkedOpenData.it) took 4.553794860839844e-05s
Believability | Calculation of trust value for Accommodations in Piedmont (LinkedOpenData.it) took 9.775161743164062e-06s
INFO | --- Analysis for grrp took 2.876650094985962s
Availability | SPARQL endpoint availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.18788576126098633s
Availability | VoID file availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.00021839141845703125s
Completeness | Calculation of interlinking completeness for Accommodations in Tuscany (LinkedOpenData.it) took 0.27135348320007324s
Reputation | Calculation of the PageRank for Accommodations in Tuscany (LinkedOpenData.it) took 0.020304441452026367s
Interlinking | Calculation of Degree of Connection for Accommodations in Tuscany (LinkedOpenData.it) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Accommodations in Tuscany (LinkedOpenData.it) took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for Accommodations in Tuscany (LinkedOpenData.it) took 6.628036499023438e-05s
Believability | Calculation of trust value for Accommodations in Tuscany (LinkedOpenData.it) took 4.76837158203125e-06s
INFO | --- Analysis for grrt took 2.587076187133789s
Availability | SPARQL endpoint availability check for Geological Timescale took 1.0389454364776611s
Availability | VoID file availability check for Geological Timescale took 0.0003390312194824219s
Extra | Recovery of all triples for Geological Timescale took 2.4536831378936768s
Performance | Total latancy measurement for Geological Timescale took 3.642287015914917s
Amount of data | Number of triples check for Geological Timescale took 0.4245154857635498s
Interoperability | New terms check for Geological Timescale took 1.65012526512146s
Versatility | Languages check for Geological Timescale took 0.4856398105621338s
Interpretability | Number of blank nodes check for Geological Timescale took 0.9872674942016602s
Security | Check HTTPS for Geological Timescale took 0.8845958709716797s
Interpretability | RDF structures check for Geological Timescale took 0.9737339019775391s
Versatility | Serialization formats check for Geological Timescale took 0.35944080352783203s
Availability | RDF dump link check for Geological Timescale took 1.0029189586639404s
License | MR license check for Geological Timescale took 0.9431469440460205s
License | HR license check for Geological Timescale took 0.4166851043701172s
Amount of data | Number of property check for Geological Timescale took 0.9520902633666992s
Understandability | Number of label check for Geological Timescale took 0.9534411430358887s
Understandability | URI regex check for Geological Timescale took 0.7555458545684814s
Understandability | Vocabs check for Geological Timescale took 0.3932502269744873s
Verifiability | Authors check for Geological Timescale took 0.38420867919921875s
Verifiability | Publishers check for Geological Timescale took 0.3883671760559082s
Performance | Throughput check for Geological Timescale took 14.261331558227539s
Amount of data | Check the number of entities for Geological Timescale took 0.019479990005493164s
Verifiability | Contribs. check for Geological Timescale took 0.38430023193359375s
Interlinking | sameAs chians check for Geological Timescale took 0.3728203773498535s
Interlinking | skos check for Geological Timescale took 0.37338757514953613s
Interlinking | skos check for Geological Timescale took 0.9878902435302734s
Timeliness | dataset update frequency check for Geological Timescale took 0.9219346046447754s
Currency | Creation date check for Geological Timescale took 1.313936471939087s
Currency | Modification date check for Geological Timescale took 0.9471139907836914s
Rep.Conc. | URIs length for Geological Timescale took 2.002486228942871s
Interoperability | New vocabularies check for Geological Timescale took 2.3543200492858887s
Consistency | Deprecated classes/propertiers check for Geological Timescale took 0.9379959106445312s
Accuracy | Check Functional Property for Geological Timescale took 0.9281260967254639s
Accuracy | Check Inverse Functional Property for Geological Timescale took 0.9036483764648438s
Accuracy | Check Empty annotation labels for Geological Timescale took 0.7685174942016602s
Accuracy | Check White space in annotation for Geological Timescale took 0.015607833862304688s
Accuracy | Check Datatype consistency for Geological Timescale took 0.07198691368103027s
Consistency | Disjoint class check for Geological Timescale took 0.38187336921691895s
Consistency | Check Misplaced properties for Geological Timescale took 0.757664680480957s
Consistency | Misplaced classes for Geological Timescale took 1.0605406761169434s
Consistency | Check Ontology hijacking for Geological Timescale took 1.7209994792938232s
Consistency | Check Invalid usage of undefined classes for Geological Timescale took 1.2535827159881592s
Consistency | Check Invalid usage of undefined properties for Geological Timescale took 1.6702947616577148s
Conciseness | Check Extensional conciseness for Geological Timescale took 0.050136566162109375s
Conciseness | Check Intensional conciseness for Geological Timescale took 0.38310837745666504s
Security | Sign check for Geological Timescale took 0.8985905647277832s
Availability | Check URIs Dereferenciability for Geological Timescale took 3.0710294246673584s
Completeness | Calculation of interlinking completeness for Geological Timescale took 0.2815256118774414s
Reputation | Calculation of the PageRank for Geological Timescale took 0.020089149475097656s
Interlinking | Calculation of Degree of Connection for Geological Timescale took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Geological Timescale took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Geological Timescale took 6.67572021484375e-05s
Interoperability | Check the re-using of existing vocabs for Geological Timescale took 1.600733995437622s
Believability | Calculation of trust value for Geological Timescale took 1.2159347534179688e-05s
INFO | --- Analysis for GTS took 103.46358823776245s
Availability | SPARQL endpoint availability check for Geological Timescale Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Geological Timescale Ontology took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for Geological Timescale Ontology took 0.26368188858032227s
Reputation | Calculation of the PageRank for Geological Timescale Ontology took 0.02214837074279785s
Interlinking | Calculation of Degree of Connection for Geological Timescale Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Geological Timescale Ontology took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Geological Timescale Ontology took 3.1948089599609375e-05s
Believability | Calculation of trust value for Geological Timescale Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for GTS-ont took 3.0191969871520996s
Availability | SPARQL endpoint availability check for GUTSTOK  took 4.172325134277344e-05s
Availability | VoID file availability check for GUTSTOK  took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for GUTSTOK  took 0.26812219619750977s
Reputation | Calculation of the PageRank for GUTSTOK  took 0.020322322845458984s
Interlinking | Calculation of Degree of Connection for GUTSTOK  took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GUTSTOK  took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for GUTSTOK  took 3.0040740966796875e-05s
Believability | Calculation of trust value for GUTSTOK  took 1.1205673217773438e-05s
INFO | --- Analysis for Guillaume_Forget took 3.0300259590148926s
Availability | SPARQL endpoint availability check for Project Gutenberg took 4.172325134277344e-05s
Availability | VoID file availability check for Project Gutenberg took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for Project Gutenberg took 0.26891207695007324s
Reputation | Calculation of the PageRank for Project Gutenberg took 0.02024555206298828s
Interlinking | Calculation of Degree of Connection for Project Gutenberg took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Project Gutenberg took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg took 6.794929504394531e-05s
Believability | Calculation of trust value for Project Gutenberg took 6.67572021484375e-06s
INFO | --- Analysis for gutenberg took 9.83867621421814s
Availability | SPARQL endpoint availability check for Global WordNet Association Interlingual Index took 8.559226989746094e-05s
Availability | VoID file availability check for Global WordNet Association Interlingual Index took 0.0006213188171386719s
Completeness | Calculation of interlinking completeness for Global WordNet Association Interlingual Index took 0.291168212890625s
Reputation | Calculation of the PageRank for Global WordNet Association Interlingual Index took 0.020229101181030273s
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.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Global WordNet Association Interlingual Index took 3.409385681152344e-05s
Believability | Calculation of trust value for Global WordNet Association Interlingual Index took 1.0013580322265625e-05s
INFO | --- Analysis for gwa-ili took 5.503413677215576s
Availability | SPARQL endpoint availability check for Geographically Weighted Regression Model took 4.1961669921875e-05s
Availability | VoID file availability check for Geographically Weighted Regression Model took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for Geographically Weighted Regression Model took 0.2638051509857178s
Reputation | Calculation of the PageRank for Geographically Weighted Regression Model took 0.020386219024658203s
Interlinking | Calculation of Degree of Connection for Geographically Weighted Regression Model took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Geographically Weighted Regression Model took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for Geographically Weighted Regression Model took 3.6716461181640625e-05s
Believability | Calculation of trust value for Geographically Weighted Regression Model took 1.049041748046875e-05s
INFO | --- Analysis for GWR took 18.831924200057983s
Availability | SPARQL endpoint availability check for High Accuracy Surface Modeling took 4.1484832763671875e-05s
Availability | VoID file availability check for High Accuracy Surface Modeling took 0.0006117820739746094s
Completeness | Calculation of interlinking completeness for High Accuracy Surface Modeling took 0.2749142646789551s
Reputation | Calculation of the PageRank for High Accuracy Surface Modeling took 0.020607471466064453s
Interlinking | Calculation of Degree of Connection for High Accuracy Surface Modeling took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for High Accuracy Surface Modeling took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for High Accuracy Surface Modeling took 3.147125244140625e-05s
Believability | Calculation of trust value for High Accuracy Surface Modeling took 1.1444091796875e-05s
INFO | --- Analysis for HASM took 20.724498748779297s
Availability | SPARQL endpoint availability check for HealthCare Ontology took 3.592083215713501s
Availability | VoID file availability check for HealthCare Ontology took 0.0006191730499267578s
Completeness | Calculation of interlinking completeness for HealthCare Ontology took 0.26444196701049805s
Reputation | Calculation of the PageRank for HealthCare Ontology took 0.022245407104492188s
Interlinking | Calculation of Degree of Connection for HealthCare Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for HealthCare Ontology took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for HealthCare Ontology took 5.125999450683594e-05s
Believability | Calculation of trust value for HealthCare Ontology took 1.1444091796875e-05s
INFO | --- Analysis for HealthCare_Ontology took 6.478927373886108s
Availability | SPARQL endpoint availability check for Meriterm Heart Failure Multilingual Terminology took 8.726119995117188e-05s
Availability | VoID file availability check for Meriterm Heart Failure Multilingual Terminology took 0.0006418228149414062s
Completeness | Calculation of interlinking completeness for Meriterm Heart Failure Multilingual Terminology took 0.2752501964569092s
Reputation | Calculation of the PageRank for Meriterm Heart Failure Multilingual Terminology took 0.02160191535949707s
Interlinking | Calculation of Degree of Connection for Meriterm Heart Failure Multilingual Terminology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Meriterm Heart Failure Multilingual Terminology took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Meriterm Heart Failure Multilingual Terminology took 6.127357482910156e-05s
Believability | Calculation of trust value for Meriterm Heart Failure Multilingual Terminology took 1.3113021850585938e-05s
INFO | --- Analysis for heartfailure took 2.7888031005859375s
Availability | SPARQL endpoint availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 21.269176721572876s
Availability | VoID file availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0006556510925292969s
Completeness | Calculation of interlinking completeness for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.2711000442504883s
Reputation | Calculation of the PageRank for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.020443439483642578s
Interlinking | Calculation of Degree of Connection for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 3.886222839355469e-05s
Believability | Calculation of trust value for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 1.0251998901367188e-05s
INFO | --- Analysis for hebis-bibliographic-resources took 118.38067579269409s
Availability | SPARQL endpoint availability check for Hedatuz took 0.24103879928588867s
Availability | VoID file availability check for Hedatuz took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for Hedatuz took 0.2752048969268799s
Reputation | Calculation of the PageRank for Hedatuz took 0.021494150161743164s
Interlinking | Calculation of Degree of Connection for Hedatuz took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Hedatuz took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Hedatuz took 3.647804260253906e-05s
Believability | Calculation of trust value for Hedatuz took 9.775161743164062e-06s
INFO | --- Analysis for hedatuz took 3.044947385787964s
Availability | SPARQL endpoint availability check for Hellenic Fire Brigade took 0.11797952651977539s
Availability | VoID file availability check for Hellenic Fire Brigade took 0.0004417896270751953s
Completeness | Calculation of interlinking completeness for Hellenic Fire Brigade took 0.26848745346069336s
Reputation | Calculation of the PageRank for Hellenic Fire Brigade took 0.020381689071655273s
Interlinking | Calculation of Degree of Connection for Hellenic Fire Brigade took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Hellenic Fire Brigade took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Hellenic Fire Brigade took 0.00012159347534179688s
Believability | Calculation of trust value for Hellenic Fire Brigade took 8.344650268554688e-06s
INFO | --- Analysis for hellenic-fire-brigade took 2.58589243888855s
Availability | SPARQL endpoint availability check for Hellenic Police took 0.01959705352783203s
Availability | VoID file availability check for Hellenic Police took 0.00043845176696777344s
Completeness | Calculation of interlinking completeness for Hellenic Police took 0.2694995403289795s
Reputation | Calculation of the PageRank for Hellenic Police took 0.0221555233001709s
Interlinking | Calculation of Degree of Connection for Hellenic Police took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Hellenic Police took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Hellenic Police took 0.00012302398681640625s
Believability | Calculation of trust value for Hellenic Police took 9.059906005859375e-06s
INFO | --- Analysis for hellenic-police took 2.515922784805298s
Availability | SPARQL endpoint availability check for Hermos took 8.606910705566406e-05s
Availability | VoID file availability check for Hermos took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for Hermos took 0.27313876152038574s
Reputation | Calculation of the PageRank for Hermos took 0.020326852798461914s
Interlinking | Calculation of Degree of Connection for Hermos took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Hermos took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Hermos took 2.7418136596679688e-05s
Believability | Calculation of trust value for Hermos took 9.775161743164062e-06s
INFO | --- Analysis for Hermos took 3.033860683441162s
Availability | SPARQL endpoint availability check for Himanshu Mahawar took 4.100799560546875e-05s
Availability | VoID file availability check for Himanshu Mahawar took 0.0009765625s
Completeness | Calculation of interlinking completeness for Himanshu Mahawar took 0.2640054225921631s
Reputation | Calculation of the PageRank for Himanshu Mahawar took 0.020459890365600586s
Interlinking | Calculation of Degree of Connection for Himanshu Mahawar took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Himanshu Mahawar took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Himanshu Mahawar took 2.765655517578125e-05s
Believability | Calculation of trust value for Himanshu Mahawar took 9.059906005859375e-06s
INFO | --- Analysis for Himanshu_Mahawar took 2.4736695289611816s
Availability | SPARQL endpoint availability check for HITO took 0.3903348445892334s
Availability | VoID file availability check for HITO took 0.0005049705505371094s
Extra | Recovery of all triples for HITO took 0.1795504093170166s
Performance | Total latancy measurement for HITO took 0.9003229141235352s
Amount of data | Number of triples check for HITO took 0.17961454391479492s
Interoperability | New terms check for HITO took 1.4761433601379395s
Versatility | Languages check for HITO took 0.22829008102416992s
Interpretability | Number of blank nodes check for HITO took 0.17671418190002441s
Interpretability | RDF structures check for HITO took 0.1889204978942871s
Versatility | Serialization formats check for HITO took 0.18387842178344727s
Availability | RDF dump link check for HITO took 0.17600107192993164s
License | MR license check for HITO took 0.1847524642944336s
License | HR license check for HITO took 0.20629024505615234s
Amount of data | Number of property check for HITO took 0.20379018783569336s
Understandability | Number of label check for HITO took 0.19062495231628418s
Understandability | URI regex check for HITO took 0.35605812072753906s
Understandability | Vocabs check for HITO took 0.17885994911193848s
Verifiability | Authors check for HITO took 0.1908116340637207s
Verifiability | Publishers check for HITO took 0.1970365047454834s
Performance | Throughput check for HITO took 10.732415199279785s
Amount of data | Check the number of entities for HITO took 6.985664367675781e-05s
Verifiability | Contribs. check for HITO took 0.1901395320892334s
Interlinking | sameAs chians check for HITO took 0.16977787017822266s
Interlinking | skos check for HITO took 0.17061448097229004s
Interlinking | skos check for HITO took 0.18458223342895508s
Timeliness | dataset update frequency check for HITO took 0.17953252792358398s
Currency | Creation date check for HITO took 0.3762047290802002s
Currency | Modification date check for HITO took 0.36005520820617676s
Rep.Conc. | URIs length for HITO took 1.0543742179870605s
Interoperability | New vocabularies check for HITO took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for HITO took 0.18581128120422363s
Accuracy | Check Functional Property for HITO took 0.16869854927062988s
Accuracy | Check Inverse Functional Property for HITO took 0.17612147331237793s
Accuracy | Check Empty annotation labels for HITO took 0.5222804546356201s
Accuracy | Check White space in annotation for HITO took 0.01332998275756836s
Consistency | Disjoint class check for HITO took 0.17709922790527344s
Consistency | Check Misplaced properties for HITO took 0.4686870574951172s
Consistency | Misplaced classes for HITO took 0.18613243103027344s
Consistency | Check Ontology hijacking for HITO took 1.7337219715118408s
Consistency | Check Invalid usage of undefined properties for HITO took 1.5036430358886719s
Conciseness | Check Extensional conciseness for HITO took 0.00012993812561035156s
Conciseness | Check Intensional conciseness for HITO took 0.16769027709960938s
Security | Sign check for HITO took 0.1850109100341797s
Availability | Check URIs Dereferenciability for HITO took 1692.8265588283539s
Completeness | Calculation of interlinking completeness for HITO took 0.4753446578979492s
Reputation | Calculation of the PageRank for HITO took 0.021203994750976562s
Interlinking | Calculation of Degree of Connection for HITO took 2.288818359375e-05s
Interlinking | Calculation of Centrality for HITO took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for HITO took 0.0001418590545654297s
Interoperability | Check the re-using of existing vocabs for HITO took 9.5367431640625e-07s
Believability | Calculation of trust value for HITO took 1.0728836059570312e-05s
INFO | --- Analysis for hito took 1740.0424675941467s
Availability | SPARQL endpoint availability check for Hoa Thịnh Phát took 15.594454050064087s
Availability | VoID file availability check for Hoa Thịnh Phát took 0.0005679130554199219s
Completeness | Calculation of interlinking completeness for Hoa Thịnh Phát took 0.26780009269714355s
Reputation | Calculation of the PageRank for Hoa Thịnh Phát took 0.020749568939208984s
Interlinking | Calculation of Degree of Connection for Hoa Thịnh Phát took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Hoa Thịnh Phát took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Hoa Thịnh Phát took 3.719329833984375e-05s
Believability | Calculation of trust value for Hoa Thịnh Phát took 2.7179718017578125e-05s
INFO | --- Analysis for Hoa_Thinh_Phat took 53.6419620513916s
Availability | SPARQL endpoint availability check for gseg took 8.869171142578125e-05s
Availability | VoID file availability check for gseg took 0.0006308555603027344s
Completeness | Calculation of interlinking completeness for gseg took 0.26555728912353516s
Reputation | Calculation of the PageRank for gseg took 0.02081298828125s
Interlinking | Calculation of Degree of Connection for gseg took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for gseg took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for gseg took 3.266334533691406e-05s
Believability | Calculation of trust value for gseg took 9.775161743164062e-06s
INFO | --- Analysis for hongse took 3.199889898300171s
Availability | SPARQL endpoint availability check for COURAGE Dataset took 2.3046200275421143s
Availability | VoID file availability check for COURAGE Dataset took 0.0007259845733642578s
Completeness | Calculation of interlinking completeness for COURAGE Dataset took 0.26612162590026855s
Reputation | Calculation of the PageRank for COURAGE Dataset took 0.020842790603637695s
Interlinking | Calculation of Degree of Connection for COURAGE Dataset took 1.52587890625e-05s
Interlinking | Calculation of Centrality for COURAGE Dataset took 0.0009610652923583984s
Interlinking | Calculation of Clustering coefficient for COURAGE Dataset took 4.363059997558594e-05s
Believability | Calculation of trust value for COURAGE Dataset took 1.1682510375976562e-05s
INFO | --- Analysis for http:cultural-opposition.eu took 6.0119054317474365s
Availability | SPARQL endpoint availability check for RoadTrb took 4.506111145019531e-05s
Availability | VoID file availability check for RoadTrb took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for RoadTrb took 0.2590515613555908s
Reputation | Calculation of the PageRank for RoadTrb took 0.020415067672729492s
Interlinking | Calculation of Degree of Connection for RoadTrb took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for RoadTrb took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for RoadTrb took 3.170967102050781e-05s
Believability | Calculation of trust value for RoadTrb took 1.0013580322265625e-05s
INFO | --- Analysis for http:data.linkedeodata.euroadidStateRoadD010Turkey-1 took 2.4500958919525146s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 8.916854858398438e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0007023811340332031s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.2741234302520752s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.020775794982910156s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 3.743171691894531e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 1.1920928955078125e-05s
INFO | --- Analysis for http:guava.iis.sinica.edu.twr4r took 30.441219329833984s
Availability | SPARQL endpoint availability check for Polictical History of Pakistan took 9.012222290039062e-05s
Availability | VoID file availability check for Polictical History of Pakistan took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for Polictical History of Pakistan took 0.28018689155578613s
Reputation | Calculation of the PageRank for Polictical History of Pakistan took 0.020598411560058594s
Interlinking | Calculation of Degree of Connection for Polictical History of Pakistan took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Polictical History of Pakistan took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Polictical History of Pakistan took 3.0040740966796875e-05s
Believability | Calculation of trust value for Polictical History of Pakistan took 6.67572021484375e-06s
INFO | --- Analysis for http:pakistan.com took 2.473619222640991s
Availability | SPARQL endpoint availability check for CEDICT took 8.654594421386719e-05s
Availability | VoID file availability check for CEDICT took 0.0007901191711425781s
Completeness | Calculation of interlinking completeness for CEDICT took 0.26302599906921387s
Reputation | Calculation of the PageRank for CEDICT took 0.020923852920532227s
Interlinking | Calculation of Degree of Connection for CEDICT took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CEDICT took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for CEDICT took 3.266334533691406e-05s
Believability | Calculation of trust value for CEDICT took 1.1205673217773438e-05s
INFO | --- Analysis for http:rdf.naturallexicon.orgzhontCedict took 3.8081254959106445s
Availability | SPARQL endpoint availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.836243629455566s
Availability | VoID file availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.27411985397338867s
Reputation | Calculation of the PageRank for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.02059650421142578s
Interlinking | Calculation of Degree of Connection for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.961822509765625e-05s
Believability | Calculation of trust value for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.1205673217773438e-05s
INFO | --- Analysis for http:sensormeasurement.appspot.comdatasetnaturopathy-dataset took 9.981354475021362s
Availability | SPARQL endpoint availability check for Pakistan Stock Market Data took 8.249282836914062e-05s
Availability | VoID file availability check for Pakistan Stock Market Data took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for Pakistan Stock Market Data took 0.264146089553833s
Reputation | Calculation of the PageRank for Pakistan Stock Market Data took 0.02074885368347168s
Interlinking | Calculation of Degree of Connection for Pakistan Stock Market Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Pakistan Stock Market Data took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Pakistan Stock Market Data took 3.123283386230469e-05s
Believability | Calculation of trust value for Pakistan Stock Market Data took 1.0251998901367188e-05s
INFO | --- Analysis for http:www.atif-sajjad.comSemster-Project# took 2.9821486473083496s
Availability | SPARQL endpoint availability check for Grand Slam Knowledge Graph took 4.410743713378906e-05s
Availability | VoID file availability check for Grand Slam Knowledge Graph took 0.00021648406982421875s
Completeness | Calculation of interlinking completeness for Grand Slam Knowledge Graph took 0.2808220386505127s
Reputation | Calculation of the PageRank for Grand Slam Knowledge Graph took 0.020976781845092773s
Interlinking | Calculation of Degree of Connection for Grand Slam Knowledge Graph took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Grand Slam Knowledge Graph took 0.0011255741119384766s
Interlinking | Calculation of Clustering coefficient for Grand Slam Knowledge Graph took 4.2438507080078125e-05s
Believability | Calculation of trust value for Grand Slam Knowledge Graph took 1.0251998901367188e-05s
INFO | --- Analysis for http:www.fateh_fahad_adeel.comgrandSlam took 2.475651502609253s
Availability | SPARQL endpoint availability check for Soccer Dataset took 9.179115295410156e-05s
Availability | VoID file availability check for Soccer Dataset took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for Soccer Dataset took 0.2737088203430176s
Reputation | Calculation of the PageRank for Soccer Dataset took 0.020773649215698242s
Interlinking | Calculation of Degree of Connection for Soccer Dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Soccer Dataset took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Soccer Dataset took 3.24249267578125e-05s
Believability | Calculation of trust value for Soccer Dataset took 1.0728836059570312e-05s
INFO | --- Analysis for http:www.msm.com took 2.477177381515503s
Availability | SPARQL endpoint availability check for Game Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Game Ontology took 0.0004951953887939453s
Completeness | Calculation of interlinking completeness for Game Ontology took 0.27342700958251953s
Reputation | Calculation of the PageRank for Game Ontology took 0.02071380615234375s
Interlinking | Calculation of Degree of Connection for Game Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Game Ontology took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Game Ontology took 3.314018249511719e-05s
Believability | Calculation of trust value for Game Ontology took 1.3828277587890625e-05s
INFO | --- Analysis for http:www.RAG.comgameonto# took 2.9920494556427s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 9.34600830078125e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0004303455352783203s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.2715177536010742s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.02038431167602539s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.218650817871094e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 7.3909759521484375e-06s
INFO | --- Analysis for http:www.semanticweb.orgambrishontologies202010untitled-ontology-24 took 3.016090154647827s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 6.270408630371094e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.26244401931762695s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.020627260208129883s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.24249267578125e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.0728836059570312e-05s
INFO | --- Analysis for http:www.semanticweb.orgarchanaontologies20215untitled-ontology-6 took 2.462507486343384s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 8.58306884765625e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.00046443939208984375s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2696990966796875s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02060246467590332s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.170967102050781e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.1444091796875e-05s
INFO | --- Analysis for http:www.semanticweb.orgmcaontologies20188untitled-ontology-47 took 2.5060415267944336s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 8.893013000488281e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.000457763671875s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2688281536102295s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020571231842041016s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.504753112792969e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.0013580322265625e-05s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIO took 2.420809745788574s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.2438507080078125e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.29729485511779785s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.022366046905517578s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.147125244140625e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.049041748046875e-05s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIOp=summary took 2.6191794872283936s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 8.630752563476562e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.000682830810546875s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2736687660217285s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020720481872558594s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.24249267578125e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.4066696166992188e-05s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBDsubmissions1downloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb took 3.7607905864715576s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.363059997558594e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0004718303680419922s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.27651071548461914s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02054452896118164s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.0517578125e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.2159347534179688e-05s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBIOsubmissions1downloadapikey=66c2aec1-4044-4900-979d-6f529857554a took 2.445948362350464s
Availability | SPARQL endpoint availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 4.601478576660156e-05s
Availability | VoID file availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0007810592651367188s
Completeness | Calculation of interlinking completeness for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.2722949981689453s
Reputation | Calculation of the PageRank for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.021811962127685547s
Interlinking | Calculation of Degree of Connection for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Diretrizes organizacionais de métodos quantitativos e computação científica took 3.218650817871094e-05s
Believability | Calculation of trust value for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.0251998901367188e-05s
INFO | --- Analysis for https:orcid.org0000-0002-6194-9354 took 4.462209224700928s
Availability | SPARQL endpoint availability check for Bookkeeping took 10.678935289382935s
Availability | VoID file availability check for Bookkeeping took 0.0005793571472167969s
Completeness | Calculation of interlinking completeness for Bookkeeping took 0.2822866439819336s
Reputation | Calculation of the PageRank for Bookkeeping took 0.020637035369873047s
Interlinking | Calculation of Degree of Connection for Bookkeeping took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bookkeeping took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Bookkeeping took 3.0517578125e-05s
Believability | Calculation of trust value for Bookkeeping took 9.775161743164062e-06s
INFO | --- Analysis for https:raw.githubusercontent.comGVogelerbookkeepingmasterbookkeeping.ttl took 13.806941747665405s
Availability | SPARQL endpoint availability check for Legal Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Legal Ontology took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for Legal Ontology took 0.2738678455352783s
Reputation | Calculation of the PageRank for Legal Ontology took 0.020420074462890625s
Interlinking | Calculation of Degree of Connection for Legal Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Legal Ontology took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Legal Ontology took 3.504753112792969e-05s
Believability | Calculation of trust value for Legal Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for https:w3id.orgdefNyOnLegal# took 3.308748483657837s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 0.00010013580322265625s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.2666153907775879s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.020479917526245117s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.843971252441406e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 5.245208740234375e-06s
INFO | --- Analysis for https:www.childrensartmuseum.grLD-project took 2.684617280960083s
Availability | SPARQL endpoint availability check for Writer Luigi Usai took 4.291534423828125e-05s
Availability | VoID file availability check for Writer Luigi Usai took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for Writer Luigi Usai took 0.27349162101745605s
Reputation | Calculation of the PageRank for Writer Luigi Usai took 0.020581483840942383s
Interlinking | Calculation of Degree of Connection for Writer Luigi Usai took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Writer Luigi Usai took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Writer Luigi Usai took 3.24249267578125e-05s
Believability | Calculation of trust value for Writer Luigi Usai took 1.0967254638671875e-05s
INFO | --- Analysis for https:www.luigiusai.itlinked-dataluigiusai took 2.614603281021118s
Availability | SPARQL endpoint availability check for Hungarian National Library (NSZL) catalog took 1.1785519123077393s
Availability | VoID file availability check for Hungarian National Library (NSZL) catalog took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for Hungarian National Library (NSZL) catalog took 0.2883458137512207s
Reputation | Calculation of the PageRank for Hungarian National Library (NSZL) catalog took 0.02063155174255371s
Interlinking | Calculation of Degree of Connection for Hungarian National Library (NSZL) catalog took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Hungarian National Library (NSZL) catalog took 0.0008273124694824219s
Interlinking | Calculation of Clustering coefficient for Hungarian National Library (NSZL) catalog took 0.0001220703125s
Believability | Calculation of trust value for Hungarian National Library (NSZL) catalog took 7.867813110351562e-06s
INFO | --- Analysis for hungarian-national-library-catalog took 3.9054152965545654s
Availability | SPARQL endpoint availability check for IATE RDF took 8.487701416015625e-05s
Availability | VoID file availability check for IATE RDF took 0.0004527568817138672s
Completeness | Calculation of interlinking completeness for IATE RDF took 0.26557159423828125s
Reputation | Calculation of the PageRank for IATE RDF took 0.02034592628479004s
Interlinking | Calculation of Degree of Connection for IATE RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for IATE RDF took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for IATE RDF took 3.62396240234375e-05s
Believability | Calculation of trust value for IATE RDF took 9.775161743164062e-06s
INFO | --- Analysis for iate-rdf took 2.645418167114258s
Availability | SPARQL endpoint availability check for IATI as Linked Data took 6.252933502197266s
Availability | VoID file availability check for IATI as Linked Data took 0.0006659030914306641s
Completeness | Calculation of interlinking completeness for IATI as Linked Data took 0.26339197158813477s
Reputation | Calculation of the PageRank for IATI as Linked Data took 0.020822763442993164s
Interlinking | Calculation of Degree of Connection for IATI as Linked Data took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for IATI as Linked Data took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for IATI as Linked Data took 8.630752563476562e-05s
Believability | Calculation of trust value for IATI as Linked Data took 1.0013580322265625e-05s
INFO | --- Analysis for iati-as-linked-data took 12.751389503479004s
Availability | SPARQL endpoint availability check for ICANE took 0.3417973518371582s
Availability | VoID file availability check for ICANE took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for ICANE took 0.2978236675262451s
Reputation | Calculation of the PageRank for ICANE took 0.020723819732666016s
Interlinking | Calculation of Degree of Connection for ICANE took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for ICANE took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for ICANE took 8.702278137207031e-05s
Believability | Calculation of trust value for ICANE took 8.344650268554688e-06s
INFO | --- Analysis for icane took 3.8097779750823975s
Availability | SPARQL endpoint availability check for ichoose took 0.11846375465393066s
Availability | VoID file availability check for ichoose took 0.0002753734588623047s
Completeness | Calculation of interlinking completeness for ichoose took 0.2686593532562256s
Reputation | Calculation of the PageRank for ichoose took 0.02116227149963379s
Interlinking | Calculation of Degree of Connection for ichoose took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ichoose took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for ichoose took 6.771087646484375e-05s
Believability | Calculation of trust value for ichoose took 9.775161743164062e-06s
INFO | --- Analysis for ichoose took 42.57476472854614s
Availability | SPARQL endpoint availability check for The Iconology Dataset took 0.33100390434265137s
Availability | VoID file availability check for The Iconology Dataset took 0.0005135536193847656s
Extra | Recovery of all triples for The Iconology Dataset took 5.834481716156006s
Performance | Total latancy measurement for The Iconology Dataset took 0.8778214454650879s
Amount of data | Number of triples check for The Iconology Dataset took 0.26018285751342773s
Interoperability | New terms check for The Iconology Dataset took 1.4333736896514893s
Versatility | Languages check for The Iconology Dataset took 0.6236581802368164s
Interpretability | Number of blank nodes check for The Iconology Dataset took 0.33930444717407227s
Interpretability | RDF structures check for The Iconology Dataset took 0.11884164810180664s
Versatility | Serialization formats check for The Iconology Dataset took 0.10912013053894043s
Availability | RDF dump link check for The Iconology Dataset took 0.08648228645324707s
License | MR license check for The Iconology Dataset took 0.10710883140563965s
License | HR license check for The Iconology Dataset took 0.23789691925048828s
Amount of data | Number of property check for The Iconology Dataset took 0.1028754711151123s
Understandability | Number of label check for The Iconology Dataset took 0.15696072578430176s
Understandability | URI regex check for The Iconology Dataset took 0.1699995994567871s
Understandability | Vocabs check for The Iconology Dataset took 0.08939909934997559s
Verifiability | Authors check for The Iconology Dataset took 0.0995943546295166s
Verifiability | Publishers check for The Iconology Dataset took 0.15226364135742188s
Performance | Throughput check for The Iconology Dataset took 10.674866199493408s
Amount of data | Check the number of entities for The Iconology Dataset took 0.00042748451232910156s
Verifiability | Contribs. check for The Iconology Dataset took 0.0864558219909668s
Interlinking | sameAs chians check for The Iconology Dataset took 0.09081101417541504s
Interlinking | skos check for The Iconology Dataset took 0.0862112045288086s
Interlinking | skos check for The Iconology Dataset took 0.08871889114379883s
Timeliness | dataset update frequency check for The Iconology Dataset took 0.08717608451843262s
Currency | Creation date check for The Iconology Dataset took 0.17271208763122559s
Currency | Modification date check for The Iconology Dataset took 0.1937255859375s
Rep.Conc. | URIs length for The Iconology Dataset took 1.3199577331542969s
Interoperability | New vocabularies check for The Iconology Dataset took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for The Iconology Dataset took 0.08022403717041016s
Accuracy | Check Empty annotation labels for The Iconology Dataset took 0.3508174419403076s
Accuracy | Check White space in annotation for The Iconology Dataset took 0.016121387481689453s
Accuracy | Check Datatype consistency for The Iconology Dataset took 0.4178025722503662s
Consistency | Disjoint class check for The Iconology Dataset took 0.07813191413879395s
Consistency | Check Misplaced properties for The Iconology Dataset took 0.16408419609069824s
Consistency | Misplaced classes for The Iconology Dataset took 0.8541834354400635s
Consistency | Check Ontology hijacking for The Iconology Dataset took 1.6043741703033447s
Consistency | Check Invalid usage of undefined classes for The Iconology Dataset took 1.2664399147033691s
Consistency | Check Invalid usage of undefined properties for The Iconology Dataset took 1.3376832008361816s
Conciseness | Check Extensional conciseness for The Iconology Dataset took 0.2877237796783447s
Security | Sign check for The Iconology Dataset took 0.07779145240783691s
Availability | Check URIs Dereferenciability for The Iconology Dataset took 2442.6332433223724s
Completeness | Calculation of interlinking completeness for The Iconology Dataset took 1.4918923377990723s
Reputation | Calculation of the PageRank for The Iconology Dataset took 0.020884990692138672s
Interlinking | Calculation of Degree of Connection for The Iconology Dataset took 3.4809112548828125e-05s
Interlinking | Calculation of Centrality for The Iconology Dataset took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for The Iconology Dataset took 2.0265579223632812e-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 1.0728836059570312e-05s
INFO | --- Analysis for iconology-dataset took 2501.0449793338776s
Availability | SPARQL endpoint availability check for IdRef: Sudoc authority data took 0.00011301040649414062s
Availability | VoID file availability check for IdRef: Sudoc authority data took 0.000629425048828125s
Completeness | Calculation of interlinking completeness for IdRef: Sudoc authority data took 0.2706310749053955s
Reputation | Calculation of the PageRank for IdRef: Sudoc authority data took 0.02039051055908203s
Interlinking | Calculation of Degree of Connection for IdRef: Sudoc authority data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for IdRef: Sudoc authority data took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for IdRef: Sudoc authority data took 7.605552673339844e-05s
Believability | Calculation of trust value for IdRef: Sudoc authority data took 1.1444091796875e-05s
INFO | --- Analysis for idreffr took 4.892989158630371s
Availability | SPARQL endpoint availability check for Intercontinental Dictionary Series took 0.6568012237548828s
Availability | VoID file availability check for Intercontinental Dictionary Series took 0.0004978179931640625s
Completeness | Calculation of interlinking completeness for Intercontinental Dictionary Series took 0.267254114151001s
Reputation | Calculation of the PageRank for Intercontinental Dictionary Series took 0.020579814910888672s
Interlinking | Calculation of Degree of Connection for Intercontinental Dictionary Series took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Intercontinental Dictionary Series took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Intercontinental Dictionary Series took 5.030632019042969e-05s
Believability | Calculation of trust value for Intercontinental Dictionary Series took 1.239776611328125e-05s
INFO | --- Analysis for ids took 3.569650888442993s
Availability | SPARQL endpoint availability check for ietflang took 0.00010752677917480469s
Availability | VoID file availability check for ietflang took 0.0008068084716796875s
Completeness | Calculation of interlinking completeness for ietflang took 0.27959132194519043s
Reputation | Calculation of the PageRank for ietflang took 0.022246122360229492s
Interlinking | Calculation of Degree of Connection for ietflang took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ietflang took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for ietflang took 4.6253204345703125e-05s
Believability | Calculation of trust value for ietflang took 9.5367431640625e-06s
INFO | --- Analysis for ietflang took 14.301556587219238s
Availability | SPARQL endpoint availability check for Index Graecorum Vocabulorum in LiLa took 0.6578962802886963s
Availability | VoID file availability check for Index Graecorum Vocabulorum in LiLa took 0.0005819797515869141s
Completeness | Calculation of interlinking completeness for Index Graecorum Vocabulorum in LiLa took 0.26003336906433105s
Reputation | Calculation of the PageRank for Index Graecorum Vocabulorum in LiLa took 0.02111649513244629s
Interlinking | Calculation of Degree of Connection for Index Graecorum Vocabulorum in LiLa took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Index Graecorum Vocabulorum in LiLa took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Index Graecorum Vocabulorum in LiLa took 4.172325134277344e-05s
Believability | Calculation of trust value for Index Graecorum Vocabulorum in LiLa took 1.1682510375976562e-05s
INFO | --- Analysis for IGVLL took 4.311024188995361s
Availability | SPARQL endpoint availability check for 3LGM² IHE Ontology took 0.4378480911254883s
Availability | VoID file availability check for 3LGM² IHE Ontology took 0.0006558895111083984s
Extra | Recovery of all triples for 3LGM² IHE Ontology took 2.0926337242126465s
Performance | Total latancy measurement for 3LGM² IHE Ontology took 0.9120216369628906s
Amount of data | Number of triples check for 3LGM² IHE Ontology took 0.21032452583312988s
Interoperability | New terms check for 3LGM² IHE Ontology took 1.4874310493469238s
Versatility | Languages check for 3LGM² IHE Ontology took 0.2115802764892578s
Interpretability | Number of blank nodes check for 3LGM² IHE Ontology took 0.21453619003295898s
Interpretability | RDF structures check for 3LGM² IHE Ontology took 0.215895414352417s
Versatility | Serialization formats check for 3LGM² IHE Ontology took 0.21608829498291016s
Availability | RDF dump link check for 3LGM² IHE Ontology took 0.17705941200256348s
License | MR license check for 3LGM² IHE Ontology took 0.18065524101257324s
License | HR license check for 3LGM² IHE Ontology took 0.19292449951171875s
Amount of data | Number of property check for 3LGM² IHE Ontology took 0.18272686004638672s
Understandability | Number of label check for 3LGM² IHE Ontology took 0.18680834770202637s
Understandability | URI regex check for 3LGM² IHE Ontology took 0.3460547924041748s
Understandability | Vocabs check for 3LGM² IHE Ontology took 0.18760013580322266s
Verifiability | Authors check for 3LGM² IHE Ontology took 0.1820840835571289s
Verifiability | Publishers check for 3LGM² IHE Ontology took 0.19591474533081055s
Performance | Throughput check for 3LGM² IHE Ontology took 10.689429759979248s
Amount of data | Check the number of entities for 3LGM² IHE Ontology took 7.200241088867188e-05s
Verifiability | Contribs. check for 3LGM² IHE Ontology took 0.17098355293273926s
Interlinking | sameAs chians check for 3LGM² IHE Ontology took 0.18649983406066895s
Interlinking | skos check for 3LGM² IHE Ontology took 0.18813848495483398s
Interlinking | skos check for 3LGM² IHE Ontology took 0.1762247085571289s
Timeliness | dataset update frequency check for 3LGM² IHE Ontology took 0.1972057819366455s
Currency | Creation date check for 3LGM² IHE Ontology took 0.3686807155609131s
Currency | Modification date check for 3LGM² IHE Ontology took 0.36157822608947754s
Rep.Conc. | URIs length for 3LGM² IHE Ontology took 0.8097338676452637s
Interoperability | New vocabularies check for 3LGM² IHE Ontology took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for 3LGM² IHE Ontology took 0.16990089416503906s
Accuracy | Check Functional Property for 3LGM² IHE Ontology took 0.17776942253112793s
Accuracy | Check Inverse Functional Property for 3LGM² IHE Ontology took 0.18694829940795898s
Accuracy | Check Empty annotation labels for 3LGM² IHE Ontology took 0.322908878326416s
Accuracy | Check White space in annotation for 3LGM² IHE Ontology took 0.001552581787109375s
Accuracy | Check Datatype consistency for 3LGM² IHE Ontology took 0.050943613052368164s
Consistency | Disjoint class check for 3LGM² IHE Ontology took 0.1867673397064209s
Consistency | Check Misplaced properties for 3LGM² IHE Ontology took 0.4129679203033447s
Consistency | Misplaced classes for 3LGM² IHE Ontology took 0.2743258476257324s
Consistency | Check Ontology hijacking for 3LGM² IHE Ontology took 1.5833520889282227s
Consistency | Check Invalid usage of undefined classes for 3LGM² IHE Ontology took 1.3255343437194824s
Consistency | Check Invalid usage of undefined properties for 3LGM² IHE Ontology took 1.538771390914917s
Conciseness | Check Extensional conciseness for 3LGM² IHE Ontology took 0.031736135482788086s
Conciseness | Check Intensional conciseness for 3LGM² IHE Ontology took 0.17136001586914062s
Security | Sign check for 3LGM² IHE Ontology took 0.18034911155700684s
Availability | Check URIs Dereferenciability for 3LGM² IHE Ontology took 365.6550967693329s
Completeness | Calculation of interlinking completeness for 3LGM² IHE Ontology took 0.3678441047668457s
Reputation | Calculation of the PageRank for 3LGM² IHE Ontology took 0.020769596099853516s
Interlinking | Calculation of Degree of Connection for 3LGM² IHE Ontology took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for 3LGM² IHE Ontology took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for 3LGM² IHE Ontology took 4.1484832763671875e-05s
Interoperability | Check the re-using of existing vocabs for 3LGM² IHE Ontology took 1.6689300537109375e-06s
Believability | Calculation of trust value for 3LGM² IHE Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for IHE took 410.89531564712524s
Availability | SPARQL endpoint availability check for Test Site, LOD Lab 317 took 2.5836105346679688s
Availability | VoID file availability check for Test Site, LOD Lab 317 took 0.0003428459167480469s
Extra | Recovery of all triples for Test Site, LOD Lab 317 took 10.674095392227173s
Performance | Total latancy measurement for Test Site, LOD Lab 317 took 7.959522485733032s
Amount of data | Number of triples check for Test Site, LOD Lab 317 took 15.961948871612549s
Interoperability | New terms check for Test Site, LOD Lab 317 took 8.861558675765991s
Versatility | Languages check for Test Site, LOD Lab 317 took 61.583500623703s
Interpretability | Number of blank nodes check for Test Site, LOD Lab 317 took 1.7908408641815186s
Security | Check HTTPS for Test Site, LOD Lab 317 took 1.0916876792907715s
Interpretability | RDF structures check for Test Site, LOD Lab 317 took 2.0337588787078857s
Versatility | Serialization formats check for Test Site, LOD Lab 317 took 1.8551814556121826s
Availability | RDF dump link check for Test Site, LOD Lab 317 took 1.6181552410125732s
License | MR license check for Test Site, LOD Lab 317 took 1.7232434749603271s
License | HR license check for Test Site, LOD Lab 317 took 1.9508113861083984s
Amount of data | Number of property check for Test Site, LOD Lab 317 took 1.7283515930175781s
Understandability | Number of label check for Test Site, LOD Lab 317 took 1.9912822246551514s
Understandability | URI regex check for Test Site, LOD Lab 317 took 3.230465888977051s
Understandability | Vocabs check for Test Site, LOD Lab 317 took 1.6461093425750732s
Verifiability | Authors check for Test Site, LOD Lab 317 took 1.70682954788208s
Verifiability | Publishers check for Test Site, LOD Lab 317 took 1.6278088092803955s
Performance | Throughput check for Test Site, LOD Lab 317 took 15.857326030731201s
Amount of data | Check the number of entities for Test Site, LOD Lab 317 took 6.866455078125e-05s
Verifiability | Contribs. check for Test Site, LOD Lab 317 took 1.6101412773132324s
Interlinking | sameAs chians check for Test Site, LOD Lab 317 took 1.6098432540893555s
Interlinking | skos check for Test Site, LOD Lab 317 took 1.9591176509857178s
Interlinking | skos check for Test Site, LOD Lab 317 took 1.6223843097686768s
Timeliness | dataset update frequency check for Test Site, LOD Lab 317 took 1.7528069019317627s
Currency | Creation date check for Test Site, LOD Lab 317 took 3.2272651195526123s
Currency | Modification date check for Test Site, LOD Lab 317 took 3.238643169403076s
Rep.Conc. | URIs length for Test Site, LOD Lab 317 took 41.49031853675842s
Interoperability | New vocabularies check for Test Site, LOD Lab 317 took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Test Site, LOD Lab 317 took 1.6069097518920898s
Accuracy | Check Functional Property for Test Site, LOD Lab 317 took 1.588332176208496s
Accuracy | Check Inverse Functional Property for Test Site, LOD Lab 317 took 1.6031172275543213s
Accuracy | Check Empty annotation labels for Test Site, LOD Lab 317 took 6.799662828445435s
Accuracy | Check White space in annotation for Test Site, LOD Lab 317 took 0.029979228973388672s
Accuracy | Check Datatype consistency for Test Site, LOD Lab 317 took 0.02816629409790039s
Consistency | Disjoint class check for Test Site, LOD Lab 317 took 1.5967767238616943s
Consistency | Check Misplaced properties for Test Site, LOD Lab 317 took 25.31731867790222s
Consistency | Misplaced classes for Test Site, LOD Lab 317 took 2.1511337757110596s
Consistency | Check Ontology hijacking for Test Site, LOD Lab 317 took 7.516968250274658s
Consistency | Check Invalid usage of undefined classes for Test Site, LOD Lab 317 took 1.3123373985290527s
Consistency | Check Invalid usage of undefined properties for Test Site, LOD Lab 317 took 24.20759630203247s
Conciseness | Check Extensional conciseness for Test Site, LOD Lab 317 took 0.03260612487792969s
Conciseness | Check Intensional conciseness for Test Site, LOD Lab 317 took 2.155292272567749s
Security | Sign check for Test Site, LOD Lab 317 took 1.7265260219573975s
Availability | Check URIs Dereferenciability for Test Site, LOD Lab 317 took 9.032634735107422s
Completeness | Calculation of interlinking completeness for Test Site, LOD Lab 317 took 0.3105771541595459s
Reputation | Calculation of the PageRank for Test Site, LOD Lab 317 took 0.0225985050201416s
Interlinking | Calculation of Degree of Connection for Test Site, LOD Lab 317 took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Test Site, LOD Lab 317 took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Test Site, LOD Lab 317 took 4.482269287109375e-05s
Interoperability | Check the re-using of existing vocabs for Test Site, LOD Lab 317 took 1.1920928955078125e-06s
Believability | Calculation of trust value for Test Site, LOD Lab 317 took 1.1205673217773438e-05s
INFO | --- Analysis for iislod-test took 506.7495095729828s
Availability | SPARQL endpoint availability check for Interpretation of Land Use Data in Ordos City took 4.410743713378906e-05s
Availability | VoID file availability check for Interpretation of Land Use Data in Ordos City took 0.0006420612335205078s
Completeness | Calculation of interlinking completeness for Interpretation of Land Use Data in Ordos City took 0.270965576171875s
Reputation | Calculation of the PageRank for Interpretation of Land Use Data in Ordos City took 0.021791696548461914s
Interlinking | Calculation of Degree of Connection for Interpretation of Land Use Data in Ordos City took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Interpretation of Land Use Data in Ordos City took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Interpretation of Land Use Data in Ordos City took 3.0994415283203125e-05s
Believability | Calculation of trust value for Interpretation of Land Use Data in Ordos City took 1.1682510375976562e-05s
INFO | --- Analysis for ILUSOC took 18.521588563919067s
Availability | SPARQL endpoint availability check for im@sparql took 7.121270179748535s
Availability | VoID file availability check for im@sparql took 0.0007619857788085938s
Completeness | Calculation of interlinking completeness for im@sparql took 0.26912832260131836s
Reputation | Calculation of the PageRank for im@sparql took 0.020588397979736328s
Interlinking | Calculation of Degree of Connection for im@sparql took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for im@sparql took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for im@sparql took 2.9087066650390625e-05s
Believability | Calculation of trust value for im@sparql took 1.239776611328125e-05s
INFO | --- Analysis for im@sparql took 13.825815916061401s
Availability | SPARQL endpoint availability check for imagery bailingniao took 8.916854858398438e-05s
Availability | VoID file availability check for imagery bailingniao took 0.0006368160247802734s
Completeness | Calculation of interlinking completeness for imagery bailingniao took 0.26902127265930176s
Reputation | Calculation of the PageRank for imagery bailingniao took 0.020543575286865234s
Interlinking | Calculation of Degree of Connection for imagery bailingniao took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for imagery bailingniao took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for imagery bailingniao took 3.1948089599609375e-05s
Believability | Calculation of trust value for imagery bailingniao took 1.3113021850585938e-05s
INFO | --- Analysis for imagery_bailingniao took 3.7231192588806152s
Availability | SPARQL endpoint availability check for Imagesnippets Image Descriptions took 1.0595753192901611s
Availability | VoID file availability check for Imagesnippets Image Descriptions took 0.0006914138793945312s
Extra | Recovery of all triples for Imagesnippets Image Descriptions took 44.77423882484436s
Performance | Total latancy measurement for Imagesnippets Image Descriptions took 3.3935868740081787s
Amount of data | Number of triples check for Imagesnippets Image Descriptions took 10.548082828521729s
Interoperability | New terms check for Imagesnippets Image Descriptions took 3.3982632160186768s
Versatility | Languages check for Imagesnippets Image Descriptions took 20.314133167266846s
Interpretability | Number of blank nodes check for Imagesnippets Image Descriptions took 8.319430828094482s
Security | Check HTTPS for Imagesnippets Image Descriptions took 0.6605744361877441s
Interpretability | RDF structures check for Imagesnippets Image Descriptions took 0.7074770927429199s
Versatility | Serialization formats check for Imagesnippets Image Descriptions took 0.6961946487426758s
Availability | RDF dump link check for Imagesnippets Image Descriptions took 0.733095645904541s
License | MR license check for Imagesnippets Image Descriptions took 0.7011709213256836s
License | HR license check for Imagesnippets Image Descriptions took 30.715166330337524s
Amount of data | Number of property check for Imagesnippets Image Descriptions took 0.7013809680938721s
Understandability | Number of label check for Imagesnippets Image Descriptions took 2.604142904281616s
Understandability | URI regex check for Imagesnippets Image Descriptions took 1.3784079551696777s
Understandability | Vocabs check for Imagesnippets Image Descriptions took 0.6906156539916992s
Verifiability | Authors check for Imagesnippets Image Descriptions took 0.6914308071136475s
Verifiability | Publishers check for Imagesnippets Image Descriptions took 0.6791515350341797s
Performance | Throughput check for Imagesnippets Image Descriptions took 13.380699634552002s
Amount of data | Check the number of entities for Imagesnippets Image Descriptions took 6.628036499023438e-05s
Verifiability | Contribs. check for Imagesnippets Image Descriptions took 0.6788632869720459s
Interlinking | sameAs chians check for Imagesnippets Image Descriptions took 0.6942565441131592s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.6968367099761963s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.663231611251831s
Timeliness | dataset update frequency check for Imagesnippets Image Descriptions took 0.7114372253417969s
Currency | Creation date check for Imagesnippets Image Descriptions took 1.398280143737793s
Currency | Modification date check for Imagesnippets Image Descriptions took 1.3905136585235596s
Rep.Conc. | URIs length for Imagesnippets Image Descriptions took 51.69021272659302s
Interoperability | New vocabularies check for Imagesnippets Image Descriptions took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Imagesnippets Image Descriptions took 0.7013771533966064s
Accuracy | Check Functional Property for Imagesnippets Image Descriptions took 0.6757612228393555s
Accuracy | Check Inverse Functional Property for Imagesnippets Image Descriptions took 0.6810760498046875s
Consistency | Disjoint class check for Imagesnippets Image Descriptions took 0.683619499206543s
Consistency | Check Misplaced properties for Imagesnippets Image Descriptions took 8.48700475692749s
Consistency | Check Ontology hijacking for Imagesnippets Image Descriptions took 17.64261221885681s
Consistency | Check Invalid usage of undefined properties for Imagesnippets Image Descriptions took 8.651139736175537s
Conciseness | Check Extensional conciseness for Imagesnippets Image Descriptions took 0.0001850128173828125s
Security | Sign check for Imagesnippets Image Descriptions took 0.7047770023345947s
Completeness | Calculation of interlinking completeness for Imagesnippets Image Descriptions took 0.3430802822113037s
Reputation | Calculation of the PageRank for Imagesnippets Image Descriptions took 0.02097940444946289s
Interlinking | Calculation of Degree of Connection for Imagesnippets Image Descriptions took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Imagesnippets Image Descriptions took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Imagesnippets Image Descriptions took 9.322166442871094e-05s
Interoperability | Check the re-using of existing vocabs for Imagesnippets Image Descriptions took 1.6689300537109375e-06s
Believability | Calculation of trust value for Imagesnippets Image Descriptions took 1.0728836059570312e-05s
INFO | --- Analysis for imagesnippets took 439.7141737937927s
Availability | SPARQL endpoint availability check for International Monetary Fund (IMF) Linked Data took 0.08986854553222656s
Availability | VoID file availability check for International Monetary Fund (IMF) Linked Data took 0.00038051605224609375s
Completeness | Calculation of interlinking completeness for International Monetary Fund (IMF) Linked Data took 0.2866199016571045s
Reputation | Calculation of the PageRank for International Monetary Fund (IMF) Linked Data took 0.020865201950073242s
Interlinking | Calculation of Degree of Connection for International Monetary Fund (IMF) Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for International Monetary Fund (IMF) Linked Data took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for International Monetary Fund (IMF) Linked Data took 8.654594421386719e-05s
Believability | Calculation of trust value for International Monetary Fund (IMF) Linked Data took 1.2636184692382812e-05s
INFO | --- Analysis for imf-linked-data took 2.580979108810425s
Availability | SPARQL endpoint availability check for MD Imtiaz Ahammad took 8.463859558105469e-05s
Availability | VoID file availability check for MD Imtiaz Ahammad took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for MD Imtiaz Ahammad took 0.27421140670776367s
Reputation | Calculation of the PageRank for MD Imtiaz Ahammad took 0.02075791358947754s
Interlinking | Calculation of Degree of Connection for MD Imtiaz Ahammad took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for MD Imtiaz Ahammad took 0.0009918212890625s
Interlinking | Calculation of Clustering coefficient for MD Imtiaz Ahammad took 1.4781951904296875e-05s
Believability | Calculation of trust value for MD Imtiaz Ahammad took 1.1682510375976562e-05s
INFO | --- Analysis for Imtiaz took 2.5321695804595947s
Availability | SPARQL endpoint availability check for Royalty Free Music took 0.0005609989166259766s
Availability | VoID file availability check for Royalty Free Music took 0.0007648468017578125s
Completeness | Calculation of interlinking completeness for Royalty Free Music took 0.2799496650695801s
Reputation | Calculation of the PageRank for Royalty Free Music took 0.020586490631103516s
Interlinking | Calculation of Degree of Connection for Royalty Free Music took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Royalty Free Music took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Royalty Free Music took 3.0994415283203125e-05s
Believability | Calculation of trust value for Royalty Free Music took 1.0013580322265625e-05s
INFO | --- Analysis for inaudio.org took 3.9056193828582764s
Availability | SPARQL endpoint availability check for Index Thomisticus Treebank in LiLa took 0.48160886764526367s
Availability | VoID file availability check for Index Thomisticus Treebank in LiLa took 0.0008223056793212891s
Completeness | Calculation of interlinking completeness for Index Thomisticus Treebank in LiLa took 0.2658247947692871s
Reputation | Calculation of the PageRank for Index Thomisticus Treebank in LiLa took 0.02086496353149414s
Interlinking | Calculation of Degree of Connection for Index Thomisticus Treebank in LiLa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Index Thomisticus Treebank in LiLa took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Index Thomisticus Treebank in LiLa took 3.8623809814453125e-05s
Believability | Calculation of trust value for Index Thomisticus Treebank in LiLa took 1.2874603271484375e-05s
INFO | --- Analysis for IndexThomisticusTreebank took 4.042173147201538s
Availability | SPARQL endpoint availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.0001010894775390625s
Availability | VoID file availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.0007431507110595703s
Completeness | Calculation of interlinking completeness for IneveryCREA, la comunidad de la creatividad educativa took 0.27709245681762695s
Reputation | Calculation of the PageRank for IneveryCREA, la comunidad de la creatividad educativa took 0.020336627960205078s
Interlinking | Calculation of Degree of Connection for IneveryCREA, la comunidad de la creatividad educativa took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for IneveryCREA, la comunidad de la creatividad educativa took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for IneveryCREA, la comunidad de la creatividad educativa took 0.00010418891906738281s
Believability | Calculation of trust value for IneveryCREA, la comunidad de la creatividad educativa took 1.2159347534179688e-05s
INFO | --- Analysis for ineverycrea took 15.046841859817505s
Availability | SPARQL endpoint availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 8.702278137207031e-05s
Availability | VoID file availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0008034706115722656s
Completeness | Calculation of interlinking completeness for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.27147579193115234s
Reputation | Calculation of the PageRank for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.020841360092163086s
Interlinking | Calculation of Degree of Connection for IneveryCREA Argentina, la comunidad de la creatividad educativa took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for IneveryCREA Argentina, la comunidad de la creatividad educativa took 9.250640869140625e-05s
Believability | Calculation of trust value for IneveryCREA Argentina, la comunidad de la creatividad educativa took 1.3113021850585938e-05s
INFO | --- Analysis for ineverycrea-argentina took 7.681833982467651s
Availability | SPARQL endpoint availability check for Influence Tracker Dataset took 272.29143047332764s
Availability | VoID file availability check for Influence Tracker Dataset took 0.0005986690521240234s
Completeness | Calculation of interlinking completeness for Influence Tracker Dataset took 0.27369236946105957s
Reputation | Calculation of the PageRank for Influence Tracker Dataset took 0.021065711975097656s
Interlinking | Calculation of Degree of Connection for Influence Tracker Dataset took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Influence Tracker Dataset took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Influence Tracker Dataset took 8.153915405273438e-05s
Believability | Calculation of trust value for Influence Tracker Dataset took 2.5510787963867188e-05s
INFO | --- Analysis for influence-tracker-dataset took 557.6774821281433s
Availability | SPARQL endpoint availability check for Instance Hub Fiscal Years took 4.1484832763671875e-05s
Availability | VoID file availability check for Instance Hub Fiscal Years took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for Instance Hub Fiscal Years took 0.28656983375549316s
Reputation | Calculation of the PageRank for Instance Hub Fiscal Years took 0.02086019515991211s
Interlinking | Calculation of Degree of Connection for Instance Hub Fiscal Years took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Instance Hub Fiscal Years took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Instance Hub Fiscal Years took 3.62396240234375e-05s
Believability | Calculation of trust value for Instance Hub Fiscal Years took 7.152557373046875e-06s
INFO | --- Analysis for instance-hub-fiscal-years took 2.712129831314087s
Availability | SPARQL endpoint availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 8.630752563476562e-05s
Availability | VoID file availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0006725788116455078s
Completeness | Calculation of interlinking completeness for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.28771257400512695s
Reputation | Calculation of the PageRank for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.02064228057861328s
Interlinking | Calculation of Degree of Connection for Interactive Maps, a collection of interactive flash maps (GNOSS) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.00010037422180175781s
Believability | Calculation of trust value for Interactive Maps, a collection of interactive flash maps (GNOSS) took 9.775161743164062e-06s
INFO | --- Analysis for interactivemaps-gnoss took 15.661331415176392s
Availability | SPARQL endpoint availability check for intervalue took 1.0272068977355957s
Availability | VoID file availability check for intervalue took 0.00022864341735839844s
Completeness | Calculation of interlinking completeness for intervalue took 0.26665449142456055s
Reputation | Calculation of the PageRank for intervalue took 0.02068471908569336s
Interlinking | Calculation of Degree of Connection for intervalue took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for intervalue took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for intervalue took 6.771087646484375e-05s
Believability | Calculation of trust value for intervalue took 1.1920928955078125e-05s
INFO | --- Analysis for intervalue took 3.5656042098999023s
Availability | SPARQL endpoint availability check for Inztrow took 8.487701416015625e-05s
Availability | VoID file availability check for Inztrow took 0.0006144046783447266s
Completeness | Calculation of interlinking completeness for Inztrow took 0.2758004665374756s
Reputation | Calculation of the PageRank for Inztrow took 0.020526409149169922s
Interlinking | Calculation of Degree of Connection for Inztrow took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Inztrow took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Inztrow took 3.24249267578125e-05s
Believability | Calculation of trust value for Inztrow took 1.0967254638671875e-05s
INFO | --- Analysis for Inztrow took 3.672578811645508s
Availability | SPARQL endpoint availability check for IPBES Assessments Ontology took 8.606910705566406e-05s
Availability | VoID file availability check for IPBES Assessments Ontology took 0.0006210803985595703s
Completeness | Calculation of interlinking completeness for IPBES Assessments Ontology took 0.27462339401245117s
Reputation | Calculation of the PageRank for IPBES Assessments Ontology took 0.020519018173217773s
Interlinking | Calculation of Degree of Connection for IPBES Assessments Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for IPBES Assessments Ontology took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for IPBES Assessments Ontology took 3.24249267578125e-05s
Believability | Calculation of trust value for IPBES Assessments Ontology took 9.775161743164062e-06s
INFO | --- Analysis for ipbes took 3.9522275924682617s
Availability | SPARQL endpoint availability check for IPTC NewsCodes took 4.291534423828125e-05s
Availability | VoID file availability check for IPTC NewsCodes took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for IPTC NewsCodes took 0.26764488220214844s
Reputation | Calculation of the PageRank for IPTC NewsCodes took 0.02078390121459961s
Interlinking | Calculation of Degree of Connection for IPTC NewsCodes took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for IPTC NewsCodes took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for IPTC NewsCodes took 4.57763671875e-05s
Believability | Calculation of trust value for IPTC NewsCodes took 1.0013580322265625e-05s
INFO | --- Analysis for iptc-newscodes took 3.3853580951690674s
Availability | SPARQL endpoint availability check for iServe: Linked Services Registry took 1.7195470333099365s
Availability | VoID file availability check for iServe: Linked Services Registry took 0.0012848377227783203s
Completeness | Calculation of interlinking completeness for iServe: Linked Services Registry took 0.26574134826660156s
Reputation | Calculation of the PageRank for iServe: Linked Services Registry took 0.020387887954711914s
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.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for iServe: Linked Services Registry took 9.608268737792969e-05s
Believability | Calculation of trust value for iServe: Linked Services Registry took 9.5367431640625e-06s
INFO | --- Analysis for iserve took 6.519794702529907s
Availability | SPARQL endpoint availability check for ISIC V4 took 21.200982332229614s
Availability | VoID file availability check for ISIC V4 took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for ISIC V4 took 0.2734410762786865s
Reputation | Calculation of the PageRank for ISIC V4 took 0.020668983459472656s
Interlinking | Calculation of Degree of Connection for ISIC V4 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ISIC V4 took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for ISIC V4 took 4.5299530029296875e-05s
Believability | Calculation of trust value for ISIC V4 took 8.821487426757812e-06s
INFO | --- Analysis for isic-v4 took 115.44039559364319s
Availability | SPARQL endpoint availability check for ISIL->DBpedia took 8.821487426757812e-05s
Availability | VoID file availability check for ISIL->DBpedia took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for ISIL->DBpedia took 0.2628011703491211s
Reputation | Calculation of the PageRank for ISIL->DBpedia took 0.020264625549316406s
Interlinking | Calculation of Degree of Connection for ISIL->DBpedia took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ISIL->DBpedia took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for ISIL->DBpedia took 6.67572021484375e-05s
Believability | Calculation of trust value for ISIL->DBpedia took 9.059906005859375e-06s
INFO | --- Analysis for isil-dbpedia took 4.07456636428833s
Availability | SPARQL endpoint availability check for Published subjects for languages in ISO 639 took 8.726119995117188e-05s
Availability | VoID file availability check for Published subjects for languages in ISO 639 took 0.0004978179931640625s
Completeness | Calculation of interlinking completeness for Published subjects for languages in ISO 639 took 0.27191710472106934s
Reputation | Calculation of the PageRank for Published subjects for languages in ISO 639 took 0.020849943161010742s
Interlinking | Calculation of Degree of Connection for Published subjects for languages in ISO 639 took 6.937980651855469e-05s
Interlinking | Calculation of Centrality for Published subjects for languages in ISO 639 took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Published subjects for languages in ISO 639 took 3.3855438232421875e-05s
Believability | Calculation of trust value for Published subjects for languages in ISO 639 took 1.049041748046875e-05s
INFO | --- Analysis for iso-639-oasis took 3.1604666709899902s
Availability | SPARQL endpoint availability check for ISOcat took 8.749961853027344e-05s
Availability | VoID file availability check for ISOcat took 0.0006096363067626953s
Completeness | Calculation of interlinking completeness for ISOcat took 0.2686910629272461s
Reputation | Calculation of the PageRank for ISOcat took 0.020813465118408203s
Interlinking | Calculation of Degree of Connection for ISOcat took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for ISOcat took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for ISOcat took 6.67572021484375e-05s
Believability | Calculation of trust value for ISOcat took 1.049041748046875e-05s
INFO | --- Analysis for isocat took 33.11950492858887s
Availability | SPARQL endpoint availability check for ISOcat-metadata took 8.320808410644531e-05s
Availability | VoID file availability check for ISOcat-metadata took 0.0007176399230957031s
Completeness | Calculation of interlinking completeness for ISOcat-metadata took 0.27538490295410156s
Reputation | Calculation of the PageRank for ISOcat-metadata took 0.02026224136352539s
Interlinking | Calculation of Degree of Connection for ISOcat-metadata took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ISOcat-metadata took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for ISOcat-metadata took 3.314018249511719e-05s
Believability | Calculation of trust value for ISOcat-metadata took 1.1920928955078125e-05s
INFO | --- Analysis for isocat-metadata took 32.727763414382935s
Availability | SPARQL endpoint availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.9167890548706055s
Availability | VoID file availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.000545501708984375s
Extra | Recovery of all triples for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 6.5480568408966064s
Performance | Total latancy measurement for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3564162254333496s
Amount of data | Number of triples check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1441364288330078s
Interoperability | New terms check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.925057888031006s
Versatility | Languages check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 90.47930121421814s
Interpretability | Number of blank nodes check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.07713723182678223s
Security | Check HTTPS for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.04618048667907715s
Interpretability | RDF structures check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09932947158813477s
Versatility | Serialization formats check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09924459457397461s
Availability | RDF dump link check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08692431449890137s
License | MR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.12893295288085938s
License | HR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 92.96250200271606s
Amount of data | Number of property check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08139419555664062s
Understandability | Number of label check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.4274461269378662s
Understandability | URI regex check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.30205368995666504s
Understandability | Vocabs check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.13295459747314453s
Verifiability | Authors check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.13926219940185547s
Verifiability | Publishers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.07877469062805176s
Performance | Throughput check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.300037384033203s
Amount of data | Check the number of entities for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 6.890296936035156e-05s
Verifiability | Contribs. check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.12447190284729004s
Interlinking | sameAs chians check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.20009231567382812s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.4451444149017334s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.4140584468841553s
Timeliness | dataset update frequency check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1293506622314453s
Currency | Creation date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.15649747848510742s
Currency | Modification date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08046507835388184s
Rep.Conc. | URIs length for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 13.290099620819092s
Interoperability | New vocabularies check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.07761812210083008s
Accuracy | Check Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08178472518920898s
Accuracy | Check Inverse Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08054256439208984s
Accuracy | Check Empty annotation labels for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 3.4358010292053223s
Accuracy | Check White space in annotation for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3148016929626465s
Accuracy | Check Datatype consistency for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2601611614227295s
Consistency | Disjoint class check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.10273528099060059s
Consistency | Check Misplaced properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 8.860964059829712s
Consistency | Misplaced classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.8868587017059326s
Consistency | Check Ontology hijacking for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 3.364328384399414s
Consistency | Check Invalid usage of undefined classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.3371937274932861s
Consistency | Check Invalid usage of undefined properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.144757986068726s
Conciseness | Check Extensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2855989933013916s
Conciseness | Check Intensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08777284622192383s
Security | Sign check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.10320782661437988s
Availability | Check URIs Dereferenciability for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.38743257522583s
Completeness | Calculation of interlinking completeness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3435094356536865s
Reputation | Calculation of the PageRank for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.021108150482177734s
Interlinking | Calculation of Degree of Connection for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.441375732421875e-05s
Interoperability | Check the re-using of existing vocabs for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.6689300537109375e-06s
Believability | Calculation of trust value for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.6927719116210938e-05s
INFO | --- Analysis for ispra-lod-place took 448.4856176376343s
Availability | SPARQL endpoint availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.05251359939575195s
Availability | VoID file availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.0004978179931640625s
Extra | Recovery of all triples for ISPRA - The Italian Data Buoy Network (RON) took 6.384628772735596s
Performance | Total latancy measurement for ISPRA - The Italian Data Buoy Network (RON) took 0.2960526943206787s
Amount of data | Number of triples check for ISPRA - The Italian Data Buoy Network (RON) took 0.13793635368347168s
Interoperability | New terms check for ISPRA - The Italian Data Buoy Network (RON) took 2.9319756031036377s
Versatility | Languages check for ISPRA - The Italian Data Buoy Network (RON) took 92.99923968315125s
Interpretability | Number of blank nodes check for ISPRA - The Italian Data Buoy Network (RON) took 0.0760185718536377s
Security | Check HTTPS for ISPRA - The Italian Data Buoy Network (RON) took 0.0320284366607666s
Interpretability | RDF structures check for ISPRA - The Italian Data Buoy Network (RON) took 0.09742403030395508s
Versatility | Serialization formats check for ISPRA - The Italian Data Buoy Network (RON) took 0.09345555305480957s
Availability | RDF dump link check for ISPRA - The Italian Data Buoy Network (RON) took 0.08099961280822754s
License | MR license check for ISPRA - The Italian Data Buoy Network (RON) took 0.15343928337097168s
License | HR license check for ISPRA - The Italian Data Buoy Network (RON) took 91.94679689407349s
Amount of data | Number of property check for ISPRA - The Italian Data Buoy Network (RON) took 0.07835841178894043s
Understandability | Number of label check for ISPRA - The Italian Data Buoy Network (RON) took 1.1657342910766602s
Understandability | URI regex check for ISPRA - The Italian Data Buoy Network (RON) took 0.28346681594848633s
Understandability | Vocabs check for ISPRA - The Italian Data Buoy Network (RON) took 0.3380262851715088s
Verifiability | Authors check for ISPRA - The Italian Data Buoy Network (RON) took 0.144547700881958s
Verifiability | Publishers check for ISPRA - The Italian Data Buoy Network (RON) took 0.07560396194458008s
Performance | Throughput check for ISPRA - The Italian Data Buoy Network (RON) took 10.448593854904175s
Amount of data | Check the number of entities for ISPRA - The Italian Data Buoy Network (RON) took 8.177757263183594e-05s
Verifiability | Contribs. check for ISPRA - The Italian Data Buoy Network (RON) took 0.1484227180480957s
Interlinking | sameAs chians check for ISPRA - The Italian Data Buoy Network (RON) took 0.20873570442199707s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.4121556282043457s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.3913075923919678s
Timeliness | dataset update frequency check for ISPRA - The Italian Data Buoy Network (RON) took 0.12832212448120117s
Currency | Creation date check for ISPRA - The Italian Data Buoy Network (RON) took 0.15343046188354492s
Currency | Modification date check for ISPRA - The Italian Data Buoy Network (RON) took 0.07729363441467285s
Rep.Conc. | URIs length for ISPRA - The Italian Data Buoy Network (RON) took 13.3767249584198s
Interoperability | New vocabularies check for ISPRA - The Italian Data Buoy Network (RON) took 6.9141387939453125e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The Italian Data Buoy Network (RON) took 0.07854390144348145s
Accuracy | Check Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.10031366348266602s
Accuracy | Check Inverse Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.09276318550109863s
Accuracy | Check Empty annotation labels for ISPRA - The Italian Data Buoy Network (RON) took 3.2089614868164062s
Accuracy | Check White space in annotation for ISPRA - The Italian Data Buoy Network (RON) took 0.30341553688049316s
Accuracy | Check Datatype consistency for ISPRA - The Italian Data Buoy Network (RON) took 0.2634432315826416s
Consistency | Disjoint class check for ISPRA - The Italian Data Buoy Network (RON) took 0.07211923599243164s
Consistency | Check Misplaced properties for ISPRA - The Italian Data Buoy Network (RON) took 8.941868543624878s
Consistency | Misplaced classes for ISPRA - The Italian Data Buoy Network (RON) took 0.8857085704803467s
Consistency | Check Ontology hijacking for ISPRA - The Italian Data Buoy Network (RON) took 3.3322532176971436s
Consistency | Check Invalid usage of undefined classes for ISPRA - The Italian Data Buoy Network (RON) took 1.3365707397460938s
Consistency | Check Invalid usage of undefined properties for ISPRA - The Italian Data Buoy Network (RON) took 10.09403657913208s
Conciseness | Check Extensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.2935044765472412s
Conciseness | Check Intensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.0865929126739502s
Security | Sign check for ISPRA - The Italian Data Buoy Network (RON) took 0.09507465362548828s
Availability | Check URIs Dereferenciability for ISPRA - The Italian Data Buoy Network (RON) took 7.9780638217926025s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian Data Buoy Network (RON) took 0.35141515731811523s
Reputation | Calculation of the PageRank for ISPRA - The Italian Data Buoy Network (RON) took 0.021001815795898438s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian Data Buoy Network (RON) took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian Data Buoy Network (RON) took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian Data Buoy Network (RON) took 3.24249267578125e-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 1.33514404296875e-05s
INFO | --- Analysis for ispra-lod-ron took 444.16208243370056s
Availability | SPARQL endpoint availability check for ISSA Agritrop Dataset took 0.6611588001251221s
Availability | VoID file availability check for ISSA Agritrop Dataset took 0.0007326602935791016s
Completeness | Calculation of interlinking completeness for ISSA Agritrop Dataset took 0.26405763626098633s
Reputation | Calculation of the PageRank for ISSA Agritrop Dataset took 0.02178812026977539s
Interlinking | Calculation of Degree of Connection for ISSA Agritrop Dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ISSA Agritrop Dataset took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for ISSA Agritrop Dataset took 9.298324584960938e-05s
Believability | Calculation of trust value for ISSA Agritrop Dataset took 1.1920928955078125e-05s
INFO | --- Analysis for issa-agritrop took 4.849761247634888s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.291534423828125e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.2717323303222656s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.020387649536132812s
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.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 2.8371810913085938e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 1.0251998901367188e-05s
INFO | --- Analysis for ISSN:0080-3626 took 2.5385186672210693s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 0.00010848045349121094s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.28079938888549805s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.020685195922851562s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0010955333709716797s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 4.76837158203125e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 1.2874603271484375e-05s
INFO | --- Analysis for ISSN:_0080-3626 took 2.808878183364868s
Availability | SPARQL endpoint availability check for Aktualne zagadnienia klasyfikacji map took 8.7738037109375e-05s
Availability | VoID file availability check for Aktualne zagadnienia klasyfikacji map took 0.0005772113800048828s
Completeness | Calculation of interlinking completeness for Aktualne zagadnienia klasyfikacji map took 0.3642144203186035s
Reputation | Calculation of the PageRank for Aktualne zagadnienia klasyfikacji map took 0.02140522003173828s
Interlinking | Calculation of Degree of Connection for Aktualne zagadnienia klasyfikacji map took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Aktualne zagadnienia klasyfikacji map took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Aktualne zagadnienia klasyfikacji map took 2.9087066650390625e-05s
Believability | Calculation of trust value for Aktualne zagadnienia klasyfikacji map took 1.1920928955078125e-05s
INFO | --- Analysis for ISSN:_0080-3626. took 2.7059671878814697s
Availability | SPARQL endpoint availability check for ISTAT Immigration (LinkedOpenData.it) took 0.24167799949645996s
Availability | VoID file availability check for ISTAT Immigration (LinkedOpenData.it) took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for ISTAT Immigration (LinkedOpenData.it) took 0.2704765796661377s
Reputation | Calculation of the PageRank for ISTAT Immigration (LinkedOpenData.it) took 0.022721052169799805s
Interlinking | Calculation of Degree of Connection for ISTAT Immigration (LinkedOpenData.it) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ISTAT Immigration (LinkedOpenData.it) took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigration (LinkedOpenData.it) took 8.296966552734375e-05s
Believability | Calculation of trust value for ISTAT Immigration (LinkedOpenData.it) took 8.58306884765625e-06s
INFO | --- Analysis for istat-immigration took 2.7250583171844482s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Italian Republic took 0.19626498222351074s
Availability | VoID file availability check for List of prices of medicinal products marketed in Italian Republic took 0.0005435943603515625s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Italian Republic took 0.3174574375152588s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Italian Republic took 0.020296573638916016s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Italian Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Italian Republic took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Italian Republic took 3.0040740966796875e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Italian Republic took 8.58306884765625e-06s
INFO | --- Analysis for it-aifa-drug-prices took 3.0423381328582764s
Availability | SPARQL endpoint availability check for Italian public schools (LinkedOpenData.it) took 0.1804368495941162s
Availability | VoID file availability check for Italian public schools (LinkedOpenData.it) took 0.00042891502380371094s
Completeness | Calculation of interlinking completeness for Italian public schools (LinkedOpenData.it) took 0.2730252742767334s
Reputation | Calculation of the PageRank for Italian public schools (LinkedOpenData.it) took 0.02017831802368164s
Interlinking | Calculation of Degree of Connection for Italian public schools (LinkedOpenData.it) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Italian public schools (LinkedOpenData.it) took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Italian public schools (LinkedOpenData.it) took 7.05718994140625e-05s
Believability | Calculation of trust value for Italian public schools (LinkedOpenData.it) took 1.049041748046875e-05s
INFO | --- Analysis for italian-public-schools-linkedopendata-it took 2.6705658435821533s
Availability | SPARQL endpoint availability check for IWN took 8.726119995117188e-05s
Availability | VoID file availability check for IWN took 0.0005106925964355469s
Completeness | Calculation of interlinking completeness for IWN took 0.2784123420715332s
Reputation | Calculation of the PageRank for IWN took 0.02030777931213379s
Interlinking | Calculation of Degree of Connection for IWN took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IWN took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for IWN took 3.62396240234375e-05s
Believability | Calculation of trust value for IWN took 1.1920928955078125e-05s
INFO | --- Analysis for iwn took 5.919073581695557s
Availability | SPARQL endpoint availability check for DBTune.org Jamendo RDF Server took 5.762098073959351s
Availability | VoID file availability check for DBTune.org Jamendo RDF Server took 0.00074005126953125s
Completeness | Calculation of interlinking completeness for DBTune.org Jamendo RDF Server took 0.2729225158691406s
Reputation | Calculation of the PageRank for DBTune.org Jamendo RDF Server took 0.02069997787475586s
Interlinking | Calculation of Degree of Connection for DBTune.org Jamendo RDF Server took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBTune.org Jamendo RDF Server took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for DBTune.org Jamendo RDF Server took 6.151199340820312e-05s
Believability | Calculation of trust value for DBTune.org Jamendo RDF Server took 1.2159347534179688e-05s
INFO | --- Analysis for jamendo-dbtune took 10.734950065612793s
Availability | SPARQL endpoint availability check for National Radioactivity Stat as Linked Data took 8.654594421386719e-05s
Availability | VoID file availability check for National Radioactivity Stat as Linked Data took 0.0005877017974853516s
Completeness | Calculation of interlinking completeness for National Radioactivity Stat as Linked Data took 0.2736198902130127s
Reputation | Calculation of the PageRank for National Radioactivity Stat as Linked Data took 0.02068352699279785s
Interlinking | Calculation of Degree of Connection for National Radioactivity Stat as Linked Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for National Radioactivity Stat as Linked Data took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for National Radioactivity Stat as Linked Data took 4.696846008300781e-05s
Believability | Calculation of trust value for National Radioactivity Stat as Linked Data took 8.821487426757812e-06s
INFO | --- Analysis for japan-radioactivity-stat took 4.827711820602417s
Availability | SPARQL endpoint availability check for JEL Classification took 4.1961669921875e-05s
Availability | VoID file availability check for JEL Classification took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for JEL Classification took 0.2806699275970459s
Reputation | Calculation of the PageRank for JEL Classification took 0.020447254180908203s
Interlinking | Calculation of Degree of Connection for JEL Classification took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for JEL Classification took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for JEL Classification took 2.9325485229492188e-05s
Believability | Calculation of trust value for JEL Classification took 1.2636184692382812e-05s
INFO | --- Analysis for jel-classification took 4.556615352630615s
Availability | SPARQL endpoint availability check for JISC Open Bibliography British National Bibliography dataset took 1.1520495414733887s
Availability | VoID file availability check for JISC Open Bibliography British National Bibliography dataset took 0.0005326271057128906s
Completeness | Calculation of interlinking completeness for JISC Open Bibliography British National Bibliography dataset took 0.2734847068786621s
Reputation | Calculation of the PageRank for JISC Open Bibliography British National Bibliography dataset took 0.02075672149658203s
Interlinking | Calculation of Degree of Connection for JISC Open Bibliography British National Bibliography dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for JISC Open Bibliography British National Bibliography dataset took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for JISC Open Bibliography British National Bibliography dataset took 3.0279159545898438e-05s
Believability | Calculation of trust value for JISC Open Bibliography British National Bibliography dataset took 9.059906005859375e-06s
INFO | --- Analysis for jiscopenbib-bl_bnb-1 took 8.286779880523682s
Availability | SPARQL endpoint availability check for JITA Classification System of Library and Information Science took 261.1745309829712s
Availability | VoID file availability check for JITA Classification System of Library and Information Science took 0.0007014274597167969s
Completeness | Calculation of interlinking completeness for JITA Classification System of Library and Information Science took 0.31197476387023926s
Reputation | Calculation of the PageRank for JITA Classification System of Library and Information Science took 0.022647857666015625s
Interlinking | Calculation of Degree of Connection for JITA Classification System of Library and Information Science took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for JITA Classification System of Library and Information Science took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for JITA Classification System of Library and Information Science took 8.630752563476562e-05s
Believability | Calculation of trust value for JITA Classification System of Library and Information Science took 1.1205673217773438e-05s
INFO | --- Analysis for jita took 540.0854008197784s
Availability | SPARQL endpoint availability check for John Goodwin's Family Tree took 20.045408725738525s
Availability | VoID file availability check for John Goodwin's Family Tree took 0.0006606578826904297s
Completeness | Calculation of interlinking completeness for John Goodwin's Family Tree took 0.3224363327026367s
Reputation | Calculation of the PageRank for John Goodwin's Family Tree took 0.020682573318481445s
Interlinking | Calculation of Degree of Connection for John Goodwin's Family Tree took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for John Goodwin's Family Tree took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for John Goodwin's Family Tree took 9.679794311523438e-05s
Believability | Calculation of trust value for John Goodwin's Family Tree took 7.3909759521484375e-06s
INFO | --- Analysis for john-goodwins-family-tree took 62.6576132774353s
Availability | SPARQL endpoint availability check for Japanese Course of Study LOD took 4.172325134277344e-05s
Availability | VoID file availability check for Japanese Course of Study LOD took 0.0003955364227294922s
Completeness | Calculation of interlinking completeness for Japanese Course of Study LOD took 0.2676873207092285s
Reputation | Calculation of the PageRank for Japanese Course of Study LOD took 0.020672082901000977s
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.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Japanese Course of Study LOD took 3.4809112548828125e-05s
Believability | Calculation of trust value for Japanese Course of Study LOD took 6.198883056640625e-06s
INFO | --- Analysis for jp-cos took 4.5444769859313965s
Availability | SPARQL endpoint availability check for Japanese Textbook LOD took 4.172325134277344e-05s
Availability | VoID file availability check for Japanese Textbook LOD took 0.0004558563232421875s
Completeness | Calculation of interlinking completeness for Japanese Textbook LOD took 0.2583749294281006s
Reputation | Calculation of the PageRank for Japanese Textbook LOD took 0.02049875259399414s
Interlinking | Calculation of Degree of Connection for Japanese Textbook LOD took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Japanese Textbook LOD took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Japanese Textbook LOD took 3.910064697265625e-05s
Believability | Calculation of trust value for Japanese Textbook LOD took 6.4373016357421875e-06s
INFO | --- Analysis for jp-textbook took 4.166393756866455s
Availability | SPARQL endpoint availability check for JRC-Names took 4.100799560546875e-05s
Availability | VoID file availability check for JRC-Names took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for JRC-Names took 0.2570505142211914s
Reputation | Calculation of the PageRank for JRC-Names took 0.020528793334960938s
Interlinking | Calculation of Degree of Connection for JRC-Names took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for JRC-Names took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for JRC-Names took 3.314018249511719e-05s
Believability | Calculation of trust value for JRC-Names took 6.67572021484375e-06s
INFO | --- Analysis for jrc-names-ec took 4.586870908737183s
Availability | SPARQL endpoint availability check for JRC-Names-MLODE took 0.82769775390625s
Availability | VoID file availability check for JRC-Names-MLODE took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for JRC-Names-MLODE took 0.27909398078918457s
Reputation | Calculation of the PageRank for JRC-Names-MLODE took 0.020769834518432617s
Interlinking | Calculation of Degree of Connection for JRC-Names-MLODE took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for JRC-Names-MLODE took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for JRC-Names-MLODE took 6.890296936035156e-05s
Believability | Calculation of trust value for JRC-Names-MLODE took 1.0013580322265625e-05s
INFO | --- Analysis for jrc-names-mlode took 3.3912007808685303s
Availability | SPARQL endpoint availability check for JudaicaLink took 4.1961669921875e-05s
Availability | VoID file availability check for JudaicaLink took 0.00037789344787597656s
Completeness | Calculation of interlinking completeness for JudaicaLink took 0.266754150390625s
Reputation | Calculation of the PageRank for JudaicaLink took 0.02059197425842285s
Interlinking | Calculation of Degree of Connection for JudaicaLink took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for JudaicaLink took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for JudaicaLink took 9.989738464355469e-05s
Believability | Calculation of trust value for JudaicaLink took 5.9604644775390625e-06s
INFO | --- Analysis for judaicalink took 3.985100746154785s
Availability | SPARQL endpoint availability check for Kallikratis municipalities took 0.13031840324401855s
Availability | VoID file availability check for Kallikratis municipalities took 0.00045180320739746094s
Completeness | Calculation of interlinking completeness for Kallikratis municipalities took 0.26613807678222656s
Reputation | Calculation of the PageRank for Kallikratis municipalities took 0.021841764450073242s
Interlinking | Calculation of Degree of Connection for Kallikratis municipalities took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Kallikratis municipalities took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Kallikratis municipalities took 9.894371032714844e-05s
Believability | Calculation of trust value for Kallikratis municipalities took 8.821487426757812e-06s
INFO | --- Analysis for kallikratis-municipalities took 2.5493431091308594s
Availability | SPARQL endpoint availability check for EU Soccer League took 0.00011610984802246094s
Availability | VoID file availability check for EU Soccer League took 0.0003352165222167969s
Completeness | Calculation of interlinking completeness for EU Soccer League took 0.2562413215637207s
Reputation | Calculation of the PageRank for EU Soccer League took 0.02061772346496582s
Interlinking | Calculation of Degree of Connection for EU Soccer League took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EU Soccer League took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for EU Soccer League took 3.1948089599609375e-05s
Believability | Calculation of trust value for EU Soccer League took 5.4836273193359375e-06s
INFO | --- Analysis for KG:Course_Submission took 3.8805832862854004s
Availability | SPARQL endpoint availability check for Legal Knowledge Graph took 8.630752563476562e-05s
Availability | VoID file availability check for Legal Knowledge Graph took 0.0007107257843017578s
Completeness | Calculation of interlinking completeness for Legal Knowledge Graph took 0.2704014778137207s
Reputation | Calculation of the PageRank for Legal Knowledge Graph took 0.020461082458496094s
Interlinking | Calculation of Degree of Connection for Legal Knowledge Graph took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Legal Knowledge Graph took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Legal Knowledge Graph took 1.3113021850585938e-05s
Believability | Calculation of trust value for Legal Knowledge Graph took 7.867813110351562e-06s
INFO | --- Analysis for KING took 2.7179603576660156s
Availability | SPARQL endpoint availability check for Klappstuhlclub took 4.220008850097656e-05s
Availability | VoID file availability check for Klappstuhlclub took 0.0007848739624023438s
Completeness | Calculation of interlinking completeness for Klappstuhlclub took 0.26198792457580566s
Reputation | Calculation of the PageRank for Klappstuhlclub took 0.020404815673828125s
Interlinking | Calculation of Degree of Connection for Klappstuhlclub took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Klappstuhlclub took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Klappstuhlclub took 6.747245788574219e-05s
Believability | Calculation of trust value for Klappstuhlclub took 5.245208740234375e-06s
INFO | --- Analysis for klappstuhlclub took 12.586190938949585s
Availability | SPARQL endpoint availability check for Linked Sensor Data (Kno.e.sis) took 10.785609006881714s
Availability | VoID file availability check for Linked Sensor Data (Kno.e.sis) took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for Linked Sensor Data (Kno.e.sis) took 0.2568526268005371s
Reputation | Calculation of the PageRank for Linked Sensor Data (Kno.e.sis) took 0.020682334899902344s
Interlinking | Calculation of Degree of Connection for Linked Sensor Data (Kno.e.sis) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Sensor Data (Kno.e.sis) took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Linked Sensor Data (Kno.e.sis) took 6.079673767089844e-05s
Believability | Calculation of trust value for Linked Sensor Data (Kno.e.sis) took 6.9141387939453125e-06s
INFO | --- Analysis for knoesis-linked-sensor-data took 23.22311782836914s
Availability | SPARQL endpoint availability check for Knowledge Forest took 8.726119995117188e-05s
Availability | VoID file availability check for Knowledge Forest took 0.0002186298370361328s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.2655782699584961s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.02035379409790039s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 3.0279159545898438e-05s
Believability | Calculation of trust value for Knowledge Forest took 6.67572021484375e-06s
INFO | --- Analysis for KnowledgeFusion took 2.440758466720581s
Availability | SPARQL endpoint availability check for KORE 50 NIF NER Corpus took 4.506111145019531e-05s
Availability | VoID file availability check for KORE 50 NIF NER Corpus took 0.0008327960968017578s
Completeness | Calculation of interlinking completeness for KORE 50 NIF NER Corpus took 0.2860405445098877s
Reputation | Calculation of the PageRank for KORE 50 NIF NER Corpus took 0.020552635192871094s
Interlinking | Calculation of Degree of Connection for KORE 50 NIF NER Corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for KORE 50 NIF NER Corpus took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for KORE 50 NIF NER Corpus took 6.580352783203125e-05s
Believability | Calculation of trust value for KORE 50 NIF NER Corpus took 6.67572021484375e-06s
INFO | --- Analysis for kore-50-nif-ner-corpus took 14.24148416519165s
Availability | SPARQL endpoint availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 4.4345855712890625e-05s
Availability | VoID file availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.00021958351135253906s
Completeness | Calculation of interlinking completeness for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.28707385063171387s
Reputation | Calculation of the PageRank for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.02051067352294922s
Interlinking | Calculation of Degree of Connection for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 2.8848648071289062e-05s
Believability | Calculation of trust value for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 5.4836273193359375e-06s
INFO | --- Analysis for Kronika_naukowa_Biblioteki_Jagiellońskiej took 2.3761088848114014s
Availability | SPARQL endpoint availability check for Informatics Studies took 4.172325134277344e-05s
Availability | VoID file availability check for Informatics Studies took 0.0005848407745361328s
Completeness | Calculation of interlinking completeness for Informatics Studies took 0.2740468978881836s
Reputation | Calculation of the PageRank for Informatics Studies took 0.020488739013671875s
Interlinking | Calculation of Degree of Connection for Informatics Studies took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Informatics Studies took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Informatics Studies took 2.9325485229492188e-05s
Believability | Calculation of trust value for Informatics Studies took 1.1205673217773438e-05s
INFO | --- Analysis for Kumar,_Gireesh__and_Singh,_Anand took 2.9242587089538574s
Availability | SPARQL endpoint availability check for Kidney and Urinary Pathway Knowledge Base took 0.05392861366271973s
Availability | VoID file availability check for Kidney and Urinary Pathway Knowledge Base took 0.0003998279571533203s
Completeness | Calculation of interlinking completeness for Kidney and Urinary Pathway Knowledge Base took 0.2786877155303955s
Reputation | Calculation of the PageRank for Kidney and Urinary Pathway Knowledge Base took 0.020572423934936523s
Interlinking | Calculation of Degree of Connection for Kidney and Urinary Pathway Knowledge Base took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Kidney and Urinary Pathway Knowledge Base took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Kidney and Urinary Pathway Knowledge Base took 3.8623809814453125e-05s
Believability | Calculation of trust value for Kidney and Urinary Pathway Knowledge Base took 5.7220458984375e-06s
INFO | --- Analysis for kupkb took 8.543774366378784s
Availability | SPARQL endpoint availability check for DBLP in RDF (L3S) took 9.58187198638916s
Availability | VoID file availability check for DBLP in RDF (L3S) took 0.0006937980651855469s
Completeness | Calculation of interlinking completeness for DBLP in RDF (L3S) took 0.27977585792541504s
Reputation | Calculation of the PageRank for DBLP in RDF (L3S) took 0.02062821388244629s
Interlinking | Calculation of Degree of Connection for DBLP in RDF (L3S) took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for DBLP in RDF (L3S) took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for DBLP in RDF (L3S) took 8.153915405273438e-05s
Believability | Calculation of trust value for DBLP in RDF (L3S) took 1.0013580322265625e-05s
INFO | --- Analysis for l3s-dblp took 43.917819023132324s
Availability | SPARQL endpoint availability check for Learning Analytics and Knowledge (LAK) Dataset took 22.657870769500732s
Availability | VoID file availability check for Learning Analytics and Knowledge (LAK) Dataset took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for Learning Analytics and Knowledge (LAK) Dataset took 0.2646019458770752s
Reputation | Calculation of the PageRank for Learning Analytics and Knowledge (LAK) Dataset took 0.020511627197265625s
Interlinking | Calculation of Degree of Connection for Learning Analytics and Knowledge (LAK) Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Learning Analytics and Knowledge (LAK) Dataset took 0.0008604526519775391s
Interlinking | Calculation of Clustering coefficient for Learning Analytics and Knowledge (LAK) Dataset took 6.604194641113281e-05s
Believability | Calculation of trust value for Learning Analytics and Knowledge (LAK) Dataset took 1.1920928955078125e-05s
INFO | --- Analysis for lak-dataset took 66.77580165863037s
Availability | SPARQL endpoint availability check for  Language Name Authority List  took 0.18346428871154785s
Availability | VoID file availability check for  Language Name Authority List  took 0.0005462169647216797s
Extra | Recovery of all triples for  Language Name Authority List  took 292.4083790779114s
Performance | Total latancy measurement for  Language Name Authority List  took 0.545405387878418s
Amount of data | Number of triples check for  Language Name Authority List  took 46.536749839782715s
Interoperability | New terms check for  Language Name Authority List  took 61.550771713256836s
Versatility | Languages check for  Language Name Authority List  took 300.0445442199707s
Interpretability | Number of blank nodes check for  Language Name Authority List  took 16.366701364517212s
Security | Check HTTPS for  Language Name Authority List  took 0.3179206848144531s
Interpretability | RDF structures check for  Language Name Authority List  took 0.540977954864502s
Versatility | Serialization formats check for  Language Name Authority List  took 10.256412982940674s
Availability | RDF dump link check for  Language Name Authority List  took 0.2695622444152832s
License | MR license check for  Language Name Authority List  took 0.8927156925201416s
License | HR license check for  Language Name Authority List  took 300.0549476146698s
Amount of data | Number of property check for  Language Name Authority List  took 0.17729520797729492s
Understandability | Number of label check for  Language Name Authority List  took 1.534071683883667s
Understandability | URI regex check for  Language Name Authority List  took 0.38472461700439453s
Understandability | Vocabs check for  Language Name Authority List  took 0.09839034080505371s
Verifiability | Authors check for  Language Name Authority List  took 0.21295595169067383s
Verifiability | Publishers check for  Language Name Authority List  took 0.18041706085205078s
Performance | Throughput check for  Language Name Authority List  took 10.529983758926392s
Amount of data | Check the number of entities for  Language Name Authority List  took 0.00011610984802246094s
Verifiability | Contribs. check for  Language Name Authority List  took 0.11678624153137207s
Interlinking | sameAs chians check for  Language Name Authority List  took 6.425641298294067s
Interlinking | skos check for  Language Name Authority List  took 0.32190632820129395s
Interlinking | skos check for  Language Name Authority List  took 0.29122042655944824s
Timeliness | dataset update frequency check for  Language Name Authority List  took 0.17540240287780762s
Currency | Creation date check for  Language Name Authority List  took 0.4201338291168213s
Currency | Modification date check for  Language Name Authority List  took 0.14962434768676758s
Rep.Conc. | URIs length for  Language Name Authority List  took 448.292512178421s
Interoperability | New vocabularies check for  Language Name Authority List  took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for  Language Name Authority List  took 0.15730643272399902s
Accuracy | Check Functional Property for  Language Name Authority List  took 0.1929340362548828s
Accuracy | Check Inverse Functional Property for  Language Name Authority List  took 0.21907448768615723s
Accuracy | Check Empty annotation labels for  Language Name Authority List  took 46.50856685638428s
Accuracy | Check White space in annotation for  Language Name Authority List  took 3.0277888774871826s
Accuracy | Check Datatype consistency for  Language Name Authority List  took 2.5405099391937256s
Consistency | Disjoint class check for  Language Name Authority List  took 0.16680216789245605s
Consistency | Check Misplaced properties for  Language Name Authority List  took 300.5911138057709s
Consistency | Misplaced classes for  Language Name Authority List  took 8.528987169265747s
Consistency | Check Ontology hijacking for  Language Name Authority List  took 46.71364784240723s
Consistency | Check Invalid usage of undefined classes for  Language Name Authority List  took 1.4416861534118652s
Consistency | Check Invalid usage of undefined properties for  Language Name Authority List  took 301.4195680618286s
Conciseness | Check Extensional conciseness for  Language Name Authority List  took 2.9693801403045654s
Conciseness | Check Intensional conciseness for  Language Name Authority List  took 0.37368321418762207s
Security | Sign check for  Language Name Authority List  took 0.4042954444885254s
Availability | Check URIs Dereferenciability for  Language Name Authority List  took 11.274698495864868s
Completeness | Calculation of interlinking completeness for  Language Name Authority List  took 0.6885344982147217s
Reputation | Calculation of the PageRank for  Language Name Authority List  took 0.021298646926879883s
Interlinking | Calculation of Degree of Connection for  Language Name Authority List  took 2.5033950805664062e-05s
Interlinking | Calculation of Centrality for  Language Name Authority List  took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for  Language Name Authority List  took 9.34600830078125e-05s
Interoperability | Check the re-using of existing vocabs for  Language Name Authority List  took 1.1920928955078125e-06s
Believability | Calculation of trust value for  Language Name Authority List  took 1.1920928955078125e-05s
INFO | --- Analysis for language-authority-list took 14437.054548978806s
Availability | SPARQL endpoint availability check for Lark took 384.3239064216614s
Availability | VoID file availability check for Lark took 0.0007698535919189453s
Completeness | Calculation of interlinking completeness for Lark took 0.46558690071105957s
Reputation | Calculation of the PageRank for Lark took 0.0211029052734375s
Interlinking | Calculation of Degree of Connection for Lark took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Lark took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Lark took 0.0001361370086669922s
Believability | Calculation of trust value for Lark took 1.0967254638671875e-05s
INFO | --- Analysis for LARK took 1676.103411912918s
Availability | SPARQL endpoint availability check for LASLA corpus in LiLa took 0.4734044075012207s
Availability | VoID file availability check for LASLA corpus in LiLa took 0.0005598068237304688s
Completeness | Calculation of interlinking completeness for LASLA corpus in LiLa took 0.273761510848999s
Reputation | Calculation of the PageRank for LASLA corpus in LiLa took 0.020652294158935547s
Interlinking | Calculation of Degree of Connection for LASLA corpus in LiLa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LASLA corpus in LiLa took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for LASLA corpus in LiLa took 4.482269287109375e-05s
Believability | Calculation of trust value for LASLA corpus in LiLa took 6.9141387939453125e-06s
INFO | --- Analysis for LASLA took 3.896496057510376s
Availability | SPARQL endpoint availability check for Latin Vallex 2.0 in LiLa took 0.4647557735443115s
Availability | VoID file availability check for Latin Vallex 2.0 in LiLa took 0.0005693435668945312s
Completeness | Calculation of interlinking completeness for Latin Vallex 2.0 in LiLa took 0.276592493057251s
Reputation | Calculation of the PageRank for Latin Vallex 2.0 in LiLa took 0.02042222023010254s
Interlinking | Calculation of Degree of Connection for Latin Vallex 2.0 in LiLa took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Latin Vallex 2.0 in LiLa took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Latin Vallex 2.0 in LiLa took 4.38690185546875e-05s
Believability | Calculation of trust value for Latin Vallex 2.0 in LiLa took 1.430511474609375e-05s
INFO | --- Analysis for Latin_Vallex2.0 took 4.004079341888428s
Availability | SPARQL endpoint availability check for LatinAffectus in LiLa took 0.43846845626831055s
Availability | VoID file availability check for LatinAffectus in LiLa took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for LatinAffectus in LiLa took 0.26384782791137695s
Reputation | Calculation of the PageRank for LatinAffectus in LiLa took 0.020438194274902344s
Interlinking | Calculation of Degree of Connection for LatinAffectus in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LatinAffectus in LiLa took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for LatinAffectus in LiLa took 3.910064697265625e-05s
Believability | Calculation of trust value for LatinAffectus in LiLa took 1.0967254638671875e-05s
INFO | --- Analysis for LatinAffectus took 4.014552593231201s
Availability | SPARQL endpoint availability check for Latin WordNet Revision in LiLa took 0.42789173126220703s
Availability | VoID file availability check for Latin WordNet Revision in LiLa took 0.0003502368927001953s
Completeness | Calculation of interlinking completeness for Latin WordNet Revision in LiLa took 0.26650118827819824s
Reputation | Calculation of the PageRank for Latin WordNet Revision in LiLa took 0.020899057388305664s
Interlinking | Calculation of Degree of Connection for Latin WordNet Revision in LiLa took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Latin WordNet Revision in LiLa took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Latin WordNet Revision in LiLa took 4.1484832763671875e-05s
Believability | Calculation of trust value for Latin WordNet Revision in LiLa took 1.1205673217773438e-05s
INFO | --- Analysis for LatinWordnetLiLa took 4.262340784072876s
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.0007033348083496094s
Completeness | Calculation of interlinking completeness for Library of Congress Subject Headings took 0.2778596878051758s
Reputation | Calculation of the PageRank for Library of Congress Subject Headings took 0.020481586456298828s
Interlinking | Calculation of Degree of Connection for Library of Congress Subject Headings took 2.4080276489257812e-05s
Interlinking | Calculation of Centrality for Library of Congress Subject Headings took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Library of Congress Subject Headings took 0.00013017654418945312s
Believability | Calculation of trust value for Library of Congress Subject Headings took 1.0967254638671875e-05s
INFO | --- Analysis for lcsh took 5.697896242141724s
Availability | SPARQL endpoint availability check for LCSubjects.org Library of Congress Subject Headings took 8.463859558105469e-05s
Availability | VoID file availability check for LCSubjects.org Library of Congress Subject Headings took 0.0005116462707519531s
Completeness | Calculation of interlinking completeness for LCSubjects.org Library of Congress Subject Headings took 0.2699453830718994s
Reputation | Calculation of the PageRank for LCSubjects.org Library of Congress Subject Headings took 0.022237539291381836s
Interlinking | Calculation of Degree of Connection for LCSubjects.org Library of Congress Subject Headings took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LCSubjects.org Library of Congress Subject Headings took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for LCSubjects.org Library of Congress Subject Headings took 8.511543273925781e-05s
Believability | Calculation of trust value for LCSubjects.org Library of Congress Subject Headings took 1.1682510375976562e-05s
INFO | --- Analysis for lcsubjects took 2.8206305503845215s
Availability | SPARQL endpoint availability check for Linked Open Data Taiwan @ Library took 9.093470096588135s
Availability | VoID file availability check for Linked Open Data Taiwan @ Library took 0.0006251335144042969s
Completeness | Calculation of interlinking completeness for Linked Open Data Taiwan @ Library took 0.31041789054870605s
Reputation | Calculation of the PageRank for Linked Open Data Taiwan @ Library took 0.020393848419189453s
Interlinking | Calculation of Degree of Connection for Linked Open Data Taiwan @ Library took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Open Data Taiwan @ Library took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Linked Open Data Taiwan @ Library took 4.5299530029296875e-05s
Believability | Calculation of trust value for Linked Open Data Taiwan @ Library took 1.0967254638671875e-05s
INFO | --- Analysis for ldt@library took 35.324196577072144s
Availability | SPARQL endpoint availability check for U ime Legije took 8.559226989746094e-05s
Availability | VoID file availability check for U ime Legije took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for U ime Legije took 0.2759237289428711s
Reputation | Calculation of the PageRank for U ime Legije took 0.020656585693359375s
Interlinking | Calculation of Degree of Connection for U ime Legije took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for U ime Legije took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for U ime Legije took 3.075599670410156e-05s
Believability | Calculation of trust value for U ime Legije took 1.0013580322265625e-05s
INFO | --- Analysis for LEGIJA_STRANACA took 2.4404447078704834s
Availability | SPARQL endpoint availability check for LiLa Lemma Bank took 0.45472145080566406s
Availability | VoID file availability check for LiLa Lemma Bank took 0.0005598068237304688s
Completeness | Calculation of interlinking completeness for LiLa Lemma Bank took 0.2722768783569336s
Reputation | Calculation of the PageRank for LiLa Lemma Bank took 0.02058696746826172s
Interlinking | Calculation of Degree of Connection for LiLa Lemma Bank took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LiLa Lemma Bank took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for LiLa Lemma Bank took 7.295608520507812e-05s
Believability | Calculation of trust value for LiLa Lemma Bank took 1.049041748046875e-05s
INFO | --- Analysis for LemmaBank took 4.292766094207764s
Availability | SPARQL endpoint availability check for lemonUby took 4.172325134277344e-05s
Availability | VoID file availability check for lemonUby took 0.0006387233734130859s
Completeness | Calculation of interlinking completeness for lemonUby took 0.2642982006072998s
Reputation | Calculation of the PageRank for lemonUby took 0.020565509796142578s
Interlinking | Calculation of Degree of Connection for lemonUby took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for lemonUby took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for lemonUby took 6.937980651855469e-05s
Believability | Calculation of trust value for lemonUby took 1.1682510375976562e-05s
INFO | --- Analysis for lemonuby took 3.0533275604248047s
Availability | SPARQL endpoint availability check for LemonWiktionary took 8.726119995117188e-05s
Availability | VoID file availability check for LemonWiktionary took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for LemonWiktionary took 0.28064513206481934s
Reputation | Calculation of the PageRank for LemonWiktionary took 0.020400285720825195s
Interlinking | Calculation of Degree of Connection for LemonWiktionary took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LemonWiktionary took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for LemonWiktionary took 3.838539123535156e-05s
Believability | Calculation of trust value for LemonWiktionary took 1.1682510375976562e-05s
INFO | --- Analysis for lemonwiktionary took 4.397841930389404s
Availability | SPARQL endpoint availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.45651769638061523s
Availability | VoID file availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.0005877017974853516s
Completeness | Calculation of interlinking completeness for Lewis and Short Latin-English Dictionary in LiLa took 0.26801514625549316s
Reputation | Calculation of the PageRank for Lewis and Short Latin-English Dictionary in LiLa took 0.020619869232177734s
Interlinking | Calculation of Degree of Connection for Lewis and Short Latin-English Dictionary in LiLa took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Lewis and Short Latin-English Dictionary in LiLa took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Lewis and Short Latin-English Dictionary in LiLa took 3.838539123535156e-05s
Believability | Calculation of trust value for Lewis and Short Latin-English Dictionary in LiLa took 1.1682510375976562e-05s
INFO | --- Analysis for LewisShort took 4.113857269287109s
Availability | SPARQL endpoint availability check for LEXIN-RDF took 0.9616529941558838s
Availability | VoID file availability check for LEXIN-RDF took 0.0006124973297119141s
Completeness | Calculation of interlinking completeness for LEXIN-RDF took 0.27350687980651855s
Reputation | Calculation of the PageRank for LEXIN-RDF took 0.021843433380126953s
Interlinking | Calculation of Degree of Connection for LEXIN-RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LEXIN-RDF took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for LEXIN-RDF took 3.075599670410156e-05s
Believability | Calculation of trust value for LEXIN-RDF took 1.5020370483398438e-05s
INFO | --- Analysis for lexin-rdf took 5.550661563873291s
Availability | SPARQL endpoint availability check for lexinfo took 8.487701416015625e-05s
Availability | VoID file availability check for lexinfo took 0.0005259513854980469s
Completeness | Calculation of interlinking completeness for lexinfo took 0.26552462577819824s
Reputation | Calculation of the PageRank for lexinfo took 0.02057504653930664s
Interlinking | Calculation of Degree of Connection for lexinfo took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for lexinfo took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for lexinfo took 9.059906005859375e-05s
Believability | Calculation of trust value for lexinfo took 1.0728836059570312e-05s
INFO | --- Analysis for lexinfo took 2.8756282329559326s
Availability | SPARQL endpoint availability check for Lexvo took 4.4345855712890625e-05s
Availability | VoID file availability check for Lexvo took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for Lexvo took 0.2605714797973633s
Reputation | Calculation of the PageRank for Lexvo took 0.02084636688232422s
Interlinking | Calculation of Degree of Connection for Lexvo took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Lexvo took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Lexvo took 0.0001823902130126953s
Believability | Calculation of trust value for Lexvo took 1.1444091796875e-05s
INFO | --- Analysis for lexvo took 3.1894447803497314s
Availability | SPARQL endpoint availability check for Lexvo.org took 8.177757263183594e-05s
Availability | VoID file availability check for Lexvo.org took 0.0005273818969726562s
Completeness | Calculation of interlinking completeness for Lexvo.org took 0.29560089111328125s
Reputation | Calculation of the PageRank for Lexvo.org took 0.0205080509185791s
Interlinking | Calculation of Degree of Connection for Lexvo.org took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Lexvo.org took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Lexvo.org took 7.724761962890625e-05s
Believability | Calculation of trust value for Lexvo.org took 1.1920928955078125e-05s
INFO | --- Analysis for lexvo-org took 2.626518964767456s
Availability | SPARQL endpoint availability check for LIBRIS took 0.5273222923278809s
Availability | VoID file availability check for LIBRIS took 0.0006132125854492188s
Extra | Recovery of all triples for LIBRIS took 20.707351684570312s
Performance | Total latancy measurement for LIBRIS took 0.7147243022918701s
Amount of data | Number of triples check for LIBRIS took 44.018166303634644s
Interoperability | New terms check for LIBRIS took 16.028806447982788s
Versatility | Languages check for LIBRIS took 0.18799328804016113s
Interpretability | Number of blank nodes check for LIBRIS took 300.10293889045715s
Security | Check HTTPS for LIBRIS took 0.3386368751525879s
Interpretability | RDF structures check for LIBRIS took 0.8134241104125977s
Versatility | Serialization formats check for LIBRIS took 0.27395081520080566s
Availability | RDF dump link check for LIBRIS took 0.2284860610961914s
License | MR license check for LIBRIS took 0.40274953842163086s
License | HR license check for LIBRIS took 0.42255425453186035s
Amount of data | Number of property check for LIBRIS took 0.19973540306091309s
Understandability | Number of label check for LIBRIS took 0.7113990783691406s
Understandability | URI regex check for LIBRIS took 0.4802367687225342s
Understandability | Vocabs check for LIBRIS took 0.14121317863464355s
Verifiability | Authors check for LIBRIS took 0.17741703987121582s
Verifiability | Publishers check for LIBRIS took 0.29605913162231445s
Performance | Throughput check for LIBRIS took 10.669461488723755s
Amount of data | Check the number of entities for LIBRIS took 7.224082946777344e-05s
Verifiability | Contribs. check for LIBRIS took 0.18995285034179688s
Interlinking | sameAs chians check for LIBRIS took 0.2682223320007324s
Interlinking | skos check for LIBRIS took 0.5633566379547119s
Interlinking | skos check for LIBRIS took 0.14063692092895508s
Timeliness | dataset update frequency check for LIBRIS took 0.16968655586242676s
Currency | Creation date check for LIBRIS took 0.40160703659057617s
Currency | Modification date check for LIBRIS took 0.6413993835449219s
Rep.Conc. | URIs length for LIBRIS took 100.3210620880127s
Interoperability | New vocabularies check for LIBRIS took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for LIBRIS took 0.19437623023986816s
Accuracy | Check Functional Property for LIBRIS took 0.24592089653015137s
Accuracy | Check Inverse Functional Property for LIBRIS took 0.19603419303894043s
Accuracy | Check Datatype consistency for LIBRIS took 0.2689681053161621s
Consistency | Disjoint class check for LIBRIS took 0.1954660415649414s
Consistency | Check Misplaced properties for LIBRIS took 60.89368724822998s
Consistency | Misplaced classes for LIBRIS took 1.1660144329071045s
Consistency | Check Ontology hijacking for LIBRIS took 5.978708267211914s
Consistency | Check Invalid usage of undefined classes for LIBRIS took 1.3017730712890625s
Consistency | Check Invalid usage of undefined properties for LIBRIS took 61.94522953033447s
Conciseness | Check Extensional conciseness for LIBRIS took 0.2835061550140381s
Conciseness | Check Intensional conciseness for LIBRIS took 0.40682053565979004s
Security | Sign check for LIBRIS took 0.2166433334350586s
Availability | Check URIs Dereferenciability for LIBRIS took 9.21431040763855s
Completeness | Calculation of interlinking completeness for LIBRIS took 0.3231184482574463s
Reputation | Calculation of the PageRank for LIBRIS took 0.02064061164855957s
Interlinking | Calculation of Degree of Connection for LIBRIS took 6.318092346191406e-05s
Interlinking | Calculation of Centrality for LIBRIS took 0.0006856918334960938s
Interlinking | Calculation of Clustering coefficient for LIBRIS took 9.965896606445312e-05s
Interoperability | Check the re-using of existing vocabs for LIBRIS took 1.6689300537109375e-06s
Believability | Calculation of trust value for LIBRIS took 1.239776611328125e-05s
INFO | --- Analysis for libris took 1146.597538948059s
Availability | SPARQL endpoint availability check for Public Library of Veroia took 0.05538654327392578s
Availability | VoID file availability check for Public Library of Veroia took 0.00041556358337402344s
Completeness | Calculation of interlinking completeness for Public Library of Veroia took 0.269855260848999s
Reputation | Calculation of the PageRank for Public Library of Veroia took 0.022110700607299805s
Interlinking | Calculation of Degree of Connection for Public Library of Veroia took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Public Library of Veroia took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Public Library of Veroia took 7.271766662597656e-05s
Believability | Calculation of trust value for Public Library of Veroia took 1.049041748046875e-05s
INFO | --- Analysis for libver took 3.649812936782837s
Availability | SPARQL endpoint availability check for Lichfield District Council - Spending took 0.12395381927490234s
Availability | VoID file availability check for Lichfield District Council - Spending took 0.0002911090850830078s
Completeness | Calculation of interlinking completeness for Lichfield District Council - Spending took 0.2786080837249756s
Reputation | Calculation of the PageRank for Lichfield District Council - Spending took 0.021204471588134766s
Interlinking | Calculation of Degree of Connection for Lichfield District Council - Spending took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Lichfield District Council - Spending took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Lichfield District Council - Spending took 7.700920104980469e-05s
Believability | Calculation of trust value for Lichfield District Council - Spending took 7.867813110351562e-06s
INFO | --- Analysis for lichfield-spending took 2.628923177719116s
Availability | SPARQL endpoint availability check for Linguistic Metadata (LIME) vocabulary took 8.511543273925781e-05s
Availability | VoID file availability check for Linguistic Metadata (LIME) vocabulary took 0.0006096363067626953s
Completeness | Calculation of interlinking completeness for Linguistic Metadata (LIME) vocabulary took 0.27811169624328613s
Reputation | Calculation of the PageRank for Linguistic Metadata (LIME) vocabulary took 0.02044820785522461s
Interlinking | Calculation of Degree of Connection for Linguistic Metadata (LIME) vocabulary took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linguistic Metadata (LIME) vocabulary took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Linguistic Metadata (LIME) vocabulary took 3.24249267578125e-05s
Believability | Calculation of trust value for Linguistic Metadata (LIME) vocabulary took 1.0013580322265625e-05s
INFO | --- Analysis for lime took 6.340653419494629s
Availability | SPARQL endpoint availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 4.1484832763671875e-05s
Availability | VoID file availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.44943976402282715s
Completeness | Calculation of interlinking completeness for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.28562235832214355s
Reputation | Calculation of the PageRank for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0218045711517334s
Interlinking | Calculation of Degree of Connection for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.00011086463928222656s
Believability | Calculation of trust value for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.1444091796875e-05s
INFO | --- Analysis for lingvoj took 42.60450625419617s
Availability | SPARQL endpoint availability check for Linked Crunchbase took 8.416175842285156e-05s
Availability | VoID file availability check for Linked Crunchbase took 0.0004622936248779297s
Completeness | Calculation of interlinking completeness for Linked Crunchbase took 0.3007998466491699s
Reputation | Calculation of the PageRank for Linked Crunchbase took 0.020219802856445312s
Interlinking | Calculation of Degree of Connection for Linked Crunchbase took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Crunchbase took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Linked Crunchbase took 7.867813110351562e-05s
Believability | Calculation of trust value for Linked Crunchbase took 1.0967254638671875e-05s
INFO | --- Analysis for linked-crunchbase took 14.889967679977417s
Availability | SPARQL endpoint availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.272860050201416s
Availability | VoID file availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.2727839946746826s
Reputation | Calculation of the PageRank for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.02116537094116211s
Interlinking | Calculation of Degree of Connection for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0008766651153564453s
Interlinking | Calculation of Clustering coefficient for LinkedDrugs: Linked Drug Product Data on a Global Scale took 7.271766662597656e-05s
Believability | Calculation of trust value for LinkedDrugs: Linked Drug Product Data on a Global Scale took 9.5367431640625e-06s
INFO | --- Analysis for linked-drugs took 6.712007284164429s
Availability | SPARQL endpoint availability check for Linked EDGAR (OntologyCentral) took 4.315376281738281e-05s
Availability | VoID file availability check for Linked EDGAR (OntologyCentral) took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for Linked EDGAR (OntologyCentral) took 0.26678991317749023s
Reputation | Calculation of the PageRank for Linked EDGAR (OntologyCentral) took 0.021083593368530273s
Interlinking | Calculation of Degree of Connection for Linked EDGAR (OntologyCentral) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked EDGAR (OntologyCentral) took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Linked EDGAR (OntologyCentral) took 9.465217590332031e-05s
Believability | Calculation of trust value for Linked EDGAR (OntologyCentral) took 8.344650268554688e-06s
INFO | --- Analysis for linked-edgar took 4.011367321014404s
Availability | SPARQL endpoint availability check for Linked Eurostat (OntologyCentral) took 8.916854858398438e-05s
Availability | VoID file availability check for Linked Eurostat (OntologyCentral) took 0.0003345012664794922s
Completeness | Calculation of interlinking completeness for Linked Eurostat (OntologyCentral) took 0.2639801502227783s
Reputation | Calculation of the PageRank for Linked Eurostat (OntologyCentral) took 0.022071361541748047s
Interlinking | Calculation of Degree of Connection for Linked Eurostat (OntologyCentral) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Eurostat (OntologyCentral) took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Linked Eurostat (OntologyCentral) took 9.584426879882812e-05s
Believability | Calculation of trust value for Linked Eurostat (OntologyCentral) took 7.3909759521484375e-06s
INFO | --- Analysis for linked-eurostat took 4.458629846572876s
Availability | SPARQL endpoint availability check for linked hypernyms took 4.863739013671875e-05s
Availability | VoID file availability check for linked hypernyms took 0.0002753734588623047s
Completeness | Calculation of interlinking completeness for linked hypernyms took 0.2691178321838379s
Reputation | Calculation of the PageRank for linked hypernyms took 0.020176410675048828s
Interlinking | Calculation of Degree of Connection for linked hypernyms took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for linked hypernyms took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for linked hypernyms took 6.961822509765625e-05s
Believability | Calculation of trust value for linked hypernyms took 6.9141387939453125e-06s
INFO | --- Analysis for linked-hypernyms took 3.233250141143799s
Availability | SPARQL endpoint availability check for Linked Life Data took 238.81852269172668s
Availability | VoID file availability check for Linked Life Data took 0.0007145404815673828s
Completeness | Calculation of interlinking completeness for Linked Life Data took 0.38999247550964355s
Reputation | Calculation of the PageRank for Linked Life Data took 0.020853519439697266s
Interlinking | Calculation of Degree of Connection for Linked Life Data took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Linked Life Data took 0.0008325576782226562s
Interlinking | Calculation of Clustering coefficient for Linked Life Data took 5.602836608886719e-05s
Believability | Calculation of trust value for Linked Life Data took 1.0251998901367188e-05s
INFO | --- Analysis for linked-life-data took 697.8392179012299s
Availability | SPARQL endpoint availability check for Linked Logainm took 0.2450728416442871s
Availability | VoID file availability check for Linked Logainm took 0.0005247592926025391s
Extra | Recovery of all triples for Linked Logainm took 3.1111319065093994s
Performance | Total latancy measurement for Linked Logainm took 0.5400862693786621s
Amount of data | Number of triples check for Linked Logainm took 0.15747547149658203s
Interoperability | New terms check for Linked Logainm took 1.4502124786376953s
Versatility | Languages check for Linked Logainm took 1.4517178535461426s
Interpretability | Number of blank nodes check for Linked Logainm took 0.12796473503112793s
Security | Check HTTPS for Linked Logainm took 0.24771690368652344s
Interpretability | RDF structures check for Linked Logainm took 0.24949908256530762s
Versatility | Serialization formats check for Linked Logainm took 0.13926100730895996s
Availability | RDF dump link check for Linked Logainm took 0.1059408187866211s
License | MR license check for Linked Logainm took 0.12568998336791992s
License | HR license check for Linked Logainm took 0.1123354434967041s
Amount of data | Number of property check for Linked Logainm took 0.1327190399169922s
Understandability | Number of label check for Linked Logainm took 0.19972634315490723s
Understandability | URI regex check for Linked Logainm took 1.2216241359710693s
Understandability | Vocabs check for Linked Logainm took 0.12494206428527832s
Verifiability | Authors check for Linked Logainm took 0.10798501968383789s
Verifiability | Publishers check for Linked Logainm took 0.10463714599609375s
Performance | Throughput check for Linked Logainm took 10.215422868728638s
Amount of data | Check the number of entities for Linked Logainm took 0.00012803077697753906s
Verifiability | Contribs. check for Linked Logainm took 0.10990381240844727s
Interlinking | sameAs chians check for Linked Logainm took 0.13749194145202637s
Interlinking | skos check for Linked Logainm took 0.1415233612060547s
Interlinking | skos check for Linked Logainm took 0.10386872291564941s
Timeliness | dataset update frequency check for Linked Logainm took 0.11763858795166016s
Currency | Creation date check for Linked Logainm took 0.23401808738708496s
Currency | Modification date check for Linked Logainm took 0.23935341835021973s
Rep.Conc. | URIs length for Linked Logainm took 0.9483861923217773s
Interoperability | New vocabularies check for Linked Logainm took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Linked Logainm took 0.1345813274383545s
Accuracy | Check Functional Property for Linked Logainm took 0.21539616584777832s
Accuracy | Check Inverse Functional Property for Linked Logainm took 0.19074654579162598s
Accuracy | Check Empty annotation labels for Linked Logainm took 0.5874598026275635s
Accuracy | Check White space in annotation for Linked Logainm took 0.024060964584350586s
Accuracy | Check Datatype consistency for Linked Logainm took 0.028169870376586914s
Consistency | Disjoint class check for Linked Logainm took 0.18603920936584473s
Consistency | Check Misplaced properties for Linked Logainm took 0.3248136043548584s
Consistency | Misplaced classes for Linked Logainm took 0.26816606521606445s
Consistency | Check Ontology hijacking for Linked Logainm took 1.8847737312316895s
Consistency | Check Invalid usage of undefined classes for Linked Logainm took 1.300668478012085s
Consistency | Check Invalid usage of undefined properties for Linked Logainm took 1.531494140625s
Conciseness | Check Extensional conciseness for Linked Logainm took 0.03235316276550293s
Conciseness | Check Intensional conciseness for Linked Logainm took 0.18207526206970215s
Security | Sign check for Linked Logainm took 0.11727738380432129s
Availability | Check URIs Dereferenciability for Linked Logainm took 895.0408046245575s
Completeness | Calculation of interlinking completeness for Linked Logainm took 0.3298921585083008s
Reputation | Calculation of the PageRank for Linked Logainm took 0.02271246910095215s
Interlinking | Calculation of Degree of Connection for Linked Logainm took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Linked Logainm took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Linked Logainm took 8.96453857421875e-05s
Interoperability | Check the re-using of existing vocabs for Linked Logainm took 1.430511474609375e-06s
Believability | Calculation of trust value for Linked Logainm took 1.0251998901367188e-05s
INFO | --- Analysis for linked-logainm took 951.762425661087s
Availability | SPARQL endpoint availability check for Linked NUTS took 8.726119995117188e-05s
Availability | VoID file availability check for Linked NUTS took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for Linked NUTS took 0.2871849536895752s
Reputation | Calculation of the PageRank for Linked NUTS took 0.02034759521484375s
Interlinking | Calculation of Degree of Connection for Linked NUTS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked NUTS took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Linked NUTS took 4.9114227294921875e-05s
Believability | Calculation of trust value for Linked NUTS took 8.344650268554688e-06s
INFO | --- Analysis for linked-nuts took 2.5595526695251465s
Availability | SPARQL endpoint availability check for Linked Open Camera (LinkedOpenData.it) took 0.3167684078216553s
Availability | VoID file availability check for Linked Open Camera (LinkedOpenData.it) took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for Linked Open Camera (LinkedOpenData.it) took 0.261014461517334s
Reputation | Calculation of the PageRank for Linked Open Camera (LinkedOpenData.it) took 0.020403146743774414s
Interlinking | Calculation of Degree of Connection for Linked Open Camera (LinkedOpenData.it) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Open Camera (LinkedOpenData.it) took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Linked Open Camera (LinkedOpenData.it) took 3.4332275390625e-05s
Believability | Calculation of trust value for Linked Open Camera (LinkedOpenData.it) took 8.106231689453125e-06s
INFO | --- Analysis for linked-open-camera took 2.822206735610962s
Availability | SPARQL endpoint availability check for Linked Open Commerce took 3.9484543800354004s
Availability | VoID file availability check for Linked Open Commerce took 0.0006978511810302734s
Completeness | Calculation of interlinking completeness for Linked Open Commerce took 0.2664909362792969s
Reputation | Calculation of the PageRank for Linked Open Commerce took 0.02024984359741211s
Interlinking | Calculation of Degree of Connection for Linked Open Commerce took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Linked Open Commerce took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Linked Open Commerce took 3.0279159545898438e-05s
Believability | Calculation of trust value for Linked Open Commerce took 1.239776611328125e-05s
INFO | --- Analysis for linked-open-commerce took 13.91979432106018s
Availability | SPARQL endpoint availability check for Linked Open Data of Ecology took 0.33371400833129883s
Availability | VoID file availability check for Linked Open Data of Ecology took 0.0004355907440185547s
Completeness | Calculation of interlinking completeness for Linked Open Data of Ecology took 0.26329922676086426s
Reputation | Calculation of the PageRank for Linked Open Data of Ecology took 0.020515918731689453s
Interlinking | Calculation of Degree of Connection for Linked Open Data of Ecology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Linked Open Data of Ecology took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Linked Open Data of Ecology took 0.00010061264038085938s
Believability | Calculation of trust value for Linked Open Data of Ecology took 1.0013580322265625e-05s
INFO | --- Analysis for linked-open-data-of-ecology took 2.7955806255340576s
Availability | SPARQL endpoint availability check for Linked Open Numbers took 4.267692565917969e-05s
Availability | VoID file availability check for Linked Open Numbers took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for Linked Open Numbers took 0.2869148254394531s
Reputation | Calculation of the PageRank for Linked Open Numbers took 0.021699905395507812s
Interlinking | Calculation of Degree of Connection for Linked Open Numbers took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Open Numbers took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Linked Open Numbers took 8.940696716308594e-05s
Believability | Calculation of trust value for Linked Open Numbers took 1.0251998901367188e-05s
INFO | --- Analysis for linked-open-numbers took 2.6796059608459473s
Availability | SPARQL endpoint availability check for Linked Open Piracy took 0.0001068115234375s
Availability | VoID file availability check for Linked Open Piracy took 0.0006387233734130859s
Completeness | Calculation of interlinking completeness for Linked Open Piracy took 0.2622349262237549s
Reputation | Calculation of the PageRank for Linked Open Piracy took 0.02052021026611328s
Interlinking | Calculation of Degree of Connection for Linked Open Piracy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Open Piracy took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Linked Open Piracy took 2.86102294921875e-05s
Believability | Calculation of trust value for Linked Open Piracy took 8.344650268554688e-06s
INFO | --- Analysis for linked-open-piracy took 6.839436769485474s
Availability | SPARQL endpoint availability check for Linked Open Vocabularies (LOV) took 35.91900038719177s
Availability | VoID file availability check for Linked Open Vocabularies (LOV) took 0.0006406307220458984s
Extra | Recovery of all triples for Linked Open Vocabularies (LOV) took 116.00407934188843s
Performance | Total latancy measurement for Linked Open Vocabularies (LOV) took 0.8889126777648926s
Amount of data | Number of triples check for Linked Open Vocabularies (LOV) took 2.555312395095825s
Interoperability | New terms check for Linked Open Vocabularies (LOV) took 2.094339370727539s
Versatility | Languages check for Linked Open Vocabularies (LOV) took 12.675421237945557s
Interpretability | Number of blank nodes check for Linked Open Vocabularies (LOV) took 1.513587474822998s
Interpretability | RDF structures check for Linked Open Vocabularies (LOV) took 3.20797061920166s
Versatility | Serialization formats check for Linked Open Vocabularies (LOV) took 0.1921401023864746s
Availability | RDF dump link check for Linked Open Vocabularies (LOV) took 1.604910135269165s
License | MR license check for Linked Open Vocabularies (LOV) took 0.18679547309875488s
License | HR license check for Linked Open Vocabularies (LOV) took 45.41450238227844s
Amount of data | Number of property check for Linked Open Vocabularies (LOV) took 0.17824029922485352s
Understandability | Number of label check for Linked Open Vocabularies (LOV) took 0.7089180946350098s
Understandability | URI regex check for Linked Open Vocabularies (LOV) took 0.3626589775085449s
Understandability | Vocabs check for Linked Open Vocabularies (LOV) took 2.462815999984741s
Verifiability | Authors check for Linked Open Vocabularies (LOV) took 0.2022559642791748s
Verifiability | Publishers check for Linked Open Vocabularies (LOV) took 0.1870710849761963s
Performance | Throughput check for Linked Open Vocabularies (LOV) took 166.12577486038208s
Amount of data | Check the number of entities for Linked Open Vocabularies (LOV) took 1.0244498252868652s
Verifiability | Contribs. check for Linked Open Vocabularies (LOV) took 0.18988418579101562s
Interlinking | sameAs chians check for Linked Open Vocabularies (LOV) took 38.67177057266235s
Interlinking | skos check for Linked Open Vocabularies (LOV) took 0.18161439895629883s
Interlinking | skos check for Linked Open Vocabularies (LOV) took 0.2813746929168701s
Timeliness | dataset update frequency check for Linked Open Vocabularies (LOV) took 0.2788410186767578s
Currency | Creation date check for Linked Open Vocabularies (LOV) took 1.1201674938201904s
Currency | Modification date check for Linked Open Vocabularies (LOV) took 0.19733595848083496s
Rep.Conc. | URIs length for Linked Open Vocabularies (LOV) took 41.70323371887207s
Interoperability | New vocabularies check for Linked Open Vocabularies (LOV) took 26.717423915863037s
Consistency | Deprecated classes/propertiers check for Linked Open Vocabularies (LOV) took 0.22756099700927734s
Accuracy | Check Functional Property for Linked Open Vocabularies (LOV) took 0.31774020195007324s
Accuracy | Check Inverse Functional Property for Linked Open Vocabularies (LOV) took 0.18616485595703125s
Accuracy | Check Empty annotation labels for Linked Open Vocabularies (LOV) took 50.892781257629395s
Accuracy | Check White space in annotation for Linked Open Vocabularies (LOV) took 0.6858267784118652s
Accuracy | Check Datatype consistency for Linked Open Vocabularies (LOV) took 4.712884187698364s
Consistency | Disjoint class check for Linked Open Vocabularies (LOV) took 0.23643064498901367s
Consistency | Check Misplaced properties for Linked Open Vocabularies (LOV) took 168.1780128479004s
Consistency | Misplaced classes for Linked Open Vocabularies (LOV) took 0.17126893997192383s
Consistency | Check Ontology hijacking for Linked Open Vocabularies (LOV) took 8.96604061126709s
Consistency | Check Invalid usage of undefined classes for Linked Open Vocabularies (LOV) took 1.3993346691131592s
Conciseness | Check Extensional conciseness for Linked Open Vocabularies (LOV) took 2.8639912605285645s
Conciseness | Check Intensional conciseness for Linked Open Vocabularies (LOV) took 2.087054491043091s
Security | Sign check for Linked Open Vocabularies (LOV) took 0.20032167434692383s
Availability | Check URIs Dereferenciability for Linked Open Vocabularies (LOV) took 5800.980434179306s
Completeness | Calculation of interlinking completeness for Linked Open Vocabularies (LOV) took 0.5967545509338379s
Reputation | Calculation of the PageRank for Linked Open Vocabularies (LOV) took 0.021053552627563477s
Interlinking | Calculation of Degree of Connection for Linked Open Vocabularies (LOV) took 6.270408630371094e-05s
Interlinking | Calculation of Centrality for Linked Open Vocabularies (LOV) took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Linked Open Vocabularies (LOV) took 5.888938903808594e-05s
Interoperability | Check the re-using of existing vocabs for Linked Open Vocabularies (LOV) took 1380.9883511066437s
Believability | Calculation of trust value for Linked Open Vocabularies (LOV) took 1.2159347534179688e-05s
INFO | --- Analysis for linked-open-vocabularies-lov took 8819.973110437393s
Availability | SPARQL endpoint availability check for Linked Periodicals Database took 8.988380432128906e-05s
Availability | VoID file availability check for Linked Periodicals Database took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for Linked Periodicals Database took 0.27086901664733887s
Reputation | Calculation of the PageRank for Linked Periodicals Database took 0.02035355567932129s
Interlinking | Calculation of Degree of Connection for Linked Periodicals Database took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Linked Periodicals Database took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Linked Periodicals Database took 3.6716461181640625e-05s
Believability | Calculation of trust value for Linked Periodicals Database took 8.344650268554688e-06s
INFO | --- Analysis for linked-periodicals took 2.576139211654663s
Availability | SPARQL endpoint availability check for Linked Index took 4.315376281738281e-05s
Availability | VoID file availability check for Linked Index took 0.0006320476531982422s
Completeness | Calculation of interlinking completeness for Linked Index took 0.2617032527923584s
Reputation | Calculation of the PageRank for Linked Index took 0.0202639102935791s
Interlinking | Calculation of Degree of Connection for Linked Index took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Index took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Linked Index took 0.00010442733764648438s
Believability | Calculation of trust value for Linked Index took 7.3909759521484375e-06s
INFO | --- Analysis for linked-stockindex took 3.180467367172241s
Availability | SPARQL endpoint availability check for Linked Structured Product Labels took 5.23519229888916s
Availability | VoID file availability check for Linked Structured Product Labels took 0.0007040500640869141s
Completeness | Calculation of interlinking completeness for Linked Structured Product Labels took 0.27314186096191406s
Reputation | Calculation of the PageRank for Linked Structured Product Labels took 0.021069049835205078s
Interlinking | Calculation of Degree of Connection for Linked Structured Product Labels took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for Linked Structured Product Labels took 0.0010230541229248047s
Interlinking | Calculation of Clustering coefficient for Linked Structured Product Labels took 5.340576171875e-05s
Believability | Calculation of trust value for Linked Structured Product Labels took 1.1444091796875e-05s
INFO | --- Analysis for linked-structured-product-labels took 18.897052764892578s
Availability | SPARQL endpoint availability check for Linked Taiwan Geo-Names took 0.3014981746673584s
Availability | VoID file availability check for Linked Taiwan Geo-Names took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for Linked Taiwan Geo-Names took 0.2882521152496338s
Reputation | Calculation of the PageRank for Linked Taiwan Geo-Names took 0.02032637596130371s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Geo-Names took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Geo-Names took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Geo-Names took 3.314018249511719e-05s
Believability | Calculation of trust value for Linked Taiwan Geo-Names took 1.0013580322265625e-05s
INFO | --- Analysis for linked-taiwan-geo-names took 2.9349632263183594s
Availability | SPARQL endpoint availability check for Linked TCGA took 20.189516305923462s
Availability | VoID file availability check for Linked TCGA took 0.0006194114685058594s
Completeness | Calculation of interlinking completeness for Linked TCGA took 0.27202272415161133s
Reputation | Calculation of the PageRank for Linked TCGA took 0.023300886154174805s
Interlinking | Calculation of Degree of Connection for Linked TCGA took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Linked TCGA took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Linked TCGA took 8.654594421386719e-05s
Believability | Calculation of trust value for Linked TCGA took 1.049041748046875e-05s
INFO | --- Analysis for linked-tcga took 62.729910135269165s
Availability | SPARQL endpoint availability check for Linked User Feedback took 0.0855865478515625s
Availability | VoID file availability check for Linked User Feedback took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for Linked User Feedback took 0.26108717918395996s
Reputation | Calculation of the PageRank for Linked User Feedback took 0.022105932235717773s
Interlinking | Calculation of Degree of Connection for Linked User Feedback took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Linked User Feedback took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Linked User Feedback took 3.910064697265625e-05s
Believability | Calculation of trust value for Linked User Feedback took 1.1682510375976562e-05s
INFO | --- Analysis for linked-user-feedback took 2.626718044281006s
Availability | SPARQL endpoint availability check for USPTO Patent data took 4.172325134277344e-05s
Availability | VoID file availability check for USPTO Patent data took 0.00028896331787109375s
Completeness | Calculation of interlinking completeness for USPTO Patent data took 0.25655508041381836s
Reputation | Calculation of the PageRank for USPTO Patent data took 0.020397424697875977s
Interlinking | Calculation of Degree of Connection for USPTO Patent data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for USPTO Patent data took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for USPTO Patent data took 8.273124694824219e-05s
Believability | Calculation of trust value for USPTO Patent data took 7.152557373046875e-06s
INFO | --- Analysis for linked-uspto-patent-data took 3.9726078510284424s
Availability | SPARQL endpoint availability check for Linked Crowdsourced Data took 0.06692385673522949s
Availability | VoID file availability check for Linked Crowdsourced Data took 0.0011017322540283203s
Completeness | Calculation of interlinking completeness for Linked Crowdsourced Data took 0.2754042148590088s
Reputation | Calculation of the PageRank for Linked Crowdsourced Data took 0.020555496215820312s
Interlinking | Calculation of Degree of Connection for Linked Crowdsourced Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Linked Crowdsourced Data took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Linked Crowdsourced Data took 3.719329833984375e-05s
Believability | Calculation of trust value for Linked Crowdsourced Data took 1.1920928955078125e-05s
INFO | --- Analysis for linkedcrowdsourceddata took 2.7271840572357178s
Availability | SPARQL endpoint availability check for LinkedCT took 1.5999019145965576s
Availability | VoID file availability check for LinkedCT took 0.0005915164947509766s
Completeness | Calculation of interlinking completeness for LinkedCT took 0.26650285720825195s
Reputation | Calculation of the PageRank for LinkedCT took 0.022525787353515625s
Interlinking | Calculation of Degree of Connection for LinkedCT took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for LinkedCT took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for LinkedCT took 0.00011134147644042969s
Believability | Calculation of trust value for LinkedCT took 1.1920928955078125e-05s
INFO | --- Analysis for linkedct took 5.485666275024414s
Availability | SPARQL endpoint availability check for LinkedGeoData took 0.14449334144592285s
Availability | VoID file availability check for LinkedGeoData took 0.000530242919921875s
Extra | Recovery of all triples for LinkedGeoData took 7.832180023193359s
Performance | Total latancy measurement for LinkedGeoData took 0.6279728412628174s
Amount of data | Number of triples check for LinkedGeoData took 95.81386685371399s
Interoperability | New terms check for LinkedGeoData took 90.96054720878601s
Versatility | Languages check for LinkedGeoData took 180.37838411331177s
Interpretability | Number of blank nodes check for LinkedGeoData took 0.41600608825683594s
Security | Check HTTPS for LinkedGeoData took 0.3059871196746826s
Interpretability | RDF structures check for LinkedGeoData took 1.0524201393127441s
Versatility | Serialization formats check for LinkedGeoData took 0.4432218074798584s
Availability | RDF dump link check for LinkedGeoData took 0.15143275260925293s
License | MR license check for LinkedGeoData took 0.7429094314575195s
License | HR license check for LinkedGeoData took 120.80605125427246s
Amount of data | Number of property check for LinkedGeoData took 0.1467573642730713s
Understandability | Number of label check for LinkedGeoData took 2.7029762268066406s
Understandability | URI regex check for LinkedGeoData took 0.3799455165863037s
Understandability | Vocabs check for LinkedGeoData took 0.15284061431884766s
Verifiability | Authors check for LinkedGeoData took 0.16267895698547363s
Verifiability | Publishers check for LinkedGeoData took 0.12310957908630371s
Performance | Throughput check for LinkedGeoData took 10.643144130706787s
Amount of data | Check the number of entities for LinkedGeoData took 0.06338882446289062s
Verifiability | Contribs. check for LinkedGeoData took 2.437911033630371s
Interlinking | sameAs chians check for LinkedGeoData took 0.3586287498474121s
Interlinking | skos check for LinkedGeoData took 0.41761136054992676s
Interlinking | skos check for LinkedGeoData took 0.12419295310974121s
Timeliness | dataset update frequency check for LinkedGeoData took 0.3881845474243164s
Currency | Creation date check for LinkedGeoData took 0.47707581520080566s
Currency | Modification date check for LinkedGeoData took 2.873462677001953s
Rep.Conc. | URIs length for LinkedGeoData took 271.79236030578613s
Interoperability | New vocabularies check for LinkedGeoData took 12.988120317459106s
Consistency | Deprecated classes/propertiers check for LinkedGeoData took 0.1512608528137207s
Accuracy | Check Functional Property for LinkedGeoData took 0.20423674583435059s
Accuracy | Check Inverse Functional Property for LinkedGeoData took 0.19027066230773926s
Accuracy | Check Empty annotation labels for LinkedGeoData took 1.6783185005187988s
Accuracy | Check White space in annotation for LinkedGeoData took 0.15547680854797363s
Accuracy | Check Datatype consistency for LinkedGeoData took 0.13432812690734863s
Consistency | Disjoint class check for LinkedGeoData took 0.22046685218811035s
Consistency | Check Misplaced properties for LinkedGeoData took 182.00850892066956s
Consistency | Misplaced classes for LinkedGeoData took 0.6334366798400879s
Consistency | Check Ontology hijacking for LinkedGeoData took 3.5753679275512695s
Consistency | Check Invalid usage of undefined classes for LinkedGeoData took 1.2316961288452148s
Consistency | Check Invalid usage of undefined properties for LinkedGeoData took 181.64888906478882s
Conciseness | Check Extensional conciseness for LinkedGeoData took 0.14709758758544922s
Conciseness | Check Intensional conciseness for LinkedGeoData took 0.5094583034515381s
Security | Sign check for LinkedGeoData took 0.7303366661071777s
Availability | Check URIs Dereferenciability for LinkedGeoData took 23.337867975234985s
Completeness | Calculation of interlinking completeness for LinkedGeoData took 0.6468348503112793s
Reputation | Calculation of the PageRank for LinkedGeoData took 0.02185821533203125s
Interlinking | Calculation of Degree of Connection for LinkedGeoData took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for LinkedGeoData took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData took 0.00018215179443359375s
Interoperability | Check the re-using of existing vocabs for LinkedGeoData took 1305.0149092674255s
Believability | Calculation of trust value for LinkedGeoData took 1.52587890625e-05s
INFO | --- Analysis for linkedgeodata took 3582.5107531547546s
Availability | SPARQL endpoint availability check for LinkedLCCN took 0.9683260917663574s
Availability | VoID file availability check for LinkedLCCN took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for LinkedLCCN took 0.29515743255615234s
Reputation | Calculation of the PageRank for LinkedLCCN took 0.020889759063720703s
Interlinking | Calculation of Degree of Connection for LinkedLCCN took 1.52587890625e-05s
Interlinking | Calculation of Centrality for LinkedLCCN took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for LinkedLCCN took 0.00011229515075683594s
Believability | Calculation of trust value for LinkedLCCN took 1.0728836059570312e-05s
INFO | --- Analysis for linkedlccn took 18.44725227355957s
Availability | SPARQL endpoint availability check for LinkedMarkMail took 4.363059997558594e-05s
Availability | VoID file availability check for LinkedMarkMail took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for LinkedMarkMail took 0.26958489418029785s
Reputation | Calculation of the PageRank for LinkedMarkMail took 0.022255420684814453s
Interlinking | Calculation of Degree of Connection for LinkedMarkMail took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for LinkedMarkMail took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for LinkedMarkMail took 4.076957702636719e-05s
Believability | Calculation of trust value for LinkedMarkMail took 1.049041748046875e-05s
INFO | --- Analysis for linkedmarkmail took 2.58701229095459s
Availability | SPARQL endpoint availability check for Linked Movie DataBase took 40.722721099853516s
Availability | VoID file availability check for Linked Movie DataBase took 0.0006291866302490234s
Completeness | Calculation of interlinking completeness for Linked Movie DataBase took 0.2776923179626465s
Reputation | Calculation of the PageRank for Linked Movie DataBase took 0.020639896392822266s
Interlinking | Calculation of Degree of Connection for Linked Movie DataBase took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Linked Movie DataBase took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Linked Movie DataBase took 0.00013065338134765625s
Believability | Calculation of trust value for Linked Movie DataBase took 1.239776611328125e-05s
INFO | --- Analysis for linkedmdb took 133.49598574638367s
Availability | SPARQL endpoint availability check for LinkedSpending took 0.5973024368286133s
Availability | VoID file availability check for LinkedSpending took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for LinkedSpending took 0.26708269119262695s
Reputation | Calculation of the PageRank for LinkedSpending took 0.02053999900817871s
Interlinking | Calculation of Degree of Connection for LinkedSpending took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LinkedSpending took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for LinkedSpending took 7.05718994140625e-05s
Believability | Calculation of trust value for LinkedSpending took 1.1205673217773438e-05s
INFO | --- Analysis for linkedspending took 4.034214019775391s
Availability | SPARQL endpoint availability check for LinkLion - A Link Repository for the Web of Data took 0.0628666877746582s
Availability | VoID file availability check for LinkLion - A Link Repository for the Web of Data took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for LinkLion - A Link Repository for the Web of Data took 0.26410865783691406s
Reputation | Calculation of the PageRank for LinkLion - A Link Repository for the Web of Data took 0.021671772003173828s
Interlinking | Calculation of Degree of Connection for LinkLion - A Link Repository for the Web of Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for LinkLion - A Link Repository for the Web of Data took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for LinkLion - A Link Repository for the Web of Data took 0.00010609626770019531s
Believability | Calculation of trust value for LinkLion - A Link Repository for the Web of Data took 1.1205673217773438e-05s
INFO | --- Analysis for linklion took 2.4861690998077393s
Availability | SPARQL endpoint availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 26.734904289245605s
Availability | VoID file availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for Lista de  Encabezamientos de Materia as Linked Open Data took 0.2637491226196289s
Reputation | Calculation of the PageRank for Lista de  Encabezamientos de Materia as Linked Open Data took 0.020699024200439453s
Interlinking | Calculation of Degree of Connection for Lista de  Encabezamientos de Materia as Linked Open Data took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Lista de  Encabezamientos de Materia as Linked Open Data took 5.507469177246094e-05s
Believability | Calculation of trust value for Lista de  Encabezamientos de Materia as Linked Open Data took 9.298324584960938e-06s
INFO | --- Analysis for lista-encabezamientos-materia took 30.896910667419434s
Availability | SPARQL endpoint availability check for lobid-organisations took 0.9436721801757812s
Availability | VoID file availability check for lobid-organisations took 0.0006272792816162109s
Completeness | Calculation of interlinking completeness for lobid-organisations took 0.2760887145996094s
Reputation | Calculation of the PageRank for lobid-organisations took 0.02138829231262207s
Interlinking | Calculation of Degree of Connection for lobid-organisations took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for lobid-organisations took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for lobid-organisations took 0.00010085105895996094s
Believability | Calculation of trust value for lobid-organisations took 1.0967254638671875e-05s
INFO | --- Analysis for lobid-organisations took 4.962364673614502s
Availability | SPARQL endpoint availability check for lobid-Bibliographic Resources took 0.6516163349151611s
Availability | VoID file availability check for lobid-Bibliographic Resources took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for lobid-Bibliographic Resources took 0.2743396759033203s
Reputation | Calculation of the PageRank for lobid-Bibliographic Resources took 0.020556211471557617s
Interlinking | Calculation of Degree of Connection for lobid-Bibliographic Resources took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for lobid-Bibliographic Resources took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for lobid-Bibliographic Resources took 9.822845458984375e-05s
Believability | Calculation of trust value for lobid-Bibliographic Resources took 9.298324584960938e-06s
INFO | --- Analysis for lobid-resources took 6.669327735900879s
Availability | SPARQL endpoint availability check for Linked Open Colors took 8.535385131835938e-05s
Availability | VoID file availability check for Linked Open Colors took 0.0012264251708984375s
Completeness | Calculation of interlinking completeness for Linked Open Colors took 0.26894068717956543s
Reputation | Calculation of the PageRank for Linked Open Colors took 0.020756006240844727s
Interlinking | Calculation of Degree of Connection for Linked Open Colors took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Linked Open Colors took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Linked Open Colors took 7.43865966796875e-05s
Believability | Calculation of trust value for Linked Open Colors took 1.0013580322265625e-05s
INFO | --- Analysis for loc took 6.761118650436401s
Availability | SPARQL endpoint availability check for Location Ontology took 8.416175842285156e-05s
Availability | VoID file availability check for Location Ontology took 0.0005497932434082031s
Completeness | Calculation of interlinking completeness for Location Ontology took 0.2739739418029785s
Reputation | Calculation of the PageRank for Location Ontology took 0.020743608474731445s
Interlinking | Calculation of Degree of Connection for Location Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Location Ontology took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Location Ontology took 3.1948089599609375e-05s
Believability | Calculation of trust value for Location Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for Location_Ontology took 4.111780405044556s
Availability | SPARQL endpoint availability check for Linked Open Computer Vision took 4.458427429199219e-05s
Availability | VoID file availability check for Linked Open Computer Vision took 0.0005705356597900391s
Completeness | Calculation of interlinking completeness for Linked Open Computer Vision took 0.2656526565551758s
Reputation | Calculation of the PageRank for Linked Open Computer Vision took 0.0207517147064209s
Interlinking | Calculation of Degree of Connection for Linked Open Computer Vision took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Linked Open Computer Vision took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Linked Open Computer Vision took 4.029273986816406e-05s
Believability | Calculation of trust value for Linked Open Computer Vision took 1.0251998901367188e-05s
INFO | --- Analysis for locv took 33.45650362968445s
Availability | SPARQL endpoint availability check for LOD-a-lot took 0.6847062110900879s
Availability | VoID file availability check for LOD-a-lot took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for LOD-a-lot took 0.27879810333251953s
Reputation | Calculation of the PageRank for LOD-a-lot took 0.020541906356811523s
Interlinking | Calculation of Degree of Connection for LOD-a-lot took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for LOD-a-lot took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for LOD-a-lot took 3.314018249511719e-05s
Believability | Calculation of trust value for LOD-a-lot took 1.0251998901367188e-05s
INFO | --- Analysis for lod-a-lot took 4.079627513885498s
Availability | SPARQL endpoint availability check for LOD2 Project Wiki took 4.100799560546875e-05s
Availability | VoID file availability check for LOD2 Project Wiki took 0.00044989585876464844s
Completeness | Calculation of interlinking completeness for LOD2 Project Wiki took 0.27171778678894043s
Reputation | Calculation of the PageRank for LOD2 Project Wiki took 0.02076101303100586s
Interlinking | Calculation of Degree of Connection for LOD2 Project Wiki took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for LOD2 Project Wiki took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for LOD2 Project Wiki took 8.726119995117188e-05s
Believability | Calculation of trust value for LOD2 Project Wiki took 1.0251998901367188e-05s
INFO | --- Analysis for lod2-project-wiki took 3.217728614807129s
Availability | SPARQL endpoint availability check for LODAC BDLS took 2.6185755729675293s
Availability | VoID file availability check for LODAC BDLS took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for LODAC BDLS took 0.2744596004486084s
Reputation | Calculation of the PageRank for LODAC BDLS took 0.021867990493774414s
Interlinking | Calculation of Degree of Connection for LODAC BDLS took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for LODAC BDLS took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for LODAC BDLS took 7.200241088867188e-05s
Believability | Calculation of trust value for LODAC BDLS took 1.3113021850585938e-05s
INFO | --- Analysis for lodac-bdls took 13.518621444702148s
Availability | SPARQL endpoint availability check for lofd took 0.11788511276245117s
Availability | VoID file availability check for lofd took 0.0004527568817138672s
Completeness | Calculation of interlinking completeness for lofd took 0.3113398551940918s
Reputation | Calculation of the PageRank for lofd took 0.021895885467529297s
Interlinking | Calculation of Degree of Connection for lofd took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for lofd took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for lofd took 3.075599670410156e-05s
Believability | Calculation of trust value for lofd took 1.0251998901367188e-05s
INFO | --- Analysis for lofd took 2.6257472038269043s
Availability | SPARQL endpoint availability check for Linking Italian University Statistics Project took 271.29425382614136s
Availability | VoID file availability check for Linking Italian University Statistics Project took 0.0007631778717041016s
Completeness | Calculation of interlinking completeness for Linking Italian University Statistics Project took 0.3072657585144043s
Reputation | Calculation of the PageRank for Linking Italian University Statistics Project took 0.020673513412475586s
Interlinking | Calculation of Degree of Connection for Linking Italian University Statistics Project took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linking Italian University Statistics Project took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Linking Italian University Statistics Project took 6.008148193359375e-05s
Believability | Calculation of trust value for Linking Italian University Statistics Project took 7.62939453125e-06s
INFO | --- Analysis for loius took 585.3457305431366s
Availability | SPARQL endpoint availability check for The London Gazette - Gazettes Data took 0.9194707870483398s
Availability | VoID file availability check for The London Gazette - Gazettes Data took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for The London Gazette - Gazettes Data took 0.2798769474029541s
Reputation | Calculation of the PageRank for The London Gazette - Gazettes Data took 0.022282123565673828s
Interlinking | Calculation of Degree of Connection for The London Gazette - Gazettes Data took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for The London Gazette - Gazettes Data took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for The London Gazette - Gazettes Data took 5.8650970458984375e-05s
Believability | Calculation of trust value for The London Gazette - Gazettes Data took 8.344650268554688e-06s
INFO | --- Analysis for london-gazette took 4.092334032058716s
Availability | SPARQL endpoint availability check for Weather Stations took 8.749961853027344e-05s
Availability | VoID file availability check for Weather Stations took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for Weather Stations took 0.25735902786254883s
Reputation | Calculation of the PageRank for Weather Stations took 0.02060723304748535s
Interlinking | Calculation of Degree of Connection for Weather Stations took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Weather Stations took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Weather Stations took 8.20159912109375e-05s
Believability | Calculation of trust value for Weather Stations took 7.867813110351562e-06s
INFO | --- Analysis for los_metar took 7.796350479125977s
Availability | SPARQL endpoint availability check for Lotico took 0.7454962730407715s
Availability | VoID file availability check for Lotico took 0.0003714561462402344s
Completeness | Calculation of interlinking completeness for Lotico took 0.2697288990020752s
Reputation | Calculation of the PageRank for Lotico took 0.02079319953918457s
Interlinking | Calculation of Degree of Connection for Lotico took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Lotico took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Lotico took 8.416175842285156e-05s
Believability | Calculation of trust value for Lotico took 1.1682510375976562e-05s
INFO | --- Analysis for lotico took 5.725285053253174s
Availability | SPARQL endpoint availability check for Lower Layer Super Output Areas took 0.3820672035217285s
Availability | VoID file availability check for Lower Layer Super Output Areas took 0.00042939186096191406s
Extra | Recovery of all triples for Lower Layer Super Output Areas took 0.9487876892089844s
Performance | Total latancy measurement for Lower Layer Super Output Areas took 0.771658182144165s
Amount of data | Number of triples check for Lower Layer Super Output Areas took 0.2805459499359131s
Interoperability | New terms check for Lower Layer Super Output Areas took 1.5706613063812256s
Versatility | Languages check for Lower Layer Super Output Areas took 0.6514415740966797s
Interpretability | Number of blank nodes check for Lower Layer Super Output Areas took 30.15667700767517s
Security | Check HTTPS for Lower Layer Super Output Areas took 0.16077899932861328s
Interpretability | RDF structures check for Lower Layer Super Output Areas took 0.28728342056274414s
Versatility | Serialization formats check for Lower Layer Super Output Areas took 0.12284588813781738s
Availability | RDF dump link check for Lower Layer Super Output Areas took 46.22471261024475s
License | MR license check for Lower Layer Super Output Areas took 0.27968692779541016s
License | HR license check for Lower Layer Super Output Areas took 30.15668773651123s
Amount of data | Number of property check for Lower Layer Super Output Areas took 0.13182592391967773s
Understandability | Number of label check for Lower Layer Super Output Areas took 0.220078706741333s
Understandability | URI regex check for Lower Layer Super Output Areas took 0.5862674713134766s
Understandability | Vocabs check for Lower Layer Super Output Areas took 0.18308115005493164s
Verifiability | Authors check for Lower Layer Super Output Areas took 0.12184000015258789s
Verifiability | Publishers check for Lower Layer Super Output Areas took 0.2830536365509033s
Performance | Throughput check for Lower Layer Super Output Areas took 12.593889951705933s
Amount of data | Check the number of entities for Lower Layer Super Output Areas took 6.699562072753906e-05s
Verifiability | Contribs. check for Lower Layer Super Output Areas took 0.7258179187774658s
Interlinking | sameAs chians check for Lower Layer Super Output Areas took 0.296522855758667s
Interlinking | skos check for Lower Layer Super Output Areas took 0.3788127899169922s
Interlinking | skos check for Lower Layer Super Output Areas took 0.12885189056396484s
Timeliness | dataset update frequency check for Lower Layer Super Output Areas took 0.20165395736694336s
Currency | Creation date check for Lower Layer Super Output Areas took 1.490105390548706s
Currency | Modification date check for Lower Layer Super Output Areas took 0.3068692684173584s
Rep.Conc. | URIs length for Lower Layer Super Output Areas took 2.5668232440948486s
Interoperability | New vocabularies check for Lower Layer Super Output Areas took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Lower Layer Super Output Areas took 0.12857365608215332s
Accuracy | Check Functional Property for Lower Layer Super Output Areas took 1.0288028717041016s
Accuracy | Check Inverse Functional Property for Lower Layer Super Output Areas took 0.13048696517944336s
Consistency | Disjoint class check for Lower Layer Super Output Areas took 0.384202241897583s
Consistency | Check Misplaced properties for Lower Layer Super Output Areas took 0.8436248302459717s
Consistency | Check Ontology hijacking for Lower Layer Super Output Areas took 3.067462682723999s
Consistency | Check Invalid usage of undefined properties for Lower Layer Super Output Areas took 1.4465975761413574s
Conciseness | Check Extensional conciseness for Lower Layer Super Output Areas took 0.00013875961303710938s
Conciseness | Check Intensional conciseness for Lower Layer Super Output Areas took 0.522986888885498s
Security | Sign check for Lower Layer Super Output Areas took 0.20288944244384766s
Completeness | Calculation of interlinking completeness for Lower Layer Super Output Areas took 0.2871978282928467s
Reputation | Calculation of the PageRank for Lower Layer Super Output Areas took 0.02055215835571289s
Interlinking | Calculation of Degree of Connection for Lower Layer Super Output Areas took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Lower Layer Super Output Areas took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Lower Layer Super Output Areas took 3.600120544433594e-05s
Interoperability | Check the re-using of existing vocabs for Lower Layer Super Output Areas took 9.5367431640625e-07s
Believability | Calculation of trust value for Lower Layer Super Output Areas took 1.0728836059570312e-05s
INFO | --- Analysis for lower-layer-super-output-areas took 269.136287689209s
Availability | SPARQL endpoint availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.6286451816558838s
Availability | VoID file availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0005846023559570312s
Extra | Recovery of all triples for Polish Land Parcel Information System (LPIS) dataset @PSNC took 119.57810235023499s
Performance | Total latancy measurement for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.8749868869781494s
Amount of data | Number of triples check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 9.473904371261597s
Interoperability | New terms check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 14.252557754516602s
Versatility | Languages check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.21696877479553s
Interpretability | Number of blank nodes check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.4195165634155273s
Interpretability | RDF structures check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2827603816986084s
Versatility | Serialization formats check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 11.505131483078003s
Availability | RDF dump link check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2457277774810791s
License | MR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.46773791313171387s
License | HR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.2368712425232s
Amount of data | Number of property check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.1816856861114502s
Understandability | Number of label check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.04062557220459s
Understandability | URI regex check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.7137608528137207s
Understandability | Vocabs check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.332294225692749s
Verifiability | Authors check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.1800837516784668s
Verifiability | Publishers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.21885061264038086s
Performance | Throughput check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 10.606216192245483s
Amount of data | Check the number of entities for Polish Land Parcel Information System (LPIS) dataset @PSNC took 3.266334533691406e-05s
Verifiability | Contribs. check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.17728447914123535s
Interlinking | sameAs chians check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.17924880981445312s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.46274328231811523s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.42011165618896484s
Timeliness | dataset update frequency check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 7.15866231918335s
Currency | Creation date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.4205033779144287s
Currency | Modification date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.23360443115234375s
Rep.Conc. | URIs length for Polish Land Parcel Information System (LPIS) dataset @PSNC took 157.59348797798157s
Interoperability | New vocabularies check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.18173646926879883s
Accuracy | Check Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.3605635166168213s
Accuracy | Check Inverse Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.3543257713317871s
Accuracy | Check Empty annotation labels for Polish Land Parcel Information System (LPIS) dataset @PSNC took 34.344643354415894s
Accuracy | Check White space in annotation for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.6329076290130615s
Accuracy | Check Datatype consistency for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.6140642166137695s
Consistency | Disjoint class check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.17645573616027832s
Consistency | Check Misplaced properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 87.24858140945435s
Consistency | Misplaced classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.22230839729309s
Consistency | Check Ontology hijacking for Polish Land Parcel Information System (LPIS) dataset @PSNC took 30.247270107269287s
Consistency | Check Invalid usage of undefined classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.3262009620666504s
Consistency | Check Invalid usage of undefined properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 87.6698899269104s
Conciseness | Check Extensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.7268192768096924s
Conciseness | Check Intensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5598955154418945s
Security | Sign check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.7746701240539551s
Availability | Check URIs Dereferenciability for Polish Land Parcel Information System (LPIS) dataset @PSNC took 22.732963800430298s
Completeness | Calculation of interlinking completeness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.6405134201049805s
Reputation | Calculation of the PageRank for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.021033287048339844s
Interlinking | Calculation of Degree of Connection for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.6702880859375e-05s
Interlinking | Calculation of Centrality for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.00010275840759277344s
Interoperability | Check the re-using of existing vocabs for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.1920928955078125e-05s
INFO | --- Analysis for LPIS_(Poland) took 2334.2106103897095s
Availability | SPARQL endpoint availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.18065142631530762s
Availability | VoID file availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0004942417144775391s
Extra | Recovery of all triples for Land parcel dataset (LPIS) from Czech Republic @PSNC took 117.14444065093994s
Performance | Total latancy measurement for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.884521484375s
Amount of data | Number of triples check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 9.11666226387024s
Interoperability | New terms check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 14.034887790679932s
Versatility | Languages check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.1930401325226s
Interpretability | Number of blank nodes check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.2748451232910156s
Interpretability | RDF structures check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2584085464477539s
Versatility | Serialization formats check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.674514055252075s
Availability | RDF dump link check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2834923267364502s
License | MR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.6147768497467041s
License | HR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.17833852767944s
Amount of data | Number of property check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.18496370315551758s
Understandability | Number of label check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.4797089099884033s
Understandability | URI regex check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.8707599639892578s
Understandability | Vocabs check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.40941524505615234s
Verifiability | Authors check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.1739795207977295s
Verifiability | Publishers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.22269678115844727s
Performance | Throughput check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 10.635526895523071s
Amount of data | Check the number of entities for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.296966552734375e-05s
Verifiability | Contribs. check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.18018054962158203s
Interlinking | sameAs chians check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.18449950218200684s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.41852402687072754s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.40545201301574707s
Timeliness | dataset update frequency check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 4.559100866317749s
Currency | Creation date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.42719268798828125s
Currency | Modification date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.22427749633789062s
Rep.Conc. | URIs length for Land parcel dataset (LPIS) from Czech Republic @PSNC took 155.079491853714s
Interoperability | New vocabularies check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.18186259269714355s
Accuracy | Check Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.36417412757873535s
Accuracy | Check Inverse Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.38013148307800293s
Accuracy | Check Empty annotation labels for Land parcel dataset (LPIS) from Czech Republic @PSNC took 44.19602417945862s
Accuracy | Check White space in annotation for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.63100528717041s
Accuracy | Check Datatype consistency for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.596407413482666s
Consistency | Disjoint class check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.1791248321533203s
Consistency | Check Misplaced properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 86.19567680358887s
Consistency | Misplaced classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.337631940841675s
Consistency | Check Ontology hijacking for Land parcel dataset (LPIS) from Czech Republic @PSNC took 34.82158422470093s
Consistency | Check Invalid usage of undefined classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.3707149028778076s
Consistency | Check Invalid usage of undefined properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 86.86719822883606s
Conciseness | Check Extensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.76948881149292s
Conciseness | Check Intensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.6465532779693604s
Security | Sign check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.0017743110656738s
Availability | Check URIs Dereferenciability for Land parcel dataset (LPIS) from Czech Republic @PSNC took 13.137326717376709s
Completeness | Calculation of interlinking completeness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.3580183982849121s
Reputation | Calculation of the PageRank for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.021580219268798828s
Interlinking | Calculation of Degree of Connection for Land parcel dataset (LPIS) from Czech Republic @PSNC took 6.175041198730469e-05s
Interlinking | Calculation of Centrality for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Land parcel dataset (LPIS) from Czech Republic @PSNC took 3.504753112792969e-05s
Interoperability | Check the re-using of existing vocabs for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.430511474609375e-06s
Believability | Calculation of trust value for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.1205673217773438e-05s
INFO | --- Analysis for LPIS_Czech_Republic took 2302.7481927871704s
Availability | SPARQL endpoint availability check for A collection of Authors for LREC2014 and related Workshops took 9.274482727050781e-05s
Availability | VoID file availability check for A collection of Authors for LREC2014 and related Workshops took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for A collection of Authors for LREC2014 and related Workshops took 0.28307676315307617s
Reputation | Calculation of the PageRank for A collection of Authors for LREC2014 and related Workshops took 0.020718097686767578s
Interlinking | Calculation of Degree of Connection for A collection of Authors for LREC2014 and related Workshops took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for A collection of Authors for LREC2014 and related Workshops took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for A collection of Authors for LREC2014 and related Workshops took 3.528594970703125e-05s
Believability | Calculation of trust value for A collection of Authors for LREC2014 and related Workshops took 1.049041748046875e-05s
INFO | --- Analysis for lremap-auth took 3.1552250385284424s
Availability | SPARQL endpoint availability check for LREC2014 and related Workshops took 8.845329284667969e-05s
Availability | VoID file availability check for LREC2014 and related Workshops took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for LREC2014 and related Workshops took 0.2705099582672119s
Reputation | Calculation of the PageRank for LREC2014 and related Workshops took 0.02021932601928711s
Interlinking | Calculation of Degree of Connection for LREC2014 and related Workshops took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LREC2014 and related Workshops took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for LREC2014 and related Workshops took 2.7418136596679688e-05s
Believability | Calculation of trust value for LREC2014 and related Workshops took 1.1205673217773438e-05s
INFO | --- Analysis for lremap-conf took 2.7470476627349854s
Availability | SPARQL endpoint availability check for First not-normalized set of language resources from LREC2014 took 4.1484832763671875e-05s
Availability | VoID file availability check for First not-normalized set of language resources from LREC2014 took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for First not-normalized set of language resources from LREC2014 took 0.2727785110473633s
Reputation | Calculation of the PageRank for First not-normalized set of language resources from LREC2014 took 0.020233869552612305s
Interlinking | Calculation of Degree of Connection for First not-normalized set of language resources from LREC2014 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for First not-normalized set of language resources from LREC2014 took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for First not-normalized set of language resources from LREC2014 took 2.86102294921875e-05s
Believability | Calculation of trust value for First not-normalized set of language resources from LREC2014 took 1.049041748046875e-05s
INFO | --- Analysis for lremap-ri took 2.7485949993133545s
Availability | SPARQL endpoint availability check for A collection of Submissions for LREC2014 and related Workshops took 4.1961669921875e-05s
Availability | VoID file availability check for A collection of Submissions for LREC2014 and related Workshops took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for A collection of Submissions for LREC2014 and related Workshops took 0.26693153381347656s
Reputation | Calculation of the PageRank for A collection of Submissions for LREC2014 and related Workshops took 0.021210670471191406s
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.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for A collection of Submissions for LREC2014 and related Workshops took 2.9325485229492188e-05s
Believability | Calculation of trust value for A collection of Submissions for LREC2014 and related Workshops took 1.0251998901367188e-05s
INFO | --- Analysis for lremap-sub took 2.735421657562256s
Availability | SPARQL endpoint availability check for LSQ took 8.821487426757812e-05s
Availability | VoID file availability check for LSQ took 0.0006763935089111328s
Completeness | Calculation of interlinking completeness for LSQ took 0.28274011611938477s
Reputation | Calculation of the PageRank for LSQ took 0.020206689834594727s
Interlinking | Calculation of Degree of Connection for LSQ took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LSQ took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for LSQ took 2.8133392333984375e-05s
Believability | Calculation of trust value for LSQ took 1.1205673217773438e-05s
INFO | --- Analysis for lsq took 3.4980108737945557s
Availability | SPARQL endpoint availability check for Lucani Pharsalia in LiLa took 0.5647130012512207s
Availability | VoID file availability check for Lucani Pharsalia in LiLa took 0.00058746337890625s
Completeness | Calculation of interlinking completeness for Lucani Pharsalia in LiLa took 0.2740626335144043s
Reputation | Calculation of the PageRank for Lucani Pharsalia in LiLa took 0.02144646644592285s
Interlinking | Calculation of Degree of Connection for Lucani Pharsalia in LiLa took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Lucani Pharsalia in LiLa took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Lucani Pharsalia in LiLa took 3.981590270996094e-05s
Believability | Calculation of trust value for Lucani Pharsalia in LiLa took 1.1682510375976562e-05s
INFO | --- Analysis for LucaniPharsalia took 4.093838453292847s
Availability | SPARQL endpoint availability check for Linked rules took 8.988380432128906e-05s
Availability | VoID file availability check for Linked rules took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for Linked rules took 0.26169538497924805s
Reputation | Calculation of the PageRank for Linked rules took 0.020258665084838867s
Interlinking | Calculation of Degree of Connection for Linked rules took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked rules took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Linked rules took 2.9087066650390625e-05s
Believability | Calculation of trust value for Linked rules took 1.3589859008789062e-05s
INFO | --- Analysis for Luminaires_senlis took 2.4231791496276855s
Availability | SPARQL endpoint availability check for Microsoft Academic Knowledge Graph took 30.514036655426025s
Availability | VoID file availability check for Microsoft Academic Knowledge Graph took 0.0005383491516113281s
Completeness | Calculation of interlinking completeness for Microsoft Academic Knowledge Graph took 0.2748899459838867s
Reputation | Calculation of the PageRank for Microsoft Academic Knowledge Graph took 0.020397424697875977s
Interlinking | Calculation of Degree of Connection for Microsoft Academic Knowledge Graph took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Microsoft Academic Knowledge Graph took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Microsoft Academic Knowledge Graph took 4.2438507080078125e-05s
Believability | Calculation of trust value for Microsoft Academic Knowledge Graph took 1.2874603271484375e-05s
INFO | --- Analysis for makg took 64.13318467140198s
Availability | SPARQL endpoint availability check for Manchester University Reading Lists took 0.00010657310485839844s
Availability | VoID file availability check for Manchester University Reading Lists took 0.0005476474761962891s
Completeness | Calculation of interlinking completeness for Manchester University Reading Lists took 0.27406835556030273s
Reputation | Calculation of the PageRank for Manchester University Reading Lists took 0.021800994873046875s
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.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Manchester University Reading Lists took 3.4332275390625e-05s
Believability | Calculation of trust value for Manchester University Reading Lists took 1.0251998901367188e-05s
INFO | --- Analysis for manchester-university-reading-lists took 4.985107660293579s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 8.726119995117188e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.27077341079711914s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.02188730239868164s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0010349750518798828s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 3.3855438232421875e-05s
Believability | Calculation of trust value for engineering equipment ontology took 1.1205673217773438e-05s
INFO | --- Analysis for manish took 2.418985605239868s
Availability | SPARQL endpoint availability check for MARC Codes List took 8.702278137207031e-05s
Availability | VoID file availability check for MARC Codes List took 0.0006029605865478516s
Completeness | Calculation of interlinking completeness for MARC Codes List took 0.26401281356811523s
Reputation | Calculation of the PageRank for MARC Codes List took 0.021525859832763672s
Interlinking | Calculation of Degree of Connection for MARC Codes List took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MARC Codes List took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for MARC Codes List took 0.00012087821960449219s
Believability | Calculation of trust value for MARC Codes List took 1.0013580322265625e-05s
INFO | --- Analysis for marc-codes took 13.547011375427246s
Availability | SPARQL endpoint availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 8.654594421386719e-05s
Availability | VoID file availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0005903244018554688s
Completeness | Calculation of interlinking completeness for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.9326810836791992s
Reputation | Calculation of the PageRank for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.020387887954711914s
Interlinking | Calculation of Degree of Connection for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 3.838539123535156e-05s
Believability | Calculation of trust value for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 9.775161743164062e-06s
INFO | --- Analysis for masc took 6.4488866329193115s
Availability | SPARQL endpoint availability check for MASC-BN-NIF took 8.869171142578125e-05s
Availability | VoID file availability check for MASC-BN-NIF took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for MASC-BN-NIF took 0.2639448642730713s
Reputation | Calculation of the PageRank for MASC-BN-NIF took 0.020461082458496094s
Interlinking | Calculation of Degree of Connection for MASC-BN-NIF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MASC-BN-NIF took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for MASC-BN-NIF took 4.00543212890625e-05s
Believability | Calculation of trust value for MASC-BN-NIF took 1.1920928955078125e-05s
INFO | --- Analysis for masc-bn-nif took 2.5147194862365723s
Availability | SPARQL endpoint availability check for Mass Observation Archive catalogue took 1.5940196514129639s
Availability | VoID file availability check for Mass Observation Archive catalogue took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for Mass Observation Archive catalogue took 0.2605447769165039s
Reputation | Calculation of the PageRank for Mass Observation Archive catalogue took 0.02136707305908203s
Interlinking | Calculation of Degree of Connection for Mass Observation Archive catalogue took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Mass Observation Archive catalogue took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Mass Observation Archive catalogue took 2.9325485229492188e-05s
Believability | Calculation of trust value for Mass Observation Archive catalogue took 1.1920928955078125e-05s
INFO | --- Analysis for massobservationarchivecatalogue took 4.083654880523682s
Availability | SPARQL endpoint availability check for medline took 8.7738037109375e-05s
Availability | VoID file availability check for medline took 0.0003521442413330078s
Completeness | Calculation of interlinking completeness for medline took 0.27631163597106934s
Reputation | Calculation of the PageRank for medline took 0.020544767379760742s
Interlinking | Calculation of Degree of Connection for medline took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for medline took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for medline took 3.504753112792969e-05s
Believability | Calculation of trust value for medline took 1.0728836059570312e-05s
INFO | --- Analysis for medline took 7.082319736480713s
Availability | SPARQL endpoint availability check for mEducator: Linked Educational Resources took 1.4447996616363525s
Availability | VoID file availability check for mEducator: Linked Educational Resources took 0.0005640983581542969s
Completeness | Calculation of interlinking completeness for mEducator: Linked Educational Resources took 0.26831650733947754s
Reputation | Calculation of the PageRank for mEducator: Linked Educational Resources took 0.020853281021118164s
Interlinking | Calculation of Degree of Connection for mEducator: Linked Educational Resources took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for mEducator: Linked Educational Resources took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for mEducator: Linked Educational Resources took 6.532669067382812e-05s
Believability | Calculation of trust value for mEducator: Linked Educational Resources took 1.0013580322265625e-05s
INFO | --- Analysis for meducator took 11.166555643081665s
Availability | SPARQL endpoint availability check for MetaShare metadata model took 4.124641418457031e-05s
Availability | VoID file availability check for MetaShare metadata model took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for MetaShare metadata model took 0.2618560791015625s
Reputation | Calculation of the PageRank for MetaShare metadata model took 0.021869182586669922s
Interlinking | Calculation of Degree of Connection for MetaShare metadata model took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MetaShare metadata model took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for MetaShare metadata model took 6.866455078125e-05s
Believability | Calculation of trust value for MetaShare metadata model took 1.0967254638671875e-05s
INFO | --- Analysis for metashare took 2.499624729156494s
Availability | SPARQL endpoint availability check for MExiCo took 4.076957702636719e-05s
Availability | VoID file availability check for MExiCo took 0.0006349086761474609s
Completeness | Calculation of interlinking completeness for MExiCo took 0.28227972984313965s
Reputation | Calculation of the PageRank for MExiCo took 0.02092719078063965s
Interlinking | Calculation of Degree of Connection for MExiCo took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for MExiCo took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for MExiCo took 5.793571472167969e-05s
Believability | Calculation of trust value for MExiCo took 1.239776611328125e-05s
INFO | --- Analysis for mexico took 22.98247742652893s
Availability | SPARQL endpoint availability check for Coronavirus dataset took 1.004641056060791s
Availability | VoID file availability check for Coronavirus dataset took 0.00046825408935546875s
Extra | Recovery of all triples for Coronavirus dataset took 5.8795342445373535s
Performance | Total latancy measurement for Coronavirus dataset took 2.4373939037323s
Amount of data | Number of triples check for Coronavirus dataset took 1.160231351852417s
Interoperability | New terms check for Coronavirus dataset took 2.5716745853424072s
Versatility | Languages check for Coronavirus dataset took 60.50018787384033s
Interpretability | Number of blank nodes check for Coronavirus dataset took 3.2034590244293213s
Interpretability | RDF structures check for Coronavirus dataset took 0.5203499794006348s
Versatility | Serialization formats check for Coronavirus dataset took 0.531926155090332s
Availability | RDF dump link check for Coronavirus dataset took 0.48731422424316406s
License | MR license check for Coronavirus dataset took 0.5399820804595947s
License | HR license check for Coronavirus dataset took 43.005204916000366s
Amount of data | Number of property check for Coronavirus dataset took 0.5181324481964111s
Understandability | Number of label check for Coronavirus dataset took 1.3998680114746094s
Understandability | URI regex check for Coronavirus dataset took 0.9735736846923828s
Understandability | Vocabs check for Coronavirus dataset took 0.4938232898712158s
Verifiability | Authors check for Coronavirus dataset took 0.538661003112793s
Verifiability | Publishers check for Coronavirus dataset took 0.4888124465942383s
Performance | Throughput check for Coronavirus dataset took 14.464352369308472s
Amount of data | Check the number of entities for Coronavirus dataset took 6.628036499023438e-05s
Verifiability | Contribs. check for Coronavirus dataset took 0.48963236808776855s
Interlinking | sameAs chians check for Coronavirus dataset took 0.5135898590087891s
Interlinking | skos check for Coronavirus dataset took 0.5295028686523438s
Interlinking | skos check for Coronavirus dataset took 0.4856572151184082s
Timeliness | dataset update frequency check for Coronavirus dataset took 0.4933609962463379s
Currency | Creation date check for Coronavirus dataset took 0.9941952228546143s
Currency | Modification date check for Coronavirus dataset took 1.0035731792449951s
Rep.Conc. | URIs length for Coronavirus dataset took 8.834587097167969s
Interoperability | New vocabularies check for Coronavirus dataset took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Coronavirus dataset took 0.5072770118713379s
Accuracy | Check Functional Property for Coronavirus dataset took 0.7570204734802246s
Accuracy | Check Inverse Functional Property for Coronavirus dataset took 0.7324843406677246s
Accuracy | Check Empty annotation labels for Coronavirus dataset took 2.1056771278381348s
Accuracy | Check White space in annotation for Coronavirus dataset took 0.02208423614501953s
Accuracy | Check Datatype consistency for Coronavirus dataset took 0.028117656707763672s
Consistency | Disjoint class check for Coronavirus dataset took 1.1102321147918701s
Consistency | Check Misplaced properties for Coronavirus dataset took 7.580899000167847s
Consistency | Misplaced classes for Coronavirus dataset took 0.6012048721313477s
Consistency | Check Ontology hijacking for Coronavirus dataset took 3.304530382156372s
Consistency | Check Invalid usage of undefined classes for Coronavirus dataset took 1.2679626941680908s
Consistency | Check Invalid usage of undefined properties for Coronavirus dataset took 6.539958953857422s
Conciseness | Check Extensional conciseness for Coronavirus dataset took 0.03442025184631348s
Conciseness | Check Intensional conciseness for Coronavirus dataset took 0.5117402076721191s
Security | Sign check for Coronavirus dataset took 0.5170223712921143s
Availability | Check URIs Dereferenciability for Coronavirus dataset took 2982.658802509308s
Completeness | Calculation of interlinking completeness for Coronavirus dataset took 0.6019136905670166s
Reputation | Calculation of the PageRank for Coronavirus dataset took 0.021688461303710938s
Interlinking | Calculation of Degree of Connection for Coronavirus dataset took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Coronavirus dataset took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Coronavirus dataset took 6.628036499023438e-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 9.775161743164062e-06s
INFO | --- Analysis for micro-coronavirus took 3224.548284292221s
Availability | SPARQL endpoint availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 8.821487426757812e-05s
Availability | VoID file availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.27377891540527344s
Reputation | Calculation of the PageRank for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.020340681076049805s
Interlinking | Calculation of Degree of Connection for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.00010967254638671875s
Believability | Calculation of trust value for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 1.1920928955078125e-05s
INFO | --- Analysis for miguiadeviajes-gnoss took 5.163148403167725s
Availability | SPARQL endpoint availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 8.940696716308594e-05s
Availability | VoID file availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.27562546730041504s
Reputation | Calculation of the PageRank for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.020671606063842773s
Interlinking | Calculation of Degree of Connection for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.00010895729064941406s
Believability | Calculation of trust value for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 9.298324584960938e-06s
INFO | --- Analysis for mismuseos-gnoss took 7.946765661239624s
Availability | SPARQL endpoint availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.23011040687561035s
Availability | VoID file availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.2773771286010742s
Reputation | Calculation of the PageRank for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.022480010986328125s
Interlinking | Calculation of Degree of Connection for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 4.673004150390625e-05s
Believability | Calculation of trust value for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 9.298324584960938e-06s
INFO | --- Analysis for mlsa took 3.093949556350708s
Availability | SPARQL endpoint availability check for Atmospheric Correction of High Resolution Optical Images model took 8.797645568847656e-05s
Availability | VoID file availability check for Atmospheric Correction of High Resolution Optical Images model took 0.0005600452423095703s
Completeness | Calculation of interlinking completeness for Atmospheric Correction of High Resolution Optical Images model took 0.2668161392211914s
Reputation | Calculation of the PageRank for Atmospheric Correction of High Resolution Optical Images model took 0.02057814598083496s
Interlinking | Calculation of Degree of Connection for Atmospheric Correction of High Resolution Optical Images model took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Atmospheric Correction of High Resolution Optical Images model took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Atmospheric Correction of High Resolution Optical Images model took 3.147125244140625e-05s
Believability | Calculation of trust value for Atmospheric Correction of High Resolution Optical Images model took 9.298324584960938e-06s
INFO | --- Analysis for model took 35.04571056365967s
Availability | SPARQL endpoint availability check for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 4.267692565917969e-05s
Availability | VoID file availability check for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.0007028579711914062s
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.26862430572509766s
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.020609378814697266s
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.1920928955078125e-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.0007195472717285156s
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 4.0531158447265625e-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 1.0251998901367188e-05s
INFO | --- Analysis for model1 took 20.298986673355103s
Availability | SPARQL endpoint availability check for MORElab took 0.9310147762298584s
Availability | VoID file availability check for MORElab took 0.00033164024353027344s
Completeness | Calculation of interlinking completeness for MORElab took 0.26711559295654297s
Reputation | Calculation of the PageRank for MORElab took 0.020989179611206055s
Interlinking | Calculation of Degree of Connection for MORElab took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for MORElab took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for MORElab took 8.988380432128906e-05s
Believability | Calculation of trust value for MORElab took 9.5367431640625e-06s
INFO | --- Analysis for morelab took 5.368054389953613s
Availability | SPARQL endpoint availability check for Mathematics Subject Classification took 1.7874367237091064s
Availability | VoID file availability check for Mathematics Subject Classification took 0.0005457401275634766s
Completeness | Calculation of interlinking completeness for Mathematics Subject Classification took 0.2643251419067383s
Reputation | Calculation of the PageRank for Mathematics Subject Classification took 0.02070021629333496s
Interlinking | Calculation of Degree of Connection for Mathematics Subject Classification took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Mathematics Subject Classification took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Mathematics Subject Classification took 9.012222290039062e-05s
Believability | Calculation of trust value for Mathematics Subject Classification took 9.775161743164062e-06s
INFO | --- Analysis for msc took 16.168225526809692s
Availability | SPARQL endpoint availability check for Multext-East took 8.559226989746094e-05s
Availability | VoID file availability check for Multext-East took 0.0004334449768066406s
Completeness | Calculation of interlinking completeness for Multext-East took 0.26663684844970703s
Reputation | Calculation of the PageRank for Multext-East took 0.021237850189208984s
Interlinking | Calculation of Degree of Connection for Multext-East took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Multext-East took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Multext-East took 3.695487976074219e-05s
Believability | Calculation of trust value for Multext-East took 1.2636184692382812e-05s
INFO | --- Analysis for multext-east took 2.468982219696045s
Availability | SPARQL endpoint availability check for Multimedia Lab took 4.1484832763671875e-05s
Availability | VoID file availability check for Multimedia Lab took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for Multimedia Lab took 0.26372241973876953s
Reputation | Calculation of the PageRank for Multimedia Lab took 0.020595788955688477s
Interlinking | Calculation of Degree of Connection for Multimedia Lab took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Multimedia Lab took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Multimedia Lab took 3.5762786865234375e-05s
Believability | Calculation of trust value for Multimedia Lab took 1.0728836059570312e-05s
INFO | --- Analysis for multimedia-lab took 2.4897477626800537s
Availability | SPARQL endpoint availability check for Muninn World War I took 1.6565628051757812s
Availability | VoID file availability check for Muninn World War I took 0.0006377696990966797s
Completeness | Calculation of interlinking completeness for Muninn World War I took 0.2724142074584961s
Reputation | Calculation of the PageRank for Muninn World War I took 0.02059340476989746s
Interlinking | Calculation of Degree of Connection for Muninn World War I took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Muninn World War I took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Muninn World War I took 8.249282836914062e-05s
Believability | Calculation of trust value for Muninn World War I took 9.775161743164062e-06s
INFO | --- Analysis for muninn-world-war-i took 10.574397325515747s
Availability | SPARQL endpoint availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 8.845329284667969e-05s
Availability | VoID file availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.000568389892578125s
Completeness | Calculation of interlinking completeness for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.2644312381744385s
Reputation | Calculation of the PageRank for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.020896196365356445s
Interlinking | Calculation of Degree of Connection for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.00011420249938964844s
Believability | Calculation of trust value for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 9.5367431640625e-06s
INFO | --- Analysis for museosespania-gnoss took 39.74336624145508s
Availability | SPARQL endpoint availability check for Italian Museums took 0.3169236183166504s
Availability | VoID file availability check for Italian Museums took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for Italian Museums took 0.2640345096588135s
Reputation | Calculation of the PageRank for Italian Museums took 0.020679950714111328s
Interlinking | Calculation of Degree of Connection for Italian Museums took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Italian Museums took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Italian Museums took 8.296966552734375e-05s
Believability | Calculation of trust value for Italian Museums took 1.2636184692382812e-05s
INFO | --- Analysis for museums-in-italy took 2.851074457168579s
Availability | SPARQL endpoint availability check for Muziekweb took 0.7627944946289062s
Availability | VoID file availability check for Muziekweb took 0.0006058216094970703s
Extra | Recovery of all triples for Muziekweb took 0.8794350624084473s
Performance | Total latancy measurement for Muziekweb took 1.4580752849578857s
Amount of data | Number of triples check for Muziekweb took 0.28896546363830566s
Interoperability | New terms check for Muziekweb took 1.6160509586334229s
Versatility | Languages check for Muziekweb took 0.3200337886810303s
Interpretability | Number of blank nodes check for Muziekweb took 0.27807044982910156s
Interpretability | RDF structures check for Muziekweb took 0.2886044979095459s
Versatility | Serialization formats check for Muziekweb took 0.30573368072509766s
Availability | RDF dump link check for Muziekweb took 0.2872765064239502s
License | MR license check for Muziekweb took 0.2823607921600342s
License | HR license check for Muziekweb took 0.3154160976409912s
Amount of data | Number of property check for Muziekweb took 0.2854139804840088s
Understandability | Number of label check for Muziekweb took 0.28699612617492676s
Understandability | URI regex check for Muziekweb took 0.5660831928253174s
Understandability | Vocabs check for Muziekweb took 0.28493452072143555s
Verifiability | Authors check for Muziekweb took 0.29686808586120605s
Verifiability | Publishers check for Muziekweb took 0.3165268898010254s
Performance | Throughput check for Muziekweb took 11.493796110153198s
Amount of data | Check the number of entities for Muziekweb took 3.170967102050781e-05s
Verifiability | Contribs. check for Muziekweb took 0.28812575340270996s
Interlinking | sameAs chians check for Muziekweb took 0.28597211837768555s
Interlinking | skos check for Muziekweb took 0.27477455139160156s
Interlinking | skos check for Muziekweb took 0.2886998653411865s
Timeliness | dataset update frequency check for Muziekweb took 0.29328179359436035s
Currency | Creation date check for Muziekweb took 0.569016695022583s
Currency | Modification date check for Muziekweb took 0.5850985050201416s
Rep.Conc. | URIs length for Muziekweb took 0.9868764877319336s
Interoperability | New vocabularies check for Muziekweb took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Muziekweb took 0.29175567626953125s
Accuracy | Check Empty annotation labels for Muziekweb took 0.5803627967834473s
Accuracy | Check White space in annotation for Muziekweb took 0.027698755264282227s
Accuracy | Check Datatype consistency for Muziekweb took 0.028616666793823242s
Consistency | Disjoint class check for Muziekweb took 0.2924540042877197s
Consistency | Check Misplaced properties for Muziekweb took 0.5800776481628418s
Consistency | Check Ontology hijacking for Muziekweb took 1.8206188678741455s
Consistency | Check Invalid usage of undefined classes for Muziekweb took 1.2691423892974854s
Consistency | Check Invalid usage of undefined properties for Muziekweb took 1.550680160522461s
Conciseness | Check Extensional conciseness for Muziekweb took 0.033499956130981445s
Conciseness | Check Intensional conciseness for Muziekweb took 0.2848851680755615s
Security | Sign check for Muziekweb took 0.2752714157104492s
Availability | Check URIs Dereferenciability for Muziekweb took 1807.7949812412262s
Completeness | Calculation of interlinking completeness for Muziekweb took 0.4670374393463135s
Reputation | Calculation of the PageRank for Muziekweb took 0.021114349365234375s
Interlinking | Calculation of Degree of Connection for Muziekweb took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Muziekweb took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Muziekweb took 6.747245788574219e-05s
Interoperability | Check the re-using of existing vocabs for Muziekweb took 1.430511474609375e-06s
Believability | Calculation of trust value for Muziekweb took 1.2874603271484375e-05s
INFO | --- Analysis for muziekweb took 1862.794894695282s
Availability | SPARQL endpoint availability check for myExperiment took 0.4706404209136963s
Availability | VoID file availability check for myExperiment took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for myExperiment took 0.2635509967803955s
Reputation | Calculation of the PageRank for myExperiment took 0.020421504974365234s
Interlinking | Calculation of Degree of Connection for myExperiment took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for myExperiment took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for myExperiment took 9.822845458984375e-05s
Believability | Calculation of trust value for myExperiment took 1.0967254638671875e-05s
INFO | --- Analysis for my-experiment took 4.106084585189819s
Availability | SPARQL endpoint availability check for My Family Lineage took 0.06800365447998047s
Availability | VoID file availability check for My Family Lineage took 0.0003559589385986328s
Completeness | Calculation of interlinking completeness for My Family Lineage took 0.26354432106018066s
Reputation | Calculation of the PageRank for My Family Lineage took 0.020452022552490234s
Interlinking | Calculation of Degree of Connection for My Family Lineage took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for My Family Lineage took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for My Family Lineage took 8.606910705566406e-05s
Believability | Calculation of trust value for My Family Lineage took 1.1444091796875e-05s
INFO | --- Analysis for my-family-lineage took 3.6605193614959717s
Availability | SPARQL endpoint availability check for My ontology test took 1.2523186206817627s
Availability | VoID file availability check for My ontology test took 0.0005300045013427734s
Completeness | Calculation of interlinking completeness for My ontology test took 0.26368117332458496s
Reputation | Calculation of the PageRank for My ontology test took 0.0202333927154541s
Interlinking | Calculation of Degree of Connection for My ontology test took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for My ontology test took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for My ontology test took 2.956390380859375e-05s
Believability | Calculation of trust value for My ontology test took 1.0251998901367188e-05s
INFO | --- Analysis for myontologytest took 3.778545379638672s
Availability | SPARQL endpoint availability check for myopenlink dataspaces took 8.7738037109375e-05s
Availability | VoID file availability check for myopenlink dataspaces took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for myopenlink dataspaces took 0.2645533084869385s
Reputation | Calculation of the PageRank for myopenlink dataspaces took 0.02024102210998535s
Interlinking | Calculation of Degree of Connection for myopenlink dataspaces took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for myopenlink dataspaces took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for myopenlink dataspaces took 0.00010132789611816406s
Believability | Calculation of trust value for myopenlink dataspaces took 1.049041748046875e-05s
INFO | --- Analysis for myopenlink-dataspaces took 2.997586250305176s
Availability | SPARQL endpoint availability check for N-Lex as Linked Data took 5.600085496902466s
Availability | VoID file availability check for N-Lex as Linked Data took 0.0005772113800048828s
Completeness | Calculation of interlinking completeness for N-Lex as Linked Data took 0.2703392505645752s
Reputation | Calculation of the PageRank for N-Lex as Linked Data took 0.021953582763671875s
Interlinking | Calculation of Degree of Connection for N-Lex as Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for N-Lex as Linked Data took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for N-Lex as Linked Data took 7.271766662597656e-05s
Believability | Calculation of trust value for N-Lex as Linked Data took 7.62939453125e-06s
INFO | --- Analysis for n-lex-as-linked-data took 14.719219446182251s
Availability | SPARQL endpoint availability check for NAICS 2007 took 25.597270011901855s
Availability | VoID file availability check for NAICS 2007 took 0.0007619857788085938s
Completeness | Calculation of interlinking completeness for NAICS 2007 took 0.2754828929901123s
Reputation | Calculation of the PageRank for NAICS 2007 took 0.0205233097076416s
Interlinking | Calculation of Degree of Connection for NAICS 2007 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for NAICS 2007 took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for NAICS 2007 took 4.6253204345703125e-05s
Believability | Calculation of trust value for NAICS 2007 took 9.775161743164062e-06s
INFO | --- Analysis for naics-2007 took 124.04488468170166s
Availability | SPARQL endpoint availability check for NAICS 2012 took 24.51980972290039s
Availability | VoID file availability check for NAICS 2012 took 0.0008406639099121094s
Completeness | Calculation of interlinking completeness for NAICS 2012 took 0.2785978317260742s
Reputation | Calculation of the PageRank for NAICS 2012 took 0.020679473876953125s
Interlinking | Calculation of Degree of Connection for NAICS 2012 took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for NAICS 2012 took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for NAICS 2012 took 5.14984130859375e-05s
Believability | Calculation of trust value for NAICS 2012 took 8.106231689453125e-06s
INFO | --- Analysis for naics-2012 took 122.94087290763855s
Availability | SPARQL endpoint availability check for Usernames  took 8.797645568847656e-05s
Availability | VoID file availability check for Usernames  took 0.00023436546325683594s
Completeness | Calculation of interlinking completeness for Usernames  took 0.2716526985168457s
Reputation | Calculation of the PageRank for Usernames  took 0.020894289016723633s
Interlinking | Calculation of Degree of Connection for Usernames  took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Usernames  took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Usernames  took 3.218650817871094e-05s
Believability | Calculation of trust value for Usernames  took 5.245208740234375e-06s
INFO | --- Analysis for Names took 2.433722972869873s
Availability | SPARQL endpoint availability check for Web NDL Authorities - National Diet Library of Japan took 1.1686921119689941s
Availability | VoID file availability check for Web NDL Authorities - National Diet Library of Japan took 0.0006835460662841797s
Extra | Recovery of all triples for Web NDL Authorities - National Diet Library of Japan took 1.3595390319824219s
Performance | Total latancy measurement for Web NDL Authorities - National Diet Library of Japan took 3.434304714202881s
Amount of data | Number of triples check for Web NDL Authorities - National Diet Library of Japan took 12.876074075698853s
Interoperability | New terms check for Web NDL Authorities - National Diet Library of Japan took 15.04031777381897s
Versatility | Languages check for Web NDL Authorities - National Diet Library of Japan took 0.7599678039550781s
Interpretability | Number of blank nodes check for Web NDL Authorities - National Diet Library of Japan took 13.773303508758545s
Security | Check HTTPS for Web NDL Authorities - National Diet Library of Japan took 0.3042640686035156s
Interpretability | RDF structures check for Web NDL Authorities - National Diet Library of Japan took 0.7662172317504883s
Versatility | Serialization formats check for Web NDL Authorities - National Diet Library of Japan took 0.3363785743713379s
Availability | RDF dump link check for Web NDL Authorities - National Diet Library of Japan took 0.7655289173126221s
License | MR license check for Web NDL Authorities - National Diet Library of Japan took 0.7740046977996826s
License | HR license check for Web NDL Authorities - National Diet Library of Japan took 90.92729544639587s
Amount of data | Number of property check for Web NDL Authorities - National Diet Library of Japan took 0.34934186935424805s
Understandability | Number of label check for Web NDL Authorities - National Diet Library of Japan took 6.685060977935791s
Understandability | URI regex check for Web NDL Authorities - National Diet Library of Japan took 0.6501815319061279s
Understandability | Vocabs check for Web NDL Authorities - National Diet Library of Japan took 0.7714238166809082s
Verifiability | Authors check for Web NDL Authorities - National Diet Library of Japan took 0.7929956912994385s
Verifiability | Publishers check for Web NDL Authorities - National Diet Library of Japan took 0.33110594749450684s
Performance | Throughput check for Web NDL Authorities - National Diet Library of Japan took 15.20263957977295s
Amount of data | Check the number of entities for Web NDL Authorities - National Diet Library of Japan took 8.392333984375e-05s
Verifiability | Contribs. check for Web NDL Authorities - National Diet Library of Japan took 0.3243129253387451s
Interlinking | sameAs chians check for Web NDL Authorities - National Diet Library of Japan took 0.9003043174743652s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 2.2332608699798584s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.0304539203643799s
Timeliness | dataset update frequency check for Web NDL Authorities - National Diet Library of Japan took 0.3243532180786133s
Currency | Creation date check for Web NDL Authorities - National Diet Library of Japan took 1.4525985717773438s
Currency | Modification date check for Web NDL Authorities - National Diet Library of Japan took 1.1135478019714355s
Rep.Conc. | URIs length for Web NDL Authorities - National Diet Library of Japan took 1.1152832508087158s
Interoperability | New vocabularies check for Web NDL Authorities - National Diet Library of Japan took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Web NDL Authorities - National Diet Library of Japan took 0.32312941551208496s
Accuracy | Check Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.33249402046203613s
Accuracy | Check Inverse Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.3210313320159912s
Accuracy | Check Empty annotation labels for Web NDL Authorities - National Diet Library of Japan took 0.33882594108581543s
Accuracy | Check White space in annotation for Web NDL Authorities - National Diet Library of Japan took 0.000732421875s
Accuracy | Check Datatype consistency for Web NDL Authorities - National Diet Library of Japan took 0.0010104179382324219s
Consistency | Disjoint class check for Web NDL Authorities - National Diet Library of Japan took 0.7787189483642578s
Consistency | Check Misplaced properties for Web NDL Authorities - National Diet Library of Japan took 0.6453840732574463s
Consistency | Misplaced classes for Web NDL Authorities - National Diet Library of Japan took 0.7801766395568848s
Consistency | Check Ontology hijacking for Web NDL Authorities - National Diet Library of Japan took 1.6101272106170654s
Consistency | Check Invalid usage of undefined classes for Web NDL Authorities - National Diet Library of Japan took 1.2383544445037842s
Consistency | Check Invalid usage of undefined properties for Web NDL Authorities - National Diet Library of Japan took 1.5624401569366455s
Conciseness | Check Extensional conciseness for Web NDL Authorities - National Diet Library of Japan took 0.0007512569427490234s
Security | Sign check for Web NDL Authorities - National Diet Library of Japan took 0.32686781883239746s
Availability | Check URIs Dereferenciability for Web NDL Authorities - National Diet Library of Japan took 4.583239793777466s
Completeness | Calculation of interlinking completeness for Web NDL Authorities - National Diet Library of Japan took 0.3442227840423584s
Reputation | Calculation of the PageRank for Web NDL Authorities - National Diet Library of Japan took 0.02062249183654785s
Interlinking | Calculation of Degree of Connection for Web NDL Authorities - National Diet Library of Japan took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Web NDL Authorities - National Diet Library of Japan took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for Web NDL Authorities - National Diet Library of Japan took 6.29425048828125e-05s
Interoperability | Check the re-using of existing vocabs for Web NDL Authorities - National Diet Library of Japan took 1.6689300537109375e-06s
Believability | Calculation of trust value for Web NDL Authorities - National Diet Library of Japan took 7.867813110351562e-06s
INFO | --- Analysis for national-diet-library-authorities took 238.31842064857483s
Availability | SPARQL endpoint availability check for National Diet Library of Japan subject headings took 0.3207881450653076s
Availability | VoID file availability check for National Diet Library of Japan subject headings took 0.0005960464477539062s
Extra | Recovery of all triples for National Diet Library of Japan subject headings took 0.8869988918304443s
Performance | Total latancy measurement for National Diet Library of Japan subject headings took 2.972454786300659s
Amount of data | Number of triples check for National Diet Library of Japan subject headings took 11.472255945205688s
Interoperability | New terms check for National Diet Library of Japan subject headings took 16.930893182754517s
Versatility | Languages check for National Diet Library of Japan subject headings took 0.33264756202697754s
Interpretability | Number of blank nodes check for National Diet Library of Japan subject headings took 13.268592834472656s
Security | Check HTTPS for National Diet Library of Japan subject headings took 0.7515838146209717s
Interpretability | RDF structures check for National Diet Library of Japan subject headings took 0.32187819480895996s
Versatility | Serialization formats check for National Diet Library of Japan subject headings took 0.32639217376708984s
Availability | RDF dump link check for National Diet Library of Japan subject headings took 0.31863832473754883s
License | MR license check for National Diet Library of Japan subject headings took 0.3244650363922119s
License | HR license check for National Diet Library of Japan subject headings took 91.27659916877747s
Amount of data | Number of property check for National Diet Library of Japan subject headings took 0.37053442001342773s
Understandability | Number of label check for National Diet Library of Japan subject headings took 4.720707416534424s
Understandability | URI regex check for National Diet Library of Japan subject headings took 0.6471946239471436s
Understandability | Vocabs check for National Diet Library of Japan subject headings took 0.80995774269104s
Verifiability | Authors check for National Diet Library of Japan subject headings took 0.33943653106689453s
Verifiability | Publishers check for National Diet Library of Japan subject headings took 0.33526039123535156s
Performance | Throughput check for National Diet Library of Japan subject headings took 14.814115762710571s
Amount of data | Check the number of entities for National Diet Library of Japan subject headings took 8.463859558105469e-05s
Verifiability | Contribs. check for National Diet Library of Japan subject headings took 0.3275730609893799s
Interlinking | sameAs chians check for National Diet Library of Japan subject headings took 0.868131160736084s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.2923271656036377s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.0460996627807617s
Timeliness | dataset update frequency check for National Diet Library of Japan subject headings took 0.33074235916137695s
Currency | Creation date check for National Diet Library of Japan subject headings took 1.4242722988128662s
Currency | Modification date check for National Diet Library of Japan subject headings took 0.672595739364624s
Rep.Conc. | URIs length for National Diet Library of Japan subject headings took 0.677807092666626s
Interoperability | New vocabularies check for National Diet Library of Japan subject headings took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for National Diet Library of Japan subject headings took 0.3228340148925781s
Accuracy | Check Functional Property for National Diet Library of Japan subject headings took 0.32030630111694336s
Accuracy | Check Inverse Functional Property for National Diet Library of Japan subject headings took 0.7787206172943115s
Accuracy | Check Empty annotation labels for National Diet Library of Japan subject headings took 0.33916425704956055s
Accuracy | Check White space in annotation for National Diet Library of Japan subject headings took 0.0007369518280029297s
Accuracy | Check Datatype consistency for National Diet Library of Japan subject headings took 0.0010182857513427734s
Consistency | Disjoint class check for National Diet Library of Japan subject headings took 0.3282904624938965s
Consistency | Check Misplaced properties for National Diet Library of Japan subject headings took 0.6598916053771973s
Consistency | Misplaced classes for National Diet Library of Japan subject headings took 0.7777717113494873s
Consistency | Check Ontology hijacking for National Diet Library of Japan subject headings took 1.6105763912200928s
Consistency | Check Invalid usage of undefined classes for National Diet Library of Japan subject headings took 1.238060712814331s
Consistency | Check Invalid usage of undefined properties for National Diet Library of Japan subject headings took 1.5601441860198975s
Conciseness | Check Extensional conciseness for National Diet Library of Japan subject headings took 0.0007016658782958984s
Security | Sign check for National Diet Library of Japan subject headings took 0.32259273529052734s
Availability | Check URIs Dereferenciability for National Diet Library of Japan subject headings took 4.769547700881958s
Completeness | Calculation of interlinking completeness for National Diet Library of Japan subject headings took 0.27274656295776367s
Reputation | Calculation of the PageRank for National Diet Library of Japan subject headings took 0.020620346069335938s
Interlinking | Calculation of Degree of Connection for National Diet Library of Japan subject headings took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for National Diet Library of Japan subject headings took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for National Diet Library of Japan subject headings took 5.53131103515625e-05s
Interoperability | Check the re-using of existing vocabs for National Diet Library of Japan subject headings took 1.1920928955078125e-06s
Believability | Calculation of trust value for National Diet Library of Japan subject headings took 1.049041748046875e-05s
INFO | --- Analysis for national-diet-library-subject-headings took 233.3712978363037s
Availability | SPARQL endpoint availability check for National Library of Greece Authority Records took 1.0615448951721191s
Availability | VoID file availability check for National Library of Greece Authority Records took 0.00044918060302734375s
Completeness | Calculation of interlinking completeness for National Library of Greece Authority Records took 0.27248644828796387s
Reputation | Calculation of the PageRank for National Library of Greece Authority Records took 0.02032470703125s
Interlinking | Calculation of Degree of Connection for National Library of Greece Authority Records took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for National Library of Greece Authority Records took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for National Library of Greece Authority Records took 4.172325134277344e-05s
Believability | Calculation of trust value for National Library of Greece Authority Records took 1.0728836059570312e-05s
INFO | --- Analysis for national-library-of-greece-authority-records took 5.078219890594482s
Availability | SPARQL endpoint availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 8.893013000488281e-05s
Availability | VoID file availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0004951953887939453s
Completeness | Calculation of interlinking completeness for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.262437105178833s
Reputation | Calculation of the PageRank for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.020525693893432617s
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.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.818771362304688e-05s
Believability | Calculation of trust value for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.0013580322265625e-05s
INFO | --- Analysis for Naturopathy took 3.3942768573760986s
Availability | SPARQL endpoint availability check for COVID-19 Data took 3.3415544033050537s
Availability | VoID file availability check for COVID-19 Data took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for COVID-19 Data took 0.26401472091674805s
Reputation | Calculation of the PageRank for COVID-19 Data took 0.020865917205810547s
Interlinking | Calculation of Degree of Connection for COVID-19 Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for COVID-19 Data took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for COVID-19 Data took 3.218650817871094e-05s
Believability | Calculation of trust value for COVID-19 Data took 1.1444091796875e-05s
INFO | --- Analysis for NCMI-COVID-19 took 7.168945074081421s
Availability | SPARQL endpoint availability check for NCMI-COVID-19 took 2.364926815032959s
Availability | VoID file availability check for NCMI-COVID-19 took 0.0005476474761962891s
Completeness | Calculation of interlinking completeness for NCMI-COVID-19 took 0.27414870262145996s
Reputation | Calculation of the PageRank for NCMI-COVID-19 took 0.020793437957763672s
Interlinking | Calculation of Degree of Connection for NCMI-COVID-19 took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for NCMI-COVID-19 took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for NCMI-COVID-19 took 1.2636184692382812e-05s
Believability | Calculation of trust value for NCMI-COVID-19 took 9.5367431640625e-06s
INFO | --- Analysis for NCMICOVID-19 took 6.20349645614624s
Availability | SPARQL endpoint availability check for Near took 0.00011801719665527344s
Availability | VoID file availability check for Near took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for Near took 0.34325289726257324s
Reputation | Calculation of the PageRank for Near took 0.02049851417541504s
Interlinking | Calculation of Degree of Connection for Near took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Near took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Near took 9.036064147949219e-05s
Believability | Calculation of trust value for Near took 1.0251998901367188e-05s
INFO | --- Analysis for near took 9.388131380081177s
Availability | SPARQL endpoint availability check for NeuroLex Wiki took 8.463859558105469e-05s
Availability | VoID file availability check for NeuroLex Wiki took 0.0004286766052246094s
Completeness | Calculation of interlinking completeness for NeuroLex Wiki took 0.28748488426208496s
Reputation | Calculation of the PageRank for NeuroLex Wiki took 0.020665645599365234s
Interlinking | Calculation of Degree of Connection for NeuroLex Wiki took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for NeuroLex Wiki took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for NeuroLex Wiki took 3.075599670410156e-05s
Believability | Calculation of trust value for NeuroLex Wiki took 9.5367431640625e-06s
INFO | --- Analysis for neurolex-wiki took 2.5435070991516113s
Availability | SPARQL endpoint availability check for Shivani Goyal Photography took 8.296966552734375e-05s
Availability | VoID file availability check for Shivani Goyal Photography took 0.00098419189453125s
Completeness | Calculation of interlinking completeness for Shivani Goyal Photography took 0.28049206733703613s
Reputation | Calculation of the PageRank for Shivani Goyal Photography took 0.021001338958740234s
Interlinking | Calculation of Degree of Connection for Shivani Goyal Photography took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Shivani Goyal Photography took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Shivani Goyal Photography took 4.744529724121094e-05s
Believability | Calculation of trust value for Shivani Goyal Photography took 8.106231689453125e-06s
INFO | --- Analysis for newborn-photography-maternity-photoshoot-shivani-goyal took 3.9292376041412354s
Availability | SPARQL endpoint availability check for News-100 NIF NER Corpus took 8.797645568847656e-05s
Availability | VoID file availability check for News-100 NIF NER Corpus took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for News-100 NIF NER Corpus took 0.2637298107147217s
Reputation | Calculation of the PageRank for News-100 NIF NER Corpus took 0.021397113800048828s
Interlinking | Calculation of Degree of Connection for News-100 NIF NER Corpus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for News-100 NIF NER Corpus took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for News-100 NIF NER Corpus took 6.628036499023438e-05s
Believability | Calculation of trust value for News-100 NIF NER Corpus took 1.0728836059570312e-05s
INFO | --- Analysis for news-100-nif-ner-corpus took 3.9939932823181152s
Availability | SPARQL endpoint availability check for neXtProt took 1.461944580078125s
Availability | VoID file availability check for neXtProt took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for neXtProt took 0.2706282138824463s
Reputation | Calculation of the PageRank for neXtProt took 0.022243976593017578s
Interlinking | Calculation of Degree of Connection for neXtProt took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for neXtProt took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for neXtProt took 3.528594970703125e-05s
Believability | Calculation of trust value for neXtProt took 1.2159347534179688e-05s
INFO | --- Analysis for nextprot took 4.4520909786224365s
Availability | SPARQL endpoint availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 8.487701416015625e-05s
Availability | VoID file availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0007925033569335938s
Completeness | Calculation of interlinking completeness for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.27387189865112305s
Reputation | Calculation of the PageRank for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.020331144332885742s
Interlinking | Calculation of Degree of Connection for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.00011038780212402344s
Believability | Calculation of trust value for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.049041748046875e-05s
INFO | --- Analysis for nextweb-gnoss took 12.030022621154785s
Availability | SPARQL endpoint availability check for NHS Jargon RDF took 9.584426879882812e-05s
Availability | VoID file availability check for NHS Jargon RDF took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for NHS Jargon RDF took 0.26793932914733887s
Reputation | Calculation of the PageRank for NHS Jargon RDF took 0.02235269546508789s
Interlinking | Calculation of Degree of Connection for NHS Jargon RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NHS Jargon RDF took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for NHS Jargon RDF took 7.891654968261719e-05s
Believability | Calculation of trust value for NHS Jargon RDF took 8.821487426757812e-06s
INFO | --- Analysis for nhs-jargon took 2.926347494125366s
Availability | SPARQL endpoint availability check for NIT Patna took 4.1484832763671875e-05s
Availability | VoID file availability check for NIT Patna took 0.0002808570861816406s
Completeness | Calculation of interlinking completeness for NIT Patna took 0.26146745681762695s
Reputation | Calculation of the PageRank for NIT Patna took 0.020673751831054688s
Interlinking | Calculation of Degree of Connection for NIT Patna took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NIT Patna took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for NIT Patna took 6.747245788574219e-05s
Believability | Calculation of trust value for NIT Patna took 1.1444091796875e-05s
INFO | --- Analysis for NITP took 3.2113068103790283s
Availability | SPARQL endpoint availability check for National Library of Russia BibCore Dataset took 8.630752563476562e-05s
Availability | VoID file availability check for National Library of Russia BibCore Dataset took 0.0006012916564941406s
Completeness | Calculation of interlinking completeness for National Library of Russia BibCore Dataset took 0.26322221755981445s
Reputation | Calculation of the PageRank for National Library of Russia BibCore Dataset took 0.022420406341552734s
Interlinking | Calculation of Degree of Connection for National Library of Russia BibCore Dataset took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for National Library of Russia BibCore Dataset took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for National Library of Russia BibCore Dataset took 3.170967102050781e-05s
Believability | Calculation of trust value for National Library of Russia BibCore Dataset took 7.867813110351562e-06s
INFO | --- Analysis for nlr-dataset-mod took 3.8328914642333984s
Availability | SPARQL endpoint availability check for Neulateinische Wortliste in LiLa took 0.5819547176361084s
Availability | VoID file availability check for Neulateinische Wortliste in LiLa took 0.0006291866302490234s
Completeness | Calculation of interlinking completeness for Neulateinische Wortliste in LiLa took 0.28003430366516113s
Reputation | Calculation of the PageRank for Neulateinische Wortliste in LiLa took 0.020490169525146484s
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.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Neulateinische Wortliste in LiLa took 3.743171691894531e-05s
Believability | Calculation of trust value for Neulateinische Wortliste in LiLa took 1.1682510375976562e-05s
INFO | --- Analysis for NLW took 4.333007335662842s
Availability | SPARQL endpoint availability check for Nobel Prizes took 3.14031982421875s
Availability | VoID file availability check for Nobel Prizes took 0.0006082057952880859s
Completeness | Calculation of interlinking completeness for Nobel Prizes took 0.267880916595459s
Reputation | Calculation of the PageRank for Nobel Prizes took 0.020427227020263672s
Interlinking | Calculation of Degree of Connection for Nobel Prizes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Nobel Prizes took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Nobel Prizes took 9.369850158691406e-05s
Believability | Calculation of trust value for Nobel Prizes took 1.049041748046875e-05s
INFO | --- Analysis for nobelprizes took 8.335172414779663s
Availability | SPARQL endpoint availability check for NoiPA took 0.28391480445861816s
Availability | VoID file availability check for NoiPA took 0.0004930496215820312s
Extra | Recovery of all triples for NoiPA took 1.4754791259765625s
Performance | Total latancy measurement for NoiPA took 0.4723782539367676s
Amount of data | Number of triples check for NoiPA took 1.6087274551391602s
Interoperability | New terms check for NoiPA took 2.8611390590667725s
Versatility | Languages check for NoiPA took 0.1096343994140625s
Interpretability | Number of blank nodes check for NoiPA took 0.10031723976135254s
Interpretability | RDF structures check for NoiPA took 0.4597036838531494s
Versatility | Serialization formats check for NoiPA took 0.2993791103363037s
Availability | RDF dump link check for NoiPA took 0.16991734504699707s
License | MR license check for NoiPA took 0.6729211807250977s
License | HR license check for NoiPA took 60.19687461853027s
Amount of data | Number of property check for NoiPA took 0.2763655185699463s
Understandability | Number of label check for NoiPA took 1.042693853378296s
Understandability | URI regex check for NoiPA took 0.7900609970092773s
Understandability | Vocabs check for NoiPA took 0.19482851028442383s
Verifiability | Authors check for NoiPA took 0.32288169860839844s
Verifiability | Publishers check for NoiPA took 0.28751373291015625s
Performance | Throughput check for NoiPA took 10.788222551345825s
Amount of data | Check the number of entities for NoiPA took 7.43865966796875e-05s
Verifiability | Contribs. check for NoiPA took 0.19703006744384766s
Interlinking | sameAs chians check for NoiPA took 0.20598483085632324s
Interlinking | skos check for NoiPA took 0.6660258769989014s
Interlinking | skos check for NoiPA took 0.1341080665588379s
Timeliness | dataset update frequency check for NoiPA took 0.2972540855407715s
Currency | Creation date check for NoiPA took 0.5409035682678223s
Currency | Modification date check for NoiPA took 0.21188974380493164s
Rep.Conc. | URIs length for NoiPA took 21.26364493370056s
Interoperability | New vocabularies check for NoiPA took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for NoiPA took 0.1735079288482666s
Accuracy | Check Functional Property for NoiPA took 0.19753026962280273s
Accuracy | Check Inverse Functional Property for NoiPA took 0.30251431465148926s
Accuracy | Check Empty annotation labels for NoiPA took 0.533761739730835s
Accuracy | Check White space in annotation for NoiPA took 0.02579522132873535s
Accuracy | Check Datatype consistency for NoiPA took 0.028168678283691406s
Consistency | Disjoint class check for NoiPA took 0.14900732040405273s
Consistency | Check Misplaced properties for NoiPA took 19.13722538948059s
Consistency | Misplaced classes for NoiPA took 0.2830374240875244s
Consistency | Check Ontology hijacking for NoiPA took 1.7375741004943848s
Consistency | Check Invalid usage of undefined classes for NoiPA took 1.2748370170593262s
Consistency | Check Invalid usage of undefined properties for NoiPA took 20.12465476989746s
Conciseness | Check Extensional conciseness for NoiPA took 0.03486919403076172s
Conciseness | Check Intensional conciseness for NoiPA took 0.14127755165100098s
Security | Sign check for NoiPA took 0.12102770805358887s
Availability | Check URIs Dereferenciability for NoiPA took 10.210705041885376s
Completeness | Calculation of interlinking completeness for NoiPA took 0.3323097229003906s
Reputation | Calculation of the PageRank for NoiPA took 0.02095651626586914s
Interlinking | Calculation of Degree of Connection for NoiPA took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for NoiPA took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for NoiPA took 3.24249267578125e-05s
Interoperability | Check the re-using of existing vocabs for NoiPA took 1.1920928955078125e-06s
Believability | Calculation of trust value for NoiPA took 1.0251998901367188e-05s
INFO | --- Analysis for NoiPA took 497.7263834476471s
Availability | SPARQL endpoint availability check for Nomenclature for Museum Cataloging took 1.109954833984375s
Availability | VoID file availability check for Nomenclature for Museum Cataloging took 0.0006706714630126953s
Completeness | Calculation of interlinking completeness for Nomenclature for Museum Cataloging took 0.27008748054504395s
Reputation | Calculation of the PageRank for Nomenclature for Museum Cataloging took 0.02067255973815918s
Interlinking | Calculation of Degree of Connection for Nomenclature for Museum Cataloging took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Nomenclature for Museum Cataloging took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Nomenclature for Museum Cataloging took 9.250640869140625e-05s
Believability | Calculation of trust value for Nomenclature for Museum Cataloging took 1.3113021850585938e-05s
INFO | --- Analysis for nom took 8.559943914413452s
Availability | SPARQL endpoint availability check for Nomenclator Asturias took 25.41577434539795s
Availability | VoID file availability check for Nomenclator Asturias took 0.0007801055908203125s
Completeness | Calculation of interlinking completeness for Nomenclator Asturias took 0.2625002861022949s
Reputation | Calculation of the PageRank for Nomenclator Asturias took 0.020852327346801758s
Interlinking | Calculation of Degree of Connection for Nomenclator Asturias took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Nomenclator Asturias took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Nomenclator Asturias took 8.106231689453125e-05s
Believability | Calculation of trust value for Nomenclator Asturias took 8.106231689453125e-06s
INFO | --- Analysis for nomenclator-asturias took 135.83565044403076s
Availability | SPARQL endpoint availability check for Nomisma.org  took 0.5343573093414307s
Availability | VoID file availability check for Nomisma.org  took 0.0004184246063232422s
Extra | Recovery of all triples for Nomisma.org  took 767.2693758010864s
Performance | Total latancy measurement for Nomisma.org  took 1.6217317581176758s
Amount of data | Number of triples check for Nomisma.org  took 37.92639112472534s
Interoperability | New terms check for Nomisma.org  took 10.56268835067749s
Versatility | Languages check for Nomisma.org  took 108.51334476470947s
Interpretability | Number of blank nodes check for Nomisma.org  took 38.758981704711914s
Security | Check HTTPS for Nomisma.org  took 0.6978116035461426s
Interpretability | RDF structures check for Nomisma.org  took 0.35141706466674805s
Versatility | Serialization formats check for Nomisma.org  took 0.4973468780517578s
Availability | RDF dump link check for Nomisma.org  took 891.247074842453s
License | MR license check for Nomisma.org  took 0.4214818477630615s
License | HR license check for Nomisma.org  took 62.71356749534607s
Amount of data | Number of property check for Nomisma.org  took 0.35226893424987793s
Understandability | Number of label check for Nomisma.org  took 9.009157180786133s
Understandability | URI regex check for Nomisma.org  took 0.6680376529693604s
Understandability | Vocabs check for Nomisma.org  took 0.3457188606262207s
Verifiability | Authors check for Nomisma.org  took 0.31020665168762207s
Verifiability | Publishers check for Nomisma.org  took 0.32866954803466797s
Performance | Throughput check for Nomisma.org  took 12.393448114395142s
Amount of data | Check the number of entities for Nomisma.org  took 58.68478035926819s
Verifiability | Contribs. check for Nomisma.org  took 0.3404257297515869s
Interlinking | sameAs chians check for Nomisma.org  took 0.33143091201782227s
Interlinking | skos check for Nomisma.org  took 1.1170012950897217s
Interlinking | skos check for Nomisma.org  took 0.4785785675048828s
Timeliness | dataset update frequency check for Nomisma.org  took 0.3095741271972656s
Currency | Creation date check for Nomisma.org  took 0.666919469833374s
Currency | Modification date check for Nomisma.org  took 0.6412878036499023s
Rep.Conc. | URIs length for Nomisma.org  took 307.8701720237732s
Interoperability | New vocabularies check for Nomisma.org  took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Nomisma.org  took 0.3443737030029297s
Accuracy | Check Functional Property for Nomisma.org  took 0.3323349952697754s
Accuracy | Check Inverse Functional Property for Nomisma.org  took 0.3057434558868408s
Accuracy | Check Empty annotation labels for Nomisma.org  took 237.18597149848938s
Accuracy | Check White space in annotation for Nomisma.org  took 2.699787139892578s
Accuracy | Check Datatype consistency for Nomisma.org  took 5.451050281524658s
Consistency | Disjoint class check for Nomisma.org  took 0.3488891124725342s
Consistency | Check Misplaced properties for Nomisma.org  took 26.688127040863037s
Consistency | Check Ontology hijacking for Nomisma.org  took 232.05235981941223s
Consistency | Check Invalid usage of undefined classes for Nomisma.org  took 1.9969677925109863s
Consistency | Check Invalid usage of undefined properties for Nomisma.org  took 27.886001586914062s
Conciseness | Check Extensional conciseness for Nomisma.org  took 2.7684428691864014s
Conciseness | Check Intensional conciseness for Nomisma.org  took 0.34063076972961426s
Security | Sign check for Nomisma.org  took 0.3338618278503418s
Availability | Check URIs Dereferenciability for Nomisma.org  took 2107.5811455249786s
Completeness | Calculation of interlinking completeness for Nomisma.org  took 0.964423418045044s
Reputation | Calculation of the PageRank for Nomisma.org  took 0.022135257720947266s
Interlinking | Calculation of Degree of Connection for Nomisma.org  took 2.3365020751953125e-05s
Interlinking | Calculation of Centrality for Nomisma.org  took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Nomisma.org  took 7.271766662597656e-05s
Interoperability | Check the re-using of existing vocabs for Nomisma.org  took 1.430511474609375e-06s
Believability | Calculation of trust value for Nomisma.org  took 7.62939453125e-06s
INFO | --- Analysis for nomisma_org took 8903.56885433197s
Availability | SPARQL endpoint availability check for Curriculum Vitae took 0.303783655166626s
Availability | VoID file availability check for Curriculum Vitae took 0.0005214214324951172s
Extra | Recovery of all triples for Curriculum Vitae took 1.2376911640167236s
Performance | Total latancy measurement for Curriculum Vitae took 0.8579103946685791s
Amount of data | Number of triples check for Curriculum Vitae took 0.11111927032470703s
Interoperability | New terms check for Curriculum Vitae took 1.567178726196289s
Versatility | Languages check for Curriculum Vitae took 0.11500263214111328s
Interpretability | Number of blank nodes check for Curriculum Vitae took 0.10665464401245117s
Interpretability | RDF structures check for Curriculum Vitae took 0.11511039733886719s
Versatility | Serialization formats check for Curriculum Vitae took 0.22515869140625s
Availability | RDF dump link check for Curriculum Vitae took 0.21438074111938477s
License | MR license check for Curriculum Vitae took 0.11193037033081055s
License | HR license check for Curriculum Vitae took 0.1116335391998291s
Amount of data | Number of property check for Curriculum Vitae took 0.2183525562286377s
Understandability | Number of label check for Curriculum Vitae took 0.10704612731933594s
Understandability | URI regex check for Curriculum Vitae took 0.32259607315063477s
Understandability | Vocabs check for Curriculum Vitae took 0.11074090003967285s
Verifiability | Authors check for Curriculum Vitae took 0.21910810470581055s
Verifiability | Publishers check for Curriculum Vitae took 0.21405410766601562s
Performance | Throughput check for Curriculum Vitae took 10.861320495605469s
Amount of data | Check the number of entities for Curriculum Vitae took 6.651878356933594e-05s
Verifiability | Contribs. check for Curriculum Vitae took 0.10882425308227539s
Interlinking | sameAs chians check for Curriculum Vitae took 0.11076140403747559s
Interlinking | skos check for Curriculum Vitae took 0.2156367301940918s
Interlinking | skos check for Curriculum Vitae took 0.10942721366882324s
Timeliness | dataset update frequency check for Curriculum Vitae took 0.22374820709228516s
Currency | Creation date check for Curriculum Vitae took 0.23059415817260742s
Currency | Modification date check for Curriculum Vitae took 0.3335545063018799s
Rep.Conc. | URIs length for Curriculum Vitae took 0.40021467208862305s
Interoperability | New vocabularies check for Curriculum Vitae took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Curriculum Vitae took 0.2115941047668457s
Accuracy | Check Functional Property for Curriculum Vitae took 0.21542739868164062s
Accuracy | Check Inverse Functional Property for Curriculum Vitae took 0.22278642654418945s
Accuracy | Check Empty annotation labels for Curriculum Vitae took 0.22318553924560547s
Accuracy | Check White space in annotation for Curriculum Vitae took 8.821487426757812e-05s
Accuracy | Check Datatype consistency for Curriculum Vitae took 0.0033049583435058594s
Consistency | Disjoint class check for Curriculum Vitae took 0.22591376304626465s
Consistency | Check Misplaced properties for Curriculum Vitae took 0.23376703262329102s
Consistency | Check Ontology hijacking for Curriculum Vitae took 1.6516528129577637s
Consistency | Check Invalid usage of undefined classes for Curriculum Vitae took 1.4637460708618164s
Consistency | Check Invalid usage of undefined properties for Curriculum Vitae took 1.6874430179595947s
Conciseness | Check Extensional conciseness for Curriculum Vitae took 0.001459360122680664s
Security | Sign check for Curriculum Vitae took 0.21141624450683594s
Availability | Check URIs Dereferenciability for Curriculum Vitae took 21.445117235183716s
Completeness | Calculation of interlinking completeness for Curriculum Vitae took 0.2665998935699463s
Reputation | Calculation of the PageRank for Curriculum Vitae took 0.020732402801513672s
Interlinking | Calculation of Degree of Connection for Curriculum Vitae took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Curriculum Vitae took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Curriculum Vitae took 3.123283386230469e-05s
Interoperability | Check the re-using of existing vocabs for Curriculum Vitae took 1.6689300537109375e-06s
Believability | Calculation of trust value for Curriculum Vitae took 1.0013580322265625e-05s
INFO | --- Analysis for Nordine_Bittich took 62.513092279434204s
Availability | SPARQL endpoint availability check for NorPark took 0.05988192558288574s
Availability | VoID file availability check for NorPark took 0.0006134510040283203s
Completeness | Calculation of interlinking completeness for NorPark took 0.26557254791259766s
Reputation | Calculation of the PageRank for NorPark took 0.02044844627380371s
Interlinking | Calculation of Degree of Connection for NorPark took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for NorPark took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for NorPark took 4.458427429199219e-05s
Believability | Calculation of trust value for NorPark took 1.0251998901367188e-05s
INFO | --- Analysis for norpark took 2.7242283821105957s
Availability | SPARQL endpoint availability check for Parking Dataset took 0.02035379409790039s
Availability | VoID file availability check for Parking Dataset took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for Parking Dataset took 0.2630136013031006s
Reputation | Calculation of the PageRank for Parking Dataset took 0.02070164680480957s
Interlinking | Calculation of Degree of Connection for Parking Dataset took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Parking Dataset took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Parking Dataset took 4.744529724121094e-05s
Believability | Calculation of trust value for Parking Dataset took 1.1444091796875e-05s
INFO | --- Analysis for norpark2 took 2.484321117401123s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset took 0.5377342700958252s
Availability | VoID file availability check for Norway fishery stocks dataset took 0.0005080699920654297s
Extra | Recovery of all triples for Norway fishery stocks dataset took 121.72660112380981s
Performance | Total latancy measurement for Norway fishery stocks dataset took 0.8869011402130127s
Amount of data | Number of triples check for Norway fishery stocks dataset took 9.327494382858276s
Interoperability | New terms check for Norway fishery stocks dataset took 14.436229705810547s
Versatility | Languages check for Norway fishery stocks dataset took 300.2013580799103s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset took 2.1306416988372803s
Interpretability | RDF structures check for Norway fishery stocks dataset took 0.2477259635925293s
Versatility | Serialization formats check for Norway fishery stocks dataset took 9.985042333602905s
Availability | RDF dump link check for Norway fishery stocks dataset took 0.2978951930999756s
License | MR license check for Norway fishery stocks dataset took 0.6673076152801514s
License | HR license check for Norway fishery stocks dataset took 300.19963335990906s
Amount of data | Number of property check for Norway fishery stocks dataset took 0.17676329612731934s
Understandability | Number of label check for Norway fishery stocks dataset took 2.4524669647216797s
Understandability | URI regex check for Norway fishery stocks dataset took 0.8449273109436035s
Understandability | Vocabs check for Norway fishery stocks dataset took 0.4550325870513916s
Verifiability | Authors check for Norway fishery stocks dataset took 0.17915630340576172s
Verifiability | Publishers check for Norway fishery stocks dataset took 0.23928356170654297s
Performance | Throughput check for Norway fishery stocks dataset took 10.72052550315857s
Amount of data | Check the number of entities for Norway fishery stocks dataset took 6.866455078125e-05s
Verifiability | Contribs. check for Norway fishery stocks dataset took 0.1803445816040039s
Interlinking | sameAs chians check for Norway fishery stocks dataset took 0.18069076538085938s
Interlinking | skos check for Norway fishery stocks dataset took 0.41268110275268555s
Interlinking | skos check for Norway fishery stocks dataset took 0.393296480178833s
Timeliness | dataset update frequency check for Norway fishery stocks dataset took 4.331320524215698s
Currency | Creation date check for Norway fishery stocks dataset took 0.4288663864135742s
Currency | Modification date check for Norway fishery stocks dataset took 0.22252678871154785s
Rep.Conc. | URIs length for Norway fishery stocks dataset took 157.07628798484802s
Interoperability | New vocabularies check for Norway fishery stocks dataset took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset took 0.1739521026611328s
Accuracy | Check Functional Property for Norway fishery stocks dataset took 0.36835575103759766s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset took 0.35874319076538086s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset took 40.666741132736206s
Accuracy | Check White space in annotation for Norway fishery stocks dataset took 2.64267897605896s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset took 2.555048942565918s
Consistency | Disjoint class check for Norway fishery stocks dataset took 0.1709883213043213s
Consistency | Check Misplaced properties for Norway fishery stocks dataset took 87.10820436477661s
Consistency | Misplaced classes for Norway fishery stocks dataset took 8.212716341018677s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset took 35.188669204711914s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset took 1.3332128524780273s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset took 88.18074440956116s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset took 2.7166290283203125s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset took 0.5203590393066406s
Security | Sign check for Norway fishery stocks dataset took 1.0133140087127686s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset took 23.60246992111206s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset took 0.39568495750427246s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset took 0.020805835723876953s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset took 3.9577484130859375e-05s
Interoperability | Check the re-using of existing vocabs for Norway fishery stocks dataset took 1.9073486328125e-06s
Believability | Calculation of trust value for Norway fishery stocks dataset took 1.1682510375976562e-05s
INFO | --- Analysis for Norway_Fishery_ took 2272.8877189159393s
Availability | SPARQL endpoint availability check for Norwegian geo-divisions took 0.25335049629211426s
Availability | VoID file availability check for Norwegian geo-divisions took 0.0003299713134765625s
Completeness | Calculation of interlinking completeness for Norwegian geo-divisions took 0.2606658935546875s
Reputation | Calculation of the PageRank for Norwegian geo-divisions took 0.020797014236450195s
Interlinking | Calculation of Degree of Connection for Norwegian geo-divisions took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Norwegian geo-divisions took 0.0007929801940917969s
Interlinking | Calculation of Clustering coefficient for Norwegian geo-divisions took 5.602836608886719e-05s
Believability | Calculation of trust value for Norwegian geo-divisions took 1.2159347534179688e-05s
INFO | --- Analysis for norwegian-geo-divisions took 5.86241888999939s
Availability | SPARQL endpoint availability check for NITP took 4.1961669921875e-05s
Availability | VoID file availability check for NITP took 0.0006289482116699219s
Completeness | Calculation of interlinking completeness for NITP took 0.2687797546386719s
Reputation | Calculation of the PageRank for NITP took 0.020684242248535156s
Interlinking | Calculation of Degree of Connection for NITP took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for NITP took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for NITP took 6.532669067382812e-05s
Believability | Calculation of trust value for NITP took 9.775161743164062e-06s
INFO | --- Analysis for notIdentifier took 3.0048165321350098s
Availability | SPARQL endpoint availability check for Nottingham Trent University Resource Lists took 4.3392181396484375e-05s
Availability | VoID file availability check for Nottingham Trent University Resource Lists took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for Nottingham Trent University Resource Lists took 0.2562427520751953s
Reputation | Calculation of the PageRank for Nottingham Trent University Resource Lists took 0.020862579345703125s
Interlinking | Calculation of Degree of Connection for Nottingham Trent University Resource Lists took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Nottingham Trent University Resource Lists took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Nottingham Trent University Resource Lists took 3.7670135498046875e-05s
Believability | Calculation of trust value for Nottingham Trent University Resource Lists took 9.059906005859375e-06s
INFO | --- Analysis for nottingham-trent-university-resource-lists took 2.757338285446167s
Availability | SPARQL endpoint availability check for NPM took 4.315376281738281e-05s
Availability | VoID file availability check for NPM took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for NPM took 0.2611227035522461s
Reputation | Calculation of the PageRank for NPM took 0.022550106048583984s
Interlinking | Calculation of Degree of Connection for NPM took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NPM took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for NPM took 3.457069396972656e-05s
Believability | Calculation of trust value for NPM took 1.0728836059570312e-05s
INFO | --- Analysis for npm took 3.2914111614227295s
Availability | SPARQL endpoint availability check for NTNU special collections took 0.032628536224365234s
Availability | VoID file availability check for NTNU special collections took 0.0005426406860351562s
Completeness | Calculation of interlinking completeness for NTNU special collections took 0.2743110656738281s
Reputation | Calculation of the PageRank for NTNU special collections took 0.0204927921295166s
Interlinking | Calculation of Degree of Connection for NTNU special collections took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for NTNU special collections took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for NTNU special collections took 5.5789947509765625e-05s
Believability | Calculation of trust value for NTNU special collections took 1.049041748046875e-05s
INFO | --- Analysis for ntnusc took 5.02172327041626s
Availability | SPARQL endpoint availability check for links took 8.106231689453125e-05s
Availability | VoID file availability check for links took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for links took 0.26986265182495117s
Reputation | Calculation of the PageRank for links took 0.020647287368774414s
Interlinking | Calculation of Degree of Connection for links took 1.52587890625e-05s
Interlinking | Calculation of Centrality for links took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for links took 1.2636184692382812e-05s
Believability | Calculation of trust value for links took 1.0013580322265625e-05s
INFO | --- Analysis for nugmyanmar took 2.410825490951538s
Availability | SPARQL endpoint availability check for NUTS (GeoVocab) took 8.296966552734375e-05s
Availability | VoID file availability check for NUTS (GeoVocab) took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for NUTS (GeoVocab) took 0.2635960578918457s
Reputation | Calculation of the PageRank for NUTS (GeoVocab) took 0.020560503005981445s
Interlinking | Calculation of Degree of Connection for NUTS (GeoVocab) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for NUTS (GeoVocab) took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for NUTS (GeoVocab) took 9.560585021972656e-05s
Believability | Calculation of trust value for NUTS (GeoVocab) took 9.059906005859375e-06s
INFO | --- Analysis for nuts-geovocab took 2.4952893257141113s
Availability | SPARQL endpoint availability check for Norsk inndeling av vitenskapsdisipliner took 0.38127946853637695s
Availability | VoID file availability check for Norsk inndeling av vitenskapsdisipliner took 0.0005853176116943359s
Completeness | Calculation of interlinking completeness for Norsk inndeling av vitenskapsdisipliner took 0.26827549934387207s
Reputation | Calculation of the PageRank for Norsk inndeling av vitenskapsdisipliner took 0.02116847038269043s
Interlinking | Calculation of Degree of Connection for Norsk inndeling av vitenskapsdisipliner took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Norsk inndeling av vitenskapsdisipliner took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Norsk inndeling av vitenskapsdisipliner took 6.699562072753906e-05s
Believability | Calculation of trust value for Norsk inndeling av vitenskapsdisipliner took 9.298324584960938e-06s
INFO | --- Analysis for nvd took 3.953252077102661s
Availability | SPARQL endpoint availability check for NERC Vocabulary Server 2.0 took 0.7278680801391602s
Availability | VoID file availability check for NERC Vocabulary Server 2.0 took 0.0005428791046142578s
Completeness | Calculation of interlinking completeness for NERC Vocabulary Server 2.0 took 0.27399587631225586s
Reputation | Calculation of the PageRank for NERC Vocabulary Server 2.0 took 0.020604848861694336s
Interlinking | Calculation of Degree of Connection for NERC Vocabulary Server 2.0 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for NERC Vocabulary Server 2.0 took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for NERC Vocabulary Server 2.0 took 7.867813110351562e-05s
Believability | Calculation of trust value for NERC Vocabulary Server 2.0 took 1.049041748046875e-05s
INFO | --- Analysis for nvs took 8.268674612045288s
Availability | SPARQL endpoint availability check for New York Times - Linked Open Data took 8.320808410644531e-05s
Availability | VoID file availability check for New York Times - Linked Open Data took 0.0004291534423828125s
Completeness | Calculation of interlinking completeness for New York Times - Linked Open Data took 0.2732679843902588s
Reputation | Calculation of the PageRank for New York Times - Linked Open Data took 0.022757291793823242s
Interlinking | Calculation of Degree of Connection for New York Times - Linked Open Data took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for New York Times - Linked Open Data took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for New York Times - Linked Open Data took 0.0001850128173828125s
Believability | Calculation of trust value for New York Times - Linked Open Data took 9.5367431640625e-06s
INFO | --- Analysis for nytimes-linked-open-data took 2.47792387008667s
Availability | SPARQL endpoint availability check for Italian Chamber of Deputies - official dataset took 0.5946102142333984s
Availability | VoID file availability check for Italian Chamber of Deputies - official dataset took 0.0006203651428222656s
Extra | Recovery of all triples for Italian Chamber of Deputies - official dataset took 1.3574395179748535s
Performance | Total latancy measurement for Italian Chamber of Deputies - official dataset took 1.7444961071014404s
Amount of data | Number of triples check for Italian Chamber of Deputies - official dataset took 2.443240165710449s
Interoperability | New terms check for Italian Chamber of Deputies - official dataset took 3.7170050144195557s
Versatility | Languages check for Italian Chamber of Deputies - official dataset took 58.222665786743164s
Interpretability | Number of blank nodes check for Italian Chamber of Deputies - official dataset took 2.3925728797912598s
Security | Check HTTPS for Italian Chamber of Deputies - official dataset took 0.28248143196105957s
Interpretability | RDF structures check for Italian Chamber of Deputies - official dataset took 0.3573441505432129s
Versatility | Serialization formats check for Italian Chamber of Deputies - official dataset took 0.4335050582885742s
Availability | RDF dump link check for Italian Chamber of Deputies - official dataset took 0.42951464653015137s
License | MR license check for Italian Chamber of Deputies - official dataset took 0.3498055934906006s
License | HR license check for Italian Chamber of Deputies - official dataset took 58.21336388587952s
Amount of data | Number of property check for Italian Chamber of Deputies - official dataset took 0.3418574333190918s
Understandability | Number of label check for Italian Chamber of Deputies - official dataset took 0.8906924724578857s
Understandability | URI regex check for Italian Chamber of Deputies - official dataset took 0.6463847160339355s
Understandability | Vocabs check for Italian Chamber of Deputies - official dataset took 0.40631842613220215s
Verifiability | Authors check for Italian Chamber of Deputies - official dataset took 0.34049034118652344s
Verifiability | Publishers check for Italian Chamber of Deputies - official dataset took 0.3412959575653076s
Performance | Throughput check for Italian Chamber of Deputies - official dataset took 10.605740070343018s
Amount of data | Check the number of entities for Italian Chamber of Deputies - official dataset took 3.266334533691406e-05s
Verifiability | Contribs. check for Italian Chamber of Deputies - official dataset took 0.33745408058166504s
Interlinking | sameAs chians check for Italian Chamber of Deputies - official dataset took 0.344470739364624s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.3756871223449707s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.33536744117736816s
Timeliness | dataset update frequency check for Italian Chamber of Deputies - official dataset took 0.4947168827056885s
Currency | Creation date check for Italian Chamber of Deputies - official dataset took 0.6271376609802246s
Currency | Modification date check for Italian Chamber of Deputies - official dataset took 0.3354177474975586s
Rep.Conc. | URIs length for Italian Chamber of Deputies - official dataset took 17.012405395507812s
Interoperability | New vocabularies check for Italian Chamber of Deputies - official dataset took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Italian Chamber of Deputies - official dataset took 0.3561112880706787s
Accuracy | Check Functional Property for Italian Chamber of Deputies - official dataset took 0.3535306453704834s
Accuracy | Check Inverse Functional Property for Italian Chamber of Deputies - official dataset took 0.3353252410888672s
Accuracy | Check Empty annotation labels for Italian Chamber of Deputies - official dataset took 0.7631914615631104s
Accuracy | Check White space in annotation for Italian Chamber of Deputies - official dataset took 0.0297086238861084s
Accuracy | Check Datatype consistency for Italian Chamber of Deputies - official dataset took 0.028265953063964844s
Consistency | Disjoint class check for Italian Chamber of Deputies - official dataset took 0.3332819938659668s
Consistency | Check Misplaced properties for Italian Chamber of Deputies - official dataset took 12.600546598434448s
Consistency | Misplaced classes for Italian Chamber of Deputies - official dataset took 0.4307997226715088s
Consistency | Check Ontology hijacking for Italian Chamber of Deputies - official dataset took 1.887404441833496s
Consistency | Check Invalid usage of undefined classes for Italian Chamber of Deputies - official dataset took 1.2290372848510742s
Consistency | Check Invalid usage of undefined properties for Italian Chamber of Deputies - official dataset took 13.639946460723877s
Conciseness | Check Extensional conciseness for Italian Chamber of Deputies - official dataset took 0.03154802322387695s
Conciseness | Check Intensional conciseness for Italian Chamber of Deputies - official dataset took 0.3724210262298584s
Security | Sign check for Italian Chamber of Deputies - official dataset took 0.3451094627380371s
Availability | Check URIs Dereferenciability for Italian Chamber of Deputies - official dataset took 9.717607498168945s
Completeness | Calculation of interlinking completeness for Italian Chamber of Deputies - official dataset took 0.36553096771240234s
Reputation | Calculation of the PageRank for Italian Chamber of Deputies - official dataset took 0.021647214889526367s
Interlinking | Calculation of Degree of Connection for Italian Chamber of Deputies - official dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Italian Chamber of Deputies - official dataset took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Italian Chamber of Deputies - official dataset took 9.560585021972656e-05s
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 1.0967254638671875e-05s
INFO | --- Analysis for ocd took 373.5589978694916s
Availability | SPARQL endpoint availability check for oceandrilling-borehole took 9.107589721679688e-05s
Availability | VoID file availability check for oceandrilling-borehole took 0.0006973743438720703s
Completeness | Calculation of interlinking completeness for oceandrilling-borehole took 0.27587032318115234s
Reputation | Calculation of the PageRank for oceandrilling-borehole took 0.021225452423095703s
Interlinking | Calculation of Degree of Connection for oceandrilling-borehole took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for oceandrilling-borehole took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for oceandrilling-borehole took 3.981590270996094e-05s
Believability | Calculation of trust value for oceandrilling-borehole took 1.0251998901367188e-05s
INFO | --- Analysis for oceandrilling-borehole took 3.10893177986145s
Availability | SPARQL endpoint availability check for Ocean Drilling - Codices took 2.478874683380127s
Availability | VoID file availability check for Ocean Drilling - Codices took 0.0007984638214111328s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Codices took 0.2880821228027344s
Reputation | Calculation of the PageRank for Ocean Drilling - Codices took 0.02117776870727539s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Codices took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Codices took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Codices took 9.298324584960938e-05s
Believability | Calculation of trust value for Ocean Drilling - Codices took 1.2874603271484375e-05s
INFO | --- Analysis for oceandrilling-codices took 7.819570779800415s
Availability | SPARQL endpoint availability check for Ocean Drilling - dbSEABED took 2.401116371154785s
Availability | VoID file availability check for Ocean Drilling - dbSEABED took 0.0006105899810791016s
Completeness | Calculation of interlinking completeness for Ocean Drilling - dbSEABED took 0.2651398181915283s
Reputation | Calculation of the PageRank for Ocean Drilling - dbSEABED took 0.022890329360961914s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - dbSEABED took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - dbSEABED took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - dbSEABED took 3.147125244140625e-05s
Believability | Calculation of trust value for Ocean Drilling - dbSEABED took 1.1920928955078125e-05s
INFO | --- Analysis for oceandrilling-dbseabed took 6.51668906211853s
Availability | SPARQL endpoint availability check for Ocean Drilling - Forams took 2.3523619174957275s
Availability | VoID file availability check for Ocean Drilling - Forams took 0.0007765293121337891s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Forams took 0.2628481388092041s
Reputation | Calculation of the PageRank for Ocean Drilling - Forams took 0.020385265350341797s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Forams took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Forams took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Forams took 3.361701965332031e-05s
Believability | Calculation of trust value for Ocean Drilling - Forams took 7.3909759521484375e-06s
INFO | --- Analysis for oceandrilling-forams took 6.731202602386475s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus LOD took 2.307060718536377s
Availability | VoID file availability check for Ocean Drilling - Janus LOD took 0.0009038448333740234s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus LOD took 0.26187753677368164s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus LOD took 0.020377397537231445s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus LOD took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus LOD took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus LOD took 3.337860107421875e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus LOD took 1.1682510375976562e-05s
INFO | --- Analysis for oceandrilling-janus took 6.720715761184692s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus Age Models took 12.195079326629639s
Availability | VoID file availability check for Ocean Drilling - Janus Age Models took 0.0007164478302001953s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus Age Models took 0.27231860160827637s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus Age Models took 0.0213015079498291s
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.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus Age Models took 3.2901763916015625e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus Age Models took 1.1682510375976562e-05s
INFO | --- Analysis for oceandrilling-janusamp took 16.690359115600586s
Availability | SPARQL endpoint availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 2.3961946964263916s
Availability | VoID file availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0008146762847900391s
Completeness | Calculation of interlinking completeness for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.2810494899749756s
Reputation | Calculation of the PageRank for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.021684885025024414s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 2.8848648071289062e-05s
Believability | Calculation of trust value for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.1682510375976562e-05s
INFO | --- Analysis for oceandrilling-ldeo took 6.806389331817627s
Availability | SPARQL endpoint availability check for Faceted Application of Subject Terminology took 4.4345855712890625e-05s
Availability | VoID file availability check for Faceted Application of Subject Terminology took 0.0005469322204589844s
Completeness | Calculation of interlinking completeness for Faceted Application of Subject Terminology took 0.2693502902984619s
Reputation | Calculation of the PageRank for Faceted Application of Subject Terminology took 0.02022075653076172s
Interlinking | Calculation of Degree of Connection for Faceted Application of Subject Terminology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Faceted Application of Subject Terminology took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Faceted Application of Subject Terminology took 5.53131103515625e-05s
Believability | Calculation of trust value for Faceted Application of Subject Terminology took 1.0251998901367188e-05s
INFO | --- Analysis for oclc-fast took 8.056347608566284s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.00010657310485839844s
Availability | VoID file availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.26191043853759766s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.022474050521850586s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 3.147125244140625e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 8.821487426757812e-06s
INFO | --- Analysis for odc-imd-environment-score took 4.5954508781433105s
Availability | SPARQL endpoint availability check for Open Data Communities - Lower layer Super Output Areas took 0.18858790397644043s
Availability | VoID file availability check for Open Data Communities - Lower layer Super Output Areas took 0.0006151199340820312s
Extra | Recovery of all triples for Open Data Communities - Lower layer Super Output Areas took 1.5355267524719238s
Performance | Total latancy measurement for Open Data Communities - Lower layer Super Output Areas took 0.8567864894866943s
Amount of data | Number of triples check for Open Data Communities - Lower layer Super Output Areas took 0.18161749839782715s
Interoperability | New terms check for Open Data Communities - Lower layer Super Output Areas took 1.4217088222503662s
Versatility | Languages check for Open Data Communities - Lower layer Super Output Areas took 0.4726712703704834s
Interpretability | Number of blank nodes check for Open Data Communities - Lower layer Super Output Areas took 30.215381145477295s
Security | Check HTTPS for Open Data Communities - Lower layer Super Output Areas took 0.1577773094177246s
Interpretability | RDF structures check for Open Data Communities - Lower layer Super Output Areas took 0.18745040893554688s
Versatility | Serialization formats check for Open Data Communities - Lower layer Super Output Areas took 0.5849587917327881s
Availability | RDF dump link check for Open Data Communities - Lower layer Super Output Areas took 47.12006878852844s
License | MR license check for Open Data Communities - Lower layer Super Output Areas took 0.123504638671875s
License | HR license check for Open Data Communities - Lower layer Super Output Areas took 30.216922998428345s
Amount of data | Number of property check for Open Data Communities - Lower layer Super Output Areas took 0.12620973587036133s
Understandability | Number of label check for Open Data Communities - Lower layer Super Output Areas took 0.1830921173095703s
Understandability | URI regex check for Open Data Communities - Lower layer Super Output Areas took 0.370434045791626s
Understandability | Vocabs check for Open Data Communities - Lower layer Super Output Areas took 0.28264427185058594s
Verifiability | Authors check for Open Data Communities - Lower layer Super Output Areas took 0.18626952171325684s
Verifiability | Publishers check for Open Data Communities - Lower layer Super Output Areas took 0.18683981895446777s
Performance | Throughput check for Open Data Communities - Lower layer Super Output Areas took 11.983974933624268s
Amount of data | Check the number of entities for Open Data Communities - Lower layer Super Output Areas took 0.0001201629638671875s
Verifiability | Contribs. check for Open Data Communities - Lower layer Super Output Areas took 0.18372440338134766s
Interlinking | sameAs chians check for Open Data Communities - Lower layer Super Output Areas took 0.18053674697875977s
Interlinking | skos check for Open Data Communities - Lower layer Super Output Areas took 0.18502569198608398s
Interlinking | skos check for Open Data Communities - Lower layer Super Output Areas took 0.12012410163879395s
Timeliness | dataset update frequency check for Open Data Communities - Lower layer Super Output Areas took 0.2243514060974121s
Currency | Creation date check for Open Data Communities - Lower layer Super Output Areas took 0.47870755195617676s
Currency | Modification date check for Open Data Communities - Lower layer Super Output Areas took 0.12531328201293945s
Rep.Conc. | URIs length for Open Data Communities - Lower layer Super Output Areas took 1.2849504947662354s
Interoperability | New vocabularies check for Open Data Communities - Lower layer Super Output Areas took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Open Data Communities - Lower layer Super Output Areas took 0.18260908126831055s
Accuracy | Check Functional Property for Open Data Communities - Lower layer Super Output Areas took 0.18787646293640137s
Accuracy | Check Inverse Functional Property for Open Data Communities - Lower layer Super Output Areas took 0.11930346488952637s
Consistency | Disjoint class check for Open Data Communities - Lower layer Super Output Areas took 0.12537193298339844s
Consistency | Check Misplaced properties for Open Data Communities - Lower layer Super Output Areas took 1.2732269763946533s
Consistency | Check Ontology hijacking for Open Data Communities - Lower layer Super Output Areas took 1.2914507389068604s
Consistency | Check Invalid usage of undefined properties for Open Data Communities - Lower layer Super Output Areas took 1.5013985633850098s
Conciseness | Check Extensional conciseness for Open Data Communities - Lower layer Super Output Areas took 0.0001475811004638672s
Conciseness | Check Intensional conciseness for Open Data Communities - Lower layer Super Output Areas took 0.4469478130340576s
Security | Sign check for Open Data Communities - Lower layer Super Output Areas took 0.6737563610076904s
Completeness | Calculation of interlinking completeness for Open Data Communities - Lower layer Super Output Areas took 0.2669246196746826s
Reputation | Calculation of the PageRank for Open Data Communities - Lower layer Super Output Areas took 0.020777463912963867s
Interlinking | Calculation of Degree of Connection for Open Data Communities - Lower layer Super Output Areas took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Data Communities - Lower layer Super Output Areas took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Open Data Communities - Lower layer Super Output Areas took 4.124641418457031e-05s
Interoperability | Check the re-using of existing vocabs for Open Data Communities - Lower layer Super Output Areas took 1.430511474609375e-06s
Believability | Calculation of trust value for Open Data Communities - Lower layer Super Output Areas took 8.344650268554688e-06s
INFO | --- Analysis for odc-lsoa took 259.22303557395935s
Availability | SPARQL endpoint availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.09318089485168457s
Availability | VoID file availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.00042700767517089844s
Completeness | Calculation of interlinking completeness for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.2538332939147949s
Reputation | Calculation of the PageRank for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.020460844039916992s
Interlinking | Calculation of Degree of Connection for Organisation for Economic Co-operation and Development (OECD) Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Organisation for Economic Co-operation and Development (OECD) Linked Data took 9.322166442871094e-05s
Believability | Calculation of trust value for Organisation for Economic Co-operation and Development (OECD) Linked Data took 4.76837158203125e-06s
INFO | --- Analysis for oecd-linked-data took 2.508960247039795s
Availability | SPARQL endpoint availability check for Orthology and Diseases Information - OGO took 30.149293422698975s
Availability | VoID file availability check for Orthology and Diseases Information - OGO took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for Orthology and Diseases Information - OGO took 0.28273797035217285s
Reputation | Calculation of the PageRank for Orthology and Diseases Information - OGO took 0.020309925079345703s
Interlinking | Calculation of Degree of Connection for Orthology and Diseases Information - OGO took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Orthology and Diseases Information - OGO took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Orthology and Diseases Information - OGO took 4.315376281738281e-05s
Believability | Calculation of trust value for Orthology and Diseases Information - OGO took 1.1205673217773438e-05s
INFO | --- Analysis for ogolod took 102.77664470672607s
Availability | SPARQL endpoint availability check for OLAC Metadata took 8.440017700195312e-05s
Availability | VoID file availability check for OLAC Metadata took 0.0006933212280273438s
Completeness | Calculation of interlinking completeness for OLAC Metadata took 0.27191972732543945s
Reputation | Calculation of the PageRank for OLAC Metadata took 0.020351409912109375s
Interlinking | Calculation of Degree of Connection for OLAC Metadata took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OLAC Metadata took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for OLAC Metadata took 4.1961669921875e-05s
Believability | Calculation of trust value for OLAC Metadata took 1.1444091796875e-05s
INFO | --- Analysis for olac took 22.58628249168396s
Availability | SPARQL endpoint availability check for OLiA took 4.220008850097656e-05s
Availability | VoID file availability check for OLiA took 0.0007610321044921875s
Completeness | Calculation of interlinking completeness for OLiA took 0.28290343284606934s
Reputation | Calculation of the PageRank for OLiA took 0.02116847038269043s
Interlinking | Calculation of Degree of Connection for OLiA took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OLiA took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for OLiA took 0.00012183189392089844s
Believability | Calculation of trust value for OLiA took 1.1205673217773438e-05s
INFO | --- Analysis for olia took 12.301548957824707s
Availability | SPARQL endpoint availability check for OLiA Discourse took 4.2438507080078125e-05s
Availability | VoID file availability check for OLiA Discourse took 0.0004038810729980469s
Completeness | Calculation of interlinking completeness for OLiA Discourse took 0.26833033561706543s
Reputation | Calculation of the PageRank for OLiA Discourse took 0.020366668701171875s
Interlinking | Calculation of Degree of Connection for OLiA Discourse took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OLiA Discourse took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for OLiA Discourse took 3.838539123535156e-05s
Believability | Calculation of trust value for OLiA Discourse took 1.1920928955078125e-05s
INFO | --- Analysis for olia-discourse took 6.8239710330963135s
Availability | SPARQL endpoint availability check for Open Land Use took 0.17757916450500488s
Availability | VoID file availability check for Open Land Use took 0.0004971027374267578s
Extra | Recovery of all triples for Open Land Use took 120.69070529937744s
Performance | Total latancy measurement for Open Land Use took 0.8751311302185059s
Amount of data | Number of triples check for Open Land Use took 9.307199478149414s
Interoperability | New terms check for Open Land Use took 13.933840990066528s
Versatility | Languages check for Open Land Use took 300.16926860809326s
Interpretability | Number of blank nodes check for Open Land Use took 2.1209630966186523s
Interpretability | RDF structures check for Open Land Use took 0.2759518623352051s
Versatility | Serialization formats check for Open Land Use took 8.044107437133789s
Availability | RDF dump link check for Open Land Use took 0.2833271026611328s
License | MR license check for Open Land Use took 0.6329615116119385s
License | HR license check for Open Land Use took 300.1755931377411s
Amount of data | Number of property check for Open Land Use took 0.18987512588500977s
Understandability | Number of label check for Open Land Use took 2.5150179862976074s
Understandability | URI regex check for Open Land Use took 0.7921328544616699s
Understandability | Vocabs check for Open Land Use took 0.5685617923736572s
Verifiability | Authors check for Open Land Use took 0.18617653846740723s
Verifiability | Publishers check for Open Land Use took 0.23249030113220215s
Performance | Throughput check for Open Land Use took 10.675426959991455s
Amount of data | Check the number of entities for Open Land Use took 7.343292236328125e-05s
Verifiability | Contribs. check for Open Land Use took 0.17940258979797363s
Interlinking | sameAs chians check for Open Land Use took 0.18478894233703613s
Interlinking | skos check for Open Land Use took 0.410555362701416s
Interlinking | skos check for Open Land Use took 0.40194129943847656s
Timeliness | dataset update frequency check for Open Land Use took 4.933467864990234s
Currency | Creation date check for Open Land Use took 0.4303708076477051s
Currency | Modification date check for Open Land Use took 0.22877216339111328s
Rep.Conc. | URIs length for Open Land Use took 159.2901840209961s
Interoperability | New vocabularies check for Open Land Use took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for Open Land Use took 0.31008458137512207s
Accuracy | Check Functional Property for Open Land Use took 0.2647554874420166s
Accuracy | Check Inverse Functional Property for Open Land Use took 0.41753387451171875s
Accuracy | Check Empty annotation labels for Open Land Use took 40.18340229988098s
Accuracy | Check White space in annotation for Open Land Use took 2.6304664611816406s
Accuracy | Check Datatype consistency for Open Land Use took 2.6300747394561768s
Consistency | Disjoint class check for Open Land Use took 0.17648053169250488s
Consistency | Check Misplaced properties for Open Land Use took 86.27582097053528s
Consistency | Misplaced classes for Open Land Use took 8.265841960906982s
Consistency | Check Ontology hijacking for Open Land Use took 32.32664179801941s
Consistency | Check Invalid usage of undefined classes for Open Land Use took 1.327125072479248s
Consistency | Check Invalid usage of undefined properties for Open Land Use took 87.79392290115356s
Conciseness | Check Extensional conciseness for Open Land Use took 2.7049291133880615s
Conciseness | Check Intensional conciseness for Open Land Use took 0.47753381729125977s
Security | Sign check for Open Land Use took 0.6832776069641113s
Availability | Check URIs Dereferenciability for Open Land Use took 9.132289409637451s
Completeness | Calculation of interlinking completeness for Open Land Use took 0.6158156394958496s
Reputation | Calculation of the PageRank for Open Land Use took 0.021360158920288086s
Interlinking | Calculation of Degree of Connection for Open Land Use took 2.384185791015625e-05s
Interlinking | Calculation of Centrality for Open Land Use took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for Open Land Use took 9.441375732421875e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use took 1.6689300537109375e-06s
Believability | Calculation of trust value for Open Land Use took 1.1920928955078125e-05s
INFO | --- Analysis for OLU took 2237.130823612213s
Availability | SPARQL endpoint availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.7785134315490723s
Availability | VoID file availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for Albanet WordNet (as part of Open Multilingual WordNet) took 0.2630338668823242s
Reputation | Calculation of the PageRank for Albanet WordNet (as part of Open Multilingual WordNet) took 0.022657155990600586s
Interlinking | Calculation of Degree of Connection for Albanet WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Albanet WordNet (as part of Open Multilingual WordNet) took 4.410743713378906e-05s
Believability | Calculation of trust value for Albanet WordNet (as part of Open Multilingual WordNet) took 6.4373016357421875e-06s
INFO | --- Analysis for omwn-als took 3.6259500980377197s
Availability | SPARQL endpoint availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.2645416259765625s
Availability | VoID file availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for Arabic WordNet (as part of Open Multilingual WordNet) took 0.2616302967071533s
Reputation | Calculation of the PageRank for Arabic WordNet (as part of Open Multilingual WordNet) took 0.020302295684814453s
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.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Arabic WordNet (as part of Open Multilingual WordNet) took 3.7670135498046875e-05s
Believability | Calculation of trust value for Arabic WordNet (as part of Open Multilingual WordNet) took 7.867813110351562e-06s
INFO | --- Analysis for omwn-arb took 3.0284979343414307s
Availability | SPARQL endpoint availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.22473478317260742s
Availability | VoID file availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.25652480125427246s
Reputation | Calculation of the PageRank for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.020223379135131836s
Interlinking | Calculation of Degree of Connection for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 3.695487976074219e-05s
Believability | Calculation of trust value for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-bul took 2.975642442703247s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.21822118759155273s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.26604723930358887s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.020279407501220703s
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.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.695487976074219e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-cow took 2.9292500019073486s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.23978519439697266s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2630152702331543s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.020274639129638672s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.695487976074219e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-cwn took 2.9245975017547607s
Availability | SPARQL endpoint availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.22745323181152344s
Availability | VoID file availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for DanNet WordNet (as part of Open Multilingual WordNet) took 0.2543191909790039s
Reputation | Calculation of the PageRank for DanNet WordNet (as part of Open Multilingual WordNet) took 0.02030158042907715s
Interlinking | Calculation of Degree of Connection for DanNet WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0006968975067138672s
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 1.049041748046875e-05s
INFO | --- Analysis for omwn-dan took 2.990856647491455s
Availability | SPARQL endpoint availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.24041986465454102s
Availability | VoID file availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for Greek WordNet (as part of Open Multilingual WordNet) took 0.2650115489959717s
Reputation | Calculation of the PageRank for Greek WordNet (as part of Open Multilingual WordNet) took 0.020571231842041016s
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.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Greek WordNet (as part of Open Multilingual WordNet) took 3.838539123535156e-05s
Believability | Calculation of trust value for Greek WordNet (as part of Open Multilingual WordNet) took 5.9604644775390625e-06s
INFO | --- Analysis for omwn-ell took 2.9513285160064697s
Availability | SPARQL endpoint availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.25278401374816895s
Availability | VoID file availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.000415802001953125s
Completeness | Calculation of interlinking completeness for Princeton WordNet (as part of Open Multilingual WordNet) took 0.26561403274536133s
Reputation | Calculation of the PageRank for Princeton WordNet (as part of Open Multilingual WordNet) took 0.02053689956665039s
Interlinking | Calculation of Degree of Connection for Princeton WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Princeton WordNet (as part of Open Multilingual WordNet) took 3.886222839355469e-05s
Believability | Calculation of trust value for Princeton WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
INFO | --- Analysis for omwn-eng took 3.0210330486297607s
Availability | SPARQL endpoint availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.26165127754211426s
Availability | VoID file availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.00042510032653808594s
Completeness | Calculation of interlinking completeness for Persian WordNet (as part of Open Multilingual WordNet) took 0.26063108444213867s
Reputation | Calculation of the PageRank for Persian WordNet (as part of Open Multilingual WordNet) took 0.021094322204589844s
Interlinking | Calculation of Degree of Connection for Persian WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Persian WordNet (as part of Open Multilingual WordNet) took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Persian WordNet (as part of Open Multilingual WordNet) took 3.981590270996094e-05s
Believability | Calculation of trust value for Persian WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
INFO | --- Analysis for omwn-fas took 3.0270402431488037s
Availability | SPARQL endpoint availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.24303364753723145s
Availability | VoID file availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004215240478515625s
Completeness | Calculation of interlinking completeness for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.2614874839782715s
Reputation | Calculation of the PageRank for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.021947860717773438s
Interlinking | Calculation of Degree of Connection for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 4.124641418457031e-05s
Believability | Calculation of trust value for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-fin took 2.9912211894989014s
Availability | SPARQL endpoint availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.2556569576263428s
Availability | VoID file availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0004246234893798828s
Completeness | Calculation of interlinking completeness for WOLF WordNet (as part of Open Multilingual WordNet) took 0.2683243751525879s
Reputation | Calculation of the PageRank for WOLF WordNet (as part of Open Multilingual WordNet) took 0.020320415496826172s
Interlinking | Calculation of Degree of Connection for WOLF WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for WOLF WordNet (as part of Open Multilingual WordNet) took 3.933906555175781e-05s
Believability | Calculation of trust value for WOLF WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
INFO | --- Analysis for omwn-fra took 3.025831460952759s
Availability | SPARQL endpoint availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.25078606605529785s
Availability | VoID file availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0005948543548583984s
Completeness | Calculation of interlinking completeness for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.272444486618042s
Reputation | Calculation of the PageRank for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.02113652229309082s
Interlinking | Calculation of Degree of Connection for Hebrew WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Hebrew WordNet (as part of Open Multilingual WordNet) took 4.0531158447265625e-05s
Believability | Calculation of trust value for Hebrew WordNet (as part of Open Multilingual WordNet) took 9.059906005859375e-06s
INFO | --- Analysis for omwn-heb took 3.0486903190612793s
Availability | SPARQL endpoint availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.26000118255615234s
Availability | VoID file availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.00022292137145996094s
Completeness | Calculation of interlinking completeness for Croatian WordNet (as part of Open Multilingual WordNet) took 0.2683587074279785s
Reputation | Calculation of the PageRank for Croatian WordNet (as part of Open Multilingual WordNet) took 0.021970748901367188s
Interlinking | Calculation of Degree of Connection for Croatian WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Croatian WordNet (as part of Open Multilingual WordNet) took 3.814697265625e-05s
Believability | Calculation of trust value for Croatian WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
INFO | --- Analysis for omwn-hrv took 2.989096164703369s
Availability | SPARQL endpoint availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.23118185997009277s
Availability | VoID file availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004181861877441406s
Completeness | Calculation of interlinking completeness for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.26780128479003906s
Reputation | Calculation of the PageRank for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.022347450256347656s
Interlinking | Calculation of Degree of Connection for IceWordNet WordNet (as part of Open Multilingual WordNet) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for IceWordNet WordNet (as part of Open Multilingual WordNet) took 3.933906555175781e-05s
Believability | Calculation of trust value for IceWordNet WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
INFO | --- Analysis for omwn-isl took 3.043168544769287s
Availability | SPARQL endpoint availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.227280855178833s
Availability | VoID file availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004189014434814453s
Completeness | Calculation of interlinking completeness for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.27155637741088867s
Reputation | Calculation of the PageRank for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.020683765411376953s
Interlinking | Calculation of Degree of Connection for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 3.9577484130859375e-05s
Believability | Calculation of trust value for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
INFO | --- Analysis for omwn-ita took 3.004286766052246s
Availability | SPARQL endpoint availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.21696209907531738s
Availability | VoID file availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0004265308380126953s
Completeness | Calculation of interlinking completeness for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.27374696731567383s
Reputation | Calculation of the PageRank for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.020585060119628906s
Interlinking | Calculation of Degree of Connection for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 3.886222839355469e-05s
Believability | Calculation of trust value for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
INFO | --- Analysis for omwn-iwn took 2.9536423683166504s
Availability | SPARQL endpoint availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.24089336395263672s
Availability | VoID file availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0004487037658691406s
Completeness | Calculation of interlinking completeness for Japanese WordNet (as part of Open Multilingual WordNet) took 0.27847933769226074s
Reputation | Calculation of the PageRank for Japanese WordNet (as part of Open Multilingual WordNet) took 0.021115541458129883s
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.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Japanese WordNet (as part of Open Multilingual WordNet) took 4.0531158447265625e-05s
Believability | Calculation of trust value for Japanese WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
INFO | --- Analysis for omwn-jpn took 3.0603573322296143s
Availability | SPARQL endpoint availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.2264397144317627s
Availability | VoID file availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.000438690185546875s
Completeness | Calculation of interlinking completeness for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.2599301338195801s
Reputation | Calculation of the PageRank for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.02158522605895996s
Interlinking | Calculation of Degree of Connection for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Multilingual Central Repository (as part of Open Multilingual WordNet) took 4.1484832763671875e-05s
Believability | Calculation of trust value for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
INFO | --- Analysis for omwn-mcr took 3.0052058696746826s
Availability | SPARQL endpoint availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.23337244987487793s
Availability | VoID file availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.2720353603363037s
Reputation | Calculation of the PageRank for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.021978139877319336s
Interlinking | Calculation of Degree of Connection for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Wordnet WordNet (as part of Open Multilingual WordNet) took 4.1484832763671875e-05s
Believability | Calculation of trust value for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
INFO | --- Analysis for omwn-msa took 2.994572162628174s
Availability | SPARQL endpoint availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.22478890419006348s
Availability | VoID file availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.00043320655822753906s
Completeness | Calculation of interlinking completeness for Open WordNet (as part of Open Multilingual WordNet) took 0.26920413970947266s
Reputation | Calculation of the PageRank for Open WordNet (as part of Open Multilingual WordNet) took 0.020360231399536133s
Interlinking | Calculation of Degree of Connection for Open WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Open WordNet (as part of Open Multilingual WordNet) took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Open WordNet (as part of Open Multilingual WordNet) took 4.00543212890625e-05s
Believability | Calculation of trust value for Open WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
INFO | --- Analysis for omwn-nld took 3.004512071609497s
Availability | SPARQL endpoint availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.23489856719970703s
Availability | VoID file availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.00042510032653808594s
Completeness | Calculation of interlinking completeness for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.26245713233947754s
Reputation | Calculation of the PageRank for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.022216081619262695s
Interlinking | Calculation of Degree of Connection for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Norwegian WordNet (as part of Open Multilingual WordNet) took 4.00543212890625e-05s
Believability | Calculation of trust value for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
INFO | --- Analysis for omwn-nor took 3.014861583709717s
Availability | SPARQL endpoint availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.2330014705657959s
Availability | VoID file availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.2889060974121094s
Reputation | Calculation of the PageRank for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.020409822463989258s
Interlinking | Calculation of Degree of Connection for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for plWordNet WordNet (as part of Open Multilingual WordNet) took 3.719329833984375e-05s
Believability | Calculation of trust value for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
INFO | --- Analysis for omwn-pol took 3.032099962234497s
Availability | SPARQL endpoint availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.24597978591918945s
Availability | VoID file availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0004165172576904297s
Completeness | Calculation of interlinking completeness for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.26244068145751953s
Reputation | Calculation of the PageRank for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.02019977569580078s
Interlinking | Calculation of Degree of Connection for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 4.076957702636719e-05s
Believability | Calculation of trust value for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
INFO | --- Analysis for omwn-por took 3.0111031532287598s
Availability | SPARQL endpoint availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.23890328407287598s
Availability | VoID file availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.00043892860412597656s
Completeness | Calculation of interlinking completeness for Romanian WordNet (as part of Open Multilingual WordNet) took 0.3699495792388916s
Reputation | Calculation of the PageRank for Romanian WordNet (as part of Open Multilingual WordNet) took 0.020751237869262695s
Interlinking | Calculation of Degree of Connection for Romanian WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Romanian WordNet (as part of Open Multilingual WordNet) took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Romanian WordNet (as part of Open Multilingual WordNet) took 4.029273986816406e-05s
Believability | Calculation of trust value for Romanian WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
INFO | --- Analysis for omwn-ron took 3.1437299251556396s
Availability | SPARQL endpoint availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.2415180206298828s
Availability | VoID file availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.00043487548828125s
Completeness | Calculation of interlinking completeness for Slovak WordNet (as part of Open Multilingual WordNet) took 0.2616114616394043s
Reputation | Calculation of the PageRank for Slovak WordNet (as part of Open Multilingual WordNet) took 0.02115488052368164s
Interlinking | Calculation of Degree of Connection for Slovak WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Slovak WordNet (as part of Open Multilingual WordNet) took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Slovak WordNet (as part of Open Multilingual WordNet) took 4.673004150390625e-05s
Believability | Calculation of trust value for Slovak WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
INFO | --- Analysis for omwn-slk took 2.9998557567596436s
Availability | SPARQL endpoint availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.24169349670410156s
Availability | VoID file availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0004315376281738281s
Completeness | Calculation of interlinking completeness for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.2787933349609375s
Reputation | Calculation of the PageRank for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.020806550979614258s
Interlinking | Calculation of Degree of Connection for sloWNet WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for sloWNet WordNet (as part of Open Multilingual WordNet) took 3.9577484130859375e-05s
Believability | Calculation of trust value for sloWNet WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
INFO | --- Analysis for omwn-slv took 3.0349905490875244s
Availability | SPARQL endpoint availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.22950029373168945s
Availability | VoID file availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0004031658172607422s
Completeness | Calculation of interlinking completeness for Swedish WordNet (as part of Open Multilingual WordNet) took 0.26318907737731934s
Reputation | Calculation of the PageRank for Swedish WordNet (as part of Open Multilingual WordNet) took 0.021350622177124023s
Interlinking | Calculation of Degree of Connection for Swedish WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Swedish WordNet (as part of Open Multilingual WordNet) took 3.981590270996094e-05s
Believability | Calculation of trust value for Swedish WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
INFO | --- Analysis for omwn-swe took 3.147799491882324s
Availability | SPARQL endpoint availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.24748468399047852s
Availability | VoID file availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.00043582916259765625s
Completeness | Calculation of interlinking completeness for Thai WordNet (as part of Open Multilingual WordNet) took 0.26549315452575684s
Reputation | Calculation of the PageRank for Thai WordNet (as part of Open Multilingual WordNet) took 0.0206296443939209s
Interlinking | Calculation of Degree of Connection for Thai WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Thai WordNet (as part of Open Multilingual WordNet) took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Thai WordNet (as part of Open Multilingual WordNet) took 4.00543212890625e-05s
Believability | Calculation of trust value for Thai WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
INFO | --- Analysis for omwn-tha took 3.0523602962493896s
Availability | SPARQL endpoint availability check for OntoBeef Domain took 6.049102544784546s
Availability | VoID file availability check for OntoBeef Domain took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for OntoBeef Domain took 0.2643096446990967s
Reputation | Calculation of the PageRank for OntoBeef Domain took 0.021707773208618164s
Interlinking | Calculation of Degree of Connection for OntoBeef Domain took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for OntoBeef Domain took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for OntoBeef Domain took 4.553794860839844e-05s
Believability | Calculation of trust value for OntoBeef Domain took 1.049041748046875e-05s
INFO | --- Analysis for ontobeef-domain took 28.587430953979492s
Availability | SPARQL endpoint availability check for Ontos News Portal took 8.416175842285156e-05s
Availability | VoID file availability check for Ontos News Portal took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for Ontos News Portal took 0.26517724990844727s
Reputation | Calculation of the PageRank for Ontos News Portal took 0.021944284439086914s
Interlinking | Calculation of Degree of Connection for Ontos News Portal took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ontos News Portal took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Ontos News Portal took 8.96453857421875e-05s
Believability | Calculation of trust value for Ontos News Portal took 1.049041748046875e-05s
INFO | --- Analysis for ontos-news-portal took 4.574285507202148s
Availability | SPARQL endpoint availability check for Ookaboo RDF dump took 8.702278137207031e-05s
Availability | VoID file availability check for Ookaboo RDF dump took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for Ookaboo RDF dump took 0.2687082290649414s
Reputation | Calculation of the PageRank for Ookaboo RDF dump took 0.021169662475585938s
Interlinking | Calculation of Degree of Connection for Ookaboo RDF dump took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Ookaboo RDF dump took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Ookaboo RDF dump took 3.24249267578125e-05s
Believability | Calculation of trust value for Ookaboo RDF dump took 8.58306884765625e-06s
INFO | --- Analysis for ookaboo-rdf-dump took 2.57560133934021s
Availability | SPARQL endpoint availability check for Open Bantu isiXhosa Lexicon took 8.630752563476562e-05s
Availability | VoID file availability check for Open Bantu isiXhosa Lexicon took 0.0005338191986083984s
Completeness | Calculation of interlinking completeness for Open Bantu isiXhosa Lexicon took 0.2660958766937256s
Reputation | Calculation of the PageRank for Open Bantu isiXhosa Lexicon took 0.020603418350219727s
Interlinking | Calculation of Degree of Connection for Open Bantu isiXhosa Lexicon took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Open Bantu isiXhosa Lexicon took 0.0008053779602050781s
Interlinking | Calculation of Clustering coefficient for Open Bantu isiXhosa Lexicon took 4.220008850097656e-05s
Believability | Calculation of trust value for Open Bantu isiXhosa Lexicon took 1.2159347534179688e-05s
INFO | --- Analysis for open-bantu-isixhosa-lexicon took 9.032731771469116s
Availability | SPARQL endpoint availability check for Open Data Euskadi took 4.315376281738281e-05s
Availability | VoID file availability check for Open Data Euskadi took 0.0007083415985107422s
Completeness | Calculation of interlinking completeness for Open Data Euskadi took 0.27193641662597656s
Reputation | Calculation of the PageRank for Open Data Euskadi took 0.020750045776367188s
Interlinking | Calculation of Degree of Connection for Open Data Euskadi took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Open Data Euskadi took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Open Data Euskadi took 5.555152893066406e-05s
Believability | Calculation of trust value for Open Data Euskadi took 8.58306884765625e-06s
INFO | --- Analysis for open-data-euskadi took 7.842361688613892s
Availability | SPARQL endpoint availability check for Open Data RISP, the Spanish Open Data community took 0.00010728836059570312s
Availability | VoID file availability check for Open Data RISP, the Spanish Open Data community took 0.0003807544708251953s
Completeness | Calculation of interlinking completeness for Open Data RISP, the Spanish Open Data community took 0.26761651039123535s
Reputation | Calculation of the PageRank for Open Data RISP, the Spanish Open Data community took 0.021907806396484375s
Interlinking | Calculation of Degree of Connection for Open Data RISP, the Spanish Open Data community took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Open Data RISP, the Spanish Open Data community took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Open Data RISP, the Spanish Open Data community took 0.00010728836059570312s
Believability | Calculation of trust value for Open Data RISP, the Spanish Open Data community took 1.1205673217773438e-05s
INFO | --- Analysis for open-data-risp took 9.124517917633057s
Availability | SPARQL endpoint availability check for Open Data Thesaurus took 0.1868143081665039s
Availability | VoID file availability check for Open Data Thesaurus took 0.0009462833404541016s
Extra | Recovery of all triples for Open Data Thesaurus took 1.0447163581848145s
Performance | Total latancy measurement for Open Data Thesaurus took 0.41846561431884766s
Amount of data | Number of triples check for Open Data Thesaurus took 0.10339188575744629s
Interoperability | New terms check for Open Data Thesaurus took 1.3337936401367188s
Versatility | Languages check for Open Data Thesaurus took 0.10987257957458496s
Interpretability | Number of blank nodes check for Open Data Thesaurus took 0.10322260856628418s
Security | Check HTTPS for Open Data Thesaurus took 0.2966458797454834s
Interpretability | RDF structures check for Open Data Thesaurus took 0.10418128967285156s
Versatility | Serialization formats check for Open Data Thesaurus took 0.10899901390075684s
Availability | RDF dump link check for Open Data Thesaurus took 0.9694123268127441s
License | MR license check for Open Data Thesaurus took 0.10419321060180664s
License | HR license check for Open Data Thesaurus took 0.0818488597869873s
Amount of data | Number of property check for Open Data Thesaurus took 0.1049036979675293s
Understandability | Number of label check for Open Data Thesaurus took 0.10391426086425781s
Understandability | URI regex check for Open Data Thesaurus took 0.16019034385681152s
Understandability | Vocabs check for Open Data Thesaurus took 0.10283756256103516s
Verifiability | Authors check for Open Data Thesaurus took 0.10365152359008789s
Verifiability | Publishers check for Open Data Thesaurus took 0.1034855842590332s
Performance | Throughput check for Open Data Thesaurus took 10.299984693527222s
Amount of data | Check the number of entities for Open Data Thesaurus took 7.2479248046875e-05s
Verifiability | Contribs. check for Open Data Thesaurus took 0.10285735130310059s
Interlinking | sameAs chians check for Open Data Thesaurus took 0.10378789901733398s
Interlinking | skos check for Open Data Thesaurus took 0.1020047664642334s
Interlinking | skos check for Open Data Thesaurus took 0.0796499252319336s
Timeliness | dataset update frequency check for Open Data Thesaurus took 0.07945895195007324s
Currency | Creation date check for Open Data Thesaurus took 0.16141152381896973s
Currency | Modification date check for Open Data Thesaurus took 0.18160343170166016s
Rep.Conc. | URIs length for Open Data Thesaurus took 0.4078195095062256s
Interoperability | New vocabularies check for Open Data Thesaurus took 1.9699022769927979s
Consistency | Deprecated classes/propertiers check for Open Data Thesaurus took 0.1077268123626709s
Accuracy | Check Functional Property for Open Data Thesaurus took 0.0788729190826416s
Accuracy | Check Inverse Functional Property for Open Data Thesaurus took 0.08423709869384766s
Accuracy | Check Empty annotation labels for Open Data Thesaurus took 0.158890962600708s
Accuracy | Check White space in annotation for Open Data Thesaurus took 0.0011725425720214844s
Consistency | Disjoint class check for Open Data Thesaurus took 0.08089900016784668s
Consistency | Check Misplaced properties for Open Data Thesaurus took 0.1636185646057129s
Consistency | Misplaced classes for Open Data Thesaurus took 0.07909154891967773s
Consistency | Check Ontology hijacking for Open Data Thesaurus took 1.3811726570129395s
Consistency | Check Invalid usage of undefined properties for Open Data Thesaurus took 1.304948091506958s
Conciseness | Check Extensional conciseness for Open Data Thesaurus took 0.00016951560974121094s
Security | Sign check for Open Data Thesaurus took 0.0772848129272461s
Completeness | Calculation of interlinking completeness for Open Data Thesaurus took 0.314831018447876s
Reputation | Calculation of the PageRank for Open Data Thesaurus took 0.020884990692138672s
Interlinking | Calculation of Degree of Connection for Open Data Thesaurus took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Open Data Thesaurus took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Open Data Thesaurus took 8.058547973632812e-05s
Interoperability | Check the re-using of existing vocabs for Open Data Thesaurus took 0.4056270122528076s
Believability | Calculation of trust value for Open Data Thesaurus took 1.3589859008789062e-05s
INFO | --- Analysis for open-data-thesaurus took 102.81340003013611s
Availability | SPARQL endpoint availability check for Open Election Data Project took 4.315376281738281e-05s
Availability | VoID file availability check for Open Election Data Project took 0.0006978511810302734s
Completeness | Calculation of interlinking completeness for Open Election Data Project took 0.2697327136993408s
Reputation | Calculation of the PageRank for Open Election Data Project took 0.020566225051879883s
Interlinking | Calculation of Degree of Connection for Open Election Data Project took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Open Election Data Project took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Open Election Data Project took 7.05718994140625e-05s
Believability | Calculation of trust value for Open Election Data Project took 9.5367431640625e-06s
INFO | --- Analysis for open-election-data-project took 42.452638387680054s
Availability | SPARQL endpoint availability check for OpenEI - Open Energy Info took 3.754937171936035s
Availability | VoID file availability check for OpenEI - Open Energy Info took 0.00122833251953125s
Completeness | Calculation of interlinking completeness for OpenEI - Open Energy Info took 0.290602445602417s
Reputation | Calculation of the PageRank for OpenEI - Open Energy Info took 0.020730972290039062s
Interlinking | Calculation of Degree of Connection for OpenEI - Open Energy Info took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for OpenEI - Open Energy Info took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for OpenEI - Open Energy Info took 8.7738037109375e-05s
Believability | Calculation of trust value for OpenEI - Open Energy Info took 9.5367431640625e-06s
INFO | --- Analysis for open-energy-info-wiki took 13.32727599143982s
Availability | SPARQL endpoint availability check for Open Library took 0.00012564659118652344s
Availability | VoID file availability check for Open Library took 0.00092315673828125s
Completeness | Calculation of interlinking completeness for Open Library took 0.27507925033569336s
Reputation | Calculation of the PageRank for Open Library took 0.020936012268066406s
Interlinking | Calculation of Degree of Connection for Open Library took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Open Library took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Open Library took 7.033348083496094e-05s
Believability | Calculation of trust value for Open Library took 1.0967254638671875e-05s
INFO | --- Analysis for open-library took 9.012287378311157s
Availability | SPARQL endpoint availability check for Open Land Use @PSNC took 0.1737658977508545s
Availability | VoID file availability check for Open Land Use @PSNC took 0.0002925395965576172s
Extra | Recovery of all triples for Open Land Use @PSNC took 116.63691592216492s
Performance | Total latancy measurement for Open Land Use @PSNC took 0.8721745014190674s
Amount of data | Number of triples check for Open Land Use @PSNC took 9.224582195281982s
Interoperability | New terms check for Open Land Use @PSNC took 14.285434007644653s
Versatility | Languages check for Open Land Use @PSNC took 300.2274992465973s
Interpretability | Number of blank nodes check for Open Land Use @PSNC took 2.11750864982605s
Interpretability | RDF structures check for Open Land Use @PSNC took 0.1841733455657959s
Versatility | Serialization formats check for Open Land Use @PSNC took 9.114477396011353s
Availability | RDF dump link check for Open Land Use @PSNC took 0.20970416069030762s
License | MR license check for Open Land Use @PSNC took 0.2988901138305664s
License | HR license check for Open Land Use @PSNC took 300.1731779575348s
Amount of data | Number of property check for Open Land Use @PSNC took 0.18439984321594238s
Understandability | Number of label check for Open Land Use @PSNC took 1.455688238143921s
Understandability | URI regex check for Open Land Use @PSNC took 0.5153279304504395s
Understandability | Vocabs check for Open Land Use @PSNC took 0.2518887519836426s
Verifiability | Authors check for Open Land Use @PSNC took 0.18399286270141602s
Verifiability | Publishers check for Open Land Use @PSNC took 0.22824764251708984s
Performance | Throughput check for Open Land Use @PSNC took 10.673488140106201s
Amount of data | Check the number of entities for Open Land Use @PSNC took 7.486343383789062e-05s
Verifiability | Contribs. check for Open Land Use @PSNC took 0.18009257316589355s
Interlinking | sameAs chians check for Open Land Use @PSNC took 0.1797332763671875s
Interlinking | skos check for Open Land Use @PSNC took 0.4718811511993408s
Interlinking | skos check for Open Land Use @PSNC took 0.4302530288696289s
Timeliness | dataset update frequency check for Open Land Use @PSNC took 4.8591368198394775s
Currency | Creation date check for Open Land Use @PSNC took 0.4393138885498047s
Currency | Modification date check for Open Land Use @PSNC took 0.23233771324157715s
Rep.Conc. | URIs length for Open Land Use @PSNC took 155.1322784423828s
Interoperability | New vocabularies check for Open Land Use @PSNC took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Open Land Use @PSNC took 0.18204379081726074s
Accuracy | Check Functional Property for Open Land Use @PSNC took 0.33855390548706055s
Accuracy | Check Inverse Functional Property for Open Land Use @PSNC took 0.32083559036254883s
Accuracy | Check Empty annotation labels for Open Land Use @PSNC took 32.22074604034424s
Accuracy | Check White space in annotation for Open Land Use @PSNC took 2.633378744125366s
Accuracy | Check Datatype consistency for Open Land Use @PSNC took 2.563242197036743s
Consistency | Disjoint class check for Open Land Use @PSNC took 0.178696870803833s
Consistency | Check Misplaced properties for Open Land Use @PSNC took 86.31836032867432s
Consistency | Misplaced classes for Open Land Use @PSNC took 8.280473947525024s
Consistency | Check Ontology hijacking for Open Land Use @PSNC took 32.34006118774414s
Consistency | Check Invalid usage of undefined classes for Open Land Use @PSNC took 1.3279201984405518s
Consistency | Check Invalid usage of undefined properties for Open Land Use @PSNC took 88.04198789596558s
Conciseness | Check Extensional conciseness for Open Land Use @PSNC took 2.695099115371704s
Conciseness | Check Intensional conciseness for Open Land Use @PSNC took 0.49680185317993164s
Security | Sign check for Open Land Use @PSNC took 0.9559457302093506s
Availability | Check URIs Dereferenciability for Open Land Use @PSNC took 9.994090557098389s
Completeness | Calculation of interlinking completeness for Open Land Use @PSNC took 0.46766209602355957s
Reputation | Calculation of the PageRank for Open Land Use @PSNC took 0.023008346557617188s
Interlinking | Calculation of Degree of Connection for Open Land Use @PSNC took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Open Land Use @PSNC took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Open Land Use @PSNC took 4.649162292480469e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use @PSNC took 2.384185791015625e-06s
Believability | Calculation of trust value for Open Land Use @PSNC took 1.0967254638671875e-05s
INFO | --- Analysis for Open_Land_Use took 2219.1374049186707s
Availability | SPARQL endpoint availability check for flyatlas took 1.171400785446167s
Availability | VoID file availability check for flyatlas took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for flyatlas took 0.27039456367492676s
Reputation | Calculation of the PageRank for flyatlas took 0.020473718643188477s
Interlinking | Calculation of Degree of Connection for flyatlas took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for flyatlas took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for flyatlas took 4.9591064453125e-05s
Believability | Calculation of trust value for flyatlas took 1.0728836059570312e-05s
INFO | --- Analysis for openbiomed-flyatlas took 5.0808141231536865s
Availability | SPARQL endpoint availability check for OpenCalais took 0.000240325927734375s
Availability | VoID file availability check for OpenCalais took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for OpenCalais took 0.27069640159606934s
Reputation | Calculation of the PageRank for OpenCalais took 0.020190000534057617s
Interlinking | Calculation of Degree of Connection for OpenCalais took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OpenCalais took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for OpenCalais took 0.00010800361633300781s
Believability | Calculation of trust value for OpenCalais took 1.3589859008789062e-05s
INFO | --- Analysis for opencalais took 5.985419511795044s
Availability | SPARQL endpoint availability check for OpenCorporates - The Open Database Of The Corporate World took 4.172325134277344e-05s
Availability | VoID file availability check for OpenCorporates - The Open Database Of The Corporate World took 0.0005428791046142578s
Completeness | Calculation of interlinking completeness for OpenCorporates - The Open Database Of The Corporate World took 0.27257299423217773s
Reputation | Calculation of the PageRank for OpenCorporates - The Open Database Of The Corporate World took 0.02063465118408203s
Interlinking | Calculation of Degree of Connection for OpenCorporates - The Open Database Of The Corporate World took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OpenCorporates - The Open Database Of The Corporate World took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for OpenCorporates - The Open Database Of The Corporate World took 7.462501525878906e-05s
Believability | Calculation of trust value for OpenCorporates - The Open Database Of The Corporate World took 8.106231689453125e-06s
INFO | --- Analysis for opencorporates took 2.7419214248657227s
Availability | SPARQL endpoint availability check for OpenCyc took 0.00010347366333007812s
Availability | VoID file availability check for OpenCyc took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for OpenCyc took 0.2619318962097168s
Reputation | Calculation of the PageRank for OpenCyc took 0.020446062088012695s
Interlinking | Calculation of Degree of Connection for OpenCyc took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenCyc took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for OpenCyc took 0.00010418891906738281s
Believability | Calculation of trust value for OpenCyc took 9.298324584960938e-06s
INFO | --- Analysis for opencyc took 2.5085747241973877s
Availability | SPARQL endpoint availability check for opendatacommunities-dev-local-authority-services took 8.606910705566406e-05s
Availability | VoID file availability check for opendatacommunities-dev-local-authority-services took 0.0006535053253173828s
Completeness | Calculation of interlinking completeness for opendatacommunities-dev-local-authority-services took 0.2725508213043213s
Reputation | Calculation of the PageRank for opendatacommunities-dev-local-authority-services took 0.020496368408203125s
Interlinking | Calculation of Degree of Connection for opendatacommunities-dev-local-authority-services took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-dev-local-authority-services took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-dev-local-authority-services took 3.504753112792969e-05s
Believability | Calculation of trust value for opendatacommunities-dev-local-authority-services took 1.33514404296875e-05s
INFO | --- Analysis for opendatacommunities-dev-local-authority-services took 3.273876667022705s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-acceptances-per-1000 took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-acceptances-per-1000 took 0.0005831718444824219s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-acceptances-per-1000 took 0.27461671829223633s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-acceptances-per-1000 took 0.020273923873901367s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-acceptances-per-1000 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-acceptances-per-1000 took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-acceptances-per-1000 took 3.910064697265625e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-acceptances-per-1000 took 1.0251998901367188e-05s
INFO | --- Analysis for opendatacommunities-homelessness-acceptances-per-1000 took 3.144423246383667s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 4.410743713378906e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0006809234619140625s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.2760741710662842s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.02156376838684082s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.0967254638671875e-05s
INFO | --- Analysis for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 4.597961664199829s
Availability | SPARQL endpoint availability check for opendatacommunities-households-2008 took 8.654594421386719e-05s
Availability | VoID file availability check for opendatacommunities-households-2008 took 0.0004374980926513672s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-2008 took 0.2687361240386963s
Reputation | Calculation of the PageRank for opendatacommunities-households-2008 took 0.020658254623413086s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-2008 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-2008 took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-2008 took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatacommunities-households-2008 took 9.775161743164062e-06s
INFO | --- Analysis for opendatacommunities-households-2008 took 2.585747480392456s
Availability | SPARQL endpoint availability check for opendatacommunities-households-accommodated-per-1000 took 9.059906005859375e-05s
Availability | VoID file availability check for opendatacommunities-households-accommodated-per-1000 took 0.0004951953887939453s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-accommodated-per-1000 took 0.26928019523620605s
Reputation | Calculation of the PageRank for opendatacommunities-households-accommodated-per-1000 took 0.02068018913269043s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-accommodated-per-1000 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-accommodated-per-1000 took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-accommodated-per-1000 took 3.910064697265625e-05s
Believability | Calculation of trust value for opendatacommunities-households-accommodated-per-1000 took 9.5367431640625e-06s
INFO | --- Analysis for opendatacommunities-households-accommodated-per-1000 took 3.271928310394287s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-population took 8.392333984375e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-population took 0.0002803802490234375s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-population took 0.2629714012145996s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-population took 0.020526647567749023s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-population took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-population took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-population took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-population took 1.0013580322265625e-05s
INFO | --- Analysis for opendatacommunities-households-projections-population took 4.485700607299805s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-totalhouseolds took 8.630752563476562e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-totalhouseolds took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-totalhouseolds took 0.2699882984161377s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-totalhouseolds took 0.020737886428833008s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-totalhouseolds took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-totalhouseolds took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-totalhouseolds took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-totalhouseolds took 9.298324584960938e-06s
INFO | --- Analysis for opendatacommunities-households-projections-totalhouseolds took 3.3444435596466064s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 8.654594421386719e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.2628591060638428s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.020911693572998047s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 4.100799560546875e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 2.4161665439605713s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.00010800361633300781s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0008080005645751953s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.2651238441467285s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.020390033721923828s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.1444091796875e-05s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 4.114176511764526s
Availability | SPARQL endpoint availability check for opendatacommunities-housing-market took 8.797645568847656e-05s
Availability | VoID file availability check for opendatacommunities-housing-market took 0.0005583763122558594s
Completeness | Calculation of interlinking completeness for opendatacommunities-housing-market took 0.2781519889831543s
Reputation | Calculation of the PageRank for opendatacommunities-housing-market took 0.02019810676574707s
Interlinking | Calculation of Degree of Connection for opendatacommunities-housing-market took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-housing-market took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-housing-market took 4.124641418457031e-05s
Believability | Calculation of trust value for opendatacommunities-housing-market took 1.239776611328125e-05s
INFO | --- Analysis for opendatacommunities-housing-market took 3.072683334350586s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-crime-rank-2010 took 9.202957153320312e-05s
Availability | VoID file availability check for opendatacommunities-imd-crime-rank-2010 took 0.0006690025329589844s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-crime-rank-2010 took 0.2655181884765625s
Reputation | Calculation of the PageRank for opendatacommunities-imd-crime-rank-2010 took 0.020319461822509766s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-crime-rank-2010 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-crime-rank-2010 took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-crime-rank-2010 took 4.291534423828125e-05s
Believability | Calculation of trust value for opendatacommunities-imd-crime-rank-2010 took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-imd-crime-rank-2010 took 3.2722110748291016s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-environment-rank-2010 took 8.487701416015625e-05s
Availability | VoID file availability check for opendatacommunities-imd-environment-rank-2010 took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-environment-rank-2010 took 0.2618997097015381s
Reputation | Calculation of the PageRank for opendatacommunities-imd-environment-rank-2010 took 0.020311594009399414s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-environment-rank-2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-environment-rank-2010 took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-environment-rank-2010 took 4.363059997558594e-05s
Believability | Calculation of trust value for opendatacommunities-imd-environment-rank-2010 took 1.0013580322265625e-05s
INFO | --- Analysis for opendatacommunities-imd-environment-rank-2010 took 3.1072945594787598s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-income-rank-la-2010 took 5.173683166503906e-05s
Availability | VoID file availability check for opendatacommunities-imd-income-rank-la-2010 took 0.0007348060607910156s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-income-rank-la-2010 took 0.2731184959411621s
Reputation | Calculation of the PageRank for opendatacommunities-imd-income-rank-la-2010 took 0.020579099655151367s
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.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-income-rank-la-2010 took 4.458427429199219e-05s
Believability | Calculation of trust value for opendatacommunities-imd-income-rank-la-2010 took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-imd-income-rank-la-2010 took 4.111982107162476s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-rank-2010 took 9.417533874511719e-05s
Availability | VoID file availability check for opendatacommunities-imd-rank-2010 took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-rank-2010 took 0.26448750495910645s
Reputation | Calculation of the PageRank for opendatacommunities-imd-rank-2010 took 0.02051401138305664s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-rank-2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-rank-2010 took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-rank-2010 took 4.3392181396484375e-05s
Believability | Calculation of trust value for opendatacommunities-imd-rank-2010 took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-imd-rank-2010 took 2.4694061279296875s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-score-2010 took 8.535385131835938e-05s
Availability | VoID file availability check for opendatacommunities-imd-score-2010 took 0.0005955696105957031s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-score-2010 took 0.26471805572509766s
Reputation | Calculation of the PageRank for opendatacommunities-imd-score-2010 took 0.0208585262298584s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-score-2010 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-score-2010 took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-score-2010 took 4.3392181396484375e-05s
Believability | Calculation of trust value for opendatacommunities-imd-score-2010 took 5.4836273193359375e-06s
INFO | --- Analysis for opendatacommunities-imd-score-2010 took 3.158421754837036s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 8.869171142578125e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0006694793701171875s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-affordable-housing-starts took 0.2634425163269043s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-affordable-housing-starts took 0.020380258560180664s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-affordable-housing-starts took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-affordable-housing-starts took 4.3392181396484375e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-affordable-housing-starts took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-affordable-housing-starts took 3.1244492530822754s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.458427429199219e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0005481243133544922s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.26418089866638184s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.020435571670532227s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.100799560546875e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 3.0220227241516113s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-housing-starts took 8.58306884765625e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-housing-starts took 0.00037026405334472656s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-housing-starts took 0.2621030807495117s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-housing-starts took 0.020327091217041016s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-housing-starts took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-housing-starts took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-housing-starts took 4.291534423828125e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-housing-starts took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-housing-starts took 3.213430404663086s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-planning-applications-granted took 4.982948303222656e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-planning-applications-granted took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-planning-applications-granted took 0.26242589950561523s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-planning-applications-granted took 0.020739078521728516s
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.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-planning-applications-granted took 4.1961669921875e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-planning-applications-granted took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-planning-applications-granted took 2.3791537284851074s
Availability | SPARQL endpoint availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.410743713378906e-05s
Availability | VoID file availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0012707710266113281s
Completeness | Calculation of interlinking completeness for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.2794923782348633s
Reputation | Calculation of the PageRank for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.021350622177124023s
Interlinking | Calculation of Degree of Connection for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0010213851928710938s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 5.2928924560546875e-05s
Believability | Calculation of trust value for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.825464487075806s
Availability | SPARQL endpoint availability check for opendatacommunities-net-additional-dwellings took 4.363059997558594e-05s
Availability | VoID file availability check for opendatacommunities-net-additional-dwellings took 0.0006308555603027344s
Completeness | Calculation of interlinking completeness for opendatacommunities-net-additional-dwellings took 0.26537537574768066s
Reputation | Calculation of the PageRank for opendatacommunities-net-additional-dwellings took 0.020306110382080078s
Interlinking | Calculation of Degree of Connection for opendatacommunities-net-additional-dwellings took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-net-additional-dwellings took 0.0007328987121582031s
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 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-net-additional-dwellings took 3.1396970748901367s
Availability | SPARQL endpoint availability check for opendatacommunities-service-expenditure took 0.00010395050048828125s
Availability | VoID file availability check for opendatacommunities-service-expenditure took 0.0006923675537109375s
Completeness | Calculation of interlinking completeness for opendatacommunities-service-expenditure took 0.26486754417419434s
Reputation | Calculation of the PageRank for opendatacommunities-service-expenditure took 0.02042841911315918s
Interlinking | Calculation of Degree of Connection for opendatacommunities-service-expenditure took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-service-expenditure took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-service-expenditure took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatacommunities-service-expenditure took 1.239776611328125e-05s
INFO | --- Analysis for opendatacommunities-service-expenditure took 4.560537576675415s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 8.96453857421875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0007131099700927734s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.27101659774780273s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.02037668228149414s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.3392181396484375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 5.0112950801849365s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0006237030029296875s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.28165531158447266s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.020539283752441406s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.458427429199219e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 3.9446675777435303s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 8.893013000488281e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0006108283996582031s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.2642347812652588s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.021180391311645508s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.4345855712890625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 5.9604644775390625e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 3.8365135192871094s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 8.606910705566406e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0006604194641113281s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.2645263671875s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0203855037689209s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.000705718994140625s
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 1.049041748046875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.568014860153198s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 8.988380432128906e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0006947517395019531s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.2713282108306885s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0222780704498291s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.38690185546875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.1682510375976562e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 3.6704890727996826s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 8.869171142578125e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0004508495330810547s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.2739293575286865s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.020499706268310547s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.315376281738281e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.239776611328125e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.958934545516968s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.00010609626770019531s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0006380081176757812s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.27521467208862305s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.022402524948120117s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 5.2928924560546875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 5.269050598144531e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 3.9233522415161133s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 8.821487426757812e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0006906986236572266s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.27025866508483887s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.020334243774414062s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.363059997558594e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 3.6337876319885254s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0006847381591796875s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.2624247074127197s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.022399187088012695s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.1205673217773438e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 3.5977842807769775s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.00066375732421875s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.2659332752227783s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.02149486541748047s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.363059997558594e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.217996120452881s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0003814697265625s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.2715911865234375s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.020354747772216797s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.649162292480469e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.71661376953125e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 3.583956003189087s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 8.702278137207031e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.28258442878723145s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.020236968994140625s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0006961822509765625s
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 1.1682510375976562e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 2.446981906890869s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 9.083747863769531e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0005195140838623047s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.2689633369445801s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.020322799682617188s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.410743713378906e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.1444091796875e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 2.4049630165100098s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0003867149353027344s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-housing-starts took 0.2600235939025879s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-housing-starts took 0.02031564712524414s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-housing-starts took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-housing-starts took 4.410743713378906e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-housing-starts took 1.1205673217773438e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-housing-starts took 3.5806264877319336s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.000705718994140625s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.2726576328277588s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.020191192626953125s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.1961669921875e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.049041748046875e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 3.6581544876098633s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0006372928619384766s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-troubled-families took 0.27654314041137695s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-troubled-families took 0.02038860321044922s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-troubled-families took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-troubled-families took 4.1961669921875e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-troubled-families took 1.239776611328125e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-troubled-families took 3.983463764190674s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 8.487701416015625e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0006654262542724609s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.26355934143066406s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.021201372146606445s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0007014274597167969s
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 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 3.3167197704315186s
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.0006573200225830078s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.27283453941345215s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.020502328872680664s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.792213439941406e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.1205673217773438e-05s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.566226243972778s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 8.368492126464844e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0006916522979736328s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.26709580421447754s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.020200490951538086s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 3.910064697265625e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.4066696166992188e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 5.724014759063721s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 8.559226989746094e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0006651878356933594s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.2621889114379883s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.021489858627319336s
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.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 3.7670135498046875e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 5.387603759765625s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-worthwhile-mean took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-worthwhile-mean took 0.0007376670837402344s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-worthwhile-mean took 0.2659318447113037s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-worthwhile-mean took 0.022022485733032227s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-worthwhile-mean took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-worthwhile-mean took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-worthwhile-mean took 4.5299530029296875e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-worthwhile-mean took 1.049041748046875e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-worthwhile-mean took 5.56855845451355s
Availability | SPARQL endpoint availability check for Open Data of Ecuador took 5.251063585281372s
Availability | VoID file availability check for Open Data of Ecuador took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for Open Data of Ecuador took 0.26782798767089844s
Reputation | Calculation of the PageRank for Open Data of Ecuador took 0.02015519142150879s
Interlinking | Calculation of Degree of Connection for Open Data of Ecuador took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Data of Ecuador took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Open Data of Ecuador took 8.440017700195312e-05s
Believability | Calculation of trust value for Open Data of Ecuador took 1.1682510375976562e-05s
INFO | --- Analysis for opendataec took 10.154752492904663s
Availability | SPARQL endpoint availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 4.410743713378906e-05s
Availability | VoID file availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.2769172191619873s
Reputation | Calculation of the PageRank for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.021996736526489258s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-education-pupils-by-school-and-datazone took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.0728836059570312e-05s
INFO | --- Analysis for opendatascotland-graph-education-pupils-by-school-and-datazone took 12.353173017501831s
Availability | SPARQL endpoint availability check for opendatascotland-graph-simd-rank took 8.606910705566406e-05s
Availability | VoID file availability check for opendatascotland-graph-simd-rank took 0.0007753372192382812s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-simd-rank took 0.269681453704834s
Reputation | Calculation of the PageRank for opendatascotland-graph-simd-rank took 0.020827293395996094s
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.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-simd-rank took 4.029273986816406e-05s
Believability | Calculation of trust value for opendatascotland-graph-simd-rank took 1.239776611328125e-05s
INFO | --- Analysis for opendatascotland-graph-simd-rank took 3.7864837646484375s
Availability | SPARQL endpoint availability check for opendatascotland-simd-crime-rank took 8.606910705566406e-05s
Availability | VoID file availability check for opendatascotland-simd-crime-rank took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-crime-rank took 0.26452064514160156s
Reputation | Calculation of the PageRank for opendatascotland-simd-crime-rank took 0.020568370819091797s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-crime-rank took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-crime-rank took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-crime-rank took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatascotland-simd-crime-rank took 1.2636184692382812e-05s
INFO | --- Analysis for opendatascotland-simd-crime-rank took 3.398817300796509s
Availability | SPARQL endpoint availability check for opendatascotland-simd-education-rank took 8.416175842285156e-05s
Availability | VoID file availability check for opendatascotland-simd-education-rank took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-education-rank took 0.26335740089416504s
Reputation | Calculation of the PageRank for opendatascotland-simd-education-rank took 0.022231101989746094s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-education-rank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-education-rank took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-education-rank took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatascotland-simd-education-rank took 1.2874603271484375e-05s
INFO | --- Analysis for opendatascotland-simd-education-rank took 3.675879955291748s
Availability | SPARQL endpoint availability check for opendatascotland-simd-employment-rank took 4.458427429199219e-05s
Availability | VoID file availability check for opendatascotland-simd-employment-rank took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-employment-rank took 0.26246142387390137s
Reputation | Calculation of the PageRank for opendatascotland-simd-employment-rank took 0.02050185203552246s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-employment-rank took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-employment-rank took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-employment-rank took 4.029273986816406e-05s
Believability | Calculation of trust value for opendatascotland-simd-employment-rank took 1.2159347534179688e-05s
INFO | --- Analysis for opendatascotland-simd-employment-rank took 3.376560926437378s
Availability | SPARQL endpoint availability check for opendatascotland-simd-geographic-access-rank took 8.559226989746094e-05s
Availability | VoID file availability check for opendatascotland-simd-geographic-access-rank took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-geographic-access-rank took 0.26991939544677734s
Reputation | Calculation of the PageRank for opendatascotland-simd-geographic-access-rank took 0.021368026733398438s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-geographic-access-rank took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-geographic-access-rank took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-geographic-access-rank took 4.124641418457031e-05s
Believability | Calculation of trust value for opendatascotland-simd-geographic-access-rank took 1.2636184692382812e-05s
INFO | --- Analysis for opendatascotland-simd-geographic-access-rank took 3.36897873878479s
Availability | SPARQL endpoint availability check for opendatascotland-simd-health-rank took 8.630752563476562e-05s
Availability | VoID file availability check for opendatascotland-simd-health-rank took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-health-rank took 0.2652723789215088s
Reputation | Calculation of the PageRank for opendatascotland-simd-health-rank took 0.02175736427307129s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-health-rank took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-health-rank took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-health-rank took 4.029273986816406e-05s
Believability | Calculation of trust value for opendatascotland-simd-health-rank took 1.049041748046875e-05s
INFO | --- Analysis for opendatascotland-simd-health-rank took 3.405024290084839s
Availability | SPARQL endpoint availability check for opendatascotland-simd-housing-rank took 8.630752563476562e-05s
Availability | VoID file availability check for opendatascotland-simd-housing-rank took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-housing-rank took 0.2727189064025879s
Reputation | Calculation of the PageRank for opendatascotland-simd-housing-rank took 0.02074718475341797s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-housing-rank took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-housing-rank took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-housing-rank took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatascotland-simd-housing-rank took 1.2874603271484375e-05s
INFO | --- Analysis for opendatascotland-simd-housing-rank took 3.418755054473877s
Availability | SPARQL endpoint availability check for opendatascotland-simd-income-rank took 8.678436279296875e-05s
Availability | VoID file availability check for opendatascotland-simd-income-rank took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-income-rank took 0.26962828636169434s
Reputation | Calculation of the PageRank for opendatascotland-simd-income-rank took 0.02233290672302246s
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.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-income-rank took 4.220008850097656e-05s
Believability | Calculation of trust value for opendatascotland-simd-income-rank took 1.1205673217773438e-05s
INFO | --- Analysis for opendatascotland-simd-income-rank took 2.4000630378723145s
Availability | SPARQL endpoint availability check for OpenLink Software LOD Cache took 30.634769201278687s
Availability | VoID file availability check for OpenLink Software LOD Cache took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for OpenLink Software LOD Cache took 0.2622828483581543s
Reputation | Calculation of the PageRank for OpenLink Software LOD Cache took 0.021856069564819336s
Interlinking | Calculation of Degree of Connection for OpenLink Software LOD Cache took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for OpenLink Software LOD Cache took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for OpenLink Software LOD Cache took 3.814697265625e-05s
Believability | Calculation of trust value for OpenLink Software LOD Cache took 1.3113021850585938e-05s
INFO | --- Analysis for openlink-lod-cache took 63.06591320037842s
Availability | SPARQL endpoint availability check for openlinksw dataspaces took 8.893013000488281e-05s
Availability | VoID file availability check for openlinksw dataspaces took 0.00061798095703125s
Completeness | Calculation of interlinking completeness for openlinksw dataspaces took 0.2844662666320801s
Reputation | Calculation of the PageRank for openlinksw dataspaces took 0.020667076110839844s
Interlinking | Calculation of Degree of Connection for openlinksw dataspaces took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for openlinksw dataspaces took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for openlinksw dataspaces took 9.512901306152344e-05s
Believability | Calculation of trust value for openlinksw dataspaces took 1.2159347534179688e-05s
INFO | --- Analysis for openlinksw-dataspaces took 2.9822440147399902s
Availability | SPARQL endpoint availability check for Openly Local :: Making Local Government More Transparent took 8.654594421386719e-05s
Availability | VoID file availability check for Openly Local :: Making Local Government More Transparent took 0.0007615089416503906s
Completeness | Calculation of interlinking completeness for Openly Local :: Making Local Government More Transparent took 0.27379560470581055s
Reputation | Calculation of the PageRank for Openly Local :: Making Local Government More Transparent took 0.02258610725402832s
Interlinking | Calculation of Degree of Connection for Openly Local :: Making Local Government More Transparent took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Openly Local :: Making Local Government More Transparent took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Openly Local :: Making Local Government More Transparent took 9.584426879882812e-05s
Believability | Calculation of trust value for Openly Local :: Making Local Government More Transparent took 5.4836273193359375e-06s
INFO | --- Analysis for openlylocal took 12.039380311965942s
Availability | SPARQL endpoint availability check for OpenMobileNetwork took 1.3387904167175293s
Availability | VoID file availability check for OpenMobileNetwork took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for OpenMobileNetwork took 0.27522778511047363s
Reputation | Calculation of the PageRank for OpenMobileNetwork took 0.021333932876586914s
Interlinking | Calculation of Degree of Connection for OpenMobileNetwork took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OpenMobileNetwork took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for OpenMobileNetwork took 7.319450378417969e-05s
Believability | Calculation of trust value for OpenMobileNetwork took 1.1444091796875e-05s
INFO | --- Analysis for openmobilenetwork took 4.756998777389526s
Availability | SPARQL endpoint availability check for Ordnance Survey Linked Data took 0.8771741390228271s
Availability | VoID file availability check for Ordnance Survey Linked Data took 0.0005757808685302734s
Completeness | Calculation of interlinking completeness for Ordnance Survey Linked Data took 0.2711458206176758s
Reputation | Calculation of the PageRank for Ordnance Survey Linked Data took 0.02020740509033203s
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.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey Linked Data took 9.560585021972656e-05s
Believability | Calculation of trust value for Ordnance Survey Linked Data took 1.0967254638671875e-05s
INFO | --- Analysis for ordnance-survey-linked-data took 5.438831567764282s
Availability | SPARQL endpoint availability check for oreilly took 8.893013000488281e-05s
Availability | VoID file availability check for oreilly took 0.0005075931549072266s
Completeness | Calculation of interlinking completeness for oreilly took 0.2691977024078369s
Reputation | Calculation of the PageRank for oreilly took 0.021035432815551758s
Interlinking | Calculation of Degree of Connection for oreilly took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for oreilly took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for oreilly took 4.673004150390625e-05s
Believability | Calculation of trust value for oreilly took 1.2636184692382812e-05s
INFO | --- Analysis for oreilly took 4.015252351760864s
Availability | SPARQL endpoint availability check for Medicine and Natural Product Data took 3.3363311290740967s
Availability | VoID file availability check for Medicine and Natural Product Data took 0.001032114028930664s
Completeness | Calculation of interlinking completeness for Medicine and Natural Product Data took 0.2657308578491211s
Reputation | Calculation of the PageRank for Medicine and Natural Product Data took 0.022893428802490234s
Interlinking | Calculation of Degree of Connection for Medicine and Natural Product Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Medicine and Natural Product Data took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for Medicine and Natural Product Data took 3.24249267578125e-05s
Believability | Calculation of trust value for Medicine and Natural Product Data took 1.3589859008789062e-05s
INFO | --- Analysis for Organchem-Data took 7.1755805015563965s
Availability | SPARQL endpoint availability check for Organic Edunet Linked Open Data took 0.04128241539001465s
Availability | VoID file availability check for Organic Edunet Linked Open Data took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for Organic Edunet Linked Open Data took 0.27217555046081543s
Reputation | Calculation of the PageRank for Organic Edunet Linked Open Data took 0.02077627182006836s
Interlinking | Calculation of Degree of Connection for Organic Edunet Linked Open Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Organic Edunet Linked Open Data took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Organic Edunet Linked Open Data took 7.414817810058594e-05s
Believability | Calculation of trust value for Organic Edunet Linked Open Data took 1.1444091796875e-05s
INFO | --- Analysis for organic-edunet took 8.514837265014648s
Availability | SPARQL endpoint availability check for Open Research Knowledge Graph (ORKG) took 0.32197141647338867s
Availability | VoID file availability check for Open Research Knowledge Graph (ORKG) took 0.0006074905395507812s
Extra | Recovery of all triples for Open Research Knowledge Graph (ORKG) took 5.7621238231658936s
Performance | Total latancy measurement for Open Research Knowledge Graph (ORKG) took 0.6498701572418213s
Amount of data | Number of triples check for Open Research Knowledge Graph (ORKG) took 0.13978242874145508s
Interoperability | New terms check for Open Research Knowledge Graph (ORKG) took 1.5828008651733398s
Versatility | Languages check for Open Research Knowledge Graph (ORKG) took 6.261128187179565s
Interpretability | Number of blank nodes check for Open Research Knowledge Graph (ORKG) took 0.11998414993286133s
Interpretability | RDF structures check for Open Research Knowledge Graph (ORKG) took 0.25586819648742676s
Versatility | Serialization formats check for Open Research Knowledge Graph (ORKG) took 0.12498283386230469s
Availability | RDF dump link check for Open Research Knowledge Graph (ORKG) took 0.11946797370910645s
License | MR license check for Open Research Knowledge Graph (ORKG) took 0.12109518051147461s
License | HR license check for Open Research Knowledge Graph (ORKG) took 4.034592390060425s
Amount of data | Number of property check for Open Research Knowledge Graph (ORKG) took 0.12453532218933105s
Understandability | Number of label check for Open Research Knowledge Graph (ORKG) took 0.16393566131591797s
Understandability | URI regex check for Open Research Knowledge Graph (ORKG) took 0.31121349334716797s
Understandability | Vocabs check for Open Research Knowledge Graph (ORKG) took 0.13831591606140137s
Verifiability | Authors check for Open Research Knowledge Graph (ORKG) took 0.12332606315612793s
Verifiability | Publishers check for Open Research Knowledge Graph (ORKG) took 0.13984012603759766s
Performance | Throughput check for Open Research Knowledge Graph (ORKG) took 10.709070205688477s
Amount of data | Check the number of entities for Open Research Knowledge Graph (ORKG) took 7.2479248046875e-05s
Verifiability | Contribs. check for Open Research Knowledge Graph (ORKG) took 0.14352965354919434s
Interlinking | sameAs chians check for Open Research Knowledge Graph (ORKG) took 0.13930535316467285s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.15523862838745117s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.1745915412902832s
Timeliness | dataset update frequency check for Open Research Knowledge Graph (ORKG) took 0.1420910358428955s
Currency | Creation date check for Open Research Knowledge Graph (ORKG) took 0.3621859550476074s
Currency | Modification date check for Open Research Knowledge Graph (ORKG) took 0.3385279178619385s
Rep.Conc. | URIs length for Open Research Knowledge Graph (ORKG) took 3.7030298709869385s
Interoperability | New vocabularies check for Open Research Knowledge Graph (ORKG) took 5.0067901611328125e-06s
Consistency | Deprecated classes/propertiers check for Open Research Knowledge Graph (ORKG) took 0.13755297660827637s
Accuracy | Check Functional Property for Open Research Knowledge Graph (ORKG) took 0.19657588005065918s
Accuracy | Check Inverse Functional Property for Open Research Knowledge Graph (ORKG) took 0.23331212997436523s
Accuracy | Check Empty annotation labels for Open Research Knowledge Graph (ORKG) took 2.3209731578826904s
Accuracy | Check White space in annotation for Open Research Knowledge Graph (ORKG) took 0.28989720344543457s
Accuracy | Check Datatype consistency for Open Research Knowledge Graph (ORKG) took 0.2673666477203369s
Consistency | Disjoint class check for Open Research Knowledge Graph (ORKG) took 0.22298955917358398s
Consistency | Check Misplaced properties for Open Research Knowledge Graph (ORKG) took 1.2529544830322266s
Consistency | Misplaced classes for Open Research Knowledge Graph (ORKG) took 0.837923526763916s
Consistency | Check Ontology hijacking for Open Research Knowledge Graph (ORKG) took 3.059298038482666s
Consistency | Check Invalid usage of undefined classes for Open Research Knowledge Graph (ORKG) took 1.2518587112426758s
Consistency | Check Invalid usage of undefined properties for Open Research Knowledge Graph (ORKG) took 1.9332149028778076s
Conciseness | Check Extensional conciseness for Open Research Knowledge Graph (ORKG) took 0.27800583839416504s
Conciseness | Check Intensional conciseness for Open Research Knowledge Graph (ORKG) took 0.12053394317626953s
Security | Sign check for Open Research Knowledge Graph (ORKG) took 0.14504694938659668s
Availability | Check URIs Dereferenciability for Open Research Knowledge Graph (ORKG) took 1859.5305862426758s
Completeness | Calculation of interlinking completeness for Open Research Knowledge Graph (ORKG) took 0.658240795135498s
Reputation | Calculation of the PageRank for Open Research Knowledge Graph (ORKG) took 0.02209782600402832s
Interlinking | Calculation of Degree of Connection for Open Research Knowledge Graph (ORKG) took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Open Research Knowledge Graph (ORKG) took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Open Research Knowledge Graph (ORKG) took 1.7881393432617188e-05s
Interoperability | Check the re-using of existing vocabs for Open Research Knowledge Graph (ORKG) took 4.5299530029296875e-06s
Believability | Calculation of trust value for Open Research Knowledge Graph (ORKG) took 1.1920928955078125e-05s
INFO | --- Analysis for orkg took 2086.059372663498s
Availability | SPARQL endpoint availability check for The Orlando Women's Writing Linked Open Data Set took 2.810462713241577s
Availability | VoID file availability check for The Orlando Women's Writing Linked Open Data Set took 0.0006427764892578125s
Completeness | Calculation of interlinking completeness for The Orlando Women's Writing Linked Open Data Set took 0.2648952007293701s
Reputation | Calculation of the PageRank for The Orlando Women's Writing Linked Open Data Set took 0.020409584045410156s
Interlinking | Calculation of Degree of Connection for The Orlando Women's Writing Linked Open Data Set took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The Orlando Women's Writing Linked Open Data Set took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for The Orlando Women's Writing Linked Open Data Set took 9.369850158691406e-05s
Believability | Calculation of trust value for The Orlando Women's Writing Linked Open Data Set took 1.3589859008789062e-05s
INFO | --- Analysis for orlando-womens-writing-linked-open-data-set took 28.129515647888184s
Availability | SPARQL endpoint availability check for OSM Semantic Network took 1.4686863422393799s
Availability | VoID file availability check for OSM Semantic Network took 0.0006310939788818359s
Completeness | Calculation of interlinking completeness for OSM Semantic Network took 0.2795422077178955s
Reputation | Calculation of the PageRank for OSM Semantic Network took 0.020434856414794922s
Interlinking | Calculation of Degree of Connection for OSM Semantic Network took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for OSM Semantic Network took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for OSM Semantic Network took 3.7670135498046875e-05s
Believability | Calculation of trust value for OSM Semantic Network took 6.67572021484375e-06s
INFO | --- Analysis for osm-semantic-network took 7.8178887367248535s
Availability | SPARQL endpoint availability check for Open Transport Map @PSNC took 0.31444406509399414s
Availability | VoID file availability check for Open Transport Map @PSNC took 0.00048351287841796875s
Extra | Recovery of all triples for Open Transport Map @PSNC took 120.58434677124023s
Performance | Total latancy measurement for Open Transport Map @PSNC took 0.8874199390411377s
Amount of data | Number of triples check for Open Transport Map @PSNC took 9.001270294189453s
Interoperability | New terms check for Open Transport Map @PSNC took 14.37470817565918s
Versatility | Languages check for Open Transport Map @PSNC took 300.1791367530823s
Interpretability | Number of blank nodes check for Open Transport Map @PSNC took 7.458030462265015s
Interpretability | RDF structures check for Open Transport Map @PSNC took 0.26455044746398926s
Versatility | Serialization formats check for Open Transport Map @PSNC took 12.859459161758423s
Availability | RDF dump link check for Open Transport Map @PSNC took 0.2796022891998291s
License | MR license check for Open Transport Map @PSNC took 0.6119096279144287s
License | HR license check for Open Transport Map @PSNC took 300.1954061985016s
Amount of data | Number of property check for Open Transport Map @PSNC took 0.18303990364074707s
Understandability | Number of label check for Open Transport Map @PSNC took 2.0592715740203857s
Understandability | URI regex check for Open Transport Map @PSNC took 0.6562092304229736s
Understandability | Vocabs check for Open Transport Map @PSNC took 0.34079909324645996s
Verifiability | Authors check for Open Transport Map @PSNC took 0.18293023109436035s
Verifiability | Publishers check for Open Transport Map @PSNC took 0.22818636894226074s
Performance | Throughput check for Open Transport Map @PSNC took 10.674245357513428s
Amount of data | Check the number of entities for Open Transport Map @PSNC took 0.00010609626770019531s
Verifiability | Contribs. check for Open Transport Map @PSNC took 0.1857128143310547s
Interlinking | sameAs chians check for Open Transport Map @PSNC took 0.18720316886901855s
Interlinking | skos check for Open Transport Map @PSNC took 0.42613959312438965s
Interlinking | skos check for Open Transport Map @PSNC took 0.4229130744934082s
Timeliness | dataset update frequency check for Open Transport Map @PSNC took 4.649902105331421s
Currency | Creation date check for Open Transport Map @PSNC took 0.4368553161621094s
Currency | Modification date check for Open Transport Map @PSNC took 0.22847700119018555s
Rep.Conc. | URIs length for Open Transport Map @PSNC took 155.2463836669922s
Interoperability | New vocabularies check for Open Transport Map @PSNC took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Open Transport Map @PSNC took 0.18164515495300293s
Accuracy | Check Functional Property for Open Transport Map @PSNC took 0.39180994033813477s
Accuracy | Check Inverse Functional Property for Open Transport Map @PSNC took 0.4198112487792969s
Accuracy | Check Empty annotation labels for Open Transport Map @PSNC took 36.461461544036865s
Accuracy | Check White space in annotation for Open Transport Map @PSNC took 2.6314027309417725s
Accuracy | Check Datatype consistency for Open Transport Map @PSNC took 2.5655908584594727s
Consistency | Disjoint class check for Open Transport Map @PSNC took 0.17968010902404785s
Consistency | Check Misplaced properties for Open Transport Map @PSNC took 86.9342269897461s
Consistency | Misplaced classes for Open Transport Map @PSNC took 8.15300726890564s
Consistency | Check Ontology hijacking for Open Transport Map @PSNC took 34.3837525844574s
Consistency | Check Invalid usage of undefined classes for Open Transport Map @PSNC took 1.327885627746582s
Consistency | Check Invalid usage of undefined properties for Open Transport Map @PSNC took 88.261390209198s
Conciseness | Check Extensional conciseness for Open Transport Map @PSNC took 2.6844866275787354s
Conciseness | Check Intensional conciseness for Open Transport Map @PSNC took 0.515073299407959s
Security | Sign check for Open Transport Map @PSNC took 0.9613838195800781s
Availability | Check URIs Dereferenciability for Open Transport Map @PSNC took 9.955746412277222s
Completeness | Calculation of interlinking completeness for Open Transport Map @PSNC took 0.3753852844238281s
Reputation | Calculation of the PageRank for Open Transport Map @PSNC took 0.020799875259399414s
Interlinking | Calculation of Degree of Connection for Open Transport Map @PSNC took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Open Transport Map @PSNC took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Open Transport Map @PSNC took 3.8623809814453125e-05s
Interoperability | Check the re-using of existing vocabs for Open Transport Map @PSNC took 1.430511474609375e-06s
Believability | Calculation of trust value for Open Transport Map @PSNC took 1.1444091796875e-05s
INFO | --- Analysis for OTM took 2256.701008796692s
Availability | SPARQL endpoint availability check for Pali English Lexicon took 1.479539394378662s
Availability | VoID file availability check for Pali English Lexicon took 0.0005567073822021484s
Completeness | Calculation of interlinking completeness for Pali English Lexicon took 0.27217698097229004s
Reputation | Calculation of the PageRank for Pali English Lexicon took 0.022084474563598633s
Interlinking | Calculation of Degree of Connection for Pali English Lexicon took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Pali English Lexicon took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Pali English Lexicon took 3.0279159545898438e-05s
Believability | Calculation of trust value for Pali English Lexicon took 1.0967254638671875e-05s
INFO | --- Analysis for pali-english-lexicon took 7.547783136367798s
Availability | SPARQL endpoint availability check for PanLex took 1.7357165813446045s
Availability | VoID file availability check for PanLex took 0.0004105567932128906s
Completeness | Calculation of interlinking completeness for PanLex took 0.2699260711669922s
Reputation | Calculation of the PageRank for PanLex took 0.023028850555419922s
Interlinking | Calculation of Degree of Connection for PanLex took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for PanLex took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for PanLex took 7.200241088867188e-05s
Believability | Calculation of trust value for PanLex took 1.0251998901367188e-05s
INFO | --- Analysis for panlex took 4.186659574508667s
Availability | SPARQL endpoint availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 8.916854858398438e-05s
Availability | VoID file availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for Parole/Simple 'lexinfo' Ontology & lexicons took 0.2936069965362549s
Reputation | Calculation of the PageRank for Parole/Simple 'lexinfo' Ontology & lexicons took 0.020528078079223633s
Interlinking | Calculation of Degree of Connection for Parole/Simple 'lexinfo' Ontology & lexicons took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Parole/Simple 'lexinfo' Ontology & lexicons took 3.9577484130859375e-05s
Believability | Calculation of trust value for Parole/Simple 'lexinfo' Ontology & lexicons took 1.0967254638671875e-05s
INFO | --- Analysis for parole-simple-lexinfo-ontology-lexicons took 5.361968994140625s
Availability | SPARQL endpoint availability check for patents.data.gov.uk took 0.07242107391357422s
Availability | VoID file availability check for patents.data.gov.uk took 0.00040841102600097656s
Completeness | Calculation of interlinking completeness for patents.data.gov.uk took 0.2714042663574219s
Reputation | Calculation of the PageRank for patents.data.gov.uk took 0.022096633911132812s
Interlinking | Calculation of Degree of Connection for patents.data.gov.uk took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for patents.data.gov.uk took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for patents.data.gov.uk took 5.14984130859375e-05s
Believability | Calculation of trust value for patents.data.gov.uk took 7.62939453125e-06s
INFO | --- Analysis for patents-data-gov-uk took 2.567119598388672s
Availability | SPARQL endpoint availability check for PDEV-Lemon took 4.410743713378906e-05s
Availability | VoID file availability check for PDEV-Lemon took 0.0005595684051513672s
Completeness | Calculation of interlinking completeness for PDEV-Lemon took 0.27222418785095215s
Reputation | Calculation of the PageRank for PDEV-Lemon took 0.02106189727783203s
Interlinking | Calculation of Degree of Connection for PDEV-Lemon took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PDEV-Lemon took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for PDEV-Lemon took 4.57763671875e-05s
Believability | Calculation of trust value for PDEV-Lemon took 1.2159347534179688e-05s
INFO | --- Analysis for pdev-lemon took 3.6675899028778076s
Availability | SPARQL endpoint availability check for pdevlemon took 5.650520324707031e-05s
Availability | VoID file availability check for pdevlemon took 0.0006589889526367188s
Completeness | Calculation of interlinking completeness for pdevlemon took 0.2756783962249756s
Reputation | Calculation of the PageRank for pdevlemon took 0.020584821701049805s
Interlinking | Calculation of Degree of Connection for pdevlemon took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for pdevlemon took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for pdevlemon took 3.147125244140625e-05s
Believability | Calculation of trust value for pdevlemon took 1.239776611328125e-05s
INFO | --- Analysis for pdevlemon took 3.0438201427459717s
Availability | SPARQL endpoint availability check for PeriodO Period Gazetteer took 8.392333984375e-05s
Availability | VoID file availability check for PeriodO Period Gazetteer took 0.0015120506286621094s
Completeness | Calculation of interlinking completeness for PeriodO Period Gazetteer took 0.27013468742370605s
Reputation | Calculation of the PageRank for PeriodO Period Gazetteer took 0.020708084106445312s
Interlinking | Calculation of Degree of Connection for PeriodO Period Gazetteer took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for PeriodO Period Gazetteer took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for PeriodO Period Gazetteer took 8.034706115722656e-05s
Believability | Calculation of trust value for PeriodO Period Gazetteer took 1.239776611328125e-05s
INFO | --- Analysis for periodo took 18.580110788345337s
Availability | SPARQL endpoint availability check for Personal_Homepages took 4.5299530029296875e-05s
Availability | VoID file availability check for Personal_Homepages took 0.0002944469451904297s
Completeness | Calculation of interlinking completeness for Personal_Homepages took 0.27027392387390137s
Reputation | Calculation of the PageRank for Personal_Homepages took 0.020262479782104492s
Interlinking | Calculation of Degree of Connection for Personal_Homepages took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Personal_Homepages took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Personal_Homepages took 0.00040459632873535156s
Believability | Calculation of trust value for Personal_Homepages took 6.9141387939453125e-06s
INFO | --- Analysis for personal-homepages took 2.4268951416015625s
Availability | SPARQL endpoint availability check for Ontology of University People took 8.630752563476562e-05s
Availability | VoID file availability check for Ontology of University People took 0.0009474754333496094s
Completeness | Calculation of interlinking completeness for Ontology of University People took 0.26163697242736816s
Reputation | Calculation of the PageRank for Ontology of University People took 0.02049851417541504s
Interlinking | Calculation of Degree of Connection for Ontology of University People took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Ontology of University People took 0.0008943080902099609s
Interlinking | Calculation of Clustering coefficient for Ontology of University People took 3.695487976074219e-05s
Believability | Calculation of trust value for Ontology of University People took 1.33514404296875e-05s
INFO | --- Analysis for PersonOnto took 2.3978028297424316s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 4.6106390953063965s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.26364684104919434s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.02219986915588379s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007121562957763672s
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 7.3909759521484375e-06s
INFO | --- Analysis for PFKHS took 8.67917251586914s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 3.383842706680298s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0006086826324462891s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.2656996250152588s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.020259380340576172s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.52587890625e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.1444091796875e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 9.775161743164062e-06s
INFO | --- Analysis for PFRPPH took 7.370736598968506s
Availability | SPARQL endpoint availability check for PGxLOD took 0.3626220226287842s
Availability | VoID file availability check for PGxLOD took 0.0006206035614013672s
Extra | Recovery of all triples for PGxLOD took 1.6820240020751953s
Performance | Total latancy measurement for PGxLOD took 0.7484917640686035s
Amount of data | Number of triples check for PGxLOD took 0.8006951808929443s
Interoperability | New terms check for PGxLOD took 1.8553402423858643s
Versatility | Languages check for PGxLOD took 60.342721939086914s
Interpretability | Number of blank nodes check for PGxLOD took 1.6909210681915283s
Interpretability | RDF structures check for PGxLOD took 0.429332971572876s
Versatility | Serialization formats check for PGxLOD took 0.2141246795654297s
Availability | RDF dump link check for PGxLOD took 14.34898328781128s
License | MR license check for PGxLOD took 0.18168115615844727s
License | HR license check for PGxLOD took 60.50850296020508s
Amount of data | Number of property check for PGxLOD took 0.18248581886291504s
Understandability | Number of label check for PGxLOD took 2.5195584297180176s
Understandability | URI regex check for PGxLOD took 0.3108680248260498s
Understandability | Vocabs check for PGxLOD took 0.1522836685180664s
Verifiability | Authors check for PGxLOD took 0.22498440742492676s
Verifiability | Publishers check for PGxLOD took 0.1536097526550293s
Performance | Throughput check for PGxLOD took 10.472451448440552s
Amount of data | Check the number of entities for PGxLOD took 0.11625170707702637s
Verifiability | Contribs. check for PGxLOD took 0.1588597297668457s
Interlinking | sameAs chians check for PGxLOD took 0.2641589641571045s
Interlinking | skos check for PGxLOD took 0.31753063201904297s
Interlinking | skos check for PGxLOD took 0.18675589561462402s
Timeliness | dataset update frequency check for PGxLOD took 0.16698265075683594s
Currency | Creation date check for PGxLOD took 0.328383207321167s
Currency | Modification date check for PGxLOD took 0.31110620498657227s
Rep.Conc. | URIs length for PGxLOD took 6.822422027587891s
Interoperability | New vocabularies check for PGxLOD took 7.804337501525879s
Consistency | Deprecated classes/propertiers check for PGxLOD took 0.14844202995300293s
Accuracy | Check Functional Property for PGxLOD took 0.19070982933044434s
Accuracy | Check Inverse Functional Property for PGxLOD took 0.1842048168182373s
Accuracy | Check Empty annotation labels for PGxLOD took 0.7019977569580078s
Accuracy | Check White space in annotation for PGxLOD took 0.03684687614440918s
Accuracy | Check Datatype consistency for PGxLOD took 0.027524471282958984s
Consistency | Disjoint class check for PGxLOD took 0.15054082870483398s
Consistency | Check Misplaced properties for PGxLOD took 6.5860748291015625s
Consistency | Misplaced classes for PGxLOD took 0.282818078994751s
Consistency | Check Ontology hijacking for PGxLOD took 1.934325933456421s
Consistency | Check Invalid usage of undefined classes for PGxLOD took 1.2195801734924316s
Consistency | Check Invalid usage of undefined properties for PGxLOD took 7.310596466064453s
Conciseness | Check Extensional conciseness for PGxLOD took 0.0323033332824707s
Conciseness | Check Intensional conciseness for PGxLOD took 0.32044267654418945s
Security | Sign check for PGxLOD took 0.1840362548828125s
Availability | Check URIs Dereferenciability for PGxLOD took 2256.930453300476s
Completeness | Calculation of interlinking completeness for PGxLOD took 0.6318402290344238s
Reputation | Calculation of the PageRank for PGxLOD took 0.02153754234313965s
Interlinking | Calculation of Degree of Connection for PGxLOD took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for PGxLOD took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for PGxLOD took 5.412101745605469e-05s
Interoperability | Check the re-using of existing vocabs for PGxLOD took 35.67540979385376s
Believability | Calculation of trust value for PGxLOD took 1.1920928955078125e-05s
INFO | --- Analysis for PGxLOD took 3473.7054398059845s
Availability | SPARQL endpoint availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.8444385528564453s
Availability | VoID file availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0008199214935302734s
Completeness | Calculation of interlinking completeness for Phonetics Information Base and Lexicon (PHOIBLE) took 0.2754361629486084s
Reputation | Calculation of the PageRank for Phonetics Information Base and Lexicon (PHOIBLE) took 0.02117156982421875s
Interlinking | Calculation of Degree of Connection for Phonetics Information Base and Lexicon (PHOIBLE) took 8.130073547363281e-05s
Interlinking | Calculation of Centrality for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0008192062377929688s
Interlinking | Calculation of Clustering coefficient for Phonetics Information Base and Lexicon (PHOIBLE) took 4.2438507080078125e-05s
Believability | Calculation of trust value for Phonetics Information Base and Lexicon (PHOIBLE) took 1.3828277587890625e-05s
INFO | --- Analysis for phoible took 4.580068588256836s
Availability | SPARQL endpoint availability check for Parallel ice sheet model took 7.033348083496094e-05s
Availability | VoID file availability check for Parallel ice sheet model took 0.0007421970367431641s
Completeness | Calculation of interlinking completeness for Parallel ice sheet model took 0.26960062980651855s
Reputation | Calculation of the PageRank for Parallel ice sheet model took 0.022098779678344727s
Interlinking | Calculation of Degree of Connection for Parallel ice sheet model took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Parallel ice sheet model took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Parallel ice sheet model took 3.1948089599609375e-05s
Believability | Calculation of trust value for Parallel ice sheet model took 1.2636184692382812e-05s
INFO | --- Analysis for PISM took 13.063283443450928s
Availability | SPARQL endpoint availability check for PlanetData Project Wiki took 4.2438507080078125e-05s
Availability | VoID file availability check for PlanetData Project Wiki took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for PlanetData Project Wiki took 0.2631521224975586s
Reputation | Calculation of the PageRank for PlanetData Project Wiki took 0.02109527587890625s
Interlinking | Calculation of Degree of Connection for PlanetData Project Wiki took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for PlanetData Project Wiki took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for PlanetData Project Wiki took 8.797645568847656e-05s
Believability | Calculation of trust value for PlanetData Project Wiki took 1.1682510375976562e-05s
INFO | --- Analysis for planetdata-project-wiki took 2.475642442703247s
Availability | SPARQL endpoint availability check for digitized plant specimen took 1.204655647277832s
Availability | VoID file availability check for digitized plant specimen took 0.0002887248992919922s
Completeness | Calculation of interlinking completeness for digitized plant specimen took 0.27742457389831543s
Reputation | Calculation of the PageRank for digitized plant specimen took 0.021355152130126953s
Interlinking | Calculation of Degree of Connection for digitized plant specimen took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for digitized plant specimen took 0.0007784366607666016s
Interlinking | Calculation of Clustering coefficient for digitized plant specimen took 7.534027099609375e-05s
Believability | Calculation of trust value for digitized plant specimen took 1.0728836059570312e-05s
INFO | --- Analysis for plant-specimen took 3.6813571453094482s
Availability | SPARQL endpoint availability check for Pleiades took 0.00012731552124023438s
Availability | VoID file availability check for Pleiades took 0.0004379749298095703s
Completeness | Calculation of interlinking completeness for Pleiades took 0.26354026794433594s
Reputation | Calculation of the PageRank for Pleiades took 0.025860071182250977s
Interlinking | Calculation of Degree of Connection for Pleiades took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Pleiades took 0.0009770393371582031s
Interlinking | Calculation of Clustering coefficient for Pleiades took 0.00010609626770019531s
Believability | Calculation of trust value for Pleiades took 1.239776611328125e-05s
INFO | --- Analysis for pleiades took 13.113872766494751s
Availability | SPARQL endpoint availability check for podorozhnyk.com took 8.463859558105469e-05s
Availability | VoID file availability check for podorozhnyk.com took 0.0008571147918701172s
Completeness | Calculation of interlinking completeness for podorozhnyk.com took 0.28066086769104004s
Reputation | Calculation of the PageRank for podorozhnyk.com took 0.021323204040527344s
Interlinking | Calculation of Degree of Connection for podorozhnyk.com took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for podorozhnyk.com took 0.0010135173797607422s
Interlinking | Calculation of Clustering coefficient for podorozhnyk.com took 3.981590270996094e-05s
Believability | Calculation of trust value for podorozhnyk.com took 1.239776611328125e-05s
INFO | --- Analysis for podorozhnyk took 3.125681161880493s
Availability | SPARQL endpoint availability check for Poképédia took 9.465217590332031e-05s
Availability | VoID file availability check for Poképédia took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for Poképédia took 0.26033592224121094s
Reputation | Calculation of the PageRank for Poképédia took 0.020674467086791992s
Interlinking | Calculation of Degree of Connection for Poképédia took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Poképédia took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Poképédia took 7.748603820800781e-05s
Believability | Calculation of trust value for Poképédia took 7.152557373046875e-06s
INFO | --- Analysis for pokepedia-fr took 2.5691685676574707s
Availability | SPARQL endpoint availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 4.863739013671875e-05s
Availability | VoID file availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0007894039154052734s
Completeness | Calculation of interlinking completeness for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.27672433853149414s
Reputation | Calculation of the PageRank for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0209808349609375s
Interlinking | Calculation of Degree of Connection for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 7.462501525878906e-05s
Believability | Calculation of trust value for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.2636184692382812e-05s
INFO | --- Analysis for polymath-virtual-library took 5.555716037750244s
Availability | SPARQL endpoint availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.2418532371520996s
Availability | VoID file availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.00048279762268066406s
Extra | Recovery of all triples for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 10.652540922164917s
Performance | Total latancy measurement for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.5651130676269531s
Amount of data | Number of triples check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.4010739326477051s
Interoperability | New terms check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.5376458168029785s
Versatility | Languages check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.3617653846740723s
Interpretability | Number of blank nodes check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.36496686935424805s
Interpretability | RDF structures check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11794734001159668s
Versatility | Serialization formats check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11599445343017578s
Availability | RDF dump link check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11948537826538086s
License | MR license check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1147007942199707s
License | HR license check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.6443560123443604s
Amount of data | Number of property check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11597561836242676s
Understandability | Number of label check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.15511202812194824s
Understandability | URI regex check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.2320699691772461s
Understandability | Vocabs check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11837530136108398s
Verifiability | Authors check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1156163215637207s
Verifiability | Publishers check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11470198631286621s
Performance | Throughput check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 10.429559707641602s
Amount of data | Check the number of entities for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 7.176399230957031e-05s
Verifiability | Contribs. check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11562800407409668s
Interlinking | sameAs chians check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.13223481178283691s
Interlinking | skos check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1459043025970459s
Interlinking | skos check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11433720588684082s
Timeliness | dataset update frequency check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11553621292114258s
Currency | Creation date check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.23042750358581543s
Currency | Modification date check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.2304096221923828s
Rep.Conc. | URIs length for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 6.319410562515259s
Interoperability | New vocabularies check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11638784408569336s
Accuracy | Check Functional Property for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12942028045654297s
Accuracy | Check Inverse Functional Property for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11207747459411621s
Accuracy | Check Empty annotation labels for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 3.2881956100463867s
Accuracy | Check White space in annotation for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.19272875785827637s
Accuracy | Check Datatype consistency for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 3.8081912994384766s
Consistency | Disjoint class check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11572146415710449s
Consistency | Check Misplaced properties for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.8438601493835449s
Consistency | Check Ontology hijacking for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 3.4284489154815674s
Consistency | Check Invalid usage of undefined classes for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.2895355224609375s
Consistency | Check Invalid usage of undefined properties for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.0686798095703125s
Conciseness | Check Extensional conciseness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.446368455886841s
Security | Sign check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11294198036193848s
Availability | Check URIs Dereferenciability for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 4727.0543694496155s
Completeness | Calculation of interlinking completeness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.7290194034576416s
Reputation | Calculation of the PageRank for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.021111249923706055s
Interlinking | Calculation of Degree of Connection for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.2874603271484375e-05s
Interoperability | Check the re-using of existing vocabs for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.9073486328125e-06s
Believability | Calculation of trust value for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.3589859008789062e-05s
INFO | --- Analysis for portuguese_prisons_releases took 4798.555550336838s
Availability | SPARQL endpoint availability check for prefix.cc took 9.679794311523438e-05s
Availability | VoID file availability check for prefix.cc took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for prefix.cc took 0.2809104919433594s
Reputation | Calculation of the PageRank for prefix.cc took 0.020395755767822266s
Interlinking | Calculation of Degree of Connection for prefix.cc took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for prefix.cc took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for prefix.cc took 3.8623809814453125e-05s
Believability | Calculation of trust value for prefix.cc took 1.1920928955078125e-05s
INFO | --- Analysis for prefix-cc took 3.105745792388916s
Availability | SPARQL endpoint availability check for PREJUST4WOMEN Knowledge Graph took 1.4892561435699463s
Availability | VoID file availability check for PREJUST4WOMEN Knowledge Graph took 0.000766754150390625s
Completeness | Calculation of interlinking completeness for PREJUST4WOMEN Knowledge Graph took 0.2696552276611328s
Reputation | Calculation of the PageRank for PREJUST4WOMEN Knowledge Graph took 0.02064061164855957s
Interlinking | Calculation of Degree of Connection for PREJUST4WOMEN Knowledge Graph took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for PREJUST4WOMEN Knowledge Graph took 0.0009832382202148438s
Interlinking | Calculation of Clustering coefficient for PREJUST4WOMEN Knowledge Graph took 6.127357482910156e-05s
Believability | Calculation of trust value for PREJUST4WOMEN Knowledge Graph took 1.2874603271484375e-05s
INFO | --- Analysis for PREJUST4WOMAN_PROJECT took 7.194628000259399s
Availability | SPARQL endpoint availability check for PreLex took 6.350744724273682s
Availability | VoID file availability check for PreLex took 0.0007417201995849609s
Completeness | Calculation of interlinking completeness for PreLex took 0.2744719982147217s
Reputation | Calculation of the PageRank for PreLex took 0.020257949829101562s
Interlinking | Calculation of Degree of Connection for PreLex took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PreLex took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for PreLex took 6.771087646484375e-05s
Believability | Calculation of trust value for PreLex took 1.239776611328125e-05s
INFO | --- Analysis for prelex took 18.992117881774902s
Availability | SPARQL endpoint availability check for Prelinger Archives took 2.9932711124420166s
Availability | VoID file availability check for Prelinger Archives took 0.0006375312805175781s
Completeness | Calculation of interlinking completeness for Prelinger Archives took 0.27635908126831055s
Reputation | Calculation of the PageRank for Prelinger Archives took 0.0202486515045166s
Interlinking | Calculation of Degree of Connection for Prelinger Archives took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Prelinger Archives took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Prelinger Archives took 2.9802322387695312e-05s
Believability | Calculation of trust value for Prelinger Archives took 9.775161743164062e-06s
INFO | --- Analysis for prelinger_archives took 19.94727921485901s
Availability | SPARQL endpoint availability check for PreMOn took 1.6991851329803467s
Availability | VoID file availability check for PreMOn took 0.0005424022674560547s
Extra | Recovery of all triples for PreMOn took 3.659186363220215s
Performance | Total latancy measurement for PreMOn took 0.6361978054046631s
Amount of data | Number of triples check for PreMOn took 0.27262234687805176s
Interoperability | New terms check for PreMOn took 1.9108569622039795s
Versatility | Languages check for PreMOn took 59.142247438430786s
Interpretability | Number of blank nodes check for PreMOn took 0.15141963958740234s
Security | Check HTTPS for PreMOn took 0.0724039077758789s
Interpretability | RDF structures check for PreMOn took 0.3635227680206299s
Versatility | Serialization formats check for PreMOn took 0.3608577251434326s
Availability | RDF dump link check for PreMOn took 0.1560649871826172s
License | MR license check for PreMOn took 0.3649752140045166s
License | HR license check for PreMOn took 0.9049422740936279s
Amount of data | Number of property check for PreMOn took 0.14721083641052246s
Understandability | Number of label check for PreMOn took 1.0500798225402832s
Understandability | URI regex check for PreMOn took 0.33283352851867676s
Understandability | Vocabs check for PreMOn took 0.2561502456665039s
Verifiability | Authors check for PreMOn took 0.1689000129699707s
Verifiability | Publishers check for PreMOn took 0.23640227317810059s
Performance | Throughput check for PreMOn took 10.669918298721313s
Amount of data | Check the number of entities for PreMOn took 7.343292236328125e-05s
Verifiability | Contribs. check for PreMOn took 0.15518927574157715s
Interlinking | sameAs chians check for PreMOn took 0.15135455131530762s
Interlinking | skos check for PreMOn took 0.2535722255706787s
Interlinking | skos check for PreMOn took 0.12145853042602539s
Timeliness | dataset update frequency check for PreMOn took 0.15171456336975098s
Currency | Creation date check for PreMOn took 0.3403294086456299s
Currency | Modification date check for PreMOn took 0.3395118713378906s
Rep.Conc. | URIs length for PreMOn took 3.6994705200195312s
Interoperability | New vocabularies check for PreMOn took 5.245208740234375e-06s
Consistency | Deprecated classes/propertiers check for PreMOn took 0.6841583251953125s
Accuracy | Check Functional Property for PreMOn took 0.682558536529541s
Accuracy | Check Inverse Functional Property for PreMOn took 0.37763428688049316s
Accuracy | Check Empty annotation labels for PreMOn took 2.152611255645752s
Accuracy | Check White space in annotation for PreMOn took 0.08082222938537598s
Accuracy | Check Datatype consistency for PreMOn took 0.08257293701171875s
Consistency | Disjoint class check for PreMOn took 0.1440749168395996s
Consistency | Check Misplaced properties for PreMOn took 1.878448247909546s
Consistency | Misplaced classes for PreMOn took 0.41031980514526367s
Consistency | Check Ontology hijacking for PreMOn took 2.5213778018951416s
Consistency | Check Invalid usage of undefined classes for PreMOn took 1.2438294887542725s
Consistency | Check Invalid usage of undefined properties for PreMOn took 2.9160268306732178s
Conciseness | Check Extensional conciseness for PreMOn took 0.08743047714233398s
Conciseness | Check Intensional conciseness for PreMOn took 0.17227864265441895s
Security | Sign check for PreMOn took 0.15705561637878418s
Availability | Check URIs Dereferenciability for PreMOn took 1121.7612826824188s
Completeness | Calculation of interlinking completeness for PreMOn took 0.39627647399902344s
Reputation | Calculation of the PageRank for PreMOn took 0.021373748779296875s
Interlinking | Calculation of Degree of Connection for PreMOn took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for PreMOn took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for PreMOn took 6.198883056640625e-05s
Interoperability | Check the re-using of existing vocabs for PreMOn took 1.1920928955078125e-06s
Believability | Calculation of trust value for PreMOn took 1.239776611328125e-05s
INFO | --- Analysis for premon took 1247.3848536014557s
Availability | SPARQL endpoint availability check for Previsible took 7.200241088867188e-05s
Availability | VoID file availability check for Previsible took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for Previsible took 0.2574319839477539s
Reputation | Calculation of the PageRank for Previsible took 0.02063751220703125s
Interlinking | Calculation of Degree of Connection for Previsible took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Previsible took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Previsible took 1.1205673217773438e-05s
Believability | Calculation of trust value for Previsible took 1.049041748046875e-05s
INFO | --- Analysis for Previsible took 2.420299768447876s
Availability | SPARQL endpoint availability check for Princeton Library FindingAids took 4.315376281738281e-05s
Availability | VoID file availability check for Princeton Library FindingAids took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for Princeton Library FindingAids took 0.25842738151550293s
Reputation | Calculation of the PageRank for Princeton Library FindingAids took 0.02036595344543457s
Interlinking | Calculation of Degree of Connection for Princeton Library FindingAids took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Princeton Library FindingAids took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Princeton Library FindingAids took 5.817413330078125e-05s
Believability | Calculation of trust value for Princeton Library FindingAids took 5.4836273193359375e-06s
INFO | --- Analysis for princeton-library-findingaids took 3.9798736572265625s
Availability | SPARQL endpoint availability check for PrinParLat in LiLa took 0.5477769374847412s
Availability | VoID file availability check for PrinParLat in LiLa took 0.0003662109375s
Completeness | Calculation of interlinking completeness for PrinParLat in LiLa took 0.2668623924255371s
Reputation | Calculation of the PageRank for PrinParLat in LiLa took 0.020298480987548828s
Interlinking | Calculation of Degree of Connection for PrinParLat in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PrinParLat in LiLa took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for PrinParLat in LiLa took 3.5762786865234375e-05s
Believability | Calculation of trust value for PrinParLat in LiLa took 5.245208740234375e-06s
INFO | --- Analysis for PrinParLat took 4.252749919891357s
Availability | SPARQL endpoint availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.26933741569519043s
Availability | VoID file availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.00038504600524902344s
Completeness | Calculation of interlinking completeness for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.266859769821167s
Reputation | Calculation of the PageRank for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.020208358764648438s
Interlinking | Calculation of Degree of Connection for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 8.392333984375e-05s
Believability | Calculation of trust value for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 6.67572021484375e-06s
INFO | --- Analysis for printed-book-auction-catalogues took 2.9822418689727783s
Availability | SPARQL endpoint availability check for Prior Panel took 4.4345855712890625e-05s
Availability | VoID file availability check for Prior Panel took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for Prior Panel took 0.2712376117706299s
Reputation | Calculation of the PageRank for Prior Panel took 0.02150249481201172s
Interlinking | Calculation of Degree of Connection for Prior Panel took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Prior Panel took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Prior Panel took 3.5762786865234375e-05s
Believability | Calculation of trust value for Prior Panel took 1.0728836059570312e-05s
INFO | --- Analysis for Prior_Panel took 2.477588415145874s
Availability | SPARQL endpoint availability check for ProductDB took 0.7073910236358643s
Availability | VoID file availability check for ProductDB took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for ProductDB took 0.2721679210662842s
Reputation | Calculation of the PageRank for ProductDB took 0.020362138748168945s
Interlinking | Calculation of Degree of Connection for ProductDB took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ProductDB took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for ProductDB took 7.462501525878906e-05s
Believability | Calculation of trust value for ProductDB took 9.775161743164062e-06s
INFO | --- Analysis for productdb took 3.7261087894439697s
Availability | SPARQL endpoint availability check for Product Types Ontology took 8.654594421386719e-05s
Availability | VoID file availability check for Product Types Ontology took 0.0005431175231933594s
Completeness | Calculation of interlinking completeness for Product Types Ontology took 0.2660541534423828s
Reputation | Calculation of the PageRank for Product Types Ontology took 0.0215911865234375s
Interlinking | Calculation of Degree of Connection for Product Types Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Product Types Ontology took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Product Types Ontology took 8.106231689453125e-05s
Believability | Calculation of trust value for Product Types Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for productontology took 3.3864738941192627s
Availability | SPARQL endpoint availability check for Prospects and Trends (GNOSS) took 4.1961669921875e-05s
Availability | VoID file availability check for Prospects and Trends (GNOSS) took 0.0006632804870605469s
Completeness | Calculation of interlinking completeness for Prospects and Trends (GNOSS) took 0.2753264904022217s
Reputation | Calculation of the PageRank for Prospects and Trends (GNOSS) took 0.0226290225982666s
Interlinking | Calculation of Degree of Connection for Prospects and Trends (GNOSS) took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Prospects and Trends (GNOSS) took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Prospects and Trends (GNOSS) took 0.00010633468627929688s
Believability | Calculation of trust value for Prospects and Trends (GNOSS) took 1.049041748046875e-05s
INFO | --- Analysis for prospects-and-trends-gnoss took 8.118264198303223s
Availability | SPARQL endpoint availability check for provenanceweb took 0.052555084228515625s
Availability | VoID file availability check for provenanceweb took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for provenanceweb took 0.26470303535461426s
Reputation | Calculation of the PageRank for provenanceweb took 0.02309107780456543s
Interlinking | Calculation of Degree of Connection for provenanceweb took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for provenanceweb took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for provenanceweb took 7.319450378417969e-05s
Believability | Calculation of trust value for provenanceweb took 1.0967254638671875e-05s
INFO | --- Analysis for provenanceweb took 51.5296425819397s
Availability | SPARQL endpoint availability check for Proyecto Apadrina,  Marketing Punto de Venta took 4.315376281738281e-05s
Availability | VoID file availability check for Proyecto Apadrina,  Marketing Punto de Venta took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for Proyecto Apadrina,  Marketing Punto de Venta took 0.26489996910095215s
Reputation | Calculation of the PageRank for Proyecto Apadrina,  Marketing Punto de Venta took 0.022086620330810547s
Interlinking | Calculation of Degree of Connection for Proyecto Apadrina,  Marketing Punto de Venta took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Proyecto Apadrina,  Marketing Punto de Venta took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Proyecto Apadrina,  Marketing Punto de Venta took 9.655952453613281e-05s
Believability | Calculation of trust value for Proyecto Apadrina,  Marketing Punto de Venta took 1.2636184692382812e-05s
INFO | --- Analysis for proyectoapadrina took 7.1426472663879395s
Availability | SPARQL endpoint availability check for Product Scheme Classifications Catalogue took 25.256118774414062s
Availability | VoID file availability check for Product Scheme Classifications Catalogue took 0.0007741451263427734s
Completeness | Calculation of interlinking completeness for Product Scheme Classifications Catalogue took 0.2668616771697998s
Reputation | Calculation of the PageRank for Product Scheme Classifications Catalogue took 0.02040266990661621s
Interlinking | Calculation of Degree of Connection for Product Scheme Classifications Catalogue took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Product Scheme Classifications Catalogue took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Product Scheme Classifications Catalogue took 3.337860107421875e-05s
Believability | Calculation of trust value for Product Scheme Classifications Catalogue took 1.0728836059570312e-05s
INFO | --- Analysis for pscs-catalogue took 123.63717794418335s
Availability | SPARQL endpoint availability check for Polythematic Structured Subject Heading System took 5.888938903808594e-05s
Availability | VoID file availability check for Polythematic Structured Subject Heading System took 0.0003802776336669922s
Completeness | Calculation of interlinking completeness for Polythematic Structured Subject Heading System took 0.263258695602417s
Reputation | Calculation of the PageRank for Polythematic Structured Subject Heading System took 0.020620107650756836s
Interlinking | Calculation of Degree of Connection for Polythematic Structured Subject Heading System took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Polythematic Structured Subject Heading System took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Polythematic Structured Subject Heading System took 7.510185241699219e-05s
Believability | Calculation of trust value for Polythematic Structured Subject Heading System took 7.62939453125e-06s
INFO | --- Analysis for psh-subject-headings took 2.8762943744659424s
Availability | SPARQL endpoint availability check for Depression took 0.4852104187011719s
Availability | VoID file availability check for Depression took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for Depression took 0.3081657886505127s
Reputation | Calculation of the PageRank for Depression took 0.021340131759643555s
Interlinking | Calculation of Degree of Connection for Depression took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Depression took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Depression took 2.9325485229492188e-05s
Believability | Calculation of trust value for Depression took 7.3909759521484375e-06s
INFO | --- Analysis for Psychology took 3.043119192123413s
Availability | SPARQL endpoint availability check for PubChem RDF took 8.559226989746094e-05s
Availability | VoID file availability check for PubChem RDF took 0.0006639957427978516s
Completeness | Calculation of interlinking completeness for PubChem RDF took 0.2709789276123047s
Reputation | Calculation of the PageRank for PubChem RDF took 0.0203857421875s
Interlinking | Calculation of Degree of Connection for PubChem RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for PubChem RDF took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for PubChem RDF took 3.838539123535156e-05s
Believability | Calculation of trust value for PubChem RDF took 1.2159347534179688e-05s
INFO | --- Analysis for PubChem_RDF took 4.917914628982544s
Availability | SPARQL endpoint availability check for Public Spending in Greece took 60.05122137069702s
Availability | VoID file availability check for Public Spending in Greece took 0.0006842613220214844s
Completeness | Calculation of interlinking completeness for Public Spending in Greece took 0.27439045906066895s
Reputation | Calculation of the PageRank for Public Spending in Greece took 0.020549535751342773s
Interlinking | Calculation of Degree of Connection for Public Spending in Greece took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Public Spending in Greece took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Public Spending in Greece took 7.843971252441406e-05s
Believability | Calculation of trust value for Public Spending in Greece took 1.3113021850585938e-05s
INFO | --- Analysis for public-spending-in-greece took 146.91112565994263s
Availability | SPARQL endpoint availability check for Publications Office Authority tables took 0.1783897876739502s
Availability | VoID file availability check for Publications Office Authority tables took 0.0005586147308349609s
Extra | Recovery of all triples for Publications Office Authority tables took 177.50847268104553s
Performance | Total latancy measurement for Publications Office Authority tables took 0.5480351448059082s
Amount of data | Number of triples check for Publications Office Authority tables took 85.31101131439209s
Interoperability | New terms check for Publications Office Authority tables took 64.34130263328552s
Versatility | Languages check for Publications Office Authority tables took 300.0488591194153s
Interpretability | Number of blank nodes check for Publications Office Authority tables took 18.30902671813965s
Security | Check HTTPS for Publications Office Authority tables took 0.3296966552734375s
Interpretability | RDF structures check for Publications Office Authority tables took 0.5293135643005371s
Versatility | Serialization formats check for Publications Office Authority tables took 8.941012859344482s
Availability | RDF dump link check for Publications Office Authority tables took 0.21372151374816895s
License | MR license check for Publications Office Authority tables took 0.2224743366241455s
License | HR license check for Publications Office Authority tables took 300.1046853065491s
Amount of data | Number of property check for Publications Office Authority tables took 0.18717074394226074s
Understandability | Number of label check for Publications Office Authority tables took 2.1304242610931396s
Understandability | URI regex check for Publications Office Authority tables took 0.4522843360900879s
Understandability | Vocabs check for Publications Office Authority tables took 0.11463236808776855s
Verifiability | Authors check for Publications Office Authority tables took 0.13709712028503418s
Verifiability | Publishers check for Publications Office Authority tables took 0.19095611572265625s
Performance | Throughput check for Publications Office Authority tables took 10.625873565673828s
Amount of data | Check the number of entities for Publications Office Authority tables took 7.653236389160156e-05s
Verifiability | Contribs. check for Publications Office Authority tables took 0.09955644607543945s
Interlinking | sameAs chians check for Publications Office Authority tables took 7.5472540855407715s
Interlinking | skos check for Publications Office Authority tables took 0.16908764839172363s
Interlinking | skos check for Publications Office Authority tables took 0.14480805397033691s
Timeliness | dataset update frequency check for Publications Office Authority tables took 0.27541589736938477s
Currency | Creation date check for Publications Office Authority tables took 0.31603050231933594s
Currency | Modification date check for Publications Office Authority tables took 0.15701961517333984s
Rep.Conc. | URIs length for Publications Office Authority tables took 419.30642461776733s
Interoperability | New vocabularies check for Publications Office Authority tables took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for Publications Office Authority tables took 0.16904091835021973s
Accuracy | Check Functional Property for Publications Office Authority tables took 0.192155122756958s
Accuracy | Check Inverse Functional Property for Publications Office Authority tables took 0.17070269584655762s
Accuracy | Check Empty annotation labels for Publications Office Authority tables took 60.52742552757263s
Accuracy | Check White space in annotation for Publications Office Authority tables took 3.063652992248535s
Accuracy | Check Datatype consistency for Publications Office Authority tables took 2.618044137954712s
Consistency | Disjoint class check for Publications Office Authority tables took 0.19997549057006836s
Consistency | Check Misplaced properties for Publications Office Authority tables took 300.4695510864258s
Consistency | Misplaced classes for Publications Office Authority tables took 8.350104808807373s
Consistency | Check Ontology hijacking for Publications Office Authority tables took 50.89731049537659s
Consistency | Check Invalid usage of undefined classes for Publications Office Authority tables took 1.698016881942749s
Consistency | Check Invalid usage of undefined properties for Publications Office Authority tables took 301.38041710853577s
Conciseness | Check Extensional conciseness for Publications Office Authority tables took 2.9903740882873535s
Conciseness | Check Intensional conciseness for Publications Office Authority tables took 0.6006479263305664s
Security | Sign check for Publications Office Authority tables took 0.4504880905151367s
Availability | Check URIs Dereferenciability for Publications Office Authority tables took 10.92596173286438s
Completeness | Calculation of interlinking completeness for Publications Office Authority tables took 0.6584558486938477s
Reputation | Calculation of the PageRank for Publications Office Authority tables took 0.02225494384765625s
Interlinking | Calculation of Degree of Connection for Publications Office Authority tables took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for Publications Office Authority tables took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Publications Office Authority tables took 4.863739013671875e-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 9.298324584960938e-06s
INFO | --- Analysis for publications_office_authority_tables took 14114.042633533478s
Availability | SPARQL endpoint availability check for QBOAirbase took 8.559226989746094e-05s
Availability | VoID file availability check for QBOAirbase took 0.0007572174072265625s
Completeness | Calculation of interlinking completeness for QBOAirbase took 0.26853013038635254s
Reputation | Calculation of the PageRank for QBOAirbase took 0.02041029930114746s
Interlinking | Calculation of Degree of Connection for QBOAirbase took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for QBOAirbase took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for QBOAirbase took 7.987022399902344e-05s
Believability | Calculation of trust value for QBOAirbase took 1.1682510375976562e-05s
INFO | --- Analysis for qboairbase took 136.23348784446716s
Availability | SPARQL endpoint availability check for Qualité de l'air took 9.012222290039062e-05s
Availability | VoID file availability check for Qualité de l'air took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for Qualité de l'air took 0.2752108573913574s
Reputation | Calculation of the PageRank for Qualité de l'air took 0.020925283432006836s
Interlinking | Calculation of Degree of Connection for Qualité de l'air took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Qualité de l'air took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air took 2.8371810913085938e-05s
Believability | Calculation of trust value for Qualité de l'air took 6.67572021484375e-06s
INFO | --- Analysis for Qualité_de_l'air took 2.8060929775238037s
Availability | SPARQL endpoint availability check for Qualité de l'air dans le monde took 4.363059997558594e-05s
Availability | VoID file availability check for Qualité de l'air dans le monde took 0.000640869140625s
Completeness | Calculation of interlinking completeness for Qualité de l'air dans le monde took 0.2740139961242676s
Reputation | Calculation of the PageRank for Qualité de l'air dans le monde took 0.023089170455932617s
Interlinking | Calculation of Degree of Connection for Qualité de l'air dans le monde took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Qualité de l'air dans le monde took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air dans le monde took 3.504753112792969e-05s
Believability | Calculation of trust value for Qualité de l'air dans le monde took 1.0728836059570312e-05s
INFO | --- Analysis for Qualité_de_l'air_dans_le_monde took 45.21387076377869s
Availability | SPARQL endpoint availability check for Querolus in LiLa took 0.5854418277740479s
Availability | VoID file availability check for Querolus in LiLa took 0.0005931854248046875s
Completeness | Calculation of interlinking completeness for Querolus in LiLa took 0.2834787368774414s
Reputation | Calculation of the PageRank for Querolus in LiLa took 0.02019047737121582s
Interlinking | Calculation of Degree of Connection for Querolus in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Querolus in LiLa took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Querolus in LiLa took 3.647804260253906e-05s
Believability | Calculation of trust value for Querolus in LiLa took 1.049041748046875e-05s
INFO | --- Analysis for Querolus took 4.112087965011597s
Availability | SPARQL endpoint availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.40343809127807617s
Availability | VoID file availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0005784034729003906s
Extra | Recovery of all triples for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 70.24735403060913s
Performance | Total latancy measurement for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.6638791561126709s
Amount of data | Number of triples check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 3.3560523986816406s
Interoperability | New terms check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.7575385570526123s
Versatility | Languages check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 9.68175983428955s
Interpretability | Number of blank nodes check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.3904786109924316s
Interpretability | RDF structures check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.20601820945739746s
Versatility | Serialization formats check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13298392295837402s
Availability | RDF dump link check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1310100555419922s
License | MR license check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.12947416305541992s
License | HR license check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.19711041450500488s
Amount of data | Number of property check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13561344146728516s
Understandability | Number of label check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13112139701843262s
Understandability | URI regex check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.25900840759277344s
Understandability | Vocabs check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.12981343269348145s
Verifiability | Authors check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13007068634033203s
Verifiability | Publishers check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13009262084960938s
Performance | Throughput check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 10.529186725616455s
Amount of data | Check the number of entities for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 7.796287536621094e-05s
Verifiability | Contribs. check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14392423629760742s
Interlinking | sameAs chians check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13081812858581543s
Interlinking | skos check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.12926840782165527s
Interlinking | skos check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13224506378173828s
Timeliness | dataset update frequency check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13032197952270508s
Currency | Creation date check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.27022409439086914s
Currency | Modification date check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.2590603828430176s
Rep.Conc. | URIs length for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 23.998015880584717s
Interoperability | New vocabularies check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.130720853805542s
Accuracy | Check Functional Property for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13993310928344727s
Accuracy | Check Inverse Functional Property for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13010859489440918s
Accuracy | Check Empty annotation labels for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13283085823059082s
Accuracy | Check White space in annotation for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 3.695487976074219e-05s
Consistency | Disjoint class check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13285112380981445s
Consistency | Check Misplaced properties for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 5.546446084976196s
Consistency | Check Ontology hijacking for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 9.54428768157959s
Consistency | Check Invalid usage of undefined properties for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 6.561074256896973s
Conciseness | Check Extensional conciseness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.00017952919006347656s
Security | Sign check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.12897515296936035s
Completeness | Calculation of interlinking completeness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.3422389030456543s
Reputation | Calculation of the PageRank for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.020801544189453125s
Interlinking | Calculation of Degree of Connection for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 5.078315734863281e-05s
Interoperability | Check the re-using of existing vocabs for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.430511474609375e-06s
Believability | Calculation of trust value for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.239776611328125e-05s
INFO | --- Analysis for racai-legalnero took 181.24818325042725s
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.0005669593811035156s
Completeness | Calculation of interlinking completeness for Romanian CoRoLa Word Embeddings took 0.27573394775390625s
Reputation | Calculation of the PageRank for Romanian CoRoLa Word Embeddings took 0.020148754119873047s
Interlinking | Calculation of Degree of Connection for Romanian CoRoLa Word Embeddings took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Romanian CoRoLa Word Embeddings took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Romanian CoRoLa Word Embeddings took 2.8133392333984375e-05s
Believability | Calculation of trust value for Romanian CoRoLa Word Embeddings took 1.239776611328125e-05s
INFO | --- Analysis for racai-llod-corola-we took 2.9995927810668945s
Availability | SPARQL endpoint availability check for PARSEME-Ro corpus took 0.1357707977294922s
Availability | VoID file availability check for PARSEME-Ro corpus took 0.0005288124084472656s
Extra | Recovery of all triples for PARSEME-Ro corpus took 70.60661220550537s
Performance | Total latancy measurement for PARSEME-Ro corpus took 0.646970272064209s
Amount of data | Number of triples check for PARSEME-Ro corpus took 6.8332359790802s
Interoperability | New terms check for PARSEME-Ro corpus took 2.07073974609375s
Versatility | Languages check for PARSEME-Ro corpus took 18.34809184074402s
Interpretability | Number of blank nodes check for PARSEME-Ro corpus took 5.368052959442139s
Interpretability | RDF structures check for PARSEME-Ro corpus took 0.12952899932861328s
Versatility | Serialization formats check for PARSEME-Ro corpus took 0.14371061325073242s
Availability | RDF dump link check for PARSEME-Ro corpus took 0.12737011909484863s
License | MR license check for PARSEME-Ro corpus took 0.13068318367004395s
License | HR license check for PARSEME-Ro corpus took 10.137576580047607s
Amount of data | Number of property check for PARSEME-Ro corpus took 0.13492846488952637s
Understandability | Number of label check for PARSEME-Ro corpus took 0.18454766273498535s
Understandability | URI regex check for PARSEME-Ro corpus took 0.2633185386657715s
Understandability | Vocabs check for PARSEME-Ro corpus took 0.13750267028808594s
Verifiability | Authors check for PARSEME-Ro corpus took 0.1309514045715332s
Verifiability | Publishers check for PARSEME-Ro corpus took 0.13059115409851074s
Performance | Throughput check for PARSEME-Ro corpus took 10.720838069915771s
Amount of data | Check the number of entities for PARSEME-Ro corpus took 7.295608520507812e-05s
Verifiability | Contribs. check for PARSEME-Ro corpus took 0.13089394569396973s
Interlinking | sameAs chians check for PARSEME-Ro corpus took 0.12938499450683594s
Interlinking | skos check for PARSEME-Ro corpus took 0.13521075248718262s
Interlinking | skos check for PARSEME-Ro corpus took 0.12911057472229004s
Timeliness | dataset update frequency check for PARSEME-Ro corpus took 0.12990570068359375s
Currency | Creation date check for PARSEME-Ro corpus took 0.25924110412597656s
Currency | Modification date check for PARSEME-Ro corpus took 0.27845239639282227s
Rep.Conc. | URIs length for PARSEME-Ro corpus took 74.72893023490906s
Interoperability | New vocabularies check for PARSEME-Ro corpus took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for PARSEME-Ro corpus took 0.1315784454345703s
Accuracy | Check Functional Property for PARSEME-Ro corpus took 0.13077664375305176s
Accuracy | Check Inverse Functional Property for PARSEME-Ro corpus took 0.12942886352539062s
Accuracy | Check Empty annotation labels for PARSEME-Ro corpus took 4.099213600158691s
Accuracy | Check White space in annotation for PARSEME-Ro corpus took 0.2296154499053955s
Consistency | Disjoint class check for PARSEME-Ro corpus took 0.15784859657287598s
Consistency | Check Misplaced properties for PARSEME-Ro corpus took 11.022325277328491s
Consistency | Check Ontology hijacking for PARSEME-Ro corpus took 35.29742646217346s
Consistency | Check Invalid usage of undefined properties for PARSEME-Ro corpus took 12.906244993209839s
Conciseness | Check Extensional conciseness for PARSEME-Ro corpus took 0.0001685619354248047s
Security | Sign check for PARSEME-Ro corpus took 0.1344754695892334s
Completeness | Calculation of interlinking completeness for PARSEME-Ro corpus took 0.4043104648590088s
Reputation | Calculation of the PageRank for PARSEME-Ro corpus took 0.020568370819091797s
Interlinking | Calculation of Degree of Connection for PARSEME-Ro corpus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for PARSEME-Ro corpus took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for PARSEME-Ro corpus took 3.790855407714844e-05s
Interoperability | Check the re-using of existing vocabs for PARSEME-Ro corpus took 1.6689300537109375e-06s
Believability | Calculation of trust value for PARSEME-Ro corpus took 7.867813110351562e-06s
INFO | --- Analysis for racai-llod-parseme-ro took 304.34488105773926s
Availability | SPARQL endpoint availability check for RoLEX took 0.13802838325500488s
Availability | VoID file availability check for RoLEX took 0.0005776882171630859s
Extra | Recovery of all triples for RoLEX took 68.26616597175598s
Performance | Total latancy measurement for RoLEX took 0.661144495010376s
Amount of data | Number of triples check for RoLEX took 1.6187973022460938s
Interoperability | New terms check for RoLEX took 1.6331462860107422s
Versatility | Languages check for RoLEX took 4.16875433921814s
Interpretability | Number of blank nodes check for RoLEX took 1.0427451133728027s
Interpretability | RDF structures check for RoLEX took 0.13003182411193848s
Versatility | Serialization formats check for RoLEX took 0.1300652027130127s
Availability | RDF dump link check for RoLEX took 0.1351776123046875s
License | MR license check for RoLEX took 0.12981915473937988s
License | HR license check for RoLEX took 0.13551545143127441s
Amount of data | Number of property check for RoLEX took 0.12943339347839355s
Understandability | Number of label check for RoLEX took 0.13747191429138184s
Understandability | URI regex check for RoLEX took 0.2573239803314209s
Understandability | Vocabs check for RoLEX took 0.13019776344299316s
Verifiability | Authors check for RoLEX took 0.12991571426391602s
Verifiability | Publishers check for RoLEX took 0.13044524192810059s
Performance | Throughput check for RoLEX took 11.581630945205688s
Amount of data | Check the number of entities for RoLEX took 7.033348083496094e-05s
Verifiability | Contribs. check for RoLEX took 0.1290569305419922s
Interlinking | sameAs chians check for RoLEX took 0.13308477401733398s
Interlinking | skos check for RoLEX took 0.12947750091552734s
Interlinking | skos check for RoLEX took 0.12914156913757324s
Timeliness | dataset update frequency check for RoLEX took 0.13236236572265625s
Currency | Creation date check for RoLEX took 0.26173901557922363s
Currency | Modification date check for RoLEX took 0.25982093811035156s
Rep.Conc. | URIs length for RoLEX took 54.93232250213623s
Interoperability | New vocabularies check for RoLEX took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for RoLEX took 0.13274645805358887s
Accuracy | Check Functional Property for RoLEX took 0.1484992504119873s
Accuracy | Check Inverse Functional Property for RoLEX took 0.1428532600402832s
Consistency | Disjoint class check for RoLEX took 0.137481689453125s
Consistency | Check Misplaced properties for RoLEX took 3.7681727409362793s
Consistency | Check Ontology hijacking for RoLEX took 16.850150108337402s
Consistency | Check Invalid usage of undefined properties for RoLEX took 3.890589952468872s
Conciseness | Check Extensional conciseness for RoLEX took 0.00014662742614746094s
Security | Sign check for RoLEX took 0.12722277641296387s
Completeness | Calculation of interlinking completeness for RoLEX took 0.3014051914215088s
Reputation | Calculation of the PageRank for RoLEX took 0.02060079574584961s
Interlinking | Calculation of Degree of Connection for RoLEX took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for RoLEX took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for RoLEX took 3.0994415283203125e-05s
Interoperability | Check the re-using of existing vocabs for RoLEX took 1.6689300537109375e-06s
Believability | Calculation of trust value for RoLEX took 1.0251998901367188e-05s
INFO | --- Analysis for racai-llod-rolex took 197.53442454338074s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 4.458427429199219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0002827644348144531s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.26667308807373047s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.020374536514282227s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 3.0994415283203125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 1.1444091796875e-05s
INFO | --- Analysis for racai-llod-romanian-treebank took 2.7012741565704346s
Availability | SPARQL endpoint availability check for JSON Romanian Wordnet took 4.3392181396484375e-05s
Availability | VoID file availability check for JSON Romanian Wordnet took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for JSON Romanian Wordnet took 0.2697765827178955s
Reputation | Calculation of the PageRank for JSON Romanian Wordnet took 0.020725488662719727s
Interlinking | Calculation of Degree of Connection for JSON Romanian Wordnet took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for JSON Romanian Wordnet took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for JSON Romanian Wordnet took 3.170967102050781e-05s
Believability | Calculation of trust value for JSON Romanian Wordnet took 9.5367431640625e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-json took 2.571363925933838s
Availability | SPARQL endpoint availability check for LMF Romanian Wordnet took 8.273124694824219e-05s
Availability | VoID file availability check for LMF Romanian Wordnet took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for LMF Romanian Wordnet took 0.27449965476989746s
Reputation | Calculation of the PageRank for LMF Romanian Wordnet took 0.021944522857666016s
Interlinking | Calculation of Degree of Connection for LMF Romanian Wordnet took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LMF Romanian Wordnet took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for LMF Romanian Wordnet took 3.0517578125e-05s
Believability | Calculation of trust value for LMF Romanian Wordnet took 1.049041748046875e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-lmf took 2.6251392364501953s
Availability | SPARQL endpoint availability check for Turtle-RDF Romanian Wordnet took 8.606910705566406e-05s
Availability | VoID file availability check for Turtle-RDF Romanian Wordnet took 0.000644683837890625s
Completeness | Calculation of interlinking completeness for Turtle-RDF Romanian Wordnet took 0.2689480781555176s
Reputation | Calculation of the PageRank for Turtle-RDF Romanian Wordnet took 0.020764827728271484s
Interlinking | Calculation of Degree of Connection for Turtle-RDF Romanian Wordnet took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Turtle-RDF Romanian Wordnet took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Turtle-RDF Romanian Wordnet took 3.123283386230469e-05s
Believability | Calculation of trust value for Turtle-RDF Romanian Wordnet took 1.0251998901367188e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-ttl took 2.6863722801208496s
Availability | SPARQL endpoint availability check for ROBIN Technical Acquisition Speech Corpus took 0.13441085815429688s
Availability | VoID file availability check for ROBIN Technical Acquisition Speech Corpus took 0.0005228519439697266s
Extra | Recovery of all triples for ROBIN Technical Acquisition Speech Corpus took 23.382684469223022s
Performance | Total latancy measurement for ROBIN Technical Acquisition Speech Corpus took 0.6542878150939941s
Amount of data | Number of triples check for ROBIN Technical Acquisition Speech Corpus took 0.3126811981201172s
Interoperability | New terms check for ROBIN Technical Acquisition Speech Corpus took 1.4382140636444092s
Versatility | Languages check for ROBIN Technical Acquisition Speech Corpus took 0.5781440734863281s
Interpretability | Number of blank nodes check for ROBIN Technical Acquisition Speech Corpus took 0.2350473403930664s
Interpretability | RDF structures check for ROBIN Technical Acquisition Speech Corpus took 0.12941431999206543s
Versatility | Serialization formats check for ROBIN Technical Acquisition Speech Corpus took 0.13148760795593262s
Availability | RDF dump link check for ROBIN Technical Acquisition Speech Corpus took 0.1748185157775879s
License | MR license check for ROBIN Technical Acquisition Speech Corpus took 0.1272284984588623s
License | HR license check for ROBIN Technical Acquisition Speech Corpus took 0.13190984725952148s
Amount of data | Number of property check for ROBIN Technical Acquisition Speech Corpus took 0.14145374298095703s
Understandability | Number of label check for ROBIN Technical Acquisition Speech Corpus took 0.13268589973449707s
Understandability | URI regex check for ROBIN Technical Acquisition Speech Corpus took 0.2571415901184082s
Understandability | Vocabs check for ROBIN Technical Acquisition Speech Corpus took 0.1306767463684082s
Verifiability | Authors check for ROBIN Technical Acquisition Speech Corpus took 0.1281740665435791s
Verifiability | Publishers check for ROBIN Technical Acquisition Speech Corpus took 0.13236403465270996s
Performance | Throughput check for ROBIN Technical Acquisition Speech Corpus took 10.631928443908691s
Amount of data | Check the number of entities for ROBIN Technical Acquisition Speech Corpus took 0.00010943412780761719s
Verifiability | Contribs. check for ROBIN Technical Acquisition Speech Corpus took 0.13021230697631836s
Interlinking | sameAs chians check for ROBIN Technical Acquisition Speech Corpus took 0.12979602813720703s
Interlinking | skos check for ROBIN Technical Acquisition Speech Corpus took 0.131087064743042s
Interlinking | skos check for ROBIN Technical Acquisition Speech Corpus took 0.14145803451538086s
Timeliness | dataset update frequency check for ROBIN Technical Acquisition Speech Corpus took 0.13354086875915527s
Currency | Creation date check for ROBIN Technical Acquisition Speech Corpus took 0.26427125930786133s
Currency | Modification date check for ROBIN Technical Acquisition Speech Corpus took 0.2613949775695801s
Rep.Conc. | URIs length for ROBIN Technical Acquisition Speech Corpus took 2.9370639324188232s
Interoperability | New vocabularies check for ROBIN Technical Acquisition Speech Corpus took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for ROBIN Technical Acquisition Speech Corpus took 0.1405491828918457s
Accuracy | Check Functional Property for ROBIN Technical Acquisition Speech Corpus took 0.1365039348602295s
Accuracy | Check Inverse Functional Property for ROBIN Technical Acquisition Speech Corpus took 0.12667274475097656s
Accuracy | Check Empty annotation labels for ROBIN Technical Acquisition Speech Corpus took 0.39298486709594727s
Accuracy | Check White space in annotation for ROBIN Technical Acquisition Speech Corpus took 0.00955820083618164s
Accuracy | Check Datatype consistency for ROBIN Technical Acquisition Speech Corpus took 1.2196357250213623s
Consistency | Disjoint class check for ROBIN Technical Acquisition Speech Corpus took 0.12728428840637207s
Consistency | Check Misplaced properties for ROBIN Technical Acquisition Speech Corpus took 0.47888755798339844s
Consistency | Check Ontology hijacking for ROBIN Technical Acquisition Speech Corpus took 2.3702473640441895s
Consistency | Check Invalid usage of undefined classes for ROBIN Technical Acquisition Speech Corpus took 1.2718546390533447s
Consistency | Check Invalid usage of undefined properties for ROBIN Technical Acquisition Speech Corpus took 1.616065502166748s
Conciseness | Check Extensional conciseness for ROBIN Technical Acquisition Speech Corpus took 0.8236870765686035s
Security | Sign check for ROBIN Technical Acquisition Speech Corpus took 0.12820887565612793s
Availability | Check URIs Dereferenciability for ROBIN Technical Acquisition Speech Corpus took 3562.583805322647s
Completeness | Calculation of interlinking completeness for ROBIN Technical Acquisition Speech Corpus took 0.6258375644683838s
Reputation | Calculation of the PageRank for ROBIN Technical Acquisition Speech Corpus took 0.02155280113220215s
Interlinking | Calculation of Degree of Connection for ROBIN Technical Acquisition Speech Corpus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ROBIN Technical Acquisition Speech Corpus took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for ROBIN Technical Acquisition Speech Corpus took 4.220008850097656e-05s
Interoperability | Check the re-using of existing vocabs for ROBIN Technical Acquisition Speech Corpus took 1.9073486328125e-06s
Believability | Calculation of trust value for ROBIN Technical Acquisition Speech Corpus took 1.3113021850585938e-05s
INFO | --- Analysis for racai-llod-rtasc took 3631.269059419632s
Availability | SPARQL endpoint availability check for SiMoNERo - the Romanian medical treebank took 0.12878179550170898s
Availability | VoID file availability check for SiMoNERo - the Romanian medical treebank took 0.0006282329559326172s
Extra | Recovery of all triples for SiMoNERo - the Romanian medical treebank took 72.99438738822937s
Performance | Total latancy measurement for SiMoNERo - the Romanian medical treebank took 0.6597094535827637s
Amount of data | Number of triples check for SiMoNERo - the Romanian medical treebank took 1.0653185844421387s
Interoperability | New terms check for SiMoNERo - the Romanian medical treebank took 1.487912893295288s
Versatility | Languages check for SiMoNERo - the Romanian medical treebank took 2.4060847759246826s
Interpretability | Number of blank nodes check for SiMoNERo - the Romanian medical treebank took 0.8061008453369141s
Interpretability | RDF structures check for SiMoNERo - the Romanian medical treebank took 0.14797711372375488s
Versatility | Serialization formats check for SiMoNERo - the Romanian medical treebank took 0.13649964332580566s
Availability | RDF dump link check for SiMoNERo - the Romanian medical treebank took 0.12939000129699707s
License | MR license check for SiMoNERo - the Romanian medical treebank took 0.13235712051391602s
License | HR license check for SiMoNERo - the Romanian medical treebank took 4.773198843002319s
Amount of data | Number of property check for SiMoNERo - the Romanian medical treebank took 0.1298515796661377s
Understandability | Number of label check for SiMoNERo - the Romanian medical treebank took 0.1365666389465332s
Understandability | URI regex check for SiMoNERo - the Romanian medical treebank took 0.276503324508667s
Understandability | Vocabs check for SiMoNERo - the Romanian medical treebank took 0.12952971458435059s
Verifiability | Authors check for SiMoNERo - the Romanian medical treebank took 0.13177275657653809s
Verifiability | Publishers check for SiMoNERo - the Romanian medical treebank took 0.15830421447753906s
Performance | Throughput check for SiMoNERo - the Romanian medical treebank took 10.517905950546265s
Amount of data | Check the number of entities for SiMoNERo - the Romanian medical treebank took 0.0001366138458251953s
Verifiability | Contribs. check for SiMoNERo - the Romanian medical treebank took 0.1302318572998047s
Interlinking | sameAs chians check for SiMoNERo - the Romanian medical treebank took 0.13088274002075195s
Interlinking | skos check for SiMoNERo - the Romanian medical treebank took 0.14325237274169922s
Interlinking | skos check for SiMoNERo - the Romanian medical treebank took 0.1298847198486328s
Timeliness | dataset update frequency check for SiMoNERo - the Romanian medical treebank took 0.1308603286743164s
Currency | Creation date check for SiMoNERo - the Romanian medical treebank took 0.2600834369659424s
Currency | Modification date check for SiMoNERo - the Romanian medical treebank took 0.2683279514312744s
Rep.Conc. | URIs length for SiMoNERo - the Romanian medical treebank took 8.702011108398438s
Interoperability | New vocabularies check for SiMoNERo - the Romanian medical treebank took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for SiMoNERo - the Romanian medical treebank took 0.12848830223083496s
Accuracy | Check Functional Property for SiMoNERo - the Romanian medical treebank took 0.12999987602233887s
Accuracy | Check Inverse Functional Property for SiMoNERo - the Romanian medical treebank took 0.1341545581817627s
Accuracy | Check Empty annotation labels for SiMoNERo - the Romanian medical treebank took 0.6979873180389404s
Accuracy | Check White space in annotation for SiMoNERo - the Romanian medical treebank took 0.019379377365112305s
Consistency | Disjoint class check for SiMoNERo - the Romanian medical treebank took 0.12935137748718262s
Consistency | Check Misplaced properties for SiMoNERo - the Romanian medical treebank took 1.407247543334961s
Consistency | Check Ontology hijacking for SiMoNERo - the Romanian medical treebank took 6.831592798233032s
Consistency | Check Invalid usage of undefined properties for SiMoNERo - the Romanian medical treebank took 2.9163942337036133s
Conciseness | Check Extensional conciseness for SiMoNERo - the Romanian medical treebank took 0.0001437664031982422s
Security | Sign check for SiMoNERo - the Romanian medical treebank took 0.12847900390625s
Completeness | Calculation of interlinking completeness for SiMoNERo - the Romanian medical treebank took 0.27733564376831055s
Reputation | Calculation of the PageRank for SiMoNERo - the Romanian medical treebank took 0.020723342895507812s
Interlinking | Calculation of Degree of Connection for SiMoNERo - the Romanian medical treebank took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SiMoNERo - the Romanian medical treebank took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for SiMoNERo - the Romanian medical treebank took 3.218650817871094e-05s
Interoperability | Check the re-using of existing vocabs for SiMoNERo - the Romanian medical treebank took 1.6689300537109375e-06s
Believability | Calculation of trust value for SiMoNERo - the Romanian medical treebank took 5.245208740234375e-06s
INFO | --- Analysis for racai-llod-simonero took 134.2410433292389s
Availability | SPARQL endpoint availability check for Rådata nå! took 0.08001255989074707s
Availability | VoID file availability check for Rådata nå! took 0.00054931640625s
Completeness | Calculation of interlinking completeness for Rådata nå! took 0.2753424644470215s
Reputation | Calculation of the PageRank for Rådata nå! took 0.02150440216064453s
Interlinking | Calculation of Degree of Connection for Rådata nå! took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Rådata nå! took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Rådata nå! took 7.963180541992188e-05s
Believability | Calculation of trust value for Rådata nå! took 1.0251998901367188e-05s
INFO | --- Analysis for radatana took 4.186831474304199s
Availability | SPARQL endpoint availability check for "Rainis and Aspazija" Linked Digital Collection took 8.988380432128906e-05s
Availability | VoID file availability check for "Rainis and Aspazija" Linked Digital Collection took 0.0007669925689697266s
Completeness | Calculation of interlinking completeness for "Rainis and Aspazija" Linked Digital Collection took 0.2728133201599121s
Reputation | Calculation of the PageRank for "Rainis and Aspazija" Linked Digital Collection took 0.020763874053955078s
Interlinking | Calculation of Degree of Connection for "Rainis and Aspazija" Linked Digital Collection took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for "Rainis and Aspazija" Linked Digital Collection took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for "Rainis and Aspazija" Linked Digital Collection took 4.00543212890625e-05s
Believability | Calculation of trust value for "Rainis and Aspazija" Linked Digital Collection took 1.1444091796875e-05s
INFO | --- Analysis for rainis-and-aspazija-linked-digital-collection took 16.562561750411987s
Availability | SPARQL endpoint availability check for Ravensburg Local Shopping Graph took 14.305596113204956s
Availability | VoID file availability check for Ravensburg Local Shopping Graph took 0.0006177425384521484s
Completeness | Calculation of interlinking completeness for Ravensburg Local Shopping Graph took 0.295473575592041s
Reputation | Calculation of the PageRank for Ravensburg Local Shopping Graph took 0.02028656005859375s
Interlinking | Calculation of Degree of Connection for Ravensburg Local Shopping Graph took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ravensburg Local Shopping Graph took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Ravensburg Local Shopping Graph took 2.956390380859375e-05s
Believability | Calculation of trust value for Ravensburg Local Shopping Graph took 1.3589859008789062e-05s
INFO | --- Analysis for ravensburg-local-shopping-graph took 28.483043909072876s
Availability | SPARQL endpoint availability check for Polish LGU financial statements took 391.91261434555054s
Availability | VoID file availability check for Polish LGU financial statements took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for Polish LGU financial statements took 0.32869863510131836s
Reputation | Calculation of the PageRank for Polish LGU financial statements took 0.02132129669189453s
Interlinking | Calculation of Degree of Connection for Polish LGU financial statements took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Polish LGU financial statements took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Polish LGU financial statements took 0.0004029273986816406s
Believability | Calculation of trust value for Polish LGU financial statements took 9.5367431640625e-06s
INFO | --- Analysis for Rb_PL_LGU took 664.8360545635223s
Availability | SPARQL endpoint availability check for RDF Book Mashup took 4.649162292480469e-05s
Availability | VoID file availability check for RDF Book Mashup took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for RDF Book Mashup took 0.2745838165283203s
Reputation | Calculation of the PageRank for RDF Book Mashup took 0.02063274383544922s
Interlinking | Calculation of Degree of Connection for RDF Book Mashup took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RDF Book Mashup took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for RDF Book Mashup took 8.296966552734375e-05s
Believability | Calculation of trust value for RDF Book Mashup took 1.0967254638671875e-05s
INFO | --- Analysis for rdf-book-mashup took 3.2383952140808105s
Availability | SPARQL endpoint availability check for Last.FM RDFization of Events, Artists, and Users took 4.1484832763671875e-05s
Availability | VoID file availability check for Last.FM RDFization of Events, Artists, and Users took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for Last.FM RDFization of Events, Artists, and Users took 0.2756838798522949s
Reputation | Calculation of the PageRank for Last.FM RDFization of Events, Artists, and Users took 0.020924806594848633s
Interlinking | Calculation of Degree of Connection for Last.FM RDFization of Events, Artists, and Users took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Last.FM RDFization of Events, Artists, and Users took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Last.FM RDFization of Events, Artists, and Users took 9.655952453613281e-05s
Believability | Calculation of trust value for Last.FM RDFization of Events, Artists, and Users took 1.1205673217773438e-05s
INFO | --- Analysis for rdfize-lastfm took 2.5055620670318604s
Availability | SPARQL endpoint availability check for RDFLicense took 261.58630871772766s
Availability | VoID file availability check for RDFLicense took 0.0005848407745361328s
Completeness | Calculation of interlinking completeness for RDFLicense took 0.28455662727355957s
Reputation | Calculation of the PageRank for RDFLicense took 0.020573854446411133s
Interlinking | Calculation of Degree of Connection for RDFLicense took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RDFLicense took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for RDFLicense took 3.838539123535156e-05s
Believability | Calculation of trust value for RDFLicense took 1.1920928955078125e-05s
INFO | --- Analysis for rdflicense took 536.5513207912445s
Availability | SPARQL endpoint availability check for RDFohloh took 8.893013000488281e-05s
Availability | VoID file availability check for RDFohloh took 0.0006473064422607422s
Completeness | Calculation of interlinking completeness for RDFohloh took 0.26445484161376953s
Reputation | Calculation of the PageRank for RDFohloh took 0.02093505859375s
Interlinking | Calculation of Degree of Connection for RDFohloh took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RDFohloh took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for RDFohloh took 9.250640869140625e-05s
Believability | Calculation of trust value for RDFohloh took 1.1682510375976562e-05s
INFO | --- Analysis for rdfohloh took 6.711368083953857s
Availability | SPARQL endpoint availability check for Reactome RDF took 0.5485324859619141s
Availability | VoID file availability check for Reactome RDF took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for Reactome RDF took 0.271120548248291s
Reputation | Calculation of the PageRank for Reactome RDF took 0.020325660705566406s
Interlinking | Calculation of Degree of Connection for Reactome RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Reactome RDF took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Reactome RDF took 3.647804260253906e-05s
Believability | Calculation of trust value for Reactome RDF took 1.2159347534179688e-05s
INFO | --- Analysis for reactome-rdf took 3.7096445560455322s
Availability | SPARQL endpoint availability check for Rechtspraak.nl took 0.10849356651306152s
Availability | VoID file availability check for Rechtspraak.nl took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for Rechtspraak.nl took 0.2695503234863281s
Reputation | Calculation of the PageRank for Rechtspraak.nl took 0.020782947540283203s
Interlinking | Calculation of Degree of Connection for Rechtspraak.nl took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Rechtspraak.nl took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Rechtspraak.nl took 9.131431579589844e-05s
Believability | Calculation of trust value for Rechtspraak.nl took 8.821487426757812e-06s
INFO | --- Analysis for rechtspraak took 2.607686758041382s
Availability | SPARQL endpoint availability check for Red Uno Internacional (Santillana) took 0.00011658668518066406s
Availability | VoID file availability check for Red Uno Internacional (Santillana) took 0.0006084442138671875s
Completeness | Calculation of interlinking completeness for Red Uno Internacional (Santillana) took 0.2658114433288574s
Reputation | Calculation of the PageRank for Red Uno Internacional (Santillana) took 0.02045893669128418s
Interlinking | Calculation of Degree of Connection for Red Uno Internacional (Santillana) took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Red Uno Internacional (Santillana) took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Red Uno Internacional (Santillana) took 8.511543273925781e-05s
Believability | Calculation of trust value for Red Uno Internacional (Santillana) took 1.0251998901367188e-05s
INFO | --- Analysis for red-uno-internacional-santillana took 7.327005863189697s
Availability | SPARQL endpoint availability check for reference.data.gov.uk took 0.07435965538024902s
Availability | VoID file availability check for reference.data.gov.uk took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for reference.data.gov.uk took 0.279191255569458s
Reputation | Calculation of the PageRank for reference.data.gov.uk took 0.02054452896118164s
Interlinking | Calculation of Degree of Connection for reference.data.gov.uk took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for reference.data.gov.uk took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for reference.data.gov.uk took 0.0001552104949951172s
Believability | Calculation of trust value for reference.data.gov.uk took 9.298324584960938e-06s
INFO | --- Analysis for reference-data-gov-uk took 2.5939667224884033s
Availability | SPARQL endpoint availability check for RELD took 0.5697019100189209s
Availability | VoID file availability check for RELD took 0.0003495216369628906s
Completeness | Calculation of interlinking completeness for RELD took 0.2795107364654541s
Reputation | Calculation of the PageRank for RELD took 0.02022838592529297s
Interlinking | Calculation of Degree of Connection for RELD took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for RELD took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for RELD took 3.0279159545898438e-05s
Believability | Calculation of trust value for RELD took 1.4543533325195312e-05s
INFO | --- Analysis for RELD took 3.8739616870880127s
Availability | SPARQL endpoint availability check for Repository for Linked Open Archival Data took 0.16699838638305664s
Availability | VoID file availability check for Repository for Linked Open Archival Data took 0.0005004405975341797s
Extra | Recovery of all triples for Repository for Linked Open Archival Data took 1.7817397117614746s
Performance | Total latancy measurement for Repository for Linked Open Archival Data took 0.6286604404449463s
Amount of data | Number of triples check for Repository for Linked Open Archival Data took 1.3493824005126953s
Interoperability | New terms check for Repository for Linked Open Archival Data took 1.7726237773895264s
Versatility | Languages check for Repository for Linked Open Archival Data took 17.242327451705933s
Interpretability | Number of blank nodes check for Repository for Linked Open Archival Data took 2.269637107849121s
Security | Check HTTPS for Repository for Linked Open Archival Data took 0.2559475898742676s
Interpretability | RDF structures check for Repository for Linked Open Archival Data took 0.3835878372192383s
Versatility | Serialization formats check for Repository for Linked Open Archival Data took 0.2575066089630127s
Availability | RDF dump link check for Repository for Linked Open Archival Data took 0.3037436008453369s
License | MR license check for Repository for Linked Open Archival Data took 0.4001731872558594s
License | HR license check for Repository for Linked Open Archival Data took 7.941409587860107s
Amount of data | Number of property check for Repository for Linked Open Archival Data took 0.11726975440979004s
Understandability | Number of label check for Repository for Linked Open Archival Data took 0.9353220462799072s
Understandability | URI regex check for Repository for Linked Open Archival Data took 0.6174314022064209s
Understandability | Vocabs check for Repository for Linked Open Archival Data took 0.1203465461730957s
Verifiability | Authors check for Repository for Linked Open Archival Data took 0.1584024429321289s
Verifiability | Publishers check for Repository for Linked Open Archival Data took 0.1571512222290039s
Performance | Throughput check for Repository for Linked Open Archival Data took 14.058652400970459s
Amount of data | Check the number of entities for Repository for Linked Open Archival Data took 0.0001437664031982422s
Verifiability | Contribs. check for Repository for Linked Open Archival Data took 0.06336784362792969s
Interlinking | sameAs chians check for Repository for Linked Open Archival Data took 0.14845824241638184s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.4129157066345215s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.06211423873901367s
Timeliness | dataset update frequency check for Repository for Linked Open Archival Data took 0.28084754943847656s
Currency | Creation date check for Repository for Linked Open Archival Data took 0.14890789985656738s
Currency | Modification date check for Repository for Linked Open Archival Data took 0.14920759201049805s
Rep.Conc. | URIs length for Repository for Linked Open Archival Data took 2.5590884685516357s
Interoperability | New vocabularies check for Repository for Linked Open Archival Data took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Repository for Linked Open Archival Data took 0.08483719825744629s
Accuracy | Check Functional Property for Repository for Linked Open Archival Data took 0.09356832504272461s
Accuracy | Check Inverse Functional Property for Repository for Linked Open Archival Data took 0.13211274147033691s
Accuracy | Check Empty annotation labels for Repository for Linked Open Archival Data took 2.803574800491333s
Accuracy | Check White space in annotation for Repository for Linked Open Archival Data took 0.027611970901489258s
Accuracy | Check Datatype consistency for Repository for Linked Open Archival Data took 0.028264522552490234s
Consistency | Disjoint class check for Repository for Linked Open Archival Data took 0.17394495010375977s
Consistency | Check Misplaced properties for Repository for Linked Open Archival Data took 1.7648532390594482s
Consistency | Misplaced classes for Repository for Linked Open Archival Data took 0.21288633346557617s
Consistency | Check Ontology hijacking for Repository for Linked Open Archival Data took 1.6714224815368652s
Consistency | Check Invalid usage of undefined classes for Repository for Linked Open Archival Data took 1.2865779399871826s
Consistency | Check Invalid usage of undefined properties for Repository for Linked Open Archival Data took 2.8953471183776855s
Conciseness | Check Extensional conciseness for Repository for Linked Open Archival Data took 0.031636714935302734s
Conciseness | Check Intensional conciseness for Repository for Linked Open Archival Data took 0.11317014694213867s
Security | Sign check for Repository for Linked Open Archival Data took 0.4613199234008789s
Availability | Check URIs Dereferenciability for Repository for Linked Open Archival Data took 1221.8887305259705s
Completeness | Calculation of interlinking completeness for Repository for Linked Open Archival Data took 0.4691643714904785s
Reputation | Calculation of the PageRank for Repository for Linked Open Archival Data took 0.021189212799072266s
Interlinking | Calculation of Degree of Connection for Repository for Linked Open Archival Data took 0.0001494884490966797s
Interlinking | Calculation of Centrality for Repository for Linked Open Archival Data took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Repository for Linked Open Archival Data took 4.792213439941406e-05s
Interoperability | Check the re-using of existing vocabs for Repository for Linked Open Archival Data took 1.6689300537109375e-06s
Believability | Calculation of trust value for Repository for Linked Open Archival Data took 1.0967254638671875e-05s
INFO | --- Analysis for reload took 1345.894190788269s
Availability | SPARQL endpoint availability check for Land use merced dataset took 4.38690185546875e-05s
Availability | VoID file availability check for Land use merced dataset took 0.0005338191986083984s
Completeness | Calculation of interlinking completeness for Land use merced dataset took 0.2692265510559082s
Reputation | Calculation of the PageRank for Land use merced dataset took 0.022798776626586914s
Interlinking | Calculation of Degree of Connection for Land use merced dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Land use merced dataset took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Land use merced dataset took 3.0279159545898438e-05s
Believability | Calculation of trust value for Land use merced dataset took 1.0967254638671875e-05s
INFO | --- Analysis for remote_Sensing took 3.0924315452575684s
Availability | SPARQL endpoint availability check for Renewable Energy Generators took 1.3862504959106445s
Availability | VoID file availability check for Renewable Energy Generators took 0.0006389617919921875s
Completeness | Calculation of interlinking completeness for Renewable Energy Generators took 0.281172513961792s
Reputation | Calculation of the PageRank for Renewable Energy Generators took 0.020359277725219727s
Interlinking | Calculation of Degree of Connection for Renewable Energy Generators took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Renewable Energy Generators took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Renewable Energy Generators took 4.172325134277344e-05s
Believability | Calculation of trust value for Renewable Energy Generators took 8.821487426757812e-06s
INFO | --- Analysis for renewable_energy_generators took 9.439116954803467s
Availability | SPARQL endpoint availability check for research.data.gov.uk took 0.05837559700012207s
Availability | VoID file availability check for research.data.gov.uk took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for research.data.gov.uk took 0.2746317386627197s
Reputation | Calculation of the PageRank for research.data.gov.uk took 0.021796464920043945s
Interlinking | Calculation of Degree of Connection for research.data.gov.uk took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for research.data.gov.uk took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for research.data.gov.uk took 9.250640869140625e-05s
Believability | Calculation of trust value for research.data.gov.uk took 1.0251998901367188e-05s
INFO | --- Analysis for research-data-gov-uk took 2.5697989463806152s
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.0006647109985351562s
Completeness | Calculation of interlinking completeness for Reuters-128 NIF NER Corpus took 0.26758337020874023s
Reputation | Calculation of the PageRank for Reuters-128 NIF NER Corpus took 0.020416259765625s
Interlinking | Calculation of Degree of Connection for Reuters-128 NIF NER Corpus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Reuters-128 NIF NER Corpus took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Reuters-128 NIF NER Corpus took 6.461143493652344e-05s
Believability | Calculation of trust value for Reuters-128 NIF NER Corpus took 1.1682510375976562e-05s
INFO | --- Analysis for reuters-128-nif-ner-corpus took 3.966470718383789s
Availability | SPARQL endpoint availability check for Revista Excelencias Turísticas took 0.051731109619140625s
Availability | VoID file availability check for Revista Excelencias Turísticas took 0.0005958080291748047s
Completeness | Calculation of interlinking completeness for Revista Excelencias Turísticas took 0.31575727462768555s
Reputation | Calculation of the PageRank for Revista Excelencias Turísticas took 0.02241826057434082s
Interlinking | Calculation of Degree of Connection for Revista Excelencias Turísticas took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Revista Excelencias Turísticas took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Revista Excelencias Turísticas took 2.9087066650390625e-05s
Believability | Calculation of trust value for Revista Excelencias Turísticas took 1.239776611328125e-05s
INFO | --- Analysis for revistas_turismo took 2.6239728927612305s
Availability | SPARQL endpoint availability check for Revyu.com - Review Anything took 0.2535421848297119s
Availability | VoID file availability check for Revyu.com - Review Anything took 0.00042176246643066406s
Completeness | Calculation of interlinking completeness for Revyu.com - Review Anything took 0.2761504650115967s
Reputation | Calculation of the PageRank for Revyu.com - Review Anything took 0.021990060806274414s
Interlinking | Calculation of Degree of Connection for Revyu.com - Review Anything took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Revyu.com - Review Anything took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Revyu.com - Review Anything took 0.0001163482666015625s
Believability | Calculation of trust value for Revyu.com - Review Anything took 9.775161743164062e-06s
INFO | --- Analysis for revyu took 2.679260492324829s
Availability | SPARQL endpoint availability check for sdafsadf took 0.3594515323638916s
Availability | VoID file availability check for sdafsadf took 0.0004923343658447266s
Completeness | Calculation of interlinking completeness for sdafsadf took 0.2652928829193115s
Reputation | Calculation of the PageRank for sdafsadf took 0.020539522171020508s
Interlinking | Calculation of Degree of Connection for sdafsadf took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for sdafsadf took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for sdafsadf took 3.0279159545898438e-05s
Believability | Calculation of trust value for sdafsadf took 1.1444091796875e-05s
INFO | --- Analysis for rgsdfg took 3.2575955390930176s
Availability | SPARQL endpoint availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 4.4345855712890625e-05s
Availability | VoID file availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for RDFizing and Interlinking the EuroStat Data Set Effort took 0.26476335525512695s
Reputation | Calculation of the PageRank for RDFizing and Interlinking the EuroStat Data Set Effort took 0.02051377296447754s
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.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for RDFizing and Interlinking the EuroStat Data Set Effort took 4.410743713378906e-05s
Believability | Calculation of trust value for RDFizing and Interlinking the EuroStat Data Set Effort took 1.1444091796875e-05s
INFO | --- Analysis for riese took 22.778690099716187s
Availability | SPARQL endpoint availability check for Répertoire International des Sources Musicales - RISM took 0.3077964782714844s
Availability | VoID file availability check for Répertoire International des Sources Musicales - RISM took 0.0006532669067382812s
Extra | Recovery of all triples for Répertoire International des Sources Musicales - RISM took 72.44510912895203s
Performance | Total latancy measurement for Répertoire International des Sources Musicales - RISM took 0.44643664360046387s
Amount of data | Number of triples check for Répertoire International des Sources Musicales - RISM took 55.1604483127594s
Interoperability | New terms check for Répertoire International des Sources Musicales - RISM took 1.6589577198028564s
Versatility | Languages check for Répertoire International des Sources Musicales - RISM took 170.94474053382874s
Interpretability | Number of blank nodes check for Répertoire International des Sources Musicales - RISM took 47.90978264808655s
Security | Check HTTPS for Répertoire International des Sources Musicales - RISM took 0.20807933807373047s
Interpretability | RDF structures check for Répertoire International des Sources Musicales - RISM took 0.1347367763519287s
Versatility | Serialization formats check for Répertoire International des Sources Musicales - RISM took 0.12340736389160156s
Availability | RDF dump link check for Répertoire International des Sources Musicales - RISM took 0.08635067939758301s
License | MR license check for Répertoire International des Sources Musicales - RISM took 0.11407351493835449s
License | HR license check for Répertoire International des Sources Musicales - RISM took 300.10386300086975s
Amount of data | Number of property check for Répertoire International des Sources Musicales - RISM took 0.11731839179992676s
Understandability | Number of label check for Répertoire International des Sources Musicales - RISM took 11.391040086746216s
Understandability | URI regex check for Répertoire International des Sources Musicales - RISM took 0.2047443389892578s
Understandability | Vocabs check for Répertoire International des Sources Musicales - RISM took 0.08361935615539551s
Verifiability | Authors check for Répertoire International des Sources Musicales - RISM took 0.09493803977966309s
Verifiability | Publishers check for Répertoire International des Sources Musicales - RISM took 0.08344554901123047s
Performance | Throughput check for Répertoire International des Sources Musicales - RISM took 10.205686569213867s
Amount of data | Check the number of entities for Répertoire International des Sources Musicales - RISM took 7.700920104980469e-05s
Verifiability | Contribs. check for Répertoire International des Sources Musicales - RISM took 0.08363080024719238s
Interlinking | sameAs chians check for Répertoire International des Sources Musicales - RISM took 1.5363402366638184s
Interlinking | skos check for Répertoire International des Sources Musicales - RISM took 0.1383073329925537s
Interlinking | skos check for Répertoire International des Sources Musicales - RISM took 0.10334181785583496s
Timeliness | dataset update frequency check for Répertoire International des Sources Musicales - RISM took 0.0882120132446289s
Currency | Creation date check for Répertoire International des Sources Musicales - RISM took 0.20322394371032715s
Currency | Modification date check for Répertoire International des Sources Musicales - RISM took 0.21776437759399414s
Rep.Conc. | URIs length for Répertoire International des Sources Musicales - RISM took 77.63897776603699s
Interoperability | New vocabularies check for Répertoire International des Sources Musicales - RISM took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Répertoire International des Sources Musicales - RISM took 0.11766219139099121s
Accuracy | Check Functional Property for Répertoire International des Sources Musicales - RISM took 0.11509847640991211s
Accuracy | Check Inverse Functional Property for Répertoire International des Sources Musicales - RISM took 0.08635139465332031s
Accuracy | Check Empty annotation labels for Répertoire International des Sources Musicales - RISM took 26.556085109710693s
Accuracy | Check White space in annotation for Répertoire International des Sources Musicales - RISM took 2.375764846801758s
Accuracy | Check Datatype consistency for Répertoire International des Sources Musicales - RISM took 3.7319705486297607s
Consistency | Disjoint class check for Répertoire International des Sources Musicales - RISM took 0.09099507331848145s
Consistency | Check Misplaced properties for Répertoire International des Sources Musicales - RISM took 46.3444459438324s
Consistency | Check Ontology hijacking for Répertoire International des Sources Musicales - RISM took 7.933678150177002s
Consistency | Check Invalid usage of undefined classes for Répertoire International des Sources Musicales - RISM took 1.2841486930847168s
Consistency | Check Invalid usage of undefined properties for Répertoire International des Sources Musicales - RISM took 44.15137219429016s
Conciseness | Check Extensional conciseness for Répertoire International des Sources Musicales - RISM took 2.729905366897583s
Security | Sign check for Répertoire International des Sources Musicales - RISM took 0.09878921508789062s
Availability | Check URIs Dereferenciability for Répertoire International des Sources Musicales - RISM took 1.2801828384399414s
Completeness | Calculation of interlinking completeness for Répertoire International des Sources Musicales - RISM took 0.6246097087860107s
Reputation | Calculation of the PageRank for Répertoire International des Sources Musicales - RISM took 0.020677804946899414s
Interlinking | Calculation of Degree of Connection for Répertoire International des Sources Musicales - RISM took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Répertoire International des Sources Musicales - RISM took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Répertoire International des Sources Musicales - RISM took 5.3882598876953125e-05s
Interoperability | Check the re-using of existing vocabs for Répertoire International des Sources Musicales - RISM took 1.9073486328125e-06s
Believability | Calculation of trust value for Répertoire International des Sources Musicales - RISM took 6.4373016357421875e-06s
INFO | --- Analysis for rism took 1113.306676864624s
Availability | SPARQL endpoint availability check for RISM Authority data took 0.08268857002258301s
Availability | VoID file availability check for RISM Authority data took 0.0005919933319091797s
Extra | Recovery of all triples for RISM Authority data took 72.58273601531982s
Performance | Total latancy measurement for RISM Authority data took 0.4831736087799072s
Amount of data | Number of triples check for RISM Authority data took 55.060152530670166s
Interoperability | New terms check for RISM Authority data took 1.49599289894104s
Versatility | Languages check for RISM Authority data took 164.933203458786s
Interpretability | Number of blank nodes check for RISM Authority data took 47.86422300338745s
Security | Check HTTPS for RISM Authority data took 0.1336345672607422s
Interpretability | RDF structures check for RISM Authority data took 0.11344051361083984s
Versatility | Serialization formats check for RISM Authority data took 0.11863493919372559s
Availability | RDF dump link check for RISM Authority data took 0.08285880088806152s
License | MR license check for RISM Authority data took 0.10238981246948242s
License | HR license check for RISM Authority data took 300.1017391681671s
Amount of data | Number of property check for RISM Authority data took 0.10805249214172363s
Understandability | Number of label check for RISM Authority data took 6.585792303085327s
Understandability | URI regex check for RISM Authority data took 0.20273637771606445s
Understandability | Vocabs check for RISM Authority data took 0.08296322822570801s
Verifiability | Authors check for RISM Authority data took 0.08424806594848633s
Verifiability | Publishers check for RISM Authority data took 0.08289551734924316s
Performance | Throughput check for RISM Authority data took 10.24845838546753s
Amount of data | Check the number of entities for RISM Authority data took 6.747245788574219e-05s
Verifiability | Contribs. check for RISM Authority data took 0.08330535888671875s
Interlinking | sameAs chians check for RISM Authority data took 1.0640616416931152s
Interlinking | skos check for RISM Authority data took 0.10747694969177246s
Interlinking | skos check for RISM Authority data took 0.08332347869873047s
Timeliness | dataset update frequency check for RISM Authority data took 0.08319902420043945s
Currency | Creation date check for RISM Authority data took 0.2783176898956299s
Currency | Modification date check for RISM Authority data took 0.2313840389251709s
Rep.Conc. | URIs length for RISM Authority data took 81.39997696876526s
Interoperability | New vocabularies check for RISM Authority data took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for RISM Authority data took 0.1290276050567627s
Accuracy | Check Functional Property for RISM Authority data took 0.11158490180969238s
Accuracy | Check Inverse Functional Property for RISM Authority data took 0.10061955451965332s
Accuracy | Check Empty annotation labels for RISM Authority data took 26.95940399169922s
Accuracy | Check White space in annotation for RISM Authority data took 2.380038022994995s
Accuracy | Check Datatype consistency for RISM Authority data took 3.8770198822021484s
Consistency | Disjoint class check for RISM Authority data took 0.09016132354736328s
Consistency | Check Misplaced properties for RISM Authority data took 43.04391932487488s
Consistency | Check Ontology hijacking for RISM Authority data took 7.958101272583008s
Consistency | Check Invalid usage of undefined classes for RISM Authority data took 1.301574468612671s
Consistency | Check Invalid usage of undefined properties for RISM Authority data took 49.04725694656372s
Conciseness | Check Extensional conciseness for RISM Authority data took 2.818274974822998s
Security | Sign check for RISM Authority data took 0.10251736640930176s
Availability | Check URIs Dereferenciability for RISM Authority data took 1.309438943862915s
Completeness | Calculation of interlinking completeness for RISM Authority data took 0.51619553565979s
Reputation | Calculation of the PageRank for RISM Authority data took 0.020982980728149414s
Interlinking | Calculation of Degree of Connection for RISM Authority data took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for RISM Authority data took 0.0006809234619140625s
Interlinking | Calculation of Clustering coefficient for RISM Authority data took 5.507469177246094e-05s
Interoperability | Check the re-using of existing vocabs for RISM Authority data took 2.384185791015625e-06s
Believability | Calculation of trust value for RISM Authority data took 1.0251998901367188e-05s
INFO | --- Analysis for rism-authorities took 1101.0622119903564s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 8.559226989746094e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.2675457000732422s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.02049732208251953s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 3.886222839355469e-05s
Believability | Calculation of trust value for engineering equipment ontology took 1.0967254638671875e-05s
INFO | --- Analysis for rk took 2.4726920127868652s
Availability | SPARQL endpoint availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.05458211898803711s
Availability | VoID file availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.00043129920959472656s
Completeness | Calculation of interlinking completeness for Association for Computing Machinery (ACM) (RKBExplorer) took 0.27803707122802734s
Reputation | Calculation of the PageRank for Association for Computing Machinery (ACM) (RKBExplorer) took 0.022445201873779297s
Interlinking | Calculation of Degree of Connection for Association for Computing Machinery (ACM) (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Association for Computing Machinery (ACM) (RKBExplorer) took 0.00022602081298828125s
Believability | Calculation of trust value for Association for Computing Machinery (ACM) (RKBExplorer) took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-acm took 2.5775318145751953s
Availability | SPARQL endpoint availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.026575803756713867s
Availability | VoID file availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.0004642009735107422s
Completeness | Calculation of interlinking completeness for Budapest University of Technology and Economics (RKBExplorer) took 0.2766432762145996s
Reputation | Calculation of the PageRank for Budapest University of Technology and Economics (RKBExplorer) took 0.022356033325195312s
Interlinking | Calculation of Degree of Connection for Budapest University of Technology and Economics (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Budapest University of Technology and Economics (RKBExplorer) took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Budapest University of Technology and Economics (RKBExplorer) took 0.00013780593872070312s
Believability | Calculation of trust value for Budapest University of Technology and Economics (RKBExplorer) took 1.0013580322265625e-05s
INFO | --- Analysis for rkb-explorer-budapest took 2.5549075603485107s
Availability | SPARQL endpoint availability check for CiteSeer (Research Index) (RKBExplorer) took 0.04934287071228027s
Availability | VoID file availability check for CiteSeer (Research Index) (RKBExplorer) took 0.00042366981506347656s
Completeness | Calculation of interlinking completeness for CiteSeer (Research Index) (RKBExplorer) took 0.2629399299621582s
Reputation | Calculation of the PageRank for CiteSeer (Research Index) (RKBExplorer) took 0.022080659866333008s
Interlinking | Calculation of Degree of Connection for CiteSeer (Research Index) (RKBExplorer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for CiteSeer (Research Index) (RKBExplorer) took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for CiteSeer (Research Index) (RKBExplorer) took 0.00020599365234375s
Believability | Calculation of trust value for CiteSeer (Research Index) (RKBExplorer) took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-citeseer took 2.6098642349243164s
Availability | SPARQL endpoint availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0341341495513916s
Availability | VoID file availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0004553794860839844s
Completeness | Calculation of interlinking completeness for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.2681617736816406s
Reputation | Calculation of the PageRank for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.020447254180908203s
Interlinking | Calculation of Degree of Connection for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0001571178436279297s
Believability | Calculation of trust value for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-cordis took 2.515592098236084s
Availability | SPARQL endpoint availability check for Resilient Computing Courseware (RKBExplorer) took 0.03336000442504883s
Availability | VoID file availability check for Resilient Computing Courseware (RKBExplorer) took 0.00039958953857421875s
Completeness | Calculation of interlinking completeness for Resilient Computing Courseware (RKBExplorer) took 0.27072668075561523s
Reputation | Calculation of the PageRank for Resilient Computing Courseware (RKBExplorer) took 0.020176172256469727s
Interlinking | Calculation of Degree of Connection for Resilient Computing Courseware (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Resilient Computing Courseware (RKBExplorer) took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Resilient Computing Courseware (RKBExplorer) took 0.00015807151794433594s
Believability | Calculation of trust value for Resilient Computing Courseware (RKBExplorer) took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-courseware took 2.4838051795959473s
Availability | SPARQL endpoint availability check for Street level crime reports for England and Wales took 0.03264188766479492s
Availability | VoID file availability check for Street level crime reports for England and Wales took 0.0005459785461425781s
Completeness | Calculation of interlinking completeness for Street level crime reports for England and Wales took 0.26376795768737793s
Reputation | Calculation of the PageRank for Street level crime reports for England and Wales took 0.020471811294555664s
Interlinking | Calculation of Degree of Connection for Street level crime reports for England and Wales took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Street level crime reports for England and Wales took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Street level crime reports for England and Wales took 3.910064697265625e-05s
Believability | Calculation of trust value for Street level crime reports for England and Wales took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-crime took 2.5438475608825684s
Availability | SPARQL endpoint availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.035830020904541016s
Availability | VoID file availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0004470348358154297s
Completeness | Calculation of interlinking completeness for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.27334022521972656s
Reputation | Calculation of the PageRank for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.022112131118774414s
Interlinking | Calculation of Degree of Connection for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00011777877807617188s
Believability | Calculation of trust value for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 9.5367431640625e-06s
INFO | --- Analysis for rkb-explorer-curriculum took 2.528946876525879s
Availability | SPARQL endpoint availability check for Technische Universität Darmstadt (RKBExplorer) took 0.03787732124328613s
Availability | VoID file availability check for Technische Universität Darmstadt (RKBExplorer) took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for Technische Universität Darmstadt (RKBExplorer) took 0.270460844039917s
Reputation | Calculation of the PageRank for Technische Universität Darmstadt (RKBExplorer) took 0.02209162712097168s
Interlinking | Calculation of Degree of Connection for Technische Universität Darmstadt (RKBExplorer) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Technische Universität Darmstadt (RKBExplorer) took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Technische Universität Darmstadt (RKBExplorer) took 5.4836273193359375e-05s
Believability | Calculation of trust value for Technische Universität Darmstadt (RKBExplorer) took 1.3113021850585938e-05s
INFO | --- Analysis for rkb-explorer-darmstadt took 2.5285303592681885s
Availability | SPARQL endpoint availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.03534507751464844s
Availability | VoID file availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.00047397613525390625s
Completeness | Calculation of interlinking completeness for DBLP Computer Science Bibliography (RKBExplorer) took 0.2678873538970947s
Reputation | Calculation of the PageRank for DBLP Computer Science Bibliography (RKBExplorer) took 0.021042585372924805s
Interlinking | Calculation of Degree of Connection for DBLP Computer Science Bibliography (RKBExplorer) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for DBLP Computer Science Bibliography (RKBExplorer) took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for DBLP Computer Science Bibliography (RKBExplorer) took 0.0002474784851074219s
Believability | Calculation of trust value for DBLP Computer Science Bibliography (RKBExplorer) took 1.2874603271484375e-05s
INFO | --- Analysis for rkb-explorer-dblp took 2.5260043144226074s
Availability | SPARQL endpoint availability check for Deep Blue (RKBExplorer) took 0.034628868103027344s
Availability | VoID file availability check for Deep Blue (RKBExplorer) took 0.00044035911560058594s
Completeness | Calculation of interlinking completeness for Deep Blue (RKBExplorer) took 0.26604390144348145s
Reputation | Calculation of the PageRank for Deep Blue (RKBExplorer) took 0.02063155174255371s
Interlinking | Calculation of Degree of Connection for Deep Blue (RKBExplorer) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Deep Blue (RKBExplorer) took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Deep Blue (RKBExplorer) took 7.462501525878906e-05s
Believability | Calculation of trust value for Deep Blue (RKBExplorer) took 9.775161743164062e-06s
INFO | --- Analysis for rkb-explorer-deepblue took 2.5262482166290283s
Availability | SPARQL endpoint availability check for DEPLOY (RKBExplorer) took 0.3612058162689209s
Availability | VoID file availability check for DEPLOY (RKBExplorer) took 0.0005345344543457031s
Completeness | Calculation of interlinking completeness for DEPLOY (RKBExplorer) took 0.265852689743042s
Reputation | Calculation of the PageRank for DEPLOY (RKBExplorer) took 0.02144336700439453s
Interlinking | Calculation of Degree of Connection for DEPLOY (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DEPLOY (RKBExplorer) took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for DEPLOY (RKBExplorer) took 9.608268737792969e-05s
Believability | Calculation of trust value for DEPLOY (RKBExplorer) took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-deploy took 3.701993227005005s
Availability | SPARQL endpoint availability check for digitaleconomy took 0.02801060676574707s
Availability | VoID file availability check for digitaleconomy took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for digitaleconomy took 0.2646646499633789s
Reputation | Calculation of the PageRank for digitaleconomy took 0.02084803581237793s
Interlinking | Calculation of Degree of Connection for digitaleconomy took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for digitaleconomy took 0.0008449554443359375s
Interlinking | Calculation of Clustering coefficient for digitaleconomy took 3.4809112548828125e-05s
Believability | Calculation of trust value for digitaleconomy took 1.2874603271484375e-05s
INFO | --- Analysis for rkb-explorer-digitaleconomy took 2.5010409355163574s
Availability | SPARQL endpoint availability check for dotAC (RKBExplorer) took 0.027115345001220703s
Availability | VoID file availability check for dotAC (RKBExplorer) took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for dotAC (RKBExplorer) took 0.2593522071838379s
Reputation | Calculation of the PageRank for dotAC (RKBExplorer) took 0.020673513412475586s
Interlinking | Calculation of Degree of Connection for dotAC (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for dotAC (RKBExplorer) took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for dotAC (RKBExplorer) took 0.00014448165893554688s
Believability | Calculation of trust value for dotAC (RKBExplorer) took 9.775161743164062e-06s
INFO | --- Analysis for rkb-explorer-dotac took 2.4646875858306885s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 0.04238557815551758s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.00036215782165527344s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.2643003463745117s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.021744966506958008s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 5.2928924560546875e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 9.775161743164062e-06s
INFO | --- Analysis for rkb-explorer-ecs took 3.8588247299194336s
Availability | SPARQL endpoint availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.02805352210998535s
Availability | VoID file availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.00032401084899902344s
Completeness | Calculation of interlinking completeness for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.27111101150512695s
Reputation | Calculation of the PageRank for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.020502090454101562s
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.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0002033710479736328s
Believability | Calculation of trust value for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.2874603271484375e-05s
INFO | --- Analysis for rkb-explorer-eprints took 2.485802173614502s
Availability | SPARQL endpoint availability check for epsrc took 0.027341127395629883s
Availability | VoID file availability check for epsrc took 0.0004718303680419922s
Completeness | Calculation of interlinking completeness for epsrc took 0.2729315757751465s
Reputation | Calculation of the PageRank for epsrc took 0.021848440170288086s
Interlinking | Calculation of Degree of Connection for epsrc took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for epsrc took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for epsrc took 6.246566772460938e-05s
Believability | Calculation of trust value for epsrc took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-epsrc took 2.5302581787109375s
Availability | SPARQL endpoint availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.027106523513793945s
Availability | VoID file availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0003743171691894531s
Completeness | Calculation of interlinking completeness for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.2678356170654297s
Reputation | Calculation of the PageRank for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.020526885986328125s
Interlinking | Calculation of Degree of Connection for ERA - Australian Research Council publication ratings (RKBExplorer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for ERA - Australian Research Council publication ratings (RKBExplorer) took 8.20159912109375e-05s
Believability | Calculation of trust value for ERA - Australian Research Council publication ratings (RKBExplorer) took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-era took 2.530388593673706s
Availability | SPARQL endpoint availability check for Institut Eurécom (RKBExplorer) took 0.026417016983032227s
Availability | VoID file availability check for Institut Eurécom (RKBExplorer) took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for Institut Eurécom (RKBExplorer) took 0.2678651809692383s
Reputation | Calculation of the PageRank for Institut Eurécom (RKBExplorer) took 0.020196914672851562s
Interlinking | Calculation of Degree of Connection for Institut Eurécom (RKBExplorer) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Institut Eurécom (RKBExplorer) took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Institut Eurécom (RKBExplorer) took 0.00010609626770019531s
Believability | Calculation of trust value for Institut Eurécom (RKBExplorer) took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-eurecom took 2.517528533935547s
Availability | SPARQL endpoint availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.37839412689208984s
Availability | VoID file availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.0005340576171875s
Completeness | Calculation of interlinking completeness for France Telecom Recherche et Développement (RKBExplorer) took 0.2700068950653076s
Reputation | Calculation of the PageRank for France Telecom Recherche et Développement (RKBExplorer) took 0.020283937454223633s
Interlinking | Calculation of Degree of Connection for France Telecom Recherche et Développement (RKBExplorer) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for France Telecom Recherche et Développement (RKBExplorer) took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for France Telecom Recherche et Développement (RKBExplorer) took 9.083747863769531e-05s
Believability | Calculation of trust value for France Telecom Recherche et Développement (RKBExplorer) took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-ft took 3.902433395385742s
Availability | SPARQL endpoint availability check for fun took 0.028044939041137695s
Availability | VoID file availability check for fun took 0.0004367828369140625s
Completeness | Calculation of interlinking completeness for fun took 0.26358795166015625s
Reputation | Calculation of the PageRank for fun took 0.0205535888671875s
Interlinking | Calculation of Degree of Connection for fun took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for fun took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for fun took 7.367134094238281e-05s
Believability | Calculation of trust value for fun took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-fun took 2.495769500732422s
Availability | SPARQL endpoint availability check for gdlc took 0.033770084381103516s
Availability | VoID file availability check for gdlc took 0.0004191398620605469s
Completeness | Calculation of interlinking completeness for gdlc took 0.2704281806945801s
Reputation | Calculation of the PageRank for gdlc took 0.022156476974487305s
Interlinking | Calculation of Degree of Connection for gdlc took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for gdlc took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for gdlc took 6.771087646484375e-05s
Believability | Calculation of trust value for gdlc took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-gdlc took 2.536026954650879s
Availability | SPARQL endpoint availability check for IBM Research GmbH (RKBExplorer) took 0.03592681884765625s
Availability | VoID file availability check for IBM Research GmbH (RKBExplorer) took 0.0004143714904785156s
Completeness | Calculation of interlinking completeness for IBM Research GmbH (RKBExplorer) took 0.2694878578186035s
Reputation | Calculation of the PageRank for IBM Research GmbH (RKBExplorer) took 0.020322322845458984s
Interlinking | Calculation of Degree of Connection for IBM Research GmbH (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IBM Research GmbH (RKBExplorer) took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for IBM Research GmbH (RKBExplorer) took 0.00011324882507324219s
Believability | Calculation of trust value for IBM Research GmbH (RKBExplorer) took 9.775161743164062e-06s
INFO | --- Analysis for rkb-explorer-ibm took 2.502497911453247s
Availability | SPARQL endpoint availability check for IEEE Papers (RKBExplorer) took 0.0352170467376709s
Availability | VoID file availability check for IEEE Papers (RKBExplorer) took 0.00041985511779785156s
Completeness | Calculation of interlinking completeness for IEEE Papers (RKBExplorer) took 0.2725064754486084s
Reputation | Calculation of the PageRank for IEEE Papers (RKBExplorer) took 0.02033090591430664s
Interlinking | Calculation of Degree of Connection for IEEE Papers (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IEEE Papers (RKBExplorer) took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for IEEE Papers (RKBExplorer) took 0.0001347064971923828s
Believability | Calculation of trust value for IEEE Papers (RKBExplorer) took 1.0013580322265625e-05s
INFO | --- Analysis for rkb-explorer-ieee took 2.5022692680358887s
Availability | SPARQL endpoint availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.027246713638305664s
Availability | VoID file availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0004208087921142578s
Completeness | Calculation of interlinking completeness for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.27607107162475586s
Reputation | Calculation of the PageRank for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.021253585815429688s
Interlinking | Calculation of Degree of Connection for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.00013875961303710938s
Believability | Calculation of trust value for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 9.775161743164062e-06s
INFO | --- Analysis for rkb-explorer-irit took 2.516770362854004s
Availability | SPARQL endpoint availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.03446650505065918s
Availability | VoID file availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0004360675811767578s
Completeness | Calculation of interlinking completeness for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.26559996604919434s
Reputation | Calculation of the PageRank for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.020090579986572266s
Interlinking | Calculation of Degree of Connection for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 6.151199340820312e-05s
Believability | Calculation of trust value for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 9.775161743164062e-06s
INFO | --- Analysis for rkb-explorer-italy took 2.477539539337158s
Availability | SPARQL endpoint availability check for UK JISC (RKBExplorer) took 0.04719972610473633s
Availability | VoID file availability check for UK JISC (RKBExplorer) took 0.0003731250762939453s
Completeness | Calculation of interlinking completeness for UK JISC (RKBExplorer) took 0.2681093215942383s
Reputation | Calculation of the PageRank for UK JISC (RKBExplorer) took 0.02060866355895996s
Interlinking | Calculation of Degree of Connection for UK JISC (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for UK JISC (RKBExplorer) took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for UK JISC (RKBExplorer) took 7.534027099609375e-05s
Believability | Calculation of trust value for UK JISC (RKBExplorer) took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-jisc took 2.548292398452759s
Availability | SPARQL endpoint availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.027701854705810547s
Availability | VoID file availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.2669074535369873s
Reputation | Calculation of the PageRank for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.020219802856445312s
Interlinking | Calculation of Degree of Connection for Vytautas Magnus University, Kaunas (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Vytautas Magnus University, Kaunas (RKBExplorer) took 4.172325134277344e-05s
Believability | Calculation of trust value for Vytautas Magnus University, Kaunas (RKBExplorer) took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-kaunas took 2.487395763397217s
Availability | SPARQL endpoint availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.025908470153808594s
Availability | VoID file availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.00045490264892578125s
Completeness | Calculation of interlinking completeness for Korean Institute of Science Technology and Information (RKBExplorer) took 0.27144813537597656s
Reputation | Calculation of the PageRank for Korean Institute of Science Technology and Information (RKBExplorer) took 0.021471738815307617s
Interlinking | Calculation of Degree of Connection for Korean Institute of Science Technology and Information (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Korean Institute of Science Technology and Information (RKBExplorer) took 0.00016570091247558594s
Believability | Calculation of trust value for Korean Institute of Science Technology and Information (RKBExplorer) took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-kisti took 2.4980409145355225s
Availability | SPARQL endpoint availability check for LAAS-CNRS (RKBExplorer) took 0.03195381164550781s
Availability | VoID file availability check for LAAS-CNRS (RKBExplorer) took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for LAAS-CNRS (RKBExplorer) took 0.28241515159606934s
Reputation | Calculation of the PageRank for LAAS-CNRS (RKBExplorer) took 0.020395278930664062s
Interlinking | Calculation of Degree of Connection for LAAS-CNRS (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LAAS-CNRS (RKBExplorer) took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for LAAS-CNRS (RKBExplorer) took 0.00014972686767578125s
Believability | Calculation of trust value for LAAS-CNRS (RKBExplorer) took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-laas took 2.5505688190460205s
Availability | SPARQL endpoint availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.02722930908203125s
Availability | VoID file availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.2734489440917969s
Reputation | Calculation of the PageRank for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.020307302474975586s
Interlinking | Calculation of Degree of Connection for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 6.580352783203125e-05s
Believability | Calculation of trust value for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-lisbon took 2.5111236572265625s
Availability | SPARQL endpoint availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.03606605529785156s
Availability | VoID file availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.00041937828063964844s
Completeness | Calculation of interlinking completeness for University of Newcastle upon Tyne (RKBExplorer) took 0.26505422592163086s
Reputation | Calculation of the PageRank for University of Newcastle upon Tyne (RKBExplorer) took 0.02070307731628418s
Interlinking | Calculation of Degree of Connection for University of Newcastle upon Tyne (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for University of Newcastle upon Tyne (RKBExplorer) took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for University of Newcastle upon Tyne (RKBExplorer) took 0.00015497207641601562s
Believability | Calculation of trust value for University of Newcastle upon Tyne (RKBExplorer) took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-newcastle took 2.5880672931671143s
Availability | SPARQL endpoint availability check for notube took 0.02823805809020996s
Availability | VoID file availability check for notube took 0.0004429817199707031s
Completeness | Calculation of interlinking completeness for notube took 0.2689375877380371s
Reputation | Calculation of the PageRank for notube took 0.020171642303466797s
Interlinking | Calculation of Degree of Connection for notube took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for notube took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for notube took 4.0531158447265625e-05s
Believability | Calculation of trust value for notube took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-notube took 2.4707493782043457s
Availability | SPARQL endpoint availability check for National Science Foundation (RKBExplorer) took 0.0380401611328125s
Availability | VoID file availability check for National Science Foundation (RKBExplorer) took 0.0003972053527832031s
Completeness | Calculation of interlinking completeness for National Science Foundation (RKBExplorer) took 0.26636481285095215s
Reputation | Calculation of the PageRank for National Science Foundation (RKBExplorer) took 0.020130634307861328s
Interlinking | Calculation of Degree of Connection for National Science Foundation (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for National Science Foundation (RKBExplorer) took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for National Science Foundation (RKBExplorer) took 0.00012803077697753906s
Believability | Calculation of trust value for National Science Foundation (RKBExplorer) took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-nsf took 2.5510919094085693s
Availability | SPARQL endpoint availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.034223318099975586s
Availability | VoID file availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.00040459632873535156s
Completeness | Calculation of interlinking completeness for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.26537609100341797s
Reputation | Calculation of the PageRank for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.02140021324157715s
Interlinking | Calculation of Degree of Connection for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0009095668792724609s
Interlinking | Calculation of Clustering coefficient for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.00017404556274414062s
Believability | Calculation of trust value for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-oai took 2.577517032623291s
Availability | SPARQL endpoint availability check for Ordnance Survey (RKBExplorer) took 0.028822898864746094s
Availability | VoID file availability check for Ordnance Survey (RKBExplorer) took 0.0003714561462402344s
Completeness | Calculation of interlinking completeness for Ordnance Survey (RKBExplorer) took 0.26204514503479004s
Reputation | Calculation of the PageRank for Ordnance Survey (RKBExplorer) took 0.02095484733581543s
Interlinking | Calculation of Degree of Connection for Ordnance Survey (RKBExplorer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Ordnance Survey (RKBExplorer) took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey (RKBExplorer) took 7.987022399902344e-05s
Believability | Calculation of trust value for Ordnance Survey (RKBExplorer) took 1.0967254638671875e-05s
INFO | --- Analysis for rkb-explorer-os took 2.5235965251922607s
Availability | SPARQL endpoint availability check for photos took 0.02490687370300293s
Availability | VoID file availability check for photos took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for photos took 0.2646157741546631s
Reputation | Calculation of the PageRank for photos took 0.020310401916503906s
Interlinking | Calculation of Degree of Connection for photos took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for photos took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for photos took 6.961822509765625e-05s
Believability | Calculation of trust value for photos took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-photos took 2.468395233154297s
Availability | SPARQL endpoint availability check for Università di Pisa (RKBExplorer) took 0.02735733985900879s
Availability | VoID file availability check for Università di Pisa (RKBExplorer) took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for Università di Pisa (RKBExplorer) took 0.26317358016967773s
Reputation | Calculation of the PageRank for Università di Pisa (RKBExplorer) took 0.020165205001831055s
Interlinking | Calculation of Degree of Connection for Università di Pisa (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Università di Pisa (RKBExplorer) took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Università di Pisa (RKBExplorer) took 0.0001163482666015625s
Believability | Calculation of trust value for Università di Pisa (RKBExplorer) took 6.4373016357421875e-06s
INFO | --- Analysis for rkb-explorer-pisa took 2.4549214839935303s
Availability | SPARQL endpoint availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.026518583297729492s
Availability | VoID file availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for Research Assessment Exercise 2001 (RKBExplorer) took 0.26047563552856445s
Reputation | Calculation of the PageRank for Research Assessment Exercise 2001 (RKBExplorer) took 0.020131349563598633s
Interlinking | Calculation of Degree of Connection for Research Assessment Exercise 2001 (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Research Assessment Exercise 2001 (RKBExplorer) took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Research Assessment Exercise 2001 (RKBExplorer) took 0.00019049644470214844s
Believability | Calculation of trust value for Research Assessment Exercise 2001 (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-rae2001 took 2.4582839012145996s
Availability | SPARQL endpoint availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.041177988052368164s
Availability | VoID file availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.26601314544677734s
Reputation | Calculation of the PageRank for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.02008652687072754s
Interlinking | Calculation of Degree of Connection for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.00013685226440429688s
Believability | Calculation of trust value for ReSIST Resilience Mechanisms (RKBExplorer.com) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-resex took 2.502178907394409s
Availability | SPARQL endpoint availability check for RISKS Digest (RKBExplorer) took 0.027615070343017578s
Availability | VoID file availability check for RISKS Digest (RKBExplorer) took 0.0004532337188720703s
Completeness | Calculation of interlinking completeness for RISKS Digest (RKBExplorer) took 0.26836204528808594s
Reputation | Calculation of the PageRank for RISKS Digest (RKBExplorer) took 0.020344257354736328s
Interlinking | Calculation of Degree of Connection for RISKS Digest (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for RISKS Digest (RKBExplorer) took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for RISKS Digest (RKBExplorer) took 9.179115295410156e-05s
Believability | Calculation of trust value for RISKS Digest (RKBExplorer) took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-risks took 2.4932003021240234s
Availability | SPARQL endpoint availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.02872753143310547s
Availability | VoID file availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.27506113052368164s
Reputation | Calculation of the PageRank for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.02129530906677246s
Interlinking | Calculation of Degree of Connection for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0001323223114013672s
Believability | Calculation of trust value for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-roma took 2.505436658859253s
Availability | SPARQL endpoint availability check for roni took 0.03474617004394531s
Availability | VoID file availability check for roni took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for roni took 0.2824695110321045s
Reputation | Calculation of the PageRank for roni took 0.020705223083496094s
Interlinking | Calculation of Degree of Connection for roni took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for roni took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for roni took 3.647804260253906e-05s
Believability | Calculation of trust value for roni took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-roni took 2.7248194217681885s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.04007387161254883s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0004360675811767578s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.2784543037414551s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.020351171493530273s
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.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.00021839141845703125s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 9.5367431640625e-06s
INFO | --- Analysis for rkb-explorer-southampton took 2.611372232437134s
Availability | SPARQL endpoint availability check for Universität Ulm (RKBExplorer) took 0.0275881290435791s
Availability | VoID file availability check for Universität Ulm (RKBExplorer) took 0.0004105567932128906s
Completeness | Calculation of interlinking completeness for Universität Ulm (RKBExplorer) took 0.2632269859313965s
Reputation | Calculation of the PageRank for Universität Ulm (RKBExplorer) took 0.02040839195251465s
Interlinking | Calculation of Degree of Connection for Universität Ulm (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universität Ulm (RKBExplorer) took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Universität Ulm (RKBExplorer) took 0.00011086463928222656s
Believability | Calculation of trust value for Universität Ulm (RKBExplorer) took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-ulm took 2.5109097957611084s
Availability | SPARQL endpoint availability check for UN/LOCODE (RKBExplorer) took 0.027393817901611328s
Availability | VoID file availability check for UN/LOCODE (RKBExplorer) took 0.00043010711669921875s
Completeness | Calculation of interlinking completeness for UN/LOCODE (RKBExplorer) took 0.2648434638977051s
Reputation | Calculation of the PageRank for UN/LOCODE (RKBExplorer) took 0.020388364791870117s
Interlinking | Calculation of Degree of Connection for UN/LOCODE (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for UN/LOCODE (RKBExplorer) took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for UN/LOCODE (RKBExplorer) took 0.00010466575622558594s
Believability | Calculation of trust value for UN/LOCODE (RKBExplorer) took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-unlocode took 2.4949185848236084s
Availability | SPARQL endpoint availability check for webconf took 0.027860641479492188s
Availability | VoID file availability check for webconf took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for webconf took 0.26476144790649414s
Reputation | Calculation of the PageRank for webconf took 0.02036571502685547s
Interlinking | Calculation of Degree of Connection for webconf took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for webconf took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for webconf took 0.00010514259338378906s
Believability | Calculation of trust value for webconf took 1.0967254638671875e-05s
INFO | --- Analysis for rkb-explorer-webconf took 12.904483079910278s
Availability | SPARQL endpoint availability check for Web Science Conference (RKBExplorer) took 0.028469562530517578s
Availability | VoID file availability check for Web Science Conference (RKBExplorer) took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for Web Science Conference (RKBExplorer) took 0.2756373882293701s
Reputation | Calculation of the PageRank for Web Science Conference (RKBExplorer) took 0.02092146873474121s
Interlinking | Calculation of Degree of Connection for Web Science Conference (RKBExplorer) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Web Science Conference (RKBExplorer) took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Web Science Conference (RKBExplorer) took 7.224082946777344e-05s
Believability | Calculation of trust value for Web Science Conference (RKBExplorer) took 1.5020370483398438e-05s
INFO | --- Analysis for rkb-explorer-webscience took 2.6116702556610107s
Availability | SPARQL endpoint availability check for ReSIST Project Wiki (RKBExplorer) took 0.027935504913330078s
Availability | VoID file availability check for ReSIST Project Wiki (RKBExplorer) took 0.0006010532379150391s
Completeness | Calculation of interlinking completeness for ReSIST Project Wiki (RKBExplorer) took 0.27657198905944824s
Reputation | Calculation of the PageRank for ReSIST Project Wiki (RKBExplorer) took 0.02033257484436035s
Interlinking | Calculation of Degree of Connection for ReSIST Project Wiki (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ReSIST Project Wiki (RKBExplorer) took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for ReSIST Project Wiki (RKBExplorer) took 0.00020623207092285156s
Believability | Calculation of trust value for ReSIST Project Wiki (RKBExplorer) took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-wiki took 2.558309316635132s
Availability | SPARQL endpoint availability check for WordNet (RKBExplorer) took 0.036020517349243164s
Availability | VoID file availability check for WordNet (RKBExplorer) took 0.0004260540008544922s
Completeness | Calculation of interlinking completeness for WordNet (RKBExplorer) took 0.5511891841888428s
Reputation | Calculation of the PageRank for WordNet (RKBExplorer) took 0.020692825317382812s
Interlinking | Calculation of Degree of Connection for WordNet (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for WordNet (RKBExplorer) took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for WordNet (RKBExplorer) took 9.417533874511719e-05s
Believability | Calculation of trust value for WordNet (RKBExplorer) took 5.245208740234375e-06s
INFO | --- Analysis for rkb-explorer-wordnet took 2.754951000213623s
Availability | SPARQL endpoint availability check for ROCEEH Out of Africa Database (ROAD) took 0.5255923271179199s
Availability | VoID file availability check for ROCEEH Out of Africa Database (ROAD) took 0.0004956722259521484s
Extra | Recovery of all triples for ROCEEH Out of Africa Database (ROAD) took 45.84742617607117s
Performance | Total latancy measurement for ROCEEH Out of Africa Database (ROAD) took 0.40152454376220703s
Amount of data | Number of triples check for ROCEEH Out of Africa Database (ROAD) took 1.5620715618133545s
Interoperability | New terms check for ROCEEH Out of Africa Database (ROAD) took 1.5552318096160889s
Versatility | Languages check for ROCEEH Out of Africa Database (ROAD) took 4.666588306427002s
Interpretability | Number of blank nodes check for ROCEEH Out of Africa Database (ROAD) took 1.2663273811340332s
Interpretability | RDF structures check for ROCEEH Out of Africa Database (ROAD) took 0.08307027816772461s
Versatility | Serialization formats check for ROCEEH Out of Africa Database (ROAD) took 0.09093856811523438s
Availability | RDF dump link check for ROCEEH Out of Africa Database (ROAD) took 0.09237384796142578s
License | MR license check for ROCEEH Out of Africa Database (ROAD) took 0.08132147789001465s
License | HR license check for ROCEEH Out of Africa Database (ROAD) took 0.09741544723510742s
Amount of data | Number of property check for ROCEEH Out of Africa Database (ROAD) took 0.07827186584472656s
Understandability | Number of label check for ROCEEH Out of Africa Database (ROAD) took 0.10917305946350098s
Understandability | URI regex check for ROCEEH Out of Africa Database (ROAD) took 0.17807865142822266s
Understandability | Vocabs check for ROCEEH Out of Africa Database (ROAD) took 0.08218884468078613s
Verifiability | Authors check for ROCEEH Out of Africa Database (ROAD) took 0.0975649356842041s
Verifiability | Publishers check for ROCEEH Out of Africa Database (ROAD) took 0.0835258960723877s
Performance | Throughput check for ROCEEH Out of Africa Database (ROAD) took 10.26801061630249s
Amount of data | Check the number of entities for ROCEEH Out of Africa Database (ROAD) took 0.00012087821960449219s
Verifiability | Contribs. check for ROCEEH Out of Africa Database (ROAD) took 0.08145403861999512s
Interlinking | sameAs chians check for ROCEEH Out of Africa Database (ROAD) took 0.08168411254882812s
Interlinking | skos check for ROCEEH Out of Africa Database (ROAD) took 0.08132290840148926s
Interlinking | skos check for ROCEEH Out of Africa Database (ROAD) took 0.08142280578613281s
Timeliness | dataset update frequency check for ROCEEH Out of Africa Database (ROAD) took 0.08196020126342773s
Currency | Creation date check for ROCEEH Out of Africa Database (ROAD) took 0.15920209884643555s
Currency | Modification date check for ROCEEH Out of Africa Database (ROAD) took 0.16326355934143066s
Rep.Conc. | URIs length for ROCEEH Out of Africa Database (ROAD) took 28.565634727478027s
Interoperability | New vocabularies check for ROCEEH Out of Africa Database (ROAD) took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for ROCEEH Out of Africa Database (ROAD) took 0.08129143714904785s
Accuracy | Check Functional Property for ROCEEH Out of Africa Database (ROAD) took 0.07781791687011719s
Accuracy | Check Inverse Functional Property for ROCEEH Out of Africa Database (ROAD) took 0.07644796371459961s
Accuracy | Check Datatype consistency for ROCEEH Out of Africa Database (ROAD) took 3.754087448120117s
Consistency | Disjoint class check for ROCEEH Out of Africa Database (ROAD) took 0.08031606674194336s
Consistency | Check Misplaced properties for ROCEEH Out of Africa Database (ROAD) took 2.8616740703582764s
Consistency | Check Ontology hijacking for ROCEEH Out of Africa Database (ROAD) took 6.166568040847778s
Consistency | Check Invalid usage of undefined classes for ROCEEH Out of Africa Database (ROAD) took 1.3657090663909912s
Consistency | Check Invalid usage of undefined properties for ROCEEH Out of Africa Database (ROAD) took 4.136133432388306s
Conciseness | Check Extensional conciseness for ROCEEH Out of Africa Database (ROAD) took 3.0283281803131104s
Security | Sign check for ROCEEH Out of Africa Database (ROAD) took 0.07810759544372559s
Availability | Check URIs Dereferenciability for ROCEEH Out of Africa Database (ROAD) took 477.5345938205719s
Completeness | Calculation of interlinking completeness for ROCEEH Out of Africa Database (ROAD) took 0.34378814697265625s
Reputation | Calculation of the PageRank for ROCEEH Out of Africa Database (ROAD) took 0.021385669708251953s
Interlinking | Calculation of Degree of Connection for ROCEEH Out of Africa Database (ROAD) took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for ROCEEH Out of Africa Database (ROAD) took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for ROCEEH Out of Africa Database (ROAD) took 9.417533874511719e-05s
Interoperability | Check the re-using of existing vocabs for ROCEEH Out of Africa Database (ROAD) took 2.1457672119140625e-06s
Believability | Calculation of trust value for ROCEEH Out of Africa Database (ROAD) took 1.3589859008789062e-05s
INFO | --- Analysis for roceeh-road took 613.975576877594s
Availability | SPARQL endpoint availability check for ontology terrorist attack took 9.608268737792969e-05s
Availability | VoID file availability check for ontology terrorist attack took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for ontology terrorist attack took 0.2755458354949951s
Reputation | Calculation of the PageRank for ontology terrorist attack took 0.020447254180908203s
Interlinking | Calculation of Degree of Connection for ontology terrorist attack took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ontology terrorist attack took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for ontology terrorist attack took 3.123283386230469e-05s
Believability | Calculation of trust value for ontology terrorist attack took 1.2636184692382812e-05s
INFO | --- Analysis for ROSHANI took 4.090659856796265s
Availability | SPARQL endpoint availability check for TERRORIST ATTACK ONTOLOGY took 8.630752563476562e-05s
Availability | VoID file availability check for TERRORIST ATTACK ONTOLOGY took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for TERRORIST ATTACK ONTOLOGY took 0.2640242576599121s
Reputation | Calculation of the PageRank for TERRORIST ATTACK ONTOLOGY took 0.02120661735534668s
Interlinking | Calculation of Degree of Connection for TERRORIST ATTACK ONTOLOGY took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for TERRORIST ATTACK ONTOLOGY took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for TERRORIST ATTACK ONTOLOGY took 3.337860107421875e-05s
Believability | Calculation of trust value for TERRORIST ATTACK ONTOLOGY took 1.3113021850585938e-05s
INFO | --- Analysis for ROSHANI_SAHU took 2.4599645137786865s
Availability | SPARQL endpoint availability check for x took 0.00010585784912109375s
Availability | VoID file availability check for x took 0.0005795955657958984s
Completeness | Calculation of interlinking completeness for x took 0.2799949645996094s
Reputation | Calculation of the PageRank for x took 0.020844221115112305s
Interlinking | Calculation of Degree of Connection for x took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for x took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for x took 3.337860107421875e-05s
Believability | Calculation of trust value for x took 8.106231689453125e-06s
INFO | --- Analysis for Rozprawa,_artykuł took 2.477079153060913s
Availability | SPARQL endpoint availability check for RSS-500 NIF NER CORPUS took 4.220008850097656e-05s
Availability | VoID file availability check for RSS-500 NIF NER CORPUS took 0.0005431175231933594s
Completeness | Calculation of interlinking completeness for RSS-500 NIF NER CORPUS took 0.2959561347961426s
Reputation | Calculation of the PageRank for RSS-500 NIF NER CORPUS took 0.020878314971923828s
Interlinking | Calculation of Degree of Connection for RSS-500 NIF NER CORPUS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for RSS-500 NIF NER CORPUS took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for RSS-500 NIF NER CORPUS took 6.556510925292969e-05s
Believability | Calculation of trust value for RSS-500 NIF NER CORPUS took 1.2874603271484375e-05s
INFO | --- Analysis for rss-500-nif-ner-corpus took 3.9342243671417236s
Availability | SPARQL endpoint availability check for Ruben Taelman's Data took 4.267692565917969e-05s
Availability | VoID file availability check for Ruben Taelman's Data took 0.0005576610565185547s
Completeness | Calculation of interlinking completeness for Ruben Taelman's Data took 0.2983119487762451s
Reputation | Calculation of the PageRank for Ruben Taelman's Data took 0.02019500732421875s
Interlinking | Calculation of Degree of Connection for Ruben Taelman's Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ruben Taelman's Data took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Ruben Taelman's Data took 6.890296936035156e-05s
Believability | Calculation of trust value for Ruben Taelman's Data took 1.1920928955078125e-05s
INFO | --- Analysis for rubentaelman took 2.9492156505584717s
Availability | SPARQL endpoint availability check for Ruben Verborgh's data took 5.412101745605469e-05s
Availability | VoID file availability check for Ruben Verborgh's data took 0.0006303787231445312s
Completeness | Calculation of interlinking completeness for Ruben Verborgh's data took 0.2656986713409424s
Reputation | Calculation of the PageRank for Ruben Verborgh's data took 0.02097606658935547s
Interlinking | Calculation of Degree of Connection for Ruben Verborgh's data took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Ruben Verborgh's data took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Ruben Verborgh's data took 8.559226989746094e-05s
Believability | Calculation of trust value for Ruben Verborgh's data took 1.239776611328125e-05s
INFO | --- Analysis for rubenverborgh took 3.1882078647613525s
Availability | SPARQL endpoint availability check for Russian Universities Specialities took 391.8222885131836s
Availability | VoID file availability check for Russian Universities Specialities took 0.0007421970367431641s
Completeness | Calculation of interlinking completeness for Russian Universities Specialities took 0.2700531482696533s
Reputation | Calculation of the PageRank for Russian Universities Specialities took 0.022231340408325195s
Interlinking | Calculation of Degree of Connection for Russian Universities Specialities took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Russian Universities Specialities took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Russian Universities Specialities took 6.604194641113281e-05s
Believability | Calculation of trust value for Russian Universities Specialities took 1.2159347534179688e-05s
INFO | --- Analysis for russian-universities-specialities took 675.0193674564362s
Availability | SPARQL endpoint availability check for SADI Semantic Web Services framework registry took 3.5507452487945557s
Availability | VoID file availability check for SADI Semantic Web Services framework registry took 0.0003173351287841797s
Completeness | Calculation of interlinking completeness for SADI Semantic Web Services framework registry took 0.25846362113952637s
Reputation | Calculation of the PageRank for SADI Semantic Web Services framework registry took 0.029744863510131836s
Interlinking | Calculation of Degree of Connection for SADI Semantic Web Services framework registry took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for SADI Semantic Web Services framework registry took 0.0010485649108886719s
Interlinking | Calculation of Clustering coefficient for SADI Semantic Web Services framework registry took 3.743171691894531e-05s
Believability | Calculation of trust value for SADI Semantic Web Services framework registry took 8.58306884765625e-06s
INFO | --- Analysis for sadi-semantic-web-services-framework-registry took 8.13591980934143s
Availability | SPARQL endpoint availability check for SALDO-RDF took 0.9224655628204346s
Availability | VoID file availability check for SALDO-RDF took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for SALDO-RDF took 0.2982511520385742s
Reputation | Calculation of the PageRank for SALDO-RDF took 0.020962953567504883s
Interlinking | Calculation of Degree of Connection for SALDO-RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SALDO-RDF took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for SALDO-RDF took 3.457069396972656e-05s
Believability | Calculation of trust value for SALDO-RDF took 1.0728836059570312e-05s
INFO | --- Analysis for saldo-rdf took 5.298703908920288s
Availability | SPARQL endpoint availability check for SALDOM-RDF took 0.5956737995147705s
Availability | VoID file availability check for SALDOM-RDF took 0.0006322860717773438s
Completeness | Calculation of interlinking completeness for SALDOM-RDF took 0.2791428565979004s
Reputation | Calculation of the PageRank for SALDOM-RDF took 0.020377635955810547s
Interlinking | Calculation of Degree of Connection for SALDOM-RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SALDOM-RDF took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for SALDOM-RDF took 3.5762786865234375e-05s
Believability | Calculation of trust value for SALDOM-RDF took 5.9604644775390625e-06s
INFO | --- Analysis for saldom-rdf took 4.875659465789795s
Availability | SPARQL endpoint availability check for Salzburgerland DE took 9.202957153320312e-05s
Availability | VoID file availability check for Salzburgerland DE took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for Salzburgerland DE took 0.2883286476135254s
Reputation | Calculation of the PageRank for Salzburgerland DE took 0.022529125213623047s
Interlinking | Calculation of Degree of Connection for Salzburgerland DE took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Salzburgerland DE took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Salzburgerland DE took 0.00010371208190917969s
Believability | Calculation of trust value for Salzburgerland DE took 7.62939453125e-06s
INFO | --- Analysis for salzburgerland-com-de took 3.2929980754852295s
Availability | SPARQL endpoint availability check for Salzburgerland EN took 4.315376281738281e-05s
Availability | VoID file availability check for Salzburgerland EN took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for Salzburgerland EN took 0.27181291580200195s
Reputation | Calculation of the PageRank for Salzburgerland EN took 0.022038698196411133s
Interlinking | Calculation of Degree of Connection for Salzburgerland EN took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Salzburgerland EN took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Salzburgerland EN took 0.00011086463928222656s
Believability | Calculation of trust value for Salzburgerland EN took 1.1205673217773438e-05s
INFO | --- Analysis for salzburgerland-com-en took 2.9032795429229736s
Availability | SPARQL endpoint availability check for Salzburgerland IT took 4.220008850097656e-05s
Availability | VoID file availability check for Salzburgerland IT took 0.0011103153228759766s
Completeness | Calculation of interlinking completeness for Salzburgerland IT took 0.2805778980255127s
Reputation | Calculation of the PageRank for Salzburgerland IT took 0.022477388381958008s
Interlinking | Calculation of Degree of Connection for Salzburgerland IT took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Salzburgerland IT took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Salzburgerland IT took 0.00010132789611816406s
Believability | Calculation of trust value for Salzburgerland IT took 1.1920928955078125e-05s
INFO | --- Analysis for salzburgerland-com-it took 2.9053032398223877s
Availability | SPARQL endpoint availability check for sandrart.net took 8.630752563476562e-05s
Availability | VoID file availability check for sandrart.net took 0.0007092952728271484s
Completeness | Calculation of interlinking completeness for sandrart.net took 0.2781398296356201s
Reputation | Calculation of the PageRank for sandrart.net took 0.020780086517333984s
Interlinking | Calculation of Degree of Connection for sandrart.net took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for sandrart.net took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for sandrart.net took 7.128715515136719e-05s
Believability | Calculation of trust value for sandrart.net took 1.2636184692382812e-05s
INFO | --- Analysis for sandrart-net took 3.514742612838745s
Availability | SPARQL endpoint availability check for Taxons  took 0.1771395206451416s
Availability | VoID file availability check for Taxons  took 0.0004627704620361328s
Extra | Recovery of all triples for Taxons  took 23.752415657043457s
Performance | Total latancy measurement for Taxons  took 0.3867661952972412s
Amount of data | Number of triples check for Taxons  took 2.623732805252075s
Interoperability | New terms check for Taxons  took 1.752230167388916s
Versatility | Languages check for Taxons  took 41.65464973449707s
Interpretability | Number of blank nodes check for Taxons  took 0.9412636756896973s
Security | Check HTTPS for Taxons  took 0.1758582592010498s
Interpretability | RDF structures check for Taxons  took 0.7139174938201904s
Versatility | Serialization formats check for Taxons  took 0.3900282382965088s
Availability | RDF dump link check for Taxons  took 0.22564125061035156s
License | MR license check for Taxons  took 1.4866316318511963s
License | HR license check for Taxons  took 1.9352192878723145s
Amount of data | Number of property check for Taxons  took 0.10238480567932129s
Understandability | Number of label check for Taxons  took 2.4527504444122314s
Understandability | URI regex check for Taxons  took 0.6328079700469971s
Understandability | Vocabs check for Taxons  took 0.18067288398742676s
Verifiability | Authors check for Taxons  took 0.08486056327819824s
Verifiability | Publishers check for Taxons  took 0.07526898384094238s
Performance | Throughput check for Taxons  took 10.499491930007935s
Amount of data | Check the number of entities for Taxons  took 7.271766662597656e-05s
Verifiability | Contribs. check for Taxons  took 0.08560299873352051s
Interlinking | sameAs chians check for Taxons  took 0.17961740493774414s
Interlinking | skos check for Taxons  took 0.14528560638427734s
Interlinking | skos check for Taxons  took 0.09097862243652344s
Timeliness | dataset update frequency check for Taxons  took 0.6922652721405029s
Currency | Creation date check for Taxons  took 0.2010974884033203s
Currency | Modification date check for Taxons  took 0.25163960456848145s
Rep.Conc. | URIs length for Taxons  took 9.401695489883423s
Interoperability | New vocabularies check for Taxons  took 5.9604644775390625e-06s
Consistency | Deprecated classes/propertiers check for Taxons  took 0.09834027290344238s
Accuracy | Check Functional Property for Taxons  took 0.2805519104003906s
Accuracy | Check Inverse Functional Property for Taxons  took 0.2606627941131592s
Accuracy | Check Empty annotation labels for Taxons  took 4.985030174255371s
Accuracy | Check White space in annotation for Taxons  took 0.2999706268310547s
Accuracy | Check Datatype consistency for Taxons  took 0.26122403144836426s
Consistency | Disjoint class check for Taxons  took 0.11081123352050781s
Consistency | Check Misplaced properties for Taxons  took 4.635420799255371s
Consistency | Misplaced classes for Taxons  took 0.9293398857116699s
Consistency | Check Ontology hijacking for Taxons  took 5.55546236038208s
Consistency | Check Invalid usage of undefined classes for Taxons  took 1.2676570415496826s
Consistency | Check Invalid usage of undefined properties for Taxons  took 5.562834978103638s
Conciseness | Check Extensional conciseness for Taxons  took 0.28160548210144043s
Conciseness | Check Intensional conciseness for Taxons  took 0.16790366172790527s
Security | Sign check for Taxons  took 0.7676661014556885s
Availability | Check URIs Dereferenciability for Taxons  took 1853.5585055351257s
Completeness | Calculation of interlinking completeness for Taxons  took 0.7464542388916016s
Reputation | Calculation of the PageRank for Taxons  took 0.021104097366333008s
Interlinking | Calculation of Degree of Connection for Taxons  took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Taxons  took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Taxons  took 8.416175842285156e-05s
Interoperability | Check the re-using of existing vocabs for Taxons  took 4.649162292480469e-05s
Believability | Calculation of trust value for Taxons  took 1.2874603271484375e-05s
INFO | --- Analysis for sandre took 2072.209291934967s
Availability | SPARQL endpoint availability check for Sanskrit English Lexicon took 1.460066795349121s
Availability | VoID file availability check for Sanskrit English Lexicon took 0.0005698204040527344s
Completeness | Calculation of interlinking completeness for Sanskrit English Lexicon took 0.27660131454467773s
Reputation | Calculation of the PageRank for Sanskrit English Lexicon took 0.020738840103149414s
Interlinking | Calculation of Degree of Connection for Sanskrit English Lexicon took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Sanskrit English Lexicon took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Sanskrit English Lexicon took 3.361701965332031e-05s
Believability | Calculation of trust value for Sanskrit English Lexicon took 1.0013580322265625e-05s
INFO | --- Analysis for sanskrit-english-lexicon took 6.598593235015869s
Availability | SPARQL endpoint availability check for Santillana Guide Dataset took 265.2158131599426s
Availability | VoID file availability check for Santillana Guide Dataset took 0.000762939453125s
Completeness | Calculation of interlinking completeness for Santillana Guide Dataset took 0.2676262855529785s
Reputation | Calculation of the PageRank for Santillana Guide Dataset took 0.020994186401367188s
Interlinking | Calculation of Degree of Connection for Santillana Guide Dataset took 6.341934204101562e-05s
Interlinking | Calculation of Centrality for Santillana Guide Dataset took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Santillana Guide Dataset took 4.6253204345703125e-05s
Believability | Calculation of trust value for Santillana Guide Dataset took 1.049041748046875e-05s
INFO | --- Analysis for santillana_guide_dataset took 670.0532140731812s
Availability | SPARQL endpoint availability check for SATAR test  took 9.393692016601562e-05s
Availability | VoID file availability check for SATAR test  took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for SATAR test  took 0.27283740043640137s
Reputation | Calculation of the PageRank for SATAR test  took 0.020444631576538086s
Interlinking | Calculation of Degree of Connection for SATAR test  took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for SATAR test  took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for SATAR test  took 2.8848648071289062e-05s
Believability | Calculation of trust value for SATAR test  took 9.775161743164062e-06s
INFO | --- Analysis for SATAR_test took 4.476355791091919s
Availability | SPARQL endpoint availability check for SCBG Data took 21.518916130065918s
Availability | VoID file availability check for SCBG Data took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for SCBG Data took 0.27007627487182617s
Reputation | Calculation of the PageRank for SCBG Data took 0.020566463470458984s
Interlinking | Calculation of Degree of Connection for SCBG Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SCBG Data took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for SCBG Data took 7.82012939453125e-05s
Believability | Calculation of trust value for SCBG Data took 1.3589859008789062e-05s
INFO | --- Analysis for SCBG-Data took 54.09037208557129s
Availability | SPARQL endpoint availability check for Schemantra took 8.869171142578125e-05s
Availability | VoID file availability check for Schemantra took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for Schemantra took 0.27187657356262207s
Reputation | Calculation of the PageRank for Schemantra took 0.02080535888671875s
Interlinking | Calculation of Degree of Connection for Schemantra took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Schemantra took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Schemantra took 3.0279159545898438e-05s
Believability | Calculation of trust value for Schemantra took 1.1920928955078125e-05s
INFO | --- Analysis for Schemantra took 2.533013343811035s
Availability | SPARQL endpoint availability check for Schemapedia: RDF schema compendium took 1.9382309913635254s
Availability | VoID file availability check for Schemapedia: RDF schema compendium took 0.0002970695495605469s
Completeness | Calculation of interlinking completeness for Schemapedia: RDF schema compendium took 0.2621917724609375s
Reputation | Calculation of the PageRank for Schemapedia: RDF schema compendium took 0.020291805267333984s
Interlinking | Calculation of Degree of Connection for Schemapedia: RDF schema compendium took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Schemapedia: RDF schema compendium took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Schemapedia: RDF schema compendium took 3.600120544433594e-05s
Believability | Calculation of trust value for Schemapedia: RDF schema compendium took 1.2159347534179688e-05s
INFO | --- Analysis for schemapedia took 4.928815841674805s
Availability | SPARQL endpoint availability check for Scholarometer took 8.726119995117188e-05s
Availability | VoID file availability check for Scholarometer took 0.0006153583526611328s
Completeness | Calculation of interlinking completeness for Scholarometer took 0.2770562171936035s
Reputation | Calculation of the PageRank for Scholarometer took 0.021206378936767578s
Interlinking | Calculation of Degree of Connection for Scholarometer took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Scholarometer took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Scholarometer took 8.130073547363281e-05s
Believability | Calculation of trust value for Scholarometer took 1.1682510375976562e-05s
INFO | --- Analysis for scholarometer took 6.993626117706299s
Availability | SPARQL endpoint availability check for The Digital Agenda Scoreboard of the European Commission took 4.38690185546875e-05s
Availability | VoID file availability check for The Digital Agenda Scoreboard of the European Commission took 0.0006222724914550781s
Completeness | Calculation of interlinking completeness for The Digital Agenda Scoreboard of the European Commission took 0.3083617687225342s
Reputation | Calculation of the PageRank for The Digital Agenda Scoreboard of the European Commission took 0.020829200744628906s
Interlinking | Calculation of Degree of Connection for The Digital Agenda Scoreboard of the European Commission took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The Digital Agenda Scoreboard of the European Commission took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for The Digital Agenda Scoreboard of the European Commission took 2.86102294921875e-05s
Believability | Calculation of trust value for The Digital Agenda Scoreboard of the European Commission took 9.5367431640625e-06s
INFO | --- Analysis for scoreboard took 5.450874328613281s
Availability | SPARQL endpoint availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 8.535385131835938e-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.0006422996520996094s
Completeness | Calculation of interlinking completeness for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.27565693855285645s
Reputation | Calculation of the PageRank for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.020200490951538086s
Interlinking | Calculation of Degree of Connection for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 2.9325485229492188e-05s
Believability | Calculation of trust value for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 9.775161743164062e-06s
INFO | --- Analysis for SDDEC took 28.107417106628418s
Availability | SPARQL endpoint availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 8.678436279296875e-05s
Availability | VoID file availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0005507469177246094s
Completeness | Calculation of interlinking completeness for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.2599453926086426s
Reputation | Calculation of the PageRank for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.020719051361083984s
Interlinking | Calculation of Degree of Connection for A Knowledge Organization System for the United Nations Sustainable Development Goals took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for A Knowledge Organization System for the United Nations Sustainable Development Goals took 2.9325485229492188e-05s
Believability | Calculation of trust value for A Knowledge Organization System for the United Nations Sustainable Development Goals took 1.049041748046875e-05s
INFO | --- Analysis for SDG took 3.193169593811035s
Availability | SPARQL endpoint availability check for sears.com took 8.320808410644531e-05s
Availability | VoID file availability check for sears.com took 0.0005576610565185547s
Completeness | Calculation of interlinking completeness for sears.com took 0.2592344284057617s
Reputation | Calculation of the PageRank for sears.com took 0.020982742309570312s
Interlinking | Calculation of Degree of Connection for sears.com took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for sears.com took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for sears.com took 6.461143493652344e-05s
Believability | Calculation of trust value for sears.com took 1.0728836059570312e-05s
INFO | --- Analysis for sears took 5.686873912811279s
Availability | SPARQL endpoint availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.05757260322570801s
Availability | VoID file availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.26209521293640137s
Reputation | Calculation of the PageRank for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0203092098236084s
Interlinking | Calculation of Degree of Connection for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 8.106231689453125e-05s
Believability | Calculation of trust value for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 1.0013580322265625e-05s
INFO | --- Analysis for sec-rdfabout took 2.772500991821289s
Availability | SPARQL endpoint availability check for Source Code Ecosystem Linked Data took 31.73423433303833s
Availability | VoID file availability check for Source Code Ecosystem Linked Data took 0.0007312297821044922s
Completeness | Calculation of interlinking completeness for Source Code Ecosystem Linked Data took 0.28213977813720703s
Reputation | Calculation of the PageRank for Source Code Ecosystem Linked Data took 0.020448923110961914s
Interlinking | Calculation of Degree of Connection for Source Code Ecosystem Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Source Code Ecosystem Linked Data took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Source Code Ecosystem Linked Data took 8.726119995117188e-05s
Believability | Calculation of trust value for Source Code Ecosystem Linked Data took 1.3828277587890625e-05s
INFO | --- Analysis for secold took 167.87150835990906s
Availability | SPARQL endpoint availability check for semanlink took 8.7738037109375e-05s
Availability | VoID file availability check for semanlink took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for semanlink took 0.2651088237762451s
Reputation | Calculation of the PageRank for semanlink took 0.020580530166625977s
Interlinking | Calculation of Degree of Connection for semanlink took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for semanlink took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for semanlink took 0.00014352798461914062s
Believability | Calculation of trust value for semanlink took 1.1920928955078125e-05s
INFO | --- Analysis for semanlink took 3.6812946796417236s
Availability | SPARQL endpoint availability check for Semantic Universe Data took 0.05548882484436035s
Availability | VoID file availability check for Semantic Universe Data took 0.0004260540008544922s
Completeness | Calculation of interlinking completeness for Semantic Universe Data took 0.2676811218261719s
Reputation | Calculation of the PageRank for Semantic Universe Data took 0.022397518157958984s
Interlinking | Calculation of Degree of Connection for Semantic Universe Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Semantic Universe Data took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Semantic Universe Data took 3.0994415283203125e-05s
Believability | Calculation of trust value for Semantic Universe Data took 9.5367431640625e-06s
INFO | --- Analysis for semantic-universe took 2.581507682800293s
Availability | SPARQL endpoint availability check for Semantic Web Dog Food Corpus took 30.218855142593384s
Availability | VoID file availability check for Semantic Web Dog Food Corpus took 0.0006201267242431641s
Completeness | Calculation of interlinking completeness for Semantic Web Dog Food Corpus took 0.3270077705383301s
Reputation | Calculation of the PageRank for Semantic Web Dog Food Corpus took 0.020575523376464844s
Interlinking | Calculation of Degree of Connection for Semantic Web Dog Food Corpus took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Semantic Web Dog Food Corpus took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Semantic Web Dog Food Corpus took 0.00012135505676269531s
Believability | Calculation of trust value for Semantic Web Dog Food Corpus took 1.0251998901367188e-05s
INFO | --- Analysis for semantic-web-dog-food took 82.95099925994873s
Availability | SPARQL endpoint availability check for semantic-web-grundlagen took 4.506111145019531e-05s
Availability | VoID file availability check for semantic-web-grundlagen took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for semantic-web-grundlagen took 0.27016711235046387s
Reputation | Calculation of the PageRank for semantic-web-grundlagen took 0.020845651626586914s
Interlinking | Calculation of Degree of Connection for semantic-web-grundlagen took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for semantic-web-grundlagen took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for semantic-web-grundlagen took 4.673004150390625e-05s
Believability | Calculation of trust value for semantic-web-grundlagen took 1.0251998901367188e-05s
INFO | --- Analysis for semantic-web-grundlagen took 2.9869911670684814s
Availability | SPARQL endpoint availability check for Semantic XBRL Financial Data took 8.916854858398438e-05s
Availability | VoID file availability check for Semantic XBRL Financial Data took 0.0005514621734619141s
Completeness | Calculation of interlinking completeness for Semantic XBRL Financial Data took 0.2635626792907715s
Reputation | Calculation of the PageRank for Semantic XBRL Financial Data took 0.020426034927368164s
Interlinking | Calculation of Degree of Connection for Semantic XBRL Financial Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Semantic XBRL Financial Data took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Semantic XBRL Financial Data took 8.511543273925781e-05s
Believability | Calculation of trust value for Semantic XBRL Financial Data took 8.106231689453125e-06s
INFO | --- Analysis for semantic-xbrl took 3.2922003269195557s
Availability | SPARQL endpoint availability check for Semantic Quran took 6.918938398361206s
Availability | VoID file availability check for Semantic Quran took 0.0004508495330810547s
Completeness | Calculation of interlinking completeness for Semantic Quran took 0.2659878730773926s
Reputation | Calculation of the PageRank for Semantic Quran took 0.02042984962463379s
Interlinking | Calculation of Degree of Connection for Semantic Quran took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Semantic Quran took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Semantic Quran took 6.985664367675781e-05s
Believability | Calculation of trust value for Semantic Quran took 1.0013580322265625e-05s
INFO | --- Analysis for semanticquran took 16.14127230644226s
Availability | SPARQL endpoint availability check for SemanticTweet took 4.315376281738281e-05s
Availability | VoID file availability check for SemanticTweet took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for SemanticTweet took 0.26725125312805176s
Reputation | Calculation of the PageRank for SemanticTweet took 0.02046036720275879s
Interlinking | Calculation of Degree of Connection for SemanticTweet took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SemanticTweet took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for SemanticTweet took 6.151199340820312e-05s
Believability | Calculation of trust value for SemanticTweet took 1.2159347534179688e-05s
INFO | --- Analysis for semantictweet took 2.561694622039795s
Availability | SPARQL endpoint availability check for semanticweb.org took 4.315376281738281e-05s
Availability | VoID file availability check for semanticweb.org took 0.0006759166717529297s
Completeness | Calculation of interlinking completeness for semanticweb.org took 0.2721552848815918s
Reputation | Calculation of the PageRank for semanticweb.org took 0.02112126350402832s
Interlinking | Calculation of Degree of Connection for semanticweb.org took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for semanticweb.org took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for semanticweb.org took 8.58306884765625e-05s
Believability | Calculation of trust value for semanticweb.org took 1.049041748046875e-05s
INFO | --- Analysis for semanticweb-org took 22.80243706703186s
Availability | SPARQL endpoint availability check for Semantic CrunchBase took 0.05961322784423828s
Availability | VoID file availability check for Semantic CrunchBase took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for Semantic CrunchBase took 0.2653381824493408s
Reputation | Calculation of the PageRank for Semantic CrunchBase took 0.020953655242919922s
Interlinking | Calculation of Degree of Connection for Semantic CrunchBase took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Semantic CrunchBase took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Semantic CrunchBase took 6.937980651855469e-05s
Believability | Calculation of trust value for Semantic CrunchBase took 9.775161743164062e-06s
INFO | --- Analysis for semsol-crunchbase took 2.512911796569824s
Availability | SPARQL endpoint availability check for SentimentWortschatz took 0.25330018997192383s
Availability | VoID file availability check for SentimentWortschatz took 0.0006577968597412109s
Completeness | Calculation of interlinking completeness for SentimentWortschatz took 0.26352858543395996s
Reputation | Calculation of the PageRank for SentimentWortschatz took 0.020635366439819336s
Interlinking | Calculation of Degree of Connection for SentimentWortschatz took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for SentimentWortschatz took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for SentimentWortschatz took 4.172325134277344e-05s
Believability | Calculation of trust value for SentimentWortschatz took 1.0013580322265625e-05s
INFO | --- Analysis for sentiws took 14.383479118347168s
Availability | SPARQL endpoint availability check for seoul-bike-data took 30.082021474838257s
Availability | VoID file availability check for seoul-bike-data took 0.0006551742553710938s
Completeness | Calculation of interlinking completeness for seoul-bike-data took 0.28477001190185547s
Reputation | Calculation of the PageRank for seoul-bike-data took 0.022341012954711914s
Interlinking | Calculation of Degree of Connection for seoul-bike-data took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for seoul-bike-data took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for seoul-bike-data took 3.600120544433594e-05s
Believability | Calculation of trust value for seoul-bike-data took 1.0013580322265625e-05s
INFO | --- Analysis for seoul-bike-data took 72.724116563797s
Availability | SPARQL endpoint availability check for Serendipity took 16.269964933395386s
Availability | VoID file availability check for Serendipity took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for Serendipity took 0.27216625213623047s
Reputation | Calculation of the PageRank for Serendipity took 0.021884918212890625s
Interlinking | Calculation of Degree of Connection for Serendipity took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Serendipity took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Serendipity took 6.961822509765625e-05s
Believability | Calculation of trust value for Serendipity took 1.0728836059570312e-05s
INFO | --- Analysis for serendipity took 23.93948006629944s
Availability | SPARQL endpoint availability check for Sherry Wine Vocabulary took 4.172325134277344e-05s
Availability | VoID file availability check for Sherry Wine Vocabulary took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for Sherry Wine Vocabulary took 0.26368260383605957s
Reputation | Calculation of the PageRank for Sherry Wine Vocabulary took 0.02054119110107422s
Interlinking | Calculation of Degree of Connection for Sherry Wine Vocabulary took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Sherry Wine Vocabulary took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Sherry Wine Vocabulary took 3.1948089599609375e-05s
Believability | Calculation of trust value for Sherry Wine Vocabulary took 1.049041748046875e-05s
INFO | --- Analysis for Sherry_Wine took 2.5648434162139893s
Availability | SPARQL endpoint availability check for Sherry Wine took 8.606910705566406e-05s
Availability | VoID file availability check for Sherry Wine took 0.0004620552062988281s
Completeness | Calculation of interlinking completeness for Sherry Wine took 0.26973462104797363s
Reputation | Calculation of the PageRank for Sherry Wine took 0.020441055297851562s
Interlinking | Calculation of Degree of Connection for Sherry Wine took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Sherry Wine took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Sherry Wine took 3.647804260253906e-05s
Believability | Calculation of trust value for Sherry Wine took 9.775161743164062e-06s
INFO | --- Analysis for Sherry_Wine_ took 2.4364519119262695s
Availability | SPARQL endpoint availability check for Shoah victims? names took 0.1598982810974121s
Availability | VoID file availability check for Shoah victims? names took 0.6449120044708252s
Extra | Recovery of all triples for Shoah victims? names took 1.7763891220092773s
Performance | Total latancy measurement for Shoah victims? names took 0.46019601821899414s
Amount of data | Number of triples check for Shoah victims? names took 1.4079737663269043s
Interoperability | New terms check for Shoah victims? names took 1.6248552799224854s
Versatility | Languages check for Shoah victims? names took 20.42443585395813s
Interpretability | Number of blank nodes check for Shoah victims? names took 1.9032573699951172s
Security | Check HTTPS for Shoah victims? names took 0.14131879806518555s
Interpretability | RDF structures check for Shoah victims? names took 0.3218667507171631s
Versatility | Serialization formats check for Shoah victims? names took 0.31728386878967285s
Availability | RDF dump link check for Shoah victims? names took 0.1293952465057373s
License | MR license check for Shoah victims? names took 0.24023795127868652s
License | HR license check for Shoah victims? names took 7.315648794174194s
Amount of data | Number of property check for Shoah victims? names took 0.25072646141052246s
Understandability | Number of label check for Shoah victims? names took 0.7503764629364014s
Understandability | URI regex check for Shoah victims? names took 0.2911970615386963s
Understandability | Vocabs check for Shoah victims? names took 0.14268827438354492s
Verifiability | Authors check for Shoah victims? names took 0.1423320770263672s
Verifiability | Publishers check for Shoah victims? names took 0.11899328231811523s
Performance | Throughput check for Shoah victims? names took 10.568934679031372s
Amount of data | Check the number of entities for Shoah victims? names took 6.842613220214844e-05s
Verifiability | Contribs. check for Shoah victims? names took 0.05301618576049805s
Interlinking | sameAs chians check for Shoah victims? names took 0.12564325332641602s
Interlinking | skos check for Shoah victims? names took 0.2626838684082031s
Interlinking | skos check for Shoah victims? names took 0.05843162536621094s
Timeliness | dataset update frequency check for Shoah victims? names took 0.29654788970947266s
Currency | Creation date check for Shoah victims? names took 0.14388370513916016s
Currency | Modification date check for Shoah victims? names took 0.14483070373535156s
Rep.Conc. | URIs length for Shoah victims? names took 2.6355321407318115s
Interoperability | New vocabularies check for Shoah victims? names took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Shoah victims? names took 0.07729506492614746s
Accuracy | Check Functional Property for Shoah victims? names took 0.11285161972045898s
Accuracy | Check Inverse Functional Property for Shoah victims? names took 0.07517361640930176s
Accuracy | Check Empty annotation labels for Shoah victims? names took 0.4713099002838135s
Accuracy | Check White space in annotation for Shoah victims? names took 0.02804398536682129s
Accuracy | Check Datatype consistency for Shoah victims? names took 0.02837371826171875s
Consistency | Disjoint class check for Shoah victims? names took 0.3520822525024414s
Consistency | Check Misplaced properties for Shoah victims? names took 2.182497262954712s
Consistency | Misplaced classes for Shoah victims? names took 0.17520451545715332s
Consistency | Check Ontology hijacking for Shoah victims? names took 1.566490650177002s
Consistency | Check Invalid usage of undefined classes for Shoah victims? names took 1.2422170639038086s
Consistency | Check Invalid usage of undefined properties for Shoah victims? names took 3.129734992980957s
Conciseness | Check Extensional conciseness for Shoah victims? names took 0.03325653076171875s
Conciseness | Check Intensional conciseness for Shoah victims? names took 0.13186001777648926s
Security | Sign check for Shoah victims? names took 0.6319999694824219s
Availability | Check URIs Dereferenciability for Shoah victims? names took 995.0462534427643s
Completeness | Calculation of interlinking completeness for Shoah victims? names took 0.4188046455383301s
Reputation | Calculation of the PageRank for Shoah victims? names took 0.02395772933959961s
Interlinking | Calculation of Degree of Connection for Shoah victims? names took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Shoah victims? names took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Shoah victims? names took 9.775161743164062e-05s
Interoperability | Check the re-using of existing vocabs for Shoah victims? names took 2.1457672119140625e-06s
Believability | Calculation of trust value for Shoah victims? names took 6.9141387939453125e-06s
INFO | --- Analysis for shoah-victims-names took 1109.5894584655762s
Availability | SPARQL endpoint availability check for Person took 9.489059448242188e-05s
Availability | VoID file availability check for Person took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for Person took 0.26348233222961426s
Reputation | Calculation of the PageRank for Person took 0.02058553695678711s
Interlinking | Calculation of Degree of Connection for Person took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Person took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Person took 3.147125244140625e-05s
Believability | Calculation of trust value for Person took 1.33514404296875e-05s
INFO | --- Analysis for Shripriya_Dubey took 2.421391248703003s
Availability | SPARQL endpoint availability check for Jishnu Raghavan (1976-2016) took 8.273124694824219e-05s
Availability | VoID file availability check for Jishnu Raghavan (1976-2016) took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for Jishnu Raghavan (1976-2016) took 0.2688252925872803s
Reputation | Calculation of the PageRank for Jishnu Raghavan (1976-2016) took 0.021613121032714844s
Interlinking | Calculation of Degree of Connection for Jishnu Raghavan (1976-2016) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Jishnu Raghavan (1976-2016) took 0.0006883144378662109s
Interlinking | Calculation of Clustering coefficient for Jishnu Raghavan (1976-2016) took 3.0994415283203125e-05s
Believability | Calculation of trust value for Jishnu Raghavan (1976-2016) took 1.1682510375976562e-05s
INFO | --- Analysis for Shutterstock took 2.4573216438293457s
Availability | SPARQL endpoint availability check for SIMPLE took 4.315376281738281e-05s
Availability | VoID file availability check for SIMPLE took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for SIMPLE took 0.2728900909423828s
Reputation | Calculation of the PageRank for SIMPLE took 0.020599365234375s
Interlinking | Calculation of Degree of Connection for SIMPLE took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for SIMPLE took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for SIMPLE took 4.029273986816406e-05s
Believability | Calculation of trust value for SIMPLE took 1.0251998901367188e-05s
INFO | --- Analysis for simple took 7.856914043426514s
Availability | SPARQL endpoint availability check for SITC-V4 took 25.62757706642151s
Availability | VoID file availability check for SITC-V4 took 0.0009057521820068359s
Completeness | Calculation of interlinking completeness for SITC-V4 took 0.2799389362335205s
Reputation | Calculation of the PageRank for SITC-V4 took 0.021067380905151367s
Interlinking | Calculation of Degree of Connection for SITC-V4 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for SITC-V4 took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for SITC-V4 took 5.221366882324219e-05s
Believability | Calculation of trust value for SITC-V4 took 1.0013580322265625e-05s
INFO | --- Analysis for sitc-v4 took 124.35148310661316s
Availability | SPARQL endpoint availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 4.506111145019531e-05s
Availability | VoID file availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0007004737854003906s
Completeness | Calculation of interlinking completeness for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.27205657958984375s
Reputation | Calculation of the PageRank for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.022456884384155273s
Interlinking | Calculation of Degree of Connection for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 4.363059997558594e-05s
Believability | Calculation of trust value for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 1.0728836059570312e-05s
INFO | --- Analysis for sli_galnet_rdf took 12.55658507347107s
Availability | SPARQL endpoint availability check for Slideshare2RDF Server took 8.7738037109375e-05s
Availability | VoID file availability check for Slideshare2RDF Server took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for Slideshare2RDF Server took 0.26572465896606445s
Reputation | Calculation of the PageRank for Slideshare2RDF Server took 0.02067112922668457s
Interlinking | Calculation of Degree of Connection for Slideshare2RDF Server took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Slideshare2RDF Server took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Slideshare2RDF Server took 3.719329833984375e-05s
Believability | Calculation of trust value for Slideshare2RDF Server took 1.33514404296875e-05s
INFO | --- Analysis for slideshare2rdf took 2.52832293510437s
Availability | SPARQL endpoint availability check for Linked Stage Graph took 0.3835747241973877s
Availability | VoID file availability check for Linked Stage Graph took 0.0005059242248535156s
Extra | Recovery of all triples for Linked Stage Graph took 1.8408772945404053s
Performance | Total latancy measurement for Linked Stage Graph took 0.968355655670166s
Amount of data | Number of triples check for Linked Stage Graph took 0.2050786018371582s
Interoperability | New terms check for Linked Stage Graph took 1.575622797012329s
Versatility | Languages check for Linked Stage Graph took 0.68045973777771s
Interpretability | Number of blank nodes check for Linked Stage Graph took 0.22515583038330078s
Security | Check HTTPS for Linked Stage Graph took 0.1246955394744873s
Interpretability | RDF structures check for Linked Stage Graph took 0.2010490894317627s
Versatility | Serialization formats check for Linked Stage Graph took 0.20007681846618652s
Availability | RDF dump link check for Linked Stage Graph took 0.19276881217956543s
License | MR license check for Linked Stage Graph took 0.3065965175628662s
License | HR license check for Linked Stage Graph took 1.8388645648956299s
Amount of data | Number of property check for Linked Stage Graph took 0.1976475715637207s
Understandability | Number of label check for Linked Stage Graph took 0.45069360733032227s
Understandability | URI regex check for Linked Stage Graph took 0.3861358165740967s
Understandability | Vocabs check for Linked Stage Graph took 0.26821374893188477s
Verifiability | Authors check for Linked Stage Graph took 0.21407651901245117s
Verifiability | Publishers check for Linked Stage Graph took 0.20862460136413574s
Performance | Throughput check for Linked Stage Graph took 11.686920166015625s
Amount of data | Check the number of entities for Linked Stage Graph took 6.890296936035156e-05s
Verifiability | Contribs. check for Linked Stage Graph took 0.19818592071533203s
Interlinking | sameAs chians check for Linked Stage Graph took 0.19534778594970703s
Interlinking | skos check for Linked Stage Graph took 0.21082282066345215s
Interlinking | skos check for Linked Stage Graph took 0.19825291633605957s
Timeliness | dataset update frequency check for Linked Stage Graph took 0.2503790855407715s
Currency | Creation date check for Linked Stage Graph took 0.39441895484924316s
Currency | Modification date check for Linked Stage Graph took 0.3938310146331787s
Rep.Conc. | URIs length for Linked Stage Graph took 1.3970139026641846s
Interoperability | New vocabularies check for Linked Stage Graph took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Linked Stage Graph took 0.19365859031677246s
Accuracy | Check Functional Property for Linked Stage Graph took 0.32818174362182617s
Accuracy | Check Inverse Functional Property for Linked Stage Graph took 0.1914217472076416s
Accuracy | Check Empty annotation labels for Linked Stage Graph took 0.7694787979125977s
Accuracy | Check White space in annotation for Linked Stage Graph took 0.023833036422729492s
Accuracy | Check Datatype consistency for Linked Stage Graph took 0.02794623374938965s
Consistency | Disjoint class check for Linked Stage Graph took 0.19460391998291016s
Consistency | Check Misplaced properties for Linked Stage Graph took 0.9000964164733887s
Consistency | Misplaced classes for Linked Stage Graph took 0.5786967277526855s
Consistency | Check Ontology hijacking for Linked Stage Graph took 2.0551180839538574s
Consistency | Check Invalid usage of undefined classes for Linked Stage Graph took 1.2941977977752686s
Consistency | Check Invalid usage of undefined properties for Linked Stage Graph took 1.8153495788574219s
Conciseness | Check Extensional conciseness for Linked Stage Graph took 0.02673816680908203s
Conciseness | Check Intensional conciseness for Linked Stage Graph took 0.5392937660217285s
Security | Sign check for Linked Stage Graph took 0.3105473518371582s
Availability | Check URIs Dereferenciability for Linked Stage Graph took 944.2184724807739s
Completeness | Calculation of interlinking completeness for Linked Stage Graph took 0.42867326736450195s
Reputation | Calculation of the PageRank for Linked Stage Graph took 0.022432804107666016s
Interlinking | Calculation of Degree of Connection for Linked Stage Graph took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Linked Stage Graph took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Linked Stage Graph took 6.532669067382812e-05s
Interoperability | Check the re-using of existing vocabs for Linked Stage Graph took 1.6689300537109375e-06s
Believability | Calculation of trust value for Linked Stage Graph took 8.106231689453125e-06s
INFO | --- Analysis for slod took 1008.7706346511841s
Availability | SPARQL endpoint availability check for Smart Points Of Interest @PSNC took 0.49121856689453125s
Availability | VoID file availability check for Smart Points Of Interest @PSNC took 0.0005040168762207031s
Extra | Recovery of all triples for Smart Points Of Interest @PSNC took 134.4372751712799s
Performance | Total latancy measurement for Smart Points Of Interest @PSNC took 0.8944957256317139s
Amount of data | Number of triples check for Smart Points Of Interest @PSNC took 9.472888708114624s
Interoperability | New terms check for Smart Points Of Interest @PSNC took 14.478055238723755s
Versatility | Languages check for Smart Points Of Interest @PSNC took 300.15868616104126s
Interpretability | Number of blank nodes check for Smart Points Of Interest @PSNC took 2.36660099029541s
Interpretability | RDF structures check for Smart Points Of Interest @PSNC took 0.2916676998138428s
Versatility | Serialization formats check for Smart Points Of Interest @PSNC took 10.025545597076416s
Availability | RDF dump link check for Smart Points Of Interest @PSNC took 0.27591967582702637s
License | MR license check for Smart Points Of Interest @PSNC took 0.5881900787353516s
License | HR license check for Smart Points Of Interest @PSNC took 300.1723647117615s
Amount of data | Number of property check for Smart Points Of Interest @PSNC took 0.1871795654296875s
Understandability | Number of label check for Smart Points Of Interest @PSNC took 2.173572063446045s
Understandability | URI regex check for Smart Points Of Interest @PSNC took 0.7903621196746826s
Understandability | Vocabs check for Smart Points Of Interest @PSNC took 0.39719271659851074s
Verifiability | Authors check for Smart Points Of Interest @PSNC took 0.18332910537719727s
Verifiability | Publishers check for Smart Points Of Interest @PSNC took 0.23170709609985352s
Performance | Throughput check for Smart Points Of Interest @PSNC took 10.693466186523438s
Amount of data | Check the number of entities for Smart Points Of Interest @PSNC took 0.0001049041748046875s
Verifiability | Contribs. check for Smart Points Of Interest @PSNC took 0.18210577964782715s
Interlinking | sameAs chians check for Smart Points Of Interest @PSNC took 0.18303704261779785s
Interlinking | skos check for Smart Points Of Interest @PSNC took 0.45590853691101074s
Interlinking | skos check for Smart Points Of Interest @PSNC took 0.3825688362121582s
Timeliness | dataset update frequency check for Smart Points Of Interest @PSNC took 6.7718119621276855s
Currency | Creation date check for Smart Points Of Interest @PSNC took 0.42388319969177246s
Currency | Modification date check for Smart Points Of Interest @PSNC took 0.22834515571594238s
Rep.Conc. | URIs length for Smart Points Of Interest @PSNC took 165.93637084960938s
Interoperability | New vocabularies check for Smart Points Of Interest @PSNC took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Smart Points Of Interest @PSNC took 0.1777052879333496s
Accuracy | Check Functional Property for Smart Points Of Interest @PSNC took 0.3713505268096924s
Accuracy | Check Inverse Functional Property for Smart Points Of Interest @PSNC took 0.3863539695739746s
Accuracy | Check Empty annotation labels for Smart Points Of Interest @PSNC took 45.54558825492859s
Accuracy | Check White space in annotation for Smart Points Of Interest @PSNC took 2.652414321899414s
Accuracy | Check Datatype consistency for Smart Points Of Interest @PSNC took 2.5477139949798584s
Consistency | Disjoint class check for Smart Points Of Interest @PSNC took 0.17530035972595215s
Consistency | Check Misplaced properties for Smart Points Of Interest @PSNC took 87.74020028114319s
Consistency | Misplaced classes for Smart Points Of Interest @PSNC took 8.273560285568237s
Consistency | Check Ontology hijacking for Smart Points Of Interest @PSNC took 37.267737865448s
Consistency | Check Invalid usage of undefined classes for Smart Points Of Interest @PSNC took 1.3855648040771484s
Consistency | Check Invalid usage of undefined properties for Smart Points Of Interest @PSNC took 88.37653064727783s
Conciseness | Check Extensional conciseness for Smart Points Of Interest @PSNC took 2.7544162273406982s
Conciseness | Check Intensional conciseness for Smart Points Of Interest @PSNC took 0.5573160648345947s
Security | Sign check for Smart Points Of Interest @PSNC took 0.9274592399597168s
Availability | Check URIs Dereferenciability for Smart Points Of Interest @PSNC took 10.818179368972778s
Completeness | Calculation of interlinking completeness for Smart Points Of Interest @PSNC took 0.6921157836914062s
Reputation | Calculation of the PageRank for Smart Points Of Interest @PSNC took 0.02070140838623047s
Interlinking | Calculation of Degree of Connection for Smart Points Of Interest @PSNC took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Smart Points Of Interest @PSNC took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Smart Points Of Interest @PSNC took 0.00010585784912109375s
Interoperability | Check the re-using of existing vocabs for Smart Points Of Interest @PSNC took 4.76837158203125e-06s
Believability | Calculation of trust value for Smart Points Of Interest @PSNC took 1.1682510375976562e-05s
INFO | --- Analysis for Smart_POI_dataset took 2344.9531559944153s
Availability | SPARQL endpoint availability check for SmartLink: Linked Services Non-Functional Properties took 4.846484661102295s
Availability | VoID file availability check for SmartLink: Linked Services Non-Functional Properties took 0.0006692409515380859s
Completeness | Calculation of interlinking completeness for SmartLink: Linked Services Non-Functional Properties took 0.26230859756469727s
Reputation | Calculation of the PageRank for SmartLink: Linked Services Non-Functional Properties took 0.022541522979736328s
Interlinking | Calculation of Degree of Connection for SmartLink: Linked Services Non-Functional Properties took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SmartLink: Linked Services Non-Functional Properties took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for SmartLink: Linked Services Non-Functional Properties took 4.100799560546875e-05s
Believability | Calculation of trust value for SmartLink: Linked Services Non-Functional Properties took 1.1205673217773438e-05s
INFO | --- Analysis for smartlink took 11.395997524261475s
Availability | SPARQL endpoint availability check for SNIK took 0.39534664154052734s
Availability | VoID file availability check for SNIK took 0.0007228851318359375s
Extra | Recovery of all triples for SNIK took 7.7330193519592285s
Performance | Total latancy measurement for SNIK took 2.5325746536254883s
Amount of data | Number of triples check for SNIK took 0.19247961044311523s
Interoperability | New terms check for SNIK took 1.4539542198181152s
Versatility | Languages check for SNIK took 0.27231359481811523s
Interpretability | Number of blank nodes check for SNIK took 0.19142937660217285s
Interpretability | RDF structures check for SNIK took 0.21729683876037598s
Versatility | Serialization formats check for SNIK took 0.19019365310668945s
Availability | RDF dump link check for SNIK took 0.169219970703125s
License | MR license check for SNIK took 0.19538569450378418s
License | HR license check for SNIK took 0.21939516067504883s
Amount of data | Number of property check for SNIK took 0.1894526481628418s
Understandability | Number of label check for SNIK took 0.21596693992614746s
Understandability | URI regex check for SNIK took 0.37581872940063477s
Understandability | Vocabs check for SNIK took 0.1861591339111328s
Verifiability | Authors check for SNIK took 0.18507909774780273s
Verifiability | Publishers check for SNIK took 0.16927385330200195s
Performance | Throughput check for SNIK took 10.698106527328491s
Amount of data | Check the number of entities for SNIK took 6.794929504394531e-05s
Verifiability | Contribs. check for SNIK took 0.1888594627380371s
Interlinking | sameAs chians check for SNIK took 0.18055367469787598s
Interlinking | skos check for SNIK took 0.1893448829650879s
Interlinking | skos check for SNIK took 0.17584228515625s
Timeliness | dataset update frequency check for SNIK took 0.18736648559570312s
Currency | Creation date check for SNIK took 0.35729193687438965s
Currency | Modification date check for SNIK took 0.3565640449523926s
Rep.Conc. | URIs length for SNIK took 2.10917592048645s
Interoperability | New vocabularies check for SNIK took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for SNIK took 0.18774676322937012s
Accuracy | Check Functional Property for SNIK took 0.16903376579284668s
Accuracy | Check Inverse Functional Property for SNIK took 0.18400335311889648s
Accuracy | Check Empty annotation labels for SNIK took 0.8178088665008545s
Accuracy | Check White space in annotation for SNIK took 0.027211904525756836s
Accuracy | Check Datatype consistency for SNIK took 0.21928191184997559s
Consistency | Disjoint class check for SNIK took 0.18554115295410156s
Consistency | Check Misplaced properties for SNIK took 0.6566638946533203s
Consistency | Misplaced classes for SNIK took 0.6813325881958008s
Consistency | Check Ontology hijacking for SNIK took 1.8372302055358887s
Consistency | Check Invalid usage of undefined classes for SNIK took 1.2723910808563232s
Consistency | Check Invalid usage of undefined properties for SNIK took 1.5160372257232666s
Conciseness | Check Extensional conciseness for SNIK took 0.1589977741241455s
Conciseness | Check Intensional conciseness for SNIK took 0.2986032962799072s
Security | Sign check for SNIK took 0.21405744552612305s
Availability | Check URIs Dereferenciability for SNIK took 1681.3019852638245s
Completeness | Calculation of interlinking completeness for SNIK took 0.45959043502807617s
Reputation | Calculation of the PageRank for SNIK took 0.02362990379333496s
Interlinking | Calculation of Degree of Connection for SNIK took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for SNIK took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for SNIK took 7.987022399902344e-05s
Interoperability | Check the re-using of existing vocabs for SNIK took 1.6689300537109375e-06s
Believability | Calculation of trust value for SNIK took 1.1682510375976562e-05s
INFO | --- Analysis for snik took 1741.70090842247s
Availability | SPARQL endpoint availability check for SocialLink took 0.5815620422363281s
Availability | VoID file availability check for SocialLink took 0.0006537437438964844s
Completeness | Calculation of interlinking completeness for SocialLink took 0.2699100971221924s
Reputation | Calculation of the PageRank for SocialLink took 0.020562410354614258s
Interlinking | Calculation of Degree of Connection for SocialLink took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SocialLink took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for SocialLink took 7.343292236328125e-05s
Believability | Calculation of trust value for SocialLink took 1.2159347534179688e-05s
INFO | --- Analysis for SocialLink took 4.09515118598938s
Availability | SPARQL endpoint availability check for FamilyRelations as SocialRole took 6.389617919921875e-05s
Availability | VoID file availability check for FamilyRelations as SocialRole took 0.0006296634674072266s
Completeness | Calculation of interlinking completeness for FamilyRelations as SocialRole took 0.2885153293609619s
Reputation | Calculation of the PageRank for FamilyRelations as SocialRole took 0.020200014114379883s
Interlinking | Calculation of Degree of Connection for FamilyRelations as SocialRole took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for FamilyRelations as SocialRole took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for FamilyRelations as SocialRole took 2.9325485229492188e-05s
Believability | Calculation of trust value for FamilyRelations as SocialRole took 1.2636184692382812e-05s
INFO | --- Analysis for SocialRoles took 9.424724817276001s
Availability | SPARQL endpoint availability check for Social Semantic Web Thesaurus took 0.1650984287261963s
Availability | VoID file availability check for Social Semantic Web Thesaurus took 0.0007936954498291016s
Extra | Recovery of all triples for Social Semantic Web Thesaurus took 20.25232982635498s
Performance | Total latancy measurement for Social Semantic Web Thesaurus took 0.4193270206451416s
Amount of data | Number of triples check for Social Semantic Web Thesaurus took 0.17950677871704102s
Interoperability | New terms check for Social Semantic Web Thesaurus took 1.4403502941131592s
Versatility | Languages check for Social Semantic Web Thesaurus took 0.32273292541503906s
Interpretability | Number of blank nodes check for Social Semantic Web Thesaurus took 0.17608857154846191s
Security | Check HTTPS for Social Semantic Web Thesaurus took 0.2949495315551758s
Interpretability | RDF structures check for Social Semantic Web Thesaurus took 0.11139798164367676s
Versatility | Serialization formats check for Social Semantic Web Thesaurus took 0.10643529891967773s
Availability | RDF dump link check for Social Semantic Web Thesaurus took 0.6906356811523438s
License | MR license check for Social Semantic Web Thesaurus took 0.10433769226074219s
License | HR license check for Social Semantic Web Thesaurus took 0.09341883659362793s
Amount of data | Number of property check for Social Semantic Web Thesaurus took 0.10217523574829102s
Understandability | Number of label check for Social Semantic Web Thesaurus took 0.10814499855041504s
Understandability | URI regex check for Social Semantic Web Thesaurus took 0.15845179557800293s
Understandability | Vocabs check for Social Semantic Web Thesaurus took 0.12012434005737305s
Verifiability | Authors check for Social Semantic Web Thesaurus took 0.1058340072631836s
Verifiability | Publishers check for Social Semantic Web Thesaurus took 0.1044776439666748s
Performance | Throughput check for Social Semantic Web Thesaurus took 10.427022695541382s
Amount of data | Check the number of entities for Social Semantic Web Thesaurus took 7.62939453125e-05s
Verifiability | Contribs. check for Social Semantic Web Thesaurus took 0.1035013198852539s
Interlinking | sameAs chians check for Social Semantic Web Thesaurus took 0.10540628433227539s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.10419011116027832s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.08098506927490234s
Timeliness | dataset update frequency check for Social Semantic Web Thesaurus took 0.08184432983398438s
Currency | Creation date check for Social Semantic Web Thesaurus took 0.1630706787109375s
Currency | Modification date check for Social Semantic Web Thesaurus took 0.18604540824890137s
Rep.Conc. | URIs length for Social Semantic Web Thesaurus took 1.906815767288208s
Interoperability | New vocabularies check for Social Semantic Web Thesaurus took 0.8884069919586182s
Consistency | Deprecated classes/propertiers check for Social Semantic Web Thesaurus took 0.10316252708435059s
Accuracy | Check Functional Property for Social Semantic Web Thesaurus took 0.07982230186462402s
Accuracy | Check Inverse Functional Property for Social Semantic Web Thesaurus took 0.08025097846984863s
Accuracy | Check Empty annotation labels for Social Semantic Web Thesaurus took 0.44147706031799316s
Accuracy | Check White space in annotation for Social Semantic Web Thesaurus took 0.012558221817016602s
Consistency | Disjoint class check for Social Semantic Web Thesaurus took 0.0782012939453125s
Consistency | Check Misplaced properties for Social Semantic Web Thesaurus took 0.26932668685913086s
Consistency | Misplaced classes for Social Semantic Web Thesaurus took 0.08421611785888672s
Consistency | Check Ontology hijacking for Social Semantic Web Thesaurus took 2.177579164505005s
Consistency | Check Invalid usage of undefined properties for Social Semantic Web Thesaurus took 1.4399900436401367s
Conciseness | Check Extensional conciseness for Social Semantic Web Thesaurus took 0.0001468658447265625s
Security | Sign check for Social Semantic Web Thesaurus took 0.08088350296020508s
Availability | Check URIs Dereferenciability for Social Semantic Web Thesaurus took 110.15488934516907s
Completeness | Calculation of interlinking completeness for Social Semantic Web Thesaurus took 0.2651937007904053s
Reputation | Calculation of the PageRank for Social Semantic Web Thesaurus took 0.02037954330444336s
Interlinking | Calculation of Degree of Connection for Social Semantic Web Thesaurus took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Social Semantic Web Thesaurus took 0.0006747245788574219s
Interlinking | Calculation of Clustering coefficient for Social Semantic Web Thesaurus took 9.608268737792969e-05s
Interoperability | Check the re-using of existing vocabs for Social Semantic Web Thesaurus took 3.814103126525879s
Believability | Calculation of trust value for Social Semantic Web Thesaurus took 1.0728836059570312e-05s
INFO | --- Analysis for socialsemweb-thesaurus took 516.1921603679657s
Availability | SPARQL endpoint availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.3112783432006836s
Availability | VoID file availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0005183219909667969s
Extra | Recovery of all triples for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 132.60967254638672s
Performance | Total latancy measurement for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.874659538269043s
Amount of data | Number of triples check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 9.162238597869873s
Interoperability | New terms check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 14.52190351486206s
Versatility | Languages check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 300.1556930541992s
Interpretability | Number of blank nodes check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.274308204650879s
Interpretability | RDF structures check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2688472270965576s
Versatility | Serialization formats check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 10.809765815734863s
Availability | RDF dump link check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.349092960357666s
License | MR license check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.6769256591796875s
License | HR license check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 300.2108871936798s
Amount of data | Number of property check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.1854715347290039s
Understandability | Number of label check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.2372655868530273s
Understandability | URI regex check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.1220166683197021s
Understandability | Vocabs check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.43646955490112305s
Verifiability | Authors check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.1856825351715088s
Verifiability | Publishers check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.22409439086914062s
Performance | Throughput check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 10.710568904876709s
Amount of data | Check the number of entities for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 6.794929504394531e-05s
Verifiability | Contribs. check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.17896509170532227s
Interlinking | sameAs chians check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.18395733833312988s
Interlinking | skos check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.4061906337738037s
Interlinking | skos check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.3958899974822998s
Timeliness | dataset update frequency check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 4.309666633605957s
Currency | Creation date check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.4376649856567383s
Currency | Modification date check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2216932773590088s
Rep.Conc. | URIs length for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 150.72076725959778s
Interoperability | New vocabularies check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.18465018272399902s
Accuracy | Check Functional Property for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.41117238998413086s
Accuracy | Check Inverse Functional Property for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.34981751441955566s
Accuracy | Check Empty annotation labels for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 37.059606075286865s
Accuracy | Check White space in annotation for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.6559951305389404s
Accuracy | Check Datatype consistency for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.616955518722534s
Consistency | Disjoint class check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.17719697952270508s
Consistency | Check Misplaced properties for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 87.14914083480835s
Consistency | Misplaced classes for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.375925540924072s
Consistency | Check Ontology hijacking for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 34.83309292793274s
Consistency | Check Invalid usage of undefined classes for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.3790135383605957s
Consistency | Check Invalid usage of undefined properties for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 88.12767338752747s
Conciseness | Check Extensional conciseness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.713517904281616s
Conciseness | Check Intensional conciseness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.517827033996582s
Security | Sign check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.0140469074249268s
Availability | Check URIs Dereferenciability for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 12.481014728546143s
Completeness | Calculation of interlinking completeness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.7019093036651611s
Reputation | Calculation of the PageRank for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.020836591720581055s
Interlinking | Calculation of Degree of Connection for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 4.124641418457031e-05s
Interoperability | Check the re-using of existing vocabs for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.430511474609375e-06s
Believability | Calculation of trust value for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.049041748046875e-05s
INFO | --- Analysis for Soil_maps took 2290.949292421341s
Availability | SPARQL endpoint availability check for terrorrist ontology took 0.00010848045349121094s
Availability | VoID file availability check for terrorrist ontology took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for terrorrist ontology took 0.26694202423095703s
Reputation | Calculation of the PageRank for terrorrist ontology took 0.020760774612426758s
Interlinking | Calculation of Degree of Connection for terrorrist ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for terrorrist ontology took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for terrorrist ontology took 3.147125244140625e-05s
Believability | Calculation of trust value for terrorrist ontology took 1.049041748046875e-05s
INFO | --- Analysis for somya_omer took 2.468536376953125s
Availability | SPARQL endpoint availability check for Sonclubcx took 0.0002205371856689453s
Availability | VoID file availability check for Sonclubcx took 0.0006000995635986328s
Completeness | Calculation of interlinking completeness for Sonclubcx took 0.26451897621154785s
Reputation | Calculation of the PageRank for Sonclubcx took 0.02034735679626465s
Interlinking | Calculation of Degree of Connection for Sonclubcx took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Sonclubcx took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Sonclubcx took 1.1682510375976562e-05s
Believability | Calculation of trust value for Sonclubcx took 9.775161743164062e-06s
INFO | --- Analysis for sonclubcx took 3.5163395404815674s
Availability | SPARQL endpoint availability check for SORS took 4.2438507080078125e-05s
Availability | VoID file availability check for SORS took 0.0005593299865722656s
Completeness | Calculation of interlinking completeness for SORS took 0.26427245140075684s
Reputation | Calculation of the PageRank for SORS took 0.021344900131225586s
Interlinking | Calculation of Degree of Connection for SORS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SORS took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for SORS took 4.8160552978515625e-05s
Believability | Calculation of trust value for SORS took 9.059906005859375e-06s
INFO | --- Analysis for sors took 12.626741409301758s
Availability | SPARQL endpoint availability check for southampton-ac-uk took 9.179115295410156e-05s
Availability | VoID file availability check for southampton-ac-uk took 0.0005054473876953125s
Completeness | Calculation of interlinking completeness for southampton-ac-uk took 0.26390647888183594s
Reputation | Calculation of the PageRank for southampton-ac-uk took 0.020790815353393555s
Interlinking | Calculation of Degree of Connection for southampton-ac-uk took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for southampton-ac-uk took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for southampton-ac-uk took 0.00012683868408203125s
Believability | Calculation of trust value for southampton-ac-uk took 1.2159347534179688e-05s
INFO | --- Analysis for southampton-ac-uk took 3.7637157440185547s
Availability | SPARQL endpoint availability check for Apps using our data (University of Southampton) took 3.064854145050049s
Availability | VoID file availability check for Apps using our data (University of Southampton) took 0.0005776882171630859s
Completeness | Calculation of interlinking completeness for Apps using our data (University of Southampton) took 0.26178908348083496s
Reputation | Calculation of the PageRank for Apps using our data (University of Southampton) took 0.02140974998474121s
Interlinking | Calculation of Degree of Connection for Apps using our data (University of Southampton) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Apps using our data (University of Southampton) took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Apps using our data (University of Southampton) took 3.1948089599609375e-05s
Believability | Calculation of trust value for Apps using our data (University of Southampton) took 1.1205673217773438e-05s
INFO | --- Analysis for southampton-ac-uk-apps took 12.336673259735107s
Availability | SPARQL endpoint availability check for ECS Southampton EPrints took 8.845329284667969e-05s
Availability | VoID file availability check for ECS Southampton EPrints took 0.00046825408935546875s
Completeness | Calculation of interlinking completeness for ECS Southampton EPrints took 0.2700381278991699s
Reputation | Calculation of the PageRank for ECS Southampton EPrints took 0.021215438842773438s
Interlinking | Calculation of Degree of Connection for ECS Southampton EPrints took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for ECS Southampton EPrints took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for ECS Southampton EPrints took 9.1552734375e-05s
Believability | Calculation of trust value for ECS Southampton EPrints took 1.0967254638671875e-05s
INFO | --- Analysis for southampton-ecs-eprints took 2.5031840801239014s
Availability | SPARQL endpoint availability check for Spanish Linguistic Datasets took 0.45609092712402344s
Availability | VoID file availability check for Spanish Linguistic Datasets took 0.00047779083251953125s
Extra | Recovery of all triples for Spanish Linguistic Datasets took 32861.4597697258s
Performance | Total latancy measurement for Spanish Linguistic Datasets took 8.602247714996338s
Amount of data | Number of triples check for Spanish Linguistic Datasets took 9.292051792144775s
Interoperability | New terms check for Spanish Linguistic Datasets took 3.0430285930633545s
Versatility | Languages check for Spanish Linguistic Datasets took 44.46790432929993s
Interpretability | Number of blank nodes check for Spanish Linguistic Datasets took 1.6315064430236816s
Security | Check HTTPS for Spanish Linguistic Datasets took 0.21128439903259277s
Interpretability | RDF structures check for Spanish Linguistic Datasets took 0.2642185688018799s
Versatility | Serialization formats check for Spanish Linguistic Datasets took 0.6205859184265137s
Availability | RDF dump link check for Spanish Linguistic Datasets took 0.26038551330566406s
License | MR license check for Spanish Linguistic Datasets took 0.29889917373657227s
License | HR license check for Spanish Linguistic Datasets took 0.4756615161895752s
Amount of data | Number of property check for Spanish Linguistic Datasets took 2.295097589492798s
Understandability | Number of label check for Spanish Linguistic Datasets took 0.29632568359375s
Understandability | URI regex check for Spanish Linguistic Datasets took 1.1328234672546387s
Understandability | Vocabs check for Spanish Linguistic Datasets took 0.2686495780944824s
Verifiability | Authors check for Spanish Linguistic Datasets took 0.5861954689025879s
Verifiability | Publishers check for Spanish Linguistic Datasets took 0.26242876052856445s
Performance | Throughput check for Spanish Linguistic Datasets took 102.30523586273193s
Amount of data | Check the number of entities for Spanish Linguistic Datasets took 7.081031799316406e-05s
Verifiability | Contribs. check for Spanish Linguistic Datasets took 0.25926947593688965s
Interlinking | sameAs chians check for Spanish Linguistic Datasets took 0.267559289932251s
Interlinking | skos check for Spanish Linguistic Datasets took 0.26444411277770996s
Interlinking | skos check for Spanish Linguistic Datasets took 0.2016758918762207s
Timeliness | dataset update frequency check for Spanish Linguistic Datasets took 0.2616136074066162s
Currency | Creation date check for Spanish Linguistic Datasets took 0.5264089107513428s
Currency | Modification date check for Spanish Linguistic Datasets took 0.5273942947387695s
Rep.Conc. | URIs length for Spanish Linguistic Datasets took 55.3686728477478s
Interoperability | New vocabularies check for Spanish Linguistic Datasets took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Spanish Linguistic Datasets took 1.0174658298492432s
Accuracy | Check Functional Property for Spanish Linguistic Datasets took 0.2602105140686035s
Accuracy | Check Inverse Functional Property for Spanish Linguistic Datasets took 25.700101137161255s
Accuracy | Check Empty annotation labels for Spanish Linguistic Datasets took 0.7325067520141602s
Accuracy | Check White space in annotation for Spanish Linguistic Datasets took 0.010220050811767578s
Consistency | Disjoint class check for Spanish Linguistic Datasets took 0.26105356216430664s
Consistency | Check Misplaced properties for Spanish Linguistic Datasets took 4.7681496143341064s
Consistency | Misplaced classes for Spanish Linguistic Datasets took 0.2701418399810791s
Consistency | Check Ontology hijacking for Spanish Linguistic Datasets took 43.44816708564758s
Consistency | Check Invalid usage of undefined properties for Spanish Linguistic Datasets took 5.643895149230957s
Conciseness | Check Extensional conciseness for Spanish Linguistic Datasets took 0.00014829635620117188s
Conciseness | Check Intensional conciseness for Spanish Linguistic Datasets took 0.28690385818481445s
Security | Sign check for Spanish Linguistic Datasets took 0.9363059997558594s
Completeness | Calculation of interlinking completeness for Spanish Linguistic Datasets took 0.7341198921203613s
Reputation | Calculation of the PageRank for Spanish Linguistic Datasets took 0.021528244018554688s
Interlinking | Calculation of Degree of Connection for Spanish Linguistic Datasets took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Spanish Linguistic Datasets took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Spanish Linguistic Datasets took 3.838539123535156e-05s
Interoperability | Check the re-using of existing vocabs for Spanish Linguistic Datasets took 2.384185791015625e-06s
Believability | Calculation of trust value for Spanish Linguistic Datasets took 1.621246337890625e-05s
INFO | --- Analysis for spanish-linguistic-datasets took 33523.26049923897s
Availability | SPARQL endpoint availability check for SPARQL Endpoint Status took 0.0429377555847168s
Availability | VoID file availability check for SPARQL Endpoint Status took 0.0004382133483886719s
Completeness | Calculation of interlinking completeness for SPARQL Endpoint Status took 0.2698557376861572s
Reputation | Calculation of the PageRank for SPARQL Endpoint Status took 0.020858049392700195s
Interlinking | Calculation of Degree of Connection for SPARQL Endpoint Status took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for SPARQL Endpoint Status took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for SPARQL Endpoint Status took 5.459785461425781e-05s
Believability | Calculation of trust value for SPARQL Endpoint Status took 1.0013580322265625e-05s
INFO | --- Analysis for sparql-endpoint-status took 2.4983279705047607s
Availability | SPARQL endpoint availability check for Springer Nature SciGraph took 4.8160552978515625e-05s
Availability | VoID file availability check for Springer Nature SciGraph took 0.0005557537078857422s
Completeness | Calculation of interlinking completeness for Springer Nature SciGraph took 0.2708585262298584s
Reputation | Calculation of the PageRank for Springer Nature SciGraph took 0.02163553237915039s
Interlinking | Calculation of Degree of Connection for Springer Nature SciGraph took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Springer Nature SciGraph took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Springer Nature SciGraph took 0.00010132789611816406s
Believability | Calculation of trust value for Springer Nature SciGraph took 1.1920928955078125e-05s
INFO | --- Analysis for springernaturescigraph took 2.927375078201294s
Availability | SPARQL endpoint availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 8.7738037109375e-05s
Availability | VoID file availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0006701946258544922s
Completeness | Calculation of interlinking completeness for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.27877378463745117s
Reputation | Calculation of the PageRank for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.02126336097717285s
Interlinking | Calculation of Degree of Connection for Syntactic Reference Corpus of Medieval French (SRCMF) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Syntactic Reference Corpus of Medieval French (SRCMF) took 3.218650817871094e-05s
Believability | Calculation of trust value for Syntactic Reference Corpus of Medieval French (SRCMF) took 1.239776611328125e-05s
INFO | --- Analysis for srcmf took 6.02040433883667s
Availability | SPARQL endpoint availability check for Lexicon of Syntactic and Semantic Framework took 0.29418206214904785s
Availability | VoID file availability check for Lexicon of Syntactic and Semantic Framework took 0.00060272216796875s
Extra | Recovery of all triples for Lexicon of Syntactic and Semantic Framework took 1.0367178916931152s
Performance | Total latancy measurement for Lexicon of Syntactic and Semantic Framework took 0.6420228481292725s
Amount of data | Number of triples check for Lexicon of Syntactic and Semantic Framework took 0.12843585014343262s
Interoperability | New terms check for Lexicon of Syntactic and Semantic Framework took 1.3705120086669922s
Versatility | Languages check for Lexicon of Syntactic and Semantic Framework took 0.13340282440185547s
Interpretability | Number of blank nodes check for Lexicon of Syntactic and Semantic Framework took 0.13174128532409668s
Security | Check HTTPS for Lexicon of Syntactic and Semantic Framework took 0.07829475402832031s
Interpretability | RDF structures check for Lexicon of Syntactic and Semantic Framework took 0.1326591968536377s
Versatility | Serialization formats check for Lexicon of Syntactic and Semantic Framework took 0.1317765712738037s
Availability | RDF dump link check for Lexicon of Syntactic and Semantic Framework took 0.12863850593566895s
License | MR license check for Lexicon of Syntactic and Semantic Framework took 0.13135075569152832s
License | HR license check for Lexicon of Syntactic and Semantic Framework took 0.13033556938171387s
Amount of data | Number of property check for Lexicon of Syntactic and Semantic Framework took 0.13451743125915527s
Understandability | Number of label check for Lexicon of Syntactic and Semantic Framework took 0.13719463348388672s
Understandability | URI regex check for Lexicon of Syntactic and Semantic Framework took 0.2578136920928955s
Understandability | Vocabs check for Lexicon of Syntactic and Semantic Framework took 0.12911653518676758s
Verifiability | Authors check for Lexicon of Syntactic and Semantic Framework took 0.13199591636657715s
Verifiability | Publishers check for Lexicon of Syntactic and Semantic Framework took 0.1300792694091797s
Performance | Throughput check for Lexicon of Syntactic and Semantic Framework took 10.383641242980957s
Amount of data | Check the number of entities for Lexicon of Syntactic and Semantic Framework took 0.00010943412780761719s
Verifiability | Contribs. check for Lexicon of Syntactic and Semantic Framework took 0.13048624992370605s
Interlinking | sameAs chians check for Lexicon of Syntactic and Semantic Framework took 0.13016557693481445s
Interlinking | skos check for Lexicon of Syntactic and Semantic Framework took 0.13008332252502441s
Interlinking | skos check for Lexicon of Syntactic and Semantic Framework took 0.13033318519592285s
Timeliness | dataset update frequency check for Lexicon of Syntactic and Semantic Framework took 0.13021469116210938s
Currency | Creation date check for Lexicon of Syntactic and Semantic Framework took 0.26178741455078125s
Currency | Modification date check for Lexicon of Syntactic and Semantic Framework took 0.26018309593200684s
Rep.Conc. | URIs length for Lexicon of Syntactic and Semantic Framework took 0.4195249080657959s
Interoperability | New vocabularies check for Lexicon of Syntactic and Semantic Framework took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for Lexicon of Syntactic and Semantic Framework took 0.12955164909362793s
Accuracy | Check Functional Property for Lexicon of Syntactic and Semantic Framework took 0.12860774993896484s
Accuracy | Check Inverse Functional Property for Lexicon of Syntactic and Semantic Framework took 0.12859606742858887s
Accuracy | Check Empty annotation labels for Lexicon of Syntactic and Semantic Framework took 0.13672876358032227s
Accuracy | Check White space in annotation for Lexicon of Syntactic and Semantic Framework took 0.0002999305725097656s
Accuracy | Check Datatype consistency for Lexicon of Syntactic and Semantic Framework took 0.035140037536621094s
Consistency | Disjoint class check for Lexicon of Syntactic and Semantic Framework took 0.12804079055786133s
Consistency | Check Misplaced properties for Lexicon of Syntactic and Semantic Framework took 0.2671816349029541s
Consistency | Misplaced classes for Lexicon of Syntactic and Semantic Framework took 0.18150043487548828s
Consistency | Check Ontology hijacking for Lexicon of Syntactic and Semantic Framework took 1.453934669494629s
Consistency | Check Invalid usage of undefined classes for Lexicon of Syntactic and Semantic Framework took 1.287099838256836s
Consistency | Check Invalid usage of undefined properties for Lexicon of Syntactic and Semantic Framework took 1.4189331531524658s
Conciseness | Check Extensional conciseness for Lexicon of Syntactic and Semantic Framework took 0.02644658088684082s
Conciseness | Check Intensional conciseness for Lexicon of Syntactic and Semantic Framework took 0.13001561164855957s
Security | Sign check for Lexicon of Syntactic and Semantic Framework took 0.13013291358947754s
Availability | Check URIs Dereferenciability for Lexicon of Syntactic and Semantic Framework took 265.24844336509705s
Completeness | Calculation of interlinking completeness for Lexicon of Syntactic and Semantic Framework took 129.59017324447632s
Reputation | Calculation of the PageRank for Lexicon of Syntactic and Semantic Framework took 0.021188020706176758s
Interlinking | Calculation of Degree of Connection for Lexicon of Syntactic and Semantic Framework took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Lexicon of Syntactic and Semantic Framework took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Lexicon of Syntactic and Semantic Framework took 5.745887756347656e-05s
Interoperability | Check the re-using of existing vocabs for Lexicon of Syntactic and Semantic Framework took 1.9073486328125e-06s
Believability | Calculation of trust value for Lexicon of Syntactic and Semantic Framework took 1.6450881958007812e-05s
INFO | --- Analysis for ssf took 955.167649269104s
Availability | SPARQL endpoint availability check for St. Andrews University Resource Lists took 6.4849853515625e-05s
Availability | VoID file availability check for St. Andrews University Resource Lists took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for St. Andrews University Resource Lists took 130.18690657615662s
Reputation | Calculation of the PageRank for St. Andrews University Resource Lists took 0.020898818969726562s
Interlinking | Calculation of Degree of Connection for St. Andrews University Resource Lists took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for St. Andrews University Resource Lists took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for St. Andrews University Resource Lists took 4.839897155761719e-05s
Believability | Calculation of trust value for St. Andrews University Resource Lists took 2.3365020751953125e-05s
INFO | --- Analysis for st-andrews-resource-lists took 525.0782403945923s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 8.845329284667969e-05s
Availability | VoID file availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0005757808685302734s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.2700340747833252s
Reputation | Calculation of the PageRank for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.021205902099609375s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 3.457069396972656e-05s
Believability | Calculation of trust value for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 9.059906005859375e-06s
INFO | --- Analysis for staff-organograms-and-pay-thurrock-thames-gateway-development-corporation took 2.955139398574829s
Availability | SPARQL endpoint availability check for Stammbuch took 6.175041198730469e-05s
Availability | VoID file availability check for Stammbuch took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for Stammbuch took 0.2771942615509033s
Reputation | Calculation of the PageRank for Stammbuch took 0.023397207260131836s
Interlinking | Calculation of Degree of Connection for Stammbuch took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Stammbuch took 0.0012001991271972656s
Interlinking | Calculation of Clustering coefficient for Stammbuch took 4.124641418457031e-05s
Believability | Calculation of trust value for Stammbuch took 1.1444091796875e-05s
INFO | --- Analysis for Stammbuch took 2.429215908050537s
Availability | SPARQL endpoint availability check for statistics.data.gov.uk took 1.2209396362304688s
Availability | VoID file availability check for statistics.data.gov.uk took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for statistics.data.gov.uk took 0.27199220657348633s
Reputation | Calculation of the PageRank for statistics.data.gov.uk took 0.02026081085205078s
Interlinking | Calculation of Degree of Connection for statistics.data.gov.uk took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statistics.data.gov.uk took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for statistics.data.gov.uk took 0.00010395050048828125s
Believability | Calculation of trust value for statistics.data.gov.uk took 9.775161743164062e-06s
INFO | --- Analysis for statistics-data-gov-uk took 4.08422589302063s
Availability | SPARQL endpoint availability check for statusnet-1w6-org took 8.797645568847656e-05s
Availability | VoID file availability check for statusnet-1w6-org took 0.0005025863647460938s
Completeness | Calculation of interlinking completeness for statusnet-1w6-org took 0.2667717933654785s
Reputation | Calculation of the PageRank for statusnet-1w6-org took 0.020910263061523438s
Interlinking | Calculation of Degree of Connection for statusnet-1w6-org took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-1w6-org took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for statusnet-1w6-org took 0.00010633468627929688s
Believability | Calculation of trust value for statusnet-1w6-org took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-1w6-org took 4.031473159790039s
Availability | SPARQL endpoint availability check for statusnet-20100-org took 8.845329284667969e-05s
Availability | VoID file availability check for statusnet-20100-org took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for statusnet-20100-org took 0.27042436599731445s
Reputation | Calculation of the PageRank for statusnet-20100-org took 0.020663738250732422s
Interlinking | Calculation of Degree of Connection for statusnet-20100-org took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-20100-org took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for statusnet-20100-org took 6.246566772460938e-05s
Believability | Calculation of trust value for statusnet-20100-org took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-20100-org took 2.6003620624542236s
Availability | SPARQL endpoint availability check for statusnet-alexandrefranke-com took 9.083747863769531e-05s
Availability | VoID file availability check for statusnet-alexandrefranke-com took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for statusnet-alexandrefranke-com took 0.26832079887390137s
Reputation | Calculation of the PageRank for statusnet-alexandrefranke-com took 0.020632505416870117s
Interlinking | Calculation of Degree of Connection for statusnet-alexandrefranke-com took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-alexandrefranke-com took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for statusnet-alexandrefranke-com took 6.985664367675781e-05s
Believability | Calculation of trust value for statusnet-alexandrefranke-com took 1.4066696166992188e-05s
INFO | --- Analysis for statusnet-alexandrefranke-com took 2.9168484210968018s
Availability | SPARQL endpoint availability check for statusnet-atari-frosch-de took 9.131431579589844e-05s
Availability | VoID file availability check for statusnet-atari-frosch-de took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for statusnet-atari-frosch-de took 0.27684974670410156s
Reputation | Calculation of the PageRank for statusnet-atari-frosch-de took 0.022096872329711914s
Interlinking | Calculation of Degree of Connection for statusnet-atari-frosch-de took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for statusnet-atari-frosch-de took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for statusnet-atari-frosch-de took 8.58306884765625e-05s
Believability | Calculation of trust value for statusnet-atari-frosch-de took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-atari-frosch-de took 2.479360818862915s
Availability | SPARQL endpoint availability check for statusnet-belfalas-org took 9.226799011230469e-05s
Availability | VoID file availability check for statusnet-belfalas-org took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for statusnet-belfalas-org took 0.26399731636047363s
Reputation | Calculation of the PageRank for statusnet-belfalas-org took 0.02196645736694336s
Interlinking | Calculation of Degree of Connection for statusnet-belfalas-org took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for statusnet-belfalas-org took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for statusnet-belfalas-org took 9.72747802734375e-05s
Believability | Calculation of trust value for statusnet-belfalas-org took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-belfalas-org took 2.467745304107666s
Availability | SPARQL endpoint availability check for statusnet-bka-li took 0.00013566017150878906s
Availability | VoID file availability check for statusnet-bka-li took 0.0007998943328857422s
Completeness | Calculation of interlinking completeness for statusnet-bka-li took 0.26804566383361816s
Reputation | Calculation of the PageRank for statusnet-bka-li took 0.021547794342041016s
Interlinking | Calculation of Degree of Connection for statusnet-bka-li took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for statusnet-bka-li took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for statusnet-bka-li took 0.00011849403381347656s
Believability | Calculation of trust value for statusnet-bka-li took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-bka-li took 12.538366317749023s
Availability | SPARQL endpoint availability check for statusnet-bonifaz-ec took 8.58306884765625e-05s
Availability | VoID file availability check for statusnet-bonifaz-ec took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for statusnet-bonifaz-ec took 0.26175355911254883s
Reputation | Calculation of the PageRank for statusnet-bonifaz-ec took 0.02058696746826172s
Interlinking | Calculation of Degree of Connection for statusnet-bonifaz-ec took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-bonifaz-ec took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for statusnet-bonifaz-ec took 4.124641418457031e-05s
Believability | Calculation of trust value for statusnet-bonifaz-ec took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-bonifaz-ec took 3.353116989135742s
Availability | SPARQL endpoint availability check for statusnet-ced117-net took 4.482269287109375e-05s
Availability | VoID file availability check for statusnet-ced117-net took 0.0005505084991455078s
Completeness | Calculation of interlinking completeness for statusnet-ced117-net took 0.278810977935791s
Reputation | Calculation of the PageRank for statusnet-ced117-net took 0.02098393440246582s
Interlinking | Calculation of Degree of Connection for statusnet-ced117-net took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-ced117-net took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for statusnet-ced117-net took 4.9114227294921875e-05s
Believability | Calculation of trust value for statusnet-ced117-net took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-ced117-net took 2.9581634998321533s
Availability | SPARQL endpoint availability check for statusnet-chickenkiller-com took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-chickenkiller-com took 0.0006992816925048828s
Completeness | Calculation of interlinking completeness for statusnet-chickenkiller-com took 0.2677607536315918s
Reputation | Calculation of the PageRank for statusnet-chickenkiller-com took 0.021036863327026367s
Interlinking | Calculation of Degree of Connection for statusnet-chickenkiller-com took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-chickenkiller-com took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for statusnet-chickenkiller-com took 5.2928924560546875e-05s
Believability | Calculation of trust value for statusnet-chickenkiller-com took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-chickenkiller-com took 2.6553022861480713s
Availability | SPARQL endpoint availability check for statusnet-chromic-org took 8.797645568847656e-05s
Availability | VoID file availability check for statusnet-chromic-org took 0.0005285739898681641s
Completeness | Calculation of interlinking completeness for statusnet-chromic-org took 0.2628633975982666s
Reputation | Calculation of the PageRank for statusnet-chromic-org took 0.020782470703125s
Interlinking | Calculation of Degree of Connection for statusnet-chromic-org took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for statusnet-chromic-org took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for statusnet-chromic-org took 0.00011515617370605469s
Believability | Calculation of trust value for statusnet-chromic-org took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-chromic-org took 2.637753963470459s
Availability | SPARQL endpoint availability check for statusnet-cooleysekula-net took 4.7206878662109375e-05s
Availability | VoID file availability check for statusnet-cooleysekula-net took 0.0006444454193115234s
Completeness | Calculation of interlinking completeness for statusnet-cooleysekula-net took 0.27144885063171387s
Reputation | Calculation of the PageRank for statusnet-cooleysekula-net took 0.022702455520629883s
Interlinking | Calculation of Degree of Connection for statusnet-cooleysekula-net took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for statusnet-cooleysekula-net took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for statusnet-cooleysekula-net took 7.963180541992188e-05s
Believability | Calculation of trust value for statusnet-cooleysekula-net took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-cooleysekula-net took 6.473074674606323s
Availability | SPARQL endpoint availability check for statusnet-coreyavis-com took 4.9591064453125e-05s
Availability | VoID file availability check for statusnet-coreyavis-com took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for statusnet-coreyavis-com took 0.26543712615966797s
Reputation | Calculation of the PageRank for statusnet-coreyavis-com took 0.020918846130371094s
Interlinking | Calculation of Degree of Connection for statusnet-coreyavis-com took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-coreyavis-com took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for statusnet-coreyavis-com took 6.270408630371094e-05s
Believability | Calculation of trust value for statusnet-coreyavis-com took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-coreyavis-com took 2.4747509956359863s
Availability | SPARQL endpoint availability check for statusnet-datenfahrt-org took 9.036064147949219e-05s
Availability | VoID file availability check for statusnet-datenfahrt-org took 0.0005664825439453125s
Completeness | Calculation of interlinking completeness for statusnet-datenfahrt-org took 0.2635619640350342s
Reputation | Calculation of the PageRank for statusnet-datenfahrt-org took 0.02092719078063965s
Interlinking | Calculation of Degree of Connection for statusnet-datenfahrt-org took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-datenfahrt-org took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for statusnet-datenfahrt-org took 6.866455078125e-05s
Believability | Calculation of trust value for statusnet-datenfahrt-org took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-datenfahrt-org took 3.0578370094299316s
Availability | SPARQL endpoint availability check for statusnet-davidhaberthuer-ch took 9.131431579589844e-05s
Availability | VoID file availability check for statusnet-davidhaberthuer-ch took 0.0005521774291992188s
Completeness | Calculation of interlinking completeness for statusnet-davidhaberthuer-ch took 0.26355409622192383s
Reputation | Calculation of the PageRank for statusnet-davidhaberthuer-ch took 0.02133774757385254s
Interlinking | Calculation of Degree of Connection for statusnet-davidhaberthuer-ch took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-davidhaberthuer-ch took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for statusnet-davidhaberthuer-ch took 0.00010347366333007812s
Believability | Calculation of trust value for statusnet-davidhaberthuer-ch took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-davidhaberthuer-ch took 2.562873125076294s
Availability | SPARQL endpoint availability check for statusnet-deuxpi-ca took 9.059906005859375e-05s
Availability | VoID file availability check for statusnet-deuxpi-ca took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for statusnet-deuxpi-ca took 0.27184057235717773s
Reputation | Calculation of the PageRank for statusnet-deuxpi-ca took 0.02257847785949707s
Interlinking | Calculation of Degree of Connection for statusnet-deuxpi-ca took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-deuxpi-ca took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for statusnet-deuxpi-ca took 6.198883056640625e-05s
Believability | Calculation of trust value for statusnet-deuxpi-ca took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-deuxpi-ca took 2.4568049907684326s
Availability | SPARQL endpoint availability check for statusnet-doomicile-de took 4.601478576660156e-05s
Availability | VoID file availability check for statusnet-doomicile-de took 0.0006277561187744141s
Completeness | Calculation of interlinking completeness for statusnet-doomicile-de took 0.27036523818969727s
Reputation | Calculation of the PageRank for statusnet-doomicile-de took 0.020650863647460938s
Interlinking | Calculation of Degree of Connection for statusnet-doomicile-de took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-doomicile-de took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for statusnet-doomicile-de took 5.14984130859375e-05s
Believability | Calculation of trust value for statusnet-doomicile-de took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-doomicile-de took 3.817477226257324s
Availability | SPARQL endpoint availability check for statusnet-dtdns-net took 8.916854858398438e-05s
Availability | VoID file availability check for statusnet-dtdns-net took 0.0007834434509277344s
Completeness | Calculation of interlinking completeness for statusnet-dtdns-net took 0.2661256790161133s
Reputation | Calculation of the PageRank for statusnet-dtdns-net took 0.021614789962768555s
Interlinking | Calculation of Degree of Connection for statusnet-dtdns-net took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for statusnet-dtdns-net took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for statusnet-dtdns-net took 6.365776062011719e-05s
Believability | Calculation of trust value for statusnet-dtdns-net took 1.4543533325195312e-05s
INFO | --- Analysis for statusnet-dtdns-net took 22.453869342803955s
Availability | SPARQL endpoint availability check for statusnet-equestriarp-net took 4.601478576660156e-05s
Availability | VoID file availability check for statusnet-equestriarp-net took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for statusnet-equestriarp-net took 0.2682456970214844s
Reputation | Calculation of the PageRank for statusnet-equestriarp-net took 0.022329092025756836s
Interlinking | Calculation of Degree of Connection for statusnet-equestriarp-net took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for statusnet-equestriarp-net took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for statusnet-equestriarp-net took 4.172325134277344e-05s
Believability | Calculation of trust value for statusnet-equestriarp-net took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-equestriarp-net took 2.4623711109161377s
Availability | SPARQL endpoint availability check for statusnet-exdc-net took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-exdc-net took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for statusnet-exdc-net took 0.26905179023742676s
Reputation | Calculation of the PageRank for statusnet-exdc-net took 0.020579814910888672s
Interlinking | Calculation of Degree of Connection for statusnet-exdc-net took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-exdc-net took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for statusnet-exdc-net took 7.486343383789062e-05s
Believability | Calculation of trust value for statusnet-exdc-net took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-exdc-net took 2.558335542678833s
Availability | SPARQL endpoint availability check for statusnet-fcac-com took 4.458427429199219e-05s
Availability | VoID file availability check for statusnet-fcac-com took 0.0005300045013427734s
Completeness | Calculation of interlinking completeness for statusnet-fcac-com took 0.27683162689208984s
Reputation | Calculation of the PageRank for statusnet-fcac-com took 0.020547151565551758s
Interlinking | Calculation of Degree of Connection for statusnet-fcac-com took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-fcac-com took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for statusnet-fcac-com took 9.131431579589844e-05s
Believability | Calculation of trust value for statusnet-fcac-com took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-fcac-com took 2.7864816188812256s
Availability | SPARQL endpoint availability check for statusnet-fcestrada-com took 5.5789947509765625e-05s
Availability | VoID file availability check for statusnet-fcestrada-com took 0.000568389892578125s
Completeness | Calculation of interlinking completeness for statusnet-fcestrada-com took 0.26375293731689453s
Reputation | Calculation of the PageRank for statusnet-fcestrada-com took 0.020615577697753906s
Interlinking | Calculation of Degree of Connection for statusnet-fcestrada-com took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for statusnet-fcestrada-com took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for statusnet-fcestrada-com took 5.459785461425781e-05s
Believability | Calculation of trust value for statusnet-fcestrada-com took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-fcestrada-com took 3.1191844940185547s
Availability | SPARQL endpoint availability check for statusnet-fragdev-com took 8.797645568847656e-05s
Availability | VoID file availability check for statusnet-fragdev-com took 0.0005908012390136719s
Completeness | Calculation of interlinking completeness for statusnet-fragdev-com took 0.27260351181030273s
Reputation | Calculation of the PageRank for statusnet-fragdev-com took 0.02204442024230957s
Interlinking | Calculation of Degree of Connection for statusnet-fragdev-com took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-fragdev-com took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for statusnet-fragdev-com took 0.00018143653869628906s
Believability | Calculation of trust value for statusnet-fragdev-com took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-fragdev-com took 3.325669765472412s
Availability | SPARQL endpoint availability check for statusnet-freelish-us took 8.821487426757812e-05s
Availability | VoID file availability check for statusnet-freelish-us took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for statusnet-freelish-us took 0.26590847969055176s
Reputation | Calculation of the PageRank for statusnet-freelish-us took 0.020821332931518555s
Interlinking | Calculation of Degree of Connection for statusnet-freelish-us took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-freelish-us took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for statusnet-freelish-us took 7.677078247070312e-05s
Believability | Calculation of trust value for statusnet-freelish-us took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-freelish-us took 2.482257604598999s
Availability | SPARQL endpoint availability check for statusnet-gegeweb-org took 8.821487426757812e-05s
Availability | VoID file availability check for statusnet-gegeweb-org took 0.0008389949798583984s
Completeness | Calculation of interlinking completeness for statusnet-gegeweb-org took 0.27218103408813477s
Reputation | Calculation of the PageRank for statusnet-gegeweb-org took 0.02081584930419922s
Interlinking | Calculation of Degree of Connection for statusnet-gegeweb-org took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for statusnet-gegeweb-org took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for statusnet-gegeweb-org took 0.00011944770812988281s
Believability | Calculation of trust value for statusnet-gegeweb-org took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-gegeweb-org took 7.476908445358276s
Availability | SPARQL endpoint availability check for statusnet-glou-org took 0.00010442733764648438s
Availability | VoID file availability check for statusnet-glou-org took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for statusnet-glou-org took 0.27126097679138184s
Reputation | Calculation of the PageRank for statusnet-glou-org took 0.02163219451904297s
Interlinking | Calculation of Degree of Connection for statusnet-glou-org took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-glou-org took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for statusnet-glou-org took 7.081031799316406e-05s
Believability | Calculation of trust value for statusnet-glou-org took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-glou-org took 2.5078835487365723s
Availability | SPARQL endpoint availability check for statusnet-gomertronic-com took 8.96453857421875e-05s
Availability | VoID file availability check for statusnet-gomertronic-com took 0.0004916191101074219s
Completeness | Calculation of interlinking completeness for statusnet-gomertronic-com took 0.27016639709472656s
Reputation | Calculation of the PageRank for statusnet-gomertronic-com took 0.0207061767578125s
Interlinking | Calculation of Degree of Connection for statusnet-gomertronic-com took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for statusnet-gomertronic-com took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for statusnet-gomertronic-com took 0.00012087821960449219s
Believability | Calculation of trust value for statusnet-gomertronic-com took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-gomertronic-com took 2.4834606647491455s
Availability | SPARQL endpoint availability check for statusnet-hackerposse-com took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-hackerposse-com took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for statusnet-hackerposse-com took 0.2667665481567383s
Reputation | Calculation of the PageRank for statusnet-hackerposse-com took 0.02059483528137207s
Interlinking | Calculation of Degree of Connection for statusnet-hackerposse-com took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-hackerposse-com took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for statusnet-hackerposse-com took 0.00010228157043457031s
Believability | Calculation of trust value for statusnet-hackerposse-com took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-hackerposse-com took 2.8958356380462646s
Availability | SPARQL endpoint availability check for statusnet-hii-co-il took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-hii-co-il took 0.00043511390686035156s
Completeness | Calculation of interlinking completeness for statusnet-hii-co-il took 0.2693455219268799s
Reputation | Calculation of the PageRank for statusnet-hii-co-il took 0.021373271942138672s
Interlinking | Calculation of Degree of Connection for statusnet-hii-co-il took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-hii-co-il took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for statusnet-hii-co-il took 6.818771362304688e-05s
Believability | Calculation of trust value for statusnet-hii-co-il took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-hii-co-il took 3.872088670730591s
Availability | SPARQL endpoint availability check for statusnet-ilikefreedom-ro took 4.792213439941406e-05s
Availability | VoID file availability check for statusnet-ilikefreedom-ro took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for statusnet-ilikefreedom-ro took 0.2615926265716553s
Reputation | Calculation of the PageRank for statusnet-ilikefreedom-ro took 0.021997928619384766s
Interlinking | Calculation of Degree of Connection for statusnet-ilikefreedom-ro took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-ilikefreedom-ro took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for statusnet-ilikefreedom-ro took 0.00010561943054199219s
Believability | Calculation of trust value for statusnet-ilikefreedom-ro took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-ilikefreedom-ro took 2.6702466011047363s
Availability | SPARQL endpoint availability check for statusnet-imirhil-fr took 4.482269287109375e-05s
Availability | VoID file availability check for statusnet-imirhil-fr took 0.0003783702850341797s
Completeness | Calculation of interlinking completeness for statusnet-imirhil-fr took 0.25898218154907227s
Reputation | Calculation of the PageRank for statusnet-imirhil-fr took 0.021170616149902344s
Interlinking | Calculation of Degree of Connection for statusnet-imirhil-fr took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-imirhil-fr took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for statusnet-imirhil-fr took 6.0558319091796875e-05s
Believability | Calculation of trust value for statusnet-imirhil-fr took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-imirhil-fr took 2.3950767517089844s
Availability | SPARQL endpoint availability check for statusnet-integralblue-com took 4.673004150390625e-05s
Availability | VoID file availability check for statusnet-integralblue-com took 0.0008449554443359375s
Completeness | Calculation of interlinking completeness for statusnet-integralblue-com took 0.25883054733276367s
Reputation | Calculation of the PageRank for statusnet-integralblue-com took 0.02030205726623535s
Interlinking | Calculation of Degree of Connection for statusnet-integralblue-com took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-integralblue-com took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for statusnet-integralblue-com took 3.8623809814453125e-05s
Believability | Calculation of trust value for statusnet-integralblue-com took 7.62939453125e-06s
INFO | --- Analysis for statusnet-integralblue-com took 2.5746052265167236s
Availability | SPARQL endpoint availability check for statusnet-johndrinkwater-name took 6.079673767089844e-05s
Availability | VoID file availability check for statusnet-johndrinkwater-name took 0.0006701946258544922s
Completeness | Calculation of interlinking completeness for statusnet-johndrinkwater-name took 0.2629077434539795s
Reputation | Calculation of the PageRank for statusnet-johndrinkwater-name took 0.02035999298095703s
Interlinking | Calculation of Degree of Connection for statusnet-johndrinkwater-name took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-johndrinkwater-name took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for statusnet-johndrinkwater-name took 5.316734313964844e-05s
Believability | Calculation of trust value for statusnet-johndrinkwater-name took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-johndrinkwater-name took 22.37733745574951s
Availability | SPARQL endpoint availability check for statusnet-jonkman-ca took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-jonkman-ca took 0.0003452301025390625s
Completeness | Calculation of interlinking completeness for statusnet-jonkman-ca took 0.2620890140533447s
Reputation | Calculation of the PageRank for statusnet-jonkman-ca took 0.02039194107055664s
Interlinking | Calculation of Degree of Connection for statusnet-jonkman-ca took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-jonkman-ca took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for statusnet-jonkman-ca took 0.00011086463928222656s
Believability | Calculation of trust value for statusnet-jonkman-ca took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-jonkman-ca took 3.2887613773345947s
Availability | SPARQL endpoint availability check for statusnet-kaimi-cc took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-kaimi-cc took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for statusnet-kaimi-cc took 0.2622807025909424s
Reputation | Calculation of the PageRank for statusnet-kaimi-cc took 0.02047872543334961s
Interlinking | Calculation of Degree of Connection for statusnet-kaimi-cc took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-kaimi-cc took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for statusnet-kaimi-cc took 9.942054748535156e-05s
Believability | Calculation of trust value for statusnet-kaimi-cc took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-kaimi-cc took 2.4499623775482178s
Availability | SPARQL endpoint availability check for statusnet-kathryl-fr took 4.482269287109375e-05s
Availability | VoID file availability check for statusnet-kathryl-fr took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for statusnet-kathryl-fr took 0.26279759407043457s
Reputation | Calculation of the PageRank for statusnet-kathryl-fr took 0.022211551666259766s
Interlinking | Calculation of Degree of Connection for statusnet-kathryl-fr took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-kathryl-fr took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for statusnet-kathryl-fr took 5.030632019042969e-05s
Believability | Calculation of trust value for statusnet-kathryl-fr took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-kathryl-fr took 2.4537160396575928s
Availability | SPARQL endpoint availability check for statusnet-kenzoid-com took 8.511543273925781e-05s
Availability | VoID file availability check for statusnet-kenzoid-com took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for statusnet-kenzoid-com took 0.26601743698120117s
Reputation | Calculation of the PageRank for statusnet-kenzoid-com took 0.0222017765045166s
Interlinking | Calculation of Degree of Connection for statusnet-kenzoid-com took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-kenzoid-com took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for statusnet-kenzoid-com took 3.981590270996094e-05s
Believability | Calculation of trust value for statusnet-kenzoid-com took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-kenzoid-com took 3.285228729248047s
Availability | SPARQL endpoint availability check for statusnet-keuser-fr took 4.649162292480469e-05s
Availability | VoID file availability check for statusnet-keuser-fr took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for statusnet-keuser-fr took 0.2597620487213135s
Reputation | Calculation of the PageRank for statusnet-keuser-fr took 0.020982980728149414s
Interlinking | Calculation of Degree of Connection for statusnet-keuser-fr took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-keuser-fr took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for statusnet-keuser-fr took 8.320808410644531e-05s
Believability | Calculation of trust value for statusnet-keuser-fr took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-keuser-fr took 2.44396710395813s
Availability | SPARQL endpoint availability check for statusnet-ldn-fai-net took 4.7206878662109375e-05s
Availability | VoID file availability check for statusnet-ldn-fai-net took 0.0007016658782958984s
Completeness | Calculation of interlinking completeness for statusnet-ldn-fai-net took 0.2673680782318115s
Reputation | Calculation of the PageRank for statusnet-ldn-fai-net took 0.021191835403442383s
Interlinking | Calculation of Degree of Connection for statusnet-ldn-fai-net took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-ldn-fai-net took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for statusnet-ldn-fai-net took 4.8160552978515625e-05s
Believability | Calculation of trust value for statusnet-ldn-fai-net took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-ldn-fai-net took 2.5552854537963867s
Availability | SPARQL endpoint availability check for statusnet-lebsanft-org took 9.179115295410156e-05s
Availability | VoID file availability check for statusnet-lebsanft-org took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for statusnet-lebsanft-org took 0.26192402839660645s
Reputation | Calculation of the PageRank for statusnet-lebsanft-org took 0.021253347396850586s
Interlinking | Calculation of Degree of Connection for statusnet-lebsanft-org took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-lebsanft-org took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for statusnet-lebsanft-org took 6.175041198730469e-05s
Believability | Calculation of trust value for statusnet-lebsanft-org took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-lebsanft-org took 2.626323938369751s
Availability | SPARQL endpoint availability check for statusnet-legadolibre-com-ar took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-legadolibre-com-ar took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for statusnet-legadolibre-com-ar took 0.2609879970550537s
Reputation | Calculation of the PageRank for statusnet-legadolibre-com-ar took 0.020658254623413086s
Interlinking | Calculation of Degree of Connection for statusnet-legadolibre-com-ar took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-legadolibre-com-ar took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for statusnet-legadolibre-com-ar took 9.465217590332031e-05s
Believability | Calculation of trust value for statusnet-legadolibre-com-ar took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-legadolibre-com-ar took 2.5602049827575684s
Availability | SPARQL endpoint availability check for statusnet-linuxwrangling-com took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-linuxwrangling-com took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for statusnet-linuxwrangling-com took 0.26660728454589844s
Reputation | Calculation of the PageRank for statusnet-linuxwrangling-com took 0.02062511444091797s
Interlinking | Calculation of Degree of Connection for statusnet-linuxwrangling-com took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-linuxwrangling-com took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for statusnet-linuxwrangling-com took 0.00011563301086425781s
Believability | Calculation of trust value for statusnet-linuxwrangling-com took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-linuxwrangling-com took 2.4607787132263184s
Availability | SPARQL endpoint availability check for statusnet-ludost-net took 8.487701416015625e-05s
Availability | VoID file availability check for statusnet-ludost-net took 0.0007426738739013672s
Completeness | Calculation of interlinking completeness for statusnet-ludost-net took 0.2634751796722412s
Reputation | Calculation of the PageRank for statusnet-ludost-net took 0.02247762680053711s
Interlinking | Calculation of Degree of Connection for statusnet-ludost-net took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-ludost-net took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for statusnet-ludost-net took 5.8650970458984375e-05s
Believability | Calculation of trust value for statusnet-ludost-net took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-ludost-net took 3.7671151161193848s
Availability | SPARQL endpoint availability check for statusnet-lydiastench-com took 8.988380432128906e-05s
Availability | VoID file availability check for statusnet-lydiastench-com took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for statusnet-lydiastench-com took 0.2718498706817627s
Reputation | Calculation of the PageRank for statusnet-lydiastench-com took 0.022597312927246094s
Interlinking | Calculation of Degree of Connection for statusnet-lydiastench-com took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-lydiastench-com took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for statusnet-lydiastench-com took 0.00010156631469726562s
Believability | Calculation of trust value for statusnet-lydiastench-com took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-lydiastench-com took 2.440453052520752s
Availability | SPARQL endpoint availability check for statusnet-m-kuttner-com took 8.654594421386719e-05s
Availability | VoID file availability check for statusnet-m-kuttner-com took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for statusnet-m-kuttner-com took 0.26475048065185547s
Reputation | Calculation of the PageRank for statusnet-m-kuttner-com took 0.02205634117126465s
Interlinking | Calculation of Degree of Connection for statusnet-m-kuttner-com took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-m-kuttner-com took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for statusnet-m-kuttner-com took 5.602836608886719e-05s
Believability | Calculation of trust value for statusnet-m-kuttner-com took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-m-kuttner-com took 3.520066261291504s
Availability | SPARQL endpoint availability check for statusnet-macno-org took 8.654594421386719e-05s
Availability | VoID file availability check for statusnet-macno-org took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for statusnet-macno-org took 0.27062201499938965s
Reputation | Calculation of the PageRank for statusnet-macno-org took 0.020955801010131836s
Interlinking | Calculation of Degree of Connection for statusnet-macno-org took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-macno-org took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for statusnet-macno-org took 0.00014972686767578125s
Believability | Calculation of trust value for statusnet-macno-org took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-macno-org took 2.4588136672973633s
Availability | SPARQL endpoint availability check for statusnet-mamalibre-com-ar took 8.58306884765625e-05s
Availability | VoID file availability check for statusnet-mamalibre-com-ar took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for statusnet-mamalibre-com-ar took 0.26101088523864746s
Reputation | Calculation of the PageRank for statusnet-mamalibre-com-ar took 0.020862102508544922s
Interlinking | Calculation of Degree of Connection for statusnet-mamalibre-com-ar took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-mamalibre-com-ar took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for statusnet-mamalibre-com-ar took 6.937980651855469e-05s
Believability | Calculation of trust value for statusnet-mamalibre-com-ar took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-mamalibre-com-ar took 2.3994524478912354s
Availability | SPARQL endpoint availability check for statusnet-maymay-net took 8.678436279296875e-05s
Availability | VoID file availability check for statusnet-maymay-net took 0.0006718635559082031s
Completeness | Calculation of interlinking completeness for statusnet-maymay-net took 0.2742762565612793s
Reputation | Calculation of the PageRank for statusnet-maymay-net took 0.020485639572143555s
Interlinking | Calculation of Degree of Connection for statusnet-maymay-net took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for statusnet-maymay-net took 0.0007939338684082031s
Interlinking | Calculation of Clustering coefficient for statusnet-maymay-net took 9.846687316894531e-05s
Believability | Calculation of trust value for statusnet-maymay-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-maymay-net took 42.11802649497986s
Availability | SPARQL endpoint availability check for statusnet-morphtown-de took 7.724761962890625e-05s
Availability | VoID file availability check for statusnet-morphtown-de took 0.00034880638122558594s
Completeness | Calculation of interlinking completeness for statusnet-morphtown-de took 0.2523386478424072s
Reputation | Calculation of the PageRank for statusnet-morphtown-de took 0.020441055297851562s
Interlinking | Calculation of Degree of Connection for statusnet-morphtown-de took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for statusnet-morphtown-de took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for statusnet-morphtown-de took 0.00016832351684570312s
Believability | Calculation of trust value for statusnet-morphtown-de took 1.4543533325195312e-05s
INFO | --- Analysis for statusnet-morphtown-de took 2.401426315307617s
Availability | SPARQL endpoint availability check for statusnet-mrblog-nl took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-mrblog-nl took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for statusnet-mrblog-nl took 0.27144718170166016s
Reputation | Calculation of the PageRank for statusnet-mrblog-nl took 0.020577669143676758s
Interlinking | Calculation of Degree of Connection for statusnet-mrblog-nl took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-mrblog-nl took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for statusnet-mrblog-nl took 0.00010395050048828125s
Believability | Calculation of trust value for statusnet-mrblog-nl took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-mrblog-nl took 2.543383836746216s
Availability | SPARQL endpoint availability check for statusnet-mulestable-net took 9.036064147949219e-05s
Availability | VoID file availability check for statusnet-mulestable-net took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for statusnet-mulestable-net took 0.26587700843811035s
Reputation | Calculation of the PageRank for statusnet-mulestable-net took 0.020579099655151367s
Interlinking | Calculation of Degree of Connection for statusnet-mulestable-net took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-mulestable-net took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for statusnet-mulestable-net took 5.4836273193359375e-05s
Believability | Calculation of trust value for statusnet-mulestable-net took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-mulestable-net took 2.450624942779541s
Availability | SPARQL endpoint availability check for statusnet-my-status-tk took 6.318092346191406e-05s
Availability | VoID file availability check for statusnet-my-status-tk took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for statusnet-my-status-tk took 0.27042174339294434s
Reputation | Calculation of the PageRank for statusnet-my-status-tk took 0.020687341690063477s
Interlinking | Calculation of Degree of Connection for statusnet-my-status-tk took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-my-status-tk took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for statusnet-my-status-tk took 5.435943603515625e-05s
Believability | Calculation of trust value for statusnet-my-status-tk took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-my-status-tk took 2.620907783508301s
Availability | SPARQL endpoint availability check for statusnet-opensim-chat-eu took 0.0001342296600341797s
Availability | VoID file availability check for statusnet-opensim-chat-eu took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for statusnet-opensim-chat-eu took 0.2727341651916504s
Reputation | Calculation of the PageRank for statusnet-opensim-chat-eu took 0.02055048942565918s
Interlinking | Calculation of Degree of Connection for statusnet-opensim-chat-eu took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-opensim-chat-eu took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for statusnet-opensim-chat-eu took 0.00010824203491210938s
Believability | Calculation of trust value for statusnet-opensim-chat-eu took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-opensim-chat-eu took 2.444958448410034s
Availability | SPARQL endpoint availability check for statusnet-orangeseeds-org took 8.559226989746094e-05s
Availability | VoID file availability check for statusnet-orangeseeds-org took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for statusnet-orangeseeds-org took 0.2750086784362793s
Reputation | Calculation of the PageRank for statusnet-orangeseeds-org took 0.020644664764404297s
Interlinking | Calculation of Degree of Connection for statusnet-orangeseeds-org took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-orangeseeds-org took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for statusnet-orangeseeds-org took 5.698204040527344e-05s
Believability | Calculation of trust value for statusnet-orangeseeds-org took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-orangeseeds-org took 2.640186309814453s
Availability | SPARQL endpoint availability check for statusnet-otbm-fr took 5.7697296142578125e-05s
Availability | VoID file availability check for statusnet-otbm-fr took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for statusnet-otbm-fr took 0.2706015110015869s
Reputation | Calculation of the PageRank for statusnet-otbm-fr took 0.02170276641845703s
Interlinking | Calculation of Degree of Connection for statusnet-otbm-fr took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for statusnet-otbm-fr took 0.000980377197265625s
Interlinking | Calculation of Clustering coefficient for statusnet-otbm-fr took 8.296966552734375e-05s
Believability | Calculation of trust value for statusnet-otbm-fr took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-otbm-fr took 2.498601198196411s
Availability | SPARQL endpoint availability check for statusnet-ourcoffs-org-au took 4.482269287109375e-05s
Availability | VoID file availability check for statusnet-ourcoffs-org-au took 0.0006098747253417969s
Completeness | Calculation of interlinking completeness for statusnet-ourcoffs-org-au took 0.26201844215393066s
Reputation | Calculation of the PageRank for statusnet-ourcoffs-org-au took 0.021207571029663086s
Interlinking | Calculation of Degree of Connection for statusnet-ourcoffs-org-au took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-ourcoffs-org-au took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for statusnet-ourcoffs-org-au took 8.416175842285156e-05s
Believability | Calculation of trust value for statusnet-ourcoffs-org-au took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-ourcoffs-org-au took 2.5073773860931396s
Availability | SPARQL endpoint availability check for statusnet-panda-id-au took 0.00011277198791503906s
Availability | VoID file availability check for statusnet-panda-id-au took 0.0006279945373535156s
Completeness | Calculation of interlinking completeness for statusnet-panda-id-au took 0.26341867446899414s
Reputation | Calculation of the PageRank for statusnet-panda-id-au took 0.020408153533935547s
Interlinking | Calculation of Degree of Connection for statusnet-panda-id-au took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-panda-id-au took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for statusnet-panda-id-au took 4.76837158203125e-05s
Believability | Calculation of trust value for statusnet-panda-id-au took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-panda-id-au took 3.1815247535705566s
Availability | SPARQL endpoint availability check for statusnet-piana-eu took 8.893013000488281e-05s
Availability | VoID file availability check for statusnet-piana-eu took 0.0006787776947021484s
Completeness | Calculation of interlinking completeness for statusnet-piana-eu took 0.2715737819671631s
Reputation | Calculation of the PageRank for statusnet-piana-eu took 0.02051520347595215s
Interlinking | Calculation of Degree of Connection for statusnet-piana-eu took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-piana-eu took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for statusnet-piana-eu took 9.775161743164062e-05s
Believability | Calculation of trust value for statusnet-piana-eu took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-piana-eu took 2.6027886867523193s
Availability | SPARQL endpoint availability check for statusnet-planet-libre-org took 8.797645568847656e-05s
Availability | VoID file availability check for statusnet-planet-libre-org took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for statusnet-planet-libre-org took 0.2641029357910156s
Reputation | Calculation of the PageRank for statusnet-planet-libre-org took 0.022208452224731445s
Interlinking | Calculation of Degree of Connection for statusnet-planet-libre-org took 1.52587890625e-05s
Interlinking | Calculation of Centrality for statusnet-planet-libre-org took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for statusnet-planet-libre-org took 8.058547973632812e-05s
Believability | Calculation of trust value for statusnet-planet-libre-org took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-planet-libre-org took 2.505972385406494s
Availability | SPARQL endpoint availability check for statusnet-postblue-info took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-postblue-info took 0.0005745887756347656s
Completeness | Calculation of interlinking completeness for statusnet-postblue-info took 0.26488828659057617s
Reputation | Calculation of the PageRank for statusnet-postblue-info took 0.021164894104003906s
Interlinking | Calculation of Degree of Connection for statusnet-postblue-info took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for statusnet-postblue-info took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for statusnet-postblue-info took 0.00022602081298828125s
Believability | Calculation of trust value for statusnet-postblue-info took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-postblue-info took 2.6570513248443604s
Availability | SPARQL endpoint availability check for statusnet-progval-net took 8.821487426757812e-05s
Availability | VoID file availability check for statusnet-progval-net took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for statusnet-progval-net took 0.28870153427124023s
Reputation | Calculation of the PageRank for statusnet-progval-net took 0.020730972290039062s
Interlinking | Calculation of Degree of Connection for statusnet-progval-net took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-progval-net took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for statusnet-progval-net took 7.987022399902344e-05s
Believability | Calculation of trust value for statusnet-progval-net took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-progval-net took 2.583477735519409s
Availability | SPARQL endpoint availability check for statusnet-qdnx-org took 8.463859558105469e-05s
Availability | VoID file availability check for statusnet-qdnx-org took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for statusnet-qdnx-org took 0.26150083541870117s
Reputation | Calculation of the PageRank for statusnet-qdnx-org took 0.020984649658203125s
Interlinking | Calculation of Degree of Connection for statusnet-qdnx-org took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-qdnx-org took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for statusnet-qdnx-org took 0.00011396408081054688s
Believability | Calculation of trust value for statusnet-qdnx-org took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-qdnx-org took 3.099672794342041s
Availability | SPARQL endpoint availability check for statusnet-qth-fr took 8.916854858398438e-05s
Availability | VoID file availability check for statusnet-qth-fr took 0.0005342960357666016s
Completeness | Calculation of interlinking completeness for statusnet-qth-fr took 0.26251935958862305s
Reputation | Calculation of the PageRank for statusnet-qth-fr took 0.02067422866821289s
Interlinking | Calculation of Degree of Connection for statusnet-qth-fr took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-qth-fr took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for statusnet-qth-fr took 6.318092346191406e-05s
Believability | Calculation of trust value for statusnet-qth-fr took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-qth-fr took 3.2756779193878174s
Availability | SPARQL endpoint availability check for statusnet-quitter-se took 5.412101745605469e-05s
Availability | VoID file availability check for statusnet-quitter-se took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for statusnet-quitter-se took 0.27248144149780273s
Reputation | Calculation of the PageRank for statusnet-quitter-se took 0.020420551300048828s
Interlinking | Calculation of Degree of Connection for statusnet-quitter-se took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-quitter-se took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for statusnet-quitter-se took 0.00021576881408691406s
Believability | Calculation of trust value for statusnet-quitter-se took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-quitter-se took 5.410659313201904s
Availability | SPARQL endpoint availability check for statusnet-rainbowdash-net took 8.702278137207031e-05s
Availability | VoID file availability check for statusnet-rainbowdash-net took 0.0005667209625244141s
Completeness | Calculation of interlinking completeness for statusnet-rainbowdash-net took 0.266711950302124s
Reputation | Calculation of the PageRank for statusnet-rainbowdash-net took 0.023212671279907227s
Interlinking | Calculation of Degree of Connection for statusnet-rainbowdash-net took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for statusnet-rainbowdash-net took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for statusnet-rainbowdash-net took 0.00010609626770019531s
Believability | Calculation of trust value for statusnet-rainbowdash-net took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-rainbowdash-net took 2.621741533279419s
Availability | SPARQL endpoint availability check for statusnet-recit-org took 9.655952453613281e-05s
Availability | VoID file availability check for statusnet-recit-org took 0.0004515647888183594s
Completeness | Calculation of interlinking completeness for statusnet-recit-org took 0.29751062393188477s
Reputation | Calculation of the PageRank for statusnet-recit-org took 0.021061420440673828s
Interlinking | Calculation of Degree of Connection for statusnet-recit-org took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for statusnet-recit-org took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for statusnet-recit-org took 5.984306335449219e-05s
Believability | Calculation of trust value for statusnet-recit-org took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-recit-org took 265.3393323421478s
Availability | SPARQL endpoint availability check for statusnet-russwurm-org took 9.870529174804688e-05s
Availability | VoID file availability check for statusnet-russwurm-org took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for statusnet-russwurm-org took 0.27868008613586426s
Reputation | Calculation of the PageRank for statusnet-russwurm-org took 0.020768404006958008s
Interlinking | Calculation of Degree of Connection for statusnet-russwurm-org took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for statusnet-russwurm-org took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for statusnet-russwurm-org took 0.0001480579376220703s
Believability | Calculation of trust value for statusnet-russwurm-org took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-russwurm-org took 133.32090163230896s
Availability | SPARQL endpoint availability check for statusnet-samnoble-org took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-samnoble-org took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for statusnet-samnoble-org took 0.2712733745574951s
Reputation | Calculation of the PageRank for statusnet-samnoble-org took 0.020746707916259766s
Interlinking | Calculation of Degree of Connection for statusnet-samnoble-org took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for statusnet-samnoble-org took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for statusnet-samnoble-org took 7.939338684082031e-05s
Believability | Calculation of trust value for statusnet-samnoble-org took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-samnoble-org took 4.826775550842285s
Availability | SPARQL endpoint availability check for statusnet-schiessle-org took 8.797645568847656e-05s
Availability | VoID file availability check for statusnet-schiessle-org took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for statusnet-schiessle-org took 0.2630290985107422s
Reputation | Calculation of the PageRank for statusnet-schiessle-org took 0.021071195602416992s
Interlinking | Calculation of Degree of Connection for statusnet-schiessle-org took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-schiessle-org took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for statusnet-schiessle-org took 8.416175842285156e-05s
Believability | Calculation of trust value for statusnet-schiessle-org took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-schiessle-org took 2.6104798316955566s
Availability | SPARQL endpoint availability check for statusnet-scoffoni-net took 0.00011515617370605469s
Availability | VoID file availability check for statusnet-scoffoni-net took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for statusnet-scoffoni-net took 0.2646763324737549s
Reputation | Calculation of the PageRank for statusnet-scoffoni-net took 0.022527217864990234s
Interlinking | Calculation of Degree of Connection for statusnet-scoffoni-net took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for statusnet-scoffoni-net took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for statusnet-scoffoni-net took 9.679794311523438e-05s
Believability | Calculation of trust value for statusnet-scoffoni-net took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-scoffoni-net took 2.478160858154297s
Availability | SPARQL endpoint availability check for statusnet-sebseb01-net took 0.00010156631469726562s
Availability | VoID file availability check for statusnet-sebseb01-net took 0.0004413127899169922s
Completeness | Calculation of interlinking completeness for statusnet-sebseb01-net took 0.26656413078308105s
Reputation | Calculation of the PageRank for statusnet-sebseb01-net took 0.022288084030151367s
Interlinking | Calculation of Degree of Connection for statusnet-sebseb01-net took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for statusnet-sebseb01-net took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for statusnet-sebseb01-net took 6.532669067382812e-05s
Believability | Calculation of trust value for statusnet-sebseb01-net took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-sebseb01-net took 2.513972043991089s
Availability | SPARQL endpoint availability check for statusnet-shnoulle-net took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-shnoulle-net took 0.0006792545318603516s
Completeness | Calculation of interlinking completeness for statusnet-shnoulle-net took 0.27463340759277344s
Reputation | Calculation of the PageRank for statusnet-shnoulle-net took 0.022270679473876953s
Interlinking | Calculation of Degree of Connection for statusnet-shnoulle-net took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-shnoulle-net took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for statusnet-shnoulle-net took 7.390975952148438e-05s
Believability | Calculation of trust value for statusnet-shnoulle-net took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-shnoulle-net took 3.35849666595459s
Availability | SPARQL endpoint availability check for statusnet-skilledtests-com took 8.440017700195312e-05s
Availability | VoID file availability check for statusnet-skilledtests-com took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for statusnet-skilledtests-com took 0.27759575843811035s
Reputation | Calculation of the PageRank for statusnet-skilledtests-com took 0.020870685577392578s
Interlinking | Calculation of Degree of Connection for statusnet-skilledtests-com took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-skilledtests-com took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for statusnet-skilledtests-com took 0.0002105236053466797s
Believability | Calculation of trust value for statusnet-skilledtests-com took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-skilledtests-com took 2.9890730381011963s
Availability | SPARQL endpoint availability check for statusnet-somsants-net took 8.726119995117188e-05s
Availability | VoID file availability check for statusnet-somsants-net took 0.0005106925964355469s
Completeness | Calculation of interlinking completeness for statusnet-somsants-net took 0.2731647491455078s
Reputation | Calculation of the PageRank for statusnet-somsants-net took 0.02089071273803711s
Interlinking | Calculation of Degree of Connection for statusnet-somsants-net took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-somsants-net took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for statusnet-somsants-net took 0.00010442733764648438s
Believability | Calculation of trust value for statusnet-somsants-net took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-somsants-net took 2.4737610816955566s
Availability | SPARQL endpoint availability check for statusnet-soucy-cc took 8.893013000488281e-05s
Availability | VoID file availability check for statusnet-soucy-cc took 0.0005860328674316406s
Completeness | Calculation of interlinking completeness for statusnet-soucy-cc took 0.2671701908111572s
Reputation | Calculation of the PageRank for statusnet-soucy-cc took 0.02086949348449707s
Interlinking | Calculation of Degree of Connection for statusnet-soucy-cc took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-soucy-cc took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for statusnet-soucy-cc took 0.00013947486877441406s
Believability | Calculation of trust value for statusnet-soucy-cc took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-soucy-cc took 4.174428939819336s
Availability | SPARQL endpoint availability check for statusnet-spip-org took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-spip-org took 0.0005071163177490234s
Completeness | Calculation of interlinking completeness for statusnet-spip-org took 0.2720823287963867s
Reputation | Calculation of the PageRank for statusnet-spip-org took 0.020631790161132812s
Interlinking | Calculation of Degree of Connection for statusnet-spip-org took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for statusnet-spip-org took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for statusnet-spip-org took 6.103515625e-05s
Believability | Calculation of trust value for statusnet-spip-org took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-spip-org took 3.2754831314086914s
Availability | SPARQL endpoint availability check for statusnet-spraci-org took 8.511543273925781e-05s
Availability | VoID file availability check for statusnet-spraci-org took 0.0006744861602783203s
Completeness | Calculation of interlinking completeness for statusnet-spraci-org took 0.26358485221862793s
Reputation | Calculation of the PageRank for statusnet-spraci-org took 0.021087646484375s
Interlinking | Calculation of Degree of Connection for statusnet-spraci-org took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for statusnet-spraci-org took 0.0010209083557128906s
Interlinking | Calculation of Clustering coefficient for statusnet-spraci-org took 8.440017700195312e-05s
Believability | Calculation of trust value for statusnet-spraci-org took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-spraci-org took 5.533838987350464s
Availability | SPARQL endpoint availability check for statusnet-ssweeny-net took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-ssweeny-net took 0.0011560916900634766s
Completeness | Calculation of interlinking completeness for statusnet-ssweeny-net took 0.25890231132507324s
Reputation | Calculation of the PageRank for statusnet-ssweeny-net took 0.022639989852905273s
Interlinking | Calculation of Degree of Connection for statusnet-ssweeny-net took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-ssweeny-net took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for statusnet-ssweeny-net took 0.00011110305786132812s
Believability | Calculation of trust value for statusnet-ssweeny-net took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-ssweeny-net took 5.608354806900024s
Availability | SPARQL endpoint availability check for statusnet-status-net took 8.749961853027344e-05s
Availability | VoID file availability check for statusnet-status-net took 0.0005509853363037109s
Completeness | Calculation of interlinking completeness for statusnet-status-net took 0.27238965034484863s
Reputation | Calculation of the PageRank for statusnet-status-net took 0.020951271057128906s
Interlinking | Calculation of Degree of Connection for statusnet-status-net took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for statusnet-status-net took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for statusnet-status-net took 0.00021958351135253906s
Believability | Calculation of trust value for statusnet-status-net took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-status-net took 3.3815248012542725s
Availability | SPARQL endpoint availability check for statusnet-sweetiebelle-net took 0.00012826919555664062s
Availability | VoID file availability check for statusnet-sweetiebelle-net took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for statusnet-sweetiebelle-net took 0.2617664337158203s
Reputation | Calculation of the PageRank for statusnet-sweetiebelle-net took 0.02085137367248535s
Interlinking | Calculation of Degree of Connection for statusnet-sweetiebelle-net took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-sweetiebelle-net took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for statusnet-sweetiebelle-net took 5.53131103515625e-05s
Believability | Calculation of trust value for statusnet-sweetiebelle-net took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-sweetiebelle-net took 2.436558961868286s
Availability | SPARQL endpoint availability check for statusnet-tekk-com-ar took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-tekk-com-ar took 0.0004363059997558594s
Completeness | Calculation of interlinking completeness for statusnet-tekk-com-ar took 0.2757840156555176s
Reputation | Calculation of the PageRank for statusnet-tekk-com-ar took 0.02078557014465332s
Interlinking | Calculation of Degree of Connection for statusnet-tekk-com-ar took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-tekk-com-ar took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for statusnet-tekk-com-ar took 9.298324584960938e-05s
Believability | Calculation of trust value for statusnet-tekk-com-ar took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-tekk-com-ar took 2.450429916381836s
Availability | SPARQL endpoint availability check for statusnet-thelovebug-org took 8.845329284667969e-05s
Availability | VoID file availability check for statusnet-thelovebug-org took 0.0005457401275634766s
Completeness | Calculation of interlinking completeness for statusnet-thelovebug-org took 0.3074772357940674s
Reputation | Calculation of the PageRank for statusnet-thelovebug-org took 0.020865917205810547s
Interlinking | Calculation of Degree of Connection for statusnet-thelovebug-org took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for statusnet-thelovebug-org took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for statusnet-thelovebug-org took 0.00012993812561035156s
Believability | Calculation of trust value for statusnet-thelovebug-org took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-thelovebug-org took 2.6600704193115234s
Availability | SPARQL endpoint availability check for statusnet-thornton2-com took 9.489059448242188e-05s
Availability | VoID file availability check for statusnet-thornton2-com took 0.0005514621734619141s
Completeness | Calculation of interlinking completeness for statusnet-thornton2-com took 0.2655527591705322s
Reputation | Calculation of the PageRank for statusnet-thornton2-com took 0.0206906795501709s
Interlinking | Calculation of Degree of Connection for statusnet-thornton2-com took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-thornton2-com took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for statusnet-thornton2-com took 7.772445678710938e-05s
Believability | Calculation of trust value for statusnet-thornton2-com took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-thornton2-com took 6.791159391403198s
Availability | SPARQL endpoint availability check for statusnet-timttmy-co-uk took 4.5299530029296875e-05s
Availability | VoID file availability check for statusnet-timttmy-co-uk took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for statusnet-timttmy-co-uk took 0.27866482734680176s
Reputation | Calculation of the PageRank for statusnet-timttmy-co-uk took 0.020645856857299805s
Interlinking | Calculation of Degree of Connection for statusnet-timttmy-co-uk took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for statusnet-timttmy-co-uk took 0.0009167194366455078s
Interlinking | Calculation of Clustering coefficient for statusnet-timttmy-co-uk took 0.00012254714965820312s
Believability | Calculation of trust value for statusnet-timttmy-co-uk took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-timttmy-co-uk took 2.7037501335144043s
Availability | SPARQL endpoint availability check for statusnet-tl1n-com took 4.673004150390625e-05s
Availability | VoID file availability check for statusnet-tl1n-com took 0.0006194114685058594s
Completeness | Calculation of interlinking completeness for statusnet-tl1n-com took 0.2651338577270508s
Reputation | Calculation of the PageRank for statusnet-tl1n-com took 0.02080082893371582s
Interlinking | Calculation of Degree of Connection for statusnet-tl1n-com took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-tl1n-com took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for statusnet-tl1n-com took 4.172325134277344e-05s
Believability | Calculation of trust value for statusnet-tl1n-com took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-tl1n-com took 4.576496839523315s
Availability | SPARQL endpoint availability check for statusnet-tschlotfeldt-de took 0.00010991096496582031s
Availability | VoID file availability check for statusnet-tschlotfeldt-de took 0.0005757808685302734s
Completeness | Calculation of interlinking completeness for statusnet-tschlotfeldt-de took 0.2714531421661377s
Reputation | Calculation of the PageRank for statusnet-tschlotfeldt-de took 0.020728588104248047s
Interlinking | Calculation of Degree of Connection for statusnet-tschlotfeldt-de took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for statusnet-tschlotfeldt-de took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for statusnet-tschlotfeldt-de took 6.651878356933594e-05s
Believability | Calculation of trust value for statusnet-tschlotfeldt-de took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-tschlotfeldt-de took 2.6285006999969482s
Availability | SPARQL endpoint availability check for statusnet-uni-siegen-de took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-uni-siegen-de took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for statusnet-uni-siegen-de took 0.2618398666381836s
Reputation | Calculation of the PageRank for statusnet-uni-siegen-de took 0.021752357482910156s
Interlinking | Calculation of Degree of Connection for statusnet-uni-siegen-de took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-uni-siegen-de took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for statusnet-uni-siegen-de took 3.814697265625e-05s
Believability | Calculation of trust value for statusnet-uni-siegen-de took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-uni-siegen-de took 2.6616902351379395s
Availability | SPARQL endpoint availability check for Super Terminology System(STEAK) - Linked Open Data took 9.012222290039062e-05s
Availability | VoID file availability check for Super Terminology System(STEAK) - Linked Open Data took 0.0005505084991455078s
Completeness | Calculation of interlinking completeness for Super Terminology System(STEAK) - Linked Open Data took 0.2689807415008545s
Reputation | Calculation of the PageRank for Super Terminology System(STEAK) - Linked Open Data took 0.021152734756469727s
Interlinking | Calculation of Degree of Connection for Super Terminology System(STEAK) - Linked Open Data took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Super Terminology System(STEAK) - Linked Open Data took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Super Terminology System(STEAK) - Linked Open Data took 3.123283386230469e-05s
Believability | Calculation of trust value for Super Terminology System(STEAK) - Linked Open Data took 1.2636184692382812e-05s
INFO | --- Analysis for steak took 2.758981227874756s
Availability | SPARQL endpoint availability check for RAMEAU subject headings (STITCH) took 8.630752563476562e-05s
Availability | VoID file availability check for RAMEAU subject headings (STITCH) took 0.0005445480346679688s
Completeness | Calculation of interlinking completeness for RAMEAU subject headings (STITCH) took 0.2707192897796631s
Reputation | Calculation of the PageRank for RAMEAU subject headings (STITCH) took 0.021054744720458984s
Interlinking | Calculation of Degree of Connection for RAMEAU subject headings (STITCH) took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for RAMEAU subject headings (STITCH) took 0.0009334087371826172s
Interlinking | Calculation of Clustering coefficient for RAMEAU subject headings (STITCH) took 6.365776062011719e-05s
Believability | Calculation of trust value for RAMEAU subject headings (STITCH) took 1.239776611328125e-05s
INFO | --- Analysis for stitch-rameau took 3.923602342605591s
Availability | SPARQL endpoint availability check for Stone Tech Square took 0.9160811901092529s
Availability | VoID file availability check for Stone Tech Square took 0.0006940364837646484s
Completeness | Calculation of interlinking completeness for Stone Tech Square took 0.2668461799621582s
Reputation | Calculation of the PageRank for Stone Tech Square took 0.024522781372070312s
Interlinking | Calculation of Degree of Connection for Stone Tech Square took 2.288818359375e-05s
Interlinking | Calculation of Centrality for Stone Tech Square took 0.0009038448333740234s
Interlinking | Calculation of Clustering coefficient for Stone Tech Square took 1.4543533325195312e-05s
Believability | Calculation of trust value for Stone Tech Square took 1.2159347534179688e-05s
INFO | --- Analysis for stone-tech-square-data took 6.243532419204712s
Availability | SPARQL endpoint availability check for STW Thesaurus for Economics took 0.39191341400146484s
Availability | VoID file availability check for STW Thesaurus for Economics took 0.0009489059448242188s
Extra | Recovery of all triples for STW Thesaurus for Economics took 17.61918354034424s
Performance | Total latancy measurement for STW Thesaurus for Economics took 1.0858492851257324s
Amount of data | Number of triples check for STW Thesaurus for Economics took 0.5843799114227295s
Interoperability | New terms check for STW Thesaurus for Economics took 1.5505619049072266s
Versatility | Languages check for STW Thesaurus for Economics took 1.4560976028442383s
Interpretability | Number of blank nodes check for STW Thesaurus for Economics took 0.43788647651672363s
Security | Check HTTPS for STW Thesaurus for Economics took 0.1548140048980713s
Interpretability | RDF structures check for STW Thesaurus for Economics took 0.2187037467956543s
Versatility | Serialization formats check for STW Thesaurus for Economics took 0.22064566612243652s
Availability | RDF dump link check for STW Thesaurus for Economics took 0.217146635055542s
License | MR license check for STW Thesaurus for Economics took 0.22345757484436035s
License | HR license check for STW Thesaurus for Economics took 2.447718620300293s
Amount of data | Number of property check for STW Thesaurus for Economics took 0.23807907104492188s
Understandability | Number of label check for STW Thesaurus for Economics took 0.6101415157318115s
Understandability | URI regex check for STW Thesaurus for Economics took 0.43689537048339844s
Understandability | Vocabs check for STW Thesaurus for Economics took 0.21724796295166016s
Verifiability | Authors check for STW Thesaurus for Economics took 0.2270979881286621s
Verifiability | Publishers check for STW Thesaurus for Economics took 0.2399282455444336s
Performance | Throughput check for STW Thesaurus for Economics took 12.586504936218262s
Amount of data | Check the number of entities for STW Thesaurus for Economics took 0.7094180583953857s
Verifiability | Contribs. check for STW Thesaurus for Economics took 0.21962761878967285s
Interlinking | sameAs chians check for STW Thesaurus for Economics took 0.2388010025024414s
Interlinking | skos check for STW Thesaurus for Economics took 0.3002619743347168s
Interlinking | skos check for STW Thesaurus for Economics took 0.2742769718170166s
Timeliness | dataset update frequency check for STW Thesaurus for Economics took 0.22040748596191406s
Currency | Creation date check for STW Thesaurus for Economics took 0.4604921340942383s
Currency | Modification date check for STW Thesaurus for Economics took 0.4580049514770508s
Rep.Conc. | URIs length for STW Thesaurus for Economics took 7.32059907913208s
Interoperability | New vocabularies check for STW Thesaurus for Economics took 445.85977244377136s
Consistency | Deprecated classes/propertiers check for STW Thesaurus for Economics took 0.23399043083190918s
Accuracy | Check Functional Property for STW Thesaurus for Economics took 0.2215099334716797s
Accuracy | Check Inverse Functional Property for STW Thesaurus for Economics took 0.24036145210266113s
Accuracy | Check Empty annotation labels for STW Thesaurus for Economics took 4.712549686431885s
Accuracy | Check White space in annotation for STW Thesaurus for Economics took 1.0385527610778809s
Accuracy | Check Datatype consistency for STW Thesaurus for Economics took 2.3333795070648193s
Consistency | Disjoint class check for STW Thesaurus for Economics took 0.23818683624267578s
Consistency | Check Misplaced properties for STW Thesaurus for Economics took 1.2056055068969727s
Consistency | Check Ontology hijacking for STW Thesaurus for Economics took 1.713054895401001s
Consistency | Check Invalid usage of undefined classes for STW Thesaurus for Economics took 1.3340258598327637s
Consistency | Check Invalid usage of undefined properties for STW Thesaurus for Economics took 2.3156092166900635s
Conciseness | Check Extensional conciseness for STW Thesaurus for Economics took 1.630444049835205s
Conciseness | Check Intensional conciseness for STW Thesaurus for Economics took 0.2330338954925537s
Security | Sign check for STW Thesaurus for Economics took 0.22779393196105957s
Availability | Check URIs Dereferenciability for STW Thesaurus for Economics took 2271.852137327194s
Completeness | Calculation of interlinking completeness for STW Thesaurus for Economics took 0.6613204479217529s
Reputation | Calculation of the PageRank for STW Thesaurus for Economics took 0.020643234252929688s
Interlinking | Calculation of Degree of Connection for STW Thesaurus for Economics took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for STW Thesaurus for Economics took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for STW Thesaurus for Economics took 0.00011563301086425781s
Interoperability | Check the re-using of existing vocabs for STW Thesaurus for Economics took 15.086150646209717s
Believability | Calculation of trust value for STW Thesaurus for Economics took 7.152557373046875e-06s
INFO | --- Analysis for stw-thesaurus-for-economics took 2824.7791831493378s
Availability | SPARQL endpoint availability check for SudershanTech took 8.916854858398438e-05s
Availability | VoID file availability check for SudershanTech took 0.0005071163177490234s
Completeness | Calculation of interlinking completeness for SudershanTech took 0.2749519348144531s
Reputation | Calculation of the PageRank for SudershanTech took 0.020620107650756836s
Interlinking | Calculation of Degree of Connection for SudershanTech took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for SudershanTech took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for SudershanTech took 3.147125244140625e-05s
Believability | Calculation of trust value for SudershanTech took 1.2874603271484375e-05s
INFO | --- Analysis for SudershanTech took 2.410837173461914s
Availability | SPARQL endpoint availability check for Sudoc bibliographic data took 0.7709085941314697s
Availability | VoID file availability check for Sudoc bibliographic data took 0.0005784034729003906s
Completeness | Calculation of interlinking completeness for Sudoc bibliographic data took 0.2697732448577881s
Reputation | Calculation of the PageRank for Sudoc bibliographic data took 0.022036075592041016s
Interlinking | Calculation of Degree of Connection for Sudoc bibliographic data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Sudoc bibliographic data took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Sudoc bibliographic data took 5.245208740234375e-05s
Believability | Calculation of trust value for Sudoc bibliographic data took 1.239776611328125e-05s
INFO | --- Analysis for sudocfr took 7.148455619812012s
Availability | SPARQL endpoint availability check for Suface Forestière Mondiale 1990-2016 took 1.0034105777740479s
Availability | VoID file availability check for Suface Forestière Mondiale 1990-2016 took 0.0003998279571533203s
Extra | Recovery of all triples for Suface Forestière Mondiale 1990-2016 took 24.66094136238098s
Performance | Total latancy measurement for Suface Forestière Mondiale 1990-2016 took 2.6789357662200928s
Amount of data | Number of triples check for Suface Forestière Mondiale 1990-2016 took 1.4662284851074219s
Interoperability | New terms check for Suface Forestière Mondiale 1990-2016 took 2.918259859085083s
Versatility | Languages check for Suface Forestière Mondiale 1990-2016 took 2.7537600994110107s
Interpretability | Number of blank nodes check for Suface Forestière Mondiale 1990-2016 took 1.2062127590179443s
Interpretability | RDF structures check for Suface Forestière Mondiale 1990-2016 took 0.548224925994873s
Versatility | Serialization formats check for Suface Forestière Mondiale 1990-2016 took 0.5747063159942627s
Availability | RDF dump link check for Suface Forestière Mondiale 1990-2016 took 0.5343201160430908s
License | MR license check for Suface Forestière Mondiale 1990-2016 took 0.5427029132843018s
License | HR license check for Suface Forestière Mondiale 1990-2016 took 9.052563428878784s
Amount of data | Number of property check for Suface Forestière Mondiale 1990-2016 took 0.576758861541748s
Understandability | Number of label check for Suface Forestière Mondiale 1990-2016 took 0.6812307834625244s
Understandability | URI regex check for Suface Forestière Mondiale 1990-2016 took 1.0775744915008545s
Understandability | Vocabs check for Suface Forestière Mondiale 1990-2016 took 0.5456054210662842s
Verifiability | Authors check for Suface Forestière Mondiale 1990-2016 took 0.5278792381286621s
Verifiability | Publishers check for Suface Forestière Mondiale 1990-2016 took 0.5254857540130615s
Performance | Throughput check for Suface Forestière Mondiale 1990-2016 took 10.628647565841675s
Amount of data | Check the number of entities for Suface Forestière Mondiale 1990-2016 took 9.489059448242188e-05s
Verifiability | Contribs. check for Suface Forestière Mondiale 1990-2016 took 0.5302035808563232s
Interlinking | sameAs chians check for Suface Forestière Mondiale 1990-2016 took 0.5507533550262451s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.6163351535797119s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.5933759212493896s
Timeliness | dataset update frequency check for Suface Forestière Mondiale 1990-2016 took 0.5334193706512451s
Currency | Creation date check for Suface Forestière Mondiale 1990-2016 took 1.0923972129821777s
Currency | Modification date check for Suface Forestière Mondiale 1990-2016 took 1.0735716819763184s
Rep.Conc. | URIs length for Suface Forestière Mondiale 1990-2016 took 38.41398000717163s
Interoperability | New vocabularies check for Suface Forestière Mondiale 1990-2016 took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Suface Forestière Mondiale 1990-2016 took 0.5279026031494141s
Accuracy | Check Functional Property for Suface Forestière Mondiale 1990-2016 took 0.5246412754058838s
Accuracy | Check Inverse Functional Property for Suface Forestière Mondiale 1990-2016 took 0.5309865474700928s
Accuracy | Check Empty annotation labels for Suface Forestière Mondiale 1990-2016 took 3.3393027782440186s
Accuracy | Check White space in annotation for Suface Forestière Mondiale 1990-2016 took 0.37694525718688965s
Consistency | Disjoint class check for Suface Forestière Mondiale 1990-2016 took 0.5356669425964355s
Consistency | Check Misplaced properties for Suface Forestière Mondiale 1990-2016 took 33.045196533203125s
Consistency | Misplaced classes for Suface Forestière Mondiale 1990-2016 took 9.404561996459961s
Consistency | Check Ontology hijacking for Suface Forestière Mondiale 1990-2016 took 300.44592094421387s
Consistency | Check Invalid usage of undefined properties for Suface Forestière Mondiale 1990-2016 took 24.35240411758423s
Conciseness | Check Extensional conciseness for Suface Forestière Mondiale 1990-2016 took 2.9455032348632812s
Conciseness | Check Intensional conciseness for Suface Forestière Mondiale 1990-2016 took 2.580711603164673s
Security | Sign check for Suface Forestière Mondiale 1990-2016 took 0.5618197917938232s
Availability | Check URIs Dereferenciability for Suface Forestière Mondiale 1990-2016 took 4527.610045433044s
Completeness | Calculation of interlinking completeness for Suface Forestière Mondiale 1990-2016 took 0.7090754508972168s
Reputation | Calculation of the PageRank for Suface Forestière Mondiale 1990-2016 took 0.02131509780883789s
Interlinking | Calculation of Degree of Connection for Suface Forestière Mondiale 1990-2016 took 6.747245788574219e-05s
Interlinking | Calculation of Centrality for Suface Forestière Mondiale 1990-2016 took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Suface Forestière Mondiale 1990-2016 took 0.00013399124145507812s
Interoperability | Check the re-using of existing vocabs for Suface Forestière Mondiale 1990-2016 took 1.430511474609375e-06s
Believability | Calculation of trust value for Suface Forestière Mondiale 1990-2016 took 1.0728836059570312e-05s
INFO | --- Analysis for Suface_Forestière_Mondiale_1990-2016 took 8132.950444698334s
Availability | SPARQL endpoint availability check for Surge Radio took 8.606910705566406e-05s
Availability | VoID file availability check for Surge Radio took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for Surge Radio took 0.26233744621276855s
Reputation | Calculation of the PageRank for Surge Radio took 0.02067399024963379s
Interlinking | Calculation of Degree of Connection for Surge Radio took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Surge Radio took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Surge Radio took 8.726119995117188e-05s
Believability | Calculation of trust value for Surge Radio took 9.775161743164062e-06s
INFO | --- Analysis for surge-radio took 3.4811623096466064s
Availability | SPARQL endpoint availability check for Soil & Water Assessment Tool took 4.220008850097656e-05s
Availability | VoID file availability check for Soil & Water Assessment Tool took 0.00061798095703125s
Completeness | Calculation of interlinking completeness for Soil & Water Assessment Tool took 0.2736046314239502s
Reputation | Calculation of the PageRank for Soil & Water Assessment Tool took 0.020682811737060547s
Interlinking | Calculation of Degree of Connection for Soil & Water Assessment Tool took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Soil & Water Assessment Tool took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Soil & Water Assessment Tool took 4.0531158447265625e-05s
Believability | Calculation of trust value for Soil & Water Assessment Tool took 1.0728836059570312e-05s
INFO | --- Analysis for SWAT took 86.25604248046875s
Availability | SPARQL endpoint availability check for Swedish Open Cultural Heritage took 0.00011587142944335938s
Availability | VoID file availability check for Swedish Open Cultural Heritage took 0.41602349281311035s
Completeness | Calculation of interlinking completeness for Swedish Open Cultural Heritage took 0.26260852813720703s
Reputation | Calculation of the PageRank for Swedish Open Cultural Heritage took 0.02049565315246582s
Interlinking | Calculation of Degree of Connection for Swedish Open Cultural Heritage took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Swedish Open Cultural Heritage took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Swedish Open Cultural Heritage took 6.961822509765625e-05s
Believability | Calculation of trust value for Swedish Open Cultural Heritage took 1.239776611328125e-05s
INFO | --- Analysis for swedish-open-cultural-heritage took 5.491570949554443s
Availability | SPARQL endpoint availability check for SweFN-RDF took 0.9180047512054443s
Availability | VoID file availability check for SweFN-RDF took 0.0005974769592285156s
Completeness | Calculation of interlinking completeness for SweFN-RDF took 0.26558542251586914s
Reputation | Calculation of the PageRank for SweFN-RDF took 0.02052903175354004s
Interlinking | Calculation of Degree of Connection for SweFN-RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SweFN-RDF took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for SweFN-RDF took 3.4809112548828125e-05s
Believability | Calculation of trust value for SweFN-RDF took 1.049041748046875e-05s
INFO | --- Analysis for swefn-rdf took 5.407155275344849s
Availability | SPARQL endpoint availability check for SwetoDblp took 5.602836608886719e-05s
Availability | VoID file availability check for SwetoDblp took 0.0006654262542724609s
Completeness | Calculation of interlinking completeness for SwetoDblp took 0.2799079418182373s
Reputation | Calculation of the PageRank for SwetoDblp took 0.02057504653930664s
Interlinking | Calculation of Degree of Connection for SwetoDblp took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SwetoDblp took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for SwetoDblp took 3.647804260253906e-05s
Believability | Calculation of trust value for SwetoDblp took 1.0728836059570312e-05s
INFO | --- Analysis for sweto-dblp took 22.754087686538696s
Availability | SPARQL endpoint availability check for Swift Vocabulary took 0.5013329982757568s
Availability | VoID file availability check for Swift Vocabulary took 0.0005767345428466797s
Extra | Recovery of all triples for Swift Vocabulary took 2.0472733974456787s
Performance | Total latancy measurement for Swift Vocabulary took 0.9406869411468506s
Amount of data | Number of triples check for Swift Vocabulary took 0.18774962425231934s
Interoperability | New terms check for Swift Vocabulary took 1.459653377532959s
Versatility | Languages check for Swift Vocabulary took 0.15008807182312012s
Interpretability | Number of blank nodes check for Swift Vocabulary took 0.1860642433166504s
Interpretability | RDF structures check for Swift Vocabulary took 0.19011759757995605s
Versatility | Serialization formats check for Swift Vocabulary took 0.19158506393432617s
Availability | RDF dump link check for Swift Vocabulary took 0.18906593322753906s
License | MR license check for Swift Vocabulary took 0.19129061698913574s
License | HR license check for Swift Vocabulary took 0.1581406593322754s
Amount of data | Number of property check for Swift Vocabulary took 0.15799260139465332s
Understandability | Number of label check for Swift Vocabulary took 0.16055655479431152s
Understandability | URI regex check for Swift Vocabulary took 0.3104543685913086s
Understandability | Vocabs check for Swift Vocabulary took 0.18737339973449707s
Verifiability | Authors check for Swift Vocabulary took 0.18888497352600098s
Verifiability | Publishers check for Swift Vocabulary took 0.18878722190856934s
Performance | Throughput check for Swift Vocabulary took 11.033086776733398s
Amount of data | Check the number of entities for Swift Vocabulary took 7.033348083496094e-05s
Verifiability | Contribs. check for Swift Vocabulary took 0.1873030662536621s
Interlinking | sameAs chians check for Swift Vocabulary took 0.18455028533935547s
Interlinking | skos check for Swift Vocabulary took 0.19106817245483398s
Interlinking | skos check for Swift Vocabulary took 0.1889479160308838s
Timeliness | dataset update frequency check for Swift Vocabulary took 0.20035910606384277s
Currency | Creation date check for Swift Vocabulary took 0.3829836845397949s
Currency | Modification date check for Swift Vocabulary took 0.37959766387939453s
Rep.Conc. | URIs length for Swift Vocabulary took 0.7707736492156982s
Interoperability | New vocabularies check for Swift Vocabulary took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for Swift Vocabulary took 0.18934035301208496s
Accuracy | Check Functional Property for Swift Vocabulary took 0.20965266227722168s
Accuracy | Check Inverse Functional Property for Swift Vocabulary took 0.18551397323608398s
Accuracy | Check Empty annotation labels for Swift Vocabulary took 0.3065066337585449s
Accuracy | Check White space in annotation for Swift Vocabulary took 0.0019578933715820312s
Accuracy | Check Datatype consistency for Swift Vocabulary took 0.03509402275085449s
Consistency | Disjoint class check for Swift Vocabulary took 0.18830537796020508s
Consistency | Check Misplaced properties for Swift Vocabulary took 0.42572712898254395s
Consistency | Misplaced classes for Swift Vocabulary took 0.26662230491638184s
Consistency | Check Ontology hijacking for Swift Vocabulary took 1.6068241596221924s
Consistency | Check Invalid usage of undefined classes for Swift Vocabulary took 1.3280940055847168s
Consistency | Check Invalid usage of undefined properties for Swift Vocabulary took 1.502056360244751s
Conciseness | Check Extensional conciseness for Swift Vocabulary took 0.030783653259277344s
Conciseness | Check Intensional conciseness for Swift Vocabulary took 0.15381121635437012s
Security | Sign check for Swift Vocabulary took 0.15664124488830566s
Availability | Check URIs Dereferenciability for Swift Vocabulary took 954.686395406723s
Completeness | Calculation of interlinking completeness for Swift Vocabulary took 0.5457353591918945s
Reputation | Calculation of the PageRank for Swift Vocabulary took 0.020986080169677734s
Interlinking | Calculation of Degree of Connection for Swift Vocabulary took 6.437301635742188e-05s
Interlinking | Calculation of Centrality for Swift Vocabulary took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Swift Vocabulary took 7.724761962890625e-05s
Interoperability | Check the re-using of existing vocabs for Swift Vocabulary took 1.9073486328125e-06s
Believability | Calculation of trust value for Swift Vocabulary took 1.1682510375976562e-05s
INFO | --- Analysis for Swift took 999.9499144554138s
Availability | SPARQL endpoint availability check for Symptoms in Chinese took 4.8160552978515625e-05s
Availability | VoID file availability check for Symptoms in Chinese took 0.0006401538848876953s
Completeness | Calculation of interlinking completeness for Symptoms in Chinese took 0.26990509033203125s
Reputation | Calculation of the PageRank for Symptoms in Chinese took 0.02042102813720703s
Interlinking | Calculation of Degree of Connection for Symptoms in Chinese took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Symptoms in Chinese took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Symptoms in Chinese took 3.7670135498046875e-05s
Believability | Calculation of trust value for Symptoms in Chinese took 1.0967254638671875e-05s
INFO | --- Analysis for symptoms-in-chinese took 52.54947543144226s
Availability | SPARQL endpoint availability check for National Digital Data Archive of Hungary (partial) took 0.33193182945251465s
Availability | VoID file availability check for National Digital Data Archive of Hungary (partial) took 0.0005726814270019531s
Extra | Recovery of all triples for National Digital Data Archive of Hungary (partial) took 0.42865467071533203s
Performance | Total latancy measurement for National Digital Data Archive of Hungary (partial) took 0.831918478012085s
Amount of data | Number of triples check for National Digital Data Archive of Hungary (partial) took 13.318503141403198s
Interoperability | New terms check for National Digital Data Archive of Hungary (partial) took 18.29881238937378s
Versatility | Languages check for National Digital Data Archive of Hungary (partial) took 0.19114899635314941s
Interpretability | Number of blank nodes check for National Digital Data Archive of Hungary (partial) took 3.5141749382019043s
Security | Check HTTPS for National Digital Data Archive of Hungary (partial) took 0.09968113899230957s
Interpretability | RDF structures check for National Digital Data Archive of Hungary (partial) took 0.38309144973754883s
Versatility | Serialization formats check for National Digital Data Archive of Hungary (partial) took 0.17978429794311523s
Availability | RDF dump link check for National Digital Data Archive of Hungary (partial) took 0.15924882888793945s
License | MR license check for National Digital Data Archive of Hungary (partial) took 0.2631669044494629s
License | HR license check for National Digital Data Archive of Hungary (partial) took 53.109302282333374s
Amount of data | Number of property check for National Digital Data Archive of Hungary (partial) took 0.4317440986633301s
Understandability | Number of label check for National Digital Data Archive of Hungary (partial) took 52.07529020309448s
Understandability | URI regex check for National Digital Data Archive of Hungary (partial) took 0.4798247814178467s
Understandability | Vocabs check for National Digital Data Archive of Hungary (partial) took 0.2399740219116211s
Verifiability | Authors check for National Digital Data Archive of Hungary (partial) took 0.1701970100402832s
Verifiability | Publishers check for National Digital Data Archive of Hungary (partial) took 0.16144514083862305s
Performance | Throughput check for National Digital Data Archive of Hungary (partial) took 11.021761894226074s
Amount of data | Check the number of entities for National Digital Data Archive of Hungary (partial) took 6.914138793945312e-05s
Verifiability | Contribs. check for National Digital Data Archive of Hungary (partial) took 0.23620080947875977s
Interlinking | sameAs chians check for National Digital Data Archive of Hungary (partial) took 0.5436570644378662s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 0.16043972969055176s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 0.15793895721435547s
Timeliness | dataset update frequency check for National Digital Data Archive of Hungary (partial) took 0.23387742042541504s
Currency | Creation date check for National Digital Data Archive of Hungary (partial) took 0.32883238792419434s
Currency | Modification date check for National Digital Data Archive of Hungary (partial) took 0.3181459903717041s
Rep.Conc. | URIs length for National Digital Data Archive of Hungary (partial) took 91.75376772880554s
Interoperability | New vocabularies check for National Digital Data Archive of Hungary (partial) took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for National Digital Data Archive of Hungary (partial) took 0.1618044376373291s
Accuracy | Check Functional Property for National Digital Data Archive of Hungary (partial) took 0.23757171630859375s
Accuracy | Check Inverse Functional Property for National Digital Data Archive of Hungary (partial) took 0.15799617767333984s
Accuracy | Check Empty annotation labels for National Digital Data Archive of Hungary (partial) took 0.2124490737915039s
Accuracy | Check White space in annotation for National Digital Data Archive of Hungary (partial) took 0.002678394317626953s
Accuracy | Check Datatype consistency for National Digital Data Archive of Hungary (partial) took 0.002103567123413086s
Consistency | Disjoint class check for National Digital Data Archive of Hungary (partial) took 0.15996742248535156s
Consistency | Check Misplaced properties for National Digital Data Archive of Hungary (partial) took 49.22019863128662s
Consistency | Misplaced classes for National Digital Data Archive of Hungary (partial) took 0.23685264587402344s
Consistency | Check Ontology hijacking for National Digital Data Archive of Hungary (partial) took 1.5859789848327637s
Consistency | Check Invalid usage of undefined classes for National Digital Data Archive of Hungary (partial) took 1.3071410655975342s
Consistency | Check Invalid usage of undefined properties for National Digital Data Archive of Hungary (partial) took 50.80024194717407s
Conciseness | Check Extensional conciseness for National Digital Data Archive of Hungary (partial) took 0.002128124237060547s
Conciseness | Check Intensional conciseness for National Digital Data Archive of Hungary (partial) took 0.36122822761535645s
Security | Sign check for National Digital Data Archive of Hungary (partial) took 0.1713869571685791s
Availability | Check URIs Dereferenciability for National Digital Data Archive of Hungary (partial) took 9.715754747390747s
Completeness | Calculation of interlinking completeness for National Digital Data Archive of Hungary (partial) took 0.29579758644104004s
Reputation | Calculation of the PageRank for National Digital Data Archive of Hungary (partial) took 0.02279806137084961s
Interlinking | Calculation of Degree of Connection for National Digital Data Archive of Hungary (partial) took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for National Digital Data Archive of Hungary (partial) took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for National Digital Data Archive of Hungary (partial) took 9.441375732421875e-05s
Interoperability | Check the re-using of existing vocabs for National Digital Data Archive of Hungary (partial) took 1.6689300537109375e-06s
Believability | Calculation of trust value for National Digital Data Archive of Hungary (partial) took 1.3828277587890625e-05s
INFO | --- Analysis for sztaki-lod took 548.1023344993591s
Availability | SPARQL endpoint availability check for Thesaurus for Graphic Materials (t4gm.info) took 8.702278137207031e-05s
Availability | VoID file availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for Thesaurus for Graphic Materials (t4gm.info) took 0.2671244144439697s
Reputation | Calculation of the PageRank for Thesaurus for Graphic Materials (t4gm.info) took 0.021967172622680664s
Interlinking | Calculation of Degree of Connection for Thesaurus for Graphic Materials (t4gm.info) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Thesaurus for Graphic Materials (t4gm.info) took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Thesaurus for Graphic Materials (t4gm.info) took 5.8650970458984375e-05s
Believability | Calculation of trust value for Thesaurus for Graphic Materials (t4gm.info) took 1.3113021850585938e-05s
INFO | --- Analysis for t4gm-info took 2.7141103744506836s
Availability | SPARQL endpoint availability check for tags2con delicious took 4.267692565917969e-05s
Availability | VoID file availability check for tags2con delicious took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for tags2con delicious took 0.2719571590423584s
Reputation | Calculation of the PageRank for tags2con delicious took 0.02053523063659668s
Interlinking | Calculation of Degree of Connection for tags2con delicious took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for tags2con delicious took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for tags2con delicious took 4.5299530029296875e-05s
Believability | Calculation of trust value for tags2con delicious took 1.1920928955078125e-05s
INFO | --- Analysis for tags2con-delicious took 44.6861526966095s
Availability | SPARQL endpoint availability check for Taiwan geographic names took 263.3595130443573s
Availability | VoID file availability check for Taiwan geographic names took 0.0007326602935791016s
Completeness | Calculation of interlinking completeness for Taiwan geographic names took 0.2827880382537842s
Reputation | Calculation of the PageRank for Taiwan geographic names took 0.020525455474853516s
Interlinking | Calculation of Degree of Connection for Taiwan geographic names took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Taiwan geographic names took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Taiwan geographic names took 7.319450378417969e-05s
Believability | Calculation of trust value for Taiwan geographic names took 1.3589859008789062e-05s
INFO | --- Analysis for taiwan-geographic-names took 667.3634307384491s
Availability | SPARQL endpoint availability check for Open Library data mirror in the Talis Platform took 9.274482727050781e-05s
Availability | VoID file availability check for Open Library data mirror in the Talis Platform took 0.0006325244903564453s
Completeness | Calculation of interlinking completeness for Open Library data mirror in the Talis Platform took 129.78476667404175s
Reputation | Calculation of the PageRank for Open Library data mirror in the Talis Platform took 0.021167755126953125s
Interlinking | Calculation of Degree of Connection for Open Library data mirror in the Talis Platform took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Open Library data mirror in the Talis Platform took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Open Library data mirror in the Talis Platform took 0.00011110305786132812s
Believability | Calculation of trust value for Open Library data mirror in the Talis Platform took 1.1205673217773438e-05s
INFO | --- Analysis for talis-openlibrary took 394.6922607421875s
Availability | SPARQL endpoint availability check for TaxonConcept Knowledge Base took 0.8396751880645752s
Availability | VoID file availability check for TaxonConcept Knowledge Base took 0.0006377696990966797s
Completeness | Calculation of interlinking completeness for TaxonConcept Knowledge Base took 0.2753579616546631s
Reputation | Calculation of the PageRank for TaxonConcept Knowledge Base took 0.02135300636291504s
Interlinking | Calculation of Degree of Connection for TaxonConcept Knowledge Base took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for TaxonConcept Knowledge Base took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for TaxonConcept Knowledge Base took 0.00012040138244628906s
Believability | Calculation of trust value for TaxonConcept Knowledge Base took 1.2874603271484375e-05s
INFO | --- Analysis for taxonconcept took 13.112771272659302s
Availability | SPARQL endpoint availability check for taxonconcept-assets took 4.38690185546875e-05s
Availability | VoID file availability check for taxonconcept-assets took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for taxonconcept-assets took 0.26799964904785156s
Reputation | Calculation of the PageRank for taxonconcept-assets took 0.021645307540893555s
Interlinking | Calculation of Degree of Connection for taxonconcept-assets took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for taxonconcept-assets took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for taxonconcept-assets took 8.511543273925781e-05s
Believability | Calculation of trust value for taxonconcept-assets took 1.1920928955078125e-05s
INFO | --- Analysis for taxonconcept-assets took 2.8379273414611816s
Availability | SPARQL endpoint availability check for taxonconcept-occurences took 4.553794860839844e-05s
Availability | VoID file availability check for taxonconcept-occurences took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for taxonconcept-occurences took 0.26879453659057617s
Reputation | Calculation of the PageRank for taxonconcept-occurences took 0.02149510383605957s
Interlinking | Calculation of Degree of Connection for taxonconcept-occurences took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for taxonconcept-occurences took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for taxonconcept-occurences took 5.459785461425781e-05s
Believability | Calculation of trust value for taxonconcept-occurences took 1.2636184692382812e-05s
INFO | --- Analysis for taxonconcept-occurences took 2.8224878311157227s
Availability | SPARQL endpoint availability check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 21.214959621429443s
Availability | VoID file availability check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.00061798095703125s
Completeness | Calculation of interlinking completeness for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.27440428733825684s
Reputation | Calculation of the PageRank for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.020680665969848633s
Interlinking | Calculation of Degree of Connection for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 5.0067901611328125e-05s
Believability | Calculation of trust value for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 1.1920928955078125e-05s
INFO | --- Analysis for taxref-ld took 74.81096005439758s
Availability | SPARQL endpoint availability check for The Cancer Genome Atlas took 262.43242144584656s
Availability | VoID file availability check for The Cancer Genome Atlas took 0.0006892681121826172s
Completeness | Calculation of interlinking completeness for The Cancer Genome Atlas took 0.27352070808410645s
Reputation | Calculation of the PageRank for The Cancer Genome Atlas took 0.02081298828125s
Interlinking | Calculation of Degree of Connection for The Cancer Genome Atlas took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for The Cancer Genome Atlas took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for The Cancer Genome Atlas took 3.838539123535156e-05s
Believability | Calculation of trust value for The Cancer Genome Atlas took 1.6450881958007812e-05s
INFO | --- Analysis for tcga took 934.1015584468842s
Availability | SPARQL endpoint availability check for TCGA Roadmap took 0.3633427619934082s
Availability | VoID file availability check for TCGA Roadmap took 0.0012257099151611328s
Completeness | Calculation of interlinking completeness for TCGA Roadmap took 0.2627079486846924s
Reputation | Calculation of the PageRank for TCGA Roadmap took 0.020732641220092773s
Interlinking | Calculation of Degree of Connection for TCGA Roadmap took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for TCGA Roadmap took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for TCGA Roadmap took 8.726119995117188e-05s
Believability | Calculation of trust value for TCGA Roadmap took 1.0728836059570312e-05s
INFO | --- Analysis for tcga-roadmap took 6.571038246154785s
Availability | SPARQL endpoint availability check for TCMGeneDIT Dataset took 1.1365597248077393s
Availability | VoID file availability check for TCMGeneDIT Dataset took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for TCMGeneDIT Dataset took 0.3299884796142578s
Reputation | Calculation of the PageRank for TCMGeneDIT Dataset took 0.020755529403686523s
Interlinking | Calculation of Degree of Connection for TCMGeneDIT Dataset took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for TCMGeneDIT Dataset took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for TCMGeneDIT Dataset took 0.00010895729064941406s
Believability | Calculation of trust value for TCMGeneDIT Dataset took 9.5367431640625e-06s
INFO | --- Analysis for tcmgenedit_dataset took 136.94295740127563s
Availability | SPARQL endpoint availability check for TDS took 8.463859558105469e-05s
Availability | VoID file availability check for TDS took 0.0007443428039550781s
Completeness | Calculation of interlinking completeness for TDS took 0.2714362144470215s
Reputation | Calculation of the PageRank for TDS took 0.020452022552490234s
Interlinking | Calculation of Degree of Connection for TDS took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for TDS took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for TDS took 4.029273986816406e-05s
Believability | Calculation of trust value for TDS took 1.2636184692382812e-05s
INFO | --- Analysis for tds took 4.554564476013184s
Availability | SPARQL endpoint availability check for TEKORD took 8.7738037109375e-05s
Availability | VoID file availability check for TEKORD took 0.0005559921264648438s
Completeness | Calculation of interlinking completeness for TEKORD took 0.27776145935058594s
Reputation | Calculation of the PageRank for TEKORD took 0.021449804306030273s
Interlinking | Calculation of Degree of Connection for TEKORD took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for TEKORD took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for TEKORD took 4.696846008300781e-05s
Believability | Calculation of trust value for TEKORD took 1.239776611328125e-05s
INFO | --- Analysis for tekord took 5.066915273666382s
Availability | SPARQL endpoint availability check for Telegraphis Linked Data took 1.67439866065979s
Availability | VoID file availability check for Telegraphis Linked Data took 0.0005381107330322266s
Completeness | Calculation of interlinking completeness for Telegraphis Linked Data took 0.3069460391998291s
Reputation | Calculation of the PageRank for Telegraphis Linked Data took 0.02081584930419922s
Interlinking | Calculation of Degree of Connection for Telegraphis Linked Data took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Telegraphis Linked Data took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Telegraphis Linked Data took 0.00011229515075683594s
Believability | Calculation of trust value for Telegraphis Linked Data took 8.344650268554688e-06s
INFO | --- Analysis for telegraphis took 7.769983768463135s
Availability | SPARQL endpoint availability check for Temple ov thee Lemur took 9.083747863769531e-05s
Availability | VoID file availability check for Temple ov thee Lemur took 0.0005698204040527344s
Completeness | Calculation of interlinking completeness for Temple ov thee Lemur took 0.26966166496276855s
Reputation | Calculation of the PageRank for Temple ov thee Lemur took 0.02188873291015625s
Interlinking | Calculation of Degree of Connection for Temple ov thee Lemur took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Temple ov thee Lemur took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Temple ov thee Lemur took 7.62939453125e-05s
Believability | Calculation of trust value for Temple ov thee Lemur took 1.239776611328125e-05s
INFO | --- Analysis for temple-ov-thee-lemur-datasets took 13.09431505203247s
Availability | SPARQL endpoint availability check for Ontology took 8.7738037109375e-05s
Availability | VoID file availability check for Ontology took 0.0006220340728759766s
Completeness | Calculation of interlinking completeness for Ontology took 0.27446675300598145s
Reputation | Calculation of the PageRank for Ontology took 0.020818710327148438s
Interlinking | Calculation of Degree of Connection for Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Ontology took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Ontology took 3.2901763916015625e-05s
Believability | Calculation of trust value for Ontology took 1.049041748046875e-05s
INFO | --- Analysis for Terrorist_attack took 3.0018601417541504s
Availability | SPARQL endpoint availability check for Terrorist Attack1 took 0.0001366138458251953s
Availability | VoID file availability check for Terrorist Attack1 took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for Terrorist Attack1 took 0.2986714839935303s
Reputation | Calculation of the PageRank for Terrorist Attack1 took 0.021174192428588867s
Interlinking | Calculation of Degree of Connection for Terrorist Attack1 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Terrorist Attack1 took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Terrorist Attack1 took 3.1948089599609375e-05s
Believability | Calculation of trust value for Terrorist Attack1 took 1.1444091796875e-05s
INFO | --- Analysis for Terrorist_Attack_1 took 2.600701332092285s
Availability | SPARQL endpoint availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 4.4345855712890625e-05s
Availability | VoID file availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0007221698760986328s
Completeness | Calculation of interlinking completeness for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.27022743225097656s
Reputation | Calculation of the PageRank for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.02085423469543457s
Interlinking | Calculation of Degree of Connection for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 3.266334533691406e-05s
Believability | Calculation of trust value for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 1.4781951904296875e-05s
INFO | --- Analysis for Tesla_Deaths took 4.252009391784668s
Availability | SPARQL endpoint availability check for test took 8.58306884765625e-05s
Availability | VoID file availability check for test took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for test took 0.2976348400115967s
Reputation | Calculation of the PageRank for test took 0.02076101303100586s
Interlinking | Calculation of Degree of Connection for test took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for test took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for test took 3.266334533691406e-05s
Believability | Calculation of trust value for test took 1.1920928955078125e-05s
INFO | --- Analysis for test took 2.5189197063446045s
Availability | SPARQL endpoint availability check for Test took 8.511543273925781e-05s
Availability | VoID file availability check for Test took 0.0004558563232421875s
Completeness | Calculation of interlinking completeness for Test took 0.2677192687988281s
Reputation | Calculation of the PageRank for Test took 0.021060466766357422s
Interlinking | Calculation of Degree of Connection for Test took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Test took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Test took 3.361701965332031e-05s
Believability | Calculation of trust value for Test took 9.775161743164062e-06s
INFO | --- Analysis for Test took 2.4241044521331787s
Availability | SPARQL endpoint availability check for test-svu took 20.182777643203735s
Availability | VoID file availability check for test-svu took 0.0004620552062988281s
Completeness | Calculation of interlinking completeness for test-svu took 0.270824670791626s
Reputation | Calculation of the PageRank for test-svu took 0.022052288055419922s
Interlinking | Calculation of Degree of Connection for test-svu took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for test-svu took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for test-svu took 3.2901763916015625e-05s
Believability | Calculation of trust value for test-svu took 9.298324584960938e-06s
INFO | --- Analysis for test-svu took 52.71569895744324s
Availability | SPARQL endpoint availability check for Test took 8.392333984375e-05s
Availability | VoID file availability check for Test took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for Test took 0.2747364044189453s
Reputation | Calculation of the PageRank for Test took 0.02054142951965332s
Interlinking | Calculation of Degree of Connection for Test took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Test took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Test took 3.337860107421875e-05s
Believability | Calculation of trust value for Test took 1.0728836059570312e-05s
INFO | --- Analysis for Test_ took 2.4835188388824463s
Availability | SPARQL endpoint availability check for xxxxx took 261.249080657959s
Availability | VoID file availability check for xxxxx took 0.0008208751678466797s
Completeness | Calculation of interlinking completeness for xxxxx took 0.2675302028656006s
Reputation | Calculation of the PageRank for xxxxx took 0.020740270614624023s
Interlinking | Calculation of Degree of Connection for xxxxx took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for xxxxx took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for xxxxx took 4.76837158203125e-05s
Believability | Calculation of trust value for xxxxx took 8.58306884765625e-06s
INFO | --- Analysis for testee took 796.3248989582062s
Availability | SPARQL endpoint availability check for tharawat magazine took 0.00011801719665527344s
Availability | VoID file availability check for tharawat magazine took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for tharawat magazine took 130.5085198879242s
Reputation | Calculation of the PageRank for tharawat magazine took 0.021001100540161133s
Interlinking | Calculation of Degree of Connection for tharawat magazine took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for tharawat magazine took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for tharawat magazine took 0.00013303756713867188s
Believability | Calculation of trust value for tharawat magazine took 1.2159347534179688e-05s
INFO | --- Analysis for tharawat-magazine-com took 394.8155493736267s
Availability | SPARQL endpoint availability check for The Drug Interaction Knowledge Base took 1.4492454528808594s
Availability | VoID file availability check for The Drug Interaction Knowledge Base took 0.0006849765777587891s
Completeness | Calculation of interlinking completeness for The Drug Interaction Knowledge Base took 0.2777674198150635s
Reputation | Calculation of the PageRank for The Drug Interaction Knowledge Base took 0.021287202835083008s
Interlinking | Calculation of Degree of Connection for The Drug Interaction Knowledge Base took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for The Drug Interaction Knowledge Base took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for The Drug Interaction Knowledge Base took 3.266334533691406e-05s
Believability | Calculation of trust value for The Drug Interaction Knowledge Base took 1.1444091796875e-05s
INFO | --- Analysis for the-drug-interaction-knowledge-base took 7.725341796875s
Availability | SPARQL endpoint availability check for The European Library Open Dataset took 3.302802801132202s
Availability | VoID file availability check for The European Library Open Dataset took 0.0006208419799804688s
Extra | Recovery of all triples for The European Library Open Dataset took 6.898926019668579s
Performance | Total latancy measurement for The European Library Open Dataset took 15.993344068527222s
Amount of data | Number of triples check for The European Library Open Dataset took 64.41853380203247s
Interoperability | New terms check for The European Library Open Dataset took 61.078141927719116s
Versatility | Languages check for The European Library Open Dataset took 3.1731643676757812s
Interpretability | Number of blank nodes check for The European Library Open Dataset took 3.1701622009277344s
Interpretability | RDF structures check for The European Library Open Dataset took 3.2036309242248535s
Versatility | Serialization formats check for The European Library Open Dataset took 3.1970348358154297s
Availability | RDF dump link check for The European Library Open Dataset took 3.2001709938049316s
License | MR license check for The European Library Open Dataset took 3.2022573947906494s
License | HR license check for The European Library Open Dataset took 3.201228141784668s
Amount of data | Number of property check for The European Library Open Dataset took 3.199399709701538s
Understandability | Number of label check for The European Library Open Dataset took 3.7337207794189453s
Understandability | URI regex check for The European Library Open Dataset took 6.3750059604644775s
Understandability | Vocabs check for The European Library Open Dataset took 3.203223943710327s
Verifiability | Authors check for The European Library Open Dataset took 3.199979782104492s
Verifiability | Publishers check for The European Library Open Dataset took 3.199660062789917s
Performance | Throughput check for The European Library Open Dataset took 31.869962453842163s
Amount of data | Check the number of entities for The European Library Open Dataset took 3.1948089599609375e-05s
Verifiability | Contribs. check for The European Library Open Dataset took 3.181689977645874s
Interlinking | sameAs chians check for The European Library Open Dataset took 3.3215208053588867s
Interlinking | skos check for The European Library Open Dataset took 3.2410659790039062s
Interlinking | skos check for The European Library Open Dataset took 3.231356620788574s
Timeliness | dataset update frequency check for The European Library Open Dataset took 3.188173532485962s
Currency | Creation date check for The European Library Open Dataset took 6.400319337844849s
Currency | Modification date check for The European Library Open Dataset took 6.398566246032715s
Rep.Conc. | URIs length for The European Library Open Dataset took 122.70780301094055s
Interoperability | New vocabularies check for The European Library Open Dataset took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for The European Library Open Dataset took 3.180933952331543s
Accuracy | Check Empty annotation labels for The European Library Open Dataset took 3.4854848384857178s
Accuracy | Check White space in annotation for The European Library Open Dataset took 0.02642822265625s
Accuracy | Check Datatype consistency for The European Library Open Dataset took 0.02761983871459961s
Consistency | Disjoint class check for The European Library Open Dataset took 3.1823906898498535s
Consistency | Check Misplaced properties for The European Library Open Dataset took 67.6611762046814s
Consistency | Misplaced classes for The European Library Open Dataset took 3.271183729171753s
Consistency | Check Ontology hijacking for The European Library Open Dataset took 4.773747205734253s
Consistency | Check Invalid usage of undefined classes for The European Library Open Dataset took 1.2758290767669678s
Consistency | Check Invalid usage of undefined properties for The European Library Open Dataset took 66.16340827941895s
Conciseness | Check Extensional conciseness for The European Library Open Dataset took 0.03239583969116211s
Conciseness | Check Intensional conciseness for The European Library Open Dataset took 0.9161288738250732s
Security | Sign check for The European Library Open Dataset took 3.16994309425354s
Availability | Check URIs Dereferenciability for The European Library Open Dataset took 10.048366069793701s
Completeness | Calculation of interlinking completeness for The European Library Open Dataset took 0.4313654899597168s
Reputation | Calculation of the PageRank for The European Library Open Dataset took 0.020920991897583008s
Interlinking | Calculation of Degree of Connection for The European Library Open Dataset took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for The European Library Open Dataset took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for The European Library Open Dataset took 6.222724914550781e-05s
Interoperability | Check the re-using of existing vocabs for The European Library Open Dataset took 9.5367431640625e-07s
Believability | Calculation of trust value for The European Library Open Dataset took 1.4781951904296875e-05s
INFO | --- Analysis for the-european-library-open-dataset took 920.4802105426788s
Availability | SPARQL endpoint availability check for The Eurostat Linked Data took 0.9466347694396973s
Availability | VoID file availability check for The Eurostat Linked Data took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for The Eurostat Linked Data took 0.2971515655517578s
Reputation | Calculation of the PageRank for The Eurostat Linked Data took 0.021131038665771484s
Interlinking | Calculation of Degree of Connection for The Eurostat Linked Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for The Eurostat Linked Data took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for The Eurostat Linked Data took 0.00010013580322265625s
Believability | Calculation of trust value for The Eurostat Linked Data took 9.059906005859375e-06s
INFO | --- Analysis for the-eurostat-linked-data took 6.542135000228882s
Availability | SPARQL endpoint availability check for The Living LOD Cloud took 8.368492126464844e-05s
Availability | VoID file availability check for The Living LOD Cloud took 0.0006985664367675781s
Completeness | Calculation of interlinking completeness for The Living LOD Cloud took 0.32970356941223145s
Reputation | Calculation of the PageRank for The Living LOD Cloud took 0.020505666732788086s
Interlinking | Calculation of Degree of Connection for The Living LOD Cloud took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for The Living LOD Cloud took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for The Living LOD Cloud took 7.510185241699219e-05s
Believability | Calculation of trust value for The Living LOD Cloud took 1.3589859008789062e-05s
INFO | --- Analysis for the-living-lod-cloud took 42.801685094833374s
Availability | SPARQL endpoint availability check for The View From took 0.08727574348449707s
Availability | VoID file availability check for The View From took 0.0003330707550048828s
Completeness | Calculation of interlinking completeness for The View From took 0.27273011207580566s
Reputation | Calculation of the PageRank for The View From took 0.020354509353637695s
Interlinking | Calculation of Degree of Connection for The View From took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The View From took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for The View From took 7.963180541992188e-05s
Believability | Calculation of trust value for The View From took 1.1444091796875e-05s
INFO | --- Analysis for the-view-from took 2.5560712814331055s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.42529582977295s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0006759166717529297s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.2753739356994629s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.02081441879272461s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 4.124641418457031e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 9.775161743164062e-06s
INFO | --- Analysis for The_Central_Bank_of_the_Republic_of_Uzbekistan took 72.96694159507751s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.093519687652588s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0007092952728271484s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.28594541549682617s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.02053689956665039s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 3.600120544433594e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 1.0967254638671875e-05s
INFO | --- Analysis for The_Respublic_of_Uzbekistan took 102.73269653320312s
Availability | SPARQL endpoint availability check for The Content Wrangler took 9.1552734375e-05s
Availability | VoID file availability check for The Content Wrangler took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for The Content Wrangler took 0.27073001861572266s
Reputation | Calculation of the PageRank for The Content Wrangler took 0.021939754486083984s
Interlinking | Calculation of Degree of Connection for The Content Wrangler took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for The Content Wrangler took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for The Content Wrangler took 0.00010466575622558594s
Believability | Calculation of trust value for The Content Wrangler took 1.0013580322265625e-05s
INFO | --- Analysis for thecontentwrangler-com took 2.9327187538146973s
Availability | SPARQL endpoint availability check for Thesaurus Datenwissen took 4.076957702636719e-05s
Availability | VoID file availability check for Thesaurus Datenwissen took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for Thesaurus Datenwissen took 0.27396202087402344s
Reputation | Calculation of the PageRank for Thesaurus Datenwissen took 0.020624876022338867s
Interlinking | Calculation of Degree of Connection for Thesaurus Datenwissen took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Thesaurus Datenwissen took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Thesaurus Datenwissen took 3.0040740966796875e-05s
Believability | Calculation of trust value for Thesaurus Datenwissen took 9.775161743164062e-06s
INFO | --- Analysis for thesaurus-datenwissen took 2.527411460876465s
Availability | SPARQL endpoint availability check for Thesaurus W for Local Archives took 0.5003485679626465s
Availability | VoID file availability check for Thesaurus W for Local Archives took 0.0005514621734619141s
Completeness | Calculation of interlinking completeness for Thesaurus W for Local Archives took 0.2766249179840088s
Reputation | Calculation of the PageRank for Thesaurus W for Local Archives took 0.021591901779174805s
Interlinking | Calculation of Degree of Connection for Thesaurus W for Local Archives took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Thesaurus W for Local Archives took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Thesaurus W for Local Archives took 7.772445678710938e-05s
Believability | Calculation of trust value for Thesaurus W for Local Archives took 1.3113021850585938e-05s
INFO | --- Analysis for thesaurus-w took 3.759415864944458s
Availability | SPARQL endpoint availability check for theses.fr took 8.797645568847656e-05s
Availability | VoID file availability check for theses.fr took 0.0007584095001220703s
Completeness | Calculation of interlinking completeness for theses.fr took 0.2672615051269531s
Reputation | Calculation of the PageRank for theses.fr took 0.020743608474731445s
Interlinking | Calculation of Degree of Connection for theses.fr took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for theses.fr took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for theses.fr took 5.030632019042969e-05s
Believability | Calculation of trust value for theses.fr took 7.3909759521484375e-06s
INFO | --- Analysis for thesesfr took 4.030287265777588s
Availability | SPARQL endpoint availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 4.410743713378906e-05s
Availability | VoID file availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.00046563148498535156s
Completeness | Calculation of interlinking completeness for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.2657322883605957s
Reputation | Calculation of the PageRank for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.021170377731323242s
Interlinking | Calculation of Degree of Connection for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 3.361701965332031e-05s
Believability | Calculation of trust value for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 9.5367431640625e-06s
INFO | --- Analysis for Thinkphile took 2.4638736248016357s
Availability | SPARQL endpoint availability check for ThIST took 265.34176445007324s
Availability | VoID file availability check for ThIST took 0.0005433559417724609s
Completeness | Calculation of interlinking completeness for ThIST took 0.27150797843933105s
Reputation | Calculation of the PageRank for ThIST took 0.021024703979492188s
Interlinking | Calculation of Degree of Connection for ThIST took 2.3603439331054688e-05s
Interlinking | Calculation of Centrality for ThIST took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for ThIST took 9.179115295410156e-05s
Believability | Calculation of trust value for ThIST took 1.0013580322265625e-05s
INFO | --- Analysis for thist took 563.4272797107697s
Availability | SPARQL endpoint availability check for TIP took 40.03256678581238s
Availability | VoID file availability check for TIP took 0.0006468296051025391s
Completeness | Calculation of interlinking completeness for TIP took 0.2654001712799072s
Reputation | Calculation of the PageRank for TIP took 0.021278858184814453s
Interlinking | Calculation of Degree of Connection for TIP took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for TIP took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for TIP took 0.00010919570922851562s
Believability | Calculation of trust value for TIP took 1.0251998901367188e-05s
INFO | --- Analysis for tip took 102.63141202926636s
Availability | SPARQL endpoint availability check for Topography based Hydrological Model took 8.58306884765625e-05s
Availability | VoID file availability check for Topography based Hydrological Model took 0.0006995201110839844s
Completeness | Calculation of interlinking completeness for Topography based Hydrological Model took 0.2640261650085449s
Reputation | Calculation of the PageRank for Topography based Hydrological Model took 0.0212857723236084s
Interlinking | Calculation of Degree of Connection for Topography based Hydrological Model took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Topography based Hydrological Model took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Topography based Hydrological Model took 3.361701965332031e-05s
Believability | Calculation of trust value for Topography based Hydrological Model took 3.8623809814453125e-05s
INFO | --- Analysis for TOPMODEL took 22.237082719802856s
Availability | SPARQL endpoint availability check for Observation dataset of forest ecosystems  took 3.6533279418945312s
Availability | VoID file availability check for Observation dataset of forest ecosystems  took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for Observation dataset of forest ecosystems  took 0.26726841926574707s
Reputation | Calculation of the PageRank for Observation dataset of forest ecosystems  took 0.02116680145263672s
Interlinking | Calculation of Degree of Connection for Observation dataset of forest ecosystems  took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Observation dataset of forest ecosystems  took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Observation dataset of forest ecosystems  took 3.9577484130859375e-05s
Believability | Calculation of trust value for Observation dataset of forest ecosystems  took 1.1444091796875e-05s
INFO | --- Analysis for TP-data took 7.536489725112915s
Availability | SPARQL endpoint availability check for Trackloaded Artist Profiles took 1.483290195465088s
Availability | VoID file availability check for Trackloaded Artist Profiles took 0.0006248950958251953s
Extra | Recovery of all triples for Trackloaded Artist Profiles took 2.038296699523926s
Performance | Total latancy measurement for Trackloaded Artist Profiles took 5.67742919921875s
Amount of data | Number of triples check for Trackloaded Artist Profiles took 1.0260260105133057s
Interoperability | New terms check for Trackloaded Artist Profiles took 2.483100652694702s
Versatility | Languages check for Trackloaded Artist Profiles took 0.9603476524353027s
Interpretability | Number of blank nodes check for Trackloaded Artist Profiles took 1.2254018783569336s
Interpretability | RDF structures check for Trackloaded Artist Profiles took 1.1290087699890137s
Versatility | Serialization formats check for Trackloaded Artist Profiles took 0.9902420043945312s
Availability | RDF dump link check for Trackloaded Artist Profiles took 1.3488874435424805s
License | MR license check for Trackloaded Artist Profiles took 1.306135892868042s
License | HR license check for Trackloaded Artist Profiles took 0.995581865310669s
Amount of data | Number of property check for Trackloaded Artist Profiles took 0.9327266216278076s
Understandability | Number of label check for Trackloaded Artist Profiles took 0.9821033477783203s
Understandability | URI regex check for Trackloaded Artist Profiles took 1.8709862232208252s
Understandability | Vocabs check for Trackloaded Artist Profiles took 0.9597890377044678s
Verifiability | Authors check for Trackloaded Artist Profiles took 0.9950146675109863s
Verifiability | Publishers check for Trackloaded Artist Profiles took 0.9859161376953125s
Performance | Throughput check for Trackloaded Artist Profiles took 15.784730195999146s
Amount of data | Check the number of entities for Trackloaded Artist Profiles took 3.0279159545898438e-05s
Verifiability | Contribs. check for Trackloaded Artist Profiles took 1.266702651977539s
Interlinking | sameAs chians check for Trackloaded Artist Profiles took 0.9648342132568359s
Interlinking | skos check for Trackloaded Artist Profiles took 0.9645426273345947s
Interlinking | skos check for Trackloaded Artist Profiles took 1.4449074268341064s
Timeliness | dataset update frequency check for Trackloaded Artist Profiles took 1.0565738677978516s
Currency | Creation date check for Trackloaded Artist Profiles took 2.1966755390167236s
Currency | Modification date check for Trackloaded Artist Profiles took 2.0766360759735107s
Rep.Conc. | URIs length for Trackloaded Artist Profiles took 2.0217275619506836s
Interoperability | New vocabularies check for Trackloaded Artist Profiles took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Trackloaded Artist Profiles took 0.963630199432373s
Consistency | Disjoint class check for Trackloaded Artist Profiles took 1.1869912147521973s
Consistency | Check Misplaced properties for Trackloaded Artist Profiles took 2.5466177463531494s
Consistency | Misplaced classes for Trackloaded Artist Profiles took 1.0387921333312988s
Consistency | Check Ontology hijacking for Trackloaded Artist Profiles took 2.4047627449035645s
Consistency | Check Invalid usage of undefined classes for Trackloaded Artist Profiles took 1.327066421508789s
Consistency | Check Invalid usage of undefined properties for Trackloaded Artist Profiles took 2.3232579231262207s
Conciseness | Check Extensional conciseness for Trackloaded Artist Profiles took 0.00015091896057128906s
Security | Sign check for Trackloaded Artist Profiles took 1.2378778457641602s
Availability | Check URIs Dereferenciability for Trackloaded Artist Profiles took 1.2693426609039307s
Completeness | Calculation of interlinking completeness for Trackloaded Artist Profiles took 0.31078457832336426s
Reputation | Calculation of the PageRank for Trackloaded Artist Profiles took 0.020578861236572266s
Interlinking | Calculation of Degree of Connection for Trackloaded Artist Profiles took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Trackloaded Artist Profiles took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Trackloaded Artist Profiles took 1.9311904907226562e-05s
Interoperability | Check the re-using of existing vocabs for Trackloaded Artist Profiles took 1.430511474609375e-06s
Believability | Calculation of trust value for Trackloaded Artist Profiles took 7.62939453125e-06s
INFO | --- Analysis for trackloaded took 109.00541090965271s
Availability | SPARQL endpoint availability check for Traditional Korean Medicine Ontology took 0.3281369209289551s
Availability | VoID file availability check for Traditional Korean Medicine Ontology took 0.0005383491516113281s
Completeness | Calculation of interlinking completeness for Traditional Korean Medicine Ontology took 0.2741110324859619s
Reputation | Calculation of the PageRank for Traditional Korean Medicine Ontology took 0.02312779426574707s
Interlinking | Calculation of Degree of Connection for Traditional Korean Medicine Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Traditional Korean Medicine Ontology took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Traditional Korean Medicine Ontology took 4.673004150390625e-05s
Believability | Calculation of trust value for Traditional Korean Medicine Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for traditional-korean-medicine took 3.3896284103393555s
Availability | SPARQL endpoint availability check for Traffic Scotland took 0.2325601577758789s
Availability | VoID file availability check for Traffic Scotland took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for Traffic Scotland took 0.2624678611755371s
Reputation | Calculation of the PageRank for Traffic Scotland took 0.020721435546875s
Interlinking | Calculation of Degree of Connection for Traffic Scotland took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Traffic Scotland took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Traffic Scotland took 3.552436828613281e-05s
Believability | Calculation of trust value for Traffic Scotland took 8.344650268554688e-06s
INFO | --- Analysis for traffic-scotland took 2.791898012161255s
Availability | SPARQL endpoint availability check for Transparency International Linked Data took 0.09909749031066895s
Availability | VoID file availability check for Transparency International Linked Data took 0.0002923011779785156s
Completeness | Calculation of interlinking completeness for Transparency International Linked Data took 0.272258996963501s
Reputation | Calculation of the PageRank for Transparency International Linked Data took 0.02080225944519043s
Interlinking | Calculation of Degree of Connection for Transparency International Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Transparency International Linked Data took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Transparency International Linked Data took 0.00010561943054199219s
Believability | Calculation of trust value for Transparency International Linked Data took 8.58306884765625e-06s
INFO | --- Analysis for transparency-linked-data took 2.594385862350464s
Availability | SPARQL endpoint availability check for transport.data.gov.uk took 0.6141335964202881s
Availability | VoID file availability check for transport.data.gov.uk took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for transport.data.gov.uk took 0.26172900199890137s
Reputation | Calculation of the PageRank for transport.data.gov.uk took 0.021357059478759766s
Interlinking | Calculation of Degree of Connection for transport.data.gov.uk took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for transport.data.gov.uk took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for transport.data.gov.uk took 9.441375732421875e-05s
Believability | Calculation of trust value for transport.data.gov.uk took 5.4836273193359375e-06s
INFO | --- Analysis for transport-data-gov-uk took 3.813385009765625s
Availability | SPARQL endpoint availability check for Trelios took 4.267692565917969e-05s
Availability | VoID file availability check for Trelios took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Trelios took 0.2808403968811035s
Reputation | Calculation of the PageRank for Trelios took 0.02105545997619629s
Interlinking | Calculation of Degree of Connection for Trelios took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Trelios took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Trelios took 1.3589859008789062e-05s
Believability | Calculation of trust value for Trelios took 1.1205673217773438e-05s
INFO | --- Analysis for Trelios took 2.4313011169433594s
Availability | SPARQL endpoint availability check for Twarql took 10.482374906539917s
Availability | VoID file availability check for Twarql took 0.00037598609924316406s
Completeness | Calculation of interlinking completeness for Twarql took 0.28226232528686523s
Reputation | Calculation of the PageRank for Twarql took 0.02072286605834961s
Interlinking | Calculation of Degree of Connection for Twarql took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Twarql took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Twarql took 6.937980651855469e-05s
Believability | Calculation of trust value for Twarql took 7.62939453125e-06s
INFO | --- Analysis for twarql took 12.931992292404175s
Availability | SPARQL endpoint availability check for TWC Data-gov took 4.220008850097656e-05s
Availability | VoID file availability check for TWC Data-gov took 0.0006458759307861328s
Completeness | Calculation of interlinking completeness for TWC Data-gov took 0.27792859077453613s
Reputation | Calculation of the PageRank for TWC Data-gov took 0.020669221878051758s
Interlinking | Calculation of Degree of Connection for TWC Data-gov took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for TWC Data-gov took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for TWC Data-gov took 3.337860107421875e-05s
Believability | Calculation of trust value for TWC Data-gov took 8.821487426757812e-06s
INFO | --- Analysis for twc-data-gov took 12.781291484832764s
Availability | SPARQL endpoint availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.15709424018859863s
Availability | VoID file availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.0006992816925048828s
Completeness | Calculation of interlinking completeness for HealthData.gov Platform (HDP) on the Semantic Web took 0.28578734397888184s
Reputation | Calculation of the PageRank for HealthData.gov Platform (HDP) on the Semantic Web took 0.021669387817382812s
Interlinking | Calculation of Degree of Connection for HealthData.gov Platform (HDP) on the Semantic Web took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for HealthData.gov Platform (HDP) on the Semantic Web took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for HealthData.gov Platform (HDP) on the Semantic Web took 4.2438507080078125e-05s
Believability | Calculation of trust value for HealthData.gov Platform (HDP) on the Semantic Web took 9.059906005859375e-06s
INFO | --- Analysis for twc-healthdata took 13.840484142303467s
Availability | SPARQL endpoint availability check for Instance Hub (all) took 4.0379674434661865s
Availability | VoID file availability check for Instance Hub (all) took 0.0004527568817138672s
Completeness | Calculation of interlinking completeness for Instance Hub (all) took 0.33527255058288574s
Reputation | Calculation of the PageRank for Instance Hub (all) took 0.021326541900634766s
Interlinking | Calculation of Degree of Connection for Instance Hub (all) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Instance Hub (all) took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Instance Hub (all) took 8.606910705566406e-05s
Believability | Calculation of trust value for Instance Hub (all) took 1.2636184692382812e-05s
INFO | --- Analysis for twc-hub took 605.3039944171906s
Availability | SPARQL endpoint availability check for IEEE VIS Source Data took 0.13433218002319336s
Availability | VoID file availability check for IEEE VIS Source Data took 0.00034117698669433594s
Completeness | Calculation of interlinking completeness for IEEE VIS Source Data took 130.70807909965515s
Reputation | Calculation of the PageRank for IEEE VIS Source Data took 0.021050453186035156s
Interlinking | Calculation of Degree of Connection for IEEE VIS Source Data took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for IEEE VIS Source Data took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for IEEE VIS Source Data took 0.0001201629638671875s
Believability | Calculation of trust value for IEEE VIS Source Data took 4.696846008300781e-05s
INFO | --- Analysis for twc-ieeevis took 757.3762238025665s
Availability | SPARQL endpoint availability check for TWC: Linking Open Government Data took 0.0005195140838623047s
Availability | VoID file availability check for TWC: Linking Open Government Data took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for TWC: Linking Open Government Data took 0.28812193870544434s
Reputation | Calculation of the PageRank for TWC: Linking Open Government Data took 0.020537614822387695s
Interlinking | Calculation of Degree of Connection for TWC: Linking Open Government Data took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for TWC: Linking Open Government Data took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for TWC: Linking Open Government Data took 9.584426879882812e-05s
Believability | Calculation of trust value for TWC: Linking Open Government Data took 8.106231689453125e-06s
INFO | --- Analysis for twc-logd took 2.6050591468811035s
Availability | SPARQL endpoint availability check for twc-opendap took 0.11856698989868164s
Availability | VoID file availability check for twc-opendap took 0.0002987384796142578s
Completeness | Calculation of interlinking completeness for twc-opendap took 0.26339030265808105s
Reputation | Calculation of the PageRank for twc-opendap took 0.02055978775024414s
Interlinking | Calculation of Degree of Connection for twc-opendap took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for twc-opendap took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for twc-opendap took 7.295608520507812e-05s
Believability | Calculation of trust value for twc-opendap took 9.775161743164062e-06s
INFO | --- Analysis for twc-opendap took 53.77291250228882s
Availability | SPARQL endpoint availability check for typepad took 8.273124694824219e-05s
Availability | VoID file availability check for typepad took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for typepad took 0.2763524055480957s
Reputation | Calculation of the PageRank for typepad took 0.020386695861816406s
Interlinking | Calculation of Degree of Connection for typepad took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for typepad took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for typepad took 5.0067901611328125e-05s
Believability | Calculation of trust value for typepad took 9.5367431640625e-06s
INFO | --- Analysis for typepad took 3.024853467941284s
Availability | SPARQL endpoint availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.8469333648681641s
Availability | VoID file availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.00055694580078125s
Completeness | Calculation of interlinking completeness for Linked Data Service der Universitätsbibliothek Mannheim took 0.26424074172973633s
Reputation | Calculation of the PageRank for Linked Data Service der Universitätsbibliothek Mannheim took 0.02095794677734375s
Interlinking | Calculation of Degree of Connection for Linked Data Service der Universitätsbibliothek Mannheim took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Data Service der Universitätsbibliothek Mannheim took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Linked Data Service der Universitätsbibliothek Mannheim took 4.38690185546875e-05s
Believability | Calculation of trust value for Linked Data Service der Universitätsbibliothek Mannheim took 1.3113021850585938e-05s
INFO | --- Analysis for ub-mannheim-linked-data took 4.600112199783325s
Availability | SPARQL endpoint availability check for Uberblic.org took 4.368232011795044s
Availability | VoID file availability check for Uberblic.org took 0.0015163421630859375s
Completeness | Calculation of interlinking completeness for Uberblic.org took 0.26999998092651367s
Reputation | Calculation of the PageRank for Uberblic.org took 0.020269155502319336s
Interlinking | Calculation of Degree of Connection for Uberblic.org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Uberblic.org took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Uberblic.org took 0.000102996826171875s
Believability | Calculation of trust value for Uberblic.org took 1.1682510375976562e-05s
INFO | --- Analysis for uberblic took 9.343862295150757s
Availability | SPARQL endpoint availability check for UDante in LiLa took 0.579383373260498s
Availability | VoID file availability check for UDante in LiLa took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for UDante in LiLa took 0.27066540718078613s
Reputation | Calculation of the PageRank for UDante in LiLa took 0.0204470157623291s
Interlinking | Calculation of Degree of Connection for UDante in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for UDante in LiLa took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for UDante in LiLa took 3.814697265625e-05s
Believability | Calculation of trust value for UDante in LiLa took 1.0728836059570312e-05s
INFO | --- Analysis for UDante took 3.9450156688690186s
Availability | SPARQL endpoint availability check for Unified Foundational Ontology took 0.8659472465515137s
Availability | VoID file availability check for Unified Foundational Ontology took 0.0006301403045654297s
Completeness | Calculation of interlinking completeness for Unified Foundational Ontology took 0.26992058753967285s
Reputation | Calculation of the PageRank for Unified Foundational Ontology took 0.020638465881347656s
Interlinking | Calculation of Degree of Connection for Unified Foundational Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Unified Foundational Ontology took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Unified Foundational Ontology took 2.8848648071289062e-05s
Believability | Calculation of trust value for Unified Foundational Ontology took 9.775161743164062e-06s
INFO | --- Analysis for ufo took 4.460310459136963s
Availability | SPARQL endpoint availability check for Uganda Disasters took 4.792213439941406e-05s
Availability | VoID file availability check for Uganda Disasters took 0.00042939186096191406s
Completeness | Calculation of interlinking completeness for Uganda Disasters took 0.280886173248291s
Reputation | Calculation of the PageRank for Uganda Disasters took 0.020392179489135742s
Interlinking | Calculation of Degree of Connection for Uganda Disasters took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Uganda Disasters took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Uganda Disasters took 4.553794860839844e-05s
Believability | Calculation of trust value for Uganda Disasters took 1.0013580322265625e-05s
INFO | --- Analysis for Uganda-Disasters-rdf-data_ took 2.4695687294006348s
Availability | SPARQL endpoint availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.049654483795166016s
Availability | VoID file availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.00040602684020996094s
Completeness | Calculation of interlinking completeness for UNESCO Institute for Statistics (UIS) Linked Data took 0.2716054916381836s
Reputation | Calculation of the PageRank for UNESCO Institute for Statistics (UIS) Linked Data took 0.020870447158813477s
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.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for UNESCO Institute for Statistics (UIS) Linked Data took 9.989738464355469e-05s
Believability | Calculation of trust value for UNESCO Institute for Statistics (UIS) Linked Data took 1.1444091796875e-05s
INFO | --- Analysis for uis-linked-data took 2.544389009475708s
Availability | SPARQL endpoint availability check for UK Legislation took 8.630752563476562e-05s
Availability | VoID file availability check for UK Legislation took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for UK Legislation took 0.26882171630859375s
Reputation | Calculation of the PageRank for UK Legislation took 0.02073955535888672s
Interlinking | Calculation of Degree of Connection for UK Legislation took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for UK Legislation took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for UK Legislation took 8.940696716308594e-05s
Believability | Calculation of trust value for UK Legislation took 8.344650268554688e-06s
INFO | --- Analysis for uk-legislation-api took 3.3278567790985107s
Availability | SPARQL endpoint availability check for UK Postcodes took 8.96453857421875e-05s
Availability | VoID file availability check for UK Postcodes took 0.0006756782531738281s
Completeness | Calculation of interlinking completeness for UK Postcodes took 0.27329039573669434s
Reputation | Calculation of the PageRank for UK Postcodes took 0.021732330322265625s
Interlinking | Calculation of Degree of Connection for UK Postcodes took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for UK Postcodes took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for UK Postcodes took 5.984306335449219e-05s
Believability | Calculation of trust value for UK Postcodes took 1.239776611328125e-05s
INFO | --- Analysis for uk-postcodes took 22.471787452697754s
Availability | SPARQL endpoint availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 4.363059997558594e-05s
Availability | VoID file availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0006060600280761719s
Completeness | Calculation of interlinking completeness for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.26143407821655273s
Reputation | Calculation of the PageRank for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.021564245223999023s
Interlinking | Calculation of Degree of Connection for UMBEL (Upper Mapping and Binding Exchange Layer) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.00013113021850585938s
Believability | Calculation of trust value for UMBEL (Upper Mapping and Binding Exchange Layer) took 1.1682510375976562e-05s
INFO | --- Analysis for umbel took 6.933309316635132s
Availability | SPARQL endpoint availability check for German environmental thesaurus UMTHES took 8.845329284667969e-05s
Availability | VoID file availability check for German environmental thesaurus UMTHES took 0.0006968975067138672s
Completeness | Calculation of interlinking completeness for German environmental thesaurus UMTHES took 0.281818151473999s
Reputation | Calculation of the PageRank for German environmental thesaurus UMTHES took 0.021568775177001953s
Interlinking | Calculation of Degree of Connection for German environmental thesaurus UMTHES took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for German environmental thesaurus UMTHES took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for German environmental thesaurus UMTHES took 4.172325134277344e-05s
Believability | Calculation of trust value for German environmental thesaurus UMTHES took 9.298324584960938e-06s
INFO | --- Analysis for umthes took 3.6027262210845947s
Availability | SPARQL endpoint availability check for UN Hazardous Materials Numbers took 1.4535768032073975s
Availability | VoID file availability check for UN Hazardous Materials Numbers took 0.0007307529449462891s
Completeness | Calculation of interlinking completeness for UN Hazardous Materials Numbers took 0.27286577224731445s
Reputation | Calculation of the PageRank for UN Hazardous Materials Numbers took 0.020641803741455078s
Interlinking | Calculation of Degree of Connection for UN Hazardous Materials Numbers took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for UN Hazardous Materials Numbers took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for UN Hazardous Materials Numbers took 3.0994415283203125e-05s
Believability | Calculation of trust value for UN Hazardous Materials Numbers took 9.5367431640625e-06s
INFO | --- Analysis for un-hazardous-numbers took 9.149832487106323s
Availability | SPARQL endpoint availability check for UniProt took 1.2219657897949219s
Availability | VoID file availability check for UniProt took 0.0005397796630859375s
Extra | Recovery of all triples for UniProt took 15.29673719406128s
Performance | Total latancy measurement for UniProt took 3.496283531188965s
Amount of data | Number of triples check for UniProt took 0.45015740394592285s
Interoperability | New terms check for UniProt took 1.6631245613098145s
Versatility | Languages check for UniProt took 1.9329416751861572s
Interpretability | Number of blank nodes check for UniProt took 1.7993826866149902s
Interpretability | RDF structures check for UniProt took 1.547816276550293s
Versatility | Serialization formats check for UniProt took 1.9589617252349854s
Availability | RDF dump link check for UniProt took 0.2382218837738037s
License | MR license check for UniProt took 1.260802984237671s
License | HR license check for UniProt took 300.0775442123413s
Amount of data | Number of property check for UniProt took 0.0979318618774414s
Understandability | Number of label check for UniProt took 43.64110732078552s
Understandability | URI regex check for UniProt took 0.5733747482299805s
Understandability | Vocabs check for UniProt took 0.7057094573974609s
Verifiability | Authors check for UniProt took 1.33012056350708s
Verifiability | Publishers check for UniProt took 1.1142587661743164s
Performance | Throughput check for UniProt took 22.50027084350586s
Amount of data | Check the number of entities for UniProt took 7.557868957519531e-05s
Verifiability | Contribs. check for UniProt took 0.7756686210632324s
Interlinking | sameAs chians check for UniProt took 0.4435861110687256s
Interlinking | skos check for UniProt took 0.8210353851318359s
Interlinking | skos check for UniProt took 0.07544445991516113s
Timeliness | dataset update frequency check for UniProt took 1.4638688564300537s
Currency | Creation date check for UniProt took 1.761746883392334s
Currency | Modification date check for UniProt took 1.4070956707000732s
Rep.Conc. | URIs length for UniProt took 113.83028268814087s
Interoperability | New vocabularies check for UniProt took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for UniProt took 0.22749876976013184s
Accuracy | Check Functional Property for UniProt took 0.30942678451538086s
Accuracy | Check Inverse Functional Property for UniProt took 0.282468318939209s
Accuracy | Check Empty annotation labels for UniProt took 11.03245735168457s
Accuracy | Check White space in annotation for UniProt took 2.4799840450286865s
Accuracy | Check Datatype consistency for UniProt took 7.12096381187439s
Consistency | Disjoint class check for UniProt took 0.4047079086303711s
Consistency | Check Misplaced properties for UniProt took 3.925382137298584s
Consistency | Check Ontology hijacking for UniProt took 7.988274097442627s
Consistency | Check Invalid usage of undefined classes for UniProt took 19624.387222766876s
Consistency | Check Invalid usage of undefined properties for UniProt took 1.9332828521728516s
Conciseness | Check Extensional conciseness for UniProt took 2.651777982711792s
Conciseness | Check Intensional conciseness for UniProt took 0.7008306980133057s
Security | Sign check for UniProt took 0.7960300445556641s
Availability | Check URIs Dereferenciability for UniProt took 4.1349687576293945s
Completeness | Calculation of interlinking completeness for UniProt took 0.5538256168365479s
Reputation | Calculation of the PageRank for UniProt took 0.020711660385131836s
Interlinking | Calculation of Degree of Connection for UniProt took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0006880760192871094s
Interlinking | Calculation of Clustering coefficient for UniProt took 4.267692565917969e-05s
Interoperability | Check the re-using of existing vocabs for UniProt took 4.5299530029296875e-06s
Believability | Calculation of trust value for UniProt took 1.0013580322265625e-05s
INFO | --- Analysis for UniProt took 20615.906904935837s
Availability | SPARQL endpoint availability check for UniProt took 6.67572021484375e-05s
Availability | VoID file availability check for UniProt took 0.0005106925964355469s
Completeness | Calculation of interlinking completeness for UniProt took 0.15732336044311523s
Reputation | Calculation of the PageRank for UniProt took 0.020628929138183594s
Interlinking | Calculation of Degree of Connection for UniProt took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for UniProt took 4.887580871582031e-05s
Believability | Calculation of trust value for UniProt took 1.1920928955078125e-05s
INFO | --- Analysis for uniprot took 1.7568907737731934s
Availability | SPARQL endpoint availability check for uniprot-metadata took 8.535385131835938e-05s
Availability | VoID file availability check for uniprot-metadata took 0.0004401206970214844s
Completeness | Calculation of interlinking completeness for uniprot-metadata took 0.24898767471313477s
Reputation | Calculation of the PageRank for uniprot-metadata took 0.020888090133666992s
Interlinking | Calculation of Degree of Connection for uniprot-metadata took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for uniprot-metadata took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for uniprot-metadata took 6.151199340820312e-05s
Believability | Calculation of trust value for uniprot-metadata took 1.1205673217773438e-05s
INFO | --- Analysis for uniprot-metadata took 1.8683245182037354s
Availability | SPARQL endpoint availability check for UniProtKB took 4.267692565917969e-05s
Availability | VoID file availability check for UniProtKB took 0.0002815723419189453s
Completeness | Calculation of interlinking completeness for UniProtKB took 0.15513253211975098s
Reputation | Calculation of the PageRank for UniProtKB took 0.020560264587402344s
Interlinking | Calculation of Degree of Connection for UniProtKB took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for UniProtKB took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for UniProtKB took 5.5789947509765625e-05s
Believability | Calculation of trust value for UniProtKB took 6.9141387939453125e-06s
INFO | --- Analysis for uniprotkb took 1.7660017013549805s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek took 8.511543273925781e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek took 0.00044536590576171875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek took 0.15842509269714355s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek took 0.020561933517456055s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek took 1.0013580322265625e-05s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek took 1.7587456703186035s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 9.1552734375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0005328655242919922s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.1563882827758789s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.020526647567749023s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek-PROIEL took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek-PROIEL took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek-PROIEL took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek-proiel took 1.7668297290802002s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Arabic took 0.00010704994201660156s
Availability | VoID file availability check for Universal Dependencies Treebank Arabic took 0.0004496574401855469s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Arabic took 0.15417766571044922s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Arabic took 0.022296428680419922s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Arabic took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Arabic took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Arabic took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Arabic took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-arabic took 1.8045580387115479s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Basque took 4.1484832763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Basque took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Basque took 0.15433430671691895s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Basque took 0.020604372024536133s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Basque took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Basque took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Basque took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Basque took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-basque took 1.8102383613586426s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Bulgarian took 4.458427429199219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Bulgarian took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Bulgarian took 0.15424251556396484s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Bulgarian took 0.021780014038085938s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Bulgarian took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Bulgarian took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Bulgarian took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Bulgarian took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-bulgarian took 1.7092125415802002s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Catalan took 8.940696716308594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Catalan took 0.0005483627319335938s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Catalan took 0.15576696395874023s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Catalan took 0.020548105239868164s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Catalan took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Catalan took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Catalan took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Catalan took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-catalan took 1.757697582244873s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Chinese took 6.794929504394531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Chinese took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Chinese took 0.16220879554748535s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Chinese took 0.020557880401611328s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Chinese took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Chinese took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Chinese took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Chinese took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-chinese took 1.786074161529541s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Coptic took 0.00010895729064941406s
Availability | VoID file availability check for Universal Dependencies Treebank Coptic took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Coptic took 0.15990948677062988s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Coptic took 0.02078390121459961s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Coptic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Coptic took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Coptic took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Coptic took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-coptic took 1.799128532409668s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Croatian took 8.726119995117188e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Croatian took 0.000446319580078125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Croatian took 0.16181039810180664s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Croatian took 0.021564483642578125s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Croatian took 2.9802322387695312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Croatian took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Croatian took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Croatian took 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-croatian took 1.7616910934448242s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech took 3.9577484130859375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech took 0.0004620552062988281s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech took 0.16480159759521484s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech took 0.022355079650878906s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech took 1.8075909614562988s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CAC took 6.4849853515625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CAC took 0.00044536590576171875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CAC took 0.16000080108642578s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CAC took 0.020552396774291992s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CAC took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CAC took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CAC took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CAC took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech-cac took 1.7907776832580566s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CLTT took 8.58306884765625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CLTT took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CLTT took 0.16243267059326172s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CLTT took 0.020453453063964844s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CLTT took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CLTT took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CLTT took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CLTT took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech-cltt took 1.7364394664764404s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Danish took 8.749961853027344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Danish took 0.00043010711669921875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Danish took 0.15257048606872559s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Danish took 0.021614789962768555s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Danish took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Danish took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Danish took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Danish took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-danish took 1.7727842330932617s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch took 4.1484832763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch took 0.00045490264892578125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch took 0.15971136093139648s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch took 0.020774126052856445s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch took 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-dutch took 1.7923989295959473s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch-LassySmall took 4.3392181396484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch-LassySmall took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch-LassySmall took 0.15750455856323242s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch-LassySmall took 0.021936655044555664s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch-LassySmall took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch-LassySmall took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch-LassySmall took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch-LassySmall took 5.4836273193359375e-06s
INFO | --- Analysis for universal-dependencies-treebank-dutch-lassysmall took 1.7841284275054932s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English took 8.535385131835938e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English took 0.15907979011535645s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English took 0.021091461181640625s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English took 0.0010433197021484375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English took 5.173683166503906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-english took 1.7473113536834717s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-ESL took 4.5299530029296875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-ESL took 0.0004978179931640625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-ESL took 0.1640307903289795s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-ESL took 0.022198200225830078s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-ESL took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-ESL took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-ESL took 4.458427429199219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-ESL took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-english-esl took 1.886286735534668s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-LinES took 8.654594421386719e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-LinES took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-LinES took 0.1616804599761963s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-LinES took 0.021260499954223633s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-LinES took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-LinES took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-LinES took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-LinES took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-english-lines took 1.7763071060180664s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Estonian took 4.6253204345703125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Estonian took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Estonian took 0.16599130630493164s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Estonian took 0.02076554298400879s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Estonian took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Estonian took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Estonian took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Estonian took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-estonian took 1.7744994163513184s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish took 8.630752563476562e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish took 0.0004305839538574219s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish took 0.15633225440979004s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish took 0.020905017852783203s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-finnish took 1.8329002857208252s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish-FTB took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish-FTB took 0.0005421638488769531s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish-FTB took 0.1519639492034912s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish-FTB took 0.020479202270507812s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish-FTB took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish-FTB took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish-FTB took 4.100799560546875e-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 1.7933495044708252s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank French took 8.249282836914062e-05s
Availability | VoID file availability check for Universal Dependencies Treebank French took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank French took 0.16476988792419434s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank French took 0.02034616470336914s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank French took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank French took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank French took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank French took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-french took 1.7910866737365723s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician took 8.845329284667969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician took 0.16648530960083008s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician took 0.02048039436340332s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-galician took 1.8004319667816162s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician-TreeGal took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician-TreeGal took 0.0004336833953857422s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician-TreeGal took 0.18270421028137207s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician-TreeGal took 0.020195484161376953s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician-TreeGal took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician-TreeGal took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician-TreeGal took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician-TreeGal took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-galician-treegal took 1.790146827697754s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank German took 8.440017700195312e-05s
Availability | VoID file availability check for Universal Dependencies Treebank German took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank German took 0.15784955024719238s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank German took 0.020406484603881836s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank German took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank German took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank German took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank German took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-german took 1.7835049629211426s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Gothic took 8.273124694824219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Gothic took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Gothic took 0.16733551025390625s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Gothic took 0.020291566848754883s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Gothic took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Gothic took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Gothic took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Gothic took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-gothic took 1.7428808212280273s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Greek took 8.392333984375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Greek took 0.0005471706390380859s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Greek took 0.1633305549621582s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Greek took 0.02033519744873047s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Greek took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Greek took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Greek took 4.553794860839844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Greek took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-greek took 1.7577900886535645s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hebrew took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hebrew took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hebrew took 0.16712522506713867s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hebrew took 0.02104353904724121s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hebrew took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hebrew took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hebrew took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hebrew took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-hebrew took 1.7675318717956543s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hindi took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hindi took 0.0002894401550292969s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hindi took 0.15318799018859863s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hindi took 0.020573854446411133s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hindi took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hindi took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hindi took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hindi took 1.3828277587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-hindi took 1.7991552352905273s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hungarian took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hungarian took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hungarian took 0.16363978385925293s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hungarian took 0.020494699478149414s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hungarian took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hungarian took 0.0007147789001464844s
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 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-hungarian took 1.825847864151001s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Indonesian took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Indonesian took 0.00022482872009277344s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Indonesian took 0.16977596282958984s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Indonesian took 0.02065253257751465s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Indonesian took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Indonesian took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Indonesian took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Indonesian took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-indonesian took 1.7791404724121094s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Irish took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Irish took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Irish took 0.1598801612854004s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Irish took 0.0205233097076416s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Irish took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Irish took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Irish took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Irish took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-irish took 1.7637214660644531s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Italian took 4.5299530029296875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Italian took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Italian took 0.1550438404083252s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Italian took 0.021654605865478516s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Italian took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Italian took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Italian took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Italian took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-italian took 1.8356707096099854s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese took 4.57763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese took 0.1543598175048828s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese took 0.02077031135559082s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-japanese took 1.7690517902374268s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese-KTC took 9.083747863769531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese-KTC took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese-KTC took 0.2800157070159912s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese-KTC took 0.020426034927368164s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese-KTC took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese-KTC took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese-KTC took 6.29425048828125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese-KTC took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-japanese-ktc took 1.8808135986328125s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Kazakh took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Kazakh took 0.0004646778106689453s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Kazakh took 0.16797685623168945s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Kazakh took 0.020550966262817383s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Kazakh took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Kazakh took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Kazakh took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Kazakh took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-kazakh took 1.8686254024505615s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin took 8.177757263183594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin took 0.16199231147766113s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin took 0.02038717269897461s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin took 1.7627274990081787s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-ITTB took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-ITTB took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-ITTB took 0.16243577003479004s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-ITTB took 0.0229339599609375s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-ITTB took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-ITTB took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-ITTB took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-ITTB took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin-ittb took 1.789421558380127s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-PROIEL took 4.506111145019531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-PROIEL took 0.00022292137145996094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-PROIEL took 0.17850255966186523s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-PROIEL took 0.020424604415893555s
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.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-PROIEL took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-PROIEL took 1.0013580322265625e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin-proiel took 1.782996416091919s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latvian took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latvian took 0.00045180320739746094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latvian took 0.1567234992980957s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latvian took 0.02060699462890625s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latvian took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latvian took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latvian took 4.315376281738281e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latvian took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-latvian took 1.7383732795715332s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Norwegian took 6.771087646484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Norwegian took 0.00046563148498535156s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Norwegian took 0.1532151699066162s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Norwegian took 0.020442724227905273s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Norwegian took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Norwegian took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Norwegian took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Norwegian took 1.1205673217773438e-05s
INFO | --- Analysis for universal-dependencies-treebank-norwegian took 1.7704617977142334s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Old_Church_Slavonic took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Old_Church_Slavonic took 0.0006017684936523438s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Old_Church_Slavonic took 0.16124248504638672s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Old_Church_Slavonic took 0.020823240280151367s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Old_Church_Slavonic took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Old_Church_Slavonic took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Old_Church_Slavonic took 4.220008850097656e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Old_Church_Slavonic took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-old-church-slavonic took 1.7583389282226562s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Persian took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Persian took 0.0002193450927734375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Persian took 0.1651904582977295s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Persian took 0.02039194107055664s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Persian took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Persian took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Persian took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Persian took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-persian took 1.7994365692138672s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Polish took 8.440017700195312e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Polish took 0.00043702125549316406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Polish took 0.15581417083740234s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Polish took 0.02074909210205078s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Polish took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Polish took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Polish took 4.7206878662109375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Polish took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-polish took 1.73512601852417s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese took 8.392333984375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese took 0.1658782958984375s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese took 0.02281785011291504s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese took 0.0012052059173583984s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese took 5.8650970458984375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-portuguese took 1.7992544174194336s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-Bosque took 4.673004150390625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-Bosque took 0.0005567073822021484s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-Bosque took 0.16115140914916992s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-Bosque took 0.020676374435424805s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-Bosque took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-Bosque took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-Bosque took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-Bosque took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-bosque took 1.7877421379089355s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-BR took 8.630752563476562e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-BR took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-BR took 0.15766525268554688s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-BR took 0.020903825759887695s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-BR took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-BR took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-BR took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-BR took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-br took 1.7794468402862549s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 8.463859558105469e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0004661083221435547s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.15188932418823242s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.020342588424682617s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-romanian took 1.7517881393432617s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian took 8.153915405273438e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian took 0.15938830375671387s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian took 0.020351409912109375s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian took 3.743171691894531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian took 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-russian took 1.7622096538543701s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian-SynTagRus took 4.458427429199219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian-SynTagRus took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian-SynTagRus took 0.1568620204925537s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian-SynTagRus took 0.02041792869567871s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian-SynTagRus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian-SynTagRus took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian-SynTagRus took 3.695487976074219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian-SynTagRus took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-russian-syntagrus took 1.9552195072174072s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Sanskrit took 8.749961853027344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Sanskrit took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Sanskrit took 0.15775823593139648s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Sanskrit took 0.02199268341064453s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Sanskrit took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Sanskrit took 0.0010039806365966797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Sanskrit took 5.1975250244140625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Sanskrit took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-sanskrit took 1.771235466003418s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovak took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovak took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovak took 0.1625196933746338s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovak took 0.02112126350402832s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovak took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovak took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovak took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovak took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-slovak took 1.7790703773498535s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian took 0.00043511390686035156s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian took 0.15319514274597168s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian took 0.02146291732788086s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-slovenian took 1.7595818042755127s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian-SST took 8.988380432128906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian-SST took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian-SST took 0.1585376262664795s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian-SST took 0.021795272827148438s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian-SST took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian-SST took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian-SST took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian-SST took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-slovenian-sst took 1.7456550598144531s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish took 0.00044846534729003906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish took 0.15319538116455078s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish took 0.02093672752380371s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish took 4.506111145019531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-spanish took 1.7214603424072266s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish-AnCora took 4.482269287109375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish-AnCora took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish-AnCora took 0.15616488456726074s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish-AnCora took 0.02097797393798828s
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.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish-AnCora took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish-AnCora took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-spanish-ancora took 1.7714991569519043s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish took 8.559226989746094e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish took 0.16033291816711426s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish took 0.020655155181884766s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish took 1.7658360004425049s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish-LinES took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish-LinES took 0.0004439353942871094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish-LinES took 0.1666719913482666s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish-LinES took 0.022353410720825195s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish-LinES took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish-LinES took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish-LinES took 4.220008850097656e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish-LinES took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish-lines took 1.7906954288482666s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish_Sign_Language took 6.580352783203125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish_Sign_Language took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish_Sign_Language took 0.15467619895935059s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish_Sign_Language took 0.020900964736938477s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish_Sign_Language took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish_Sign_Language took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish_Sign_Language took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish_Sign_Language took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish-sign-language took 1.844782829284668s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Tamil took 6.985664367675781e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Tamil took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Tamil took 0.1712024211883545s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Tamil took 0.021455049514770508s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Tamil took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Tamil took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Tamil took 4.1961669921875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Tamil took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-tamil took 1.7552270889282227s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Turkish took 8.463859558105469e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Turkish took 0.0004322528839111328s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Turkish took 0.16237330436706543s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Turkish took 0.02085590362548828s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Turkish took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Turkish took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Turkish took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Turkish took 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-turkish took 1.7838637828826904s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ukrainian took 0.00012874603271484375s
Availability | VoID file availability check for Universal Dependencies Treebank Ukrainian took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ukrainian took 0.15960454940795898s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ukrainian took 0.020972251892089844s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ukrainian took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ukrainian took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ukrainian took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ukrainian took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-ukrainian took 1.830259084701538s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Uyghur took 8.463859558105469e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Uyghur took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Uyghur took 0.15778017044067383s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Uyghur took 0.02110457420349121s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Uyghur took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Uyghur took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Uyghur took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Uyghur took 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-uyghur took 1.7736308574676514s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Vietnamese took 0.00010538101196289062s
Availability | VoID file availability check for Universal Dependencies Treebank Vietnamese took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Vietnamese took 0.1589822769165039s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Vietnamese took 0.021260499954223633s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Vietnamese took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Vietnamese took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Vietnamese took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Vietnamese took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-vietnamese took 1.859368085861206s
Availability | SPARQL endpoint availability check for Universidad de Cuenca - LinkedData took 9.608268737792969e-05s
Availability | VoID file availability check for Universidad de Cuenca - LinkedData took 0.000457763671875s
Completeness | Calculation of interlinking completeness for Universidad de Cuenca - LinkedData took 0.16386985778808594s
Reputation | Calculation of the PageRank for Universidad de Cuenca - LinkedData took 0.0205843448638916s
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.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Universidad de Cuenca - LinkedData took 6.794929504394531e-05s
Believability | Calculation of trust value for Universidad de Cuenca - LinkedData took 9.775161743164062e-06s
INFO | --- Analysis for universidad-de-cuenca-linkeddata took 1.79305100440979s
Availability | SPARQL endpoint availability check for University of Plymouth Reading Lists took 8.535385131835938e-05s
Availability | VoID file availability check for University of Plymouth Reading Lists took 0.0004296302795410156s
Completeness | Calculation of interlinking completeness for University of Plymouth Reading Lists took 0.15208029747009277s
Reputation | Calculation of the PageRank for University of Plymouth Reading Lists took 0.022173404693603516s
Interlinking | Calculation of Degree of Connection for University of Plymouth Reading Lists took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for University of Plymouth Reading Lists took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for University of Plymouth Reading Lists took 5.1021575927734375e-05s
Believability | Calculation of trust value for University of Plymouth Reading Lists took 1.0013580322265625e-05s
INFO | --- Analysis for university-plymouth-reading-lists took 1.776413917541504s
Availability | SPARQL endpoint availability check for University of Sussex Reading Lists took 6.628036499023438e-05s
Availability | VoID file availability check for University of Sussex Reading Lists took 0.00020837783813476562s
Completeness | Calculation of interlinking completeness for University of Sussex Reading Lists took 0.15128755569458008s
Reputation | Calculation of the PageRank for University of Sussex Reading Lists took 0.021274089813232422s
Interlinking | Calculation of Degree of Connection for University of Sussex Reading Lists took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for University of Sussex Reading Lists took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for University of Sussex Reading Lists took 3.7670135498046875e-05s
Believability | Calculation of trust value for University of Sussex Reading Lists took 1.2636184692382812e-05s
INFO | --- Analysis for university-sussex-reading-lists took 1.7372701168060303s
Availability | SPARQL endpoint availability check for UNODC - Statistics on criminal justice took 0.00010514259338378906s
Availability | VoID file availability check for UNODC - Statistics on criminal justice took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for UNODC - Statistics on criminal justice took 0.16307950019836426s
Reputation | Calculation of the PageRank for UNODC - Statistics on criminal justice took 0.022432565689086914s
Interlinking | Calculation of Degree of Connection for UNODC - Statistics on criminal justice took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for UNODC - Statistics on criminal justice took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for UNODC - Statistics on criminal justice took 6.890296936035156e-05s
Believability | Calculation of trust value for UNODC - Statistics on criminal justice took 5.4836273193359375e-06s
INFO | --- Analysis for unodc took 1.7776718139648438s
Availability | SPARQL endpoint availability check for Super Ontology took 8.630752563476562e-05s
Availability | VoID file availability check for Super Ontology took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.17964649200439453s
Reputation | Calculation of the PageRank for Super Ontology took 0.022605419158935547s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 9.918212890625e-05s
Believability | Calculation of trust value for Super Ontology took 1.1444091796875e-05s
INFO | --- Analysis for upper-ontology took 1.8212039470672607s
Availability | SPARQL endpoint availability check for Sup_Ont: An Upper Ontology took 8.463859558105469e-05s
Availability | VoID file availability check for Sup_Ont: An Upper Ontology took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for Sup_Ont: An Upper Ontology took 0.15336179733276367s
Reputation | Calculation of the PageRank for Sup_Ont: An Upper Ontology took 0.02128314971923828s
Interlinking | Calculation of Degree of Connection for Sup_Ont: An Upper Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Sup_Ont: An Upper Ontology took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Sup_Ont: An Upper Ontology took 3.695487976074219e-05s
Believability | Calculation of trust value for Sup_Ont: An Upper Ontology took 1.239776611328125e-05s
INFO | --- Analysis for Upper_Ontology took 1.7973527908325195s
Availability | SPARQL endpoint availability check for Urban Atlas dataset took 8.654594421386719e-05s
Availability | VoID file availability check for Urban Atlas dataset took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset took 0.1547229290008545s
Reputation | Calculation of the PageRank for Urban Atlas dataset took 0.020376920700073242s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset took 2.6941299438476562e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset took 3.218650817871094e-05s
Believability | Calculation of trust value for Urban Atlas dataset took 1.2159347534179688e-05s
INFO | --- Analysis for Urban_Atlas_ took 1.7662599086761475s
Availability | SPARQL endpoint availability check for Urban Atlas dataset @PSNC took 8.463859558105469e-05s
Availability | VoID file availability check for Urban Atlas dataset @PSNC took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset @PSNC took 0.1615147590637207s
Reputation | Calculation of the PageRank for Urban Atlas dataset @PSNC took 0.02289128303527832s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset @PSNC took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset @PSNC took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset @PSNC took 3.0994415283203125e-05s
Believability | Calculation of trust value for Urban Atlas dataset @PSNC took 1.239776611328125e-05s
INFO | --- Analysis for Urban_Atlas_Dataset took 1.8189301490783691s
Availability | SPARQL endpoint availability check for URIBurner took 8.58306884765625e-05s
Availability | VoID file availability check for URIBurner took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for URIBurner took 0.15710854530334473s
Reputation | Calculation of the PageRank for URIBurner took 0.02061939239501953s
Interlinking | Calculation of Degree of Connection for URIBurner took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for URIBurner took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for URIBurner took 8.940696716308594e-05s
Believability | Calculation of trust value for URIBurner took 1.239776611328125e-05s
INFO | --- Analysis for uriburner took 1.8382656574249268s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.00011086463928222656s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0004405975341796875s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.15366697311401367s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.020999670028686523s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 3.409385681152344e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.0728836059570312e-05s
INFO | --- Analysis for urn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976 took 1.7460143566131592s
Availability | SPARQL endpoint availability check for Legija Stranaca took 9.942054748535156e-05s
Availability | VoID file availability check for Legija Stranaca took 0.0003018379211425781s
Completeness | Calculation of interlinking completeness for Legija Stranaca took 0.16109681129455566s
Reputation | Calculation of the PageRank for Legija Stranaca took 0.020925521850585938s
Interlinking | Calculation of Degree of Connection for Legija Stranaca took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Legija Stranaca took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Legija Stranaca took 3.218650817871094e-05s
Believability | Calculation of trust value for Legija Stranaca took 1.0728836059570312e-05s
INFO | --- Analysis for Uros_Legija_Susa took 1.7426872253417969s
Availability | SPARQL endpoint availability check for Legija took 8.535385131835938e-05s
Availability | VoID file availability check for Legija took 0.0004496574401855469s
Completeness | Calculation of interlinking completeness for Legija took 0.15552806854248047s
Reputation | Calculation of the PageRank for Legija took 0.02063894271850586s
Interlinking | Calculation of Degree of Connection for Legija took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Legija took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Legija took 3.170967102050781e-05s
Believability | Calculation of trust value for Legija took 1.1205673217773438e-05s
INFO | --- Analysis for Uros_Susa took 1.7622020244598389s
Availability | SPARQL endpoint availability check for USAGE review corpus took 8.630752563476562e-05s
Availability | VoID file availability check for USAGE review corpus took 0.00046563148498535156s
Completeness | Calculation of interlinking completeness for USAGE review corpus took 0.1766510009765625s
Reputation | Calculation of the PageRank for USAGE review corpus took 0.02068185806274414s
Interlinking | Calculation of Degree of Connection for USAGE review corpus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for USAGE review corpus took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for USAGE review corpus took 3.0279159545898438e-05s
Believability | Calculation of trust value for USAGE review corpus took 5.7220458984375e-06s
INFO | --- Analysis for usage-review-corpus took 1.7606596946716309s
Availability | SPARQL endpoint availability check for Universidad Técnica Particular de Loja - Linked Open Data took 8.511543273925781e-05s
Availability | VoID file availability check for Universidad Técnica Particular de Loja - Linked Open Data took 0.0004367828369140625s
Completeness | Calculation of interlinking completeness for Universidad Técnica Particular de Loja - Linked Open Data took 0.151397705078125s
Reputation | Calculation of the PageRank for Universidad Técnica Particular de Loja - Linked Open Data took 0.02182459831237793s
Interlinking | Calculation of Degree of Connection for Universidad Técnica Particular de Loja - Linked Open Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universidad Técnica Particular de Loja - Linked Open Data took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Universidad Técnica Particular de Loja - Linked Open Data took 7.748603820800781e-05s
Believability | Calculation of trust value for Universidad Técnica Particular de Loja - Linked Open Data took 6.198883056640625e-06s
INFO | --- Analysis for utpl-lod took 1.7433972358703613s
Availability | SPARQL endpoint availability check for terrorist attack took 8.487701416015625e-05s
Availability | VoID file availability check for terrorist attack took 0.0004336833953857422s
Completeness | Calculation of interlinking completeness for terrorist attack took 0.1509532928466797s
Reputation | Calculation of the PageRank for terrorist attack took 0.02073192596435547s
Interlinking | Calculation of Degree of Connection for terrorist attack took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for terrorist attack took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for terrorist attack took 3.170967102050781e-05s
Believability | Calculation of trust value for terrorist attack took 1.0967254638671875e-05s
INFO | --- Analysis for varsha took 1.7330822944641113s
Availability | SPARQL endpoint availability check for VA took 4.506111145019531e-05s
Availability | VoID file availability check for VA took 0.0004439353942871094s
Completeness | Calculation of interlinking completeness for VA took 0.15282869338989258s
Reputation | Calculation of the PageRank for VA took 0.02107071876525879s
Interlinking | Calculation of Degree of Connection for VA took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for VA took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for VA took 3.147125244140625e-05s
Believability | Calculation of trust value for VA took 1.0251998901367188e-05s
INFO | --- Analysis for Vehicule_Autonome took 1.7752876281738281s
Availability | SPARQL endpoint availability check for Velez (1744) Index Totius Artis in LiLa took 4.2438507080078125e-05s
Availability | VoID file availability check for Velez (1744) Index Totius Artis in LiLa took 0.000209808349609375s
Completeness | Calculation of interlinking completeness for Velez (1744) Index Totius Artis in LiLa took 0.15929388999938965s
Reputation | Calculation of the PageRank for Velez (1744) Index Totius Artis in LiLa took 0.021135330200195312s
Interlinking | Calculation of Degree of Connection for Velez (1744) Index Totius Artis in LiLa took 1.239776611328125e-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.8623809814453125e-05s
Believability | Calculation of trust value for Velez (1744) Index Totius Artis in LiLa took 1.049041748046875e-05s
INFO | --- Analysis for VelezIndexTotiusArtis took 1.754209280014038s
Availability | SPARQL endpoint availability check for Verrijkt Koninkrijk took 4.291534423828125e-05s
Availability | VoID file availability check for Verrijkt Koninkrijk took 0.00044465065002441406s
Completeness | Calculation of interlinking completeness for Verrijkt Koninkrijk took 0.16336417198181152s
Reputation | Calculation of the PageRank for Verrijkt Koninkrijk took 0.020702600479125977s
Interlinking | Calculation of Degree of Connection for Verrijkt Koninkrijk took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Verrijkt Koninkrijk took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Verrijkt Koninkrijk took 8.416175842285156e-05s
Believability | Calculation of trust value for Verrijkt Koninkrijk took 1.049041748046875e-05s
INFO | --- Analysis for verrijktkoninkrijk took 1.7557728290557861s
Availability | SPARQL endpoint availability check for VIAF: The Virtual International Authority File took 8.96453857421875e-05s
Availability | VoID file availability check for VIAF: The Virtual International Authority File took 0.0004410743713378906s
Completeness | Calculation of interlinking completeness for VIAF: The Virtual International Authority File took 0.15583300590515137s
Reputation | Calculation of the PageRank for VIAF: The Virtual International Authority File took 0.022191762924194336s
Interlinking | Calculation of Degree of Connection for VIAF: The Virtual International Authority File took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for VIAF: The Virtual International Authority File took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for VIAF: The Virtual International Authority File took 0.00017023086547851562s
Believability | Calculation of trust value for VIAF: The Virtual International Authority File took 1.049041748046875e-05s
INFO | --- Analysis for viaf took 1.768352746963501s
Availability | SPARQL endpoint availability check for Vihar Exports took 8.273124694824219e-05s
Availability | VoID file availability check for Vihar Exports took 0.0004298686981201172s
Completeness | Calculation of interlinking completeness for Vihar Exports took 0.1671295166015625s
Reputation | Calculation of the PageRank for Vihar Exports took 0.021675825119018555s
Interlinking | Calculation of Degree of Connection for Vihar Exports took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Vihar Exports took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Vihar Exports took 3.24249267578125e-05s
Believability | Calculation of trust value for Vihar Exports took 1.0251998901367188e-05s
INFO | --- Analysis for Vihar_Exports took 1.7497155666351318s
Availability | SPARQL endpoint availability check for VIVO took 8.153915405273438e-05s
Availability | VoID file availability check for VIVO took 0.0004296302795410156s
Completeness | Calculation of interlinking completeness for VIVO took 0.16091084480285645s
Reputation | Calculation of the PageRank for VIVO took 0.02157306671142578s
Interlinking | Calculation of Degree of Connection for VIVO took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for VIVO took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for VIVO took 7.224082946777344e-05s
Believability | Calculation of trust value for VIVO took 1.0013580322265625e-05s
INFO | --- Analysis for vivo took 1.7898313999176025s
Availability | SPARQL endpoint availability check for VIVO Cornell took 4.4345855712890625e-05s
Availability | VoID file availability check for VIVO Cornell took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for VIVO Cornell took 0.1645827293395996s
Reputation | Calculation of the PageRank for VIVO Cornell took 0.02195119857788086s
Interlinking | Calculation of Degree of Connection for VIVO Cornell took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for VIVO Cornell took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for VIVO Cornell took 8.273124694824219e-05s
Believability | Calculation of trust value for VIVO Cornell took 1.1205673217773438e-05s
INFO | --- Analysis for vivo-cornell-university took 1.7825469970703125s
Availability | SPARQL endpoint availability check for VIVO Indiana took 8.511543273925781e-05s
Availability | VoID file availability check for VIVO Indiana took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for VIVO Indiana took 0.15725255012512207s
Reputation | Calculation of the PageRank for VIVO Indiana took 0.022655487060546875s
Interlinking | Calculation of Degree of Connection for VIVO Indiana took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for VIVO Indiana took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for VIVO Indiana took 9.250640869140625e-05s
Believability | Calculation of trust value for VIVO Indiana took 1.2159347534179688e-05s
INFO | --- Analysis for vivo-indiana-university took 1.7469892501831055s
Availability | SPARQL endpoint availability check for VIVO Ponce took 6.771087646484375e-05s
Availability | VoID file availability check for VIVO Ponce took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for VIVO Ponce took 0.18675804138183594s
Reputation | Calculation of the PageRank for VIVO Ponce took 0.02034306526184082s
Interlinking | Calculation of Degree of Connection for VIVO Ponce took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for VIVO Ponce took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for VIVO Ponce took 3.5762786865234375e-05s
Believability | Calculation of trust value for VIVO Ponce took 1.1682510375976562e-05s
INFO | --- Analysis for vivo-ponce took 1.8169095516204834s
Availability | SPARQL endpoint availability check for VIVO Scripps Research Institute took 4.363059997558594e-05s
Availability | VoID file availability check for VIVO Scripps Research Institute took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for VIVO Scripps Research Institute took 0.1623685359954834s
Reputation | Calculation of the PageRank for VIVO Scripps Research Institute took 0.020766735076904297s
Interlinking | Calculation of Degree of Connection for VIVO Scripps Research Institute took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for VIVO Scripps Research Institute took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for VIVO Scripps Research Institute took 3.838539123535156e-05s
Believability | Calculation of trust value for VIVO Scripps Research Institute took 1.811981201171875e-05s
INFO | --- Analysis for vivo-scripps-research-institute took 1.8034336566925049s
Availability | SPARQL endpoint availability check for VIVO University of Florida took 4.315376281738281e-05s
Availability | VoID file availability check for VIVO University of Florida took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for VIVO University of Florida took 0.15460968017578125s
Reputation | Calculation of the PageRank for VIVO University of Florida took 0.021825075149536133s
Interlinking | Calculation of Degree of Connection for VIVO University of Florida took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for VIVO University of Florida took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for VIVO University of Florida took 0.00010251998901367188s
Believability | Calculation of trust value for VIVO University of Florida took 1.0251998901367188e-05s
INFO | --- Analysis for vivo-university-of-florida took 1.7507133483886719s
Availability | SPARQL endpoint availability check for VIVO Weill Cornell Medical College took 8.511543273925781e-05s
Availability | VoID file availability check for VIVO Weill Cornell Medical College took 0.0004284381866455078s
Completeness | Calculation of interlinking completeness for VIVO Weill Cornell Medical College took 0.15168404579162598s
Reputation | Calculation of the PageRank for VIVO Weill Cornell Medical College took 0.02068018913269043s
Interlinking | Calculation of Degree of Connection for VIVO Weill Cornell Medical College took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for VIVO Weill Cornell Medical College took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for VIVO Weill Cornell Medical College took 3.838539123535156e-05s
Believability | Calculation of trust value for VIVO Weill Cornell Medical College took 9.298324584960938e-06s
INFO | --- Analysis for vivo-weill-cornell-medical-college took 1.7434914112091064s
Availability | SPARQL endpoint availability check for VIVO WUSTL took 4.100799560546875e-05s
Availability | VoID file availability check for VIVO WUSTL took 0.00031447410583496094s
Completeness | Calculation of interlinking completeness for VIVO WUSTL took 131.07511162757874s
Reputation | Calculation of the PageRank for VIVO WUSTL took 0.020895957946777344s
Interlinking | Calculation of Degree of Connection for VIVO WUSTL took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for VIVO WUSTL took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for VIVO WUSTL took 4.839897155761719e-05s
Believability | Calculation of trust value for VIVO WUSTL took 6.198883056640625e-06s
INFO | --- Analysis for vivo-wustl took 394.9019465446472s
Availability | SPARQL endpoint availability check for vivo2doi took 8.392333984375e-05s
Availability | VoID file availability check for vivo2doi took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for vivo2doi took 0.16896677017211914s
Reputation | Calculation of the PageRank for vivo2doi took 0.02075052261352539s
Interlinking | Calculation of Degree of Connection for vivo2doi took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for vivo2doi took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for vivo2doi took 4.029273986816406e-05s
Believability | Calculation of trust value for vivo2doi took 1.049041748046875e-05s
INFO | --- Analysis for vivo2doi took 1.7615563869476318s
Availability | SPARQL endpoint availability check for WordNet 3.0 (VU Amsterdam) took 8.320808410644531e-05s
Availability | VoID file availability check for WordNet 3.0 (VU Amsterdam) took 0.00043964385986328125s
Completeness | Calculation of interlinking completeness for WordNet 3.0 (VU Amsterdam) took 0.15509629249572754s
Reputation | Calculation of the PageRank for WordNet 3.0 (VU Amsterdam) took 0.020511865615844727s
Interlinking | Calculation of Degree of Connection for WordNet 3.0 (VU Amsterdam) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for WordNet 3.0 (VU Amsterdam) took 0.0007925033569335938s
Interlinking | Calculation of Clustering coefficient for WordNet 3.0 (VU Amsterdam) took 7.2479248046875e-05s
Believability | Calculation of trust value for WordNet 3.0 (VU Amsterdam) took 1.33514404296875e-05s
INFO | --- Analysis for vu-wordnet took 1.7411136627197266s
Availability | SPARQL endpoint availability check for vulnerapedia took 8.344650268554688e-05s
Availability | VoID file availability check for vulnerapedia took 0.00045180320739746094s
Completeness | Calculation of interlinking completeness for vulnerapedia took 0.15844392776489258s
Reputation | Calculation of the PageRank for vulnerapedia took 0.02151775360107422s
Interlinking | Calculation of Degree of Connection for vulnerapedia took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for vulnerapedia took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for vulnerapedia took 8.678436279296875e-05s
Believability | Calculation of trust value for vulnerapedia took 1.1682510375976562e-05s
INFO | --- Analysis for vulnerapedia took 1.7639875411987305s
Availability | SPARQL endpoint availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 8.630752563476562e-05s
Availability | VoID file availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.15620684623718262s
Reputation | Calculation of the PageRank for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.020201921463012695s
Interlinking | Calculation of Degree of Connection for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 3.123283386230469e-05s
Believability | Calculation of trust value for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.1682510375976562e-05s
INFO | --- Analysis for VVASIAK took 1.751493215560913s
Availability | SPARQL endpoint availability check for Statybu imone - Vyvasta took 8.177757263183594e-05s
Availability | VoID file availability check for Statybu imone - Vyvasta took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for Statybu imone - Vyvasta took 0.17984318733215332s
Reputation | Calculation of the PageRank for Statybu imone - Vyvasta took 0.020238399505615234s
Interlinking | Calculation of Degree of Connection for Statybu imone - Vyvasta took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Statybu imone - Vyvasta took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Statybu imone - Vyvasta took 2.8133392333984375e-05s
Believability | Calculation of trust value for Statybu imone - Vyvasta took 1.0728836059570312e-05s
INFO | --- Analysis for Vyvasta took 1.8194518089294434s
Availability | SPARQL endpoint availability check for W3C took 5.698204040527344e-05s
Availability | VoID file availability check for W3C took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for W3C took 0.1550300121307373s
Reputation | Calculation of the PageRank for W3C took 0.020634174346923828s
Interlinking | Calculation of Degree of Connection for W3C took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for W3C took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for W3C took 0.00013828277587890625s
Believability | Calculation of trust value for W3C took 1.0967254638671875e-05s
INFO | --- Analysis for w3c took 1.7477436065673828s
Availability | SPARQL endpoint availability check for WordNet 2.0 (W3C) took 8.940696716308594e-05s
Availability | VoID file availability check for WordNet 2.0 (W3C) took 0.000438690185546875s
Completeness | Calculation of interlinking completeness for WordNet 2.0 (W3C) took 0.1747760772705078s
Reputation | Calculation of the PageRank for WordNet 2.0 (W3C) took 0.022243261337280273s
Interlinking | Calculation of Degree of Connection for WordNet 2.0 (W3C) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for WordNet 2.0 (W3C) took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for WordNet 2.0 (W3C) took 0.00013399124145507812s
Believability | Calculation of trust value for WordNet 2.0 (W3C) took 1.0728836059570312e-05s
INFO | --- Analysis for w3c-wordnet took 1.8008882999420166s
Availability | SPARQL endpoint availability check for WarSampo took 0.3522963523864746s
Availability | VoID file availability check for WarSampo took 0.0005488395690917969s
Extra | Recovery of all triples for WarSampo took 157.23415398597717s
Performance | Total latancy measurement for WarSampo took 0.7879810333251953s
Amount of data | Number of triples check for WarSampo took 17.75824809074402s
Interoperability | New terms check for WarSampo took 3.840648889541626s
Versatility | Languages check for WarSampo took 53.59406614303589s
Interpretability | Number of blank nodes check for WarSampo took 17.72888684272766s
Security | Check HTTPS for WarSampo took 0.3803877830505371s
Interpretability | RDF structures check for WarSampo took 0.1823580265045166s
Versatility | Serialization formats check for WarSampo took 0.1911165714263916s
Availability | RDF dump link check for WarSampo took 0.7768731117248535s
License | MR license check for WarSampo took 0.17890071868896484s
License | HR license check for WarSampo took 42.728097438812256s
Amount of data | Number of property check for WarSampo took 0.18163466453552246s
Understandability | Number of label check for WarSampo took 10.562601089477539s
Understandability | URI regex check for WarSampo took 0.33996009826660156s
Understandability | Vocabs check for WarSampo took 0.15355658531188965s
Verifiability | Authors check for WarSampo took 0.18617510795593262s
Verifiability | Publishers check for WarSampo took 0.17783212661743164s
Performance | Throughput check for WarSampo took 10.485603332519531s
Amount of data | Check the number of entities for WarSampo took 14.808770656585693s
Verifiability | Contribs. check for WarSampo took 0.18833684921264648s
Interlinking | sameAs chians check for WarSampo took 0.1859879493713379s
Interlinking | skos check for WarSampo took 0.19440340995788574s
Interlinking | skos check for WarSampo took 0.14880156517028809s
Timeliness | dataset update frequency check for WarSampo took 0.21323084831237793s
Currency | Creation date check for WarSampo took 0.33885693550109863s
Currency | Modification date check for WarSampo took 0.35183143615722656s
Rep.Conc. | URIs length for WarSampo took 87.5464403629303s
Interoperability | New vocabularies check for WarSampo took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for WarSampo took 0.19292902946472168s
Accuracy | Check Functional Property for WarSampo took 0.18706297874450684s
Accuracy | Check Inverse Functional Property for WarSampo took 0.16248464584350586s
Accuracy | Check Empty annotation labels for WarSampo took 50.4145565032959s
Accuracy | Check White space in annotation for WarSampo took 2.1740379333496094s
Accuracy | Check Datatype consistency for WarSampo took 5.38658332824707s
Consistency | Disjoint class check for WarSampo took 0.187300443649292s
Consistency | Check Misplaced properties for WarSampo took 20.35420870780945s
Consistency | Check Ontology hijacking for WarSampo took 58.08282256126404s
Consistency | Check Invalid usage of undefined classes for WarSampo took 1.3379464149475098s
Consistency | Check Invalid usage of undefined properties for WarSampo took 1.5542125701904297s
Conciseness | Check Extensional conciseness for WarSampo took 2.7866642475128174s
Conciseness | Check Intensional conciseness for WarSampo took 0.26288747787475586s
Security | Sign check for WarSampo took 0.16547250747680664s
Availability | Check URIs Dereferenciability for WarSampo took 2.491008996963501s
Completeness | Calculation of interlinking completeness for WarSampo took 0.32857823371887207s
Reputation | Calculation of the PageRank for WarSampo took 0.020927906036376953s
Interlinking | Calculation of Degree of Connection for WarSampo took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for WarSampo took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for WarSampo took 8.916854858398438e-05s
Interoperability | Check the re-using of existing vocabs for WarSampo took 1.6689300537109375e-06s
Believability | Calculation of trust value for WarSampo took 1.0013580322265625e-05s
INFO | --- Analysis for warsampo took 1221.1264808177948s
Availability | SPARQL endpoint availability check for WASABI RDF Knowledge Graph took 20.455251216888428s
Availability | VoID file availability check for WASABI RDF Knowledge Graph took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for WASABI RDF Knowledge Graph took 0.15474796295166016s
Reputation | Calculation of the PageRank for WASABI RDF Knowledge Graph took 0.020633459091186523s
Interlinking | Calculation of Degree of Connection for WASABI RDF Knowledge Graph took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for WASABI RDF Knowledge Graph took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for WASABI RDF Knowledge Graph took 7.510185241699219e-05s
Believability | Calculation of trust value for WASABI RDF Knowledge Graph took 9.775161743164062e-06s
INFO | --- Analysis for wasabi took 52.3579683303833s
Availability | SPARQL endpoint availability check for FAO water areas classification as linked data @PSNC took 4.076957702636719e-05s
Availability | VoID file availability check for FAO water areas classification as linked data @PSNC took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for FAO water areas classification as linked data @PSNC took 0.16065692901611328s
Reputation | Calculation of the PageRank for FAO water areas classification as linked data @PSNC took 0.020601987838745117s
Interlinking | Calculation of Degree of Connection for FAO water areas classification as linked data @PSNC took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for FAO water areas classification as linked data @PSNC took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for FAO water areas classification as linked data @PSNC took 3.0517578125e-05s
Believability | Calculation of trust value for FAO water areas classification as linked data @PSNC took 1.0013580322265625e-05s
INFO | --- Analysis for Water_Areas_Classification took 1.7350475788116455s
Availability | SPARQL endpoint availability check for Water buffer dataset from Czech Republic @PSNC took 4.076957702636719e-05s
Availability | VoID file availability check for Water buffer dataset from Czech Republic @PSNC took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for Water buffer dataset from Czech Republic @PSNC took 0.16167402267456055s
Reputation | Calculation of the PageRank for Water buffer dataset from Czech Republic @PSNC took 0.0206754207611084s
Interlinking | Calculation of Degree of Connection for Water buffer dataset from Czech Republic @PSNC took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Water buffer dataset from Czech Republic @PSNC took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Water buffer dataset from Czech Republic @PSNC took 2.8371810913085938e-05s
Believability | Calculation of trust value for Water buffer dataset from Czech Republic @PSNC took 1.1205673217773438e-05s
INFO | --- Analysis for Water_Buffer took 1.7552647590637207s
Availability | SPARQL endpoint availability check for WebIsALOD took 3.9577484130859375e-05s
Availability | VoID file availability check for WebIsALOD took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for WebIsALOD took 0.1821300983428955s
Reputation | Calculation of the PageRank for WebIsALOD took 0.020469188690185547s
Interlinking | Calculation of Degree of Connection for WebIsALOD took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for WebIsALOD took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for WebIsALOD took 6.961822509765625e-05s
Believability | Calculation of trust value for WebIsALOD took 1.049041748046875e-05s
INFO | --- Analysis for webisalod took 1.8110947608947754s
Availability | SPARQL endpoint availability check for webnmasunotraveler took 8.487701416015625e-05s
Availability | VoID file availability check for webnmasunotraveler took 0.0005824565887451172s
Completeness | Calculation of interlinking completeness for webnmasunotraveler took 0.1659078598022461s
Reputation | Calculation of the PageRank for webnmasunotraveler took 0.020868539810180664s
Interlinking | Calculation of Degree of Connection for webnmasunotraveler took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for webnmasunotraveler took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for webnmasunotraveler took 3.743171691894531e-05s
Believability | Calculation of trust value for webnmasunotraveler took 1.33514404296875e-05s
INFO | --- Analysis for webnmasunotraveler took 1.8227174282073975s
Availability | SPARQL endpoint availability check for Whisky Circle took 8.392333984375e-05s
Availability | VoID file availability check for Whisky Circle took 0.0005397796630859375s
Completeness | Calculation of interlinking completeness for Whisky Circle took 0.16164946556091309s
Reputation | Calculation of the PageRank for Whisky Circle took 0.02215743064880371s
Interlinking | Calculation of Degree of Connection for Whisky Circle took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Whisky Circle took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Whisky Circle took 0.00010776519775390625s
Believability | Calculation of trust value for Whisky Circle took 1.3113021850585938e-05s
INFO | --- Analysis for whisky-circle-info took 1.7442145347595215s
Availability | SPARQL endpoint availability check for Corona Virus Infected Cases Ontology took 8.463859558105469e-05s
Availability | VoID file availability check for Corona Virus Infected Cases Ontology took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for Corona Virus Infected Cases Ontology took 0.15647339820861816s
Reputation | Calculation of the PageRank for Corona Virus Infected Cases Ontology took 0.02061009407043457s
Interlinking | Calculation of Degree of Connection for Corona Virus Infected Cases Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Corona Virus Infected Cases Ontology took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Corona Virus Infected Cases Ontology took 3.6716461181640625e-05s
Believability | Calculation of trust value for Corona Virus Infected Cases Ontology took 1.33514404296875e-05s
INFO | --- Analysis for WHOnto took 1.7532539367675781s
Availability | SPARQL endpoint availability check for COvid-19 statistics Ontology took 8.535385131835938e-05s
Availability | VoID file availability check for COvid-19 statistics Ontology took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for COvid-19 statistics Ontology took 0.15582609176635742s
Reputation | Calculation of the PageRank for COvid-19 statistics Ontology took 0.022365331649780273s
Interlinking | Calculation of Degree of Connection for COvid-19 statistics Ontology took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for COvid-19 statistics Ontology took 0.0009758472442626953s
Interlinking | Calculation of Clustering coefficient for COvid-19 statistics Ontology took 4.100799560546875e-05s
Believability | Calculation of trust value for COvid-19 statistics Ontology took 1.239776611328125e-05s
INFO | --- Analysis for whonto took 1.7506444454193115s
Availability | SPARQL endpoint availability check for Wikidata took 4.2438507080078125e-05s
Availability | VoID file availability check for Wikidata took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for Wikidata took 0.15777134895324707s
Reputation | Calculation of the PageRank for Wikidata took 0.020708084106445312s
Interlinking | Calculation of Degree of Connection for Wikidata took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Wikidata took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Wikidata took 0.0003142356872558594s
Believability | Calculation of trust value for Wikidata took 1.0251998901367188e-05s
INFO | --- Analysis for wikidata took 1.73506498336792s
Availability | SPARQL endpoint availability check for Wikilinks RDF/NIF took 8.20159912109375e-05s
Availability | VoID file availability check for Wikilinks RDF/NIF took 0.00044417381286621094s
Completeness | Calculation of interlinking completeness for Wikilinks RDF/NIF took 0.1651449203491211s
Reputation | Calculation of the PageRank for Wikilinks RDF/NIF took 0.020588397979736328s
Interlinking | Calculation of Degree of Connection for Wikilinks RDF/NIF took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Wikilinks RDF/NIF took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Wikilinks RDF/NIF took 6.699562072753906e-05s
Believability | Calculation of trust value for Wikilinks RDF/NIF took 4.76837158203125e-06s
INFO | --- Analysis for wikilinks-rdf-nif took 1.818361759185791s
Availability | SPARQL endpoint availability check for wiktionary.dbpedia.org took 8.058547973632812e-05s
Availability | VoID file availability check for wiktionary.dbpedia.org took 0.0004451274871826172s
Completeness | Calculation of interlinking completeness for wiktionary.dbpedia.org took 0.15561652183532715s
Reputation | Calculation of the PageRank for wiktionary.dbpedia.org took 0.022490978240966797s
Interlinking | Calculation of Degree of Connection for wiktionary.dbpedia.org took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for wiktionary.dbpedia.org took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for wiktionary.dbpedia.org took 8.368492126464844e-05s
Believability | Calculation of trust value for wiktionary.dbpedia.org took 9.775161743164062e-06s
INFO | --- Analysis for wiktionary-dbpedia-org took 1.7580528259277344s
Availability | SPARQL endpoint availability check for The World Literature Knowledge Graph took 1.2369768619537354s
Availability | VoID file availability check for The World Literature Knowledge Graph took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for The World Literature Knowledge Graph took 0.15552878379821777s
Reputation | Calculation of the PageRank for The World Literature Knowledge Graph took 0.022667646408081055s
Interlinking | Calculation of Degree of Connection for The World Literature Knowledge Graph took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for The World Literature Knowledge Graph took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for The World Literature Knowledge Graph took 3.075599670410156e-05s
Believability | Calculation of trust value for The World Literature Knowledge Graph took 9.775161743164062e-06s
INFO | --- Analysis for wl-kg took 3.2561049461364746s
Availability | SPARQL endpoint availability check for Wordnet-Wikipedia/DBpedia instance mapping took 8.559226989746094e-05s
Availability | VoID file availability check for Wordnet-Wikipedia/DBpedia instance mapping took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for Wordnet-Wikipedia/DBpedia instance mapping took 0.1556224822998047s
Reputation | Calculation of the PageRank for Wordnet-Wikipedia/DBpedia instance mapping took 0.02144765853881836s
Interlinking | Calculation of Degree of Connection for Wordnet-Wikipedia/DBpedia instance mapping took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Wordnet-Wikipedia/DBpedia instance mapping took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Wordnet-Wikipedia/DBpedia instance mapping took 7.009506225585938e-05s
Believability | Calculation of trust value for Wordnet-Wikipedia/DBpedia instance mapping took 1.3113021850585938e-05s
INFO | --- Analysis for wn-wiki-instances took 1.7619433403015137s
Availability | SPARQL endpoint availability check for World Loanword Database took 8.153915405273438e-05s
Availability | VoID file availability check for World Loanword Database took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for World Loanword Database took 0.15332770347595215s
Reputation | Calculation of the PageRank for World Loanword Database took 0.0203244686126709s
Interlinking | Calculation of Degree of Connection for World Loanword Database took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for World Loanword Database took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for World Loanword Database took 6.914138793945312e-05s
Believability | Calculation of trust value for World Loanword Database took 1.0013580322265625e-05s
INFO | --- Analysis for wold took 1.7474069595336914s
Availability | SPARQL endpoint availability check for Wood Trick LLC took 7.891654968261719e-05s
Availability | VoID file availability check for Wood Trick LLC took 0.0004353523254394531s
Completeness | Calculation of interlinking completeness for Wood Trick LLC took 0.15967321395874023s
Reputation | Calculation of the PageRank for Wood Trick LLC took 0.020505189895629883s
Interlinking | Calculation of Degree of Connection for Wood Trick LLC took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Wood Trick LLC took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Wood Trick LLC took 3.123283386230469e-05s
Believability | Calculation of trust value for Wood Trick LLC took 1.0967254638671875e-05s
INFO | --- Analysis for woodtrick took 1.7657990455627441s
Availability | SPARQL endpoint availability check for Word Formation Latin (WFL) in LiLa took 4.363059997558594e-05s
Availability | VoID file availability check for Word Formation Latin (WFL) in LiLa took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for Word Formation Latin (WFL) in LiLa took 0.15476131439208984s
Reputation | Calculation of the PageRank for Word Formation Latin (WFL) in LiLa took 0.021801471710205078s
Interlinking | Calculation of Degree of Connection for Word Formation Latin (WFL) in LiLa took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Word Formation Latin (WFL) in LiLa took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Word Formation Latin (WFL) in LiLa took 3.910064697265625e-05s
Believability | Calculation of trust value for Word Formation Latin (WFL) in LiLa took 1.0013580322265625e-05s
INFO | --- Analysis for WordFormationLatin took 1.790778398513794s
Availability | SPARQL endpoint availability check for WordLift Blog EN took 8.58306884765625e-05s
Availability | VoID file availability check for WordLift Blog EN took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for WordLift Blog EN took 0.15264439582824707s
Reputation | Calculation of the PageRank for WordLift Blog EN took 0.020561933517456055s
Interlinking | Calculation of Degree of Connection for WordLift Blog EN took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for WordLift Blog EN took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for WordLift Blog EN took 0.00010156631469726562s
Believability | Calculation of trust value for WordLift Blog EN took 1.1682510375976562e-05s
INFO | --- Analysis for wordlift-io-blog-en took 1.7387309074401855s
Availability | SPARQL endpoint availability check for WordLift IT took 8.153915405273438e-05s
Availability | VoID file availability check for WordLift IT took 0.0002090930938720703s
Completeness | Calculation of interlinking completeness for WordLift IT took 0.15142488479614258s
Reputation | Calculation of the PageRank for WordLift IT took 0.021767139434814453s
Interlinking | Calculation of Degree of Connection for WordLift IT took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for WordLift IT took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for WordLift IT took 0.00010037422180175781s
Believability | Calculation of trust value for WordLift IT took 1.0013580322265625e-05s
INFO | --- Analysis for wordlift-io-blog-it took 1.7577235698699951s
Availability | SPARQL endpoint availability check for WordNet-RDF took 4.100799560546875e-05s
Availability | VoID file availability check for WordNet-RDF took 0.0004367828369140625s
Completeness | Calculation of interlinking completeness for WordNet-RDF took 0.16840910911560059s
Reputation | Calculation of the PageRank for WordNet-RDF took 0.02060842514038086s
Interlinking | Calculation of Degree of Connection for WordNet-RDF took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for WordNet-RDF took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for WordNet-RDF took 9.036064147949219e-05s
Believability | Calculation of trust value for WordNet-RDF took 9.298324584960938e-06s
INFO | --- Analysis for wordnet-rdf took 1.7518513202667236s
Availability | SPARQL endpoint availability check for wordpress took 8.177757263183594e-05s
Availability | VoID file availability check for wordpress took 0.00020313262939453125s
Completeness | Calculation of interlinking completeness for wordpress took 0.1609506607055664s
Reputation | Calculation of the PageRank for wordpress took 0.02060842514038086s
Interlinking | Calculation of Degree of Connection for wordpress took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for wordpress took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for wordpress took 8.320808410644531e-05s
Believability | Calculation of trust value for wordpress took 1.0013580322265625e-05s
INFO | --- Analysis for wordpress took 1.766749620437622s
Availability | SPARQL endpoint availability check for World Bank Linked Data took 8.58306884765625e-05s
Availability | VoID file availability check for World Bank Linked Data took 0.0005850791931152344s
Completeness | Calculation of interlinking completeness for World Bank Linked Data took 0.16033244132995605s
Reputation | Calculation of the PageRank for World Bank Linked Data took 0.02150106430053711s
Interlinking | Calculation of Degree of Connection for World Bank Linked Data took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for World Bank Linked Data took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for World Bank Linked Data took 0.00011992454528808594s
Believability | Calculation of trust value for World Bank Linked Data took 1.2636184692382812e-05s
INFO | --- Analysis for world-bank-linked-data took 1.7754833698272705s
Availability | SPARQL endpoint availability check for World Factbook (FU Berlin) took 8.177757263183594e-05s
Availability | VoID file availability check for World Factbook (FU Berlin) took 0.00046825408935546875s
Completeness | Calculation of interlinking completeness for World Factbook (FU Berlin) took 0.15311980247497559s
Reputation | Calculation of the PageRank for World Factbook (FU Berlin) took 0.020312070846557617s
Interlinking | Calculation of Degree of Connection for World Factbook (FU Berlin) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for World Factbook (FU Berlin) took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for World Factbook (FU Berlin) took 8.511543273925781e-05s
Believability | Calculation of trust value for World Factbook (FU Berlin) took 9.775161743164062e-06s
INFO | --- Analysis for world-factbook-fu-berlin took 1.8085601329803467s
Availability | SPARQL endpoint availability check for World Wide Web Foundation took 8.225440979003906e-05s
Availability | VoID file availability check for World Wide Web Foundation took 0.0004363059997558594s
Completeness | Calculation of interlinking completeness for World Wide Web Foundation took 0.1630568504333496s
Reputation | Calculation of the PageRank for World Wide Web Foundation took 0.020311832427978516s
Interlinking | Calculation of Degree of Connection for World Wide Web Foundation took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for World Wide Web Foundation took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for World Wide Web Foundation took 8.749961853027344e-05s
Believability | Calculation of trust value for World Wide Web Foundation took 1.0728836059570312e-05s
INFO | --- Analysis for world-wide-web-foundation took 1.7782347202301025s
Availability | SPARQL endpoint availability check for World War 1 as Linked Open Data took 0.1761305332183838s
Availability | VoID file availability check for World War 1 as Linked Open Data took 0.0004494190216064453s
Extra | Recovery of all triples for World War 1 as Linked Open Data took 15.32305645942688s
Performance | Total latancy measurement for World War 1 as Linked Open Data took 0.7720949649810791s
Amount of data | Number of triples check for World War 1 as Linked Open Data took 0.22603869438171387s
Interoperability | New terms check for World War 1 as Linked Open Data took 2.0505549907684326s
Versatility | Languages check for World War 1 as Linked Open Data took 0.3610045909881592s
Interpretability | Number of blank nodes check for World War 1 as Linked Open Data took 0.22835636138916016s
Security | Check HTTPS for World War 1 as Linked Open Data took 0.22946739196777344s
Interpretability | RDF structures check for World War 1 as Linked Open Data took 0.351712703704834s
Versatility | Serialization formats check for World War 1 as Linked Open Data took 0.49159812927246094s
Availability | RDF dump link check for World War 1 as Linked Open Data took 6.448431730270386s
License | MR license check for World War 1 as Linked Open Data took 0.176893949508667s
License | HR license check for World War 1 as Linked Open Data took 1.6183452606201172s
Amount of data | Number of property check for World War 1 as Linked Open Data took 0.17474961280822754s
Understandability | Number of label check for World War 1 as Linked Open Data took 0.3997642993927002s
Understandability | URI regex check for World War 1 as Linked Open Data took 0.3463773727416992s
Understandability | Vocabs check for World War 1 as Linked Open Data took 0.21116232872009277s
Verifiability | Authors check for World War 1 as Linked Open Data took 0.17619824409484863s
Verifiability | Publishers check for World War 1 as Linked Open Data took 0.1751565933227539s
Performance | Throughput check for World War 1 as Linked Open Data took 10.570170402526855s
Amount of data | Check the number of entities for World War 1 as Linked Open Data took 0.0717611312866211s
Verifiability | Contribs. check for World War 1 as Linked Open Data took 0.17673325538635254s
Interlinking | sameAs chians check for World War 1 as Linked Open Data took 0.22134733200073242s
Interlinking | skos check for World War 1 as Linked Open Data took 0.17839431762695312s
Interlinking | skos check for World War 1 as Linked Open Data took 0.1496872901916504s
Timeliness | dataset update frequency check for World War 1 as Linked Open Data took 0.17150044441223145s
Currency | Creation date check for World War 1 as Linked Open Data took 0.35347771644592285s
Currency | Modification date check for World War 1 as Linked Open Data took 0.1834125518798828s
Rep.Conc. | URIs length for World War 1 as Linked Open Data took 3.420639991760254s
Interoperability | New vocabularies check for World War 1 as Linked Open Data took 79.91351985931396s
Consistency | Deprecated classes/propertiers check for World War 1 as Linked Open Data took 0.1996915340423584s
Accuracy | Check Functional Property for World War 1 as Linked Open Data took 0.17503595352172852s
Accuracy | Check Inverse Functional Property for World War 1 as Linked Open Data took 0.1509716510772705s
Accuracy | Check Empty annotation labels for World War 1 as Linked Open Data took 1.6903181076049805s
Accuracy | Check White space in annotation for World War 1 as Linked Open Data took 0.049353599548339844s
Accuracy | Check Datatype consistency for World War 1 as Linked Open Data took 0.31229519844055176s
Consistency | Disjoint class check for World War 1 as Linked Open Data took 0.17438960075378418s
Consistency | Check Misplaced properties for World War 1 as Linked Open Data took 0.5622138977050781s
Consistency | Check Ontology hijacking for World War 1 as Linked Open Data took 2.227293014526367s
Consistency | Check Invalid usage of undefined classes for World War 1 as Linked Open Data took 1.289088249206543s
Consistency | Check Invalid usage of undefined properties for World War 1 as Linked Open Data took 1.5166349411010742s
Conciseness | Check Extensional conciseness for World War 1 as Linked Open Data took 0.19043469429016113s
Conciseness | Check Intensional conciseness for World War 1 as Linked Open Data took 0.6371614933013916s
Security | Sign check for World War 1 as Linked Open Data took 0.18224835395812988s
Availability | Check URIs Dereferenciability for World War 1 as Linked Open Data took 1460.677217721939s
Completeness | Calculation of interlinking completeness for World War 1 as Linked Open Data took 0.5133998394012451s
Reputation | Calculation of the PageRank for World War 1 as Linked Open Data took 0.021246910095214844s
Interlinking | Calculation of Degree of Connection for World War 1 as Linked Open Data took 6.985664367675781e-05s
Interlinking | Calculation of Centrality for World War 1 as Linked Open Data took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for World War 1 as Linked Open Data took 9.393692016601562e-05s
Interoperability | Check the re-using of existing vocabs for World War 1 as Linked Open Data took 441.5092854499817s
Believability | Calculation of trust value for World War 1 as Linked Open Data took 1.2159347534179688e-05s
INFO | --- Analysis for ww1lod took 2062.271317720413s
Availability | SPARQL endpoint availability check for xLiD-Lexica took 4.00543212890625e-05s
Availability | VoID file availability check for xLiD-Lexica took 0.0004394054412841797s
Completeness | Calculation of interlinking completeness for xLiD-Lexica took 0.1866292953491211s
Reputation | Calculation of the PageRank for xLiD-Lexica took 0.020785093307495117s
Interlinking | Calculation of Degree of Connection for xLiD-Lexica took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for xLiD-Lexica took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for xLiD-Lexica took 8.177757263183594e-05s
Believability | Calculation of trust value for xLiD-Lexica took 1.1920928955078125e-05s
INFO | --- Analysis for xlid-lexica took 1.790400743484497s
Availability | SPARQL endpoint availability check for Open Multilingual Wordnet took 4.458427429199219e-05s
Availability | VoID file availability check for Open Multilingual Wordnet took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for Open Multilingual Wordnet took 0.1595306396484375s
Reputation | Calculation of the PageRank for Open Multilingual Wordnet took 0.02044534683227539s
Interlinking | Calculation of Degree of Connection for Open Multilingual Wordnet took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Multilingual Wordnet took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Open Multilingual Wordnet took 3.814697265625e-05s
Believability | Calculation of trust value for Open Multilingual Wordnet took 7.3909759521484375e-06s
INFO | --- Analysis for xwn took 1.802706003189087s
Availability | SPARQL endpoint availability check for xxx took 8.702278137207031e-05s
Availability | VoID file availability check for xxx took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for xxx took 0.16182374954223633s
Reputation | Calculation of the PageRank for xxx took 0.020866870880126953s
Interlinking | Calculation of Degree of Connection for xxx took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for xxx took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for xxx took 3.1948089599609375e-05s
Believability | Calculation of trust value for xxx took 1.2159347534179688e-05s
INFO | --- Analysis for xx took 1.7369167804718018s
Availability | SPARQL endpoint availability check for YAGO took 8.535385131835938e-05s
Availability | VoID file availability check for YAGO took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for YAGO took 0.1550157070159912s
Reputation | Calculation of the PageRank for YAGO took 0.02250957489013672s
Interlinking | Calculation of Degree of Connection for YAGO took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for YAGO took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for YAGO took 0.0001304149627685547s
Believability | Calculation of trust value for YAGO took 1.2159347534179688e-05s
INFO | --- Analysis for yago took 1.7478537559509277s
Availability | SPARQL endpoint availability check for Yahoo Geoplanet RDF took 8.249282836914062e-05s
Availability | VoID file availability check for Yahoo Geoplanet RDF took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for Yahoo Geoplanet RDF took 0.16037297248840332s
Reputation | Calculation of the PageRank for Yahoo Geoplanet RDF took 0.020255088806152344s
Interlinking | Calculation of Degree of Connection for Yahoo Geoplanet RDF took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Yahoo Geoplanet RDF took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Yahoo Geoplanet RDF took 7.605552673339844e-05s
Believability | Calculation of trust value for Yahoo Geoplanet RDF took 1.1920928955078125e-05s
INFO | --- Analysis for yahoo_geoplanet took 1.7867872714996338s
Availability | SPARQL endpoint availability check for Yale Senselab took 9.965896606445312e-05s
Availability | VoID file availability check for Yale Senselab took 0.0008220672607421875s
Completeness | Calculation of interlinking completeness for Yale Senselab took 0.16233563423156738s
Reputation | Calculation of the PageRank for Yale Senselab took 0.021031856536865234s
Interlinking | Calculation of Degree of Connection for Yale Senselab took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Yale Senselab took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Yale Senselab took 2.7894973754882812e-05s
Believability | Calculation of trust value for Yale Senselab took 1.1920928955078125e-05s
INFO | --- Analysis for yale_senselab took 1.7374303340911865s
Availability | SPARQL endpoint availability check for test-dapp-2 took 8.344650268554688e-05s
Availability | VoID file availability check for test-dapp-2 took 0.0004642009735107422s
Completeness | Calculation of interlinking completeness for test-dapp-2 took 0.15693068504333496s
Reputation | Calculation of the PageRank for test-dapp-2 took 0.020534276962280273s
Interlinking | Calculation of Degree of Connection for test-dapp-2 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for test-dapp-2 took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for test-dapp-2 took 2.9325485229492188e-05s
Believability | Calculation of trust value for test-dapp-2 took 1.1682510375976562e-05s
INFO | --- Analysis for yordhis took 1.74574875831604s
Availability | SPARQL endpoint availability check for Yovisto - academic video search took 7.295608520507812e-05s
Availability | VoID file availability check for Yovisto - academic video search took 0.0005645751953125s
Completeness | Calculation of interlinking completeness for Yovisto - academic video search took 0.1677711009979248s
Reputation | Calculation of the PageRank for Yovisto - academic video search took 0.020351648330688477s
Interlinking | Calculation of Degree of Connection for Yovisto - academic video search took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Yovisto - academic video search took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Yovisto - academic video search took 6.67572021484375e-05s
Believability | Calculation of trust value for Yovisto - academic video search took 1.1682510375976562e-05s
INFO | --- Analysis for yovisto took 1.7749834060668945s
Availability | SPARQL endpoint availability check for YSA - General Finnish Thesaurus took 4.220008850097656e-05s
Availability | VoID file availability check for YSA - General Finnish Thesaurus took 0.0004305839538574219s
Completeness | Calculation of interlinking completeness for YSA - General Finnish Thesaurus took 0.16401982307434082s
Reputation | Calculation of the PageRank for YSA - General Finnish Thesaurus took 0.02169966697692871s
Interlinking | Calculation of Degree of Connection for YSA - General Finnish Thesaurus took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for YSA - General Finnish Thesaurus took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for YSA - General Finnish Thesaurus took 3.504753112792969e-05s
Believability | Calculation of trust value for YSA - General Finnish Thesaurus took 1.0013580322265625e-05s
INFO | --- Analysis for ysa took 1.7892100811004639s
Availability | SPARQL endpoint availability check for YSO - General Finnish Ontology took 8.869171142578125e-05s
Availability | VoID file availability check for YSO - General Finnish Ontology took 0.00045371055603027344s
Completeness | Calculation of interlinking completeness for YSO - General Finnish Ontology took 0.15198135375976562s
Reputation | Calculation of the PageRank for YSO - General Finnish Ontology took 0.02065420150756836s
Interlinking | Calculation of Degree of Connection for YSO - General Finnish Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for YSO - General Finnish Ontology took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for YSO - General Finnish Ontology took 5.245208740234375e-05s
Believability | Calculation of trust value for YSO - General Finnish Ontology took 9.5367431640625e-06s
INFO | --- Analysis for yso took 1.745239019393921s
Availability | SPARQL endpoint availability check for yso-fi-allars took 8.511543273925781e-05s
Availability | VoID file availability check for yso-fi-allars took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for yso-fi-allars took 0.16729283332824707s
Reputation | Calculation of the PageRank for yso-fi-allars took 0.02094101905822754s
Interlinking | Calculation of Degree of Connection for yso-fi-allars took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for yso-fi-allars took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for yso-fi-allars took 3.4809112548828125e-05s
Believability | Calculation of trust value for yso-fi-allars took 1.239776611328125e-05s
INFO | --- Analysis for yso-fi-allars took 1.8407950401306152s
Availability | SPARQL endpoint availability check for yso-fi-ysa took 4.029273986816406e-05s
Availability | VoID file availability check for yso-fi-ysa took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for yso-fi-ysa took 0.1614372730255127s
Reputation | Calculation of the PageRank for yso-fi-ysa took 0.021502256393432617s
Interlinking | Calculation of Degree of Connection for yso-fi-ysa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for yso-fi-ysa took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for yso-fi-ysa took 3.0994415283203125e-05s
Believability | Calculation of trust value for yso-fi-ysa took 1.1920928955078125e-05s
INFO | --- Analysis for yso-fi-ysa took 1.8079211711883545s
Availability | SPARQL endpoint availability check for YSO places took 4.00543212890625e-05s
Availability | VoID file availability check for YSO places took 0.0005905628204345703s
Completeness | Calculation of interlinking completeness for YSO places took 0.15636849403381348s
Reputation | Calculation of the PageRank for YSO places took 0.020496606826782227s
Interlinking | Calculation of Degree of Connection for YSO places took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for YSO places took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for YSO places took 2.765655517578125e-05s
Believability | Calculation of trust value for YSO places took 1.2874603271484375e-05s
INFO | --- Analysis for yso-paikat took 1.7278187274932861s
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.0004916191101074219s
Completeness | Calculation of interlinking completeness for Datos Abiertos de Zaragoza took 0.15225553512573242s
Reputation | Calculation of the PageRank for Datos Abiertos de Zaragoza took 0.022816896438598633s
Interlinking | Calculation of Degree of Connection for Datos Abiertos de Zaragoza took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Datos Abiertos de Zaragoza took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Datos Abiertos de Zaragoza took 3.123283386230469e-05s
Believability | Calculation of trust value for Datos Abiertos de Zaragoza took 1.2636184692382812e-05s
INFO | --- Analysis for zaragoza-datosabiertos took 1.7773938179016113s
Availability | SPARQL endpoint availability check for zaragoza_turruta took 8.630752563476562e-05s
Availability | VoID file availability check for zaragoza_turruta took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for zaragoza_turruta took 0.163590669631958s
Reputation | Calculation of the PageRank for zaragoza_turruta took 0.022176265716552734s
Interlinking | Calculation of Degree of Connection for zaragoza_turruta took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for zaragoza_turruta took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for zaragoza_turruta took 3.314018249511719e-05s
Believability | Calculation of trust value for zaragoza_turruta took 1.1682510375976562e-05s
INFO | --- Analysis for zaragoza_turruta took 1.7579994201660156s
Availability | SPARQL endpoint availability check for ZBW Labs took 4.2438507080078125e-05s
Availability | VoID file availability check for ZBW Labs took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for ZBW Labs took 0.15114235877990723s
Reputation | Calculation of the PageRank for ZBW Labs took 0.02139425277709961s
Interlinking | Calculation of Degree of Connection for ZBW Labs took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ZBW Labs took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for ZBW Labs took 6.461143493652344e-05s
Believability | Calculation of trust value for ZBW Labs took 1.2159347534179688e-05s
INFO | --- Analysis for zbw-labs took 1.7363474369049072s
Availability | SPARQL endpoint availability check for 20th Century Press Archives took 0.24711203575134277s
Availability | VoID file availability check for 20th Century Press Archives took 0.0005354881286621094s
Extra | Recovery of all triples for 20th Century Press Archives took 58.02845573425293s
Performance | Total latancy measurement for 20th Century Press Archives took 0.7422783374786377s
Amount of data | Number of triples check for 20th Century Press Archives took 1.0447397232055664s
Interoperability | New terms check for 20th Century Press Archives took 1.844224452972412s
Versatility | Languages check for 20th Century Press Archives took 3.034916400909424s
Interpretability | Number of blank nodes check for 20th Century Press Archives took 0.12190675735473633s
Interpretability | RDF structures check for 20th Century Press Archives took 0.14454960823059082s
Versatility | Serialization formats check for 20th Century Press Archives took 0.15297245979309082s
Availability | RDF dump link check for 20th Century Press Archives took 0.12581944465637207s
License | MR license check for 20th Century Press Archives took 0.12515616416931152s
License | HR license check for 20th Century Press Archives took 5.585636854171753s
Amount of data | Number of property check for 20th Century Press Archives took 0.1514146327972412s
Understandability | Number of label check for 20th Century Press Archives took 0.4947826862335205s
Understandability | URI regex check for 20th Century Press Archives took 0.2695884704589844s
Understandability | Vocabs check for 20th Century Press Archives took 0.12805891036987305s
Verifiability | Authors check for 20th Century Press Archives took 0.14230108261108398s
Verifiability | Publishers check for 20th Century Press Archives took 0.1288924217224121s
Performance | Throughput check for 20th Century Press Archives took 10.354942560195923s
Amount of data | Check the number of entities for 20th Century Press Archives took 0.00010538101196289062s
Verifiability | Contribs. check for 20th Century Press Archives took 0.12980175018310547s
Interlinking | sameAs chians check for 20th Century Press Archives took 0.132979154586792s
Interlinking | skos check for 20th Century Press Archives took 0.17041373252868652s
Interlinking | skos check for 20th Century Press Archives took 0.1652204990386963s
Timeliness | dataset update frequency check for 20th Century Press Archives took 0.13444185256958008s
Currency | Creation date check for 20th Century Press Archives took 0.2582426071166992s
Currency | Modification date check for 20th Century Press Archives took 0.267270565032959s
Rep.Conc. | URIs length for 20th Century Press Archives took 18.520704984664917s
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.12756919860839844s
Accuracy | Check Functional Property for 20th Century Press Archives took 0.12848901748657227s
Accuracy | Check Inverse Functional Property for 20th Century Press Archives took 0.1289811134338379s
Accuracy | Check Empty annotation labels for 20th Century Press Archives took 8.685190916061401s
Accuracy | Check White space in annotation for 20th Century Press Archives took 0.8710582256317139s
Accuracy | Check Datatype consistency for 20th Century Press Archives took 4.01087760925293s
Consistency | Disjoint class check for 20th Century Press Archives took 0.14453125s
Consistency | Check Misplaced properties for 20th Century Press Archives took 2.782449722290039s
Consistency | Check Ontology hijacking for 20th Century Press Archives took 3.3521077632904053s
Consistency | Check Invalid usage of undefined classes for 20th Century Press Archives took 6.9071125984191895s
Consistency | Check Invalid usage of undefined properties for 20th Century Press Archives took 3.4253668785095215s
Conciseness | Check Extensional conciseness for 20th Century Press Archives took 2.7690045833587646s
Security | Sign check for 20th Century Press Archives took 0.15004467964172363s
Availability | Check URIs Dereferenciability for 20th Century Press Archives took 1.7307558059692383s
Completeness | Calculation of interlinking completeness for 20th Century Press Archives took 0.19463038444519043s
Reputation | Calculation of the PageRank for 20th Century Press Archives took 0.020989656448364258s
Interlinking | Calculation of Degree of Connection for 20th Century Press Archives took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for 20th Century Press Archives took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for 20th Century Press Archives took 0.00010251998901367188s
Interoperability | Check the re-using of existing vocabs for 20th Century Press Archives took 2.384185791015625e-06s
Believability | Calculation of trust value for 20th Century Press Archives took 1.33514404296875e-05s
INFO | --- Analysis for zbw-pressemappe20 took 155.44963192939758s
Availability | SPARQL endpoint availability check for zhishi.lemon took 4.506111145019531e-05s
Availability | VoID file availability check for zhishi.lemon took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for zhishi.lemon took 0.16109704971313477s
Reputation | Calculation of the PageRank for zhishi.lemon took 0.020674943923950195s
Interlinking | Calculation of Degree of Connection for zhishi.lemon took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for zhishi.lemon took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for zhishi.lemon took 4.38690185546875e-05s
Believability | Calculation of trust value for zhishi.lemon took 9.775161743164062e-06s
INFO | --- Analysis for zhishi-lemon took 1.7501647472381592s
Availability | SPARQL endpoint availability check for Zhishi.me took 8.296966552734375e-05s
Availability | VoID file availability check for Zhishi.me took 0.0004405975341796875s
Completeness | Calculation of interlinking completeness for Zhishi.me took 0.15839028358459473s
Reputation | Calculation of the PageRank for Zhishi.me took 0.020554304122924805s
Interlinking | Calculation of Degree of Connection for Zhishi.me took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Zhishi.me took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Zhishi.me took 6.937980651855469e-05s
Believability | Calculation of trust value for Zhishi.me took 1.0013580322265625e-05s
INFO | --- Analysis for zhishi-me took 1.7401683330535889s
Availability | SPARQL endpoint availability check for MusicBrainz (zitgist.com) took 8.368492126464844e-05s
Availability | VoID file availability check for MusicBrainz (zitgist.com) took 0.0002148151397705078s
Completeness | Calculation of interlinking completeness for MusicBrainz (zitgist.com) took 0.15912222862243652s
Reputation | Calculation of the PageRank for MusicBrainz (zitgist.com) took 0.022284507751464844s
Interlinking | Calculation of Degree of Connection for MusicBrainz (zitgist.com) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for MusicBrainz (zitgist.com) took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for MusicBrainz (zitgist.com) took 6.341934204101562e-05s
Believability | Calculation of trust value for MusicBrainz (zitgist.com) took 9.298324584960938e-06s
INFO | --- Analysis for zitgist-musicbrainz took 1.7393627166748047s
Availability | SPARQL endpoint availability check for 红色经典歌曲关联数据集 took 8.368492126464844e-05s
Availability | VoID file availability check for 红色经典歌曲关联数据集 took 0.0004398822784423828s
Completeness | Calculation of interlinking completeness for 红色经典歌曲关联数据集 took 0.1569652557373047s
Reputation | Calculation of the PageRank for 红色经典歌曲关联数据集 took 0.02236175537109375s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲关联数据集 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲关联数据集 took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲关联数据集 took 3.075599670410156e-05s
Believability | Calculation of trust value for 红色经典歌曲关联数据集 took 1.1444091796875e-05s
INFO | --- Analysis for 红色经典歌曲关联数据集 took 1.7444560527801514s
Availability | SPARQL endpoint availability check for performing-arts.ch took 0.2998499870300293s
Availability | VoID file availability check for performing-arts.ch took 0.0004706382751464844s
Extra | Recovery of all triples for performing-arts.ch took 72.03100848197937s
Performance | Total latancy measurement for performing-arts.ch took 0.662041187286377s
Amount of data | Number of triples check for performing-arts.ch took 28.35818886756897s
Interoperability | New terms check for performing-arts.ch took 1.4265995025634766s
Versatility | Languages check for performing-arts.ch took 60.12951159477234s
Interpretability | Number of blank nodes check for performing-arts.ch took 56.44616174697876s
Interpretability | RDF structures check for performing-arts.ch took 0.15163946151733398s
Versatility | Serialization formats check for performing-arts.ch took 0.1504354476928711s
Availability | RDF dump link check for performing-arts.ch took 0.130767822265625s
License | MR license check for performing-arts.ch took 0.14309215545654297s
License | HR license check for performing-arts.ch took 51.28307032585144s
Amount of data | Number of property check for performing-arts.ch took 0.16624784469604492s
Understandability | Number of label check for performing-arts.ch took 2.4589426517486572s
Understandability | URI regex check for performing-arts.ch took 0.28666090965270996s
Understandability | Vocabs check for performing-arts.ch took 0.14128899574279785s
Verifiability | Authors check for performing-arts.ch took 0.14777803421020508s
Verifiability | Publishers check for performing-arts.ch took 0.14670944213867188s
Performance | Throughput check for performing-arts.ch took 11.044458627700806s
Amount of data | Check the number of entities for performing-arts.ch took 6.985664367675781e-05s
Verifiability | Contribs. check for performing-arts.ch took 0.1432628631591797s
Interlinking | sameAs chians check for performing-arts.ch took 0.3262760639190674s
Interlinking | skos check for performing-arts.ch took 0.15439867973327637s
Interlinking | skos check for performing-arts.ch took 0.1582036018371582s
Timeliness | dataset update frequency check for performing-arts.ch took 0.15125226974487305s
Currency | Creation date check for performing-arts.ch took 0.29201817512512207s
Currency | Modification date check for performing-arts.ch took 0.2889533042907715s
Rep.Conc. | URIs length for performing-arts.ch took 21.337376594543457s
Interoperability | New vocabularies check for performing-arts.ch took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for performing-arts.ch took 0.13877439498901367s
Accuracy | Check Functional Property for performing-arts.ch took 0.1411752700805664s
Accuracy | Check Inverse Functional Property for performing-arts.ch took 0.13835811614990234s
Accuracy | Check Empty annotation labels for performing-arts.ch took 10.385905265808105s
Accuracy | Check White space in annotation for performing-arts.ch took 2.523510456085205s
Accuracy | Check Datatype consistency for performing-arts.ch took 5.820678234100342s
Consistency | Disjoint class check for performing-arts.ch took 0.14362573623657227s
Consistency | Check Misplaced properties for performing-arts.ch took 0.3487849235534668s
Consistency | Misplaced classes for performing-arts.ch took 8.249665260314941s
Consistency | Check Ontology hijacking for performing-arts.ch took 39.14603662490845s
Consistency | Check Invalid usage of undefined classes for performing-arts.ch took 15539.591301441193s
Consistency | Check Invalid usage of undefined properties for performing-arts.ch took 1.7829186916351318s
Conciseness | Check Extensional conciseness for performing-arts.ch took 2.84299373626709s
Conciseness | Check Intensional conciseness for performing-arts.ch took 0.2759530544281006s
Security | Sign check for performing-arts.ch took 0.1485295295715332s
Availability | Check URIs Dereferenciability for performing-arts.ch took 3.221188545227051s
Completeness | Calculation of interlinking completeness for performing-arts.ch took 0.4285547733306885s
Reputation | Calculation of the PageRank for performing-arts.ch took 0.021070003509521484s
Interlinking | Calculation of Degree of Connection for performing-arts.ch took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for performing-arts.ch took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for performing-arts.ch took 2.2411346435546875e-05s
Interoperability | Check the re-using of existing vocabs for performing-arts.ch took 2.1457672119140625e-06s
Believability | Calculation of trust value for performing-arts.ch took 1.2159347534179688e-05s
INFO | --- Analysis for performing-arts.ch took 16383.010139465332s
Availability | SPARQL endpoint availability check for The Art & Architecture Thesaurus took 2.512526035308838s
Availability | VoID file availability check for The Art & Architecture Thesaurus took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for The Art & Architecture Thesaurus took 0.15330815315246582s
Reputation | Calculation of the PageRank for The Art & Architecture Thesaurus took 0.020743608474731445s
Interlinking | Calculation of Degree of Connection for The Art & Architecture Thesaurus took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for The Art & Architecture Thesaurus took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for The Art & Architecture Thesaurus took 1.2874603271484375e-05s
Believability | Calculation of trust value for The Art & Architecture Thesaurus took 1.0728836059570312e-05s
INFO | --- Analysis for The-AA-Thesaurus took 7.233941555023193s
Availability | SPARQL endpoint availability check for MiMoTextBase took 1.2892611026763916s
Availability | VoID file availability check for MiMoTextBase took 0.001352548599243164s
Completeness | Calculation of interlinking completeness for MiMoTextBase took 0.157029390335083s
Reputation | Calculation of the PageRank for MiMoTextBase took 0.020724773406982422s
Interlinking | Calculation of Degree of Connection for MiMoTextBase took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for MiMoTextBase took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for MiMoTextBase took 1.2874603271484375e-05s
Believability | Calculation of trust value for MiMoTextBase took 1.3113021850585938e-05s
INFO | --- Analysis for MiMoTextBase took 4.4108006954193115s
Availability | SPARQL endpoint availability check for National Library of Sweden took 0.5191483497619629s
Availability | VoID file availability check for National Library of Sweden took 0.0006761550903320312s
Extra | Recovery of all triples for National Library of Sweden took 6.72422194480896s
Performance | Total latancy measurement for National Library of Sweden took 0.9827392101287842s
Amount of data | Number of triples check for National Library of Sweden took 24.928420305252075s
Interoperability | New terms check for National Library of Sweden took 15.65359354019165s
Versatility | Languages check for National Library of Sweden took 0.20066142082214355s
Interpretability | Number of blank nodes check for National Library of Sweden took 300.14695620536804s
Interpretability | RDF structures check for National Library of Sweden took 0.3074018955230713s
Versatility | Serialization formats check for National Library of Sweden took 0.22891020774841309s
Availability | RDF dump link check for National Library of Sweden took 0.19758224487304688s
License | MR license check for National Library of Sweden took 0.21863698959350586s
License | HR license check for National Library of Sweden took 0.3124983310699463s
Amount of data | Number of property check for National Library of Sweden took 0.19970130920410156s
Understandability | Number of label check for National Library of Sweden took 0.3827321529388428s
Understandability | URI regex check for National Library of Sweden took 0.49657607078552246s
Understandability | Vocabs check for National Library of Sweden took 0.2033088207244873s
Verifiability | Authors check for National Library of Sweden took 0.20841550827026367s
Verifiability | Publishers check for National Library of Sweden took 0.23685193061828613s
Performance | Throughput check for National Library of Sweden took 11.730604648590088s
Amount of data | Check the number of entities for National Library of Sweden took 6.914138793945312e-05s
Verifiability | Contribs. check for National Library of Sweden took 0.21879053115844727s
Interlinking | sameAs chians check for National Library of Sweden took 0.2281665802001953s
Interlinking | skos check for National Library of Sweden took 0.20621085166931152s
Interlinking | skos check for National Library of Sweden took 0.19460010528564453s
Timeliness | dataset update frequency check for National Library of Sweden took 0.19978117942810059s
Currency | Creation date check for National Library of Sweden took 0.39408421516418457s
Currency | Modification date check for National Library of Sweden took 0.4604659080505371s
Rep.Conc. | URIs length for National Library of Sweden took 83.87674808502197s
Interoperability | New vocabularies check for National Library of Sweden took 6.9141387939453125e-06s
Consistency | Deprecated classes/propertiers check for National Library of Sweden took 0.20359134674072266s
Accuracy | Check Functional Property for National Library of Sweden took 0.1988379955291748s
Accuracy | Check Inverse Functional Property for National Library of Sweden took 0.19258522987365723s
Accuracy | Check Datatype consistency for National Library of Sweden took 0.2729513645172119s
Consistency | Disjoint class check for National Library of Sweden took 0.19716835021972656s
Consistency | Check Misplaced properties for National Library of Sweden took 60.64411401748657s
Consistency | Misplaced classes for National Library of Sweden took 1.0982496738433838s
Consistency | Check Ontology hijacking for National Library of Sweden took 3.177847146987915s
Consistency | Check Invalid usage of undefined classes for National Library of Sweden took 1.2762765884399414s
Consistency | Check Invalid usage of undefined properties for National Library of Sweden took 61.84262728691101s
Conciseness | Check Extensional conciseness for National Library of Sweden took 0.28115010261535645s
Conciseness | Check Intensional conciseness for National Library of Sweden took 0.3478209972381592s
Security | Sign check for National Library of Sweden took 0.33130669593811035s
Availability | Check URIs Dereferenciability for National Library of Sweden took 12.533897876739502s
Completeness | Calculation of interlinking completeness for National Library of Sweden took 0.22800660133361816s
Reputation | Calculation of the PageRank for National Library of Sweden took 0.020545005798339844s
Interlinking | Calculation of Degree of Connection for National Library of Sweden took 2.5033950805664062e-05s
Interlinking | Calculation of Centrality for National Library of Sweden took 0.0006759166717529297s
Interlinking | Calculation of Clustering coefficient for National Library of Sweden took 2.1696090698242188e-05s
Interoperability | Check the re-using of existing vocabs for National Library of Sweden took 1.430511474609375e-06s
Believability | Calculation of trust value for National Library of Sweden took 1.0967254638671875e-05s
INFO | --- Analysis for NLS took 1766.032809495926s
Availability | SPARQL endpoint availability check for Japan Search took 1.087587833404541s
Availability | VoID file availability check for Japan Search took 0.0004994869232177734s
Extra | Recovery of all triples for Japan Search took 3.47627592086792s
Performance | Total latancy measurement for Japan Search took 2.74600887298584s
Amount of data | Number of triples check for Japan Search took 5.0972981452941895s
Interoperability | New terms check for Japan Search took 4.152709722518921s
Versatility | Languages check for Japan Search took 0.2617354393005371s
Interpretability | Number of blank nodes check for Japan Search took 12.96177339553833s
Interpretability | RDF structures check for Japan Search took 1.044368028640747s
Versatility | Serialization formats check for Japan Search took 0.8125040531158447s
Availability | RDF dump link check for Japan Search took 0.2954447269439697s
License | MR license check for Japan Search took 0.4636564254760742s
License | HR license check for Japan Search took 10.284225225448608s
Amount of data | Number of property check for Japan Search took 0.7324469089508057s
Understandability | Number of label check for Japan Search took 2.5257034301757812s
Understandability | URI regex check for Japan Search took 0.5397310256958008s
Understandability | Vocabs check for Japan Search took 0.2672414779663086s
Verifiability | Authors check for Japan Search took 0.7510232925415039s
Verifiability | Publishers check for Japan Search took 0.2635324001312256s
Performance | Throughput check for Japan Search took 10.574785947799683s
Amount of data | Check the number of entities for Japan Search took 7.176399230957031e-05s
Verifiability | Contribs. check for Japan Search took 0.26454830169677734s
Interlinking | sameAs chians check for Japan Search took 0.26508426666259766s
Interlinking | skos check for Japan Search took 0.2830526828765869s
Interlinking | skos check for Japan Search took 0.26671862602233887s
Timeliness | dataset update frequency check for Japan Search took 0.3262174129486084s
Currency | Creation date check for Japan Search took 0.5291650295257568s
Currency | Modification date check for Japan Search took 0.5307626724243164s
Rep.Conc. | URIs length for Japan Search took 13.666805028915405s
Interoperability | New vocabularies check for Japan Search took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for Japan Search took 0.26319146156311035s
Accuracy | Check Empty annotation labels for Japan Search took 2.197453260421753s
Accuracy | Check White space in annotation for Japan Search took 0.02910637855529785s
Accuracy | Check Datatype consistency for Japan Search took 0.027788639068603516s
Consistency | Disjoint class check for Japan Search took 0.7194945812225342s
Consistency | Check Misplaced properties for Japan Search took 10.771151304244995s
Consistency | Misplaced classes for Japan Search took 0.35094165802001953s
Consistency | Check Ontology hijacking for Japan Search took 2.4981954097747803s
Consistency | Check Invalid usage of undefined classes for Japan Search took 1.2460789680480957s
Consistency | Check Invalid usage of undefined properties for Japan Search took 13.146774291992188s
Conciseness | Check Extensional conciseness for Japan Search took 0.03468728065490723s
Conciseness | Check Intensional conciseness for Japan Search took 0.9457440376281738s
Security | Sign check for Japan Search took 0.26931023597717285s
Availability | Check URIs Dereferenciability for Japan Search took 11.964332103729248s
Completeness | Calculation of interlinking completeness for Japan Search took 0.20577764511108398s
Reputation | Calculation of the PageRank for Japan Search took 0.02094411849975586s
Interlinking | Calculation of Degree of Connection for Japan Search took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Japan Search took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Japan Search took 1.3113021850585938e-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 1.3589859008789062e-05s
INFO | --- Analysis for Japan-Search took 385.6602418422699s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection took 0.9835116863250732s
Availability | VoID file availability check for Rijksmuseum Collection took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection took 0.16422319412231445s
Reputation | Calculation of the PageRank for Rijksmuseum Collection took 0.020621299743652344s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection took 1.71661376953125e-05s
Believability | Calculation of trust value for Rijksmuseum Collection took 1.0728836059570312e-05s
INFO | --- Analysis for Rijksmuseum took 3.3621480464935303s
Availability | SPARQL endpoint availability check for Finnish Public Libraries took 0.5168728828430176s
Availability | VoID file availability check for Finnish Public Libraries took 0.0007236003875732422s
Extra | Recovery of all triples for Finnish Public Libraries took 14.568212270736694s
Performance | Total latancy measurement for Finnish Public Libraries took 1.5243659019470215s
Amount of data | Number of triples check for Finnish Public Libraries took 49.900280714035034s
Interoperability | New terms check for Finnish Public Libraries took 13.129353761672974s
Versatility | Languages check for Finnish Public Libraries took 60.272053241729736s
Interpretability | Number of blank nodes check for Finnish Public Libraries took 51.853554487228394s
Interpretability | RDF structures check for Finnish Public Libraries took 0.47561025619506836s
Versatility | Serialization formats check for Finnish Public Libraries took 0.24238801002502441s
Availability | RDF dump link check for Finnish Public Libraries took 0.2613358497619629s
License | MR license check for Finnish Public Libraries took 0.26886677742004395s
License | HR license check for Finnish Public Libraries took 34.05897331237793s
Amount of data | Number of property check for Finnish Public Libraries took 0.269672155380249s
Understandability | Number of label check for Finnish Public Libraries took 12.089866638183594s
Understandability | URI regex check for Finnish Public Libraries took 0.37644100189208984s
Understandability | Vocabs check for Finnish Public Libraries took 0.260317325592041s
Verifiability | Authors check for Finnish Public Libraries took 0.21994400024414062s
Verifiability | Publishers check for Finnish Public Libraries took 0.1074826717376709s
Performance | Throughput check for Finnish Public Libraries took 11.142058610916138s
Amount of data | Check the number of entities for Finnish Public Libraries took 6.866455078125e-05s
Verifiability | Contribs. check for Finnish Public Libraries took 0.10827803611755371s
Interlinking | sameAs chians check for Finnish Public Libraries took 0.4574451446533203s
Interlinking | skos check for Finnish Public Libraries took 0.12346363067626953s
Interlinking | skos check for Finnish Public Libraries took 0.43178462982177734s
Timeliness | dataset update frequency check for Finnish Public Libraries took 0.2663109302520752s
Currency | Creation date check for Finnish Public Libraries took 0.2378396987915039s
Currency | Modification date check for Finnish Public Libraries took 0.37798118591308594s
Rep.Conc. | URIs length for Finnish Public Libraries took 76.18528461456299s
Interoperability | New vocabularies check for Finnish Public Libraries took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Finnish Public Libraries took 0.431948184967041s
Accuracy | Check Functional Property for Finnish Public Libraries took 0.2608184814453125s
Accuracy | Check Inverse Functional Property for Finnish Public Libraries took 0.25901365280151367s
Accuracy | Check Empty annotation labels for Finnish Public Libraries took 8.017995595932007s
Accuracy | Check White space in annotation for Finnish Public Libraries took 2.1653494834899902s
Accuracy | Check Datatype consistency for Finnish Public Libraries took 4.437572479248047s
Consistency | Disjoint class check for Finnish Public Libraries took 0.38237881660461426s
Consistency | Check Misplaced properties for Finnish Public Libraries took 56.8810613155365s
Consistency | Check Ontology hijacking for Finnish Public Libraries took 13.939454555511475s
Consistency | Check Invalid usage of undefined classes for Finnish Public Libraries took 1.5372018814086914s
Consistency | Check Invalid usage of undefined properties for Finnish Public Libraries took 60.72514986991882s
Conciseness | Check Extensional conciseness for Finnish Public Libraries took 2.7315518856048584s
Security | Sign check for Finnish Public Libraries took 0.30874204635620117s
Availability | Check URIs Dereferenciability for Finnish Public Libraries took 0.7717416286468506s
Completeness | Calculation of interlinking completeness for Finnish Public Libraries took 131.20189213752747s
Reputation | Calculation of the PageRank for Finnish Public Libraries took 0.021259784698486328s
Interlinking | Calculation of Degree of Connection for Finnish Public Libraries took 2.288818359375e-05s
Interlinking | Calculation of Centrality for Finnish Public Libraries took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Finnish Public Libraries took 1.9550323486328125e-05s
Interoperability | Check the re-using of existing vocabs for Finnish Public Libraries took 2.1457672119140625e-06s
Believability | Calculation of trust value for Finnish Public Libraries took 6.198883056640625e-06s
INFO | --- Analysis for FI-Library took 882.2849009037018s
Availability | SPARQL endpoint availability check for Shanghai Library Open Data Platform took 3.8557722568511963s
Availability | VoID file availability check for Shanghai Library Open Data Platform took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for Shanghai Library Open Data Platform took 0.17338252067565918s
Reputation | Calculation of the PageRank for Shanghai Library Open Data Platform took 0.021177053451538086s
Interlinking | Calculation of Degree of Connection for Shanghai Library Open Data Platform took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Shanghai Library Open Data Platform took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Shanghai Library Open Data Platform took 1.4066696166992188e-05s
Believability | Calculation of trust value for Shanghai Library Open Data Platform took 1.2874603271484375e-05s
INFO | --- Analysis for Shanghai-Library-Open-Data-Platform took 7.924180746078491s
Availability | SPARQL endpoint availability check for National Library Netherlands took 1.3261950016021729s
Availability | VoID file availability check for National Library Netherlands took 0.0006866455078125s
Extra | Recovery of all triples for National Library Netherlands took 1.1194937229156494s
Performance | Total latancy measurement for National Library Netherlands took 0.7222211360931396s
Amount of data | Number of triples check for National Library Netherlands took 0.623265266418457s
Interoperability | New terms check for National Library Netherlands took 5.277468919754028s
Versatility | Languages check for National Library Netherlands took 58.13734793663025s
Interpretability | Number of blank nodes check for National Library Netherlands took 0.15928220748901367s
Interpretability | RDF structures check for National Library Netherlands took 0.364682674407959s
Versatility | Serialization formats check for National Library Netherlands took 0.15671133995056152s
Availability | RDF dump link check for National Library Netherlands took 0.15012073516845703s
License | MR license check for National Library Netherlands took 0.4156763553619385s
License | HR license check for National Library Netherlands took 58.13872313499451s
Amount of data | Number of property check for National Library Netherlands took 0.1622457504272461s
Understandability | Number of label check for National Library Netherlands took 12.354342699050903s
Understandability | URI regex check for National Library Netherlands took 0.2966897487640381s
Understandability | Vocabs check for National Library Netherlands took 0.154371976852417s
Verifiability | Authors check for National Library Netherlands took 0.1597437858581543s
Verifiability | Publishers check for National Library Netherlands took 0.15645146369934082s
Performance | Throughput check for National Library Netherlands took 10.886623620986938s
Amount of data | Check the number of entities for National Library Netherlands took 0.00010824203491210938s
Verifiability | Contribs. check for National Library Netherlands took 0.1542520523071289s
Interlinking | sameAs chians check for National Library Netherlands took 0.984421968460083s
Interlinking | skos check for National Library Netherlands took 0.19544219970703125s
Interlinking | skos check for National Library Netherlands took 0.1400284767150879s
Timeliness | dataset update frequency check for National Library Netherlands took 0.15344452857971191s
Currency | Creation date check for National Library Netherlands took 0.46282482147216797s
Currency | Modification date check for National Library Netherlands took 0.4913909435272217s
Rep.Conc. | URIs length for National Library Netherlands took 7.920305252075195s
Interoperability | New vocabularies check for National Library Netherlands took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for National Library Netherlands took 0.15124869346618652s
Accuracy | Check Empty annotation labels for National Library Netherlands took 0.5809111595153809s
Accuracy | Check White space in annotation for National Library Netherlands took 0.0267031192779541s
Accuracy | Check Datatype consistency for National Library Netherlands took 0.028354644775390625s
Consistency | Disjoint class check for National Library Netherlands took 0.3419673442840576s
Consistency | Check Misplaced properties for National Library Netherlands took 3.632734775543213s
Consistency | Check Ontology hijacking for National Library Netherlands took 1.8532683849334717s
Consistency | Check Invalid usage of undefined classes for National Library Netherlands took 1.281611680984497s
Consistency | Check Invalid usage of undefined properties for National Library Netherlands took 1.4213142395019531s
Conciseness | Check Extensional conciseness for National Library Netherlands took 0.03378939628601074s
Security | Sign check for National Library Netherlands took 0.16049838066101074s
Availability | Check URIs Dereferenciability for National Library Netherlands took 1603.9469816684723s
Completeness | Calculation of interlinking completeness for National Library Netherlands took 0.3809089660644531s
Reputation | Calculation of the PageRank for National Library Netherlands took 0.020786285400390625s
Interlinking | Calculation of Degree of Connection for National Library Netherlands took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for National Library Netherlands took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for National Library Netherlands took 1.8835067749023438e-05s
Interoperability | Check the re-using of existing vocabs for National Library Netherlands took 1.9073486328125e-06s
Believability | Calculation of trust value for National Library Netherlands took 1.2636184692382812e-05s
INFO | --- Analysis for National-Library-Netherlands took 1795.752149105072s
Availability | SPARQL endpoint availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.3559303283691406s
Availability | VoID file availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0007336139678955078s
Completeness | Calculation of interlinking completeness for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.15526866912841797s
Reputation | Calculation of the PageRank for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.02123570442199707s
Interlinking | Calculation of Degree of Connection for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 2.3365020751953125e-05s
Interlinking | Calculation of Centrality for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0010728836059570312s
Interlinking | Calculation of Clustering coefficient for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.4066696166992188e-05s
Believability | Calculation of trust value for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 7.3909759521484375e-06s
INFO | --- Analysis for Antique-Renaissance took 4.100873708724976s
Availability | SPARQL endpoint availability check for ARTSDATA.CA took 4.004911661148071s
Availability | VoID file availability check for ARTSDATA.CA took 0.0005433559417724609s
Completeness | Calculation of interlinking completeness for ARTSDATA.CA took 0.17052602767944336s
Reputation | Calculation of the PageRank for ARTSDATA.CA took 0.021753311157226562s
Interlinking | Calculation of Degree of Connection for ARTSDATA.CA took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for ARTSDATA.CA took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for ARTSDATA.CA took 1.2636184692382812e-05s
Believability | Calculation of trust value for ARTSDATA.CA took 1.1205673217773438e-05s
INFO | --- Analysis for ARTSDATA-CA took 8.573288917541504s
Availability | SPARQL endpoint availability check for Architecture of Knowledge took 0.17008447647094727s
Availability | VoID file availability check for Architecture of Knowledge took 0.0005533695220947266s
Completeness | Calculation of interlinking completeness for Architecture of Knowledge took 0.17204785346984863s
Reputation | Calculation of the PageRank for Architecture of Knowledge took 0.02081465721130371s
Interlinking | Calculation of Degree of Connection for Architecture of Knowledge took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Architecture of Knowledge took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Architecture of Knowledge took 1.239776611328125e-05s
Believability | Calculation of trust value for Architecture of Knowledge took 1.2874603271484375e-05s
INFO | --- Analysis for ArCo took 2.252458333969116s
Availability | SPARQL endpoint availability check for ConfermentSampo took 0.3260810375213623s
Availability | VoID file availability check for ConfermentSampo took 0.0005025863647460938s
Extra | Recovery of all triples for ConfermentSampo took 102.49543380737305s
Performance | Total latancy measurement for ConfermentSampo took 0.7876744270324707s
Amount of data | Number of triples check for ConfermentSampo took 30.555510997772217s
Interoperability | New terms check for ConfermentSampo took 33.912362813949585s
Versatility | Languages check for ConfermentSampo took 30.5459406375885s
Interpretability | Number of blank nodes check for ConfermentSampo took 7.073473691940308s
Security | Check HTTPS for ConfermentSampo took 0.3790767192840576s
Interpretability | RDF structures check for ConfermentSampo took 0.19093918800354004s
Versatility | Serialization formats check for ConfermentSampo took 0.20051336288452148s
Availability | RDF dump link check for ConfermentSampo took 3.022847890853882s
License | MR license check for ConfermentSampo took 0.18515753746032715s
License | HR license check for ConfermentSampo took 0.25230860710144043s
Amount of data | Number of property check for ConfermentSampo took 0.19194817543029785s
Understandability | Number of label check for ConfermentSampo took 10.068725109100342s
Understandability | URI regex check for ConfermentSampo took 0.34293270111083984s
Understandability | Vocabs check for ConfermentSampo took 0.1632692813873291s
Verifiability | Authors check for ConfermentSampo took 0.18296265602111816s
Verifiability | Publishers check for ConfermentSampo took 0.18199753761291504s
Performance | Throughput check for ConfermentSampo took 10.597413301467896s
Amount of data | Check the number of entities for ConfermentSampo took 0.000274658203125s
Verifiability | Contribs. check for ConfermentSampo took 0.1606311798095703s
Interlinking | sameAs chians check for ConfermentSampo took 0.7040975093841553s
Interlinking | skos check for ConfermentSampo took 0.17191219329833984s
Interlinking | skos check for ConfermentSampo took 0.14928150177001953s
Timeliness | dataset update frequency check for ConfermentSampo took 0.15832805633544922s
Currency | Creation date check for ConfermentSampo took 0.3490283489227295s
Currency | Modification date check for ConfermentSampo took 0.3429083824157715s
Rep.Conc. | URIs length for ConfermentSampo took 30.46032953262329s
Interoperability | New vocabularies check for ConfermentSampo took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for ConfermentSampo took 0.1877424716949463s
Accuracy | Check Functional Property for ConfermentSampo took 0.18296527862548828s
Accuracy | Check Inverse Functional Property for ConfermentSampo took 0.1589033603668213s
Accuracy | Check Empty annotation labels for ConfermentSampo took 14.912862300872803s
Accuracy | Check White space in annotation for ConfermentSampo took 2.99404239654541s
Consistency | Disjoint class check for ConfermentSampo took 0.15975260734558105s
Consistency | Check Misplaced properties for ConfermentSampo took 6.832547187805176s
Consistency | Check Ontology hijacking for ConfermentSampo took 15.42951250076294s
Consistency | Check Invalid usage of undefined properties for ConfermentSampo took 1.5663652420043945s
Conciseness | Check Extensional conciseness for ConfermentSampo took 0.00014090538024902344s
Conciseness | Check Intensional conciseness for ConfermentSampo took 0.3224802017211914s
Security | Sign check for ConfermentSampo took 0.1557002067565918s
Availability | Check URIs Dereferenciability for ConfermentSampo took 1323.4104838371277s
Completeness | Calculation of interlinking completeness for ConfermentSampo took 0.24021291732788086s
Reputation | Calculation of the PageRank for ConfermentSampo took 0.02194976806640625s
Interlinking | Calculation of Degree of Connection for ConfermentSampo took 2.4557113647460938e-05s
Interlinking | Calculation of Centrality for ConfermentSampo took 0.0010464191436767578s
Interlinking | Calculation of Clustering coefficient for ConfermentSampo took 2.1457672119140625e-05s
Interoperability | Check the re-using of existing vocabs for ConfermentSampo took 4.5299530029296875e-06s
Believability | Calculation of trust value for ConfermentSampo took 1.4543533325195312e-05s
INFO | --- Analysis for ConfermentSampo took 1739.4360494613647s
Availability | SPARQL endpoint availability check for Museum Finland took 0.2636129856109619s
Availability | VoID file availability check for Museum Finland took 0.00047779083251953125s
Extra | Recovery of all triples for Museum Finland took 5.914856195449829s
Performance | Total latancy measurement for Museum Finland took 0.7741599082946777s
Amount of data | Number of triples check for Museum Finland took 0.3191959857940674s
Interoperability | New terms check for Museum Finland took 1.705596685409546s
Versatility | Languages check for Museum Finland took 0.6359500885009766s
Interpretability | Number of blank nodes check for Museum Finland took 0.29763317108154297s
Security | Check HTTPS for Museum Finland took 0.2318739891052246s
Interpretability | RDF structures check for Museum Finland took 0.3606071472167969s
Versatility | Serialization formats check for Museum Finland took 0.19049835205078125s
Availability | RDF dump link check for Museum Finland took 0.15213966369628906s
License | MR license check for Museum Finland took 0.1839005947113037s
License | HR license check for Museum Finland took 0.4045875072479248s
Amount of data | Number of property check for Museum Finland took 0.17721343040466309s
Understandability | Number of label check for Museum Finland took 0.46282410621643066s
Understandability | URI regex check for Museum Finland took 0.3034818172454834s
Understandability | Vocabs check for Museum Finland took 0.1502218246459961s
Verifiability | Authors check for Museum Finland took 0.1725752353668213s
Verifiability | Publishers check for Museum Finland took 0.15109682083129883s
Performance | Throughput check for Museum Finland took 10.52243161201477s
Amount of data | Check the number of entities for Museum Finland took 7.843971252441406e-05s
Verifiability | Contribs. check for Museum Finland took 0.15201163291931152s
Interlinking | sameAs chians check for Museum Finland took 0.15292859077453613s
Interlinking | skos check for Museum Finland took 0.1533496379852295s
Interlinking | skos check for Museum Finland took 0.1491837501525879s
Timeliness | dataset update frequency check for Museum Finland took 0.15206050872802734s
Currency | Creation date check for Museum Finland took 0.327800989151001s
Currency | Modification date check for Museum Finland took 0.3489534854888916s
Rep.Conc. | URIs length for Museum Finland took 3.3744747638702393s
Interoperability | New vocabularies check for Museum Finland took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Museum Finland took 0.17542552947998047s
Accuracy | Check Functional Property for Museum Finland took 0.1654052734375s
Accuracy | Check Inverse Functional Property for Museum Finland took 0.15101957321166992s
Accuracy | Check Empty annotation labels for Museum Finland took 0.9650003910064697s
Accuracy | Check White space in annotation for Museum Finland took 0.060697078704833984s
Accuracy | Check Datatype consistency for Museum Finland took 0.941469669342041s
Consistency | Disjoint class check for Museum Finland took 0.1506640911102295s
Consistency | Check Misplaced properties for Museum Finland took 0.5992848873138428s
Consistency | Check Ontology hijacking for Museum Finland took 2.001884937286377s
Consistency | Check Invalid usage of undefined classes for Museum Finland took 1.2669947147369385s
Consistency | Check Invalid usage of undefined properties for Museum Finland took 1.4157450199127197s
Conciseness | Check Extensional conciseness for Museum Finland took 0.6323118209838867s
Conciseness | Check Intensional conciseness for Museum Finland took 0.5530693531036377s
Security | Sign check for Museum Finland took 0.15129971504211426s
Availability | Check URIs Dereferenciability for Museum Finland took 8.00064730644226s
Completeness | Calculation of interlinking completeness for Museum Finland took 0.1576380729675293s
Reputation | Calculation of the PageRank for Museum Finland took 0.020465850830078125s
Interlinking | Calculation of Degree of Connection for Museum Finland took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Museum Finland took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for Museum Finland took 1.239776611328125e-05s
Interoperability | Check the re-using of existing vocabs for Museum Finland took 1.6689300537109375e-06s
Believability | Calculation of trust value for Museum Finland took 1.0728836059570312e-05s
INFO | --- Analysis for FI-Museum took 60.82924723625183s
Availability | SPARQL endpoint availability check for Mapping Manuscript Migrations took 0.17975068092346191s
Availability | VoID file availability check for Mapping Manuscript Migrations took 0.0005788803100585938s
Extra | Recovery of all triples for Mapping Manuscript Migrations took 16.18909001350403s
Performance | Total latancy measurement for Mapping Manuscript Migrations took 0.7748994827270508s
Amount of data | Number of triples check for Mapping Manuscript Migrations took 29.88139033317566s
Interoperability | New terms check for Mapping Manuscript Migrations took 55.88336753845215s
Versatility | Languages check for Mapping Manuscript Migrations took 74.29573106765747s
Interpretability | Number of blank nodes check for Mapping Manuscript Migrations took 28.79847288131714s
Security | Check HTTPS for Mapping Manuscript Migrations took 0.38568806648254395s
Interpretability | RDF structures check for Mapping Manuscript Migrations took 0.1529085636138916s
Versatility | Serialization formats check for Mapping Manuscript Migrations took 0.15284276008605957s
Availability | RDF dump link check for Mapping Manuscript Migrations took 0.15148115158081055s
License | MR license check for Mapping Manuscript Migrations took 0.1759345531463623s
License | HR license check for Mapping Manuscript Migrations took 1.690194845199585s
Amount of data | Number of property check for Mapping Manuscript Migrations took 0.15166163444519043s
Understandability | Number of label check for Mapping Manuscript Migrations took 19.176459074020386s
Understandability | URI regex check for Mapping Manuscript Migrations took 0.3332028388977051s
Understandability | Vocabs check for Mapping Manuscript Migrations took 0.15172529220581055s
Verifiability | Authors check for Mapping Manuscript Migrations took 0.1760549545288086s
Verifiability | Publishers check for Mapping Manuscript Migrations took 0.17532944679260254s
Performance | Throughput check for Mapping Manuscript Migrations took 10.457929849624634s
Amount of data | Check the number of entities for Mapping Manuscript Migrations took 0.9983763694763184s
Verifiability | Contribs. check for Mapping Manuscript Migrations took 0.17572665214538574s
Interlinking | sameAs chians check for Mapping Manuscript Migrations took 0.5543522834777832s
Interlinking | skos check for Mapping Manuscript Migrations took 0.1527390480041504s
Interlinking | skos check for Mapping Manuscript Migrations took 0.14822745323181152s
Timeliness | dataset update frequency check for Mapping Manuscript Migrations took 0.15666651725769043s
Currency | Creation date check for Mapping Manuscript Migrations took 0.32782602310180664s
Currency | Modification date check for Mapping Manuscript Migrations took 0.18545246124267578s
Rep.Conc. | URIs length for Mapping Manuscript Migrations took 47.572471380233765s
Interoperability | New vocabularies check for Mapping Manuscript Migrations took 7.152557373046875e-06s
Consistency | Deprecated classes/propertiers check for Mapping Manuscript Migrations took 0.17514920234680176s
Accuracy | Check Functional Property for Mapping Manuscript Migrations took 0.1866765022277832s
Accuracy | Check Inverse Functional Property for Mapping Manuscript Migrations took 0.15164709091186523s
Accuracy | Check Empty annotation labels for Mapping Manuscript Migrations took 10.239594459533691s
Accuracy | Check White space in annotation for Mapping Manuscript Migrations took 2.424649715423584s
Accuracy | Check Datatype consistency for Mapping Manuscript Migrations took 5.70188045501709s
Consistency | Disjoint class check for Mapping Manuscript Migrations took 0.19433856010437012s
Consistency | Check Misplaced properties for Mapping Manuscript Migrations took 22.763667345046997s
Consistency | Check Ontology hijacking for Mapping Manuscript Migrations took 16.1141517162323s
Consistency | Check Invalid usage of undefined classes for Mapping Manuscript Migrations took 1.5687434673309326s
Consistency | Check Invalid usage of undefined properties for Mapping Manuscript Migrations took 1.5593984127044678s
Conciseness | Check Extensional conciseness for Mapping Manuscript Migrations took 2.8003602027893066s
Conciseness | Check Intensional conciseness for Mapping Manuscript Migrations took 0.17752742767333984s
Security | Sign check for Mapping Manuscript Migrations took 0.16084766387939453s
Availability | Check URIs Dereferenciability for Mapping Manuscript Migrations took 1553.290777683258s
Completeness | Calculation of interlinking completeness for Mapping Manuscript Migrations took 0.44570112228393555s
Reputation | Calculation of the PageRank for Mapping Manuscript Migrations took 0.022942781448364258s
Interlinking | Calculation of Degree of Connection for Mapping Manuscript Migrations took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Mapping Manuscript Migrations took 0.0006842613220214844s
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 1.9073486328125e-06s
Believability | Calculation of trust value for Mapping Manuscript Migrations took 1.239776611328125e-05s
INFO | --- Analysis for MMM took 2267.762235879898s
Availability | SPARQL endpoint availability check for Semantic Kalevala took 0.21710515022277832s
Availability | VoID file availability check for Semantic Kalevala took 0.0004734992980957031s
Extra | Recovery of all triples for Semantic Kalevala took 9.901520252227783s
Performance | Total latancy measurement for Semantic Kalevala took 0.7657620906829834s
Amount of data | Number of triples check for Semantic Kalevala took 0.39661169052124023s
Interoperability | New terms check for Semantic Kalevala took 3.201937198638916s
Versatility | Languages check for Semantic Kalevala took 0.96097731590271s
Interpretability | Number of blank nodes check for Semantic Kalevala took 0.44959211349487305s
Security | Check HTTPS for Semantic Kalevala took 0.37900519371032715s
Interpretability | RDF structures check for Semantic Kalevala took 0.26712489128112793s
Versatility | Serialization formats check for Semantic Kalevala took 0.1822659969329834s
Availability | RDF dump link check for Semantic Kalevala took 0.15348505973815918s
License | MR license check for Semantic Kalevala took 0.19762206077575684s
License | HR license check for Semantic Kalevala took 1.1862733364105225s
Amount of data | Number of property check for Semantic Kalevala took 0.1753556728363037s
Understandability | Number of label check for Semantic Kalevala took 1.510122537612915s
Understandability | URI regex check for Semantic Kalevala took 0.32529783248901367s
Understandability | Vocabs check for Semantic Kalevala took 0.16107583045959473s
Verifiability | Authors check for Semantic Kalevala took 0.16312241554260254s
Verifiability | Publishers check for Semantic Kalevala took 0.1633152961730957s
Performance | Throughput check for Semantic Kalevala took 10.509977102279663s
Amount of data | Check the number of entities for Semantic Kalevala took 8.630752563476562e-05s
Verifiability | Contribs. check for Semantic Kalevala took 0.16409945487976074s
Interlinking | sameAs chians check for Semantic Kalevala took 0.18015003204345703s
Interlinking | skos check for Semantic Kalevala took 0.2712128162384033s
Interlinking | skos check for Semantic Kalevala took 0.14868521690368652s
Timeliness | dataset update frequency check for Semantic Kalevala took 0.17330312728881836s
Currency | Creation date check for Semantic Kalevala took 0.3309760093688965s
Currency | Modification date check for Semantic Kalevala took 0.32715916633605957s
Rep.Conc. | URIs length for Semantic Kalevala took 4.664480686187744s
Interoperability | New vocabularies check for Semantic Kalevala took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for Semantic Kalevala took 0.1948988437652588s
Accuracy | Check Functional Property for Semantic Kalevala took 0.17403197288513184s
Accuracy | Check Inverse Functional Property for Semantic Kalevala took 0.15139150619506836s
Accuracy | Check Empty annotation labels for Semantic Kalevala took 1.7871425151824951s
Accuracy | Check White space in annotation for Semantic Kalevala took 0.2921907901763916s
Accuracy | Check Datatype consistency for Semantic Kalevala took 1.3782076835632324s
Consistency | Disjoint class check for Semantic Kalevala took 0.15201377868652344s
Consistency | Check Misplaced properties for Semantic Kalevala took 0.7486491203308105s
Consistency | Check Ontology hijacking for Semantic Kalevala took 2.226332187652588s
Consistency | Check Invalid usage of undefined classes for Semantic Kalevala took 1.3570010662078857s
Consistency | Check Invalid usage of undefined properties for Semantic Kalevala took 1.524644374847412s
Conciseness | Check Extensional conciseness for Semantic Kalevala took 0.8778033256530762s
Conciseness | Check Intensional conciseness for Semantic Kalevala took 0.22694039344787598s
Security | Sign check for Semantic Kalevala took 0.15265321731567383s
Availability | Check URIs Dereferenciability for Semantic Kalevala took 2957.7967100143433s
Completeness | Calculation of interlinking completeness for Semantic Kalevala took 0.26482510566711426s
Reputation | Calculation of the PageRank for Semantic Kalevala took 0.49704551696777344s
Interlinking | Calculation of Degree of Connection for Semantic Kalevala took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Semantic Kalevala took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Semantic Kalevala took 1.33514404296875e-05s
Interoperability | Check the re-using of existing vocabs for Semantic Kalevala took 1.9073486328125e-06s
Believability | Calculation of trust value for Semantic Kalevala took 1.1205673217773438e-05s
INFO | --- Analysis for Semantic-Kalevala took 3022.1717891693115s
Availability | SPARQL endpoint availability check for Smithsonian American Art Museum took 0.870171308517456s
Availability | VoID file availability check for Smithsonian American Art Museum took 0.0006747245788574219s
Extra | Recovery of all triples for Smithsonian American Art Museum took 270.5780358314514s
Performance | Total latancy measurement for Smithsonian American Art Museum took 2.8993046283721924s
Amount of data | Number of triples check for Smithsonian American Art Museum took 0.5626490116119385s
Interoperability | New terms check for Smithsonian American Art Museum took 3.1769025325775146s
Versatility | Languages check for Smithsonian American Art Museum took 25.769522428512573s
Interpretability | Number of blank nodes check for Smithsonian American Art Museum took 0.5647201538085938s
Security | Check HTTPS for Smithsonian American Art Museum took 0.35422611236572266s
Interpretability | RDF structures check for Smithsonian American Art Museum took 0.6632483005523682s
Versatility | Serialization formats check for Smithsonian American Art Museum took 0.6335229873657227s
Availability | RDF dump link check for Smithsonian American Art Museum took 0.5706229209899902s
License | MR license check for Smithsonian American Art Museum took 0.6024510860443115s
License | HR license check for Smithsonian American Art Museum took 17.03494167327881s
Amount of data | Number of property check for Smithsonian American Art Museum took 0.5653584003448486s
Understandability | Number of label check for Smithsonian American Art Museum took 0.5646369457244873s
Understandability | URI regex check for Smithsonian American Art Museum took 1.1772334575653076s
Understandability | Vocabs check for Smithsonian American Art Museum took 0.5707876682281494s
Verifiability | Authors check for Smithsonian American Art Museum took 0.5749640464782715s
Verifiability | Publishers check for Smithsonian American Art Museum took 0.6061651706695557s
Performance | Throughput check for Smithsonian American Art Museum took 11.433372974395752s
Amount of data | Check the number of entities for Smithsonian American Art Museum took 6.937980651855469e-05s
Verifiability | Contribs. check for Smithsonian American Art Museum took 0.5723316669464111s
Interlinking | sameAs chians check for Smithsonian American Art Museum took 0.564258337020874s
Interlinking | skos check for Smithsonian American Art Museum took 0.5727071762084961s
Interlinking | skos check for Smithsonian American Art Museum took 0.5669167041778564s
Timeliness | dataset update frequency check for Smithsonian American Art Museum took 0.5745646953582764s
Currency | Creation date check for Smithsonian American Art Museum took 1.243833303451538s
Currency | Modification date check for Smithsonian American Art Museum took 1.1829357147216797s
Rep.Conc. | URIs length for Smithsonian American Art Museum took 103.36749625205994s
Interoperability | New vocabularies check for Smithsonian American Art Museum took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Smithsonian American Art Museum took 0.571765661239624s
Accuracy | Check Empty annotation labels for Smithsonian American Art Museum took 18.93617343902588s
Accuracy | Check White space in annotation for Smithsonian American Art Museum took 0.4961583614349365s
Accuracy | Check Datatype consistency for Smithsonian American Art Museum took 4.154415845870972s
Consistency | Disjoint class check for Smithsonian American Art Museum took 0.5755374431610107s
Consistency | Check Misplaced properties for Smithsonian American Art Museum took 5.508393049240112s
Consistency | Check Ontology hijacking for Smithsonian American Art Museum took 94.27469420433044s
Consistency | Check Invalid usage of undefined classes for Smithsonian American Art Museum took 1.5577940940856934s
Consistency | Check Invalid usage of undefined properties for Smithsonian American Art Museum took 4.764739274978638s
Conciseness | Check Extensional conciseness for Smithsonian American Art Museum took 2.8268415927886963s
Conciseness | Check Intensional conciseness for Smithsonian American Art Museum took 0.6154510974884033s
Security | Sign check for Smithsonian American Art Museum took 0.5685462951660156s
Availability | Check URIs Dereferenciability for Smithsonian American Art Museum took 6.135002136230469s
Completeness | Calculation of interlinking completeness for Smithsonian American Art Museum took 0.43645787239074707s
Reputation | Calculation of the PageRank for Smithsonian American Art Museum took 0.02035355567932129s
Interlinking | Calculation of Degree of Connection for Smithsonian American Art Museum took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Smithsonian American Art Museum took 0.0006794929504394531s
Interlinking | Calculation of Clustering coefficient for Smithsonian American Art Museum took 1.2874603271484375e-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 1.2636184692382812e-05s
INFO | --- Analysis for Smithsonian took 678.8982839584351s
Availability | SPARQL endpoint availability check for Zeri Photo Archive took 0.5825643539428711s
Availability | VoID file availability check for Zeri Photo Archive took 0.0006716251373291016s
Extra | Recovery of all triples for Zeri Photo Archive took 41.00071907043457s
Performance | Total latancy measurement for Zeri Photo Archive took 0.23242688179016113s
Amount of data | Number of triples check for Zeri Photo Archive took 60.067060708999634s
Interoperability | New terms check for Zeri Photo Archive took 6.407040596008301s
Versatility | Languages check for Zeri Photo Archive took 60.0933563709259s
Interpretability | Number of blank nodes check for Zeri Photo Archive took 61.24322700500488s
Interpretability | RDF structures check for Zeri Photo Archive took 1.1657662391662598s
Versatility | Serialization formats check for Zeri Photo Archive took 0.03055739402770996s
Availability | RDF dump link check for Zeri Photo Archive took 0.03212285041809082s
License | MR license check for Zeri Photo Archive took 0.030304908752441406s
License | HR license check for Zeri Photo Archive took 0.03007030487060547s
Amount of data | Number of property check for Zeri Photo Archive took 0.02971029281616211s
Understandability | Number of label check for Zeri Photo Archive took 0.03173947334289551s
Understandability | URI regex check for Zeri Photo Archive took 0.059557199478149414s
Understandability | Vocabs check for Zeri Photo Archive took 0.029568195343017578s
Verifiability | Authors check for Zeri Photo Archive took 0.029521703720092773s
Verifiability | Publishers check for Zeri Photo Archive took 0.028865814208984375s
Amount of data | Check the number of entities for Zeri Photo Archive took 9.655952453613281e-05s
Verifiability | Contribs. check for Zeri Photo Archive took 0.03180336952209473s
Interlinking | sameAs chians check for Zeri Photo Archive took 0.029000282287597656s
Interlinking | skos check for Zeri Photo Archive took 0.03210735321044922s
Interlinking | skos check for Zeri Photo Archive took 0.02888178825378418s
Timeliness | dataset update frequency check for Zeri Photo Archive took 0.03603553771972656s
Currency | Creation date check for Zeri Photo Archive took 0.060556650161743164s
Currency | Modification date check for Zeri Photo Archive took 0.058356523513793945s
Rep.Conc. | URIs length for Zeri Photo Archive took 3.4607737064361572s
Interoperability | New vocabularies check for Zeri Photo Archive took 2.384185791015625e-07s
Consistency | Deprecated classes/propertiers check for Zeri Photo Archive took 0.028968095779418945s
Accuracy | Check Datatype consistency for Zeri Photo Archive took 4.568685531616211s
Consistency | Disjoint class check for Zeri Photo Archive took 0.03419947624206543s
Consistency | Check Ontology hijacking for Zeri Photo Archive took 0.028808116912841797s
Consistency | Check Invalid usage of undefined properties for Zeri Photo Archive took 1.2996852397918701s
Conciseness | Check Extensional conciseness for Zeri Photo Archive took 2.937638759613037s
Security | Sign check for Zeri Photo Archive took 0.02897500991821289s
Availability | Check URIs Dereferenciability for Zeri Photo Archive took 21.66086435317993s
Completeness | Calculation of interlinking completeness for Zeri Photo Archive took 0.24338078498840332s
Reputation | Calculation of the PageRank for Zeri Photo Archive took 0.0206148624420166s
Interlinking | Calculation of Degree of Connection for Zeri Photo Archive took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Zeri Photo Archive took 0.0006771087646484375s
Interlinking | Calculation of Clustering coefficient for Zeri Photo Archive took 1.7642974853515625e-05s
Interoperability | Check the re-using of existing vocabs for Zeri Photo Archive took 7.152557373046875e-07s
Believability | Calculation of trust value for Zeri Photo Archive took 7.152557373046875e-06s
INFO | --- Analysis for Zeri-Photo-Archive took 657.4367723464966s
Availability | SPARQL endpoint availability check for Archives Hub took 21.24665093421936s
Availability | VoID file availability check for Archives Hub took 0.00030612945556640625s
Completeness | Calculation of interlinking completeness for Archives Hub took 131.05998063087463s
Reputation | Calculation of the PageRank for Archives Hub took 0.022227764129638672s
Interlinking | Calculation of Degree of Connection for Archives Hub took 2.5510787963867188e-05s
Interlinking | Calculation of Centrality for Archives Hub took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Archives Hub took 2.002716064453125e-05s
Believability | Calculation of trust value for Archives Hub took 1.3589859008789062e-05s
INFO | --- Analysis for Archives-Hub took 574.5874173641205s
Availability | SPARQL endpoint availability check for Yale centre of British Art took 1.5780487060546875s
Availability | VoID file availability check for Yale centre of British Art took 0.0005276203155517578s
Completeness | Calculation of interlinking completeness for Yale centre of British Art took 0.15760087966918945s
Reputation | Calculation of the PageRank for Yale centre of British Art took 0.020508289337158203s
Interlinking | Calculation of Degree of Connection for Yale centre of British Art took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Yale centre of British Art took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Yale centre of British Art took 1.7881393432617188e-05s
Believability | Calculation of trust value for Yale centre of British Art took 9.059906005859375e-06s
INFO | --- Analysis for Yale took 3.32292103767395s
Availability | SPARQL endpoint availability check for Alexandria Digital Library Gazetteer took 261.2217769622803s
Availability | VoID file availability check for Alexandria Digital Library Gazetteer took 0.0005331039428710938s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library Gazetteer took 0.16377520561218262s
Reputation | Calculation of the PageRank for Alexandria Digital Library Gazetteer took 0.020562171936035156s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library Gazetteer took 2.384185791015625e-05s
Interlinking | Calculation of Centrality for Alexandria Digital Library Gazetteer took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library Gazetteer took 1.6927719116210938e-05s
Believability | Calculation of trust value for Alexandria Digital Library Gazetteer took 1.1920928955078125e-05s
INFO | --- Analysis for ADL took 665.0027761459351s
Availability | SPARQL endpoint availability check for MusicKG took 0.7405943870544434s
Availability | VoID file availability check for MusicKG took 0.0006642341613769531s
Completeness | Calculation of interlinking completeness for MusicKG took 0.16066431999206543s
Reputation | Calculation of the PageRank for MusicKG took 0.022327661514282227s
Interlinking | Calculation of Degree of Connection for MusicKG took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for MusicKG took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for MusicKG took 1.239776611328125e-05s
Believability | Calculation of trust value for MusicKG took 1.2874603271484375e-05s
INFO | --- Analysis for MusicKG took 3.0150578022003174s
Availability | SPARQL endpoint availability check for CIDOC-CRM took 0.765617847442627s
Availability | VoID file availability check for CIDOC-CRM took 0.0006341934204101562s
Completeness | Calculation of interlinking completeness for CIDOC-CRM took 0.1631333827972412s
Reputation | Calculation of the PageRank for CIDOC-CRM took 0.023772239685058594s
Interlinking | Calculation of Degree of Connection for CIDOC-CRM took 2.3365020751953125e-05s
Interlinking | Calculation of Centrality for CIDOC-CRM took 0.0010554790496826172s
Interlinking | Calculation of Clustering coefficient for CIDOC-CRM took 1.33514404296875e-05s
Believability | Calculation of trust value for CIDOC-CRM took 1.2159347534179688e-05s
INFO | --- Analysis for CIDOC-CRM took 2.7592124938964844s
Availability | SPARQL endpoint availability check for Mondis took 0.28162097930908203s
Availability | VoID file availability check for Mondis took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for Mondis took 0.16344118118286133s
Reputation | Calculation of the PageRank for Mondis took 0.020632505416870117s
Interlinking | Calculation of Degree of Connection for Mondis took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Mondis took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Mondis took 1.2636184692382812e-05s
Believability | Calculation of trust value for Mondis took 1.0728836059570312e-05s
INFO | --- Analysis for Mondis took 2.02714467048645s
Availability | SPARQL endpoint availability check for DigitalNZ took 3.544015407562256s
Availability | VoID file availability check for DigitalNZ took 0.0003514289855957031s
Completeness | Calculation of interlinking completeness for DigitalNZ took 0.15575408935546875s
Reputation | Calculation of the PageRank for DigitalNZ took 0.020412206649780273s
Interlinking | Calculation of Degree of Connection for DigitalNZ took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for DigitalNZ took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for DigitalNZ took 1.1682510375976562e-05s
Believability | Calculation of trust value for DigitalNZ took 1.1682510375976562e-05s
INFO | --- Analysis for DigitalNZ took 6.1368842124938965s
Availability | SPARQL endpoint availability check for Fondazione Zeri took 0.15536952018737793s
Availability | VoID file availability check for Fondazione Zeri took 0.0005424022674560547s
Completeness | Calculation of interlinking completeness for Fondazione Zeri took 0.15937447547912598s
Reputation | Calculation of the PageRank for Fondazione Zeri took 0.020487546920776367s
Interlinking | Calculation of Degree of Connection for Fondazione Zeri took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Fondazione Zeri took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Fondazione Zeri took 1.239776611328125e-05s
Believability | Calculation of trust value for Fondazione Zeri took 9.775161743164062e-06s
INFO | --- Analysis for Fondazione-Zeri took 2.53208589553833s
Availability | SPARQL endpoint availability check for Digital Public Library of America took 0.11810803413391113s
Availability | VoID file availability check for Digital Public Library of America took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for Digital Public Library of America took 0.16838788986206055s
Reputation | Calculation of the PageRank for Digital Public Library of America took 0.022332191467285156s
Interlinking | Calculation of Degree of Connection for Digital Public Library of America took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Digital Public Library of America took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Digital Public Library of America took 1.1682510375976562e-05s
Believability | Calculation of trust value for Digital Public Library of America took 1.0013580322265625e-05s
INFO | --- Analysis for Library-of-America took 2.4005253314971924s
Availability | SPARQL endpoint availability check for Auckland Museum took 1.5272629261016846s
Availability | VoID file availability check for Auckland Museum took 0.0006158351898193359s
Completeness | Calculation of interlinking completeness for Auckland Museum took 0.15728449821472168s
Reputation | Calculation of the PageRank for Auckland Museum took 0.02031230926513672s
Interlinking | Calculation of Degree of Connection for Auckland Museum took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Auckland Museum took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Auckland Museum took 1.2636184692382812e-05s
Believability | Calculation of trust value for Auckland Museum took 1.1920928955078125e-05s
INFO | --- Analysis for Auckland-Museum took 4.82147741317749s
Availability | SPARQL endpoint availability check for National Library of Spain took 1.849494218826294s
Availability | VoID file availability check for National Library of Spain took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for National Library of Spain took 0.1535494327545166s
Reputation | Calculation of the PageRank for National Library of Spain took 0.02070164680480957s
Interlinking | Calculation of Degree of Connection for National Library of Spain took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for National Library of Spain took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for National Library of Spain took 1.2159347534179688e-05s
Believability | Calculation of trust value for National Library of Spain took 1.1444091796875e-05s
INFO | --- Analysis for BNE took 3.5893051624298096s
Availability | SPARQL endpoint availability check for National Library of Korea took 1.628779649734497s
Availability | VoID file availability check for National Library of Korea took 0.0005314350128173828s
Completeness | Calculation of interlinking completeness for National Library of Korea took 0.15373897552490234s
Reputation | Calculation of the PageRank for National Library of Korea took 0.020738840103149414s
Interlinking | Calculation of Degree of Connection for National Library of Korea took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for National Library of Korea took 0.0009760856628417969s
Interlinking | Calculation of Clustering coefficient for National Library of Korea took 1.3589859008789062e-05s
Believability | Calculation of trust value for National Library of Korea took 1.621246337890625e-05s
INFO | --- Analysis for Korea-Library took 3.381103515625s
Availability | SPARQL endpoint availability check for The State Russian Museum took 1.2127420902252197s
Availability | VoID file availability check for The State Russian Museum took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for The State Russian Museum took 0.15208673477172852s
Reputation | Calculation of the PageRank for The State Russian Museum took 0.021163463592529297s
Interlinking | Calculation of Degree of Connection for The State Russian Museum took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for The State Russian Museum took 0.0008866786956787109s
Interlinking | Calculation of Clustering coefficient for The State Russian Museum took 1.3828277587890625e-05s
Believability | Calculation of trust value for The State Russian Museum took 6.9141387939453125e-06s
INFO | --- Analysis for Russian-Museum took 2.9465157985687256s
Availability | SPARQL endpoint availability check for National Library of Scotland took 1.7772924900054932s
Availability | VoID file availability check for National Library of Scotland took 0.0006110668182373047s
Completeness | Calculation of interlinking completeness for National Library of Scotland took 0.16477274894714355s
Reputation | Calculation of the PageRank for National Library of Scotland took 0.02038264274597168s
Interlinking | Calculation of Degree of Connection for National Library of Scotland took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for National Library of Scotland took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for National Library of Scotland took 1.2874603271484375e-05s
Believability | Calculation of trust value for National Library of Scotland took 1.2636184692382812e-05s
INFO | --- Analysis for National-Library-of-Scotland took 5.848072052001953s
Availability | SPARQL endpoint availability check for Epigraphic Database Heidelberg took 0.29315853118896484s
Availability | VoID file availability check for Epigraphic Database Heidelberg took 0.0006227493286132812s
Completeness | Calculation of interlinking completeness for Epigraphic Database Heidelberg took 0.15270185470581055s
Reputation | Calculation of the PageRank for Epigraphic Database Heidelberg took 0.02104473114013672s
Interlinking | Calculation of Degree of Connection for Epigraphic Database Heidelberg took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Epigraphic Database Heidelberg took 0.0006890296936035156s
Interlinking | Calculation of Clustering coefficient for Epigraphic Database Heidelberg took 1.239776611328125e-05s
Believability | Calculation of trust value for Epigraphic Database Heidelberg took 1.1682510375976562e-05s
INFO | --- Analysis for Epigraphic-Database-Heidelberg took 2.144786834716797s
Availability | SPARQL endpoint availability check for OntoComedySources took 0.1887671947479248s
Availability | VoID file availability check for OntoComedySources took 0.0012712478637695312s
Completeness | Calculation of interlinking completeness for OntoComedySources took 0.15970611572265625s
Reputation | Calculation of the PageRank for OntoComedySources took 0.020684242248535156s
Interlinking | Calculation of Degree of Connection for OntoComedySources took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for OntoComedySources took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for OntoComedySources took 1.3828277587890625e-05s
Believability | Calculation of trust value for OntoComedySources took 1.1444091796875e-05s
INFO | --- Analysis for OntoComedySources took 2.628293037414551s
Availability | SPARQL endpoint availability check for OntoCeramic 2.0 took 0.19229650497436523s
Availability | VoID file availability check for OntoCeramic 2.0 took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for OntoCeramic 2.0 took 0.15561175346374512s
Reputation | Calculation of the PageRank for OntoCeramic 2.0 took 0.02130270004272461s
Interlinking | Calculation of Degree of Connection for OntoCeramic 2.0 took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for OntoCeramic 2.0 took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for OntoCeramic 2.0 took 1.1920928955078125e-05s
Believability | Calculation of trust value for OntoCeramic 2.0 took 1.239776611328125e-05s
INFO | --- Analysis for OntoCeramic-2.0 took 3.377554416656494s
Availability | SPARQL endpoint availability check for SaintGall Ontology took 0.2043757438659668s
Availability | VoID file availability check for SaintGall Ontology took 0.00043964385986328125s
Completeness | Calculation of interlinking completeness for SaintGall Ontology took 0.1550602912902832s
Reputation | Calculation of the PageRank for SaintGall Ontology took 0.021372556686401367s
Interlinking | Calculation of Degree of Connection for SaintGall Ontology took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for SaintGall Ontology took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for SaintGall Ontology took 1.33514404296875e-05s
Believability | Calculation of trust value for SaintGall Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for SaintGall-Ontology took 1.9227831363677979s
Availability | SPARQL endpoint availability check for Linguistic Phenomena Ontology took 0.7453949451446533s
Availability | VoID file availability check for Linguistic Phenomena Ontology took 0.0006000995635986328s
Completeness | Calculation of interlinking completeness for Linguistic Phenomena Ontology took 0.16132855415344238s
Reputation | Calculation of the PageRank for Linguistic Phenomena Ontology took 0.021473407745361328s
Interlinking | Calculation of Degree of Connection for Linguistic Phenomena Ontology took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for Linguistic Phenomena Ontology took 0.0009305477142333984s
Interlinking | Calculation of Clustering coefficient for Linguistic Phenomena Ontology took 1.3828277587890625e-05s
Believability | Calculation of trust value for Linguistic Phenomena Ontology took 1.239776611328125e-05s
INFO | --- Analysis for Linguistic-Phenomena-Ontology took 2.7797048091888428s
Availability | SPARQL endpoint availability check for ICON took 0.2517859935760498s
Availability | VoID file availability check for ICON took 0.0006492137908935547s
Completeness | Calculation of interlinking completeness for ICON took 0.16463184356689453s
Reputation | Calculation of the PageRank for ICON took 0.020421743392944336s
Interlinking | Calculation of Degree of Connection for ICON took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for ICON took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for ICON took 1.1682510375976562e-05s
Believability | Calculation of trust value for ICON took 1.2159347534179688e-05s
INFO | --- Analysis for ICON took 2.843126058578491s
Availability | SPARQL endpoint availability check for Polifonia took 0.2820918560028076s
Availability | VoID file availability check for Polifonia took 0.0006422996520996094s
Completeness | Calculation of interlinking completeness for Polifonia took 0.1577293872833252s
Reputation | Calculation of the PageRank for Polifonia took 0.020322561264038086s
Interlinking | Calculation of Degree of Connection for Polifonia took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Polifonia took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Polifonia took 1.1444091796875e-05s
Believability | Calculation of trust value for Polifonia took 1.2636184692382812e-05s
INFO | --- Analysis for Polifonia took 3.0407211780548096s
Availability | SPARQL endpoint availability check for Atlas of Paths Ontology - Italian Application Profile took 0.2246847152709961s
Availability | VoID file availability check for Atlas of Paths Ontology - Italian Application Profile took 0.0007064342498779297s
Completeness | Calculation of interlinking completeness for Atlas of Paths Ontology - Italian Application Profile took 0.16192960739135742s
Reputation | Calculation of the PageRank for Atlas of Paths Ontology - Italian Application Profile took 0.020502328872680664s
Interlinking | Calculation of Degree of Connection for Atlas of Paths Ontology - Italian Application Profile took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Atlas of Paths Ontology - Italian Application Profile took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Atlas of Paths Ontology - Italian Application Profile took 1.2636184692382812e-05s
Believability | Calculation of trust value for Atlas of Paths Ontology - Italian Application Profile took 7.3909759521484375e-06s
INFO | --- Analysis for Atlas-of-Paths took 2.5528576374053955s
Availability | SPARQL endpoint availability check for Music Note Ontology took 0.25595855712890625s
Availability | VoID file availability check for Music Note Ontology took 0.0006811618804931641s
Completeness | Calculation of interlinking completeness for Music Note Ontology took 0.17100191116333008s
Reputation | Calculation of the PageRank for Music Note Ontology took 0.02208995819091797s
Interlinking | Calculation of Degree of Connection for Music Note Ontology took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Music Note Ontology took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Music Note Ontology took 1.1444091796875e-05s
Believability | Calculation of trust value for Music Note Ontology took 1.239776611328125e-05s
INFO | --- Analysis for Music-Note-Ontology took 6.433138608932495s
Availability | SPARQL endpoint availability check for HaMSE took 0.18743491172790527s
Availability | VoID file availability check for HaMSE took 0.0006346702575683594s
Completeness | Calculation of interlinking completeness for HaMSE took 0.1650853157043457s
Reputation | Calculation of the PageRank for HaMSE took 0.021639347076416016s
Interlinking | Calculation of Degree of Connection for HaMSE took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for HaMSE took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for HaMSE took 1.1920928955078125e-05s
Believability | Calculation of trust value for HaMSE took 1.2636184692382812e-05s
INFO | --- Analysis for HaMSE took 3.385908365249634s
Availability | SPARQL endpoint availability check for FOOD: FOod in Open Data took 0.09593558311462402s
Availability | VoID file availability check for FOOD: FOod in Open Data took 0.0006055831909179688s
Completeness | Calculation of interlinking completeness for FOOD: FOod in Open Data took 0.16871428489685059s
Reputation | Calculation of the PageRank for FOOD: FOod in Open Data took 0.020520925521850586s
Interlinking | Calculation of Degree of Connection for FOOD: FOod in Open Data took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for FOOD: FOod in Open Data took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for FOOD: FOod in Open Data took 1.0967254638671875e-05s
Believability | Calculation of trust value for FOOD: FOod in Open Data took 1.2159347534179688e-05s
INFO | --- Analysis for FOod took 3.5130436420440674s
Availability | SPARQL endpoint availability check for The ATLAS of Italian Digital Cultural Heritage took 0.763221263885498s
Availability | VoID file availability check for The ATLAS of Italian Digital Cultural Heritage took 0.0005981922149658203s
Completeness | Calculation of interlinking completeness for The ATLAS of Italian Digital Cultural Heritage took 0.16088247299194336s
Reputation | Calculation of the PageRank for The ATLAS of Italian Digital Cultural Heritage took 0.021506547927856445s
Interlinking | Calculation of Degree of Connection for The ATLAS of Italian Digital Cultural Heritage took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for The ATLAS of Italian Digital Cultural Heritage took 0.0009796619415283203s
Interlinking | Calculation of Clustering coefficient for The ATLAS of Italian Digital Cultural Heritage took 1.4066696166992188e-05s
Believability | Calculation of trust value for The ATLAS of Italian Digital Cultural Heritage took 1.1682510375976562e-05s
INFO | --- Analysis for ATLAS-Italian-Digital-CH took 3.6501665115356445s
Availability | SPARQL endpoint availability check for ARIADNEplus Knowledge Base took 1.353255033493042s
Availability | VoID file availability check for ARIADNEplus Knowledge Base took 0.0006873607635498047s
Completeness | Calculation of interlinking completeness for ARIADNEplus Knowledge Base took 0.15601301193237305s
Reputation | Calculation of the PageRank for ARIADNEplus Knowledge Base took 0.020658493041992188s
Interlinking | Calculation of Degree of Connection for ARIADNEplus Knowledge Base took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for ARIADNEplus Knowledge Base took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for ARIADNEplus Knowledge Base took 1.2874603271484375e-05s
Believability | Calculation of trust value for ARIADNEplus Knowledge Base took 1.1444091796875e-05s
INFO | --- Analysis for ARIADNE took 4.325688600540161s
Availability | SPARQL endpoint availability check for Odeuropa Ontology took 0.3682405948638916s
Availability | VoID file availability check for Odeuropa Ontology took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for Odeuropa Ontology took 0.19090986251831055s
Reputation | Calculation of the PageRank for Odeuropa Ontology took 0.020550966262817383s
Interlinking | Calculation of Degree of Connection for Odeuropa Ontology took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Odeuropa Ontology took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Odeuropa Ontology took 1.1444091796875e-05s
Believability | Calculation of trust value for Odeuropa Ontology took 9.5367431640625e-06s
INFO | --- Analysis for Odeuropa took 2.1256508827209473s

--- Total time for analysis:519802.7923588753s ---
--- Total time for analysis:144.38966454413202 hours ---