Availability | SPARQL endpoint availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.00010228157043457031s
Availability | VoID file availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.0006704330444335938s
Completeness | Calculation of interlinking completeness for Korespondencja Emila Szramka z Janem Kuderą took 0.29982590675354004s
Reputation | Calculation of the PageRank for Korespondencja Emila Szramka z Janem Kuderą took 0.6080794334411621s
Interlinking | Calculation of Degree of Connection for Korespondencja Emila Szramka z Janem Kuderą took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Korespondencja Emila Szramka z Janem Kuderą took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Korespondencja Emila Szramka z Janem Kuderą took 0.0004088878631591797s
Believability | Calculation of trust value for Korespondencja Emila Szramka z Janem Kuderą took 1.1920928955078125e-05s
INFO | --- Analysis for 0080-3626 took 5.233852863311768s
Availability | SPARQL endpoint availability check for 土地利用图 took 0.00010538101196289062s
Availability | VoID file availability check for 土地利用图 took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for 土地利用图 took 0.28876447677612305s
Reputation | Calculation of the PageRank for 土地利用图 took 0.020270109176635742s
Interlinking | Calculation of Degree of Connection for 土地利用图 took 3.552436828613281e-05s
Interlinking | Calculation of Centrality for 土地利用图 took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for 土地利用图 took 3.5762786865234375e-05s
Believability | Calculation of trust value for 土地利用图 took 1.1920928955078125e-05s
INFO | --- Analysis for 10.12041geodata.290864223.ver1.db_ took 2.59451961517334s
Availability | SPARQL endpoint availability check for 113322 took 0.00011610984802246094s
Availability | VoID file availability check for 113322 took 0.0006716251373291016s
Completeness | Calculation of interlinking completeness for 113322 took 0.296262264251709s
Reputation | Calculation of the PageRank for 113322 took 0.022452116012573242s
Interlinking | Calculation of Degree of Connection for 113322 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for 113322 took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for 113322 took 3.218650817871094e-05s
Believability | Calculation of trust value for 113322 took 1.5974044799804688e-05s
INFO | --- Analysis for 11 took 4.0676023960113525s
Availability | SPARQL endpoint availability check for Korepetycje Buki took 4.553794860839844e-05s
Availability | VoID file availability check for Korepetycje Buki took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for Korepetycje Buki took 0.2756223678588867s
Reputation | Calculation of the PageRank for Korepetycje Buki took 0.02051258087158203s
Interlinking | Calculation of Degree of Connection for Korepetycje Buki took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Korepetycje Buki took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Korepetycje Buki took 3.24249267578125e-05s
Believability | Calculation of trust value for Korepetycje Buki took 1.4066696166992188e-05s
INFO | --- Analysis for 12323 took 2.5436201095581055s
Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.06458520889282227s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.28643083572387695s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.02037835121154785s
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.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 9.34600830078125e-05s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 1.3828277587890625e-05s
INFO | --- Analysis for 2000-us-census-rdf took 2.647228479385376s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 2.277006149291992s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.0006191730499267578s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.29051709175109863s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.02261066436767578s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 4.5299530029296875e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 1.0251998901367188e-05s
INFO | --- Analysis for 2001-spanish-census-to-rdf took 6.658597707748413s
Availability | SPARQL endpoint availability check for Open Data Web took 10.434722661972046s
Availability | VoID file availability check for Open Data Web took 0.0005652904510498047s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.3024609088897705s
Reputation | Calculation of the PageRank for Open Data Web took 0.02043294906616211s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0008144378662109375s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 4.076957702636719e-05s
Believability | Calculation of trust value for Open Data Web took 1.3828277587890625e-05s
INFO | --- Analysis for _data.odw.tw took 18.6807062625885s
Availability | SPARQL endpoint availability check for 土地利用 took 4.792213439941406e-05s
Availability | VoID file availability check for 土地利用 took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for 土地利用 took 0.2758057117462158s
Reputation | Calculation of the PageRank for 土地利用 took 0.020397424697875977s
Interlinking | Calculation of Degree of Connection for 土地利用 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for 土地利用 took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for 土地利用 took 3.0517578125e-05s
Believability | Calculation of trust value for 土地利用 took 1.3828277587890625e-05s
INFO | --- Analysis for _data1.odw.tw took 2.603492021560669s
Availability | SPARQL endpoint availability check for 土地利用模型 took 4.6253204345703125e-05s
Availability | VoID file availability check for 土地利用模型 took 0.0006575584411621094s
Completeness | Calculation of interlinking completeness for 土地利用模型 took 0.287477970123291s
Reputation | Calculation of the PageRank for 土地利用模型 took 0.02126312255859375s
Interlinking | Calculation of Degree of Connection for 土地利用模型 took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for 土地利用模型 took 0.0012447834014892578s
Interlinking | Calculation of Clustering coefficient for 土地利用模型 took 4.673004150390625e-05s
Believability | Calculation of trust value for 土地利用模型 took 1.4066696166992188e-05s
INFO | --- Analysis for _data2.odw.tw took 4.833195924758911s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.673004150390625e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.00069427490234375s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.3021852970123291s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020978927612304688s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0008027553558349609s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.528594970703125e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.2874603271484375e-05s
INFO | --- Analysis for _https:data.bioontology.orgontologiesBOFdownloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb&download_format=rdf took 3.922889471054077s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 4.553794860839844e-05s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.0005788803100585938s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.2898259162902832s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.020684003829956055s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 3.24249267578125e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 1.5020370483398438e-05s
INFO | --- Analysis for a-collection-of-papers-for-lrec2014-and-related-workshops took 3.217656373977661s
Availability | SPARQL endpoint availability check for ITS TEST DATASET took 4.673004150390625e-05s
Availability | VoID file availability check for ITS TEST DATASET took 0.0007688999176025391s
Completeness | Calculation of interlinking completeness for ITS TEST DATASET took 0.2876608371734619s
Reputation | Calculation of the PageRank for ITS TEST DATASET took 0.021047115325927734s
Interlinking | Calculation of Degree of Connection for ITS TEST DATASET took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ITS TEST DATASET took 0.0007994174957275391s
Interlinking | Calculation of Clustering coefficient for ITS TEST DATASET took 3.4332275390625e-05s
Believability | Calculation of trust value for ITS TEST DATASET took 1.0251998901367188e-05s
INFO | --- Analysis for A1 took 3.6738715171813965s
Availability | SPARQL endpoint availability check for SummerOlympics took 2.30348539352417s
Availability | VoID file availability check for SummerOlympics took 0.0008082389831542969s
Completeness | Calculation of interlinking completeness for SummerOlympics took 0.31017065048217773s
Reputation | Calculation of the PageRank for SummerOlympics took 0.02017378807067871s
Interlinking | Calculation of Degree of Connection for SummerOlympics took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for SummerOlympics took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for SummerOlympics took 6.866455078125e-05s
Believability | Calculation of trust value for SummerOlympics took 1.430511474609375e-05s
INFO | --- Analysis for abc took 9.959794521331787s
Availability | SPARQL endpoint availability check for Test_m took 0.00010228157043457031s
Availability | VoID file availability check for Test_m took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for Test_m took 0.270648717880249s
Reputation | Calculation of the PageRank for Test_m took 0.02141714096069336s
Interlinking | Calculation of Degree of Connection for Test_m took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Test_m took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Test_m took 3.170967102050781e-05s
Believability | Calculation of trust value for Test_m took 1.1682510375976562e-05s
INFO | --- Analysis for ABC took 2.7266101837158203s
Availability | SPARQL endpoint availability check for my intro took 9.322166442871094e-05s
Availability | VoID file availability check for my intro took 0.00028896331787109375s
Completeness | Calculation of interlinking completeness for my intro took 0.27132320404052734s
Reputation | Calculation of the PageRank for my intro took 0.02048182487487793s
Interlinking | Calculation of Degree of Connection for my intro took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for my intro took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for my intro took 3.170967102050781e-05s
Believability | Calculation of trust value for my intro took 1.0013580322265625e-05s
INFO | --- Analysis for abhay_intro took 2.517174482345581s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.0885157585144043s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.276029109954834s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.020367145538330078s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 0.00010609626770019531s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 1.3589859008789062e-05s
INFO | --- Analysis for abs-linked-data took 2.707660436630249s
Availability | SPARQL endpoint availability check for AcadOnto took 9.1552734375e-05s
Availability | VoID file availability check for AcadOnto took 0.00034546852111816406s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.28223657608032227s
Reputation | Calculation of the PageRank for AcadOnto took 0.020616531372070312s
Interlinking | Calculation of Degree of Connection for AcadOnto took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for AcadOnto took 0.0007965564727783203s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 3.504753112792969e-05s
Believability | Calculation of trust value for AcadOnto took 1.4781951904296875e-05s
INFO | --- Analysis for acadonto took 3.109579086303711s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 9.098577499389648s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0007691383361816406s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.27439069747924805s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.02050042152404785s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0007419586181640625s
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 1.0728836059570312e-05s
INFO | --- Analysis for acorn-sat took 35.37569880485535s
Availability | SPARQL endpoint availability check for Addgene took 9.560585021972656e-05s
Availability | VoID file availability check for Addgene took 0.0007436275482177734s
Completeness | Calculation of interlinking completeness for Addgene took 0.2931647300720215s
Reputation | Calculation of the PageRank for Addgene took 0.020497560501098633s
Interlinking | Calculation of Degree of Connection for Addgene took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Addgene took 0.0007784366607666016s
Interlinking | Calculation of Clustering coefficient for Addgene took 3.933906555175781e-05s
Believability | Calculation of trust value for Addgene took 1.3828277587890625e-05s
INFO | --- Analysis for addgene took 15.83963942527771s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 9.34600830078125e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.0007801055908203125s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.2854902744293213s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.02029252052307129s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 9.632110595703125e-05s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 1.3828277587890625e-05s
INFO | --- Analysis for aegp-spanish-textile-and-clothing-association took 6.80065131187439s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 0.4648711681365967s
Availability | VoID file availability check for AEMET metereological dataset took 0.0006470680236816406s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.2709319591522217s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.02053546905517578s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0008022785186767578s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 3.933906555175781e-05s
Believability | Calculation of trust value for AEMET metereological dataset took 1.239776611328125e-05s
INFO | --- Analysis for aemet took 5.0283801555633545s
Availability | SPARQL endpoint availability check for AgriNepalData took 0.03970646858215332s
Availability | VoID file availability check for AgriNepalData took 0.0005834102630615234s
Completeness | Calculation of interlinking completeness for AgriNepalData took 0.27973127365112305s
Reputation | Calculation of the PageRank for AgriNepalData took 0.02210831642150879s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 7.2479248046875e-05s
Believability | Calculation of trust value for AgriNepalData took 1.33514404296875e-05s
INFO | --- Analysis for agrinepaldata took 2.700089454650879s
Availability | SPARQL endpoint availability check for AGRIS took 260.426353931427s
Availability | VoID file availability check for AGRIS took 0.0006363391876220703s
Completeness | Calculation of interlinking completeness for AGRIS took 0.2932271957397461s
Reputation | Calculation of the PageRank for AGRIS took 0.020779848098754883s
Interlinking | Calculation of Degree of Connection for AGRIS took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for AGRIS took 0.0008666515350341797s
Interlinking | Calculation of Clustering coefficient for AGRIS took 9.131431579589844e-05s
Believability | Calculation of trust value for AGRIS took 1.33514404296875e-05s
INFO | --- Analysis for agris took 572.170806646347s
Availability | SPARQL endpoint availability check for AGROVOC took 0.1981191635131836s
Availability | VoID file availability check for AGROVOC took 0.0006000995635986328s
Extra | Recovery of all triples for AGROVOC took 84.56114745140076s
Performance | Total latancy measurement for AGROVOC took 0.4511587619781494s
Amount of data | Number of triples check for AGROVOC took 148.99576830863953s
Interoperability | New terms check for AGROVOC took 4.415603876113892s
Versatility | Languages check for AGROVOC took 300.08492279052734s
Interpretability | Number of blank nodes check for AGROVOC took 124.11056780815125s
Interpretability | RDF structures check for AGROVOC took 0.0892341136932373s
Versatility | Serialization formats check for AGROVOC took 0.08600902557373047s
Availability | RDF dump link check for AGROVOC took 0.09540843963623047s
License | MR license check for AGROVOC took 0.08675646781921387s
License | HR license check for AGROVOC took 1.2942531108856201s
Amount of data | Number of property check for AGROVOC took 0.10196566581726074s
Understandability | Number of label check for AGROVOC took 59.34198784828186s
Understandability | URI regex check for AGROVOC took 0.1658310890197754s
Understandability | Vocabs check for AGROVOC took 0.08808374404907227s
Verifiability | Authors check for AGROVOC took 0.07797908782958984s
Verifiability | Publishers check for AGROVOC took 0.09130191802978516s
Performance | Throughput check for AGROVOC took 10.535348892211914s
Amount of data | Check the number of entities for AGROVOC took 8.821487426757812e-05s
Verifiability | Contribs. check for AGROVOC took 0.09450888633728027s
Interlinking | sameAs chians check for AGROVOC took 0.09338116645812988s
Interlinking | skos check for AGROVOC took 4.503561735153198s
Interlinking | skos check for AGROVOC took 4.27715802192688s
Timeliness | dataset update frequency check for AGROVOC took 0.09032750129699707s
Currency | Creation date check for AGROVOC took 0.18735718727111816s
Currency | Modification date check for AGROVOC took 0.1663203239440918s
Rep.Conc. | URIs length for AGROVOC took 131.08679723739624s
Interoperability | New vocabularies check for AGROVOC took 1.1682510375976562e-05s
Consistency | Deprecated classes/propertiers check for AGROVOC took 0.09761691093444824s
Accuracy | Check Functional Property for AGROVOC took 0.08621430397033691s
Accuracy | Check Inverse Functional Property for AGROVOC took 0.08528780937194824s
Accuracy | Check Empty annotation labels for AGROVOC took 17.38666844367981s
Accuracy | Check White space in annotation for AGROVOC took 3.008542776107788s
Accuracy | Check Datatype consistency for AGROVOC took 4.534964561462402s
Consistency | Disjoint class check for AGROVOC took 0.0795888900756836s
Consistency | Check Misplaced properties for AGROVOC took 25.159159660339355s
Consistency | Check Ontology hijacking for AGROVOC took 178.75245451927185s
Consistency | Check Invalid usage of undefined classes for AGROVOC took 1.706451654434204s
Consistency | Check Invalid usage of undefined properties for AGROVOC took 29.629552602767944s
Conciseness | Check Extensional conciseness for AGROVOC took 2.6320242881774902s
Conciseness | Check Intensional conciseness for AGROVOC took 0.1564955711364746s
Security | Sign check for AGROVOC took 0.09361958503723145s
Availability | Check URIs Dereferenciability for AGROVOC took 2.9443159103393555s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.5957705974578857s
Reputation | Calculation of the PageRank for AGROVOC took 0.021816015243530273s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 0.0001270771026611328s
Interoperability | Check the re-using of existing vocabs for AGROVOC took 2.1457672119140625e-06s
Believability | Calculation of trust value for AGROVOC took 1.049041748046875e-05s
INFO | --- Analysis for agrovoc took 1682.8573713302612s
Availability | SPARQL endpoint availability check for Analytics India Magazine took 1.329160451889038s
Availability | VoID file availability check for Analytics India Magazine took 0.0006852149963378906s
Extra | Recovery of all triples for Analytics India Magazine took 2.582972764968872s
Performance | Total latancy measurement for Analytics India Magazine took 1.4044981002807617s
Amount of data | Number of triples check for Analytics India Magazine took 1.2169299125671387s
Versatility | Languages check for Analytics India Magazine took 1.3123350143432617s
Interpretability | Number of blank nodes check for Analytics India Magazine took 1.5495836734771729s
Interpretability | RDF structures check for Analytics India Magazine took 1.3566272258758545s
Versatility | Serialization formats check for Analytics India Magazine took 1.6862869262695312s
Availability | RDF dump link check for Analytics India Magazine took 1.3007135391235352s
License | MR license check for Analytics India Magazine took 1.0201013088226318s
License | HR license check for Analytics India Magazine took 1.236774206161499s
Amount of data | Number of property check for Analytics India Magazine took 1.4818353652954102s
Understandability | Number of label check for Analytics India Magazine took 1.3648455142974854s
Understandability | URI regex check for Analytics India Magazine took 2.273308038711548s
Understandability | Vocabs check for Analytics India Magazine took 1.2759807109832764s
Verifiability | Authors check for Analytics India Magazine took 1.1259334087371826s
Verifiability | Publishers check for Analytics India Magazine took 1.18782377243042s
Performance | Throughput check for Analytics India Magazine took 16.158692836761475s
Amount of data | Check the number of entities for Analytics India Magazine took 4.792213439941406e-05s
Verifiability | Contribs. check for Analytics India Magazine took 0.9437823295593262s
Interlinking | sameAs chians check for Analytics India Magazine took 0.9305069446563721s
Interlinking | skos check for Analytics India Magazine took 1.047959804534912s
Interlinking | skos check for Analytics India Magazine took 0.13726234436035156s
Timeliness | dataset update frequency check for Analytics India Magazine took 0.9225571155548096s
Currency | Creation date check for Analytics India Magazine took 2.3951783180236816s
Currency | Modification date check for Analytics India Magazine took 2.1132943630218506s
Rep.Conc. | URIs length for Analytics India Magazine took 3.0755887031555176s
Interoperability | New vocabularies check for Analytics India Magazine took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for Analytics India Magazine took 0.9985942840576172s
Consistency | Disjoint class check for Analytics India Magazine took 1.2455198764801025s
Consistency | Check Ontology hijacking for Analytics India Magazine took 1.1018364429473877s
Consistency | Check Invalid usage of undefined properties for Analytics India Magazine took 2.5696935653686523s
Conciseness | Check Extensional conciseness for Analytics India Magazine took 0.00015044212341308594s
Security | Sign check for Analytics India Magazine took 1.0947518348693848s
Completeness | Calculation of interlinking completeness for Analytics India Magazine took 0.37772202491760254s
Reputation | Calculation of the PageRank for Analytics India Magazine took 0.022469282150268555s
Interlinking | Calculation of Degree of Connection for Analytics India Magazine took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Analytics India Magazine took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Analytics India Magazine took 3.409385681152344e-05s
Interoperability | Check the re-using of existing vocabs for Analytics India Magazine took 1.6689300537109375e-06s
Believability | Calculation of trust value for Analytics India Magazine took 1.3828277587890625e-05s
INFO | --- Analysis for AIM took 92.63058400154114s
Availability | SPARQL endpoint availability check for All India Survey of Higher Education took 8.392333984375e-05s
Availability | VoID file availability check for All India Survey of Higher Education took 0.0005352497100830078s
Completeness | Calculation of interlinking completeness for All India Survey of Higher Education took 0.28577280044555664s
Reputation | Calculation of the PageRank for All India Survey of Higher Education took 0.020781993865966797s
Interlinking | Calculation of Degree of Connection for All India Survey of Higher Education took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for All India Survey of Higher Education took 0.0009515285491943359s
Interlinking | Calculation of Clustering coefficient for All India Survey of Higher Education took 4.410743713378906e-05s
Believability | Calculation of trust value for All India Survey of Higher Education took 1.3828277587890625e-05s
INFO | --- Analysis for AISHE took 2.6609766483306885s
Availability | SPARQL endpoint availability check for  equipment ontology took 9.202957153320312e-05s
Availability | VoID file availability check for  equipment ontology took 0.0005679130554199219s
Completeness | Calculation of interlinking completeness for  equipment ontology took 0.28569626808166504s
Reputation | Calculation of the PageRank for  equipment ontology took 0.02061915397644043s
Interlinking | Calculation of Degree of Connection for  equipment ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for  equipment ontology took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for  equipment ontology took 3.62396240234375e-05s
Believability | Calculation of trust value for  equipment ontology took 1.1444091796875e-05s
INFO | --- Analysis for akash took 2.5763349533081055s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 263.3425097465515s
Availability | VoID file availability check for aliada-scanbit-net took 0.001062154769897461s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 0.4554135799407959s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.022986173629760742s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0007898807525634766s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.00012540817260742188s
Believability | Calculation of trust value for aliada-scanbit-net took 1.3589859008789062e-05s
INFO | --- Analysis for aliada-scanbit-net took 1454.9360842704773s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 0.6388685703277588s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.0005197525024414062s
Extra | Recovery of all triples for Allie Abbreviation And Long Form Database in Life Science took 136.15432476997375s
Performance | Total latancy measurement for Allie Abbreviation And Long Form Database in Life Science took 2.9504222869873047s
Amount of data | Number of triples check for Allie Abbreviation And Long Form Database in Life Science took 1.4163625240325928s
Interoperability | New terms check for Allie Abbreviation And Long Form Database in Life Science took 3.633974075317383s
Versatility | Languages check for Allie Abbreviation And Long Form Database in Life Science took 300.07226037979126s
Interpretability | Number of blank nodes check for Allie Abbreviation And Long Form Database in Life Science took 3.718003034591675s
Security | Check HTTPS for Allie Abbreviation And Long Form Database in Life Science took 1.868274450302124s
Interpretability | RDF structures check for Allie Abbreviation And Long Form Database in Life Science took 0.5970897674560547s
Versatility | Serialization formats check for Allie Abbreviation And Long Form Database in Life Science took 0.6578230857849121s
Availability | RDF dump link check for Allie Abbreviation And Long Form Database in Life Science took 0.5629136562347412s
License | MR license check for Allie Abbreviation And Long Form Database in Life Science took 0.5999777317047119s
License | HR license check for Allie Abbreviation And Long Form Database in Life Science took 31.58212971687317s
Amount of data | Number of property check for Allie Abbreviation And Long Form Database in Life Science took 0.5736217498779297s
Understandability | Number of label check for Allie Abbreviation And Long Form Database in Life Science took 0.7926812171936035s
Understandability | URI regex check for Allie Abbreviation And Long Form Database in Life Science took 1.1770310401916504s
Understandability | Vocabs check for Allie Abbreviation And Long Form Database in Life Science took 0.6050679683685303s
Verifiability | Authors check for Allie Abbreviation And Long Form Database in Life Science took 0.5990300178527832s
Verifiability | Publishers check for Allie Abbreviation And Long Form Database in Life Science took 0.5570602416992188s
Performance | Throughput check for Allie Abbreviation And Long Form Database in Life Science took 10.855909824371338s
Amount of data | Check the number of entities for Allie Abbreviation And Long Form Database in Life Science took 7.581710815429688e-05s
Verifiability | Contribs. check for Allie Abbreviation And Long Form Database in Life Science took 0.5680382251739502s
Interlinking | sameAs chians check for Allie Abbreviation And Long Form Database in Life Science took 0.5837557315826416s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.6689224243164062s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.5570003986358643s
Timeliness | dataset update frequency check for Allie Abbreviation And Long Form Database in Life Science took 0.5939853191375732s
Currency | Creation date check for Allie Abbreviation And Long Form Database in Life Science took 1.9053869247436523s
Currency | Modification date check for Allie Abbreviation And Long Form Database in Life Science took 1.1157076358795166s
Rep.Conc. | URIs length for Allie Abbreviation And Long Form Database in Life Science took 53.971259117126465s
Interoperability | New vocabularies check for Allie Abbreviation And Long Form Database in Life Science took 2.714174270629883s
Consistency | Deprecated classes/propertiers check for Allie Abbreviation And Long Form Database in Life Science took 0.5616214275360107s
Accuracy | Check Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6850643157958984s
Accuracy | Check Inverse Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6614682674407959s
Accuracy | Check Empty annotation labels for Allie Abbreviation And Long Form Database in Life Science took 36.070608377456665s
Accuracy | Check White space in annotation for Allie Abbreviation And Long Form Database in Life Science took 3.0823802947998047s
Accuracy | Check Datatype consistency for Allie Abbreviation And Long Form Database in Life Science took 2.7399375438690186s
Consistency | Disjoint class check for Allie Abbreviation And Long Form Database in Life Science took 0.5924491882324219s
Consistency | Check Misplaced properties for Allie Abbreviation And Long Form Database in Life Science took 10.422576427459717s
Consistency | Misplaced classes for Allie Abbreviation And Long Form Database in Life Science took 9.11225700378418s
Consistency | Check Ontology hijacking for Allie Abbreviation And Long Form Database in Life Science took 32.697842836380005s
Consistency | Check Invalid usage of undefined classes for Allie Abbreviation And Long Form Database in Life Science took 1.5513310432434082s
Consistency | Check Invalid usage of undefined properties for Allie Abbreviation And Long Form Database in Life Science took 11.589023351669312s
Conciseness | Check Extensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 2.8320155143737793s
Conciseness | Check Intensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 0.8273336887359619s
Security | Sign check for Allie Abbreviation And Long Form Database in Life Science took 0.5467221736907959s
Availability | Check URIs Dereferenciability for Allie Abbreviation And Long Form Database in Life Science took 13813.448743104935s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 0.5933609008789062s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.02350640296936035s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0008561611175537109s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 0.0001327991485595703s
Interoperability | Check the re-using of existing vocabs for Allie Abbreviation And Long Form Database in Life Science took 3.930914878845215s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 1.4781951904296875e-05s
INFO | --- Analysis for allie-abbreviation-and-long-form-database-in-life-science took 14566.58282160759s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 0.29696083068847656s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.0007061958312988281s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 0.28371715545654297s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.02059626579284668s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 4.172325134277344e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 1.52587890625e-05s
INFO | --- Analysis for alpino-rdf took 3.6769630908966064s
Availability | SPARQL endpoint availability check for AAT-atawil took 9.560585021972656e-05s
Availability | VoID file availability check for AAT-atawil took 0.0006310939788818359s
Completeness | Calculation of interlinking completeness for AAT-atawil took 0.31125473976135254s
Reputation | Calculation of the PageRank for AAT-atawil took 0.02146124839782715s
Interlinking | Calculation of Degree of Connection for AAT-atawil took 1.52587890625e-05s
Interlinking | Calculation of Centrality for AAT-atawil took 0.0011229515075683594s
Interlinking | Calculation of Clustering coefficient for AAT-atawil took 4.363059997558594e-05s
Believability | Calculation of trust value for AAT-atawil took 1.5020370483398438e-05s
INFO | --- Analysis for Altawil took 2.6677095890045166s
Availability | SPARQL endpoint availability check for Amer Nejma took 4.6253204345703125e-05s
Availability | VoID file availability check for Amer Nejma took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for Amer Nejma took 0.28172945976257324s
Reputation | Calculation of the PageRank for Amer Nejma took 0.022476673126220703s
Interlinking | Calculation of Degree of Connection for Amer Nejma took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Amer Nejma took 0.0008509159088134766s
Interlinking | Calculation of Clustering coefficient for Amer Nejma took 3.6716461181640625e-05s
Believability | Calculation of trust value for Amer Nejma took 1.4781951904296875e-05s
INFO | --- Analysis for Amer_Nejma took 2.6111929416656494s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.739567756652832s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.2836027145385742s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.020455360412597656s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 9.72747802734375e-05s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.3828277587890625e-05s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 4.340157747268677s
Availability | SPARQL endpoint availability check for Anime Dataset took 9.179115295410156e-05s
Availability | VoID file availability check for Anime Dataset took 0.0006761550903320312s
Completeness | Calculation of interlinking completeness for Anime Dataset took 0.2822384834289551s
Reputation | Calculation of the PageRank for Anime Dataset took 0.02104043960571289s
Interlinking | Calculation of Degree of Connection for Anime Dataset took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Anime Dataset took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Anime Dataset took 3.337860107421875e-05s
Believability | Calculation of trust value for Anime Dataset took 9.5367431640625e-06s
INFO | --- Analysis for Anime took 3.8488433361053467s
Availability | SPARQL endpoint availability check for ANNO took 9.608268737792969e-05s
Availability | VoID file availability check for ANNO took 0.0007314682006835938s
Completeness | Calculation of interlinking completeness for ANNO took 0.27518415451049805s
Reputation | Calculation of the PageRank for ANNO took 0.020754098892211914s
Interlinking | Calculation of Degree of Connection for ANNO took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ANNO took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for ANNO took 3.647804260253906e-05s
Believability | Calculation of trust value for ANNO took 1.1205673217773438e-05s
INFO | --- Analysis for anno took 7.934150457382202s
Availability | SPARQL endpoint availability check for Antique Cars Collection (Linked Cars) took 0.00010991096496582031s
Availability | VoID file availability check for Antique Cars Collection (Linked Cars) took 0.0006389617919921875s
Completeness | Calculation of interlinking completeness for Antique Cars Collection (Linked Cars) took 0.29338884353637695s
Reputation | Calculation of the PageRank for Antique Cars Collection (Linked Cars) took 0.02051067352294922s
Interlinking | Calculation of Degree of Connection for Antique Cars Collection (Linked Cars) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Antique Cars Collection (Linked Cars) took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for Antique Cars Collection (Linked Cars) took 8.249282836914062e-05s
Believability | Calculation of trust value for Antique Cars Collection (Linked Cars) took 1.430511474609375e-05s
INFO | --- Analysis for AntiqueCarsCollection took 3.2334413528442383s
Availability | SPARQL endpoint availability check for apache took 9.369850158691406e-05s
Availability | VoID file availability check for apache took 0.0008296966552734375s
Completeness | Calculation of interlinking completeness for apache took 0.2993018627166748s
Reputation | Calculation of the PageRank for apache took 0.020346403121948242s
Interlinking | Calculation of Degree of Connection for apache took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for apache took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for apache took 5.698204040527344e-05s
Believability | Calculation of trust value for apache took 1.3828277587890625e-05s
INFO | --- Analysis for apache took 3.513669967651367s
Availability | SPARQL endpoint availability check for Apertium RDF took 9.369850158691406e-05s
Availability | VoID file availability check for Apertium RDF took 0.0006542205810546875s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.26427316665649414s
Reputation | Calculation of the PageRank for Apertium RDF took 0.022240400314331055s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 4.5299530029296875e-05s
Believability | Calculation of trust value for Apertium RDF took 1.3589859008789062e-05s
INFO | --- Analysis for apertium-rdf took 5.791853904724121s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 9.250640869140625e-05s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.29041147232055664s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.020407676696777344s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.0007660388946533203s
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 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-ca-it took 5.872255802154541s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 5.125999450683594e-05s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.0006048679351806641s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.287278413772583s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.022345304489135742s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 4.458427429199219e-05s
Believability | Calculation of trust value for Apertium RDF EN-CA took 1.3828277587890625e-05s
INFO | --- Analysis for apertium-rdf-en-ca took 5.8894944190979s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 9.131431579589844e-05s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.0005843639373779297s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.29419708251953125s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.020433664321899414s
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.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 4.673004150390625e-05s
Believability | Calculation of trust value for Apertium RDF EN-ES took 1.2636184692382812e-05s
INFO | --- Analysis for apertium-rdf-en-es took 5.82103967666626s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 4.8160552978515625e-05s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.0006263256072998047s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.28505849838256836s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.020917654037475586s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-GL took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-GL took 0.0008213520050048828s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 5.459785461425781e-05s
Believability | Calculation of trust value for Apertium RDF EN-GL took 1.2874603271484375e-05s
INFO | --- Analysis for apertium-rdf-en-gl took 5.715839147567749s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 9.417533874511719e-05s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.0005822181701660156s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 0.2815577983856201s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.02060246467590332s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 4.792213439941406e-05s
Believability | Calculation of trust value for Apertium RDF EO-CA took 1.33514404296875e-05s
INFO | --- Analysis for apertium-rdf-eo-ca took 5.801229000091553s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 4.57763671875e-05s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.0006947517395019531s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.28366851806640625s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.02089095115661621s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-EN took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-EN took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 5.0067901611328125e-05s
Believability | Calculation of trust value for Apertium RDF EO-EN took 1.0728836059570312e-05s
INFO | --- Analysis for apertium-rdf-eo-en took 5.823987245559692s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 4.649162292480469e-05s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.0003578662872314453s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.26808881759643555s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.020344257354736328s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 4.553794860839844e-05s
Believability | Calculation of trust value for Apertium RDF EO-ES took 7.867813110351562e-06s
INFO | --- Analysis for apertium-rdf-eo-es took 5.656107187271118s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 4.506111145019531e-05s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.0006785392761230469s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.27446842193603516s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.020494461059570312s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.0008122920989990234s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 5.626678466796875e-05s
Believability | Calculation of trust value for Apertium RDF EO-FR took 1.0013580322265625e-05s
INFO | --- Analysis for apertium-rdf-eo-fr took 5.707001447677612s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 5.1021575927734375e-05s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.0006220340728759766s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.28553318977355957s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.02035665512084961s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 4.506111145019531e-05s
Believability | Calculation of trust value for Apertium RDF ES-AN took 1.2159347534179688e-05s
INFO | --- Analysis for apertium-rdf-es-an took 6.001615285873413s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 4.482269287109375e-05s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0006847381591796875s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.2635993957519531s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.020531892776489258s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 4.839897155761719e-05s
Believability | Calculation of trust value for Apertium RDF ES-AST took 8.344650268554688e-06s
INFO | --- Analysis for apertium-rdf-es-ast took 5.806735277175903s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 8.654594421386719e-05s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.0008082389831542969s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 0.2846031188964844s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.02163100242614746s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 4.935264587402344e-05s
Believability | Calculation of trust value for Apertium RDF ES-CA took 1.0251998901367188e-05s
INFO | --- Analysis for apertium-rdf-es-ca took 25.058647871017456s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 4.696846008300781e-05s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.0007119178771972656s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.2951176166534424s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.02029585838317871s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 4.482269287109375e-05s
Believability | Calculation of trust value for Apertium RDF ES-GL took 1.5974044799804688e-05s
INFO | --- Analysis for apertium-rdf-es-gl took 5.818370342254639s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 0.00010991096496582031s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.00044226646423339844s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.28444385528564453s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.02251267433166504s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0007853507995605469s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 4.792213439941406e-05s
Believability | Calculation of trust value for Apertium RDF ES-PT took 1.4066696166992188e-05s
INFO | --- Analysis for apertium-rdf-es-pt took 5.797681093215942s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 0.00015687942504882812s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.29665112495422363s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.020521163940429688s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.0007944107055664062s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 4.744529724121094e-05s
Believability | Calculation of trust value for Apertium RDF ES-RO took 1.3589859008789062e-05s
INFO | --- Analysis for apertium-rdf-es-ro took 5.864140033721924s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 4.887580871582031e-05s
Availability | VoID file availability check for Apertium RDF EU-EN took 0.0007617473602294922s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.29741358757019043s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.020654678344726562s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 4.744529724121094e-05s
Believability | Calculation of trust value for Apertium RDF EU-EN took 1.5974044799804688e-05s
INFO | --- Analysis for apertium-rdf-eu-en took 5.902500867843628s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 9.489059448242188e-05s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.0007398128509521484s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.28864121437072754s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.02090311050415039s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 4.553794860839844e-05s
Believability | Calculation of trust value for Apertium RDF EU-ES took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-eu-es took 5.768197059631348s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 4.792213439941406e-05s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.0007088184356689453s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.2851297855377197s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.020352602005004883s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 4.7206878662109375e-05s
Believability | Calculation of trust value for Apertium RDF FR-CA took 1.4066696166992188e-05s
INFO | --- Analysis for apertium-rdf-fr-ca took 5.734210729598999s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 0.00015664100646972656s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.0006685256958007812s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.30588531494140625s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.020508289337158203s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 4.982948303222656e-05s
Believability | Calculation of trust value for Apertium RDF FR-ES took 1.3589859008789062e-05s
INFO | --- Analysis for apertium-rdf-fr-es took 5.883775472640991s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 5.173683166503906e-05s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0004639625549316406s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 0.29389166831970215s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.02099323272705078s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.001074075698852539s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 5.435943603515625e-05s
Believability | Calculation of trust value for Apertium RDF OC-CA took 1.430511474609375e-05s
INFO | --- Analysis for apertium-rdf-oc-ca took 5.8654444217681885s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 9.679794311523438e-05s
Availability | VoID file availability check for Apertium RDF OC-ES took 0.0007460117340087891s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 0.2957754135131836s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.020723819732666016s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 4.935264587402344e-05s
Believability | Calculation of trust value for Apertium RDF OC-ES took 1.3589859008789062e-05s
INFO | --- Analysis for apertium-rdf-oc-es took 5.84737491607666s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 9.441375732421875e-05s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.0008852481842041016s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 0.28888845443725586s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.022461414337158203s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0007987022399902344s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 5.626678466796875e-05s
Believability | Calculation of trust value for Apertium RDF PT-CA took 1.7642974853515625e-05s
INFO | --- Analysis for apertium-rdf-pt-ca took 5.8615851402282715s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 9.322166442871094e-05s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.0006358623504638672s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.2869434356689453s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.02045583724975586s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 4.8160552978515625e-05s
Believability | Calculation of trust value for Apertium RDF PT-GL took 1.1205673217773438e-05s
INFO | --- Analysis for apertium-rdf-pt-gl took 6.4460389614105225s
Availability | SPARQL endpoint availability check for AragoDBpedia - aragon open data took 0.5560853481292725s
Availability | VoID file availability check for AragoDBpedia - aragon open data took 0.0011219978332519531s
Extra | Recovery of all triples for AragoDBpedia - aragon open data took 2.7216796875s
Performance | Total latancy measurement for AragoDBpedia - aragon open data took 1.5947608947753906s
Amount of data | Number of triples check for AragoDBpedia - aragon open data took 0.7038741111755371s
Interoperability | New terms check for AragoDBpedia - aragon open data took 2.162527084350586s
Versatility | Languages check for AragoDBpedia - aragon open data took 60.40739822387695s
Interpretability | Number of blank nodes check for AragoDBpedia - aragon open data took 4.102403163909912s
Security | Check HTTPS for AragoDBpedia - aragon open data took 0.22478199005126953s
Interpretability | RDF structures check for AragoDBpedia - aragon open data took 0.560049295425415s
Versatility | Serialization formats check for AragoDBpedia - aragon open data took 0.8423998355865479s
Availability | RDF dump link check for AragoDBpedia - aragon open data took 0.3574230670928955s
License | MR license check for AragoDBpedia - aragon open data took 0.4797170162200928s
License | HR license check for AragoDBpedia - aragon open data took 5.385693311691284s
Amount of data | Number of property check for AragoDBpedia - aragon open data took 0.34128761291503906s
Understandability | Number of label check for AragoDBpedia - aragon open data took 0.4355039596557617s
Understandability | URI regex check for AragoDBpedia - aragon open data took 0.7374029159545898s
Understandability | Vocabs check for AragoDBpedia - aragon open data took 0.3630189895629883s
Verifiability | Authors check for AragoDBpedia - aragon open data took 0.38997626304626465s
Verifiability | Publishers check for AragoDBpedia - aragon open data took 0.32886338233947754s
Performance | Throughput check for AragoDBpedia - aragon open data took 12.341805696487427s
Amount of data | Check the number of entities for AragoDBpedia - aragon open data took 7.128715515136719e-05s
Verifiability | Contribs. check for AragoDBpedia - aragon open data took 0.5038421154022217s
Interlinking | sameAs chians check for AragoDBpedia - aragon open data took 0.43105101585388184s
Interlinking | skos check for AragoDBpedia - aragon open data took 0.7763657569885254s
Interlinking | skos check for AragoDBpedia - aragon open data took 0.3304886817932129s
Timeliness | dataset update frequency check for AragoDBpedia - aragon open data took 0.5093445777893066s
Currency | Creation date check for AragoDBpedia - aragon open data took 1.0752649307250977s
Currency | Modification date check for AragoDBpedia - aragon open data took 0.35941338539123535s
Rep.Conc. | URIs length for AragoDBpedia - aragon open data took 5.651921987533569s
Interoperability | New vocabularies check for AragoDBpedia - aragon open data took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for AragoDBpedia - aragon open data took 0.31881284713745117s
Accuracy | Check Functional Property for AragoDBpedia - aragon open data took 0.4343233108520508s
Accuracy | Check Inverse Functional Property for AragoDBpedia - aragon open data took 0.4396545886993408s
Accuracy | Check Empty annotation labels for AragoDBpedia - aragon open data took 1.2641727924346924s
Accuracy | Check White space in annotation for AragoDBpedia - aragon open data took 0.030376195907592773s
Accuracy | Check Datatype consistency for AragoDBpedia - aragon open data took 0.02930593490600586s
Consistency | Disjoint class check for AragoDBpedia - aragon open data took 0.3436710834503174s
Consistency | Check Misplaced properties for AragoDBpedia - aragon open data took 4.245518207550049s
Consistency | Misplaced classes for AragoDBpedia - aragon open data took 0.5443964004516602s
Consistency | Check Ontology hijacking for AragoDBpedia - aragon open data took 2.5016307830810547s
Consistency | Check Invalid usage of undefined classes for AragoDBpedia - aragon open data took 1.4361119270324707s
Consistency | Check Invalid usage of undefined properties for AragoDBpedia - aragon open data took 5.121819734573364s
Conciseness | Check Extensional conciseness for AragoDBpedia - aragon open data took 0.03300142288208008s
Conciseness | Check Intensional conciseness for AragoDBpedia - aragon open data took 0.5565574169158936s
Security | Sign check for AragoDBpedia - aragon open data took 0.6603624820709229s
Availability | Check URIs Dereferenciability for AragoDBpedia - aragon open data took 2725.0284838676453s
Completeness | Calculation of interlinking completeness for AragoDBpedia - aragon open data took 0.4865405559539795s
Reputation | Calculation of the PageRank for AragoDBpedia - aragon open data took 0.02123880386352539s
Interlinking | Calculation of Degree of Connection for AragoDBpedia - aragon open data took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for AragoDBpedia - aragon open data took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for AragoDBpedia - aragon open data took 5.602836608886719e-05s
Interoperability | Check the re-using of existing vocabs for AragoDBpedia - aragon open data took 1.6689300537109375e-06s
Believability | Calculation of trust value for AragoDBpedia - aragon open data took 1.0967254638671875e-05s
INFO | --- Analysis for aragodbpedia took 2985.0898303985596s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 30.336216926574707s
Availability | VoID file availability check for Archives Hub Linked Data took 0.0007498264312744141s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.2910952568054199s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.025456905364990234s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 6.151199340820312e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 1.0967254638671875e-05s
INFO | --- Analysis for archiveshub-linkeddata took 83.19273114204407s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 4.4898293018341064s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.0006592273712158203s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 0.29380178451538086s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.020862817764282227s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 3.695487976074219e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 1.4781951904296875e-05s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 20.23443031311035s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.824895143508911s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0006551742553710938s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.28593969345092773s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.02062702178955078s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0007853507995605469s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 5.1021575927734375e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.430511474609375e-05s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 16.413479804992676s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 8.916854858398438e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0007417201995849609s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.3518533706665039s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.020930767059326172s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.00011897087097167969s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.3828277587890625e-05s
INFO | --- Analysis for artenuevosmedios-gnoss took 167.7159185409546s
Availability | SPARQL endpoint availability check for Arthroscopy community took 9.131431579589844e-05s
Availability | VoID file availability check for Arthroscopy community took 0.0006191730499267578s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 0.29999208450317383s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.020601272583007812s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 0.00011467933654785156s
Believability | Calculation of trust value for Arthroscopy community took 1.4781951904296875e-05s
INFO | --- Analysis for arthroscopy took 33.729615449905396s
Availability | SPARQL endpoint availability check for Wikidata entry for Art × Science International took 0.6662664413452148s
Availability | VoID file availability check for Wikidata entry for Art × Science International took 0.0007257461547851562s
Extra | Recovery of all triples for Wikidata entry for Art × Science International took 42.77314472198486s
Performance | Total latancy measurement for Wikidata entry for Art × Science International took 1.2890210151672363s
Amount of data | Number of triples check for Wikidata entry for Art × Science International took 65.17458248138428s
Interoperability | New terms check for Wikidata entry for Art × Science International took 2.3864240646362305s
Versatility | Languages check for Wikidata entry for Art × Science International took 65.1542980670929s
Interpretability | Number of blank nodes check for Wikidata entry for Art × Science International took 65.16584467887878s
Interpretability | RDF structures check for Wikidata entry for Art × Science International took 0.3903939723968506s
Versatility | Serialization formats check for Wikidata entry for Art × Science International took 0.5917975902557373s
Availability | RDF dump link check for Wikidata entry for Art × Science International took 0.6063516139984131s
License | MR license check for Wikidata entry for Art × Science International took 0.2604072093963623s
License | HR license check for Wikidata entry for Art × Science International took 65.16905403137207s
Amount of data | Number of property check for Wikidata entry for Art × Science International took 0.17059016227722168s
Understandability | Number of label check for Wikidata entry for Art × Science International took 60.22529935836792s
Understandability | URI regex check for Wikidata entry for Art × Science International took 0.3974931240081787s
Understandability | Vocabs check for Wikidata entry for Art × Science International took 0.17323732376098633s
Verifiability | Authors check for Wikidata entry for Art × Science International took 0.3061363697052002s
Verifiability | Publishers check for Wikidata entry for Art × Science International took 0.2654585838317871s
Amount of data | Check the number of entities for Wikidata entry for Art × Science International took 7.891654968261719e-05s
Verifiability | Contribs. check for Wikidata entry for Art × Science International took 0.18537211418151855s
Interlinking | sameAs chians check for Wikidata entry for Art × Science International took 30.977211236953735s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.24956631660461426s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.0927741527557373s
Timeliness | dataset update frequency check for Wikidata entry for Art × Science International took 0.35546040534973145s
Currency | Creation date check for Wikidata entry for Art × Science International took 0.3521120548248291s
Currency | Modification date check for Wikidata entry for Art × Science International took 0.6294009685516357s
Rep.Conc. | URIs length for Wikidata entry for Art × Science International took 46.41133427619934s
Interoperability | New vocabularies check for Wikidata entry for Art × Science International took 6.9141387939453125e-06s
Consistency | Deprecated classes/propertiers check for Wikidata entry for Art × Science International took 0.24701547622680664s
Accuracy | Check Empty annotation labels for Wikidata entry for Art × Science International took 30.809361696243286s
Accuracy | Check White space in annotation for Wikidata entry for Art × Science International took 2.696899890899658s
Accuracy | Check Datatype consistency for Wikidata entry for Art × Science International took 4.779117107391357s
Consistency | Disjoint class check for Wikidata entry for Art × Science International took 0.18051505088806152s
Consistency | Check Misplaced properties for Wikidata entry for Art × Science International took 36.15446329116821s
Consistency | Misplaced classes for Wikidata entry for Art × Science International took 8.995315551757812s
Consistency | Check Ontology hijacking for Wikidata entry for Art × Science International took 61.975608587265015s
Consistency | Check Invalid usage of undefined properties for Wikidata entry for Art × Science International took 2.269127130508423s
Conciseness | Check Extensional conciseness for Wikidata entry for Art × Science International took 2.861743450164795s
Conciseness | Check Intensional conciseness for Wikidata entry for Art × Science International took 1.643068552017212s
Security | Sign check for Wikidata entry for Art × Science International took 0.20333051681518555s
Availability | Check URIs Dereferenciability for Wikidata entry for Art × Science International took 0.2884042263031006s
Completeness | Calculation of interlinking completeness for Wikidata entry for Art × Science International took 0.4378550052642822s
Reputation | Calculation of the PageRank for Wikidata entry for Art × Science International took 0.020912885665893555s
Interlinking | Calculation of Degree of Connection for Wikidata entry for Art × Science International took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Wikidata entry for Art × Science International took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Wikidata entry for Art × Science International took 2.3603439331054688e-05s
Interoperability | Check the re-using of existing vocabs for Wikidata entry for Art × Science International took 9.059906005859375e-06s
Believability | Calculation of trust value for Wikidata entry for Art × Science International took 1.1205673217773438e-05s
INFO | --- Analysis for artxscienceinternational-wikidata took 879.403044462204s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 3.2058675289154053s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0006601810455322266s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.30091285705566406s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.02127385139465332s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 7.987022399902344e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.3589859008789062e-05s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 12.100623369216919s
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.183854579925537s
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.0005671977996826172s
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.28617405891418457s
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.020371675491333008s
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.1444091796875e-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.0007379055023193359s
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.3828277587890625e-05s
INFO | --- Analysis for ASCDC-AS-NTUE-School-Art-Textbooks took 10.468974113464355s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.193389654159546s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0006864070892333984s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.28429484367370605s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.020605802536010742s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 9.34600830078125e-05s
Believability | Calculation of trust value for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.1920928955078125e-05s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 11.445568323135376s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.176957368850708s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.0007541179656982422s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 0.29427599906921387s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.020641565322875977s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 5.1021575927734375e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 1.430511474609375e-05s
INFO | --- Analysis for ASCDC-CRB took 13.460276365280151s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.194944381713867s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0007214546203613281s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.2861754894256592s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.020493268966674805s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.250640869140625e-05s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.5367431640625e-06s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 11.00321650505066s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.1934216022491455s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.0006558895111083984s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 0.2855570316314697s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.0206451416015625s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 4.0531158447265625e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 1.1444091796875e-05s
INFO | --- Analysis for ASCDC-DQOT took 12.021823167800903s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.159623622894287s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0007050037384033203s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.3053872585296631s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.020824432373046875s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 8.416175842285156e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 8.821487426757812e-06s
INFO | --- Analysis for ASCDC-IHP-WCD took 12.004135847091675s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 2.90995454788208s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.0006954669952392578s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 0.3391716480255127s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.020596742630004883s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 8.273124694824219e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 1.2874603271484375e-05s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 14.202357769012451s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.1728222370147705s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0006661415100097656s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.29231786727905273s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.02059340476989746s
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.2874603271484375e-05s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 5.984306335449219e-05s
Believability | Calculation of trust value for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 1.5020370483398438e-05s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 11.087503671646118s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.171189069747925s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.28365230560302734s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.020795345306396484s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 5.888938903808594e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.3113021850585938e-05s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 10.893779516220093s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 3.875361442565918s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.00061798095703125s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.2810957431793213s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.020710229873657227s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 5.245208740234375e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.3828277587890625e-05s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 15.309511423110962s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.17207670211792s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0013756752014160156s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.30387163162231445s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.02198004722595215s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 7.963180541992188e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.3828277587890625e-05s
INFO | --- Analysis for ASCDC-Tibetan-Audio-Archive took 10.557877779006958s
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.1704440116882324s
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.00072479248046875s
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.28406214714050293s
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.020657777786254883s
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.2159347534179688e-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.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 8.487701416015625e-05s
Believability | Calculation of trust value for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 1.3113021850585938e-05s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 12.006133794784546s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 2.1633732318878174s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 0.3000202178955078s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.020768404006958008s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 5.1021575927734375e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 1.4066696166992188e-05s
INFO | --- Analysis for ASCDC_-_DNB took 10.552122116088867s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 4.7206878662109375e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 0.0015015602111816406s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 0.30735158920288086s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.020737171173095703s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 7.009506225585938e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 1.3589859008789062e-05s
INFO | --- Analysis for asit took 8.01306700706482s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 4.76837158203125e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.0007014274597167969s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.2791726589202881s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.020856142044067383s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 5.054473876953125e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 1.3589859008789062e-05s
INFO | --- Analysis for asjp took 5.8403894901275635s
Availability | SPARQL endpoint availability check for ASN:US took 2.2281882762908936s
Availability | VoID file availability check for ASN:US took 0.0005388259887695312s
Completeness | Calculation of interlinking completeness for ASN:US took 0.28872227668762207s
Reputation | Calculation of the PageRank for ASN:US took 0.022347450256347656s
Interlinking | Calculation of Degree of Connection for ASN:US took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ASN:US took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for ASN:US took 7.224082946777344e-05s
Believability | Calculation of trust value for ASN:US took 1.1205673217773438e-05s
INFO | --- Analysis for asn-us took 12.766895771026611s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 5.507469177246094e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.0006918907165527344s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.2986776828765869s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.020865440368652344s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 3.337860107421875e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 6.198883056640625e-06s
INFO | --- Analysis for aspire-mmu took 4.77757716178894s
Availability | SPARQL endpoint availability check for associations took 4.673004150390625e-05s
Availability | VoID file availability check for associations took 0.0007832050323486328s
Completeness | Calculation of interlinking completeness for associations took 0.300736665725708s
Reputation | Calculation of the PageRank for associations took 0.020522356033325195s
Interlinking | Calculation of Degree of Connection for associations took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for associations took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for associations took 7.390975952148438e-05s
Believability | Calculation of trust value for associations took 1.430511474609375e-05s
INFO | --- Analysis for associations took 7.689505100250244s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 9.34600830078125e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.0006270408630371094s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 0.2813405990600586s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.022603273391723633s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 0.00012683868408203125s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 1.4066696166992188e-05s
INFO | --- Analysis for athelia-rfid took 6.655116558074951s
Availability | SPARQL endpoint availability check for Augustini Confessiones in LiLa took 0.5704655647277832s
Availability | VoID file availability check for Augustini Confessiones in LiLa took 0.0007035732269287109s
Completeness | Calculation of interlinking completeness for Augustini Confessiones in LiLa took 0.3125803470611572s
Reputation | Calculation of the PageRank for Augustini Confessiones in LiLa took 0.02240753173828125s
Interlinking | Calculation of Degree of Connection for Augustini Confessiones in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Augustini Confessiones in LiLa took 0.0007784366607666016s
Interlinking | Calculation of Clustering coefficient for Augustini Confessiones in LiLa took 5.555152893066406e-05s
Believability | Calculation of trust value for Augustini Confessiones in LiLa took 1.33514404296875e-05s
INFO | --- Analysis for AugustiniConfessiones took 4.201838493347168s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 0.4836292266845703s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.0006644725799560547s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.2820007801055908s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.023006677627563477s
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.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 9.775161743164062e-05s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 1.33514404296875e-05s
INFO | --- Analysis for austrian_ski_racers took 3.8221235275268555s
Availability | SPARQL endpoint availability check for AVsOnto took 9.632110595703125e-05s
Availability | VoID file availability check for AVsOnto took 0.00067138671875s
Completeness | Calculation of interlinking completeness for AVsOnto took 0.28181004524230957s
Reputation | Calculation of the PageRank for AVsOnto took 0.023442506790161133s
Interlinking | Calculation of Degree of Connection for AVsOnto took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for AVsOnto took 0.0011284351348876953s
Interlinking | Calculation of Clustering coefficient for AVsOnto took 4.4345855712890625e-05s
Believability | Calculation of trust value for AVsOnto took 1.430511474609375e-05s
INFO | --- Analysis for AVsOnto took 3.4404852390289307s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.23112893104553223s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0005762577056884766s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 292.148948431015s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.4969518184661865s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0621943473816s
Interoperability | New terms check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 254.19634914398193s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0848157405853s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0895597934723s
Security | Check HTTPS for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.22585773468017578s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.21385931968688965s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12938261032104492s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0896763801574707s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 55.424736976623535s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.06753730773926s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1359233856201172s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 233.25996160507202s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2742955684661865s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.13414764404296875s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10672307014465332s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1292130947113037s
Performance | Throughput check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.399129390716553s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 6.198883056640625e-05s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10231447219848633s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.03845977783203s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.16026520729064941s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12154150009155273s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.15335369110107422s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2560250759124756s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.25647664070129395s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1422.9078743457794s
Interoperability | New vocabularies check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1780402660369873s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 12.230220556259155s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.2814669609069824s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 5.016781330108643s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.17264723777770996s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.1577482223511s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 23.099985361099243s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.124291181564331s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 301.6872799396515s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.85734486579895s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2957470417022705s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.135927677154541s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.7414476871490479s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.02306962013244629s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0010569095611572266s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 9.751319885253906e-05s
Interoperability | Check the re-using of existing vocabs for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.1457672119140625e-06s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.0967254638671875e-05s
INFO | --- Analysis for b3kat took 5072.955813407898s
Availability | SPARQL endpoint availability check for BabelNet took 0.46813225746154785s
Availability | VoID file availability check for BabelNet took 0.0007162094116210938s
Completeness | Calculation of interlinking completeness for BabelNet took 0.27988457679748535s
Reputation | Calculation of the PageRank for BabelNet took 0.02102494239807129s
Interlinking | Calculation of Degree of Connection for BabelNet took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for BabelNet took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.0001678466796875s
Believability | Calculation of trust value for BabelNet took 1.33514404296875e-05s
INFO | --- Analysis for babelnet took 4.640340805053711s
Availability | SPARQL endpoint availability check for Bacevicius.lt took 9.298324584960938e-05s
Availability | VoID file availability check for Bacevicius.lt took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for Bacevicius.lt took 0.2783195972442627s
Reputation | Calculation of the PageRank for Bacevicius.lt took 0.020708799362182617s
Interlinking | Calculation of Degree of Connection for Bacevicius.lt took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bacevicius.lt took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Bacevicius.lt took 3.4809112548828125e-05s
Believability | Calculation of trust value for Bacevicius.lt took 1.4066696166992188e-05s
INFO | --- Analysis for Bacevicius.lt took 2.600834846496582s
Availability | SPARQL endpoint availability check for Basisregistratie Adressen en Gebouwen took 0.46283626556396484s
Availability | VoID file availability check for Basisregistratie Adressen en Gebouwen took 0.000812530517578125s
Completeness | Calculation of interlinking completeness for Basisregistratie Adressen en Gebouwen took 0.27222514152526855s
Reputation | Calculation of the PageRank for Basisregistratie Adressen en Gebouwen took 0.021877050399780273s
Interlinking | Calculation of Degree of Connection for Basisregistratie Adressen en Gebouwen took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Basisregistratie Adressen en Gebouwen took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Basisregistratie Adressen en Gebouwen took 5.173683166503906e-05s
Believability | Calculation of trust value for Basisregistratie Adressen en Gebouwen took 9.775161743164062e-06s
INFO | --- Analysis for bag took 4.133906364440918s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 2.1537575721740723s
Availability | VoID file availability check for 红色经典歌曲 took 0.0006120204925537109s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.2713348865509033s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020979642868041992s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007953643798828125s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.7670135498046875e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.4066696166992188e-05s
INFO | --- Analysis for baixue took 4.785447835922241s
Availability | SPARQL endpoint availability check for baixue composer took 4.553794860839844e-05s
Availability | VoID file availability check for baixue composer took 0.0006077289581298828s
Completeness | Calculation of interlinking completeness for baixue composer took 0.305600643157959s
Reputation | Calculation of the PageRank for baixue composer took 0.020572423934936523s
Interlinking | Calculation of Degree of Connection for baixue composer took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for baixue composer took 0.0008080005645751953s
Interlinking | Calculation of Clustering coefficient for baixue composer took 4.076957702636719e-05s
Believability | Calculation of trust value for baixue composer took 1.3113021850585938e-05s
INFO | --- Analysis for baixue_composer took 3.026298999786377s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 9.655952453613281e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0007338523864746094s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.28928375244140625s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020665407180786133s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.457069396972656e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.430511474609375e-05s
INFO | --- Analysis for baixue_imagery took 3.1121108531951904s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 0.000102996826171875s
Availability | VoID file availability check for 红色经典歌曲 took 0.00066375732421875s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.296297550201416s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020621061325073242s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.409385681152344e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.430511474609375e-05s
INFO | --- Analysis for baixue_imagery1 took 4.351982355117798s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 9.417533874511719e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.0006735324859619141s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 0.2799108028411865s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.020763397216796875s
Interlinking | Calculation of Degree of Connection for Basque EuroWordNet-lemon lexicon (3.0) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Basque EuroWordNet-lemon lexicon (3.0) took 0.000804901123046875s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 4.601478576660156e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 9.775161743164062e-06s
INFO | --- Analysis for basque-eurowordnet-lemon-lexicon-3-0 took 3.0709080696105957s
Availability | SPARQL endpoint availability check for BBC Music took 0.2778201103210449s
Availability | VoID file availability check for BBC Music took 0.0006906986236572266s
Completeness | Calculation of interlinking completeness for BBC Music took 0.30536603927612305s
Reputation | Calculation of the PageRank for BBC Music took 0.020573139190673828s
Interlinking | Calculation of Degree of Connection for BBC Music took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for BBC Music took 0.0008029937744140625s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.00013327598571777344s
Believability | Calculation of trust value for BBC Music took 1.3113021850585938e-05s
INFO | --- Analysis for bbc-music took 3.4762861728668213s
Availability | SPARQL endpoint availability check for BBC Programmes took 0.3223233222961426s
Availability | VoID file availability check for BBC Programmes took 0.0006310939788818359s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.3067450523376465s
Reputation | Calculation of the PageRank for BBC Programmes took 0.021048307418823242s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 0.0001125335693359375s
Believability | Calculation of trust value for BBC Programmes took 1.4066696166992188e-05s
INFO | --- Analysis for bbc-programmes took 12.074089288711548s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.23474979400634766s
Availability | VoID file availability check for BBC Wildlife Finder took 0.0006792545318603516s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 0.28479671478271484s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.02122664451599121s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 0.00010585784912109375s
Believability | Calculation of trust value for BBC Wildlife Finder took 1.0967254638671875e-05s
INFO | --- Analysis for bbc-wildlife-finder took 9.41699481010437s
Availability | SPARQL endpoint availability check for BBOP took 0.0001266002655029297s
Availability | VoID file availability check for BBOP took 0.0008804798126220703s
Completeness | Calculation of interlinking completeness for BBOP took 0.2882082462310791s
Reputation | Calculation of the PageRank for BBOP took 0.02074575424194336s
Interlinking | Calculation of Degree of Connection for BBOP took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.552436828613281e-05s
Believability | Calculation of trust value for BBOP took 1.33514404296875e-05s
INFO | --- Analysis for bbop-selected took 20.020487308502197s
Availability | SPARQL endpoint availability check for Bdgp took 1.0525479316711426s
Availability | VoID file availability check for Bdgp took 0.0003733634948730469s
Completeness | Calculation of interlinking completeness for Bdgp took 0.27736401557922363s
Reputation | Calculation of the PageRank for Bdgp took 0.0213778018951416s
Interlinking | Calculation of Degree of Connection for Bdgp took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bdgp took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Bdgp took 3.743171691894531e-05s
Believability | Calculation of trust value for Bdgp took 1.33514404296875e-05s
INFO | --- Analysis for bdgp took 4.783882141113281s
Availability | SPARQL endpoint availability check for Bendev Junior took 4.673004150390625e-05s
Availability | VoID file availability check for Bendev Junior took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for Bendev Junior took 0.27257728576660156s
Reputation | Calculation of the PageRank for Bendev Junior took 0.022522449493408203s
Interlinking | Calculation of Degree of Connection for Bendev Junior took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Bendev Junior took 0.0008299350738525391s
Interlinking | Calculation of Clustering coefficient for Bendev Junior took 3.62396240234375e-05s
Believability | Calculation of trust value for Bendev Junior took 1.4066696166992188e-05s
INFO | --- Analysis for bendevoficial took 3.6009292602539062s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 9.051260948181152s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.0006842613220214844s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.30058908462524414s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.020874738693237305s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 8.273124694824219e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 1.0013580322265625e-05s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 22.463191986083984s
Availability | SPARQL endpoint availability check for berlios took 8.988380432128906e-05s
Availability | VoID file availability check for berlios took 0.0005931854248046875s
Completeness | Calculation of interlinking completeness for berlios took 0.28679633140563965s
Reputation | Calculation of the PageRank for berlios took 0.02100825309753418s
Interlinking | Calculation of Degree of Connection for berlios took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for berlios took 0.0008137226104736328s
Interlinking | Calculation of Clustering coefficient for berlios took 0.00010275840759277344s
Believability | Calculation of trust value for berlios took 1.4781951904296875e-05s
INFO | --- Analysis for berlios took 2.9991209506988525s
Availability | SPARQL endpoint availability check for Between Our Worlds took 4.76837158203125e-05s
Availability | VoID file availability check for Between Our Worlds took 0.0005867481231689453s
Completeness | Calculation of interlinking completeness for Between Our Worlds took 0.345609188079834s
Reputation | Calculation of the PageRank for Between Our Worlds took 0.020476341247558594s
Interlinking | Calculation of Degree of Connection for Between Our Worlds took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Between Our Worlds took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for Between Our Worlds took 7.390975952148438e-05s
Believability | Calculation of trust value for Between Our Worlds took 1.3828277587890625e-05s
INFO | --- Analysis for betweenourworlds took 9.04493236541748s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.22889018058776855s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0007846355438232422s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.26741981506347656s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.02048206329345703s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.1552734375e-05s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.0013580322265625e-05s
INFO | --- Analysis for bfs-linked-data took 2.879503011703491s
Availability | SPARQL endpoint availability check for BibBase took 0.06798171997070312s
Availability | VoID file availability check for BibBase took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for BibBase took 0.2647843360900879s
Reputation | Calculation of the PageRank for BibBase took 0.020960092544555664s
Interlinking | Calculation of Degree of Connection for BibBase took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for BibBase took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for BibBase took 0.0001010894775390625s
Believability | Calculation of trust value for BibBase took 1.4781951904296875e-05s
INFO | --- Analysis for bibbase took 2.578547477722168s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 5.269050598144531e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.0008258819580078125s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.3101072311401367s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.020936250686645508s
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.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 0.00010561943054199219s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 1.239776611328125e-05s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 9.488701343536377s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 9.202957153320312e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.0006144046783447266s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.27030491828918457s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.02100539207458496s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 0.00010752677917480469s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 1.4543533325195312e-05s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 9.16336965560913s
Availability | SPARQL endpoint availability check for BibSonomy - The blue social bookmark and publication sharing system. took 4.57763671875e-05s
Availability | VoID file availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.0007042884826660156s
Completeness | Calculation of interlinking completeness for BibSonomy - The blue social bookmark and publication sharing system. took 0.2724642753601074s
Reputation | Calculation of the PageRank for BibSonomy - The blue social bookmark and publication sharing system. took 0.021759986877441406s
Interlinking | Calculation of Degree of Connection for BibSonomy - The blue social bookmark and publication sharing system. took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for BibSonomy - The blue social bookmark and publication sharing system. took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for BibSonomy - The blue social bookmark and publication sharing system. took 4.315376281738281e-05s
Believability | Calculation of trust value for BibSonomy - The blue social bookmark and publication sharing system. took 1.4543533325195312e-05s
INFO | --- Analysis for BibSonomy took 8.957857131958008s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 8.797645568847656e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.0004360675811767578s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.2876319885253906s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.02102041244506836s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0007948875427246094s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 4.315376281738281e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 1.4781951904296875e-05s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 9.677761316299438s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 9.250640869140625e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.0006701946258544922s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 0.26447606086730957s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.020451068878173828s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2010 took 3.3855438232421875e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2010 took 1.3113021850585938e-05s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 2.9355902671813965s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 1.8751170635223389s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.0006642341613769531s
Extra | Recovery of all triples for Bio2RDF::Affymetrix took 20.48937463760376s
Performance | Total latancy measurement for Bio2RDF::Affymetrix took 0.5261921882629395s
Amount of data | Number of triples check for Bio2RDF::Affymetrix took 46.358354568481445s
Interoperability | New terms check for Bio2RDF::Affymetrix took 42.91398596763611s
Versatility | Languages check for Bio2RDF::Affymetrix took 60.11653733253479s
Interpretability | Number of blank nodes check for Bio2RDF::Affymetrix took 0.14349818229675293s
Interpretability | RDF structures check for Bio2RDF::Affymetrix took 0.7575483322143555s
Versatility | Serialization formats check for Bio2RDF::Affymetrix took 0.17861223220825195s
Availability | RDF dump link check for Bio2RDF::Affymetrix took 2.102839231491089s
License | MR license check for Bio2RDF::Affymetrix took 0.35852980613708496s
License | HR license check for Bio2RDF::Affymetrix took 60.103883504867554s
Amount of data | Number of property check for Bio2RDF::Affymetrix took 0.13447976112365723s
Understandability | Number of label check for Bio2RDF::Affymetrix took 9.760764360427856s
Understandability | URI regex check for Bio2RDF::Affymetrix took 0.4019958972930908s
Understandability | Vocabs check for Bio2RDF::Affymetrix took 0.13450288772583008s
Verifiability | Authors check for Bio2RDF::Affymetrix took 0.12703800201416016s
Verifiability | Publishers check for Bio2RDF::Affymetrix took 0.13722777366638184s
Performance | Throughput check for Bio2RDF::Affymetrix took 10.695968627929688s
Amount of data | Check the number of entities for Bio2RDF::Affymetrix took 85.95051741600037s
Verifiability | Contribs. check for Bio2RDF::Affymetrix took 0.4405357837677002s
Interlinking | sameAs chians check for Bio2RDF::Affymetrix took 0.24853205680847168s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.812124490737915s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.2229459285736084s
Timeliness | dataset update frequency check for Bio2RDF::Affymetrix took 0.10229873657226562s
Currency | Creation date check for Bio2RDF::Affymetrix took 0.2643880844116211s
Currency | Modification date check for Bio2RDF::Affymetrix took 0.22943615913391113s
Rep.Conc. | URIs length for Bio2RDF::Affymetrix took 109.380619764328s
Interoperability | New vocabularies check for Bio2RDF::Affymetrix took 25.173237562179565s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Affymetrix took 0.3307483196258545s
Accuracy | Check Functional Property for Bio2RDF::Affymetrix took 0.17422842979431152s
Accuracy | Check Inverse Functional Property for Bio2RDF::Affymetrix took 0.11726117134094238s
Accuracy | Check Empty annotation labels for Bio2RDF::Affymetrix took 6.915225982666016s
Accuracy | Check White space in annotation for Bio2RDF::Affymetrix took 0.9019627571105957s
Accuracy | Check Datatype consistency for Bio2RDF::Affymetrix took 0.6954951286315918s
Consistency | Disjoint class check for Bio2RDF::Affymetrix took 0.2839775085449219s
Consistency | Check Misplaced properties for Bio2RDF::Affymetrix took 65.04706883430481s
Consistency | Misplaced classes for Bio2RDF::Affymetrix took 2.3817522525787354s
Consistency | Check Ontology hijacking for Bio2RDF::Affymetrix took 6.286395788192749s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Affymetrix took 1.4463098049163818s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Affymetrix took 61.52452039718628s
Conciseness | Check Extensional conciseness for Bio2RDF::Affymetrix took 0.7223689556121826s
Conciseness | Check Intensional conciseness for Bio2RDF::Affymetrix took 0.337414026260376s
Security | Sign check for Bio2RDF::Affymetrix took 0.11504125595092773s
Availability | Check URIs Dereferenciability for Bio2RDF::Affymetrix took 10.490498542785645s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 0.3754112720489502s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.020856142044067383s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 0.00011038780212402344s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Affymetrix took 35.65389966964722s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 1.430511474609375e-05s
INFO | --- Analysis for bio2rdf-affymetrix took 1080.8901703357697s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 0.5097367763519287s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.0007977485656738281s
Extra | Recovery of all triples for Bio2RDF::Biomodels took 18.722500801086426s
Performance | Total latancy measurement for Bio2RDF::Biomodels took 1.2652206420898438s
Amount of data | Number of triples check for Bio2RDF::Biomodels took 44.86396884918213s
Interoperability | New terms check for Bio2RDF::Biomodels took 42.02882170677185s
Versatility | Languages check for Bio2RDF::Biomodels took 60.25423765182495s
Interpretability | Number of blank nodes check for Bio2RDF::Biomodels took 0.28144359588623047s
Security | Check HTTPS for Bio2RDF::Biomodels took 0.17098259925842285s
Interpretability | RDF structures check for Bio2RDF::Biomodels took 1.138113021850586s
Versatility | Serialization formats check for Bio2RDF::Biomodels took 0.3410460948944092s
Availability | RDF dump link check for Bio2RDF::Biomodels took 2.0502967834472656s
License | MR license check for Bio2RDF::Biomodels took 0.554344892501831s
License | HR license check for Bio2RDF::Biomodels took 60.23963379859924s
Amount of data | Number of property check for Bio2RDF::Biomodels took 0.2816615104675293s
Understandability | Number of label check for Bio2RDF::Biomodels took 9.938743352890015s
Understandability | URI regex check for Bio2RDF::Biomodels took 0.5643491744995117s
Understandability | Vocabs check for Bio2RDF::Biomodels took 0.2632756233215332s
Verifiability | Authors check for Bio2RDF::Biomodels took 0.25022387504577637s
Verifiability | Publishers check for Bio2RDF::Biomodels took 0.24612069129943848s
Performance | Throughput check for Bio2RDF::Biomodels took 11.27624225616455s
Amount of data | Check the number of entities for Bio2RDF::Biomodels took 86.77185416221619s
Verifiability | Contribs. check for Bio2RDF::Biomodels took 0.590935230255127s
Interlinking | sameAs chians check for Bio2RDF::Biomodels took 0.3711850643157959s
Interlinking | skos check for Bio2RDF::Biomodels took 0.8367810249328613s
Interlinking | skos check for Bio2RDF::Biomodels took 0.4125838279724121s
Timeliness | dataset update frequency check for Bio2RDF::Biomodels took 0.25023841857910156s
Currency | Creation date check for Bio2RDF::Biomodels took 0.5189201831817627s
Currency | Modification date check for Bio2RDF::Biomodels took 0.5332517623901367s
Rep.Conc. | URIs length for Bio2RDF::Biomodels took 111.66666197776794s
Interoperability | New vocabularies check for Bio2RDF::Biomodels took 26.13037133216858s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Biomodels took 0.43148207664489746s
Accuracy | Check Functional Property for Bio2RDF::Biomodels took 0.307422399520874s
Accuracy | Check Inverse Functional Property for Bio2RDF::Biomodels took 0.29622983932495117s
Accuracy | Check Empty annotation labels for Bio2RDF::Biomodels took 7.484389781951904s
Accuracy | Check White space in annotation for Bio2RDF::Biomodels took 0.907294511795044s
Accuracy | Check Datatype consistency for Bio2RDF::Biomodels took 0.7170145511627197s
Consistency | Disjoint class check for Bio2RDF::Biomodels took 0.42531585693359375s
Consistency | Check Misplaced properties for Bio2RDF::Biomodels took 65.63290238380432s
Consistency | Misplaced classes for Bio2RDF::Biomodels took 2.4937055110931396s
Consistency | Check Ontology hijacking for Bio2RDF::Biomodels took 6.567720890045166s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Biomodels took 1.4324829578399658s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Biomodels took 61.69376468658447s
Conciseness | Check Extensional conciseness for Bio2RDF::Biomodels took 0.7255494594573975s
Conciseness | Check Intensional conciseness for Bio2RDF::Biomodels took 0.45339369773864746s
Security | Sign check for Bio2RDF::Biomodels took 0.273115873336792s
Availability | Check URIs Dereferenciability for Bio2RDF::Biomodels took 9.107317447662354s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 0.43154239654541016s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.020828962326049805s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.00012063980102539062s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Biomodels took 27.83432674407959s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 1.5735626220703125e-05s
INFO | --- Analysis for bio2rdf-biomodels took 1078.801662683487s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 0.49936461448669434s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.0006620883941650391s
Extra | Recovery of all triples for Bio2RDF::Bioportal took 19.270498514175415s
Performance | Total latancy measurement for Bio2RDF::Bioportal took 1.2632720470428467s
Amount of data | Number of triples check for Bio2RDF::Bioportal took 45.070760011672974s
Interoperability | New terms check for Bio2RDF::Bioportal took 42.21251320838928s
Versatility | Languages check for Bio2RDF::Bioportal took 60.24422359466553s
Interpretability | Number of blank nodes check for Bio2RDF::Bioportal took 0.2563440799713135s
Security | Check HTTPS for Bio2RDF::Bioportal took 0.14391112327575684s
Interpretability | RDF structures check for Bio2RDF::Bioportal took 0.9047009944915771s
Versatility | Serialization formats check for Bio2RDF::Bioportal took 0.31693506240844727s
Availability | RDF dump link check for Bio2RDF::Bioportal took 2.1815905570983887s
License | MR license check for Bio2RDF::Bioportal took 0.5153553485870361s
License | HR license check for Bio2RDF::Bioportal took 60.242308616638184s
Amount of data | Number of property check for Bio2RDF::Bioportal took 0.2560431957244873s
Understandability | Number of label check for Bio2RDF::Bioportal took 10.129099369049072s
Understandability | URI regex check for Bio2RDF::Bioportal took 0.582503080368042s
Understandability | Vocabs check for Bio2RDF::Bioportal took 0.2558896541595459s
Verifiability | Authors check for Bio2RDF::Bioportal took 0.26900506019592285s
Verifiability | Publishers check for Bio2RDF::Bioportal took 0.25481414794921875s
Performance | Throughput check for Bio2RDF::Bioportal took 11.148383378982544s
Amount of data | Check the number of entities for Bio2RDF::Bioportal took 86.86563658714294s
Verifiability | Contribs. check for Bio2RDF::Bioportal took 0.6053130626678467s
Interlinking | sameAs chians check for Bio2RDF::Bioportal took 0.3854525089263916s
Interlinking | skos check for Bio2RDF::Bioportal took 0.8502535820007324s
Interlinking | skos check for Bio2RDF::Bioportal took 0.34875035285949707s
Timeliness | dataset update frequency check for Bio2RDF::Bioportal took 0.26907825469970703s
Currency | Creation date check for Bio2RDF::Bioportal took 0.49631643295288086s
Currency | Modification date check for Bio2RDF::Bioportal took 0.5271439552307129s
Rep.Conc. | URIs length for Bio2RDF::Bioportal took 107.92615914344788s
Interoperability | New vocabularies check for Bio2RDF::Bioportal took 33.31739377975464s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Bioportal took 0.41988348960876465s
Accuracy | Check Functional Property for Bio2RDF::Bioportal took 0.27570462226867676s
Accuracy | Check Inverse Functional Property for Bio2RDF::Bioportal took 0.2748279571533203s
Accuracy | Check Empty annotation labels for Bio2RDF::Bioportal took 7.012854099273682s
Accuracy | Check White space in annotation for Bio2RDF::Bioportal took 0.9001145362854004s
Accuracy | Check Datatype consistency for Bio2RDF::Bioportal took 0.7291343212127686s
Consistency | Disjoint class check for Bio2RDF::Bioportal took 0.4001643657684326s
Consistency | Check Misplaced properties for Bio2RDF::Bioportal took 65.25275588035583s
Consistency | Misplaced classes for Bio2RDF::Bioportal took 2.48673677444458s
Consistency | Check Ontology hijacking for Bio2RDF::Bioportal took 6.925016641616821s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Bioportal took 1.4418139457702637s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Bioportal took 61.68264842033386s
Conciseness | Check Extensional conciseness for Bio2RDF::Bioportal took 0.7369832992553711s
Conciseness | Check Intensional conciseness for Bio2RDF::Bioportal took 0.43913960456848145s
Security | Sign check for Bio2RDF::Bioportal took 0.2778501510620117s
Availability | Check URIs Dereferenciability for Bio2RDF::Bioportal took 9.91608452796936s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 0.43138909339904785s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.020802974700927734s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.0004639625549316406s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Bioportal took 28.31986689567566s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 1.5020370483398438e-05s
INFO | --- Analysis for bio2rdf-bioportal took 1092.8541371822357s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 0.13570284843444824s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.0007729530334472656s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 0.2900266647338867s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.020780563354492188s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 6.008148193359375e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 1.3589859008789062e-05s
INFO | --- Analysis for bio2rdf-chembl took 16.342728853225708s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 0.4740159511566162s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.0006258487701416016s
Extra | Recovery of all triples for Bio2RDF::Clinicaltrials took 18.31300687789917s
Performance | Total latancy measurement for Bio2RDF::Clinicaltrials took 1.2601072788238525s
Amount of data | Number of triples check for Bio2RDF::Clinicaltrials took 45.49563193321228s
Interoperability | New terms check for Bio2RDF::Clinicaltrials took 41.496269941329956s
Versatility | Languages check for Bio2RDF::Clinicaltrials took 60.2473783493042s
Interpretability | Number of blank nodes check for Bio2RDF::Clinicaltrials took 0.27521562576293945s
Security | Check HTTPS for Bio2RDF::Clinicaltrials took 0.1430649757385254s
Interpretability | RDF structures check for Bio2RDF::Clinicaltrials took 1.0170588493347168s
Versatility | Serialization formats check for Bio2RDF::Clinicaltrials took 0.31770944595336914s
Availability | RDF dump link check for Bio2RDF::Clinicaltrials took 2.1516759395599365s
License | MR license check for Bio2RDF::Clinicaltrials took 0.5458247661590576s
License | HR license check for Bio2RDF::Clinicaltrials took 60.24035096168518s
Amount of data | Number of property check for Bio2RDF::Clinicaltrials took 0.24010491371154785s
Understandability | Number of label check for Bio2RDF::Clinicaltrials took 9.922130346298218s
Understandability | URI regex check for Bio2RDF::Clinicaltrials took 0.592876672744751s
Understandability | Vocabs check for Bio2RDF::Clinicaltrials took 0.2521672248840332s
Verifiability | Authors check for Bio2RDF::Clinicaltrials took 0.2680017948150635s
Verifiability | Publishers check for Bio2RDF::Clinicaltrials took 0.2393631935119629s
Performance | Throughput check for Bio2RDF::Clinicaltrials took 11.271608829498291s
Amount of data | Check the number of entities for Bio2RDF::Clinicaltrials took 87.00575160980225s
Verifiability | Contribs. check for Bio2RDF::Clinicaltrials took 0.5700058937072754s
Interlinking | sameAs chians check for Bio2RDF::Clinicaltrials took 0.3789634704589844s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.924811601638794s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.3654203414916992s
Timeliness | dataset update frequency check for Bio2RDF::Clinicaltrials took 0.2602963447570801s
Currency | Creation date check for Bio2RDF::Clinicaltrials took 0.5144219398498535s
Currency | Modification date check for Bio2RDF::Clinicaltrials took 0.5555472373962402s
Rep.Conc. | URIs length for Bio2RDF::Clinicaltrials took 108.13603115081787s
Interoperability | New vocabularies check for Bio2RDF::Clinicaltrials took 29.0976083278656s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Clinicaltrials took 0.4268953800201416s
Accuracy | Check Functional Property for Bio2RDF::Clinicaltrials took 0.27120518684387207s
Accuracy | Check Inverse Functional Property for Bio2RDF::Clinicaltrials took 0.2975633144378662s
Accuracy | Check Empty annotation labels for Bio2RDF::Clinicaltrials took 6.867294788360596s
Accuracy | Check White space in annotation for Bio2RDF::Clinicaltrials took 0.8964328765869141s
Accuracy | Check Datatype consistency for Bio2RDF::Clinicaltrials took 0.7051763534545898s
Consistency | Disjoint class check for Bio2RDF::Clinicaltrials took 0.5493447780609131s
Consistency | Check Misplaced properties for Bio2RDF::Clinicaltrials took 64.96806573867798s
Consistency | Misplaced classes for Bio2RDF::Clinicaltrials took 2.5044875144958496s
Consistency | Check Ontology hijacking for Bio2RDF::Clinicaltrials took 6.962814092636108s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Clinicaltrials took 1.4320502281188965s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Clinicaltrials took 61.68153524398804s
Conciseness | Check Extensional conciseness for Bio2RDF::Clinicaltrials took 0.7229013442993164s
Conciseness | Check Intensional conciseness for Bio2RDF::Clinicaltrials took 0.48372697830200195s
Security | Sign check for Bio2RDF::Clinicaltrials took 0.2943723201751709s
Availability | Check URIs Dereferenciability for Bio2RDF::Clinicaltrials took 20.912904500961304s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 0.46569204330444336s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.021140575408935547s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 6.175041198730469e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Clinicaltrials took 24.439847469329834s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-clinicaltrials took 1088.4300365447998s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 0.4815196990966797s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.0006053447723388672s
Extra | Recovery of all triples for Bio2RDF::Ctd took 19.034533739089966s
Performance | Total latancy measurement for Bio2RDF::Ctd took 1.2775394916534424s
Amount of data | Number of triples check for Bio2RDF::Ctd took 45.95664167404175s
Interoperability | New terms check for Bio2RDF::Ctd took 41.356807231903076s
Versatility | Languages check for Bio2RDF::Ctd took 60.240617752075195s
Interpretability | Number of blank nodes check for Bio2RDF::Ctd took 0.2609291076660156s
Security | Check HTTPS for Bio2RDF::Ctd took 0.15928912162780762s
Interpretability | RDF structures check for Bio2RDF::Ctd took 0.6387908458709717s
Versatility | Serialization formats check for Bio2RDF::Ctd took 0.37050437927246094s
Availability | RDF dump link check for Bio2RDF::Ctd took 1.9585380554199219s
License | MR license check for Bio2RDF::Ctd took 0.5018260478973389s
License | HR license check for Bio2RDF::Ctd took 60.25410008430481s
Amount of data | Number of property check for Bio2RDF::Ctd took 0.2580690383911133s
Understandability | Number of label check for Bio2RDF::Ctd took 9.867311716079712s
Understandability | URI regex check for Bio2RDF::Ctd took 0.6134412288665771s
Understandability | Vocabs check for Bio2RDF::Ctd took 0.26675891876220703s
Verifiability | Authors check for Bio2RDF::Ctd took 0.28107142448425293s
Verifiability | Publishers check for Bio2RDF::Ctd took 0.2604808807373047s
Performance | Throughput check for Bio2RDF::Ctd took 10.848694801330566s
Amount of data | Check the number of entities for Bio2RDF::Ctd took 87.19432663917542s
Verifiability | Contribs. check for Bio2RDF::Ctd took 2.0372743606567383s
Interlinking | sameAs chians check for Bio2RDF::Ctd took 0.3832128047943115s
Interlinking | skos check for Bio2RDF::Ctd took 0.8786334991455078s
Interlinking | skos check for Bio2RDF::Ctd took 0.3485136032104492s
Timeliness | dataset update frequency check for Bio2RDF::Ctd took 0.2552032470703125s
Currency | Creation date check for Bio2RDF::Ctd took 0.5252180099487305s
Currency | Modification date check for Bio2RDF::Ctd took 0.5023183822631836s
Rep.Conc. | URIs length for Bio2RDF::Ctd took 109.86302733421326s
Interoperability | New vocabularies check for Bio2RDF::Ctd took 30.09630012512207s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ctd took 0.4116811752319336s
Accuracy | Check Functional Property for Bio2RDF::Ctd took 0.28598904609680176s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ctd took 0.294478178024292s
Accuracy | Check Empty annotation labels for Bio2RDF::Ctd took 7.702092885971069s
Accuracy | Check White space in annotation for Bio2RDF::Ctd took 0.8982880115509033s
Accuracy | Check Datatype consistency for Bio2RDF::Ctd took 0.695448637008667s
Consistency | Disjoint class check for Bio2RDF::Ctd took 0.40465354919433594s
Consistency | Check Misplaced properties for Bio2RDF::Ctd took 65.18789505958557s
Consistency | Misplaced classes for Bio2RDF::Ctd took 2.509500741958618s
Consistency | Check Ontology hijacking for Bio2RDF::Ctd took 6.624479293823242s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ctd took 1.4445793628692627s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ctd took 61.721216917037964s
Conciseness | Check Extensional conciseness for Bio2RDF::Ctd took 0.7245347499847412s
Conciseness | Check Intensional conciseness for Bio2RDF::Ctd took 0.4662461280822754s
Security | Sign check for Bio2RDF::Ctd took 0.28451108932495117s
Availability | Check URIs Dereferenciability for Bio2RDF::Ctd took 15.403172016143799s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 0.35946202278137207s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.020987510681152344s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 7.486343383789062e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ctd took 26.149085998535156s
Believability | Calculation of trust value for Bio2RDF::Ctd took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-ctd took 1096.8355491161346s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 4.744529724121094e-05s
Availability | VoID file availability check for bio2rdf-dataset took 0.0006575584411621094s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 0.31331706047058105s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.021982908248901367s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0008161067962646484s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 5.91278076171875e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 1.3828277587890625e-05s
INFO | --- Analysis for bio2rdf-dataset took 2.880218505859375s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 0.4836301803588867s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.0006425380706787109s
Extra | Recovery of all triples for Bio2RDF::Dbsnp took 19.351949214935303s
Performance | Total latancy measurement for Bio2RDF::Dbsnp took 1.3106300830841064s
Amount of data | Number of triples check for Bio2RDF::Dbsnp took 46.41589307785034s
Interoperability | New terms check for Bio2RDF::Dbsnp took 42.710498094558716s
Versatility | Languages check for Bio2RDF::Dbsnp took 60.23593878746033s
Interpretability | Number of blank nodes check for Bio2RDF::Dbsnp took 0.27507758140563965s
Security | Check HTTPS for Bio2RDF::Dbsnp took 0.15662336349487305s
Interpretability | RDF structures check for Bio2RDF::Dbsnp took 0.6923692226409912s
Versatility | Serialization formats check for Bio2RDF::Dbsnp took 0.3244030475616455s
Availability | RDF dump link check for Bio2RDF::Dbsnp took 2.1702418327331543s
License | MR license check for Bio2RDF::Dbsnp took 0.5091121196746826s
License | HR license check for Bio2RDF::Dbsnp took 60.25404405593872s
Amount of data | Number of property check for Bio2RDF::Dbsnp took 0.25881528854370117s
Understandability | Number of label check for Bio2RDF::Dbsnp took 9.710932731628418s
Understandability | URI regex check for Bio2RDF::Dbsnp took 0.6035583019256592s
Understandability | Vocabs check for Bio2RDF::Dbsnp took 0.2416093349456787s
Verifiability | Authors check for Bio2RDF::Dbsnp took 0.2753727436065674s
Verifiability | Publishers check for Bio2RDF::Dbsnp took 0.24267363548278809s
Performance | Throughput check for Bio2RDF::Dbsnp took 10.839676856994629s
Amount of data | Check the number of entities for Bio2RDF::Dbsnp took 86.46365022659302s
Verifiability | Contribs. check for Bio2RDF::Dbsnp took 0.5506181716918945s
Interlinking | sameAs chians check for Bio2RDF::Dbsnp took 0.3720426559448242s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.8507885932922363s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.38848137855529785s
Timeliness | dataset update frequency check for Bio2RDF::Dbsnp took 0.2695584297180176s
Currency | Creation date check for Bio2RDF::Dbsnp took 0.49997949600219727s
Currency | Modification date check for Bio2RDF::Dbsnp took 0.5079543590545654s
Rep.Conc. | URIs length for Bio2RDF::Dbsnp took 110.33181595802307s
Interoperability | New vocabularies check for Bio2RDF::Dbsnp took 29.18139934539795s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Dbsnp took 0.4264335632324219s
Accuracy | Check Functional Property for Bio2RDF::Dbsnp took 0.25925326347351074s
Accuracy | Check Inverse Functional Property for Bio2RDF::Dbsnp took 0.27222156524658203s
Accuracy | Check Empty annotation labels for Bio2RDF::Dbsnp took 7.41156268119812s
Accuracy | Check White space in annotation for Bio2RDF::Dbsnp took 0.8926777839660645s
Accuracy | Check Datatype consistency for Bio2RDF::Dbsnp took 0.6880373954772949s
Consistency | Disjoint class check for Bio2RDF::Dbsnp took 0.44354891777038574s
Consistency | Check Misplaced properties for Bio2RDF::Dbsnp took 65.19454383850098s
Consistency | Misplaced classes for Bio2RDF::Dbsnp took 2.4716360569000244s
Consistency | Check Ontology hijacking for Bio2RDF::Dbsnp took 6.686997652053833s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Dbsnp took 1.429792881011963s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Dbsnp took 61.691736698150635s
Conciseness | Check Extensional conciseness for Bio2RDF::Dbsnp took 0.7170748710632324s
Conciseness | Check Intensional conciseness for Bio2RDF::Dbsnp took 0.4279196262359619s
Security | Sign check for Bio2RDF::Dbsnp took 0.2665221691131592s
Availability | Check URIs Dereferenciability for Bio2RDF::Dbsnp took 9.772580623626709s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 0.4249885082244873s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.021346330642700195s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 8.821487426757812e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Dbsnp took 22.562929391860962s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 1.0013580322265625e-05s
INFO | --- Analysis for bio2rdf-dbsnp took 1077.6797490119934s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 0.4547603130340576s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.0008153915405273438s
Extra | Recovery of all triples for Bio2RDF::Drugbank took 19.003418922424316s
Performance | Total latancy measurement for Bio2RDF::Drugbank took 1.2492015361785889s
Amount of data | Number of triples check for Bio2RDF::Drugbank took 45.42002725601196s
Interoperability | New terms check for Bio2RDF::Drugbank took 41.086641788482666s
Versatility | Languages check for Bio2RDF::Drugbank took 60.23197817802429s
Interpretability | Number of blank nodes check for Bio2RDF::Drugbank took 0.27310943603515625s
Security | Check HTTPS for Bio2RDF::Drugbank took 0.15819692611694336s
Interpretability | RDF structures check for Bio2RDF::Drugbank took 0.6549217700958252s
Versatility | Serialization formats check for Bio2RDF::Drugbank took 0.3367886543273926s
Availability | RDF dump link check for Bio2RDF::Drugbank took 2.1378214359283447s
License | MR license check for Bio2RDF::Drugbank took 0.466888427734375s
License | HR license check for Bio2RDF::Drugbank took 60.25259828567505s
Amount of data | Number of property check for Bio2RDF::Drugbank took 0.2649650573730469s
Understandability | Number of label check for Bio2RDF::Drugbank took 9.944901943206787s
Understandability | URI regex check for Bio2RDF::Drugbank took 0.599297285079956s
Understandability | Vocabs check for Bio2RDF::Drugbank took 0.2775247097015381s
Verifiability | Authors check for Bio2RDF::Drugbank took 0.26580047607421875s
Verifiability | Publishers check for Bio2RDF::Drugbank took 0.2494344711303711s
Performance | Throughput check for Bio2RDF::Drugbank took 11.402061223983765s
Amount of data | Check the number of entities for Bio2RDF::Drugbank took 86.76444482803345s
Verifiability | Contribs. check for Bio2RDF::Drugbank took 0.591794490814209s
Interlinking | sameAs chians check for Bio2RDF::Drugbank took 0.36669087409973145s
Interlinking | skos check for Bio2RDF::Drugbank took 0.8040051460266113s
Interlinking | skos check for Bio2RDF::Drugbank took 0.3439302444458008s
Timeliness | dataset update frequency check for Bio2RDF::Drugbank took 0.2977886199951172s
Currency | Creation date check for Bio2RDF::Drugbank took 0.533334493637085s
Currency | Modification date check for Bio2RDF::Drugbank took 0.5001187324523926s
Rep.Conc. | URIs length for Bio2RDF::Drugbank took 110.86040949821472s
Interoperability | New vocabularies check for Bio2RDF::Drugbank took 39.392632722854614s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Drugbank took 0.4823899269104004s
Accuracy | Check Functional Property for Bio2RDF::Drugbank took 0.28171539306640625s
Accuracy | Check Inverse Functional Property for Bio2RDF::Drugbank took 0.2891578674316406s
Accuracy | Check Empty annotation labels for Bio2RDF::Drugbank took 7.292958498001099s
Accuracy | Check White space in annotation for Bio2RDF::Drugbank took 0.9076688289642334s
Accuracy | Check Datatype consistency for Bio2RDF::Drugbank took 0.700812816619873s
Consistency | Disjoint class check for Bio2RDF::Drugbank took 0.44710826873779297s
Consistency | Check Misplaced properties for Bio2RDF::Drugbank took 65.48371696472168s
Consistency | Misplaced classes for Bio2RDF::Drugbank took 2.4850406646728516s
Consistency | Check Ontology hijacking for Bio2RDF::Drugbank took 6.9755988121032715s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Drugbank took 1.4406230449676514s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Drugbank took 61.672139406204224s
Conciseness | Check Extensional conciseness for Bio2RDF::Drugbank took 0.7103099822998047s
Conciseness | Check Intensional conciseness for Bio2RDF::Drugbank took 0.6076533794403076s
Security | Sign check for Bio2RDF::Drugbank took 0.27439236640930176s
Availability | Check URIs Dereferenciability for Bio2RDF::Drugbank took 9.97192120552063s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 0.4882242679595947s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.020964622497558594s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.00011897087097167969s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Drugbank took 35.154393434524536s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 1.430511474609375e-05s
INFO | --- Analysis for bio2rdf-drugbank took 1105.8159501552582s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 0.4688148498535156s
Availability | VoID file availability check for Bio2RDF::Genage took 0.0007038116455078125s
Extra | Recovery of all triples for Bio2RDF::Genage took 18.74593210220337s
Performance | Total latancy measurement for Bio2RDF::Genage took 1.2701592445373535s
Amount of data | Number of triples check for Bio2RDF::Genage took 45.06833815574646s
Interoperability | New terms check for Bio2RDF::Genage took 41.801363706588745s
Versatility | Languages check for Bio2RDF::Genage took 60.26108241081238s
Interpretability | Number of blank nodes check for Bio2RDF::Genage took 0.2674875259399414s
Security | Check HTTPS for Bio2RDF::Genage took 0.15565872192382812s
Interpretability | RDF structures check for Bio2RDF::Genage took 0.7819030284881592s
Versatility | Serialization formats check for Bio2RDF::Genage took 0.3434290885925293s
Availability | RDF dump link check for Bio2RDF::Genage took 1.9331834316253662s
License | MR license check for Bio2RDF::Genage took 0.4937586784362793s
License | HR license check for Bio2RDF::Genage took 60.25126600265503s
Amount of data | Number of property check for Bio2RDF::Genage took 0.27107763290405273s
Understandability | Number of label check for Bio2RDF::Genage took 10.621746301651001s
Understandability | URI regex check for Bio2RDF::Genage took 0.5730834007263184s
Understandability | Vocabs check for Bio2RDF::Genage took 0.2460339069366455s
Verifiability | Authors check for Bio2RDF::Genage took 0.27366209030151367s
Verifiability | Publishers check for Bio2RDF::Genage took 0.27837038040161133s
Performance | Throughput check for Bio2RDF::Genage took 10.406068086624146s
Amount of data | Check the number of entities for Bio2RDF::Genage took 88.27026867866516s
Verifiability | Contribs. check for Bio2RDF::Genage took 0.7464396953582764s
Interlinking | sameAs chians check for Bio2RDF::Genage took 0.39129090309143066s
Interlinking | skos check for Bio2RDF::Genage took 0.8483426570892334s
Interlinking | skos check for Bio2RDF::Genage took 0.33791184425354004s
Timeliness | dataset update frequency check for Bio2RDF::Genage took 0.2629282474517822s
Currency | Creation date check for Bio2RDF::Genage took 0.5101702213287354s
Currency | Modification date check for Bio2RDF::Genage took 0.5115835666656494s
Rep.Conc. | URIs length for Bio2RDF::Genage took 108.4689552783966s
Interoperability | New vocabularies check for Bio2RDF::Genage took 35.10523223876953s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Genage took 0.43893861770629883s
Accuracy | Check Functional Property for Bio2RDF::Genage took 0.2873106002807617s
Accuracy | Check Inverse Functional Property for Bio2RDF::Genage took 0.28281354904174805s
Accuracy | Check Empty annotation labels for Bio2RDF::Genage took 7.7080371379852295s
Accuracy | Check White space in annotation for Bio2RDF::Genage took 0.8882906436920166s
Accuracy | Check Datatype consistency for Bio2RDF::Genage took 0.7035489082336426s
Consistency | Disjoint class check for Bio2RDF::Genage took 0.4204709529876709s
Consistency | Check Misplaced properties for Bio2RDF::Genage took 65.5344762802124s
Consistency | Misplaced classes for Bio2RDF::Genage took 2.5039432048797607s
Consistency | Check Ontology hijacking for Bio2RDF::Genage took 6.453485012054443s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Genage took 1.436492919921875s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Genage took 61.685059547424316s
Conciseness | Check Extensional conciseness for Bio2RDF::Genage took 0.7466652393341064s
Conciseness | Check Intensional conciseness for Bio2RDF::Genage took 0.4771120548248291s
Security | Sign check for Bio2RDF::Genage took 0.3011455535888672s
Availability | Check URIs Dereferenciability for Bio2RDF::Genage took 9.26096224784851s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 0.47254180908203125s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.020940542221069336s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 6.127357482910156e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Genage took 29.232507467269897s
Believability | Calculation of trust value for Bio2RDF::Genage took 1.049041748046875e-05s
INFO | --- Analysis for bio2rdf-genage took 1091.2329998016357s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 0.49610257148742676s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.0006735324859619141s
Extra | Recovery of all triples for Bio2RDF::Gendr took 18.348681926727295s
Performance | Total latancy measurement for Bio2RDF::Gendr took 1.2251102924346924s
Amount of data | Number of triples check for Bio2RDF::Gendr took 45.039064168930054s
Interoperability | New terms check for Bio2RDF::Gendr took 41.226653814315796s
Versatility | Languages check for Bio2RDF::Gendr took 60.24025201797485s
Interpretability | Number of blank nodes check for Bio2RDF::Gendr took 0.2595183849334717s
Security | Check HTTPS for Bio2RDF::Gendr took 0.14887452125549316s
Interpretability | RDF structures check for Bio2RDF::Gendr took 0.6353774070739746s
Versatility | Serialization formats check for Bio2RDF::Gendr took 0.3445594310760498s
Availability | RDF dump link check for Bio2RDF::Gendr took 2.2418696880340576s
License | MR license check for Bio2RDF::Gendr took 0.5241713523864746s
License | HR license check for Bio2RDF::Gendr took 60.233394145965576s
Amount of data | Number of property check for Bio2RDF::Gendr took 0.39853358268737793s
Understandability | Number of label check for Bio2RDF::Gendr took 10.813459634780884s
Understandability | URI regex check for Bio2RDF::Gendr took 0.6291580200195312s
Understandability | Vocabs check for Bio2RDF::Gendr took 0.26009178161621094s
Verifiability | Authors check for Bio2RDF::Gendr took 0.2674708366394043s
Verifiability | Publishers check for Bio2RDF::Gendr took 0.2576406002044678s
Performance | Throughput check for Bio2RDF::Gendr took 11.100869178771973s
Amount of data | Check the number of entities for Bio2RDF::Gendr took 89.06596517562866s
Verifiability | Contribs. check for Bio2RDF::Gendr took 0.5880031585693359s
Interlinking | sameAs chians check for Bio2RDF::Gendr took 0.3443751335144043s
Interlinking | skos check for Bio2RDF::Gendr took 0.7594413757324219s
Interlinking | skos check for Bio2RDF::Gendr took 0.33640336990356445s
Timeliness | dataset update frequency check for Bio2RDF::Gendr took 0.25660133361816406s
Currency | Creation date check for Bio2RDF::Gendr took 0.5184836387634277s
Currency | Modification date check for Bio2RDF::Gendr took 0.5260889530181885s
Rep.Conc. | URIs length for Bio2RDF::Gendr took 108.03849625587463s
Interoperability | New vocabularies check for Bio2RDF::Gendr took 23.16946291923523s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Gendr took 0.47705698013305664s
Accuracy | Check Functional Property for Bio2RDF::Gendr took 0.28803396224975586s
Accuracy | Check Inverse Functional Property for Bio2RDF::Gendr took 0.2886490821838379s
Accuracy | Check Empty annotation labels for Bio2RDF::Gendr took 8.796014547348022s
Accuracy | Check White space in annotation for Bio2RDF::Gendr took 0.9005312919616699s
Accuracy | Check Datatype consistency for Bio2RDF::Gendr took 0.7024736404418945s
Consistency | Disjoint class check for Bio2RDF::Gendr took 0.4128389358520508s
Consistency | Check Misplaced properties for Bio2RDF::Gendr took 67.26399230957031s
Consistency | Misplaced classes for Bio2RDF::Gendr took 2.4762444496154785s
Consistency | Check Ontology hijacking for Bio2RDF::Gendr took 6.429722547531128s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Gendr took 1.4302918910980225s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Gendr took 92.46433210372925s
Conciseness | Check Extensional conciseness for Bio2RDF::Gendr took 0.7459456920623779s
Conciseness | Check Intensional conciseness for Bio2RDF::Gendr took 0.8812756538391113s
Security | Sign check for Bio2RDF::Gendr took 0.2819399833679199s
Availability | Check URIs Dereferenciability for Bio2RDF::Gendr took 10.742397785186768s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 0.3247995376586914s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.021160125732421875s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 6.866455078125e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Gendr took 25.089938640594482s
Believability | Calculation of trust value for Bio2RDF::Gendr took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-gendr took 1109.0852279663086s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 0.6120500564575195s
Availability | VoID file availability check for Bio2RDF::Goa took 0.0007023811340332031s
Extra | Recovery of all triples for Bio2RDF::Goa took 18.714284658432007s
Performance | Total latancy measurement for Bio2RDF::Goa took 1.2812860012054443s
Amount of data | Number of triples check for Bio2RDF::Goa took 47.155768156051636s
Interoperability | New terms check for Bio2RDF::Goa took 40.83132743835449s
Versatility | Languages check for Bio2RDF::Goa took 60.27799201011658s
Interpretability | Number of blank nodes check for Bio2RDF::Goa took 0.28661108016967773s
Security | Check HTTPS for Bio2RDF::Goa took 0.16753387451171875s
Interpretability | RDF structures check for Bio2RDF::Goa took 0.7775535583496094s
Versatility | Serialization formats check for Bio2RDF::Goa took 0.33139777183532715s
Availability | RDF dump link check for Bio2RDF::Goa took 1.924527645111084s
License | MR license check for Bio2RDF::Goa took 0.47676515579223633s
License | HR license check for Bio2RDF::Goa took 60.23837161064148s
Amount of data | Number of property check for Bio2RDF::Goa took 0.24832463264465332s
Understandability | Number of label check for Bio2RDF::Goa took 10.720450639724731s
Understandability | URI regex check for Bio2RDF::Goa took 0.6210837364196777s
Understandability | Vocabs check for Bio2RDF::Goa took 0.2658412456512451s
Verifiability | Authors check for Bio2RDF::Goa took 0.26847410202026367s
Verifiability | Publishers check for Bio2RDF::Goa took 0.26421523094177246s
Performance | Throughput check for Bio2RDF::Goa took 10.799965143203735s
Amount of data | Check the number of entities for Bio2RDF::Goa took 89.44488954544067s
Verifiability | Contribs. check for Bio2RDF::Goa took 0.723224401473999s
Interlinking | sameAs chians check for Bio2RDF::Goa took 0.35607028007507324s
Interlinking | skos check for Bio2RDF::Goa took 0.7596030235290527s
Interlinking | skos check for Bio2RDF::Goa took 0.38790297508239746s
Timeliness | dataset update frequency check for Bio2RDF::Goa took 0.2556123733520508s
Currency | Creation date check for Bio2RDF::Goa took 0.5210072994232178s
Currency | Modification date check for Bio2RDF::Goa took 0.5053501129150391s
Rep.Conc. | URIs length for Bio2RDF::Goa took 109.80137062072754s
Interoperability | New vocabularies check for Bio2RDF::Goa took 30.649329662322998s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Goa took 0.407120943069458s
Accuracy | Check Functional Property for Bio2RDF::Goa took 0.2788076400756836s
Accuracy | Check Inverse Functional Property for Bio2RDF::Goa took 0.27578067779541016s
Accuracy | Check Empty annotation labels for Bio2RDF::Goa took 7.855287790298462s
Accuracy | Check White space in annotation for Bio2RDF::Goa took 0.8961994647979736s
Accuracy | Check Datatype consistency for Bio2RDF::Goa took 0.7187089920043945s
Consistency | Disjoint class check for Bio2RDF::Goa took 0.4140634536743164s
Consistency | Check Misplaced properties for Bio2RDF::Goa took 65.42457890510559s
Consistency | Misplaced classes for Bio2RDF::Goa took 2.5417633056640625s
Consistency | Check Ontology hijacking for Bio2RDF::Goa took 6.543526887893677s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Goa took 1.4432716369628906s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Goa took 61.669307708740234s
Conciseness | Check Extensional conciseness for Bio2RDF::Goa took 0.7513411045074463s
Conciseness | Check Intensional conciseness for Bio2RDF::Goa took 0.46274399757385254s
Security | Sign check for Bio2RDF::Goa took 0.2772090435028076s
Availability | Check URIs Dereferenciability for Bio2RDF::Goa took 9.360761880874634s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 0.5287079811096191s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.021229267120361328s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0010459423065185547s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 8.273124694824219e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Goa took 40.309866189956665s
Believability | Calculation of trust value for Bio2RDF::Goa took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-goa took 1108.8734760284424s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 0.6171829700469971s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.0006873607635498047s
Extra | Recovery of all triples for Bio2RDF::Hgnc took 20.143752813339233s
Performance | Total latancy measurement for Bio2RDF::Hgnc took 1.2764997482299805s
Amount of data | Number of triples check for Bio2RDF::Hgnc took 46.760793685913086s
Interoperability | New terms check for Bio2RDF::Hgnc took 41.74400806427002s
Versatility | Languages check for Bio2RDF::Hgnc took 60.24295473098755s
Interpretability | Number of blank nodes check for Bio2RDF::Hgnc took 0.2541816234588623s
Security | Check HTTPS for Bio2RDF::Hgnc took 0.17181038856506348s
Interpretability | RDF structures check for Bio2RDF::Hgnc took 1.1062602996826172s
Versatility | Serialization formats check for Bio2RDF::Hgnc took 0.31372714042663574s
Availability | RDF dump link check for Bio2RDF::Hgnc took 2.128204107284546s
License | MR license check for Bio2RDF::Hgnc took 0.6167237758636475s
License | HR license check for Bio2RDF::Hgnc took 60.25774312019348s
Amount of data | Number of property check for Bio2RDF::Hgnc took 0.26981449127197266s
Understandability | Number of label check for Bio2RDF::Hgnc took 9.399744749069214s
Understandability | URI regex check for Bio2RDF::Hgnc took 0.5939900875091553s
Understandability | Vocabs check for Bio2RDF::Hgnc took 0.27304673194885254s
Verifiability | Authors check for Bio2RDF::Hgnc took 0.24245953559875488s
Verifiability | Publishers check for Bio2RDF::Hgnc took 0.2551388740539551s
Performance | Throughput check for Bio2RDF::Hgnc took 11.047346115112305s
Amount of data | Check the number of entities for Bio2RDF::Hgnc took 88.90464425086975s
Verifiability | Contribs. check for Bio2RDF::Hgnc took 0.738783597946167s
Interlinking | sameAs chians check for Bio2RDF::Hgnc took 0.3858981132507324s
Interlinking | skos check for Bio2RDF::Hgnc took 0.9152481555938721s
Interlinking | skos check for Bio2RDF::Hgnc took 0.33602046966552734s
Timeliness | dataset update frequency check for Bio2RDF::Hgnc took 0.27413153648376465s
Currency | Creation date check for Bio2RDF::Hgnc took 0.5430426597595215s
Currency | Modification date check for Bio2RDF::Hgnc took 0.5187442302703857s
Rep.Conc. | URIs length for Bio2RDF::Hgnc took 111.52110815048218s
Interoperability | New vocabularies check for Bio2RDF::Hgnc took 28.254014015197754s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Hgnc took 0.42729616165161133s
Accuracy | Check Functional Property for Bio2RDF::Hgnc took 0.2965421676635742s
Accuracy | Check Inverse Functional Property for Bio2RDF::Hgnc took 0.29144835472106934s
Accuracy | Check Empty annotation labels for Bio2RDF::Hgnc took 7.682614803314209s
Accuracy | Check White space in annotation for Bio2RDF::Hgnc took 0.8989810943603516s
Accuracy | Check Datatype consistency for Bio2RDF::Hgnc took 0.702948808670044s
Consistency | Disjoint class check for Bio2RDF::Hgnc took 0.36511993408203125s
Consistency | Check Misplaced properties for Bio2RDF::Hgnc took 66.2352135181427s
Consistency | Misplaced classes for Bio2RDF::Hgnc took 2.504279375076294s
Consistency | Check Ontology hijacking for Bio2RDF::Hgnc took 6.347872972488403s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Hgnc took 1.4297316074371338s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Hgnc took 61.68782949447632s
Conciseness | Check Extensional conciseness for Bio2RDF::Hgnc took 0.7634670734405518s
Conciseness | Check Intensional conciseness for Bio2RDF::Hgnc took 0.4638326168060303s
Security | Sign check for Bio2RDF::Hgnc took 0.25982022285461426s
Availability | Check URIs Dereferenciability for Bio2RDF::Hgnc took 10.83898639678955s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 0.3919718265533447s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.020976543426513672s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.00011610984802246094s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Hgnc took 32.61751890182495s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 1.5735626220703125e-05s
INFO | --- Analysis for bio2rdf-hgnc took 1094.6545803546906s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 0.5780768394470215s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.000637054443359375s
Extra | Recovery of all triples for Bio2RDF::Homologene took 18.894511222839355s
Performance | Total latancy measurement for Bio2RDF::Homologene took 1.2670700550079346s
Amount of data | Number of triples check for Bio2RDF::Homologene took 44.8321270942688s
Interoperability | New terms check for Bio2RDF::Homologene took 41.90081024169922s
Versatility | Languages check for Bio2RDF::Homologene took 60.24833846092224s
Interpretability | Number of blank nodes check for Bio2RDF::Homologene took 0.2700324058532715s
Security | Check HTTPS for Bio2RDF::Homologene took 0.17041754722595215s
Interpretability | RDF structures check for Bio2RDF::Homologene took 0.7938816547393799s
Versatility | Serialization formats check for Bio2RDF::Homologene took 0.45948100090026855s
Availability | RDF dump link check for Bio2RDF::Homologene took 2.149348497390747s
License | MR license check for Bio2RDF::Homologene took 0.5189368724822998s
License | HR license check for Bio2RDF::Homologene took 60.23949909210205s
Amount of data | Number of property check for Bio2RDF::Homologene took 0.27553391456604004s
Understandability | Number of label check for Bio2RDF::Homologene took 10.405409812927246s
Understandability | URI regex check for Bio2RDF::Homologene took 0.5737779140472412s
Understandability | Vocabs check for Bio2RDF::Homologene took 0.2774639129638672s
Verifiability | Authors check for Bio2RDF::Homologene took 0.2764136791229248s
Verifiability | Publishers check for Bio2RDF::Homologene took 0.26125144958496094s
Performance | Throughput check for Bio2RDF::Homologene took 11.274748802185059s
Amount of data | Check the number of entities for Bio2RDF::Homologene took 90.83790946006775s
Verifiability | Contribs. check for Bio2RDF::Homologene took 0.7514574527740479s
Interlinking | sameAs chians check for Bio2RDF::Homologene took 0.3688337802886963s
Interlinking | skos check for Bio2RDF::Homologene took 0.8371045589447021s
Interlinking | skos check for Bio2RDF::Homologene took 0.347851037979126s
Timeliness | dataset update frequency check for Bio2RDF::Homologene took 0.23818755149841309s
Currency | Creation date check for Bio2RDF::Homologene took 0.5193712711334229s
Currency | Modification date check for Bio2RDF::Homologene took 0.5087878704071045s
Rep.Conc. | URIs length for Bio2RDF::Homologene took 109.86457633972168s
Interoperability | New vocabularies check for Bio2RDF::Homologene took 34.57063817977905s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Homologene took 0.42861247062683105s
Accuracy | Check Functional Property for Bio2RDF::Homologene took 0.28019046783447266s
Accuracy | Check Inverse Functional Property for Bio2RDF::Homologene took 0.2982914447784424s
Accuracy | Check Empty annotation labels for Bio2RDF::Homologene took 7.459084987640381s
Accuracy | Check White space in annotation for Bio2RDF::Homologene took 0.8969531059265137s
Accuracy | Check Datatype consistency for Bio2RDF::Homologene took 0.7182586193084717s
Consistency | Disjoint class check for Bio2RDF::Homologene took 0.42650651931762695s
Consistency | Check Misplaced properties for Bio2RDF::Homologene took 65.33697175979614s
Consistency | Misplaced classes for Bio2RDF::Homologene took 2.5373318195343018s
Consistency | Check Ontology hijacking for Bio2RDF::Homologene took 6.482455015182495s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Homologene took 1.4205663204193115s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Homologene took 61.68378973007202s
Conciseness | Check Extensional conciseness for Bio2RDF::Homologene took 0.7743890285491943s
Conciseness | Check Intensional conciseness for Bio2RDF::Homologene took 0.4330708980560303s
Security | Sign check for Bio2RDF::Homologene took 0.25821661949157715s
Availability | Check URIs Dereferenciability for Bio2RDF::Homologene took 9.553701877593994s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 0.4441533088684082s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.02135610580444336s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0008182525634765625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 0.0001347064971923828s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Homologene took 21.96058487892151s
Believability | Calculation of trust value for Bio2RDF::Homologene took 1.3828277587890625e-05s
INFO | --- Analysis for bio2rdf-homologene took 1084.5745692253113s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 0.6034097671508789s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.0006365776062011719s
Extra | Recovery of all triples for Bio2RDF::Interpro took 19.812193632125854s
Performance | Total latancy measurement for Bio2RDF::Interpro took 1.2812201976776123s
Amount of data | Number of triples check for Bio2RDF::Interpro took 45.90136957168579s
Interoperability | New terms check for Bio2RDF::Interpro took 41.443658113479614s
Versatility | Languages check for Bio2RDF::Interpro took 60.22954177856445s
Interpretability | Number of blank nodes check for Bio2RDF::Interpro took 0.27726316452026367s
Security | Check HTTPS for Bio2RDF::Interpro took 0.16885852813720703s
Interpretability | RDF structures check for Bio2RDF::Interpro took 0.8052806854248047s
Versatility | Serialization formats check for Bio2RDF::Interpro took 0.31416749954223633s
Availability | RDF dump link check for Bio2RDF::Interpro took 2.076575756072998s
License | MR license check for Bio2RDF::Interpro took 0.5639617443084717s
License | HR license check for Bio2RDF::Interpro took 60.24429988861084s
Amount of data | Number of property check for Bio2RDF::Interpro took 0.2659327983856201s
Understandability | Number of label check for Bio2RDF::Interpro took 10.087766885757446s
Understandability | URI regex check for Bio2RDF::Interpro took 0.5940048694610596s
Understandability | Vocabs check for Bio2RDF::Interpro took 0.2488386631011963s
Verifiability | Authors check for Bio2RDF::Interpro took 0.2586672306060791s
Verifiability | Publishers check for Bio2RDF::Interpro took 0.254697322845459s
Performance | Throughput check for Bio2RDF::Interpro took 11.07884955406189s
Amount of data | Check the number of entities for Bio2RDF::Interpro took 91.23630261421204s
Verifiability | Contribs. check for Bio2RDF::Interpro took 1.5364067554473877s
Interlinking | sameAs chians check for Bio2RDF::Interpro took 0.35419559478759766s
Interlinking | skos check for Bio2RDF::Interpro took 0.8295388221740723s
Interlinking | skos check for Bio2RDF::Interpro took 0.3598902225494385s
Timeliness | dataset update frequency check for Bio2RDF::Interpro took 0.26537013053894043s
Currency | Creation date check for Bio2RDF::Interpro took 0.5396256446838379s
Currency | Modification date check for Bio2RDF::Interpro took 0.5091209411621094s
Rep.Conc. | URIs length for Bio2RDF::Interpro took 109.92438173294067s
Interoperability | New vocabularies check for Bio2RDF::Interpro took 28.579108953475952s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Interpro took 0.39723706245422363s
Accuracy | Check Functional Property for Bio2RDF::Interpro took 0.27855634689331055s
Accuracy | Check Inverse Functional Property for Bio2RDF::Interpro took 0.2698988914489746s
Accuracy | Check Empty annotation labels for Bio2RDF::Interpro took 7.449778318405151s
Accuracy | Check White space in annotation for Bio2RDF::Interpro took 0.9073512554168701s
Accuracy | Check Datatype consistency for Bio2RDF::Interpro took 0.7222988605499268s
Consistency | Disjoint class check for Bio2RDF::Interpro took 0.50124192237854s
Consistency | Check Misplaced properties for Bio2RDF::Interpro took 65.76132726669312s
Consistency | Misplaced classes for Bio2RDF::Interpro took 2.5207080841064453s
Consistency | Check Ontology hijacking for Bio2RDF::Interpro took 6.490962028503418s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Interpro took 1.4205915927886963s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Interpro took 61.64190721511841s
Conciseness | Check Extensional conciseness for Bio2RDF::Interpro took 0.7634079456329346s
Conciseness | Check Intensional conciseness for Bio2RDF::Interpro took 0.4479255676269531s
Security | Sign check for Bio2RDF::Interpro took 0.2806103229522705s
Availability | Check URIs Dereferenciability for Bio2RDF::Interpro took 10.722248315811157s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 0.3709852695465088s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.020829439163208008s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 0.00011157989501953125s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Interpro took 33.40443968772888s
Believability | Calculation of trust value for Bio2RDF::Interpro took 1.0728836059570312e-05s
INFO | --- Analysis for bio2rdf-interpro took 1096.10547041893s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 0.15514254570007324s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.0007250308990478516s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 0.28508448600769043s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.022170305252075195s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 8.273124694824219e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 1.430511474609375e-05s
INFO | --- Analysis for bio2rdf-iproclass took 16.51249599456787s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 0.6119952201843262s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.0005350112915039062s
Extra | Recovery of all triples for Bio2RDF::Irefindex took 19.84218406677246s
Performance | Total latancy measurement for Bio2RDF::Irefindex took 1.2571544647216797s
Amount of data | Number of triples check for Bio2RDF::Irefindex took 45.96317505836487s
Interoperability | New terms check for Bio2RDF::Irefindex took 42.28722143173218s
Versatility | Languages check for Bio2RDF::Irefindex took 60.238929271698s
Interpretability | Number of blank nodes check for Bio2RDF::Irefindex took 0.257047176361084s
Security | Check HTTPS for Bio2RDF::Irefindex took 0.15623140335083008s
Interpretability | RDF structures check for Bio2RDF::Irefindex took 1.084550142288208s
Versatility | Serialization formats check for Bio2RDF::Irefindex took 0.3177516460418701s
Availability | RDF dump link check for Bio2RDF::Irefindex took 2.0949137210845947s
License | MR license check for Bio2RDF::Irefindex took 0.5977070331573486s
License | HR license check for Bio2RDF::Irefindex took 60.25961971282959s
Amount of data | Number of property check for Bio2RDF::Irefindex took 0.2844526767730713s
Understandability | Number of label check for Bio2RDF::Irefindex took 10.376599788665771s
Understandability | URI regex check for Bio2RDF::Irefindex took 0.5660500526428223s
Understandability | Vocabs check for Bio2RDF::Irefindex took 0.27131056785583496s
Verifiability | Authors check for Bio2RDF::Irefindex took 0.2486097812652588s
Verifiability | Publishers check for Bio2RDF::Irefindex took 0.2586324214935303s
Performance | Throughput check for Bio2RDF::Irefindex took 10.862016201019287s
Amount of data | Check the number of entities for Bio2RDF::Irefindex took 84.5566029548645s
Verifiability | Contribs. check for Bio2RDF::Irefindex took 0.7267482280731201s
Interlinking | sameAs chians check for Bio2RDF::Irefindex took 0.37363100051879883s
Interlinking | skos check for Bio2RDF::Irefindex took 0.8312172889709473s
Interlinking | skos check for Bio2RDF::Irefindex took 0.3576812744140625s
Timeliness | dataset update frequency check for Bio2RDF::Irefindex took 0.27277278900146484s
Currency | Creation date check for Bio2RDF::Irefindex took 0.5123188495635986s
Currency | Modification date check for Bio2RDF::Irefindex took 0.5261931419372559s
Rep.Conc. | URIs length for Bio2RDF::Irefindex took 108.92113900184631s
Interoperability | New vocabularies check for Bio2RDF::Irefindex took 30.17739224433899s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Irefindex took 0.43025779724121094s
Accuracy | Check Functional Property for Bio2RDF::Irefindex took 0.2829244136810303s
Accuracy | Check Inverse Functional Property for Bio2RDF::Irefindex took 0.28617382049560547s
Accuracy | Check Empty annotation labels for Bio2RDF::Irefindex took 7.338397741317749s
Accuracy | Check White space in annotation for Bio2RDF::Irefindex took 0.8966448307037354s
Accuracy | Check Datatype consistency for Bio2RDF::Irefindex took 0.6876695156097412s
Consistency | Disjoint class check for Bio2RDF::Irefindex took 0.42822861671447754s
Consistency | Check Misplaced properties for Bio2RDF::Irefindex took 65.11697959899902s
Consistency | Misplaced classes for Bio2RDF::Irefindex took 2.47128963470459s
Consistency | Check Ontology hijacking for Bio2RDF::Irefindex took 6.787444114685059s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Irefindex took 1.4301109313964844s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Irefindex took 61.67187237739563s
Conciseness | Check Extensional conciseness for Bio2RDF::Irefindex took 0.7321841716766357s
Conciseness | Check Intensional conciseness for Bio2RDF::Irefindex took 0.4625072479248047s
Security | Sign check for Bio2RDF::Irefindex took 0.2730295658111572s
Availability | Check URIs Dereferenciability for Bio2RDF::Irefindex took 9.316455841064453s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 0.6590404510498047s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.02085113525390625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 8.177757263183594e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Irefindex took 26.868109464645386s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 1.4066696166992188e-05s
INFO | --- Analysis for bio2rdf-irefindex took 1080.2322432994843s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 0.14589881896972656s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.0003979206085205078s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 0.34346628189086914s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.02043461799621582s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 3.5762786865234375e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 1.0728836059570312e-05s
INFO | --- Analysis for bio2rdf-linkedspl took 9.837190628051758s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 0.6092796325683594s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.0004169940948486328s
Extra | Recovery of all triples for Bio2RDF::Lsr took 19.310173749923706s
Performance | Total latancy measurement for Bio2RDF::Lsr took 1.2499580383300781s
Amount of data | Number of triples check for Bio2RDF::Lsr took 45.15754413604736s
Interoperability | New terms check for Bio2RDF::Lsr took 42.94100522994995s
Versatility | Languages check for Bio2RDF::Lsr took 60.244372844696045s
Interpretability | Number of blank nodes check for Bio2RDF::Lsr took 0.27971816062927246s
Security | Check HTTPS for Bio2RDF::Lsr took 0.15689969062805176s
Interpretability | RDF structures check for Bio2RDF::Lsr took 1.1802818775177002s
Versatility | Serialization formats check for Bio2RDF::Lsr took 0.3004186153411865s
Availability | RDF dump link check for Bio2RDF::Lsr took 2.308701753616333s
License | MR license check for Bio2RDF::Lsr took 0.445432186126709s
License | HR license check for Bio2RDF::Lsr took 60.23933386802673s
Amount of data | Number of property check for Bio2RDF::Lsr took 0.27959656715393066s
Understandability | Number of label check for Bio2RDF::Lsr took 10.727282047271729s
Understandability | URI regex check for Bio2RDF::Lsr took 0.6143612861633301s
Understandability | Vocabs check for Bio2RDF::Lsr took 0.2711453437805176s
Verifiability | Authors check for Bio2RDF::Lsr took 0.26958584785461426s
Verifiability | Publishers check for Bio2RDF::Lsr took 0.25993847846984863s
Performance | Throughput check for Bio2RDF::Lsr took 11.375770568847656s
Amount of data | Check the number of entities for Bio2RDF::Lsr took 89.41854858398438s
Verifiability | Contribs. check for Bio2RDF::Lsr took 0.7169466018676758s
Interlinking | sameAs chians check for Bio2RDF::Lsr took 0.3701140880584717s
Interlinking | skos check for Bio2RDF::Lsr took 1.1447155475616455s
Interlinking | skos check for Bio2RDF::Lsr took 0.35066747665405273s
Timeliness | dataset update frequency check for Bio2RDF::Lsr took 0.26112937927246094s
Currency | Creation date check for Bio2RDF::Lsr took 0.52984619140625s
Currency | Modification date check for Bio2RDF::Lsr took 0.5160470008850098s
Rep.Conc. | URIs length for Bio2RDF::Lsr took 108.88523840904236s
Interoperability | New vocabularies check for Bio2RDF::Lsr took 40.68078327178955s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Lsr took 0.4337737560272217s
Accuracy | Check Functional Property for Bio2RDF::Lsr took 0.286517858505249s
Accuracy | Check Inverse Functional Property for Bio2RDF::Lsr took 0.2941427230834961s
Accuracy | Check Empty annotation labels for Bio2RDF::Lsr took 6.810205698013306s
Accuracy | Check White space in annotation for Bio2RDF::Lsr took 0.8981971740722656s
Accuracy | Check Datatype consistency for Bio2RDF::Lsr took 0.692211389541626s
Consistency | Disjoint class check for Bio2RDF::Lsr took 0.4893949031829834s
Consistency | Check Misplaced properties for Bio2RDF::Lsr took 65.07820534706116s
Consistency | Misplaced classes for Bio2RDF::Lsr took 2.4822466373443604s
Consistency | Check Ontology hijacking for Bio2RDF::Lsr took 6.37005615234375s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Lsr took 1.4250662326812744s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Lsr took 61.662885904312134s
Conciseness | Check Extensional conciseness for Bio2RDF::Lsr took 0.7353026866912842s
Conciseness | Check Intensional conciseness for Bio2RDF::Lsr took 0.7301621437072754s
Security | Sign check for Bio2RDF::Lsr took 0.3005483150482178s
Availability | Check URIs Dereferenciability for Bio2RDF::Lsr took 10.009161710739136s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 0.42333412170410156s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.021238088607788086s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 2.3365020751953125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 6.008148193359375e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Lsr took 23.853660345077515s
Believability | Calculation of trust value for Bio2RDF::Lsr took 1.430511474609375e-05s
INFO | --- Analysis for bio2rdf-lsr took 1100.421424627304s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 0.6239101886749268s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.0006372928619384766s
Extra | Recovery of all triples for Bio2RDF::Mesh took 19.510193347930908s
Performance | Total latancy measurement for Bio2RDF::Mesh took 1.2398600578308105s
Amount of data | Number of triples check for Bio2RDF::Mesh took 45.92773079872131s
Interoperability | New terms check for Bio2RDF::Mesh took 43.73131465911865s
Versatility | Languages check for Bio2RDF::Mesh took 60.24445104598999s
Interpretability | Number of blank nodes check for Bio2RDF::Mesh took 0.2602102756500244s
Security | Check HTTPS for Bio2RDF::Mesh took 0.16392064094543457s
Interpretability | RDF structures check for Bio2RDF::Mesh took 1.044152021408081s
Versatility | Serialization formats check for Bio2RDF::Mesh took 0.35522007942199707s
Availability | RDF dump link check for Bio2RDF::Mesh took 2.0803611278533936s
License | MR license check for Bio2RDF::Mesh took 0.38081789016723633s
License | HR license check for Bio2RDF::Mesh took 60.23036003112793s
Amount of data | Number of property check for Bio2RDF::Mesh took 0.7269556522369385s
Understandability | Number of label check for Bio2RDF::Mesh took 10.497154474258423s
Understandability | URI regex check for Bio2RDF::Mesh took 0.579601526260376s
Understandability | Vocabs check for Bio2RDF::Mesh took 0.2719135284423828s
Verifiability | Authors check for Bio2RDF::Mesh took 0.2519659996032715s
Verifiability | Publishers check for Bio2RDF::Mesh took 0.2528982162475586s
Performance | Throughput check for Bio2RDF::Mesh took 11.258513927459717s
Amount of data | Check the number of entities for Bio2RDF::Mesh took 85.99586415290833s
Verifiability | Contribs. check for Bio2RDF::Mesh took 0.8264758586883545s
Interlinking | sameAs chians check for Bio2RDF::Mesh took 0.3683438301086426s
Interlinking | skos check for Bio2RDF::Mesh took 0.845562219619751s
Interlinking | skos check for Bio2RDF::Mesh took 0.34111475944519043s
Timeliness | dataset update frequency check for Bio2RDF::Mesh took 0.2530643939971924s
Currency | Creation date check for Bio2RDF::Mesh took 0.5349571704864502s
Currency | Modification date check for Bio2RDF::Mesh took 0.5269782543182373s
Rep.Conc. | URIs length for Bio2RDF::Mesh took 109.73583936691284s
Interoperability | New vocabularies check for Bio2RDF::Mesh took 20.15930938720703s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mesh took 0.4388711452484131s
Accuracy | Check Functional Property for Bio2RDF::Mesh took 0.27715516090393066s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mesh took 0.2823829650878906s
Accuracy | Check Empty annotation labels for Bio2RDF::Mesh took 6.779197454452515s
Accuracy | Check White space in annotation for Bio2RDF::Mesh took 0.9047267436981201s
Accuracy | Check Datatype consistency for Bio2RDF::Mesh took 0.6899294853210449s
Consistency | Disjoint class check for Bio2RDF::Mesh took 0.4203786849975586s
Consistency | Check Misplaced properties for Bio2RDF::Mesh took 66.08316111564636s
Consistency | Misplaced classes for Bio2RDF::Mesh took 2.474682331085205s
Consistency | Check Ontology hijacking for Bio2RDF::Mesh took 6.4891908168792725s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mesh took 1.431312084197998s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mesh took 61.671520709991455s
Conciseness | Check Extensional conciseness for Bio2RDF::Mesh took 0.7193529605865479s
Conciseness | Check Intensional conciseness for Bio2RDF::Mesh took 0.4470813274383545s
Security | Sign check for Bio2RDF::Mesh took 0.2645606994628906s
Availability | Check URIs Dereferenciability for Bio2RDF::Mesh took 9.145949363708496s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 0.5175044536590576s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.021129846572875977s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 8.726119995117188e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mesh took 30.022945404052734s
Believability | Calculation of trust value for Bio2RDF::Mesh took 1.3828277587890625e-05s
INFO | --- Analysis for bio2rdf-mesh took 1076.2801566123962s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 0.6259317398071289s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.0003771781921386719s
Extra | Recovery of all triples for Bio2RDF::Mgi took 18.1747784614563s
Performance | Total latancy measurement for Bio2RDF::Mgi took 1.2137179374694824s
Amount of data | Number of triples check for Bio2RDF::Mgi took 45.896435260772705s
Interoperability | New terms check for Bio2RDF::Mgi took 40.760512351989746s
Versatility | Languages check for Bio2RDF::Mgi took 60.296467304229736s
Interpretability | Number of blank nodes check for Bio2RDF::Mgi took 0.2725353240966797s
Security | Check HTTPS for Bio2RDF::Mgi took 0.15889525413513184s
Interpretability | RDF structures check for Bio2RDF::Mgi took 1.0129313468933105s
Versatility | Serialization formats check for Bio2RDF::Mgi took 0.33019113540649414s
Availability | RDF dump link check for Bio2RDF::Mgi took 2.234354019165039s
License | MR license check for Bio2RDF::Mgi took 0.5190901756286621s
License | HR license check for Bio2RDF::Mgi took 60.25202775001526s
Amount of data | Number of property check for Bio2RDF::Mgi took 0.2550787925720215s
Understandability | Number of label check for Bio2RDF::Mgi took 10.377207279205322s
Understandability | URI regex check for Bio2RDF::Mgi took 0.5792429447174072s
Understandability | Vocabs check for Bio2RDF::Mgi took 0.2614898681640625s
Verifiability | Authors check for Bio2RDF::Mgi took 0.26900553703308105s
Verifiability | Publishers check for Bio2RDF::Mgi took 0.23962855339050293s
Performance | Throughput check for Bio2RDF::Mgi took 11.085088014602661s
Amount of data | Check the number of entities for Bio2RDF::Mgi took 89.60321974754333s
Verifiability | Contribs. check for Bio2RDF::Mgi took 0.7029073238372803s
Interlinking | sameAs chians check for Bio2RDF::Mgi took 0.422182559967041s
Interlinking | skos check for Bio2RDF::Mgi took 1.1605465412139893s
Interlinking | skos check for Bio2RDF::Mgi took 0.3345646858215332s
Timeliness | dataset update frequency check for Bio2RDF::Mgi took 0.2583627700805664s
Currency | Creation date check for Bio2RDF::Mgi took 0.5123460292816162s
Currency | Modification date check for Bio2RDF::Mgi took 0.514768123626709s
Rep.Conc. | URIs length for Bio2RDF::Mgi took 109.52363586425781s
Interoperability | New vocabularies check for Bio2RDF::Mgi took 24.396872520446777s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mgi took 0.4271562099456787s
Accuracy | Check Functional Property for Bio2RDF::Mgi took 0.2866353988647461s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mgi took 0.28418874740600586s
Accuracy | Check Empty annotation labels for Bio2RDF::Mgi took 7.173823356628418s
Accuracy | Check White space in annotation for Bio2RDF::Mgi took 0.897165060043335s
Accuracy | Check Datatype consistency for Bio2RDF::Mgi took 0.7034549713134766s
Consistency | Disjoint class check for Bio2RDF::Mgi took 0.4417128562927246s
Consistency | Check Misplaced properties for Bio2RDF::Mgi took 65.5953459739685s
Consistency | Misplaced classes for Bio2RDF::Mgi took 2.4858906269073486s
Consistency | Check Ontology hijacking for Bio2RDF::Mgi took 6.45423150062561s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mgi took 1.433401107788086s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mgi took 61.66826272010803s
Conciseness | Check Extensional conciseness for Bio2RDF::Mgi took 0.7542903423309326s
Conciseness | Check Intensional conciseness for Bio2RDF::Mgi took 0.40958261489868164s
Security | Sign check for Bio2RDF::Mgi took 0.2756383419036865s
Availability | Check URIs Dereferenciability for Bio2RDF::Mgi took 10.334675788879395s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 0.40160465240478516s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.020978927612304688s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 0.00010585784912109375s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mgi took 23.787415027618408s
Believability | Calculation of trust value for Bio2RDF::Mgi took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-mgi took 1083.8040747642517s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 0.6143872737884521s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.0006277561187744141s
Extra | Recovery of all triples for Bio2RDF::Ncbigene took 19.71964144706726s
Performance | Total latancy measurement for Bio2RDF::Ncbigene took 1.2816450595855713s
Amount of data | Number of triples check for Bio2RDF::Ncbigene took 45.33196973800659s
Interoperability | New terms check for Bio2RDF::Ncbigene took 42.804007053375244s
Versatility | Languages check for Bio2RDF::Ncbigene took 60.25254487991333s
Interpretability | Number of blank nodes check for Bio2RDF::Ncbigene took 0.2807612419128418s
Security | Check HTTPS for Bio2RDF::Ncbigene took 0.15720033645629883s
Interpretability | RDF structures check for Bio2RDF::Ncbigene took 0.8551993370056152s
Versatility | Serialization formats check for Bio2RDF::Ncbigene took 0.3389308452606201s
Availability | RDF dump link check for Bio2RDF::Ncbigene took 2.051461696624756s
License | MR license check for Bio2RDF::Ncbigene took 0.6389696598052979s
License | HR license check for Bio2RDF::Ncbigene took 60.23217248916626s
Amount of data | Number of property check for Bio2RDF::Ncbigene took 0.2714519500732422s
Understandability | Number of label check for Bio2RDF::Ncbigene took 10.780314445495605s
Understandability | URI regex check for Bio2RDF::Ncbigene took 0.6137275695800781s
Understandability | Vocabs check for Bio2RDF::Ncbigene took 0.25486087799072266s
Verifiability | Authors check for Bio2RDF::Ncbigene took 0.25637221336364746s
Verifiability | Publishers check for Bio2RDF::Ncbigene took 0.25874972343444824s
Performance | Throughput check for Bio2RDF::Ncbigene took 10.885740280151367s
Amount of data | Check the number of entities for Bio2RDF::Ncbigene took 88.56342124938965s
Verifiability | Contribs. check for Bio2RDF::Ncbigene took 0.8398895263671875s
Interlinking | sameAs chians check for Bio2RDF::Ncbigene took 0.3656346797943115s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.8837881088256836s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.3448069095611572s
Timeliness | dataset update frequency check for Bio2RDF::Ncbigene took 0.2832834720611572s
Currency | Creation date check for Bio2RDF::Ncbigene took 0.5060470104217529s
Currency | Modification date check for Bio2RDF::Ncbigene took 0.5299112796783447s
Rep.Conc. | URIs length for Bio2RDF::Ncbigene took 109.33595299720764s
Interoperability | New vocabularies check for Bio2RDF::Ncbigene took 27.175033569335938s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ncbigene took 0.44634103775024414s
Accuracy | Check Functional Property for Bio2RDF::Ncbigene took 0.2751939296722412s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ncbigene took 0.2884256839752197s
Accuracy | Check Empty annotation labels for Bio2RDF::Ncbigene took 7.210159778594971s
Accuracy | Check White space in annotation for Bio2RDF::Ncbigene took 0.9069173336029053s
Accuracy | Check Datatype consistency for Bio2RDF::Ncbigene took 0.6971595287322998s
Consistency | Disjoint class check for Bio2RDF::Ncbigene took 0.40497779846191406s
Consistency | Check Misplaced properties for Bio2RDF::Ncbigene took 65.57169461250305s
Consistency | Misplaced classes for Bio2RDF::Ncbigene took 2.475198745727539s
Consistency | Check Ontology hijacking for Bio2RDF::Ncbigene took 6.411927938461304s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ncbigene took 1.4465100765228271s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ncbigene took 61.68756437301636s
Conciseness | Check Extensional conciseness for Bio2RDF::Ncbigene took 0.763218879699707s
Conciseness | Check Intensional conciseness for Bio2RDF::Ncbigene took 0.4454538822174072s
Security | Sign check for Bio2RDF::Ncbigene took 0.2979605197906494s
Availability | Check URIs Dereferenciability for Bio2RDF::Ncbigene took 9.152118682861328s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 0.7095606327056885s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.021431684494018555s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.00013256072998046875s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ncbigene took 20.615258932113647s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 1.4543533325195312e-05s
INFO | --- Analysis for bio2rdf-ncbigene took 1081.6404540538788s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 0.6141378879547119s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.0007266998291015625s
Extra | Recovery of all triples for Bio2RDF::Ndc took 18.25458526611328s
Performance | Total latancy measurement for Bio2RDF::Ndc took 1.298518180847168s
Amount of data | Number of triples check for Bio2RDF::Ndc took 46.13918471336365s
Interoperability | New terms check for Bio2RDF::Ndc took 43.02661752700806s
Versatility | Languages check for Bio2RDF::Ndc took 60.25631856918335s
Interpretability | Number of blank nodes check for Bio2RDF::Ndc took 0.27945876121520996s
Security | Check HTTPS for Bio2RDF::Ndc took 0.15857839584350586s
Interpretability | RDF structures check for Bio2RDF::Ndc took 1.0940673351287842s
Versatility | Serialization formats check for Bio2RDF::Ndc took 0.3403170108795166s
Availability | RDF dump link check for Bio2RDF::Ndc took 2.155806541442871s
License | MR license check for Bio2RDF::Ndc took 0.592374324798584s
License | HR license check for Bio2RDF::Ndc took 60.235556840896606s
Amount of data | Number of property check for Bio2RDF::Ndc took 0.26299357414245605s
Understandability | Number of label check for Bio2RDF::Ndc took 9.835356712341309s
Understandability | URI regex check for Bio2RDF::Ndc took 0.5923497676849365s
Understandability | Vocabs check for Bio2RDF::Ndc took 0.25448107719421387s
Verifiability | Authors check for Bio2RDF::Ndc took 0.2578463554382324s
Verifiability | Publishers check for Bio2RDF::Ndc took 0.2593963146209717s
Performance | Throughput check for Bio2RDF::Ndc took 10.873896598815918s
Amount of data | Check the number of entities for Bio2RDF::Ndc took 90.96833038330078s
Verifiability | Contribs. check for Bio2RDF::Ndc took 0.7077670097351074s
Interlinking | sameAs chians check for Bio2RDF::Ndc took 0.3670156002044678s
Interlinking | skos check for Bio2RDF::Ndc took 0.9955556392669678s
Interlinking | skos check for Bio2RDF::Ndc took 0.3514525890350342s
Timeliness | dataset update frequency check for Bio2RDF::Ndc took 0.2555711269378662s
Currency | Creation date check for Bio2RDF::Ndc took 0.5107622146606445s
Currency | Modification date check for Bio2RDF::Ndc took 0.5123553276062012s
Rep.Conc. | URIs length for Bio2RDF::Ndc took 108.52145171165466s
Interoperability | New vocabularies check for Bio2RDF::Ndc took 22.974318504333496s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ndc took 0.40151143074035645s
Accuracy | Check Functional Property for Bio2RDF::Ndc took 0.28554582595825195s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ndc took 0.27959203720092773s
Accuracy | Check Empty annotation labels for Bio2RDF::Ndc took 8.187655925750732s
Accuracy | Check White space in annotation for Bio2RDF::Ndc took 0.8953824043273926s
Accuracy | Check Datatype consistency for Bio2RDF::Ndc took 0.7091856002807617s
Consistency | Disjoint class check for Bio2RDF::Ndc took 0.4498941898345947s
Consistency | Check Misplaced properties for Bio2RDF::Ndc took 65.18969988822937s
Consistency | Misplaced classes for Bio2RDF::Ndc took 2.5085842609405518s
Consistency | Check Ontology hijacking for Bio2RDF::Ndc took 6.906678676605225s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ndc took 1.4294278621673584s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ndc took 61.6830313205719s
Conciseness | Check Extensional conciseness for Bio2RDF::Ndc took 0.7507085800170898s
Conciseness | Check Intensional conciseness for Bio2RDF::Ndc took 0.44678258895874023s
Security | Sign check for Bio2RDF::Ndc took 0.26445937156677246s
Availability | Check URIs Dereferenciability for Bio2RDF::Ndc took 9.990100383758545s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 0.35767102241516113s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.020693302154541016s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 5.888938903808594e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ndc took 24.271018266677856s
Believability | Calculation of trust value for Bio2RDF::Ndc took 1.3828277587890625e-05s
INFO | --- Analysis for bio2rdf-ndc took 1079.1196293830872s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 0.14665961265563965s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.000682830810546875s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.2803502082824707s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.021197080612182617s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 3.552436828613281e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 1.430511474609375e-05s
INFO | --- Analysis for bio2rdf-nextprot took 3.65944766998291s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 0.60701584815979s
Availability | VoID file availability check for Bio2RDF::Omim took 0.0006341934204101562s
Extra | Recovery of all triples for Bio2RDF::Omim took 18.5960910320282s
Performance | Total latancy measurement for Bio2RDF::Omim took 1.3138964176177979s
Amount of data | Number of triples check for Bio2RDF::Omim took 44.962430000305176s
Interoperability | New terms check for Bio2RDF::Omim took 41.73765683174133s
Versatility | Languages check for Bio2RDF::Omim took 60.24824023246765s
Interpretability | Number of blank nodes check for Bio2RDF::Omim took 0.2949965000152588s
Security | Check HTTPS for Bio2RDF::Omim took 0.16948318481445312s
Interpretability | RDF structures check for Bio2RDF::Omim took 0.7969048023223877s
Versatility | Serialization formats check for Bio2RDF::Omim took 0.3605966567993164s
Availability | RDF dump link check for Bio2RDF::Omim took 2.109168529510498s
License | MR license check for Bio2RDF::Omim took 0.47405123710632324s
License | HR license check for Bio2RDF::Omim took 60.2614369392395s
Amount of data | Number of property check for Bio2RDF::Omim took 0.26663804054260254s
Understandability | Number of label check for Bio2RDF::Omim took 9.688711404800415s
Understandability | URI regex check for Bio2RDF::Omim took 0.584181547164917s
Understandability | Vocabs check for Bio2RDF::Omim took 0.27009153366088867s
Verifiability | Authors check for Bio2RDF::Omim took 0.2711906433105469s
Verifiability | Publishers check for Bio2RDF::Omim took 0.2548410892486572s
Performance | Throughput check for Bio2RDF::Omim took 10.823678255081177s
Amount of data | Check the number of entities for Bio2RDF::Omim took 87.7413899898529s
Verifiability | Contribs. check for Bio2RDF::Omim took 0.7061252593994141s
Interlinking | sameAs chians check for Bio2RDF::Omim took 0.3967564105987549s
Interlinking | skos check for Bio2RDF::Omim took 0.9931387901306152s
Interlinking | skos check for Bio2RDF::Omim took 0.3480415344238281s
Timeliness | dataset update frequency check for Bio2RDF::Omim took 0.2459123134613037s
Currency | Creation date check for Bio2RDF::Omim took 0.5057322978973389s
Currency | Modification date check for Bio2RDF::Omim took 0.4909636974334717s
Rep.Conc. | URIs length for Bio2RDF::Omim took 108.87018036842346s
Interoperability | New vocabularies check for Bio2RDF::Omim took 23.529472827911377s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Omim took 0.4198169708251953s
Accuracy | Check Functional Property for Bio2RDF::Omim took 0.2583789825439453s
Accuracy | Check Inverse Functional Property for Bio2RDF::Omim took 0.2726311683654785s
Accuracy | Check Empty annotation labels for Bio2RDF::Omim took 6.693900108337402s
Accuracy | Check White space in annotation for Bio2RDF::Omim took 0.9125156402587891s
Accuracy | Check Datatype consistency for Bio2RDF::Omim took 0.684450626373291s
Consistency | Disjoint class check for Bio2RDF::Omim took 0.4284207820892334s
Consistency | Check Misplaced properties for Bio2RDF::Omim took 65.09577250480652s
Consistency | Misplaced classes for Bio2RDF::Omim took 2.471652030944824s
Consistency | Check Ontology hijacking for Bio2RDF::Omim took 6.640939235687256s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Omim took 1.4438557624816895s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Omim took 61.65901732444763s
Conciseness | Check Extensional conciseness for Bio2RDF::Omim took 0.7293648719787598s
Conciseness | Check Intensional conciseness for Bio2RDF::Omim took 0.46617865562438965s
Security | Sign check for Bio2RDF::Omim took 0.2704012393951416s
Availability | Check URIs Dereferenciability for Bio2RDF::Omim took 9.179714679718018s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 0.4719507694244385s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.02138805389404297s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.00013971328735351562s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Omim took 20.61969232559204s
Believability | Calculation of trust value for Bio2RDF::Omim took 1.430511474609375e-05s
INFO | --- Analysis for bio2rdf-omim took 1064.3467049598694s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 0.0001087188720703125s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.0003960132598876953s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.2816154956817627s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.020313739776611328s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 4.267692565917969e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 9.298324584960938e-06s
INFO | --- Analysis for bio2rdf-omim-resources took 2.903677463531494s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 0.6035113334655762s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.0006389617919921875s
Extra | Recovery of all triples for Bio2RDF::Orphanet took 19.508127212524414s
Performance | Total latancy measurement for Bio2RDF::Orphanet took 1.2424871921539307s
Amount of data | Number of triples check for Bio2RDF::Orphanet took 45.17939472198486s
Interoperability | New terms check for Bio2RDF::Orphanet took 42.15562319755554s
Versatility | Languages check for Bio2RDF::Orphanet took 60.23954510688782s
Interpretability | Number of blank nodes check for Bio2RDF::Orphanet took 0.25138425827026367s
Security | Check HTTPS for Bio2RDF::Orphanet took 0.15683555603027344s
Interpretability | RDF structures check for Bio2RDF::Orphanet took 0.6394884586334229s
Versatility | Serialization formats check for Bio2RDF::Orphanet took 0.32335424423217773s
Availability | RDF dump link check for Bio2RDF::Orphanet took 2.057417154312134s
License | MR license check for Bio2RDF::Orphanet took 0.4653141498565674s
License | HR license check for Bio2RDF::Orphanet took 60.25791144371033s
Amount of data | Number of property check for Bio2RDF::Orphanet took 0.27954602241516113s
Understandability | Number of label check for Bio2RDF::Orphanet took 9.940517663955688s
Understandability | URI regex check for Bio2RDF::Orphanet took 0.5973832607269287s
Understandability | Vocabs check for Bio2RDF::Orphanet took 0.24692606925964355s
Verifiability | Authors check for Bio2RDF::Orphanet took 0.25519251823425293s
Verifiability | Publishers check for Bio2RDF::Orphanet took 0.2534916400909424s
Performance | Throughput check for Bio2RDF::Orphanet took 11.547461032867432s
Amount of data | Check the number of entities for Bio2RDF::Orphanet took 87.49867749214172s
Verifiability | Contribs. check for Bio2RDF::Orphanet took 1.540457010269165s
Interlinking | sameAs chians check for Bio2RDF::Orphanet took 0.3327970504760742s
Interlinking | skos check for Bio2RDF::Orphanet took 0.8061070442199707s
Interlinking | skos check for Bio2RDF::Orphanet took 0.33280348777770996s
Timeliness | dataset update frequency check for Bio2RDF::Orphanet took 0.24455642700195312s
Currency | Creation date check for Bio2RDF::Orphanet took 0.5048940181732178s
Currency | Modification date check for Bio2RDF::Orphanet took 0.5158448219299316s
Rep.Conc. | URIs length for Bio2RDF::Orphanet took 110.57199478149414s
Interoperability | New vocabularies check for Bio2RDF::Orphanet took 23.100860595703125s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Orphanet took 0.42682313919067383s
Accuracy | Check Functional Property for Bio2RDF::Orphanet took 0.27718591690063477s
Accuracy | Check Inverse Functional Property for Bio2RDF::Orphanet took 0.2846999168395996s
Accuracy | Check Empty annotation labels for Bio2RDF::Orphanet took 6.768040418624878s
Accuracy | Check White space in annotation for Bio2RDF::Orphanet took 0.8964016437530518s
Accuracy | Check Datatype consistency for Bio2RDF::Orphanet took 0.7059378623962402s
Consistency | Disjoint class check for Bio2RDF::Orphanet took 0.36054372787475586s
Consistency | Check Misplaced properties for Bio2RDF::Orphanet took 65.08914828300476s
Consistency | Misplaced classes for Bio2RDF::Orphanet took 2.5043833255767822s
Consistency | Check Ontology hijacking for Bio2RDF::Orphanet took 6.521286249160767s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Orphanet took 1.414738416671753s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Orphanet took 61.68486022949219s
Conciseness | Check Extensional conciseness for Bio2RDF::Orphanet took 0.7228250503540039s
Conciseness | Check Intensional conciseness for Bio2RDF::Orphanet took 0.4497208595275879s
Security | Sign check for Bio2RDF::Orphanet took 0.2864067554473877s
Availability | Check URIs Dereferenciability for Bio2RDF::Orphanet took 11.094506740570068s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 0.36565351486206055s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.02096700668334961s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 0.00010585784912109375s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Orphanet took 26.590238094329834s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 1.4543533325195312e-05s
INFO | --- Analysis for bio2rdf-orphanet took 1080.2471623420715s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 0.14973735809326172s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.0006077289581298828s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 0.3390188217163086s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.020435571670532227s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 3.886222839355469e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 1.430511474609375e-05s
INFO | --- Analysis for bio2rdf-pathwaycommons took 9.354635238647461s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 0.5981547832489014s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.0006768703460693359s
Extra | Recovery of all triples for Bio2RDF::Pharmgkb took 19.020148515701294s
Performance | Total latancy measurement for Bio2RDF::Pharmgkb took 1.317103624343872s
Amount of data | Number of triples check for Bio2RDF::Pharmgkb took 46.33775782585144s
Interoperability | New terms check for Bio2RDF::Pharmgkb took 41.569212198257446s
Versatility | Languages check for Bio2RDF::Pharmgkb took 60.26158380508423s
Interpretability | Number of blank nodes check for Bio2RDF::Pharmgkb took 0.2767486572265625s
Security | Check HTTPS for Bio2RDF::Pharmgkb took 0.1679215431213379s
Interpretability | RDF structures check for Bio2RDF::Pharmgkb took 0.7403011322021484s
Versatility | Serialization formats check for Bio2RDF::Pharmgkb took 0.30766868591308594s
Availability | RDF dump link check for Bio2RDF::Pharmgkb took 2.1066653728485107s
License | MR license check for Bio2RDF::Pharmgkb took 0.4771549701690674s
License | HR license check for Bio2RDF::Pharmgkb took 60.26686096191406s
Amount of data | Number of property check for Bio2RDF::Pharmgkb took 0.26627659797668457s
Understandability | Number of label check for Bio2RDF::Pharmgkb took 10.874826669692993s
Understandability | URI regex check for Bio2RDF::Pharmgkb took 0.5829143524169922s
Understandability | Vocabs check for Bio2RDF::Pharmgkb took 0.2675473690032959s
Verifiability | Authors check for Bio2RDF::Pharmgkb took 0.2681081295013428s
Verifiability | Publishers check for Bio2RDF::Pharmgkb took 0.26290035247802734s
Performance | Throughput check for Bio2RDF::Pharmgkb took 10.631523132324219s
Amount of data | Check the number of entities for Bio2RDF::Pharmgkb took 86.12986040115356s
Verifiability | Contribs. check for Bio2RDF::Pharmgkb took 0.7610929012298584s
Interlinking | sameAs chians check for Bio2RDF::Pharmgkb took 0.344407320022583s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.8173742294311523s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.3761253356933594s
Timeliness | dataset update frequency check for Bio2RDF::Pharmgkb took 0.26190185546875s
Currency | Creation date check for Bio2RDF::Pharmgkb took 0.5286688804626465s
Currency | Modification date check for Bio2RDF::Pharmgkb took 0.5288419723510742s
Rep.Conc. | URIs length for Bio2RDF::Pharmgkb took 108.82866048812866s
Interoperability | New vocabularies check for Bio2RDF::Pharmgkb took 25.529439210891724s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pharmgkb took 0.4596982002258301s
Accuracy | Check Functional Property for Bio2RDF::Pharmgkb took 0.28987908363342285s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pharmgkb took 0.2761814594268799s
Accuracy | Check Empty annotation labels for Bio2RDF::Pharmgkb took 7.779491186141968s
Accuracy | Check White space in annotation for Bio2RDF::Pharmgkb took 0.900991678237915s
Accuracy | Check Datatype consistency for Bio2RDF::Pharmgkb took 0.6986947059631348s
Consistency | Disjoint class check for Bio2RDF::Pharmgkb took 0.42200636863708496s
Consistency | Check Misplaced properties for Bio2RDF::Pharmgkb took 65.55561017990112s
Consistency | Misplaced classes for Bio2RDF::Pharmgkb took 2.480893611907959s
Consistency | Check Ontology hijacking for Bio2RDF::Pharmgkb took 6.650573253631592s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pharmgkb took 1.420290470123291s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pharmgkb took 61.68162655830383s
Conciseness | Check Extensional conciseness for Bio2RDF::Pharmgkb took 0.7350485324859619s
Conciseness | Check Intensional conciseness for Bio2RDF::Pharmgkb took 0.4392433166503906s
Security | Sign check for Bio2RDF::Pharmgkb took 0.28342556953430176s
Availability | Check URIs Dereferenciability for Bio2RDF::Pharmgkb took 9.495419979095459s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 0.7319784164428711s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.02093029022216797s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 2.288818359375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 9.512901306152344e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pharmgkb took 19.819432735443115s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 1.0013580322265625e-05s
INFO | --- Analysis for bio2rdf-pharmgkb took 1073.9726829528809s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 0.6052520275115967s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.0007109642028808594s
Extra | Recovery of all triples for Bio2RDF::Pubmed took 19.261688709259033s
Performance | Total latancy measurement for Bio2RDF::Pubmed took 1.2289690971374512s
Amount of data | Number of triples check for Bio2RDF::Pubmed took 45.910057067871094s
Interoperability | New terms check for Bio2RDF::Pubmed took 41.72455024719238s
Versatility | Languages check for Bio2RDF::Pubmed took 60.22951579093933s
Interpretability | Number of blank nodes check for Bio2RDF::Pubmed took 0.2940375804901123s
Security | Check HTTPS for Bio2RDF::Pubmed took 0.15798616409301758s
Interpretability | RDF structures check for Bio2RDF::Pubmed took 0.6697959899902344s
Versatility | Serialization formats check for Bio2RDF::Pubmed took 0.34783363342285156s
Availability | RDF dump link check for Bio2RDF::Pubmed took 2.059128522872925s
License | MR license check for Bio2RDF::Pubmed took 0.5282814502716064s
License | HR license check for Bio2RDF::Pubmed took 60.25445365905762s
Amount of data | Number of property check for Bio2RDF::Pubmed took 0.3140869140625s
Understandability | Number of label check for Bio2RDF::Pubmed took 10.970450639724731s
Understandability | URI regex check for Bio2RDF::Pubmed took 0.6046850681304932s
Understandability | Vocabs check for Bio2RDF::Pubmed took 0.24745774269104004s
Verifiability | Authors check for Bio2RDF::Pubmed took 0.2743105888366699s
Verifiability | Publishers check for Bio2RDF::Pubmed took 0.25235724449157715s
Performance | Throughput check for Bio2RDF::Pubmed took 11.096476793289185s
Amount of data | Check the number of entities for Bio2RDF::Pubmed took 86.14090371131897s
Verifiability | Contribs. check for Bio2RDF::Pubmed took 0.7526254653930664s
Interlinking | sameAs chians check for Bio2RDF::Pubmed took 0.3566591739654541s
Interlinking | skos check for Bio2RDF::Pubmed took 1.0113670825958252s
Interlinking | skos check for Bio2RDF::Pubmed took 0.3889021873474121s
Timeliness | dataset update frequency check for Bio2RDF::Pubmed took 0.24727797508239746s
Currency | Creation date check for Bio2RDF::Pubmed took 0.5408596992492676s
Currency | Modification date check for Bio2RDF::Pubmed took 0.5317776203155518s
Rep.Conc. | URIs length for Bio2RDF::Pubmed took 108.96846795082092s
Interoperability | New vocabularies check for Bio2RDF::Pubmed took 24.836819648742676s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pubmed took 0.419553279876709s
Accuracy | Check Functional Property for Bio2RDF::Pubmed took 0.2786979675292969s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pubmed took 0.2831118106842041s
Accuracy | Check Empty annotation labels for Bio2RDF::Pubmed took 6.932224273681641s
Accuracy | Check White space in annotation for Bio2RDF::Pubmed took 0.9006786346435547s
Accuracy | Check Datatype consistency for Bio2RDF::Pubmed took 0.6918635368347168s
Consistency | Disjoint class check for Bio2RDF::Pubmed took 0.3999917507171631s
Consistency | Check Misplaced properties for Bio2RDF::Pubmed took 65.35111331939697s
Consistency | Misplaced classes for Bio2RDF::Pubmed took 2.473637104034424s
Consistency | Check Ontology hijacking for Bio2RDF::Pubmed took 6.471271514892578s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pubmed took 1.433962106704712s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pubmed took 61.696781396865845s
Conciseness | Check Extensional conciseness for Bio2RDF::Pubmed took 0.728269100189209s
Conciseness | Check Intensional conciseness for Bio2RDF::Pubmed took 0.4294755458831787s
Security | Sign check for Bio2RDF::Pubmed took 0.27274274826049805s
Availability | Check URIs Dereferenciability for Bio2RDF::Pubmed took 9.43982481956482s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 0.39879703521728516s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.024296283721923828s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.00014472007751464844s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pubmed took 21.581939220428467s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 1.5974044799804688e-05s
INFO | --- Analysis for bio2rdf-pubmed took 1072.0720705986023s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 0.1469583511352539s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0007565021514892578s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 0.33020925521850586s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.022554397583007812s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 8.320808410644531e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-sabiork took 9.477197408676147s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 1.418379783630371s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.000652313232421875s
Extra | Recovery of all triples for Bio2RDF::Sgd took 19.577086687088013s
Performance | Total latancy measurement for Bio2RDF::Sgd took 1.2561793327331543s
Amount of data | Number of triples check for Bio2RDF::Sgd took 45.99840426445007s
Interoperability | New terms check for Bio2RDF::Sgd took 42.67974138259888s
Versatility | Languages check for Bio2RDF::Sgd took 60.240357398986816s
Interpretability | Number of blank nodes check for Bio2RDF::Sgd took 0.2873713970184326s
Security | Check HTTPS for Bio2RDF::Sgd took 0.14685583114624023s
Interpretability | RDF structures check for Bio2RDF::Sgd took 0.6547601222991943s
Versatility | Serialization formats check for Bio2RDF::Sgd took 0.32016873359680176s
Availability | RDF dump link check for Bio2RDF::Sgd took 2.198712110519409s
License | MR license check for Bio2RDF::Sgd took 0.5048234462738037s
License | HR license check for Bio2RDF::Sgd took 60.25331163406372s
Amount of data | Number of property check for Bio2RDF::Sgd took 0.2635176181793213s
Understandability | Number of label check for Bio2RDF::Sgd took 10.310899496078491s
Understandability | URI regex check for Bio2RDF::Sgd took 0.6093595027923584s
Understandability | Vocabs check for Bio2RDF::Sgd took 0.2665116786956787s
Verifiability | Authors check for Bio2RDF::Sgd took 0.2568855285644531s
Verifiability | Publishers check for Bio2RDF::Sgd took 0.25699758529663086s
Performance | Throughput check for Bio2RDF::Sgd took 10.853545427322388s
Amount of data | Check the number of entities for Bio2RDF::Sgd took 87.75310373306274s
Verifiability | Contribs. check for Bio2RDF::Sgd took 0.712080717086792s
Interlinking | sameAs chians check for Bio2RDF::Sgd took 0.38072729110717773s
Interlinking | skos check for Bio2RDF::Sgd took 0.8219254016876221s
Interlinking | skos check for Bio2RDF::Sgd took 0.3607819080352783s
Timeliness | dataset update frequency check for Bio2RDF::Sgd took 0.25248098373413086s
Currency | Creation date check for Bio2RDF::Sgd took 0.5354156494140625s
Currency | Modification date check for Bio2RDF::Sgd took 0.533625602722168s
Rep.Conc. | URIs length for Bio2RDF::Sgd took 110.96682119369507s
Interoperability | New vocabularies check for Bio2RDF::Sgd took 20.899237871170044s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sgd took 0.43261122703552246s
Accuracy | Check Functional Property for Bio2RDF::Sgd took 0.2916562557220459s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sgd took 0.2943425178527832s
Accuracy | Check Empty annotation labels for Bio2RDF::Sgd took 6.9561309814453125s
Accuracy | Check White space in annotation for Bio2RDF::Sgd took 0.9012048244476318s
Accuracy | Check Datatype consistency for Bio2RDF::Sgd took 0.701845645904541s
Consistency | Disjoint class check for Bio2RDF::Sgd took 0.40562891960144043s
Consistency | Check Misplaced properties for Bio2RDF::Sgd took 65.5465030670166s
Consistency | Misplaced classes for Bio2RDF::Sgd took 2.5306992530822754s
Consistency | Check Ontology hijacking for Bio2RDF::Sgd took 7.160772085189819s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sgd took 1.4247491359710693s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sgd took 61.67587900161743s
Conciseness | Check Extensional conciseness for Bio2RDF::Sgd took 0.7197320461273193s
Conciseness | Check Intensional conciseness for Bio2RDF::Sgd took 0.4435555934906006s
Security | Sign check for Bio2RDF::Sgd took 0.2624013423919678s
Availability | Check URIs Dereferenciability for Bio2RDF::Sgd took 24.285577297210693s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 0.44765233993530273s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.021162986755371094s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00011658668518066406s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sgd took 30.684117078781128s
Believability | Calculation of trust value for Bio2RDF::Sgd took 1.5735626220703125e-05s
INFO | --- Analysis for bio2rdf-sgd took 1096.0106210708618s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 9.465217590332031e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 0.30056285858154297s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.020313262939453125s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0007872581481933594s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 4.00543212890625e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 1.430511474609375e-05s
INFO | --- Analysis for bio2rdf-sgd-resources took 2.9460275173187256s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 0.5888550281524658s
Availability | VoID file availability check for Bio2RDF::Sider took 0.0006506443023681641s
Extra | Recovery of all triples for Bio2RDF::Sider took 18.736807584762573s
Performance | Total latancy measurement for Bio2RDF::Sider took 1.286637306213379s
Amount of data | Number of triples check for Bio2RDF::Sider took 45.247175216674805s
Interoperability | New terms check for Bio2RDF::Sider took 42.83646249771118s
Versatility | Languages check for Bio2RDF::Sider took 60.261656045913696s
Interpretability | Number of blank nodes check for Bio2RDF::Sider took 0.2663688659667969s
Security | Check HTTPS for Bio2RDF::Sider took 0.15864872932434082s
Interpretability | RDF structures check for Bio2RDF::Sider took 0.846449613571167s
Versatility | Serialization formats check for Bio2RDF::Sider took 0.32656145095825195s
Availability | RDF dump link check for Bio2RDF::Sider took 2.0763163566589355s
License | MR license check for Bio2RDF::Sider took 0.48781371116638184s
License | HR license check for Bio2RDF::Sider took 60.25734519958496s
Amount of data | Number of property check for Bio2RDF::Sider took 0.24240350723266602s
Understandability | Number of label check for Bio2RDF::Sider took 10.477649688720703s
Understandability | URI regex check for Bio2RDF::Sider took 0.5935499668121338s
Understandability | Vocabs check for Bio2RDF::Sider took 0.25079870223999023s
Verifiability | Authors check for Bio2RDF::Sider took 0.25490880012512207s
Verifiability | Publishers check for Bio2RDF::Sider took 0.2557382583618164s
Performance | Throughput check for Bio2RDF::Sider took 10.68699026107788s
Amount of data | Check the number of entities for Bio2RDF::Sider took 88.30060601234436s
Verifiability | Contribs. check for Bio2RDF::Sider took 0.703148603439331s
Interlinking | sameAs chians check for Bio2RDF::Sider took 0.3634510040283203s
Interlinking | skos check for Bio2RDF::Sider took 0.842458963394165s
Interlinking | skos check for Bio2RDF::Sider took 0.33441972732543945s
Timeliness | dataset update frequency check for Bio2RDF::Sider took 0.2498152256011963s
Currency | Creation date check for Bio2RDF::Sider took 0.5220263004302979s
Currency | Modification date check for Bio2RDF::Sider took 0.5236401557922363s
Rep.Conc. | URIs length for Bio2RDF::Sider took 109.16941428184509s
Interoperability | New vocabularies check for Bio2RDF::Sider took 21.527886629104614s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sider took 0.4262382984161377s
Accuracy | Check Functional Property for Bio2RDF::Sider took 0.271038293838501s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sider took 0.27962327003479004s
Accuracy | Check Empty annotation labels for Bio2RDF::Sider took 7.25786018371582s
Accuracy | Check White space in annotation for Bio2RDF::Sider took 0.8970551490783691s
Accuracy | Check Datatype consistency for Bio2RDF::Sider took 0.702301025390625s
Consistency | Disjoint class check for Bio2RDF::Sider took 0.39808034896850586s
Consistency | Check Misplaced properties for Bio2RDF::Sider took 65.55831670761108s
Consistency | Misplaced classes for Bio2RDF::Sider took 2.513589859008789s
Consistency | Check Ontology hijacking for Bio2RDF::Sider took 6.901827573776245s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sider took 1.4372472763061523s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sider took 61.697386741638184s
Conciseness | Check Extensional conciseness for Bio2RDF::Sider took 0.7320384979248047s
Conciseness | Check Intensional conciseness for Bio2RDF::Sider took 0.4371473789215088s
Security | Sign check for Bio2RDF::Sider took 0.2600977420806885s
Availability | Check URIs Dereferenciability for Bio2RDF::Sider took 25.320770502090454s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 0.4169762134552002s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.021295785903930664s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 4.57763671875e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sider took 32.78274917602539s
Believability | Calculation of trust value for Bio2RDF::Sider took 1.3828277587890625e-05s
INFO | --- Analysis for bio2rdf-sider took 1100.2368216514587s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 4.458427429199219e-05s
Availability | VoID file availability check for bio2rdf-taxon took 0.0007176399230957031s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 0.2862081527709961s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.02022552490234375s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 4.410743713378906e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 1.4543533325195312e-05s
INFO | --- Analysis for bio2rdf-taxon took 2.8508734703063965s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 0.6018826961517334s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.0006341934204101562s
Extra | Recovery of all triples for Bio2RDF::Taxonomy took 19.911459922790527s
Performance | Total latancy measurement for Bio2RDF::Taxonomy took 1.2562229633331299s
Amount of data | Number of triples check for Bio2RDF::Taxonomy took 45.922983169555664s
Interoperability | New terms check for Bio2RDF::Taxonomy took 46.17402958869934s
Versatility | Languages check for Bio2RDF::Taxonomy took 60.259541749954224s
Interpretability | Number of blank nodes check for Bio2RDF::Taxonomy took 0.2741549015045166s
Security | Check HTTPS for Bio2RDF::Taxonomy took 0.1543102264404297s
Interpretability | RDF structures check for Bio2RDF::Taxonomy took 0.2753636837005615s
Versatility | Serialization formats check for Bio2RDF::Taxonomy took 0.3324260711669922s
Availability | RDF dump link check for Bio2RDF::Taxonomy took 2.0184032917022705s
License | MR license check for Bio2RDF::Taxonomy took 0.4804072380065918s
License | HR license check for Bio2RDF::Taxonomy took 60.25551962852478s
Amount of data | Number of property check for Bio2RDF::Taxonomy took 0.26146841049194336s
Understandability | Number of label check for Bio2RDF::Taxonomy took 11.012490272521973s
Understandability | URI regex check for Bio2RDF::Taxonomy took 0.5879659652709961s
Understandability | Vocabs check for Bio2RDF::Taxonomy took 0.2543468475341797s
Verifiability | Authors check for Bio2RDF::Taxonomy took 0.29509520530700684s
Verifiability | Publishers check for Bio2RDF::Taxonomy took 0.2788255214691162s
Performance | Throughput check for Bio2RDF::Taxonomy took 11.34497356414795s
Amount of data | Check the number of entities for Bio2RDF::Taxonomy took 87.32643556594849s
Verifiability | Contribs. check for Bio2RDF::Taxonomy took 0.7329566478729248s
Interlinking | sameAs chians check for Bio2RDF::Taxonomy took 0.3751850128173828s
Interlinking | skos check for Bio2RDF::Taxonomy took 1.17842698097229s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.34879636764526367s
Timeliness | dataset update frequency check for Bio2RDF::Taxonomy took 0.25408196449279785s
Currency | Creation date check for Bio2RDF::Taxonomy took 0.5185654163360596s
Currency | Modification date check for Bio2RDF::Taxonomy took 0.5222022533416748s
Rep.Conc. | URIs length for Bio2RDF::Taxonomy took 110.18872046470642s
Interoperability | New vocabularies check for Bio2RDF::Taxonomy took 23.38252305984497s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Taxonomy took 0.4379260540008545s
Accuracy | Check Functional Property for Bio2RDF::Taxonomy took 0.2757742404937744s
Accuracy | Check Inverse Functional Property for Bio2RDF::Taxonomy took 0.2634596824645996s
Accuracy | Check Empty annotation labels for Bio2RDF::Taxonomy took 7.096413850784302s
Accuracy | Check White space in annotation for Bio2RDF::Taxonomy took 0.900425910949707s
Accuracy | Check Datatype consistency for Bio2RDF::Taxonomy took 0.7141289710998535s
Consistency | Disjoint class check for Bio2RDF::Taxonomy took 0.42785072326660156s
Consistency | Check Misplaced properties for Bio2RDF::Taxonomy took 64.97587323188782s
Consistency | Misplaced classes for Bio2RDF::Taxonomy took 2.5008201599121094s
Consistency | Check Ontology hijacking for Bio2RDF::Taxonomy took 6.631666660308838s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Taxonomy took 1.4505715370178223s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Taxonomy took 61.688719511032104s
Conciseness | Check Extensional conciseness for Bio2RDF::Taxonomy took 0.7376317977905273s
Conciseness | Check Intensional conciseness for Bio2RDF::Taxonomy took 0.4260890483856201s
Security | Sign check for Bio2RDF::Taxonomy took 0.2724144458770752s
Availability | Check URIs Dereferenciability for Bio2RDF::Taxonomy took 9.117415189743042s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 1.480780839920044s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.020931482315063477s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 0.00010967254638671875s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Taxonomy took 15.11984634399414s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 1.049041748046875e-05s
INFO | --- Analysis for bio2rdf-taxonomy took 1074.3317468166351s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 0.15285873413085938s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.0006761550903320312s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 0.3129463195800781s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.020553112030029297s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 3.528594970703125e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 1.430511474609375e-05s
INFO | --- Analysis for bio2rdf-wikipathways took 17.14806079864502s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 0.6041538715362549s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.0007998943328857422s
Extra | Recovery of all triples for Bio2RDF::Wormbase took 18.783982515335083s
Performance | Total latancy measurement for Bio2RDF::Wormbase took 1.2268648147583008s
Amount of data | Number of triples check for Bio2RDF::Wormbase took 45.04803705215454s
Interoperability | New terms check for Bio2RDF::Wormbase took 42.20759105682373s
Versatility | Languages check for Bio2RDF::Wormbase took 60.23853302001953s
Interpretability | Number of blank nodes check for Bio2RDF::Wormbase took 0.2805187702178955s
Security | Check HTTPS for Bio2RDF::Wormbase took 0.15772700309753418s
Interpretability | RDF structures check for Bio2RDF::Wormbase took 0.819411039352417s
Versatility | Serialization formats check for Bio2RDF::Wormbase took 0.32183289527893066s
Availability | RDF dump link check for Bio2RDF::Wormbase took 2.2388319969177246s
License | MR license check for Bio2RDF::Wormbase took 0.5239312648773193s
License | HR license check for Bio2RDF::Wormbase took 60.24850058555603s
Amount of data | Number of property check for Bio2RDF::Wormbase took 0.2736525535583496s
Understandability | Number of label check for Bio2RDF::Wormbase took 9.577080726623535s
Understandability | URI regex check for Bio2RDF::Wormbase took 0.5686213970184326s
Understandability | Vocabs check for Bio2RDF::Wormbase took 0.26839733123779297s
Verifiability | Authors check for Bio2RDF::Wormbase took 0.26880788803100586s
Verifiability | Publishers check for Bio2RDF::Wormbase took 0.24032950401306152s
Performance | Throughput check for Bio2RDF::Wormbase took 11.733325958251953s
Amount of data | Check the number of entities for Bio2RDF::Wormbase took 87.52891778945923s
Verifiability | Contribs. check for Bio2RDF::Wormbase took 0.7309932708740234s
Interlinking | sameAs chians check for Bio2RDF::Wormbase took 0.3711507320404053s
Interlinking | skos check for Bio2RDF::Wormbase took 0.8799457550048828s
Interlinking | skos check for Bio2RDF::Wormbase took 0.34369683265686035s
Timeliness | dataset update frequency check for Bio2RDF::Wormbase took 0.24505972862243652s
Currency | Creation date check for Bio2RDF::Wormbase took 0.5172004699707031s
Currency | Modification date check for Bio2RDF::Wormbase took 0.51285719871521s
Rep.Conc. | URIs length for Bio2RDF::Wormbase took 109.06736588478088s
Interoperability | New vocabularies check for Bio2RDF::Wormbase took 25.872838735580444s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Wormbase took 0.41645145416259766s
Accuracy | Check Functional Property for Bio2RDF::Wormbase took 0.2664520740509033s
Accuracy | Check Inverse Functional Property for Bio2RDF::Wormbase took 0.2655656337738037s
Accuracy | Check Empty annotation labels for Bio2RDF::Wormbase took 7.315106630325317s
Accuracy | Check White space in annotation for Bio2RDF::Wormbase took 0.9052824974060059s
Accuracy | Check Datatype consistency for Bio2RDF::Wormbase took 0.7001149654388428s
Consistency | Disjoint class check for Bio2RDF::Wormbase took 0.42615842819213867s
Consistency | Check Misplaced properties for Bio2RDF::Wormbase took 65.13286995887756s
Consistency | Misplaced classes for Bio2RDF::Wormbase took 2.491225481033325s
Consistency | Check Ontology hijacking for Bio2RDF::Wormbase took 6.750638723373413s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Wormbase took 1.4313440322875977s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Wormbase took 61.67328357696533s
Conciseness | Check Extensional conciseness for Bio2RDF::Wormbase took 0.7229280471801758s
Conciseness | Check Intensional conciseness for Bio2RDF::Wormbase took 0.44629621505737305s
Security | Sign check for Bio2RDF::Wormbase took 0.27686595916748047s
Availability | Check URIs Dereferenciability for Bio2RDF::Wormbase took 13.306445837020874s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 0.38824963569641113s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.021314144134521484s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 8.654594421386719e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Wormbase took 22.20011568069458s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 1.3828277587890625e-05s
INFO | --- Analysis for bio2rdf-wormbase took 1081.2935526371002s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 0.6110365390777588s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 0.27321839332580566s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.020201444625854492s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 8.797645568847656e-05s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 1.1205673217773438e-05s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 3.2479774951934814s
Availability | SPARQL endpoint availability check for BioLOD for Protein Data Bank Japan took 4.935264587402344e-05s
Availability | VoID file availability check for BioLOD for Protein Data Bank Japan took 0.0006051063537597656s
Completeness | Calculation of interlinking completeness for BioLOD for Protein Data Bank Japan took 0.34990382194519043s
Reputation | Calculation of the PageRank for BioLOD for Protein Data Bank Japan took 0.020874500274658203s
Interlinking | Calculation of Degree of Connection for BioLOD for Protein Data Bank Japan took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for BioLOD for Protein Data Bank Japan took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for BioLOD for Protein Data Bank Japan took 4.4345855712890625e-05s
Believability | Calculation of trust value for BioLOD for Protein Data Bank Japan took 1.1205673217773438e-05s
INFO | --- Analysis for biolod-pdb took 7.922560453414917s
Availability | SPARQL endpoint availability check for BioModels RDF took 0.6524174213409424s
Availability | VoID file availability check for BioModels RDF took 0.0006334781646728516s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.28896093368530273s
Reputation | Calculation of the PageRank for BioModels RDF took 0.020606279373168945s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 4.0531158447265625e-05s
Believability | Calculation of trust value for BioModels RDF took 1.4781951904296875e-05s
INFO | --- Analysis for biomodels-rdf took 4.009052991867065s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.142908811569214s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0004050731658935547s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.3158082962036133s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.022273778915405273s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.4809112548828125e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.4066696166992188e-05s
INFO | --- Analysis for Biop took 6.106007099151611s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 8.940696716308594e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.29877543449401855s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.02239203453063965s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.814697265625e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.3113021850585938e-05s
INFO | --- Analysis for Bioportal took 2.759052276611328s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 8.702278137207031e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 0.0012691020965576172s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.285768985748291s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.020440340042114258s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.0008025169372558594s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006124973297119141s
Believability | Calculation of trust value for Amphibian gross anatomy took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-aao took 3.0449817180633545s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 0.00010013580322265625s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.0006470680236816406s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 0.3090400695800781s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.020829200744628906s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.00031065940856933594s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-aba took 3.007601261138916s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 9.274482727050781e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.0005991458892822266s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.2878708839416504s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.020857810974121094s
Interlinking | Calculation of Degree of Connection for Cancer Research and Management ACGT Master Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Cancer Research and Management ACGT Master Ontology took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0015442371368408203s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-acgt took 2.8200252056121826s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 8.821487426757812e-05s
Availability | VoID file availability check for Animal natural history and life history took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 0.2735171318054199s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.020420074462890625s
Interlinking | Calculation of Degree of Connection for Animal natural history and life history took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Animal natural history and life history took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.00033736228942871094s
Believability | Calculation of trust value for Animal natural history and life history took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-adw took 2.9066507816314697s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 8.869171142578125e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.0005929470062255859s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 0.28791093826293945s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.020795822143554688s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.0005145072937011719s
Believability | Calculation of trust value for Anatomical Entity Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-aeo took 2.8496787548065186s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 4.506111145019531e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 0.30677366256713867s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.02051234245300293s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0009672641754150391s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-aero took 2.8335046768188477s
Availability | SPARQL endpoint availability check for AI/RHEUM took 4.3392181396484375e-05s
Availability | VoID file availability check for AI/RHEUM took 0.0005967617034912109s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 0.30061793327331543s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.020778417587280273s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.0004258155822753906s
Believability | Calculation of trust value for AI/RHEUM took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-air took 2.8309266567230225s
Availability | SPARQL endpoint availability check for Amino Acid took 8.654594421386719e-05s
Availability | VoID file availability check for Amino Acid took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for Amino Acid took 0.31718921661376953s
Reputation | Calculation of the PageRank for Amino Acid took 0.022849082946777344s
Interlinking | Calculation of Degree of Connection for Amino Acid took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Amino Acid took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.00025844573974609375s
Believability | Calculation of trust value for Amino Acid took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-amino-acid took 2.985670328140259s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 9.012222290039062e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.2901310920715332s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.020737409591674805s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.0002989768981933594s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-apo took 2.9005990028381348s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 8.988380432128906e-05s
Availability | VoID file availability check for African Traditional Medicine took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 0.28342103958129883s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.020719528198242188s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.00025200843811035156s
Believability | Calculation of trust value for African Traditional Medicine took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-atmo took 2.913841485977173s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 8.797645568847656e-05s
Availability | VoID file availability check for Amphibian taxonomy took 0.0005924701690673828s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.29079508781433105s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.02064347267150879s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 9.417533874511719e-05s
Believability | Calculation of trust value for Amphibian taxonomy took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ato took 2.8628487586975098s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 4.7206878662109375e-05s
Availability | VoID file availability check for BioAssay Ontology took 0.0006494522094726562s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 0.30753469467163086s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.020720481872558594s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.0013599395751953125s
Believability | Calculation of trust value for BioAssay Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-bao took 2.849822998046875s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 8.726119995117188e-05s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 0.29770445823669434s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.020463228225708008s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.00038242340087890625s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 2.8690881729125977s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 9.250640869140625e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.0005490779876708984s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.2888481616973877s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.02038860321044922s
Interlinking | Calculation of Degree of Connection for Breast Cancer Grading Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Breast Cancer Grading Ontology took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.0003590583801269531s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-bcgo took 2.8848867416381836s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 9.34600830078125e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.2887558937072754s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.020993471145629883s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.0015208721160888672s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-bdo took 2.8808298110961914s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 8.845329284667969e-05s
Availability | VoID file availability check for Basic Formal Ontology took 0.0005273818969726562s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.2926909923553467s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.020797252655029297s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0005137920379638672s
Believability | Calculation of trust value for Basic Formal Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-bfo took 2.8458797931671143s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 0.00010228157043457031s
Availability | VoID file availability check for Bleeding History Phenotype took 0.0009624958038330078s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.2865777015686035s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.0229341983795166s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0007572174072265625s
Believability | Calculation of trust value for Bleeding History Phenotype took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-bho took 2.8585917949676514s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 9.322166442871094e-05s
Availability | VoID file availability check for Bilateria anatomy took 0.0005896091461181641s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.27770519256591797s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.020335674285888672s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.0004584789276123047s
Believability | Calculation of trust value for Bilateria anatomy took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-bila took 2.920809507369995s
Availability | SPARQL endpoint availability check for BIRNLex took 4.6253204345703125e-05s
Availability | VoID file availability check for BIRNLex took 0.0005581378936767578s
Completeness | Calculation of interlinking completeness for BIRNLex took 0.29041218757629395s
Reputation | Calculation of the PageRank for BIRNLex took 0.021381855010986328s
Interlinking | Calculation of Degree of Connection for BIRNLex took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for BIRNLex took 0.0007872581481933594s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.001519918441772461s
Believability | Calculation of trust value for BIRNLex took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-birnlex took 2.8595147132873535s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.649162292480469e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.2987964153289795s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020505666732788086s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007996559143066406s
Believability | Calculation of trust value for Gene Regulation Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-bootstrep took 2.8313496112823486s
Availability | SPARQL endpoint availability check for BioPAX took 9.34600830078125e-05s
Availability | VoID file availability check for BioPAX took 0.0006082057952880859s
Completeness | Calculation of interlinking completeness for BioPAX took 0.2965667247772217s
Reputation | Calculation of the PageRank for BioPAX took 0.02036452293395996s
Interlinking | Calculation of Degree of Connection for BioPAX took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for BioPAX took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for BioPAX took 0.00010180473327636719s
Believability | Calculation of trust value for BioPAX took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-bp took 2.8834104537963867s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.00034117698669433594s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.29667043685913086s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.02048802375793457s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.0003273487091064453s
Believability | Calculation of trust value for Biomedical Resource Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-bro_x1 took 2.8694052696228027s
Availability | SPARQL endpoint availability check for Spatial Ontology took 4.553794860839844e-05s
Availability | VoID file availability check for Spatial Ontology took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 0.2755007743835449s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.02042222023010254s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.00022339820861816406s
Believability | Calculation of trust value for Spatial Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-bspo took 2.9784886837005615s
Availability | SPARQL endpoint availability check for BioTop took 4.5299530029296875e-05s
Availability | VoID file availability check for BioTop took 0.0005328655242919922s
Completeness | Calculation of interlinking completeness for BioTop took 0.30771517753601074s
Reputation | Calculation of the PageRank for BioTop took 0.02046680450439453s
Interlinking | Calculation of Degree of Connection for BioTop took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for BioTop took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006518363952636719s
Believability | Calculation of trust value for BioTop took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-bt took 2.9117355346679688s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 9.107589721679688e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.28064727783203125s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.021148681640625s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BRENDA tissue / enzyme source took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0008893013000488281s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-bto took 2.893073081970215s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 9.608268737792969e-05s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.0012390613555908203s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.3419837951660156s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.021578550338745117s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.0018644332885742188s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-canco took 3.2692153453826904s
Availability | SPARQL endpoint availability check for CAO took 8.96453857421875e-05s
Availability | VoID file availability check for CAO took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for CAO took 0.29061388969421387s
Reputation | Calculation of the PageRank for CAO took 0.020606040954589844s
Interlinking | Calculation of Degree of Connection for CAO took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for CAO took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0006418228149414062s
Believability | Calculation of trust value for CAO took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-cao took 2.8620059490203857s
Availability | SPARQL endpoint availability check for CareLex took 8.893013000488281e-05s
Availability | VoID file availability check for CareLex took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for CareLex took 0.306837797164917s
Reputation | Calculation of the PageRank for CareLex took 0.02201390266418457s
Interlinking | Calculation of Degree of Connection for CareLex took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CareLex took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for CareLex took 5.459785461425781e-05s
Believability | Calculation of trust value for CareLex took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-carelex took 2.9967644214630127s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 9.584426879882812e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 0.0005536079406738281s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.29975438117980957s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.0217132568359375s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.0009632110595703125s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0009217262268066406s
Believability | Calculation of trust value for Cell Cycle Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-cco took 2.8445186614990234s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 8.988380432128906e-05s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 0.0005803108215332031s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.2983384132385254s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.021535873413085938s
Interlinking | Calculation of Degree of Connection for Comparative Data Analysis Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Comparative Data Analysis Ontology took 0.0007970333099365234s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.000293731689453125s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-cdao took 2.7568962574005127s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 8.7738037109375e-05s
Availability | VoID file availability check for Chemical entities of biological interest took 0.0005106925964355469s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.2979860305786133s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.020583629608154297s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0008051395416259766s
Believability | Calculation of trust value for Chemical entities of biological interest took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-chebi took 2.830073833465576s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 4.458427429199219e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.00036525726318359375s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.2803184986114502s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.021464824676513672s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.0002503395080566406s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-chem2bio2owl took 2.80253005027771s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 9.202957153320312e-05s
Availability | VoID file availability check for Chemical Information Ontology took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.2887856960296631s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.02077507972717285s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0007619857788085938s
Believability | Calculation of trust value for Chemical Information Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-cheminf took 2.9180288314819336s
Availability | SPARQL endpoint availability check for Cell type took 9.298324584960938e-05s
Availability | VoID file availability check for Cell type took 0.0005025863647460938s
Completeness | Calculation of interlinking completeness for Cell type took 0.2840592861175537s
Reputation | Calculation of the PageRank for Cell type took 0.02052021026611328s
Interlinking | Calculation of Degree of Connection for Cell type took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cell type took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.0003848075866699219s
Believability | Calculation of trust value for Cell type took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-cl took 2.737169027328491s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 8.940696716308594e-05s
Availability | VoID file availability check for Cell Line Ontology took 0.0006070137023925781s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.396334171295166s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.021008968353271484s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0008404254913330078s
Believability | Calculation of trust value for Cell Line Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-clo took 3.015712261199951s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 8.869171142578125e-05s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 0.29065823554992676s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.021340370178222656s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.00018858909606933594s
Believability | Calculation of trust value for Clinical Measurement Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-cmo took 2.9128949642181396s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 0.3018007278442383s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.02245354652404785s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.00023031234741210938s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-cno took 2.904494285583496s
Availability | SPARQL endpoint availability check for Wheat trait took 4.506111145019531e-05s
Availability | VoID file availability check for Wheat trait took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for Wheat trait took 0.2924387454986572s
Reputation | Calculation of the PageRank for Wheat trait took 0.020626068115234375s
Interlinking | Calculation of Degree of Connection for Wheat trait took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Wheat trait took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 5.984306335449219e-05s
Believability | Calculation of trust value for Wheat trait took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-co_wheat took 2.889174461364746s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 9.059906005859375e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.0004620552062988281s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.2961878776550293s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.020476579666137695s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.0003476142883300781s
Believability | Calculation of trust value for Cognitive Atlas took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-cogat took 2.768965482711792s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.2903895378112793s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.02062249183654785s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0007708072662353516s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-cogpo took 2.814136266708374s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 6.771087646484375e-05s
Availability | VoID file availability check for Current Procedural Terminology took 0.0005495548248291016s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.27730846405029297s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.020719528198242188s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.0004532337188720703s
Believability | Calculation of trust value for Current Procedural Terminology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-cpt took 2.8408284187316895s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 8.821487426757812e-05s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.0005621910095214844s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 0.33170413970947266s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.020951032638549805s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.0017938613891601562s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-csp took 3.322617292404175s
Availability | SPARQL endpoint availability check for COSTART took 9.179115295410156e-05s
Availability | VoID file availability check for COSTART took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for COSTART took 0.28409886360168457s
Reputation | Calculation of the PageRank for COSTART took 0.021163463592529297s
Interlinking | Calculation of Degree of Connection for COSTART took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for COSTART took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0009815692901611328s
Believability | Calculation of trust value for COSTART took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-cst took 2.8544299602508545s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 8.940696716308594e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 0.0013899803161621094s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.28721165657043457s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.020884990692138672s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.0005247592926025391s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-ctcae took 2.828517436981201s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 8.797645568847656e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.000583648681640625s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.2921569347381592s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.020489215850830078s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.0004744529724121094s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-ctx took 2.9199163913726807s
Availability | SPARQL endpoint availability check for Dendritic cell took 9.1552734375e-05s
Availability | VoID file availability check for Dendritic cell took 0.0005867481231689453s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.27431702613830566s
Reputation | Calculation of the PageRank for Dendritic cell took 0.020888090133666992s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.0003070831298828125s
Believability | Calculation of trust value for Dendritic cell took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-dc_cl took 2.801255941390991s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 8.893013000488281e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 0.28679800033569336s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.02078843116760254s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 9.1552734375e-05s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-ddanat took 2.9124135971069336s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 4.839897155761719e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.0005774497985839844s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.2996952533721924s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.020581722259521484s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.0009691715240478516s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-ddi took 2.841766595840454s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 8.821487426757812e-05s
Availability | VoID file availability check for Diagnostic Ontology took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.3941187858581543s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.022755146026611328s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 8.96453857421875e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-diagnosticont took 2.932387351989746s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 8.869171142578125e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.2770042419433594s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.02161240577697754s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.00017523765563964844s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-dikb-evidence took 2.8286736011505127s
Availability | SPARQL endpoint availability check for Human disease ontology took 9.226799011230469e-05s
Availability | VoID file availability check for Human disease ontology took 0.0012583732604980469s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.2909693717956543s
Reputation | Calculation of the PageRank for Human disease ontology took 0.021303176879882812s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Human disease ontology took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0006585121154785156s
Believability | Calculation of trust value for Human disease ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-doid took 2.7996842861175537s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 0.0005841255187988281s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 0.2813539505004883s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.02050018310546875s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0008225440979003906s
Believability | Calculation of trust value for Electrocardiography Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-ecg took 2.813405990600586s
Availability | SPARQL endpoint availability check for Evidence codes took 5.817413330078125e-05s
Availability | VoID file availability check for Evidence codes took 0.0005517005920410156s
Completeness | Calculation of interlinking completeness for Evidence codes took 0.2989082336425781s
Reputation | Calculation of the PageRank for Evidence codes took 0.02205634117126465s
Interlinking | Calculation of Degree of Connection for Evidence codes took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Evidence codes took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 3.504753112792969e-05s
Believability | Calculation of trust value for Evidence codes took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-eco took 2.8144302368164062s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 0.0005097389221191406s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.32613301277160645s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.020615339279174805s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.0018014907836914062s
Believability | Calculation of trust value for Experimental Factor Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-efo took 3.290207624435425s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 4.57763671875e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 0.2866044044494629s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.02072882652282715s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.0011987686157226562s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-ehda took 2.862598419189453s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 0.0001087188720703125s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.0006213188171386719s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.29799842834472656s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.020611047744750977s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007195472717285156s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ehdaa took 2.850057601928711s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 9.274482727050781e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.3001234531402588s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.020598649978637695s
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.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0005383491516113281s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-ehdaa2 took 2.863751173019409s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 8.654594421386719e-05s
Availability | VoID file availability check for Mouse gross anatomy and development took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 0.285236120223999s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.022137880325317383s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 3.314018249511719e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-emap took 2.897834062576294s
Availability | SPARQL endpoint availability check for Environment Ontology took 9.012222290039062e-05s
Availability | VoID file availability check for Environment Ontology took 0.0007121562957763672s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.29489564895629883s
Reputation | Calculation of the PageRank for Environment Ontology took 0.021260499954223633s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.00042891502380371094s
Believability | Calculation of trust value for Environment Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-envo took 2.936840295791626s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 0.00010895729064941406s
Availability | VoID file availability check for Plant environmental conditions took 0.0013244152069091797s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.28451967239379883s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.021719932556152344s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.00030684471130371094s
Believability | Calculation of trust value for Plant environmental conditions took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-eo took 2.895296096801758s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 8.893013000488281e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.2869555950164795s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.02099013328552246s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0008230209350585938s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.0012602806091308594s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-ep took 2.878592014312744s
Availability | SPARQL endpoint availability check for Epilepsy took 0.00011348724365234375s
Availability | VoID file availability check for Epilepsy took 0.0006310939788818359s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.3022294044494629s
Reputation | Calculation of the PageRank for Epilepsy took 0.022225141525268555s
Interlinking | Calculation of Degree of Connection for Epilepsy took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Epilepsy took 0.0009989738464355469s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.0001742839813232422s
Believability | Calculation of trust value for Epilepsy took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-epileponto took 2.7422404289245605s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 9.250640869140625e-05s
Availability | VoID file availability check for eagle-i research resource ontology took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.2965421676635742s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.021762371063232422s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.0011620521545410156s
Believability | Calculation of trust value for eagle-i research resource ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-ero took 2.8224291801452637s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 9.369850158691406e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.0006270408630371094s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 0.28161072731018066s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.02071547508239746s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.0011188983917236328s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-ev took 2.9427170753479004s
Availability | SPARQL endpoint availability check for ExO took 5.221366882324219e-05s
Availability | VoID file availability check for ExO took 0.0005397796630859375s
Completeness | Calculation of interlinking completeness for ExO took 0.3104069232940674s
Reputation | Calculation of the PageRank for ExO took 0.020594120025634766s
Interlinking | Calculation of Degree of Connection for ExO took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for ExO took 0.0008642673492431641s
Interlinking | Calculation of Clustering coefficient for ExO took 0.0003170967102050781s
Believability | Calculation of trust value for ExO took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-exo took 2.8635730743408203s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 0.00010323524475097656s
Availability | VoID file availability check for Fungal gross anatomy took 0.0005934238433837891s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 0.28554558753967285s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.020956993103027344s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.0001475811004638672s
Believability | Calculation of trust value for Fungal gross anatomy took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-fao took 2.8322370052337646s
Availability | SPARQL endpoint availability check for Biological imaging methods took 4.649162292480469e-05s
Availability | VoID file availability check for Biological imaging methods took 0.0006220340728759766s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.29146409034729004s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.020572900772094727s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.00020241737365722656s
Believability | Calculation of trust value for Biological imaging methods took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-fbbi took 2.794874668121338s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 9.369850158691406e-05s
Availability | VoID file availability check for Drosophila gross anatomy took 0.0005342960357666016s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 0.28624939918518066s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.026851177215576172s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0007083415985107422s
Believability | Calculation of trust value for Drosophila gross anatomy took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-fbbt took 3.0138697624206543s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 9.012222290039062e-05s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.0005528926849365234s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.2819709777832031s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.029577016830444336s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.0006015300750732422s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-fbcv took 2.7859537601470947s
Availability | SPARQL endpoint availability check for Drosophila development took 0.0001461505889892578s
Availability | VoID file availability check for Drosophila development took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.30235838890075684s
Reputation | Calculation of the PageRank for Drosophila development took 0.0211336612701416s
Interlinking | Calculation of Degree of Connection for Drosophila development took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Drosophila development took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.982948303222656e-05s
Believability | Calculation of trust value for Drosophila development took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-fbdv took 2.821262836456299s
Availability | SPARQL endpoint availability check for Fly taxonomy took 8.869171142578125e-05s
Availability | VoID file availability check for Fly taxonomy took 0.0008568763732910156s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.27770233154296875s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.022169828414916992s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.0004456043243408203s
Believability | Calculation of trust value for Fly taxonomy took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-fbsp took 2.8825860023498535s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 9.751319885253906e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.000568389892578125s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.28600120544433594s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.020588159561157227s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.00024366378784179688s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-fda-meddevice took 2.87011456489563s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 9.059906005859375e-05s
Availability | VoID file availability check for Family Health History Ontology took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 0.31030988693237305s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.021032094955444336s
Interlinking | Calculation of Degree of Connection for Family Health History Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Family Health History Ontology took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.0004355907440185547s
Believability | Calculation of trust value for Family Health History Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-fhho took 2.8877766132354736s
Availability | SPARQL endpoint availability check for Influenza Ontology took 9.584426879882812e-05s
Availability | VoID file availability check for Influenza Ontology took 0.0013747215270996094s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.2889728546142578s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.020502567291259766s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.001100778579711914s
Believability | Calculation of trust value for Influenza Ontology took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-flu took 2.7893168926239014s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 4.553794860839844e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.2998228073120117s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.0207059383392334s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 7.033348083496094e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-fma took 2.858442544937134s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 0.00010442733764648438s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 0.2876012325286865s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.02066183090209961s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.0001404285430908203s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-fypo took 2.9228999614715576s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 9.465217590332031e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 0.0006051063537597656s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.30332064628601074s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.021921157836914062s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 9.679794311523438e-05s
Believability | Calculation of trust value for GeoSpecies Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-geospecies took 2.8883745670318604s
Availability | SPARQL endpoint availability check for General Formal Ontology took 0.00010442733764648438s
Availability | VoID file availability check for General Formal Ontology took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.30780649185180664s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.0205991268157959s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0007994174957275391s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.0001914501190185547s
Believability | Calculation of trust value for General Formal Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-gfo took 2.9172825813293457s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 9.274482727050781e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.000579833984375s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.28301572799682617s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.02057504653930664s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.0006709098815917969s
Believability | Calculation of trust value for General Formal Ontology: Biology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-gfo-bio took 2.893254041671753s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 9.107589721679688e-05s
Availability | VoID file availability check for Gene Ontology Extension took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 0.2736685276031494s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.022614002227783203s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0009515285491943359s
Believability | Calculation of trust value for Gene Ontology Extension took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-go_x1 took 2.7631728649139404s
Availability | SPARQL endpoint availability check for Gene Ontology took 9.608268737792969e-05s
Availability | VoID file availability check for Gene Ontology took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.2957589626312256s
Reputation | Calculation of the PageRank for Gene Ontology took 0.021576881408691406s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0008871555328369141s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0009746551513671875s
Believability | Calculation of trust value for Gene Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-go_x2 took 2.8525609970092773s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 4.6253204345703125e-05s
Availability | VoID file availability check for Cereal Plant Development took 0.0005986690521240234s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 0.29927635192871094s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.022092819213867188s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0007863044738769531s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 3.695487976074219e-05s
Believability | Calculation of trust value for Cereal Plant Development took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-gro took 2.8236424922943115s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 9.131431579589844e-05s
Availability | VoID file availability check for Cereal plant gross anatomy took 0.0005924701690673828s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 0.2992558479309082s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.02059483528137207s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.0004425048828125s
Believability | Calculation of trust value for Cereal plant gross anatomy took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-gro_x1 took 2.7711455821990967s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 8.916854858398438e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.27921009063720703s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020858287811279297s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007548332214355469s
Believability | Calculation of trust value for Gene Regulation Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-gro_x2 took 2.9513392448425293s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 4.744529724121094e-05s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.0005686283111572266s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.28970813751220703s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.020951032638549805s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0005674362182617188s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-hao took 2.867605209350586s
Availability | SPARQL endpoint availability check for HCPCS took 5.054473876953125e-05s
Availability | VoID file availability check for HCPCS took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for HCPCS took 0.2968599796295166s
Reputation | Calculation of the PageRank for HCPCS took 0.020930767059326172s
Interlinking | Calculation of Degree of Connection for HCPCS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for HCPCS took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.00022935867309570312s
Believability | Calculation of trust value for HCPCS took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-hcpcs took 2.972414016723633s
Availability | SPARQL endpoint availability check for Health Level Seven took 8.940696716308594e-05s
Availability | VoID file availability check for Health Level Seven took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for Health Level Seven took 0.2797281742095947s
Reputation | Calculation of the PageRank for Health Level Seven took 0.020882844924926758s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.0012996196746826172s
Believability | Calculation of trust value for Health Level Seven took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-hl7 took 2.8474884033203125s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 0.000125885009765625s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.0005342960357666016s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.2930111885070801s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.020570755004882812s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.0003502368927001953s
Believability | Calculation of trust value for HEALTH_INDICATORS took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-hlth_indics took 2.802415132522583s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 9.512901306152344e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.0005633831024169922s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.2898707389831543s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.021044254302978516s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 3.62396240234375e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-hom took 2.8409996032714844s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 4.696846008300781e-05s
Availability | VoID file availability check for HOM-HARVARD took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 0.2889070510864258s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.020917892456054688s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 3.337860107421875e-05s
Believability | Calculation of trust value for HOM-HARVARD took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-hom_harvard took 2.879319667816162s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 0.00010538101196289062s
Availability | VoID file availability check for Human Phenotype Ontology took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.2790963649749756s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.020713090896606445s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0006899833679199219s
Believability | Calculation of trust value for Human Phenotype Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-hp_x1 took 2.770557403564453s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 9.202957153320312e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 0.28729963302612305s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.02065300941467285s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.0010273456573486328s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-hpio took 2.8650667667388916s
Availability | SPARQL endpoint availability check for HUGO took 9.059906005859375e-05s
Availability | VoID file availability check for HUGO took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for HUGO took 0.278245210647583s
Reputation | Calculation of the PageRank for HUGO took 0.02068805694580078s
Interlinking | Calculation of Degree of Connection for HUGO took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for HUGO took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for HUGO took 8.130073547363281e-05s
Believability | Calculation of trust value for HUGO took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-hugo took 2.8572580814361572s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 6.079673767089844e-05s
Availability | VoID file availability check for Information Artifact Ontology took 0.000579833984375s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 0.30213046073913574s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.020931482315063477s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0006780624389648438s
Believability | Calculation of trust value for Information Artifact Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-iao took 2.9435932636260986s
Availability | SPARQL endpoint availability check for ICD10 took 5.459785461425781e-05s
Availability | VoID file availability check for ICD10 took 0.0006291866302490234s
Completeness | Calculation of interlinking completeness for ICD10 took 0.28460025787353516s
Reputation | Calculation of the PageRank for ICD10 took 0.023869752883911133s
Interlinking | Calculation of Degree of Connection for ICD10 took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for ICD10 took 0.0012111663818359375s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.001024007797241211s
Believability | Calculation of trust value for ICD10 took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-icd10 took 2.84019136428833s
Availability | SPARQL endpoint availability check for ICD10CM took 0.00010156631469726562s
Availability | VoID file availability check for ICD10CM took 0.0004978179931640625s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.27675795555114746s
Reputation | Calculation of the PageRank for ICD10CM took 0.02051854133605957s
Interlinking | Calculation of Degree of Connection for ICD10CM took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ICD10CM took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0006246566772460938s
Believability | Calculation of trust value for ICD10CM took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-icd10cm took 2.7912518978118896s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 9.393692016601562e-05s
Availability | VoID file availability check for ICD-10-PCS took 0.0005793571472167969s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 0.30234384536743164s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.022843599319458008s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.00015878677368164062s
Believability | Calculation of trust value for ICD-10-PCS took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-icd10pcs took 2.8259470462799072s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 5.435943603515625e-05s
Availability | VoID file availability check for International Classification of Diseases took 0.00044345855712890625s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 0.2780907154083252s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.020728588104248047s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0006415843963623047s
Believability | Calculation of trust value for International Classification of Diseases took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-icd9cm took 2.7383360862731934s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 9.584426879882812e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.0005750656127929688s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.27838873863220215s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.02105259895324707s
Interlinking | Calculation of Degree of Connection for International Classification of Functioning, Disability and Health (ICF) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for International Classification of Functioning, Disability and Health (ICF) took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.0004825592041015625s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-icf_x1 took 2.888810157775879s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 6.556510925292969e-05s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 0.29122400283813477s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.020798921585083008s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.0008692741394042969s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.0013554096221923828s
Believability | Calculation of trust value for International Classification for Nursing Practice took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-icnp took 2.965573787689209s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 4.57763671875e-05s
Availability | VoID file availability check for International Classification of Primary Care took 0.0005981922149658203s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 0.29210567474365234s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.02082371711730957s
Interlinking | Calculation of Degree of Connection for International Classification of Primary Care took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for International Classification of Primary Care took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.0004572868347167969s
Believability | Calculation of trust value for International Classification of Primary Care took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-icpc took 2.819601058959961s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 8.96453857421875e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.2768745422363281s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.020953893661499023s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0008778572082519531s
Believability | Calculation of trust value for ICPC-2 PLUS took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-icpc2p took 2.7944741249084473s
Availability | SPARQL endpoint availability check for ICPS Network took 9.226799011230469e-05s
Availability | VoID file availability check for ICPS Network took 0.00045371055603027344s
Completeness | Calculation of interlinking completeness for ICPS Network took 0.27088332176208496s
Reputation | Calculation of the PageRank for ICPS Network took 0.02068471908569336s
Interlinking | Calculation of Degree of Connection for ICPS Network took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ICPS Network took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.0002353191375732422s
Believability | Calculation of trust value for ICPS Network took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-icps took 2.8020575046539307s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 4.792213439941406e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 0.0005943775177001953s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.2730739116668701s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.02074575424194336s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0009090900421142578s
Believability | Calculation of trust value for Infectious Disease Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ido took 2.7842626571655273s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 9.036064147949219e-05s
Availability | VoID file availability check for Brucellosis Ontology took 0.0006120204925537109s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.29618406295776367s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.020561933517456055s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0011844635009765625s
Believability | Calculation of trust value for Brucellosis Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-idobru took 2.8865272998809814s
Availability | SPARQL endpoint availability check for Malaria Ontology took 5.817413330078125e-05s
Availability | VoID file availability check for Malaria Ontology took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.2752537727355957s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.020828723907470703s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.0013306140899658203s
Believability | Calculation of trust value for Malaria Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-idomal took 2.885256767272949s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 8.702278137207031e-05s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.0006849765777587891s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 0.3007030487060547s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.02065443992614746s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.00031375885009765625s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-iev took 2.7946770191192627s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 9.179115295410156e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.0006020069122314453s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.28153181076049805s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.02288532257080078s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.0007970333099365234s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.00017261505126953125s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-imgt took 2.9389266967773438s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 9.226799011230469e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.0005342960357666016s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.3008410930633545s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.020594120025634766s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.000579833984375s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-imr took 2.848750591278076s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 6.0558319091796875e-05s
Availability | VoID file availability check for Interaction Network Ontology took 0.0005695819854736328s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.27184605598449707s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.02219390869140625s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0008711814880371094s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0008680820465087891s
Believability | Calculation of trust value for Interaction Network Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-ino took 2.7670705318450928s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 4.673004150390625e-05s
Availability | VoID file availability check for Hewan Invertebrata took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.31447482109069824s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.020772933959960938s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 4.0531158447265625e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-invertebrata took 2.894953489303589s
Availability | SPARQL endpoint availability check for IxnO took 9.584426879882812e-05s
Availability | VoID file availability check for IxnO took 0.0005795955657958984s
Completeness | Calculation of interlinking completeness for IxnO took 0.2703113555908203s
Reputation | Calculation of the PageRank for IxnO took 0.020784378051757812s
Interlinking | Calculation of Degree of Connection for IxnO took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for IxnO took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.00020933151245117188s
Believability | Calculation of trust value for IxnO took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-ixno took 2.8912289142608643s
Availability | SPARQL endpoint availability check for SysMO-JERM took 9.226799011230469e-05s
Availability | VoID file availability check for SysMO-JERM took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 0.28914666175842285s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.020476102828979492s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.000385284423828125s
Believability | Calculation of trust value for SysMO-JERM took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-jerm took 2.7685954570770264s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 9.465217590332031e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.2753109931945801s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.02055191993713379s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 3.504753112792969e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-kisao took 2.7904090881347656s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 9.465217590332031e-05s
Availability | VoID file availability check for Loggerhead nesting took 0.0006291866302490234s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.28575730323791504s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.020532846450805664s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.00021314620971679688s
Believability | Calculation of trust value for Loggerhead nesting took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-lhn took 2.7955713272094727s
Availability | SPARQL endpoint availability check for Lipid Ontology took 8.273124694824219e-05s
Availability | VoID file availability check for Lipid Ontology took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 0.28858447074890137s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.020560026168823242s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.00021982192993164062s
Believability | Calculation of trust value for Lipid Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-lipro took 2.84478497505188s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 9.393692016601562e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.0005536079406738281s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.33461785316467285s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.022181034088134766s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.0018284320831298828s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-lnc took 3.32301926612854s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 0.00012230873107910156s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.0005629062652587891s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 0.28240156173706055s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.020786523818969727s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0006585121154785156s
Believability | Calculation of trust value for Mouse adult gross anatomy took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-ma took 2.8385074138641357s
Availability | SPARQL endpoint availability check for Multiple alignment took 4.553794860839844e-05s
Availability | VoID file availability check for Multiple alignment took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for Multiple alignment took 0.27387452125549316s
Reputation | Calculation of the PageRank for Multiple alignment took 0.020626068115234375s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.00021719932556152344s
Believability | Calculation of trust value for Multiple alignment took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-mao took 2.8132612705230713s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 8.726119995117188e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 0.0006458759307861328s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 0.2733592987060547s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.02333998680114746s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0006968975067138672s
Believability | Calculation of trust value for Minimal anatomical terminology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-mat took 2.884834051132202s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 8.797645568847656e-05s
Availability | VoID file availability check for Breast tissue cell lines took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.28287315368652344s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.021640777587890625s
Interlinking | Calculation of Degree of Connection for Breast tissue cell lines took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Breast tissue cell lines took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.0004239082336425781s
Believability | Calculation of trust value for Breast tissue cell lines took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-mcbcc took 2.8497464656829834s
Availability | SPARQL endpoint availability check for Cell line ontology took 6.890296936035156e-05s
Availability | VoID file availability check for Cell line ontology took 0.0007102489471435547s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.29218578338623047s
Reputation | Calculation of the PageRank for Cell line ontology took 0.020506858825683594s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0007607936859130859s
Believability | Calculation of trust value for Cell line ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-mccl took 2.918458938598633s
Availability | SPARQL endpoint availability check for Cell line ontology took 5.364418029785156e-05s
Availability | VoID file availability check for Cell line ontology took 0.0007011890411376953s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.2989509105682373s
Reputation | Calculation of the PageRank for Cell line ontology took 0.022423982620239258s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0014603137969970703s
Believability | Calculation of trust value for Cell line ontology took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-mccl_x1 took 2.8538384437561035s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 4.553794860839844e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.30217480659484863s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.02097320556640625s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.0002548694610595703s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-mcv took 2.833529472351074s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 0.0001232624053955078s
Availability | VoID file availability check for Master Drug Data Base took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 0.28969478607177734s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.02071070671081543s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.0008342266082763672s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.00020003318786621094s
Believability | Calculation of trust value for Master Drug Data Base took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-mddb took 2.783813714981079s
Availability | SPARQL endpoint availability check for MedDRA took 4.553794860839844e-05s
Availability | VoID file availability check for MedDRA took 0.0006101131439208984s
Completeness | Calculation of interlinking completeness for MedDRA took 0.28942084312438965s
Reputation | Calculation of the PageRank for MedDRA took 0.02076578140258789s
Interlinking | Calculation of Degree of Connection for MedDRA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MedDRA took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.0011506080627441406s
Believability | Calculation of trust value for MedDRA took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-mdr took 2.892719030380249s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 9.34600830078125e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.00034356117248535156s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.2907123565673828s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.02082967758178711s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0009214878082275391s
Believability | Calculation of trust value for MedlinePlus Health Topics took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-medlineplus took 2.9205665588378906s
Availability | SPARQL endpoint availability check for MeGO took 8.797645568847656e-05s
Availability | VoID file availability check for MeGO took 0.0006995201110839844s
Completeness | Calculation of interlinking completeness for MeGO took 0.29940366744995117s
Reputation | Calculation of the PageRank for MeGO took 0.020726919174194336s
Interlinking | Calculation of Degree of Connection for MeGO took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for MeGO took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.00015974044799804688s
Believability | Calculation of trust value for MeGO took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-mego took 2.9573118686676025s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 4.696846008300781e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 0.0006859302520751953s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 0.3554666042327881s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.02238607406616211s
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.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.0019006729125976562s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-mesh-owl took 3.3594794273376465s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 0.00012874603271484375s
Availability | VoID file availability check for Mental Functioning Ontology took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 0.2936720848083496s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.02061915397644043s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0006864070892333984s
Believability | Calculation of trust value for Mental Functioning Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-mf took 2.881222724914551s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 9.202957153320312e-05s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.0006196498870849609s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 0.2899332046508789s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.021099328994750977s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0005559921264648438s
Believability | Calculation of trust value for Medaka fish anatomy and development took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-mfo took 2.773873805999756s
Availability | SPARQL endpoint availability check for Emotion Ontology took 8.916854858398438e-05s
Availability | VoID file availability check for Emotion Ontology took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 0.2770388126373291s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.021717548370361328s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0007836818695068359s
Believability | Calculation of trust value for Emotion Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-mfoem took 2.9254350662231445s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 9.751319885253906e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.30630993843078613s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.02167201042175293s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.00011157989501953125s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-mhc took 2.791954278945923s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 9.608268737792969e-05s
Availability | VoID file availability check for Protein-protein interaction took 0.0005915164947509766s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.27927613258361816s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.020441055297851562s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0006742477416992188s
Believability | Calculation of trust value for Protein-protein interaction took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-mi took 2.8037726879119873s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 4.601478576660156e-05s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.0004582405090332031s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.2940254211425781s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.02045893669128418s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0007221698760986328s
Believability | Calculation of trust value for Mosquito insecticide resistance took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-miro took 2.747938394546509s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 4.5299530029296875e-05s
Availability | VoID file availability check for Measurement Method Ontology took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.3171980381011963s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.022411108016967773s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.00014543533325195312s
Believability | Calculation of trust value for Measurement Method Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-mmo took 2.838026762008667s
Availability | SPARQL endpoint availability check for MGED Ontology took 4.673004150390625e-05s
Availability | VoID file availability check for MGED Ontology took 0.0005772113800048828s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.28672194480895996s
Reputation | Calculation of the PageRank for MGED Ontology took 0.02075958251953125s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.0003993511199951172s
Believability | Calculation of trust value for MGED Ontology took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-mo took 2.8270251750946045s
Availability | SPARQL endpoint availability check for Protein modification took 4.458427429199219e-05s
Availability | VoID file availability check for Protein modification took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for Protein modification took 0.29615139961242676s
Reputation | Calculation of the PageRank for Protein modification took 0.023166179656982422s
Interlinking | Calculation of Degree of Connection for Protein modification took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Protein modification took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.0002434253692626953s
Believability | Calculation of trust value for Protein modification took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-mod took 2.7612133026123047s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 0.00010085105895996094s
Availability | VoID file availability check for Mammalian phenotype took 0.0004923343658447266s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 0.29784488677978516s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.020590543746948242s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0006930828094482422s
Believability | Calculation of trust value for Mammalian phenotype took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mp took 2.795029640197754s
Availability | SPARQL endpoint availability check for Mouse pathology took 9.131431579589844e-05s
Availability | VoID file availability check for Mouse pathology took 0.0005214214324951172s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.2926359176635742s
Reputation | Calculation of the PageRank for Mouse pathology took 0.02269268035888672s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Mouse pathology took 0.001085519790649414s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.0006265640258789062s
Believability | Calculation of trust value for Mouse pathology took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-mpath took 2.7042996883392334s
Availability | SPARQL endpoint availability check for Mass spectrometry took 9.417533874511719e-05s
Availability | VoID file availability check for Mass spectrometry took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.3007481098175049s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.02348470687866211s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0009202957153320312s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.00043511390686035156s
Believability | Calculation of trust value for Mass spectrometry took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-ms took 2.8576457500457764s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 4.410743713378906e-05s
Availability | VoID file availability check for Medical Subject Headings took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.3375513553619385s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.020687580108642578s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0008263587951660156s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.002053976058959961s
Believability | Calculation of trust value for Medical Subject Headings took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-msh took 3.2410669326782227s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 4.6253204345703125e-05s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.2851853370666504s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.020421981811523438s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.0001857280731201172s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-mthch took 2.7526493072509766s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 5.626678466796875e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.0005357265472412109s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 0.26679205894470215s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.020794153213500977s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0008244514465332031s
Believability | Calculation of trust value for Natural Products Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-natpro took 2.865142583847046s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 4.506111145019531e-05s
Availability | VoID file availability check for NCBI organismal classification took 0.0005438327789306641s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.27922534942626953s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.020379066467285156s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0008292198181152344s
Believability | Calculation of trust value for NCBI organismal classification took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-ncbitaxon took 2.7986886501312256s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 4.57763671875e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.00036835670471191406s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.33994388580322266s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.02079486846923828s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.00208282470703125s
Believability | Calculation of trust value for NCI Thesaurus took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ncit took 3.1828248500823975s
Availability | SPARQL endpoint availability check for National Drug Data File took 4.482269287109375e-05s
Availability | VoID file availability check for National Drug Data File took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.3133232593536377s
Reputation | Calculation of the PageRank for National Drug Data File took 0.02067422866821289s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for National Drug Data File took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0006365776062011719s
Believability | Calculation of trust value for National Drug Data File took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-nddf took 2.855126142501831s
Availability | SPARQL endpoint availability check for National Drug File took 9.465217590332031e-05s
Availability | VoID file availability check for National Drug File took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for National Drug File took 0.29746222496032715s
Reputation | Calculation of the PageRank for National Drug File took 0.02088165283203125s
Interlinking | Calculation of Degree of Connection for National Drug File took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for National Drug File took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.0012569427490234375s
Believability | Calculation of trust value for National Drug File took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-ndfrt took 2.8038246631622314s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 9.012222290039062e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.0005459785461425781s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.29489827156066895s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.02152228355407715s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.0012121200561523438s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-nemo_x1 took 2.9099950790405273s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 0.00013589859008789062s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.0005886554718017578s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.2726311683654785s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.020861148834228516s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer Ontology took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.000667572021484375s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-neomark took 2.7992584705352783s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 4.5299530029296875e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 0.0005347728729248047s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 0.31087684631347656s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.020867347717285156s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.00013875961303710938s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-neomarkontology took 2.913076877593994s
Availability | SPARQL endpoint availability check for NIFSTD took 9.274482727050781e-05s
Availability | VoID file availability check for NIFSTD took 0.0005545616149902344s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.33911681175231934s
Reputation | Calculation of the PageRank for NIFSTD took 0.020749568939208984s
Interlinking | Calculation of Degree of Connection for NIFSTD took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NIFSTD took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.0018873214721679688s
Believability | Calculation of trust value for NIFSTD took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-nif took 3.25811505317688s
Availability | SPARQL endpoint availability check for NIF Cell took 9.202957153320312e-05s
Availability | VoID file availability check for NIF Cell took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.2724742889404297s
Reputation | Calculation of the PageRank for NIF Cell took 0.020639896392822266s
Interlinking | Calculation of Degree of Connection for NIF Cell took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NIF Cell took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.0013375282287597656s
Believability | Calculation of trust value for NIF Cell took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-nif_cell took 2.879957675933838s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 5.125999450683594e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.0006449222564697266s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.29695701599121094s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.020607948303222656s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.0014727115631103516s
Believability | Calculation of trust value for NIF Dysfunction took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-nif_dysfunction took 2.9091925621032715s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 5.340576171875e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.0002875328063964844s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.2865276336669922s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.021125078201293945s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0005860328674316406s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-nigo took 2.7485029697418213s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 9.34600830078125e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 0.0005617141723632812s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.27680110931396484s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.02219676971435547s
Interlinking | Calculation of Degree of Connection for NMR-instrument specific component of metabolomics investigations took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for NMR-instrument specific component of metabolomics investigations took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0005495548248291016s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-nmr took 2.871365785598755s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 9.34600830078125e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 0.0005435943603515625s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.3251001834869385s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.020782947540283203s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.0007989406585693359s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.0001232624053955078s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-nonrctontology took 2.7766246795654297s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 4.5299530029296875e-05s
Availability | VoID file availability check for NanoParticle Ontology took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.3018524646759033s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.02059149742126465s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.0012269020080566406s
Believability | Calculation of trust value for NanoParticle Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-npo took 2.7951879501342773s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 9.274482727050781e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.30551671981811523s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.020542621612548828s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0007255077362060547s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-oae took 2.8121249675750732s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 5.435943603515625e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 0.2949199676513672s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.020647764205932617s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.00145721435546875s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-obi took 2.924199342727661s
Availability | SPARQL endpoint availability check for OBOE took 4.673004150390625e-05s
Availability | VoID file availability check for OBOE took 0.0005528926849365234s
Completeness | Calculation of interlinking completeness for OBOE took 0.2894258499145508s
Reputation | Calculation of the PageRank for OBOE took 0.021196842193603516s
Interlinking | Calculation of Degree of Connection for OBOE took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for OBOE took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.0001227855682373047s
Believability | Calculation of trust value for OBOE took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-oboe took 2.913163185119629s
Availability | SPARQL endpoint availability check for OBOE SBC took 5.078315734863281e-05s
Availability | VoID file availability check for OBOE SBC took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for OBOE SBC took 0.29398608207702637s
Reputation | Calculation of the PageRank for OBOE SBC took 0.020552635192871094s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0008094310760498047s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0008122920989990234s
Believability | Calculation of trust value for OBOE SBC took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-oboe-sbc took 2.848395586013794s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 0.00010347366333007812s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 0.28892064094543457s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.02078986167907715s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0006132125854492188s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-ocre took 2.756901264190674s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 4.601478576660156e-05s
Availability | VoID file availability check for Ontology for disease genetic investigation took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 0.28490281105041504s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.021029949188232422s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0009279251098632812s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-odgi took 2.827117443084717s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 4.482269287109375e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 0.27967381477355957s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.020318031311035156s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0008814334869384766s
Believability | Calculation of trust value for Ontology for Genetic Interval took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ogi took 2.797170400619507s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 9.107589721679688e-05s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 0.0006592273712158203s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 0.2865879535675049s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.02056145668029785s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.00032830238342285156s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-ogmd took 2.7819201946258545s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 9.5367431640625e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.2895810604095459s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.020546674728393555s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0006799697875976562s
Believability | Calculation of trust value for Ontology for General Medical Science took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-ogms took 2.8421213626861572s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 9.226799011230469e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.2775263786315918s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.020830869674682617s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.0011265277862548828s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-omim took 2.7761070728302s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 4.506111145019531e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 0.00044035911560058594s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.26926326751708984s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.020505905151367188s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.0003685951232910156s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-omit took 2.7586710453033447s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 8.7738037109375e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.3013439178466797s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.021001577377319336s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0006084442138671875s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-omrse took 2.6303489208221436s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 4.4345855712890625e-05s
Availability | VoID file availability check for Ontology of Data Mining took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.2841179370880127s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.021234512329101562s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.0007967948913574219s
Believability | Calculation of trust value for Ontology of Data Mining took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-ontodm took 2.884492874145508s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 4.649162292480469e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.0006012916564941406s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 0.2928328514099121s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.02126622200012207s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.00026106834411621094s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-ontodt took 2.8082237243652344s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 9.012222290039062e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.2748701572418213s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.020615339279174805s
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.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.0006709098815917969s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ontoorpha took 2.7909772396087646s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 8.845329284667969e-05s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 0.28853821754455566s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.021149396896362305s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0009622573852539062s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-opl took 2.876993417739868s
Availability | SPARQL endpoint availability check for Phenotypic quality took 8.678436279296875e-05s
Availability | VoID file availability check for Phenotypic quality took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.29052114486694336s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.020995616912841797s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0009467601776123047s
Believability | Calculation of trust value for Phenotypic quality took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-pato took 2.852912664413452s
Availability | SPARQL endpoint availability check for Physician Data Query took 4.9114227294921875e-05s
Availability | VoID file availability check for Physician Data Query took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.2828066349029541s
Reputation | Calculation of the PageRank for Physician Data Query took 0.021013498306274414s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Physician Data Query took 0.0008080005645751953s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0008738040924072266s
Believability | Calculation of trust value for Physician Data Query took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-pdq took 2.8581154346466064s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 4.5299530029296875e-05s
Availability | VoID file availability check for Pediatric Terminology took 0.0005278587341308594s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.2929973602294922s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.021206378936767578s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0008280277252197266s
Believability | Calculation of trust value for Pediatric Terminology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-pedterm took 2.8060288429260254s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 4.5299530029296875e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 0.2888615131378174s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.020794391632080078s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.00021195411682128906s
Believability | Calculation of trust value for Parasite Experiment Ontology took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-peo took 2.774407386779785s
Availability | SPARQL endpoint availability check for PHARE took 9.322166442871094e-05s
Availability | VoID file availability check for PHARE took 0.0005829334259033203s
Completeness | Calculation of interlinking completeness for PHARE took 0.2783222198486328s
Reputation | Calculation of the PageRank for PHARE took 0.02059483528137207s
Interlinking | Calculation of Degree of Connection for PHARE took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for PHARE took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006444454193115234s
Believability | Calculation of trust value for PHARE took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-phare took 2.888150453567505s
Availability | SPARQL endpoint availability check for PKO_Re took 4.57763671875e-05s
Availability | VoID file availability check for PKO_Re took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.27369070053100586s
Reputation | Calculation of the PageRank for PKO_Re took 0.020601511001586914s
Interlinking | Calculation of Degree of Connection for PKO_Re took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for PKO_Re took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.0001780986785888672s
Believability | Calculation of trust value for PKO_Re took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-pko took 2.870239734649658s
Availability | SPARQL endpoint availability check for PMA 2010 took 9.107589721679688e-05s
Availability | VoID file availability check for PMA 2010 took 0.0005433559417724609s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.29811716079711914s
Reputation | Calculation of the PageRank for PMA 2010 took 0.02094888687133789s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.00090789794921875s
Believability | Calculation of trust value for PMA 2010 took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-pma took 2.8406479358673096s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 9.322166442871094e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.0005433559417724609s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.2857551574707031s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.020923376083374023s
Interlinking | Calculation of Degree of Connection for Physical Medicine and Rehabilitation took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Physical Medicine and Rehabilitation took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.0001804828643798828s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-pmr took 2.8527870178222656s
Availability | SPARQL endpoint availability check for Plant Anatomy took 9.131431579589844e-05s
Availability | VoID file availability check for Plant Anatomy took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.2873725891113281s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.021570920944213867s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.0003876686096191406s
Believability | Calculation of trust value for Plant Anatomy took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-po took 2.818730354309082s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 8.7738037109375e-05s
Availability | VoID file availability check for Plant Growth and Development Stage took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.2905440330505371s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.020755529403686523s
Interlinking | Calculation of Degree of Connection for Plant Growth and Development Stage took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Plant Growth and Development Stage took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 7.748603820800781e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-po_x1 took 2.8322572708129883s
Availability | SPARQL endpoint availability check for Plant Ontology took 4.6253204345703125e-05s
Availability | VoID file availability check for Plant Ontology took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.31041574478149414s
Reputation | Calculation of the PageRank for Plant Ontology took 0.022388935089111328s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.0004334449768066406s
Believability | Calculation of trust value for Plant Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-po_x2 took 2.838927984237671s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 5.793571472167969e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.3011007308959961s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.021614789962768555s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0006561279296875s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-pr took 2.8828742504119873s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 9.632110595703125e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 0.0005435943603515625s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 0.2783510684967041s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.02270793914794922s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.00028443336486816406s
Believability | Calculation of trust value for Proteomics data and process provenance took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-propreo took 2.782731056213379s
Availability | SPARQL endpoint availability check for Pathway ontology took 8.821487426757812e-05s
Availability | VoID file availability check for Pathway ontology took 0.0006296634674072266s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.29315662384033203s
Reputation | Calculation of the PageRank for Pathway ontology took 0.021579980850219727s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Pathway ontology took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.0001494884490966797s
Believability | Calculation of trust value for Pathway ontology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-pw took 2.743258476257324s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 9.036064147949219e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.00029587745666503906s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.3558170795440674s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.021281719207763672s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 3.4809112548828125e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-qibo took 2.8503801822662354s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 4.792213439941406e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.34120917320251465s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.02077651023864746s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0018143653869628906s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-rcd took 3.348173141479492s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.2998824119567871s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.021312236785888672s
Interlinking | Calculation of Degree of Connection for Randomized Controlled Trials (RCT) Ontology took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Randomized Controlled Trials (RCT) Ontology took 0.0009205341339111328s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.00016498565673828125s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-rctontology took 2.8723740577697754s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 4.7206878662109375e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 0.0003151893615722656s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.284332275390625s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.020626544952392578s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 0.00010442733764648438s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-repo took 2.8389031887054443s
Availability | SPARQL endpoint availability check for Physico-chemical process took 5.1021575927734375e-05s
Availability | VoID file availability check for Physico-chemical process took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.2840449810028076s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.02133965492248535s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.000850677490234375s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.0002346038818359375s
Believability | Calculation of trust value for Physico-chemical process took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-rex took 2.7212817668914795s
Availability | SPARQL endpoint availability check for RadLex took 4.458427429199219e-05s
Availability | VoID file availability check for RadLex took 0.0005922317504882812s
Completeness | Calculation of interlinking completeness for RadLex took 0.28838586807250977s
Reputation | Calculation of the PageRank for RadLex took 0.02151799201965332s
Interlinking | Calculation of Degree of Connection for RadLex took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for RadLex took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.0015797615051269531s
Believability | Calculation of trust value for RadLex took 6.079673767089844e-05s
INFO | --- Analysis for bioportal-rid took 2.7928531169891357s
Availability | SPARQL endpoint availability check for RNA ontology took 4.649162292480469e-05s
Availability | VoID file availability check for RNA ontology took 0.0005800724029541016s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.2864532470703125s
Reputation | Calculation of the PageRank for RNA ontology took 0.02229452133178711s
Interlinking | Calculation of Degree of Connection for RNA ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for RNA ontology took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0005724430084228516s
Believability | Calculation of trust value for RNA ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-rnao took 2.8373897075653076s
Availability | SPARQL endpoint availability check for Role Ontology took 4.57763671875e-05s
Availability | VoID file availability check for Role Ontology took 0.000331878662109375s
Completeness | Calculation of interlinking completeness for Role Ontology took 0.2629971504211426s
Reputation | Calculation of the PageRank for Role Ontology took 0.021500587463378906s
Interlinking | Calculation of Degree of Connection for Role Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Role Ontology took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.00019788742065429688s
Believability | Calculation of trust value for Role Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-roleo took 2.839179039001465s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 9.202957153320312e-05s
Availability | VoID file availability check for Rat Strain Ontology took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.3137538433074951s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.02050638198852539s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.00017952919006347656s
Believability | Calculation of trust value for Rat Strain Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-rs took 2.8459527492523193s
Availability | SPARQL endpoint availability check for RxNORM took 4.458427429199219e-05s
Availability | VoID file availability check for RxNORM took 0.0006091594696044922s
Completeness | Calculation of interlinking completeness for RxNORM took 0.28353190422058105s
Reputation | Calculation of the PageRank for RxNORM took 0.020586490631103516s
Interlinking | Calculation of Degree of Connection for RxNORM took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for RxNORM took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0006220340728759766s
Believability | Calculation of trust value for RxNORM took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-rxnorm took 2.808311939239502s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 8.988380432128906e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.30078959465026855s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.02138662338256836s
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.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.0010275840759277344s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-sao took 2.8267524242401123s
Availability | SPARQL endpoint availability check for Systems Biology took 9.417533874511719e-05s
Availability | VoID file availability check for Systems Biology took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.2884657382965088s
Reputation | Calculation of the PageRank for Systems Biology took 0.020752429962158203s
Interlinking | Calculation of Degree of Connection for Systems Biology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Systems Biology took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.00047206878662109375s
Believability | Calculation of trust value for Systems Biology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-sbo took 3.057677984237671s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 0.00010275840759277344s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.0005974769592285156s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.2750720977783203s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.021101951599121094s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.00012540817260742188s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-sbro took 2.825923442840576s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 0.00017714500427246094s
Availability | VoID file availability check for Sleep Domain Ontology took 0.0005290508270263672s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.29778409004211426s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.02102947235107422s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.0013434886932373047s
Believability | Calculation of trust value for Sleep Domain Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-sdo took 2.8082616329193115s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 4.553794860839844e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.2874577045440674s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.02240467071533203s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0007925033569335938s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.0003478527069091797s
Believability | Calculation of trust value for Sample processing and separation techniques took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-sep took 2.832263708114624s
Availability | SPARQL endpoint availability check for Student Health Record took 9.012222290039062e-05s
Availability | VoID file availability check for Student Health Record took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.29265475273132324s
Reputation | Calculation of the PageRank for Student Health Record took 0.020577192306518555s
Interlinking | Calculation of Degree of Connection for Student Health Record took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Student Health Record took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.0004703998565673828s
Believability | Calculation of trust value for Student Health Record took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-shr took 2.8660662174224854s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 7.534027099609375e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.0006113052368164062s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 0.28873634338378906s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.022693395614624023s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.0012178421020507812s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-sio took 3.6324477195739746s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 9.083747863769531e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 0.28905487060546875s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.020836591720581055s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.00022482872009277344s
Believability | Calculation of trust value for Situation-Based Access Control took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-sitbac took 2.8377442359924316s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 4.506111145019531e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.0005817413330078125s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.31414294242858887s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.022130727767944336s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 1.52587890625e-05s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.0019598007202148438s
Believability | Calculation of trust value for SNOMED Clinical Terms took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-snomedct took 3.2244410514831543s
Availability | SPARQL endpoint availability check for SNP-Ontology took 8.940696716308594e-05s
Availability | VoID file availability check for SNP-Ontology took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.28140974044799805s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.020775794982910156s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0006973743438720703s
Believability | Calculation of trust value for SNP-Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-snpo took 2.8160994052886963s
Availability | SPARQL endpoint availability check for Sequence types and features took 9.918212890625e-05s
Availability | VoID file availability check for Sequence types and features took 0.0005784034729003906s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.27794742584228516s
Reputation | Calculation of the PageRank for Sequence types and features took 0.0208284854888916s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Sequence types and features took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0005974769592285156s
Believability | Calculation of trust value for Sequence types and features took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-so_x1 took 2.8134214878082275s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 7.224082946777344e-05s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 0.0006353855133056641s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.356569766998291s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.021230459213256836s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.0015943050384521484s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-sopharm took 3.337801933288574s
Availability | SPARQL endpoint availability check for SoyOntology took 4.553794860839844e-05s
Availability | VoID file availability check for SoyOntology took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.27654457092285156s
Reputation | Calculation of the PageRank for SoyOntology took 0.02095794677734375s
Interlinking | Calculation of Degree of Connection for SoyOntology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SoyOntology took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.0001304149627685547s
Believability | Calculation of trust value for SoyOntology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-soy took 2.9178478717803955s
Availability | SPARQL endpoint availability check for Spider Ontology took 4.601478576660156e-05s
Availability | VoID file availability check for Spider Ontology took 0.00028634071350097656s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.29857921600341797s
Reputation | Calculation of the PageRank for Spider Ontology took 0.02051258087158203s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.00031304359436035156s
Believability | Calculation of trust value for Spider Ontology took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-spd took 2.7682268619537354s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 5.698204040527344e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.2708287239074707s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.02083277702331543s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.0003044605255126953s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-spto took 2.784761905670166s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 9.059906005859375e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.0005862712860107422s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.28638267517089844s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.02053523063659668s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0008053779602050781s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.0004899501800537109s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-sso took 2.897503614425659s
Availability | SPARQL endpoint availability check for Software Ontology took 0.00011348724365234375s
Availability | VoID file availability check for Software Ontology took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.28763890266418457s
Reputation | Calculation of the PageRank for Software Ontology took 0.020611286163330078s
Interlinking | Calculation of Degree of Connection for Software Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Software Ontology took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.00041675567626953125s
Believability | Calculation of trust value for Software Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-swo took 2.792189598083496s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 0.0001583099365234375s
Availability | VoID file availability check for Tick gross anatomy took 0.00034809112548828125s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.28569579124450684s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.02051568031311035s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.0008537769317626953s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.0002841949462890625s
Believability | Calculation of trust value for Tick gross anatomy took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-tads took 2.832180976867676s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 9.489059448242188e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.31575489044189453s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.02063155174255371s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0008738040924072266s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-tao took 2.848649024963379s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 9.036064147949219e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.27674078941345215s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.022274017333984375s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 9.72747802734375e-05s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-taxrank took 2.796370506286621s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 9.369850158691406e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 0.0006392002105712891s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.2871105670928955s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.02047133445739746s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 7.343292236328125e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-teddy took 2.7732739448547363s
Availability | SPARQL endpoint availability check for Time Event Ontology took 9.107589721679688e-05s
Availability | VoID file availability check for Time Event Ontology took 0.0005466938018798828s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.283674955368042s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.03314566612243652s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 2.47955322265625e-05s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0014309883117675781s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.001325368881225586s
Believability | Calculation of trust value for Time Event Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-teo took 2.861267566680908s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 8.845329284667969e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 0.0005445480346679688s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.32227587699890137s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.020674943923950195s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.0003952980041503906s
Believability | Calculation of trust value for Mosquito gross anatomy took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-tgma took 2.8340771198272705s
Availability | SPARQL endpoint availability check for thesaurus took 9.5367431640625e-05s
Availability | VoID file availability check for thesaurus took 0.0005555152893066406s
Completeness | Calculation of interlinking completeness for thesaurus took 0.26972389221191406s
Reputation | Calculation of the PageRank for thesaurus took 0.02075672149658203s
Interlinking | Calculation of Degree of Connection for thesaurus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for thesaurus took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for thesaurus took 7.390975952148438e-05s
Believability | Calculation of trust value for thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-thesaurus took 2.8052570819854736s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 4.6253204345703125e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.2800261974334717s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.020739078521728516s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.00035858154296875s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 2.756605386734009s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 7.843971252441406e-05s
Availability | VoID file availability check for Translational Medicine Ontology took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.2963893413543701s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.020537614822387695s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0008549690246582031s
Believability | Calculation of trust value for Translational Medicine Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-tmo took 2.765376091003418s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 4.649162292480469e-05s
Availability | VoID file availability check for Plant Trait Ontology took 0.0005750656127929688s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 0.27702999114990234s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.02057623863220215s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.0001773834228515625s
Believability | Calculation of trust value for Plant Trait Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-to took 2.8080906867980957s
Availability | SPARQL endpoint availability check for TOK_Ontology took 4.673004150390625e-05s
Availability | VoID file availability check for TOK_Ontology took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 0.3139970302581787s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.02096867561340332s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.0001888275146484375s
Believability | Calculation of trust value for TOK_Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-tok took 2.8152472972869873s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 9.512901306152344e-05s
Availability | VoID file availability check for Teleost taxonomy took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 0.3190159797668457s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.02241659164428711s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.00021004676818847656s
Believability | Calculation of trust value for Teleost taxonomy took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-tto took 2.8706681728363037s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 4.696846008300781e-05s
Availability | VoID file availability check for Uber anatomy ontology took 0.0005943775177001953s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.284818172454834s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.020538330078125s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.00115203857421875s
Believability | Calculation of trust value for Uber anatomy ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-uberon took 2.7964766025543213s
Availability | SPARQL endpoint availability check for Units Ontology took 9.298324584960938e-05s
Availability | VoID file availability check for Units Ontology took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.29621338844299316s
Reputation | Calculation of the PageRank for Units Ontology took 0.02099609375s
Interlinking | Calculation of Degree of Connection for Units Ontology took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Units Ontology took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.0002415180206298828s
Believability | Calculation of trust value for Units Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-unitsontology took 2.841217517852783s
Availability | SPARQL endpoint availability check for Units of measurement took 9.226799011230469e-05s
Availability | VoID file availability check for Units of measurement took 0.0011172294616699219s
Completeness | Calculation of interlinking completeness for Units of measurement took 0.2793843746185303s
Reputation | Calculation of the PageRank for Units of measurement took 0.020677566528320312s
Interlinking | Calculation of Degree of Connection for Units of measurement took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Units of measurement took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.0002887248992919922s
Believability | Calculation of trust value for Units of measurement took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-uo took 2.7385451793670654s
Availability | SPARQL endpoint availability check for VANDF took 5.555152893066406e-05s
Availability | VoID file availability check for VANDF took 0.0006010532379150391s
Completeness | Calculation of interlinking completeness for VANDF took 0.3025689125061035s
Reputation | Calculation of the PageRank for VANDF took 0.022153139114379883s
Interlinking | Calculation of Degree of Connection for VANDF took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for VANDF took 0.0008206367492675781s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0007426738739013672s
Believability | Calculation of trust value for VANDF took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-vandf took 2.8640146255493164s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 0.00016617774963378906s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.0006213188171386719s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 0.28569507598876953s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.022005796432495117s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0008997917175292969s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.0005524158477783203s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-vao took 2.943687677383423s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 9.036064147949219e-05s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 0.0004978179931640625s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 0.2880086898803711s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.020793914794921875s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0008194446563720703s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0006921291351318359s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 1.3828277587890625e-05s
INFO | --- Analysis for bioportal-vhog took 2.794545888900757s
Availability | SPARQL endpoint availability check for VIVO took 4.553794860839844e-05s
Availability | VoID file availability check for VIVO took 0.0003142356872558594s
Completeness | Calculation of interlinking completeness for VIVO took 0.28458189964294434s
Reputation | Calculation of the PageRank for VIVO took 0.022413969039916992s
Interlinking | Calculation of Degree of Connection for VIVO took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for VIVO took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.00042700767517089844s
Believability | Calculation of trust value for VIVO took 1.4066696166992188e-05s
INFO | --- Analysis for bioportal-vivo took 2.8501603603363037s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 9.560585021972656e-05s
Availability | VoID file availability check for Vaccine Ontology took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.288301944732666s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.020543575286865234s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.001272439956665039s
Believability | Calculation of trust value for Vaccine Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-vo took 2.8436286449432373s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 4.506111145019531e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.2838912010192871s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.020879507064819336s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.00023818016052246094s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-vt took 3.0528039932250977s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 8.511543273925781e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.28908443450927734s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.020578861236572266s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.0005147457122802734s
Believability | Calculation of trust value for C. elegans gross anatomy took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-wbbt took 2.906977653503418s
Availability | SPARQL endpoint availability check for C. elegans development took 9.5367431640625e-05s
Availability | VoID file availability check for C. elegans development took 0.0005648136138916016s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.28906965255737305s
Reputation | Calculation of the PageRank for C. elegans development took 0.021776437759399414s
Interlinking | Calculation of Degree of Connection for C. elegans development took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for C. elegans development took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 5.316734313964844e-05s
Believability | Calculation of trust value for C. elegans development took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-wbls took 2.893584728240967s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 4.482269287109375e-05s
Availability | VoID file availability check for C. elegans phenotype took 0.0006034374237060547s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.2907371520996094s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.02085709571838379s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 0.00010347366333007812s
Believability | Calculation of trust value for C. elegans phenotype took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-wbphenotype took 2.8079254627227783s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 7.200241088867188e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.0005810260772705078s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.28975677490234375s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.02057647705078125s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0006167888641357422s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-who took 2.718841791152954s
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.0004734992980957031s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.2861778736114502s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.021060466766357422s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.0008380413055419922s
Believability | Calculation of trust value for Xenopus anatomy and development took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-xao took 2.8177073001861572s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 4.649162292480469e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.296314001083374s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.021201133728027344s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.00025582313537597656s
Believability | Calculation of trust value for Experimental Conditions Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-xco took 2.839517593383789s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 0.00014734268188476562s
Availability | VoID file availability check for Yeast phenotypes took 0.0005886554718017578s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 0.26816868782043457s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.020762205123901367s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.0002827644348144531s
Believability | Calculation of trust value for Yeast phenotypes took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ypo took 2.8097472190856934s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 9.250640869140625e-05s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.0005974769592285156s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 0.27947330474853516s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.0216672420501709s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.0007786750793457031s
Believability | Calculation of trust value for Zebrafish anatomy and development took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-zfa took 3.132551431655884s
Availability | SPARQL endpoint availability check for Indian Terrorism Ontology (InTO) took 0.00011754035949707031s
Availability | VoID file availability check for Indian Terrorism Ontology (InTO) took 0.0007617473602294922s
Completeness | Calculation of interlinking completeness for Indian Terrorism Ontology (InTO) took 0.3151259422302246s
Reputation | Calculation of the PageRank for Indian Terrorism Ontology (InTO) took 0.021205425262451172s
Interlinking | Calculation of Degree of Connection for Indian Terrorism Ontology (InTO) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Indian Terrorism Ontology (InTO) took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Indian Terrorism Ontology (InTO) took 3.504753112792969e-05s
Believability | Calculation of trust value for Indian Terrorism Ontology (InTO) took 1.430511474609375e-05s
INFO | --- Analysis for Bioportal_link took 4.088542699813843s
Availability | SPARQL endpoint availability check for BioSamples RDF took 0.44777703285217285s
Availability | VoID file availability check for BioSamples RDF took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.3264153003692627s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.02123403549194336s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 3.719329833984375e-05s
Believability | Calculation of trust value for BioSamples RDF took 1.3589859008789062e-05s
INFO | --- Analysis for biosamples-rdf took 3.7246735095977783s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 0.10534477233886719s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.0005106925964355469s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 0.27514076232910156s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.02095818519592285s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.00012564659118652344s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 1.4543533325195312e-05s
INFO | --- Analysis for bis-linked-data took 2.7275431156158447s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 9.131431579589844e-05s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0007102489471435547s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.3018343448638916s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.02104043960571289s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.553794860839844e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 1.4781951904296875e-05s
INFO | --- Analysis for bll-thesaurus took 3.779550075531006s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 1.0190927982330322s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.0007183551788330078s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 0.28781628608703613s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.020657062530517578s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.000782012939453125s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 8.0108642578125e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 1.4781951904296875e-05s
INFO | --- Analysis for bluk-bnb took 13.197619676589966s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.32036566734313965s
Availability | VoID file availability check for Thesaurus BNCF took 0.0006515979766845703s
Extra | Recovery of all triples for Thesaurus BNCF took 44.30772352218628s
Performance | Total latancy measurement for Thesaurus BNCF took 0.6076831817626953s
Amount of data | Number of triples check for Thesaurus BNCF took 0.6045219898223877s
Interoperability | New terms check for Thesaurus BNCF took 1.5750019550323486s
Versatility | Languages check for Thesaurus BNCF took 7.079038858413696s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 0.7974579334259033s
Security | Check HTTPS for Thesaurus BNCF took 0.0883491039276123s
Interpretability | RDF structures check for Thesaurus BNCF took 0.12279653549194336s
Versatility | Serialization formats check for Thesaurus BNCF took 0.11542487144470215s
Availability | RDF dump link check for Thesaurus BNCF took 0.11082053184509277s
License | MR license check for Thesaurus BNCF took 0.11142683029174805s
License | HR license check for Thesaurus BNCF took 0.17892169952392578s
Amount of data | Number of property check for Thesaurus BNCF took 0.12436676025390625s
Understandability | Number of label check for Thesaurus BNCF took 0.2510535717010498s
Understandability | URI regex check for Thesaurus BNCF took 0.244948148727417s
Understandability | Vocabs check for Thesaurus BNCF took 0.1121218204498291s
Verifiability | Authors check for Thesaurus BNCF took 0.11805486679077148s
Verifiability | Publishers check for Thesaurus BNCF took 0.12193775177001953s
Performance | Throughput check for Thesaurus BNCF took 10.563827753067017s
Amount of data | Check the number of entities for Thesaurus BNCF took 6.937980651855469e-05s
Verifiability | Contribs. check for Thesaurus BNCF took 0.1282203197479248s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.11823678016662598s
Interlinking | skos check for Thesaurus BNCF took 0.16080117225646973s
Interlinking | skos check for Thesaurus BNCF took 0.13330340385437012s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.11932849884033203s
Currency | Creation date check for Thesaurus BNCF took 0.2436225414276123s
Currency | Modification date check for Thesaurus BNCF took 0.24937129020690918s
Rep.Conc. | URIs length for Thesaurus BNCF took 27.416868448257446s
Interoperability | New vocabularies check for Thesaurus BNCF took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.10937952995300293s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.17450690269470215s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.11972427368164062s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 13.842389822006226s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.496828556060791s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 3.978625774383545s
Consistency | Disjoint class check for Thesaurus BNCF took 0.1172800064086914s
Consistency | Check Misplaced properties for Thesaurus BNCF took 0.8150286674499512s
Consistency | Misplaced classes for Thesaurus BNCF took 6.8705854415893555s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 8.7440505027771s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.6557519435882568s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.39349627494812s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.4254837036132812s
Security | Sign check for Thesaurus BNCF took 0.12053060531616211s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 20.978726387023926s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.3604390621185303s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.020776748657226562s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 9.059906005859375e-05s
Interoperability | Check the re-using of existing vocabs for Thesaurus BNCF took 2.6226043701171875e-06s
Believability | Calculation of trust value for Thesaurus BNCF took 1.4781951904296875e-05s
INFO | --- Analysis for bncf-ns took 185.49541687965393s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5517630577087402s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0007586479187011719s
Extra | Recovery of all triples for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.576925277709961s
Performance | Total latancy measurement for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.917490005493164s
Amount of data | Number of triples check for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.752910614013672s
Interoperability | New terms check for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.215750217437744s
Versatility | Languages check for BPR ? Bibliography of the Italian Parliament and electoral studies took 58.230963945388794s
Interpretability | Number of blank nodes check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.6956002712249756s
Security | Check HTTPS for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.30524420738220215s
Interpretability | RDF structures check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.36160922050476074s
Versatility | Serialization formats check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4390685558319092s
Availability | RDF dump link check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4350006580352783s
License | MR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.38317060470581055s
License | HR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 58.23896265029907s
Amount of data | Number of property check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.38975000381469727s
Understandability | Number of label check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6062102317810059s
Understandability | URI regex check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.8152022361755371s
Understandability | Vocabs check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3836030960083008s
Verifiability | Authors check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.387589693069458s
Verifiability | Publishers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4152238368988037s
Performance | Throughput check for BPR ? Bibliography of the Italian Parliament and electoral studies took 11.637462139129639s
Amount of data | Check the number of entities for BPR ? Bibliography of the Italian Parliament and electoral studies took 7.581710815429688e-05s
Verifiability | Contribs. check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3756144046783447s
Interlinking | sameAs chians check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4062023162841797s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.35790467262268066s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.39202332496643066s
Timeliness | dataset update frequency check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3784937858581543s
Currency | Creation date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.8789136409759521s
Currency | Modification date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3980734348297119s
Rep.Conc. | URIs length for BPR ? Bibliography of the Italian Parliament and electoral studies took 16.970508575439453s
Interoperability | New vocabularies check for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.36968278884887695s
Accuracy | Check Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.35875940322875977s
Accuracy | Check Inverse Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3512725830078125s
Accuracy | Check Empty annotation labels for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7287204265594482s
Accuracy | Check White space in annotation for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.024021387100219727s
Accuracy | Check Datatype consistency for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.03080439567565918s
Consistency | Disjoint class check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.38458824157714844s
Consistency | Check Misplaced properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 12.730916976928711s
Consistency | Misplaced classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.49746084213256836s
Consistency | Check Ontology hijacking for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.621950626373291s
Consistency | Check Invalid usage of undefined classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.8794937133789062s
Consistency | Check Invalid usage of undefined properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 14.515040874481201s
Conciseness | Check Extensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.03217935562133789s
Conciseness | Check Intensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3972046375274658s
Security | Sign check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.38356757164001465s
Availability | Check URIs Dereferenciability for BPR ? Bibliography of the Italian Parliament and electoral studies took 10.371574878692627s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3388831615447998s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.02480292320251465s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.744529724121094e-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.1920928955078125e-05s
INFO | --- Analysis for bpr took 396.99019861221313s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 9.989738464355469e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.293440580368042s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.021450042724609375s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 7.414817810058594e-05s
Believability | Calculation of trust value for Brazilian Politicians took 1.0251998901367188e-05s
INFO | --- Analysis for brazilian-politicians took 2.898739814758301s
Availability | SPARQL endpoint availability check for Bricklink took 2.3140110969543457s
Availability | VoID file availability check for Bricklink took 0.0006301403045654297s
Completeness | Calculation of interlinking completeness for Bricklink took 0.2899606227874756s
Reputation | Calculation of the PageRank for Bricklink took 0.02066183090209961s
Interlinking | Calculation of Degree of Connection for Bricklink took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bricklink took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Bricklink took 7.081031799316406e-05s
Believability | Calculation of trust value for Bricklink took 1.5020370483398438e-05s
INFO | --- Analysis for bricklink took 12.235194444656372s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.184582471847534s
Availability | VoID file availability check for British Museum Collection took 0.0007448196411132812s
Completeness | Calculation of interlinking completeness for British Museum Collection took 0.2808194160461426s
Reputation | Calculation of the PageRank for British Museum Collection took 0.0207059383392334s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for British Museum Collection took 0.0008358955383300781s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 3.814697265625e-05s
Believability | Calculation of trust value for British Museum Collection took 1.3589859008789062e-05s
INFO | --- Analysis for british-museum-collection took 73.04380464553833s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 4.649162292480469e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.2845003604888916s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.020772695541381836s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 4.673004150390625e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 1.5020370483398438e-05s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 2.664865493774414s
Availability | SPARQL endpoint availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.26311731338500977s
Availability | VoID file availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.000579833984375s
Extra | Recovery of all triples for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 12.657879829406738s
Performance | Total latancy measurement for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.6086382865905762s
Amount of data | Number of triples check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.0555775165557861s
Interoperability | New terms check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.891200065612793s
Versatility | Languages check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 5.85216498374939s
Interpretability | Number of blank nodes check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.8476212024688721s
Interpretability | RDF structures check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11635923385620117s
Versatility | Serialization formats check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.13138055801391602s
Availability | RDF dump link check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12110567092895508s
License | MR license check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12956571578979492s
License | HR license check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 17.334293365478516s
Amount of data | Number of property check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1224832534790039s
Understandability | Number of label check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.16590023040771484s
Understandability | URI regex check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.2564234733581543s
Understandability | Vocabs check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12916898727416992s
Verifiability | Authors check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11471796035766602s
Verifiability | Publishers check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12911009788513184s
Performance | Throughput check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 10.989004611968994s
Amount of data | Check the number of entities for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 7.295608520507812e-05s
Verifiability | Contribs. check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12969326972961426s
Interlinking | sameAs chians check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12222051620483398s
Interlinking | skos check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.13086938858032227s
Interlinking | skos check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11451125144958496s
Timeliness | dataset update frequency check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11469459533691406s
Currency | Creation date check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.2360215187072754s
Currency | Modification date check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.2521646022796631s
Rep.Conc. | URIs length for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 10.714771270751953s
Interoperability | New vocabularies check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.13135123252868652s
Accuracy | Check Functional Property for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11431884765625s
Accuracy | Check Inverse Functional Property for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1209254264831543s
Accuracy | Check Empty annotation labels for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.3866071701049805s
Accuracy | Check White space in annotation for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.245208740234375s
Accuracy | Check Datatype consistency for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 4.695391654968262s
Consistency | Disjoint class check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11496329307556152s
Consistency | Check Misplaced properties for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.1224582195281982s
Consistency | Check Ontology hijacking for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 5.768381118774414s
Consistency | Check Invalid usage of undefined classes for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.4009971618652344s
Consistency | Check Invalid usage of undefined properties for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 3.528902292251587s
Conciseness | Check Extensional conciseness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.799694538116455s
Security | Sign check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12121129035949707s
Availability | Check URIs Dereferenciability for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 3678.17427277565s
Completeness | Calculation of interlinking completeness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.8828377723693848s
Reputation | Calculation of the PageRank for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.021548986434936523s
Interlinking | Calculation of Degree of Connection for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0008089542388916016s
Interlinking | Calculation of Clustering coefficient for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.7179718017578125e-05s
Interoperability | Check the re-using of existing vocabs for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.1457672119140625e-06s
Believability | Calculation of trust value for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.0251998901367188e-05s
INFO | --- Analysis for bulgarian_admissions_to_correctional_facilities took 3788.6624026298523s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 0.22600340843200684s
Availability | VoID file availability check for business.data.gov.uk took 0.0005629062652587891s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 0.2927055358886719s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.023059844970703125s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 5.91278076171875e-05s
Believability | Calculation of trust value for business.data.gov.uk took 1.1205673217773438e-05s
INFO | --- Analysis for business-data-gov-uk took 2.97982120513916s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 0.5038909912109375s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.0007770061492919922s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 2.185870409011841s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 1.4765007495880127s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 0.38436365127563477s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 1.7787482738494873s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 44.27112340927124s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 0.3035125732421875s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.17870211601257324s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 0.45636534690856934s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 0.3266139030456543s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 0.2995119094848633s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 0.3773510456085205s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 19.55681824684143s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 0.33072972297668457s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 0.5419399738311768s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 0.6322143077850342s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.2947242259979248s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 0.3641185760498047s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.2891397476196289s
Performance | Throughput check for Biblioteca Virtual Miguel de Cervantes took 11.801275491714478s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 7.486343383789062e-05s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 0.3032567501068115s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 0.3093585968017578s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.3552696704864502s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.29749155044555664s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 0.32335829734802246s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 0.6390798091888428s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 0.5952694416046143s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 3.2643721103668213s
Interoperability | New vocabularies check for Biblioteca Virtual Miguel de Cervantes took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for Biblioteca Virtual Miguel de Cervantes took 0.280684232711792s
Accuracy | Check Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.4516105651855469s
Accuracy | Check Inverse Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.44836878776550293s
Accuracy | Check Empty annotation labels for Biblioteca Virtual Miguel de Cervantes took 1.1742706298828125s
Accuracy | Check White space in annotation for Biblioteca Virtual Miguel de Cervantes took 0.03419828414916992s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.030161380767822266s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 0.354306697845459s
Consistency | Check Misplaced properties for Biblioteca Virtual Miguel de Cervantes took 1.4891548156738281s
Consistency | Misplaced classes for Biblioteca Virtual Miguel de Cervantes took 0.3864622116088867s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 2.5447182655334473s
Consistency | Check Invalid usage of undefined classes for Biblioteca Virtual Miguel de Cervantes took 1.441490888595581s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 2.569129705429077s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.034410715103149414s
Conciseness | Check Intensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.2997913360595703s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 0.3205230236053467s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 1648.404054403305s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 0.38329648971557617s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.021689891815185547s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 5.555152893066406e-05s
Interoperability | Check the re-using of existing vocabs for Biblioteca Virtual Miguel de Cervantes took 1.430511474609375e-06s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes took 1.430511474609375e-05s
INFO | --- Analysis for BVMC took 1787.0425236225128s
Availability | SPARQL endpoint availability check for cablegate took 1.6946320533752441s
Availability | VoID file availability check for cablegate took 0.0005886554718017578s
Completeness | Calculation of interlinking completeness for cablegate took 0.2857201099395752s
Reputation | Calculation of the PageRank for cablegate took 0.02089405059814453s
Interlinking | Calculation of Degree of Connection for cablegate took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for cablegate took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for cablegate took 7.295608520507812e-05s
Believability | Calculation of trust value for cablegate took 1.2159347534179688e-05s
INFO | --- Analysis for cablegate took 16.698777675628662s
Availability | SPARQL endpoint availability check for Calames took 9.131431579589844e-05s
Availability | VoID file availability check for Calames took 0.0006048679351806641s
Completeness | Calculation of interlinking completeness for Calames took 0.2919657230377197s
Reputation | Calculation of the PageRank for Calames took 0.020720243453979492s
Interlinking | Calculation of Degree of Connection for Calames took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Calames took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Calames took 4.506111145019531e-05s
Believability | Calculation of trust value for Calames took 1.4781951904296875e-05s
INFO | --- Analysis for calames took 4.476195573806763s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.4104890823364258s
Availability | VoID file availability check for CaLiGraph took 0.0005466938018798828s
Extra | Recovery of all triples for CaLiGraph took 1.160050868988037s
Performance | Total latancy measurement for CaLiGraph took 1.2001159191131592s
Amount of data | Number of triples check for CaLiGraph took 13.660528421401978s
Interoperability | New terms check for CaLiGraph took 2.2470667362213135s
Versatility | Languages check for CaLiGraph took 60.306485652923584s
Interpretability | Number of blank nodes check for CaLiGraph took 0.25795412063598633s
Security | Check HTTPS for CaLiGraph took 0.13930630683898926s
Interpretability | RDF structures check for CaLiGraph took 0.28662967681884766s
Versatility | Serialization formats check for CaLiGraph took 0.2738945484161377s
Availability | RDF dump link check for CaLiGraph took 0.24523544311523438s
License | MR license check for CaLiGraph took 0.2546708583831787s
License | HR license check for CaLiGraph took 60.303433656692505s
Amount of data | Number of property check for CaLiGraph took 0.26912927627563477s
Understandability | Number of label check for CaLiGraph took 3.278351306915283s
Understandability | URI regex check for CaLiGraph took 0.532778263092041s
Understandability | Vocabs check for CaLiGraph took 0.2698993682861328s
Verifiability | Authors check for CaLiGraph took 0.26434874534606934s
Verifiability | Publishers check for CaLiGraph took 0.2798786163330078s
Performance | Throughput check for CaLiGraph took 11.39433479309082s
Amount of data | Check the number of entities for CaLiGraph took 0.014496564865112305s
Verifiability | Contribs. check for CaLiGraph took 0.26346635818481445s
Interlinking | sameAs chians check for CaLiGraph took 0.6891031265258789s
Interlinking | skos check for CaLiGraph took 0.26328182220458984s
Interlinking | skos check for CaLiGraph took 0.24164915084838867s
Timeliness | dataset update frequency check for CaLiGraph took 0.2723064422607422s
Currency | Creation date check for CaLiGraph took 0.5170931816101074s
Currency | Modification date check for CaLiGraph took 0.5115611553192139s
Rep.Conc. | URIs length for CaLiGraph took 61.03050208091736s
Interoperability | New vocabularies check for CaLiGraph took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.2514774799346924s
Accuracy | Check Functional Property for CaLiGraph took 0.24745869636535645s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.2701442241668701s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.5645320415496826s
Accuracy | Check White space in annotation for CaLiGraph took 0.026604890823364258s
Accuracy | Check Datatype consistency for CaLiGraph took 0.052361249923706055s
Consistency | Disjoint class check for CaLiGraph took 0.26172542572021484s
Consistency | Check Misplaced properties for CaLiGraph took 60.91377282142639s
Consistency | Misplaced classes for CaLiGraph took 0.5034527778625488s
Consistency | Check Ontology hijacking for CaLiGraph took 2.166764259338379s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.442613124847412s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.7161979675293s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.0346980094909668s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.475522518157959s
Security | Sign check for CaLiGraph took 0.24789834022521973s
Availability | Check URIs Dereferenciability for CaLiGraph took 9.400504112243652s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.35476136207580566s
Reputation | Calculation of the PageRank for CaLiGraph took 0.021344423294067383s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 3.528594970703125e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.430511474609375e-06s
Believability | Calculation of trust value for CaLiGraph took 1.0728836059570312e-05s
INFO | --- Analysis for CaLiGraph took 1451.3124947547913s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.2768685817718506s
Availability | VoID file availability check for CaLiGraph took 0.0007903575897216797s
Extra | Recovery of all triples for CaLiGraph took 1.2099599838256836s
Performance | Total latancy measurement for CaLiGraph took 1.2471489906311035s
Amount of data | Number of triples check for CaLiGraph took 13.632090330123901s
Interoperability | New terms check for CaLiGraph took 2.124249219894409s
Versatility | Languages check for CaLiGraph took 60.32077479362488s
Interpretability | Number of blank nodes check for CaLiGraph took 0.2667090892791748s
Security | Check HTTPS for CaLiGraph took 0.15153026580810547s
Interpretability | RDF structures check for CaLiGraph took 0.26430821418762207s
Versatility | Serialization formats check for CaLiGraph took 0.25950026512145996s
Availability | RDF dump link check for CaLiGraph took 0.24572324752807617s
License | MR license check for CaLiGraph took 0.26695847511291504s
License | HR license check for CaLiGraph took 60.30859923362732s
Amount of data | Number of property check for CaLiGraph took 0.2904164791107178s
Understandability | Number of label check for CaLiGraph took 3.271782875061035s
Understandability | URI regex check for CaLiGraph took 0.5205259323120117s
Understandability | Vocabs check for CaLiGraph took 0.269500732421875s
Verifiability | Authors check for CaLiGraph took 0.25623297691345215s
Verifiability | Publishers check for CaLiGraph took 0.2843763828277588s
Performance | Throughput check for CaLiGraph took 11.371706247329712s
Amount of data | Check the number of entities for CaLiGraph took 0.01256704330444336s
Verifiability | Contribs. check for CaLiGraph took 0.26047515869140625s
Interlinking | sameAs chians check for CaLiGraph took 0.6685426235198975s
Interlinking | skos check for CaLiGraph took 0.2664947509765625s
Interlinking | skos check for CaLiGraph took 0.218430757522583s
Timeliness | dataset update frequency check for CaLiGraph took 0.27338528633117676s
Currency | Creation date check for CaLiGraph took 0.5413384437561035s
Currency | Modification date check for CaLiGraph took 0.5285062789916992s
Rep.Conc. | URIs length for CaLiGraph took 61.08091688156128s
Interoperability | New vocabularies check for CaLiGraph took 4.76837158203125e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.26767587661743164s
Accuracy | Check Functional Property for CaLiGraph took 0.257326602935791s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.25727057456970215s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.5805628299713135s
Accuracy | Check White space in annotation for CaLiGraph took 0.026591777801513672s
Accuracy | Check Datatype consistency for CaLiGraph took 0.05110502243041992s
Consistency | Disjoint class check for CaLiGraph took 0.2584075927734375s
Consistency | Check Misplaced properties for CaLiGraph took 60.94050884246826s
Consistency | Misplaced classes for CaLiGraph took 0.6151161193847656s
Consistency | Check Ontology hijacking for CaLiGraph took 2.092346429824829s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.4225902557373047s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.70246386528015s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.030371427536010742s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.4474344253540039s
Security | Sign check for CaLiGraph took 0.270463228225708s
Availability | Check URIs Dereferenciability for CaLiGraph took 9.338637590408325s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.8118884563446045s
Reputation | Calculation of the PageRank for CaLiGraph took 0.020920991897583008s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 8.392333984375e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.6689300537109375e-06s
Believability | Calculation of trust value for CaLiGraph took 1.5020370483398438e-05s
INFO | --- Analysis for caligraph took 1455.6260917186737s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 0.062108516693115234s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.2967202663421631s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.021267175674438477s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 3.4809112548828125e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 1.5735626220703125e-05s
INFO | --- Analysis for cap-italy-rdf took 2.84531307220459s
Availability | SPARQL endpoint availability check for person took 9.608268737792969e-05s
Availability | VoID file availability check for person took 0.0005517005920410156s
Completeness | Calculation of interlinking completeness for person took 0.30194807052612305s
Reputation | Calculation of the PageRank for person took 0.021110057830810547s
Interlinking | Calculation of Degree of Connection for person took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for person took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for person took 4.363059997558594e-05s
Believability | Calculation of trust value for person took 1.3589859008789062e-05s
INFO | --- Analysis for card took 2.6342921257019043s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 4.863739013671875e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0007421970367431641s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 0.29060840606689453s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.021396398544311523s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0007908344268798828s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 4.363059997558594e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 1.4781951904296875e-05s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 3.027181625366211s
Availability | SPARQL endpoint availability check for Norway catch records dataset @PSNC took 0.49559617042541504s
Availability | VoID file availability check for Norway catch records dataset @PSNC took 0.0005359649658203125s
Extra | Recovery of all triples for Norway catch records dataset @PSNC took 108.95033717155457s
Performance | Total latancy measurement for Norway catch records dataset @PSNC took 0.9803996086120605s
Amount of data | Number of triples check for Norway catch records dataset @PSNC took 9.742573022842407s
Interoperability | New terms check for Norway catch records dataset @PSNC took 14.206697940826416s
Versatility | Languages check for Norway catch records dataset @PSNC took 300.16662311553955s
Interpretability | Number of blank nodes check for Norway catch records dataset @PSNC took 2.3203885555267334s
Interpretability | RDF structures check for Norway catch records dataset @PSNC took 0.3189826011657715s
Versatility | Serialization formats check for Norway catch records dataset @PSNC took 7.907172441482544s
Availability | RDF dump link check for Norway catch records dataset @PSNC took 0.34807658195495605s
License | MR license check for Norway catch records dataset @PSNC took 0.7679908275604248s
License | HR license check for Norway catch records dataset @PSNC took 300.169442653656s
Amount of data | Number of property check for Norway catch records dataset @PSNC took 0.20561480522155762s
Understandability | Number of label check for Norway catch records dataset @PSNC took 2.0342230796813965s
Understandability | URI regex check for Norway catch records dataset @PSNC took 1.0392985343933105s
Understandability | Vocabs check for Norway catch records dataset @PSNC took 0.5235042572021484s
Verifiability | Authors check for Norway catch records dataset @PSNC took 0.21829009056091309s
Verifiability | Publishers check for Norway catch records dataset @PSNC took 0.24574542045593262s
Performance | Throughput check for Norway catch records dataset @PSNC took 11.28035831451416s
Amount of data | Check the number of entities for Norway catch records dataset @PSNC took 7.176399230957031e-05s
Verifiability | Contribs. check for Norway catch records dataset @PSNC took 0.21961498260498047s
Interlinking | sameAs chians check for Norway catch records dataset @PSNC took 0.18549823760986328s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.5099976062774658s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.43741297721862793s
Timeliness | dataset update frequency check for Norway catch records dataset @PSNC took 4.159816026687622s
Currency | Creation date check for Norway catch records dataset @PSNC took 0.4767022132873535s
Currency | Modification date check for Norway catch records dataset @PSNC took 0.26323485374450684s
Rep.Conc. | URIs length for Norway catch records dataset @PSNC took 153.8918571472168s
Interoperability | New vocabularies check for Norway catch records dataset @PSNC took 1.2874603271484375e-05s
Consistency | Deprecated classes/propertiers check for Norway catch records dataset @PSNC took 0.21236824989318848s
Accuracy | Check Functional Property for Norway catch records dataset @PSNC took 0.45866966247558594s
Accuracy | Check Inverse Functional Property for Norway catch records dataset @PSNC took 0.4546318054199219s
Accuracy | Check Empty annotation labels for Norway catch records dataset @PSNC took 37.599218130111694s
Accuracy | Check White space in annotation for Norway catch records dataset @PSNC took 2.6821227073669434s
Accuracy | Check Datatype consistency for Norway catch records dataset @PSNC took 2.720607280731201s
Consistency | Disjoint class check for Norway catch records dataset @PSNC took 0.20023775100708008s
Consistency | Check Misplaced properties for Norway catch records dataset @PSNC took 87.67005324363708s
Consistency | Misplaced classes for Norway catch records dataset @PSNC took 8.35171103477478s
Consistency | Check Ontology hijacking for Norway catch records dataset @PSNC took 39.9709415435791s
Consistency | Check Invalid usage of undefined classes for Norway catch records dataset @PSNC took 1.5284106731414795s
Consistency | Check Invalid usage of undefined properties for Norway catch records dataset @PSNC took 88.49249076843262s
Conciseness | Check Extensional conciseness for Norway catch records dataset @PSNC took 2.793023109436035s
Conciseness | Check Intensional conciseness for Norway catch records dataset @PSNC took 0.5696001052856445s
Security | Sign check for Norway catch records dataset @PSNC took 1.5279755592346191s
Availability | Check URIs Dereferenciability for Norway catch records dataset @PSNC took 10.267160892486572s
Completeness | Calculation of interlinking completeness for Norway catch records dataset @PSNC took 0.48412370681762695s
Reputation | Calculation of the PageRank for Norway catch records dataset @PSNC took 0.021470308303833008s
Interlinking | Calculation of Degree of Connection for Norway catch records dataset @PSNC took 2.4557113647460938e-05s
Interlinking | Calculation of Centrality for Norway catch records dataset @PSNC took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Norway catch records dataset @PSNC took 5.245208740234375e-05s
Interoperability | Check the re-using of existing vocabs for Norway catch records dataset @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Norway catch records dataset @PSNC took 1.6450881958007812e-05s
INFO | --- Analysis for Catch_Record_(2014-_2019) took 2310.1094324588776s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 4.76837158203125e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0006191730499267578s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.2905087471008301s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.021907806396484375s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0007843971252441406s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.00011372566223144531s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.3828277587890625e-05s
INFO | --- Analysis for ce4r took 47.166524171829224s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.45986199378967285s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.00030112266540527344s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 1.2156596183776855s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 0.84987473487854s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.22493767738342285s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 1.6616768836975098s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 19.341899871826172s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17499184608459473s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4013645648956299s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17393827438354492s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1691441535949707s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.6311337947845459s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.39391303062438965s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1518259048461914s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.7074167728424072s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.33272266387939453s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17500543594360352s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2818629741668701s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3715858459472656s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 11.031091690063477s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 5.745887756347656e-05s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.22861194610595703s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2508878707885742s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.7940125465393066s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15524506568908691s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1860828399658203s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.5198428630828857s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.31732773780822754s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 1.2723441123962402s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15699481964111328s
Accuracy | Check Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.2813682556152344s
Accuracy | Check Inverse Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.29706621170043945s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 2.2912139892578125s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.028606414794921875s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.03018355369567871s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.235870361328125s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 0.7531206607818604s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 2.090452194213867s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 1.4381804466247559s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.7111096382141113s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.03179621696472168s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.22930240631103516s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1630561351776123s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 2533.911584854126s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 0.7228755950927734s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.0208890438079834s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 4.9114227294921875e-05s
Interoperability | Check the re-using of existing vocabs for Linked Data Cultural Heritage Agency of the Netherlands took 1.9073486328125e-06s
Believability | Calculation of trust value for Linked Data Cultural Heritage Agency of the Netherlands took 1.0728836059570312e-05s
INFO | --- Analysis for ceo took 2622.03173494339s
Availability | SPARQL endpoint availability check for Chat Game corpus took 4.76837158203125e-05s
Availability | VoID file availability check for Chat Game corpus took 0.0007882118225097656s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 0.3038523197174072s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.022240161895751953s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 3.838539123535156e-05s
Believability | Calculation of trust value for Chat Game corpus took 1.2636184692382812e-05s
INFO | --- Analysis for chat-game-corpus took 12.789887428283691s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 4.696846008300781e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.0008690357208251953s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 0.3031728267669678s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.02210068702697754s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 7.009506225585938e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 1.239776611328125e-05s
INFO | --- Analysis for chem2bio2rdf took 133.9102485179901s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 0.5953595638275146s
Availability | VoID file availability check for ChEMBL RDF took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.27828550338745117s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.02061009407043457s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 5.245208740234375e-05s
Believability | Calculation of trust value for ChEMBL RDF took 1.4781951904296875e-05s
INFO | --- Analysis for chembl-rdf took 3.8776018619537354s
Availability | SPARQL endpoint availability check for chemdb  dataset took 1.0292370319366455s
Availability | VoID file availability check for chemdb  dataset took 0.0005307197570800781s
Extra | Recovery of all triples for chemdb  dataset took 4.932911157608032s
Performance | Total latancy measurement for chemdb  dataset took 2.5300281047821045s
Amount of data | Number of triples check for chemdb  dataset took 0.5570659637451172s
Interoperability | New terms check for chemdb  dataset took 3.600473403930664s
Versatility | Languages check for chemdb  dataset took 22.799458980560303s
Interpretability | Number of blank nodes check for chemdb  dataset took 0.5398190021514893s
Interpretability | RDF structures check for chemdb  dataset took 0.5356769561767578s
Versatility | Serialization formats check for chemdb  dataset took 0.5151898860931396s
Availability | RDF dump link check for chemdb  dataset took 0.4968113899230957s
License | MR license check for chemdb  dataset took 0.5008335113525391s
License | HR license check for chemdb  dataset took 3.0946409702301025s
Amount of data | Number of property check for chemdb  dataset took 0.5317716598510742s
Understandability | Number of label check for chemdb  dataset took 0.5512173175811768s
Understandability | URI regex check for chemdb  dataset took 0.9974064826965332s
Understandability | Vocabs check for chemdb  dataset took 0.5155353546142578s
Verifiability | Authors check for chemdb  dataset took 0.4966857433319092s
Verifiability | Publishers check for chemdb  dataset took 0.49962592124938965s
Performance | Throughput check for chemdb  dataset took 12.54916787147522s
Amount of data | Check the number of entities for chemdb  dataset took 8.7738037109375e-05s
Verifiability | Contribs. check for chemdb  dataset took 0.5070593357086182s
Interlinking | sameAs chians check for chemdb  dataset took 0.5419409275054932s
Interlinking | skos check for chemdb  dataset took 0.5005288124084473s
Interlinking | skos check for chemdb  dataset took 0.4941701889038086s
Timeliness | dataset update frequency check for chemdb  dataset took 0.5049359798431396s
Currency | Creation date check for chemdb  dataset took 1.0169744491577148s
Currency | Modification date check for chemdb  dataset took 1.0339488983154297s
Rep.Conc. | URIs length for chemdb  dataset took 2.898851156234741s
Interoperability | New vocabularies check for chemdb  dataset took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for chemdb  dataset took 0.5206327438354492s
Accuracy | Check Functional Property for chemdb  dataset took 0.5337302684783936s
Accuracy | Check Inverse Functional Property for chemdb  dataset took 0.4961545467376709s
Accuracy | Check Empty annotation labels for chemdb  dataset took 2.1524014472961426s
Accuracy | Check White space in annotation for chemdb  dataset took 0.03056931495666504s
Accuracy | Check Datatype consistency for chemdb  dataset took 0.03592419624328613s
Consistency | Disjoint class check for chemdb  dataset took 0.4967074394226074s
Consistency | Check Misplaced properties for chemdb  dataset took 1.2204835414886475s
Consistency | Misplaced classes for chemdb  dataset took 0.6155397891998291s
Consistency | Check Ontology hijacking for chemdb  dataset took 3.591840982437134s
Consistency | Check Invalid usage of undefined classes for chemdb  dataset took 1.4310476779937744s
Consistency | Check Invalid usage of undefined properties for chemdb  dataset took 2.1339471340179443s
Conciseness | Check Extensional conciseness for chemdb  dataset took 0.035541534423828125s
Conciseness | Check Intensional conciseness for chemdb  dataset took 0.531726598739624s
Security | Sign check for chemdb  dataset took 0.5055108070373535s
Availability | Check URIs Dereferenciability for chemdb  dataset took 2518.7326118946075s
Completeness | Calculation of interlinking completeness for chemdb  dataset took 0.5106513500213623s
Reputation | Calculation of the PageRank for chemdb  dataset took 0.02138805389404297s
Interlinking | Calculation of Degree of Connection for chemdb  dataset took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for chemdb  dataset took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for chemdb  dataset took 8.320808410644531e-05s
Interoperability | Check the re-using of existing vocabs for chemdb  dataset took 1.9073486328125e-06s
Believability | Calculation of trust value for chemdb  dataset took 1.1920928955078125e-05s
INFO | --- Analysis for chemdb-basicInfo took 4817.992572784424s
Availability | SPARQL endpoint availability check for chemdb estimated properties dataset took 0.5264465808868408s
Availability | VoID file availability check for chemdb estimated properties dataset took 0.0003466606140136719s
Extra | Recovery of all triples for chemdb estimated properties dataset took 4.984553813934326s
Performance | Total latancy measurement for chemdb estimated properties dataset took 2.542783498764038s
Amount of data | Number of triples check for chemdb estimated properties dataset took 0.5546655654907227s
Interoperability | New terms check for chemdb estimated properties dataset took 3.6306140422821045s
Versatility | Languages check for chemdb estimated properties dataset took 23.203892707824707s
Interpretability | Number of blank nodes check for chemdb estimated properties dataset took 0.540745735168457s
Interpretability | RDF structures check for chemdb estimated properties dataset took 0.5412368774414062s
Versatility | Serialization formats check for chemdb estimated properties dataset took 0.8833341598510742s
Availability | RDF dump link check for chemdb estimated properties dataset took 0.5939364433288574s
License | MR license check for chemdb estimated properties dataset took 0.9096055030822754s
License | HR license check for chemdb estimated properties dataset took 3.336179494857788s
Amount of data | Number of property check for chemdb estimated properties dataset took 0.5325348377227783s
Understandability | Number of label check for chemdb estimated properties dataset took 1.3840415477752686s
Understandability | URI regex check for chemdb estimated properties dataset took 1.1615002155303955s
Understandability | Vocabs check for chemdb estimated properties dataset took 0.5446898937225342s
Verifiability | Authors check for chemdb estimated properties dataset took 0.5881178379058838s
Verifiability | Publishers check for chemdb estimated properties dataset took 0.5743908882141113s
Performance | Throughput check for chemdb estimated properties dataset took 11.987977743148804s
Amount of data | Check the number of entities for chemdb estimated properties dataset took 8.416175842285156e-05s
Verifiability | Contribs. check for chemdb estimated properties dataset took 0.5287632942199707s
Interlinking | sameAs chians check for chemdb estimated properties dataset took 0.5574235916137695s
Interlinking | skos check for chemdb estimated properties dataset took 0.558112621307373s
Interlinking | skos check for chemdb estimated properties dataset took 0.5004885196685791s
Timeliness | dataset update frequency check for chemdb estimated properties dataset took 0.5618789196014404s
Currency | Creation date check for chemdb estimated properties dataset took 1.0801656246185303s
Currency | Modification date check for chemdb estimated properties dataset took 1.0266404151916504s
Rep.Conc. | URIs length for chemdb estimated properties dataset took 2.9872093200683594s
Interoperability | New vocabularies check for chemdb estimated properties dataset took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for chemdb estimated properties dataset took 0.5101790428161621s
Accuracy | Check Functional Property for chemdb estimated properties dataset took 0.5376749038696289s
Accuracy | Check Inverse Functional Property for chemdb estimated properties dataset took 0.5527520179748535s
Accuracy | Check Empty annotation labels for chemdb estimated properties dataset took 2.282867908477783s
Accuracy | Check White space in annotation for chemdb estimated properties dataset took 0.030701160430908203s
Accuracy | Check Datatype consistency for chemdb estimated properties dataset took 0.03560781478881836s
Consistency | Disjoint class check for chemdb estimated properties dataset took 0.5640201568603516s
Consistency | Check Misplaced properties for chemdb estimated properties dataset took 1.231414794921875s
Consistency | Misplaced classes for chemdb estimated properties dataset took 0.61893630027771s
Consistency | Check Ontology hijacking for chemdb estimated properties dataset took 3.5940027236938477s
Consistency | Check Invalid usage of undefined classes for chemdb estimated properties dataset took 1.408574104309082s
Consistency | Check Invalid usage of undefined properties for chemdb estimated properties dataset took 2.120558977127075s
Conciseness | Check Extensional conciseness for chemdb estimated properties dataset took 0.03426384925842285s
Conciseness | Check Intensional conciseness for chemdb estimated properties dataset took 0.525378942489624s
Security | Sign check for chemdb estimated properties dataset took 0.6831338405609131s
Availability | Check URIs Dereferenciability for chemdb estimated properties dataset took 2521.04762840271s
Completeness | Calculation of interlinking completeness for chemdb estimated properties dataset took 0.46961212158203125s
Reputation | Calculation of the PageRank for chemdb estimated properties dataset took 0.0218050479888916s
Interlinking | Calculation of Degree of Connection for chemdb estimated properties dataset took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for chemdb estimated properties dataset took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for chemdb estimated properties dataset took 6.556510925292969e-05s
Interoperability | Check the re-using of existing vocabs for chemdb estimated properties dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for chemdb estimated properties dataset took 1.430511474609375e-05s
INFO | --- Analysis for chemdb-estimatedProperties took 5079.060758829117s
Availability | SPARQL endpoint availability check for chemdb phase transition dataset took 0.5223262310028076s
Availability | VoID file availability check for chemdb phase transition dataset took 0.0005805492401123047s
Extra | Recovery of all triples for chemdb phase transition dataset took 18.074537754058838s
Performance | Total latancy measurement for chemdb phase transition dataset took 2.608031749725342s
Amount of data | Number of triples check for chemdb phase transition dataset took 0.5529303550720215s
Interoperability | New terms check for chemdb phase transition dataset took 6.152520179748535s
Versatility | Languages check for chemdb phase transition dataset took 23.322556734085083s
Interpretability | Number of blank nodes check for chemdb phase transition dataset took 0.5378406047821045s
Interpretability | RDF structures check for chemdb phase transition dataset took 0.5407328605651855s
Versatility | Serialization formats check for chemdb phase transition dataset took 0.7313361167907715s
Availability | RDF dump link check for chemdb phase transition dataset took 0.593317985534668s
License | MR license check for chemdb phase transition dataset took 1.1732704639434814s
License | HR license check for chemdb phase transition dataset took 3.323354482650757s
Amount of data | Number of property check for chemdb phase transition dataset took 0.5390093326568604s
Understandability | Number of label check for chemdb phase transition dataset took 1.669301986694336s
Understandability | URI regex check for chemdb phase transition dataset took 1.2019274234771729s
Understandability | Vocabs check for chemdb phase transition dataset took 0.5783727169036865s
Verifiability | Authors check for chemdb phase transition dataset took 0.6454422473907471s
Verifiability | Publishers check for chemdb phase transition dataset took 0.5790536403656006s
Performance | Throughput check for chemdb phase transition dataset took 12.583104848861694s
Amount of data | Check the number of entities for chemdb phase transition dataset took 7.414817810058594e-05s
Verifiability | Contribs. check for chemdb phase transition dataset took 0.5400826930999756s
Interlinking | sameAs chians check for chemdb phase transition dataset took 0.6713616847991943s
Interlinking | skos check for chemdb phase transition dataset took 0.8341248035430908s
Interlinking | skos check for chemdb phase transition dataset took 0.4979863166809082s
Timeliness | dataset update frequency check for chemdb phase transition dataset took 0.6593959331512451s
Currency | Creation date check for chemdb phase transition dataset took 1.1196556091308594s
Currency | Modification date check for chemdb phase transition dataset took 1.0247595310211182s
Rep.Conc. | URIs length for chemdb phase transition dataset took 5.059173107147217s
Interoperability | New vocabularies check for chemdb phase transition dataset took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for chemdb phase transition dataset took 0.500948429107666s
Accuracy | Check Functional Property for chemdb phase transition dataset took 0.6225254535675049s
Accuracy | Check Inverse Functional Property for chemdb phase transition dataset took 0.6016685962677002s
Accuracy | Check Empty annotation labels for chemdb phase transition dataset took 4.84930682182312s
Accuracy | Check White space in annotation for chemdb phase transition dataset took 0.030737638473510742s
Accuracy | Check Datatype consistency for chemdb phase transition dataset took 0.03535962104797363s
Consistency | Disjoint class check for chemdb phase transition dataset took 0.5744736194610596s
Consistency | Check Misplaced properties for chemdb phase transition dataset took 1.2418863773345947s
Consistency | Misplaced classes for chemdb phase transition dataset took 0.6122832298278809s
Consistency | Check Ontology hijacking for chemdb phase transition dataset took 5.938194751739502s
Consistency | Check Invalid usage of undefined classes for chemdb phase transition dataset took 1.4098615646362305s
Consistency | Check Invalid usage of undefined properties for chemdb phase transition dataset took 2.1316707134246826s
Conciseness | Check Extensional conciseness for chemdb phase transition dataset took 0.052292585372924805s
Conciseness | Check Intensional conciseness for chemdb phase transition dataset took 0.5438332557678223s
Security | Sign check for chemdb phase transition dataset took 0.8174333572387695s
Availability | Check URIs Dereferenciability for chemdb phase transition dataset took 2520.6101636886597s
Completeness | Calculation of interlinking completeness for chemdb phase transition dataset took 0.47875308990478516s
Reputation | Calculation of the PageRank for chemdb phase transition dataset took 0.021241426467895508s
Interlinking | Calculation of Degree of Connection for chemdb phase transition dataset took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for chemdb phase transition dataset took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for chemdb phase transition dataset took 5.245208740234375e-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.4066696166992188e-05s
INFO | --- Analysis for chemdb-phaseTransition took 4811.482342720032s
Availability | SPARQL endpoint availability check for chemdb thermochemistry dataset took 0.524791955947876s
Availability | VoID file availability check for chemdb thermochemistry dataset took 0.0005271434783935547s
Extra | Recovery of all triples for chemdb thermochemistry dataset took 13.098392248153687s
Performance | Total latancy measurement for chemdb thermochemistry dataset took 2.5405402183532715s
Amount of data | Number of triples check for chemdb thermochemistry dataset took 0.5460386276245117s
Interoperability | New terms check for chemdb thermochemistry dataset took 4.524083137512207s
Versatility | Languages check for chemdb thermochemistry dataset took 22.316494941711426s
Interpretability | Number of blank nodes check for chemdb thermochemistry dataset took 0.5328950881958008s
Interpretability | RDF structures check for chemdb thermochemistry dataset took 0.5227770805358887s
Versatility | Serialization formats check for chemdb thermochemistry dataset took 0.5285539627075195s
Availability | RDF dump link check for chemdb thermochemistry dataset took 0.5004146099090576s
License | MR license check for chemdb thermochemistry dataset took 0.5660865306854248s
License | HR license check for chemdb thermochemistry dataset took 3.166231155395508s
Amount of data | Number of property check for chemdb thermochemistry dataset took 0.5349342823028564s
Understandability | Number of label check for chemdb thermochemistry dataset took 0.5240259170532227s
Understandability | URI regex check for chemdb thermochemistry dataset took 1.0494427680969238s
Understandability | Vocabs check for chemdb thermochemistry dataset took 0.5012972354888916s
Verifiability | Authors check for chemdb thermochemistry dataset took 0.5035767555236816s
Verifiability | Publishers check for chemdb thermochemistry dataset took 0.49913454055786133s
Performance | Throughput check for chemdb thermochemistry dataset took 12.081407070159912s
Amount of data | Check the number of entities for chemdb thermochemistry dataset took 0.00011301040649414062s
Verifiability | Contribs. check for chemdb thermochemistry dataset took 0.4994220733642578s
Interlinking | sameAs chians check for chemdb thermochemistry dataset took 0.5413413047790527s
Interlinking | skos check for chemdb thermochemistry dataset took 0.5011546611785889s
Interlinking | skos check for chemdb thermochemistry dataset took 0.4928288459777832s
Timeliness | dataset update frequency check for chemdb thermochemistry dataset took 0.5128457546234131s
Currency | Creation date check for chemdb thermochemistry dataset took 1.0439105033874512s
Currency | Modification date check for chemdb thermochemistry dataset took 1.0282959938049316s
Rep.Conc. | URIs length for chemdb thermochemistry dataset took 3.93984317779541s
Interoperability | New vocabularies check for chemdb thermochemistry dataset took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for chemdb thermochemistry dataset took 0.5079576969146729s
Accuracy | Check Functional Property for chemdb thermochemistry dataset took 0.5227813720703125s
Accuracy | Check Inverse Functional Property for chemdb thermochemistry dataset took 0.5036640167236328s
Accuracy | Check Empty annotation labels for chemdb thermochemistry dataset took 3.3460423946380615s
Accuracy | Check White space in annotation for chemdb thermochemistry dataset took 0.03015613555908203s
Accuracy | Check Datatype consistency for chemdb thermochemistry dataset took 0.035331010818481445s
Consistency | Disjoint class check for chemdb thermochemistry dataset took 0.49217748641967773s
Consistency | Check Misplaced properties for chemdb thermochemistry dataset took 1.2439179420471191s
Consistency | Misplaced classes for chemdb thermochemistry dataset took 0.6336658000946045s
Consistency | Check Ontology hijacking for chemdb thermochemistry dataset took 4.531417369842529s
Consistency | Check Invalid usage of undefined classes for chemdb thermochemistry dataset took 1.4291610717773438s
Consistency | Check Invalid usage of undefined properties for chemdb thermochemistry dataset took 2.117628812789917s
Conciseness | Check Extensional conciseness for chemdb thermochemistry dataset took 0.03505730628967285s
Conciseness | Check Intensional conciseness for chemdb thermochemistry dataset took 0.5159034729003906s
Security | Sign check for chemdb thermochemistry dataset took 0.4971163272857666s
Availability | Check URIs Dereferenciability for chemdb thermochemistry dataset took 2514.396812915802s
Completeness | Calculation of interlinking completeness for chemdb thermochemistry dataset took 0.5046041011810303s
Reputation | Calculation of the PageRank for chemdb thermochemistry dataset took 0.022190093994140625s
Interlinking | Calculation of Degree of Connection for chemdb thermochemistry dataset took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for chemdb thermochemistry dataset took 0.0007669925689697266s
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.6689300537109375e-06s
Believability | Calculation of trust value for chemdb thermochemistry dataset took 1.430511474609375e-05s
INFO | --- Analysis for chemdb-thermochemistry took 4787.080500602722s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 0.00010037422180175781s
Availability | VoID file availability check for ChemPedia RDF took 0.0008165836334228516s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 0.3150336742401123s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.022185087203979492s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0008275508880615234s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 3.814697265625e-05s
Believability | Calculation of trust value for ChemPedia RDF took 1.3113021850585938e-05s
INFO | --- Analysis for chempedia-rdf took 9.567872047424316s
Availability | SPARQL endpoint availability check for Chiman Maru took 4.9591064453125e-05s
Availability | VoID file availability check for Chiman Maru took 0.00035119056701660156s
Completeness | Calculation of interlinking completeness for Chiman Maru took 0.293701171875s
Reputation | Calculation of the PageRank for Chiman Maru took 0.02102041244506836s
Interlinking | Calculation of Degree of Connection for Chiman Maru took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Chiman Maru took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Chiman Maru took 3.62396240234375e-05s
Believability | Calculation of trust value for Chiman Maru took 2.002716064453125e-05s
INFO | --- Analysis for ChimanMaru_Entrepreneur took 2.578667402267456s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 393.2167980670929s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.0008165836334228516s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 0.32369112968444824s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.021353721618652344s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0007834434509277344s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 4.410743713378906e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 1.1682510375976562e-05s
INFO | --- Analysis for Chinese_Red_Classic_Song_Linked_Data_Dataset took 801.354647397995s
Availability | SPARQL endpoint availability check for Chronicling America took 5.626678466796875e-05s
Availability | VoID file availability check for Chronicling America took 0.0008652210235595703s
Completeness | Calculation of interlinking completeness for Chronicling America took 0.28498315811157227s
Reputation | Calculation of the PageRank for Chronicling America took 0.020864248275756836s
Interlinking | Calculation of Degree of Connection for Chronicling America took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Chronicling America took 0.0007824897766113281s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 0.00011515617370605469s
Believability | Calculation of trust value for Chronicling America took 1.4543533325195312e-05s
INFO | --- Analysis for chronicling-america took 246.21140122413635s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.6467101573944092s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.0004756450653076172s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 85.66188192367554s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.6059131622314453s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 2.0210282802581787s
Interoperability | New terms check for Cultural Heritage Thesaurus took 2.211294651031494s
Versatility | Languages check for Cultural Heritage Thesaurus took 8.351903915405273s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 2.659738302230835s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.3397693634033203s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.36789870262145996s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 6.0969579219818115s
License | MR license check for Cultural Heritage Thesaurus took 0.2897226810455322s
License | HR license check for Cultural Heritage Thesaurus took 0.6587629318237305s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.4077765941619873s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.7377569675445557s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.646275520324707s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.31762242317199707s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.3137485980987549s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.3441140651702881s
Performance | Throughput check for Cultural Heritage Thesaurus took 11.429404497146606s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 8.153915405273438e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.30097389221191406s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.30112695693969727s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.38756775856018066s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.43333935737609863s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.3611636161804199s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.6749417781829834s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.6027960777282715s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 32.06623411178589s
Interoperability | New vocabularies check for Cultural Heritage Thesaurus took 0.7610719203948975s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.3186051845550537s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.37282633781433105s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.2983431816101074s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 7.358694553375244s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.2246699333190918s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.3003664016723633s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 2.7485318183898926s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.3247401714324951s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 7.103667259216309s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 4.130752801895142s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.0001685619354248047s
Security | Sign check for Cultural Heritage Thesaurus took 0.3147239685058594s
Availability | Check URIs Dereferenciability for Cultural Heritage Thesaurus took 370.4976580142975s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 0.3009200096130371s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.021254301071166992s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 2.8848648071289062e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0008594989776611328s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 0.00011849403381347656s
Interoperability | Check the re-using of existing vocabs for Cultural Heritage Thesaurus took 2.682011127471924s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 3.0279159545898438e-05s
INFO | --- Analysis for cht took 586.7577481269836s
Availability | SPARQL endpoint availability check for ciard-ring took 9.822845458984375e-05s
Availability | VoID file availability check for ciard-ring took 0.00034308433532714844s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.29151487350463867s
Reputation | Calculation of the PageRank for ciard-ring took 0.02072596549987793s
Interlinking | Calculation of Degree of Connection for ciard-ring took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for ciard-ring took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 5.793571472167969e-05s
Believability | Calculation of trust value for ciard-ring took 1.1920928955078125e-05s
INFO | --- Analysis for ciard-ring took 11.341467142105103s
Availability | SPARQL endpoint availability check for Cine Figure took 4.673004150390625e-05s
Availability | VoID file availability check for Cine Figure took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for Cine Figure took 0.3061497211456299s
Reputation | Calculation of the PageRank for Cine Figure took 0.021051883697509766s
Interlinking | Calculation of Degree of Connection for Cine Figure took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Cine Figure took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Cine Figure took 4.982948303222656e-05s
Believability | Calculation of trust value for Cine Figure took 9.775161743164062e-06s
INFO | --- Analysis for Cine_Figure took 2.7074360847473145s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 1.6419181823730469s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.0007283687591552734s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.3282303810119629s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.020623445510864258s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0007975101470947266s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 4.792213439941406e-05s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 1.4066696166992188e-05s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 10.354862689971924s
Availability | SPARQL endpoint availability check for CIPFA took 7.176399230957031e-05s
Availability | VoID file availability check for CIPFA took 0.0006668567657470703s
Completeness | Calculation of interlinking completeness for CIPFA took 0.29229211807250977s
Reputation | Calculation of the PageRank for CIPFA took 0.021186113357543945s
Interlinking | Calculation of Degree of Connection for CIPFA took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for CIPFA took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for CIPFA took 4.1484832763671875e-05s
Believability | Calculation of trust value for CIPFA took 6.67572021484375e-06s
INFO | --- Analysis for cipfa took 2.778376340866089s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 60.052300691604614s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.0006911754608154297s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.4401712417602539s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.02119922637939453s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.0008237361907958984s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.0004189014434814453s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 1.0967254638671875e-05s
INFO | --- Analysis for ckan took 263.02964210510254s
Availability | SPARQL endpoint availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.5730915069580078s
Availability | VoID file availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.00042748451232910156s
Completeness | Calculation of interlinking completeness for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.2738327980041504s
Reputation | Calculation of the PageRank for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.020780324935913086s
Interlinking | Calculation of Degree of Connection for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0007874965667724609s
Interlinking | Calculation of Clustering coefficient for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 4.792213439941406e-05s
Believability | Calculation of trust value for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.5735626220703125e-05s
INFO | --- Analysis for CLaSSES took 4.451931715011597s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 6.175041198730469e-05s
Availability | VoID file availability check for Temples of the Classical World took 0.000751495361328125s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 0.2940683364868164s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.02074146270751953s
Interlinking | Calculation of Degree of Connection for Temples of the Classical World took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Temples of the Classical World took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 3.504753112792969e-05s
Believability | Calculation of trust value for Temples of the Classical World took 1.5020370483398438e-05s
INFO | --- Analysis for classical_temples took 4.715162754058838s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 1.111678123474121s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.0003986358642578125s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 0.29640746116638184s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.021541118621826172s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 2.3365020751953125e-05s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0010120868682861328s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 0.00010800361633300781s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 6.198883056640625e-06s
INFO | --- Analysis for clean-energy-data-reegle took 5.45640754699707s
Availability | SPARQL endpoint availability check for CLLD-afbo took 4.506111145019531e-05s
Availability | VoID file availability check for CLLD-afbo took 0.00036525726318359375s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.2833535671234131s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.020791292190551758s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 7.939338684082031e-05s
Believability | Calculation of trust value for CLLD-afbo took 1.0013580322265625e-05s
INFO | --- Analysis for clld-afbo took 3.640289783477783s
Availability | SPARQL endpoint availability check for CLLD-APICS took 4.482269287109375e-05s
Availability | VoID file availability check for CLLD-APICS took 0.0007426738739013672s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 0.28086066246032715s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.020839929580688477s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0007936954498291016s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 8.654594421386719e-05s
Believability | Calculation of trust value for CLLD-APICS took 9.298324584960938e-06s
INFO | --- Analysis for clld-apics took 3.7539076805114746s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 9.369850158691406e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.00030541419982910156s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.2812676429748535s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.020926952362060547s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 5.0067901611328125e-05s
Believability | Calculation of trust value for CLLD-EWAVE took 8.821487426757812e-06s
INFO | --- Analysis for clld-ewave took 3.6991255283355713s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 4.57763671875e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.0005958080291748047s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 0.29000234603881836s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.021489858627319336s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 0.00010561943054199219s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 1.3113021850585938e-05s
INFO | --- Analysis for clld-glottolog took 3.701148748397827s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 4.458427429199219e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.0006237030029296875s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.28756237030029297s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.02107691764831543s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 8.726119995117188e-05s
Believability | Calculation of trust value for CLLD-PHOIBLE took 1.5020370483398438e-05s
INFO | --- Analysis for clld-phoible took 3.6592323780059814s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 4.601478576660156e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.0006721019744873047s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 0.29352498054504395s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.022381067276000977s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 8.273124694824219e-05s
Believability | Calculation of trust value for CLLD-SAILS took 1.52587890625e-05s
INFO | --- Analysis for clld-sails took 3.758718252182007s
Availability | SPARQL endpoint availability check for CLLD-WALS took 0.0001163482666015625s
Availability | VoID file availability check for CLLD-WALS took 0.0006949901580810547s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.28319549560546875s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.020556926727294922s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 9.226799011230469e-05s
Believability | Calculation of trust value for CLLD-WALS took 1.239776611328125e-05s
INFO | --- Analysis for clld-wals took 3.7244760990142822s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 9.036064147949219e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.0003578662872314453s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 0.281696081161499s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.02050924301147461s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 8.273124694824219e-05s
Believability | Calculation of trust value for CLLD-WOLD took 1.0251998901367188e-05s
INFO | --- Analysis for clld-wold took 3.669792890548706s
Availability | SPARQL endpoint availability check for Cooperation Databank took 0.1728670597076416s
Availability | VoID file availability check for Cooperation Databank took 0.0002932548522949219s
Completeness | Calculation of interlinking completeness for Cooperation Databank took 0.283843994140625s
Reputation | Calculation of the PageRank for Cooperation Databank took 0.020517826080322266s
Interlinking | Calculation of Degree of Connection for Cooperation Databank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cooperation Databank took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Cooperation Databank took 4.7206878662109375e-05s
Believability | Calculation of trust value for Cooperation Databank took 1.4066696166992188e-05s
INFO | --- Analysis for CoDa took 2.850057363510132s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 1.0610260963439941s
Availability | VoID file availability check for OpenUpLabs COINS took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.3516504764556885s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.02091526985168457s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 3.361701965332031e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 6.4373016357421875e-06s
INFO | --- Analysis for coins-openuplabs took 3.7617363929748535s
Availability | SPARQL endpoint availability check for Catalogue of Life in China 2003 Edition took 3.4259212017059326s
Availability | VoID file availability check for Catalogue of Life in China 2003 Edition took 0.00030350685119628906s
Completeness | Calculation of interlinking completeness for Catalogue of Life in China 2003 Edition took 0.2862858772277832s
Reputation | Calculation of the PageRank for Catalogue of Life in China 2003 Edition took 0.02038431167602539s
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.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Catalogue of Life in China 2003 Edition took 8.440017700195312e-05s
Believability | Calculation of trust value for Catalogue of Life in China 2003 Edition took 1.3589859008789062e-05s
INFO | --- Analysis for CoLChina_sp2000 took 7.437223196029663s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 0.06022191047668457s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.0005321502685546875s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 0.2850229740142822s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.02149510383605957s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0007417201995849609s
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.430511474609375e-05s
INFO | --- Analysis for colinda took 2.7603824138641357s
Availability | SPARQL endpoint availability check for CN  2012 took 26.06163263320923s
Availability | VoID file availability check for CN  2012 took 0.0008285045623779297s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.28068089485168457s
Reputation | Calculation of the PageRank for CN  2012 took 0.021028757095336914s
Interlinking | Calculation of Degree of Connection for CN  2012 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CN  2012 took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 3.910064697265625e-05s
Believability | Calculation of trust value for CN  2012 took 1.0013580322265625e-05s
INFO | --- Analysis for combined-nomenclature-2012 took 124.65379309654236s
Availability | SPARQL endpoint availability check for Computational Historical Semantics in LiLa took 0.4629323482513428s
Availability | VoID file availability check for Computational Historical Semantics in LiLa took 0.00061798095703125s
Completeness | Calculation of interlinking completeness for Computational Historical Semantics in LiLa took 0.26875925064086914s
Reputation | Calculation of the PageRank for Computational Historical Semantics in LiLa took 0.020836830139160156s
Interlinking | Calculation of Degree of Connection for Computational Historical Semantics in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Computational Historical Semantics in LiLa took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Computational Historical Semantics in LiLa took 4.220008850097656e-05s
Believability | Calculation of trust value for Computational Historical Semantics in LiLa took 1.0251998901367188e-05s
INFO | --- Analysis for CompHistSem took 4.082971572875977s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 1.6580398082733154s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.0007569789886474609s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 0.29187464714050293s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.0224151611328125s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 4.482269287109375e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 1.1682510375976562e-05s
INFO | --- Analysis for comsode-d3-2 took 7.699483633041382s
Availability | SPARQL endpoint availability check for 2011 US Congress People took 9.179115295410156e-05s
Availability | VoID file availability check for 2011 US Congress People took 0.0006537437438964844s
Completeness | Calculation of interlinking completeness for 2011 US Congress People took 0.28374767303466797s
Reputation | Calculation of the PageRank for 2011 US Congress People took 0.022874832153320312s
Interlinking | Calculation of Degree of Connection for 2011 US Congress People took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for 2011 US Congress People took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for 2011 US Congress People took 8.749961853027344e-05s
Believability | Calculation of trust value for 2011 US Congress People took 1.0728836059570312e-05s
INFO | --- Analysis for congresspeople took 3.19307804107666s
Availability | SPARQL endpoint availability check for MIMO took 0.3124990463256836s
Availability | VoID file availability check for MIMO took 0.0006494522094726562s
Completeness | Calculation of interlinking completeness for MIMO took 0.28737592697143555s
Reputation | Calculation of the PageRank for MIMO took 0.021958589553833008s
Interlinking | Calculation of Degree of Connection for MIMO took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for MIMO took 0.0007979869842529297s
Interlinking | Calculation of Clustering coefficient for MIMO took 1.5735626220703125e-05s
Believability | Calculation of trust value for MIMO took 1.5020370483398438e-05s
INFO | --- Analysis for CONNECTED took 4.0361328125s
Availability | SPARQL endpoint availability check for Copyright Free Music took 4.696846008300781e-05s
Availability | VoID file availability check for Copyright Free Music took 0.0008080005645751953s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 0.2874746322631836s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.020494937896728516s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 3.552436828613281e-05s
Believability | Calculation of trust value for Copyright Free Music took 1.4781951904296875e-05s
INFO | --- Analysis for Copyright_Free_Music took 3.489224910736084s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 4.696846008300781e-05s
Availability | VoID file availability check for CopyrightTermBank took 0.0006475448608398438s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 0.29309701919555664s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.020735740661621094s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 7.486343383789062e-05s
Believability | Calculation of trust value for CopyrightTermBank took 1.33514404296875e-05s
INFO | --- Analysis for copyrighttermbank took 34.14587092399597s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 2.6089792251586914s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.0007085800170898438s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.2900385856628418s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.020734310150146484s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 4.6253204345703125e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 1.4781951904296875e-05s
INFO | --- Analysis for core took 8.161945104598999s
Availability | SPARQL endpoint availability check for Corine linked dataset @PSNC took 0.5730788707733154s
Availability | VoID file availability check for Corine linked dataset @PSNC took 0.0005238056182861328s
Extra | Recovery of all triples for Corine linked dataset @PSNC took 120.84579968452454s
Performance | Total latancy measurement for Corine linked dataset @PSNC took 0.9966988563537598s
Amount of data | Number of triples check for Corine linked dataset @PSNC took 9.80083966255188s
Interoperability | New terms check for Corine linked dataset @PSNC took 14.492656230926514s
Versatility | Languages check for Corine linked dataset @PSNC took 300.2008271217346s
Interpretability | Number of blank nodes check for Corine linked dataset @PSNC took 2.312492847442627s
Interpretability | RDF structures check for Corine linked dataset @PSNC took 0.3288264274597168s
Versatility | Serialization formats check for Corine linked dataset @PSNC took 9.413224458694458s
Availability | RDF dump link check for Corine linked dataset @PSNC took 0.3247549533843994s
License | MR license check for Corine linked dataset @PSNC took 0.9492771625518799s
License | HR license check for Corine linked dataset @PSNC took 300.2074337005615s
Amount of data | Number of property check for Corine linked dataset @PSNC took 0.21148467063903809s
Understandability | Number of label check for Corine linked dataset @PSNC took 3.198472499847412s
Understandability | URI regex check for Corine linked dataset @PSNC took 1.3745081424713135s
Understandability | Vocabs check for Corine linked dataset @PSNC took 0.6697788238525391s
Verifiability | Authors check for Corine linked dataset @PSNC took 0.22026491165161133s
Verifiability | Publishers check for Corine linked dataset @PSNC took 0.23589396476745605s
Performance | Throughput check for Corine linked dataset @PSNC took 11.109880685806274s
Amount of data | Check the number of entities for Corine linked dataset @PSNC took 7.104873657226562e-05s
Verifiability | Contribs. check for Corine linked dataset @PSNC took 0.20429039001464844s
Interlinking | sameAs chians check for Corine linked dataset @PSNC took 0.20238804817199707s
Interlinking | skos check for Corine linked dataset @PSNC took 0.5126888751983643s
Interlinking | skos check for Corine linked dataset @PSNC took 0.4461400508880615s
Timeliness | dataset update frequency check for Corine linked dataset @PSNC took 5.4713404178619385s
Currency | Creation date check for Corine linked dataset @PSNC took 0.4741358757019043s
Currency | Modification date check for Corine linked dataset @PSNC took 0.2371387481689453s
Rep.Conc. | URIs length for Corine linked dataset @PSNC took 159.0521559715271s
Interoperability | New vocabularies check for Corine linked dataset @PSNC took 1.239776611328125e-05s
Consistency | Deprecated classes/propertiers check for Corine linked dataset @PSNC took 0.21349787712097168s
Accuracy | Check Functional Property for Corine linked dataset @PSNC took 0.44432687759399414s
Accuracy | Check Inverse Functional Property for Corine linked dataset @PSNC took 0.4311952590942383s
Accuracy | Check Empty annotation labels for Corine linked dataset @PSNC took 34.25541305541992s
Accuracy | Check White space in annotation for Corine linked dataset @PSNC took 2.6890273094177246s
Accuracy | Check Datatype consistency for Corine linked dataset @PSNC took 2.6407408714294434s
Consistency | Disjoint class check for Corine linked dataset @PSNC took 0.1828300952911377s
Consistency | Check Misplaced properties for Corine linked dataset @PSNC took 87.5717601776123s
Consistency | Misplaced classes for Corine linked dataset @PSNC took 8.416463136672974s
Consistency | Check Ontology hijacking for Corine linked dataset @PSNC took 33.337456703186035s
Consistency | Check Invalid usage of undefined classes for Corine linked dataset @PSNC took 1.4945826530456543s
Consistency | Check Invalid usage of undefined properties for Corine linked dataset @PSNC took 89.1121609210968s
Conciseness | Check Extensional conciseness for Corine linked dataset @PSNC took 2.7517924308776855s
Conciseness | Check Intensional conciseness for Corine linked dataset @PSNC took 0.535658597946167s
Security | Sign check for Corine linked dataset @PSNC took 1.677887201309204s
Availability | Check URIs Dereferenciability for Corine linked dataset @PSNC took 10.011680841445923s
Completeness | Calculation of interlinking completeness for Corine linked dataset @PSNC took 0.783623456954956s
Reputation | Calculation of the PageRank for Corine linked dataset @PSNC took 0.02224278450012207s
Interlinking | Calculation of Degree of Connection for Corine linked dataset @PSNC took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Corine linked dataset @PSNC took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Corine linked dataset @PSNC took 4.744529724121094e-05s
Interoperability | Check the re-using of existing vocabs for Corine linked dataset @PSNC took 2.1457672119140625e-06s
Believability | Calculation of trust value for Corine linked dataset @PSNC took 1.3113021850585938e-05s
INFO | --- Analysis for Corine_linked_dataset took 2290.424781560898s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 9.417533874511719e-05s
Availability | VoID file availability check for Cornetto1.2 took 0.0006613731384277344s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.28690314292907715s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.020932912826538086s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0008084774017333984s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 6.699562072753906e-05s
Believability | Calculation of trust value for Cornetto1.2 took 1.0967254638671875e-05s
INFO | --- Analysis for cornetto took 12.961597681045532s
Availability | SPARQL endpoint availability check for Corporate Body Named Authority List  took 0.1581277847290039s
Availability | VoID file availability check for Corporate Body Named Authority List  took 0.0003533363342285156s
Extra | Recovery of all triples for Corporate Body Named Authority List  took 220.36548042297363s
Performance | Total latancy measurement for Corporate Body Named Authority List  took 0.588414192199707s
Amount of data | Number of triples check for Corporate Body Named Authority List  took 126.27375197410583s
Interoperability | New terms check for Corporate Body Named Authority List  took 54.835206747055054s
Versatility | Languages check for Corporate Body Named Authority List  took 300.04875445365906s
Interpretability | Number of blank nodes check for Corporate Body Named Authority List  took 61.675349712371826s
Security | Check HTTPS for Corporate Body Named Authority List  took 0.37381434440612793s
Interpretability | RDF structures check for Corporate Body Named Authority List  took 0.6681962013244629s
Versatility | Serialization formats check for Corporate Body Named Authority List  took 3.529019355773926s
Availability | RDF dump link check for Corporate Body Named Authority List  took 0.19958972930908203s
License | MR license check for Corporate Body Named Authority List  took 0.36600279808044434s
License | HR license check for Corporate Body Named Authority List  took 300.106249332428s
Amount of data | Number of property check for Corporate Body Named Authority List  took 0.15622782707214355s
Understandability | Number of label check for Corporate Body Named Authority List  took 2.168070077896118s
Understandability | URI regex check for Corporate Body Named Authority List  took 0.3872063159942627s
Understandability | Vocabs check for Corporate Body Named Authority List  took 0.10597467422485352s
Verifiability | Authors check for Corporate Body Named Authority List  took 0.13231587409973145s
Verifiability | Publishers check for Corporate Body Named Authority List  took 0.23421454429626465s
Performance | Throughput check for Corporate Body Named Authority List  took 10.555971384048462s
Amount of data | Check the number of entities for Corporate Body Named Authority List  took 8.559226989746094e-05s
Verifiability | Contribs. check for Corporate Body Named Authority List  took 0.2257688045501709s
Interlinking | sameAs chians check for Corporate Body Named Authority List  took 5.998937368392944s
Interlinking | skos check for Corporate Body Named Authority List  took 0.4194827079772949s
Interlinking | skos check for Corporate Body Named Authority List  took 0.3059673309326172s
Timeliness | dataset update frequency check for Corporate Body Named Authority List  took 0.23745465278625488s
Currency | Creation date check for Corporate Body Named Authority List  took 0.4346792697906494s
Currency | Modification date check for Corporate Body Named Authority List  took 0.13373541831970215s
Rep.Conc. | URIs length for Corporate Body Named Authority List  took 412.3929388523102s
Interoperability | New vocabularies check for Corporate Body Named Authority List  took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for Corporate Body Named Authority List  took 0.14884448051452637s
Accuracy | Check Functional Property for Corporate Body Named Authority List  took 0.18607330322265625s
Accuracy | Check Inverse Functional Property for Corporate Body Named Authority List  took 0.16314101219177246s
Accuracy | Check Empty annotation labels for Corporate Body Named Authority List  took 40.00560665130615s
Accuracy | Check White space in annotation for Corporate Body Named Authority List  took 3.070981025695801s
Accuracy | Check Datatype consistency for Corporate Body Named Authority List  took 2.6503446102142334s
Consistency | Disjoint class check for Corporate Body Named Authority List  took 0.17783451080322266s
Consistency | Check Misplaced properties for Corporate Body Named Authority List  took 300.56957721710205s
Consistency | Misplaced classes for Corporate Body Named Authority List  took 8.567944288253784s
Consistency | Check Ontology hijacking for Corporate Body Named Authority List  took 36.88271951675415s
Consistency | Check Invalid usage of undefined classes for Corporate Body Named Authority List  took 1.9117958545684814s
Consistency | Check Invalid usage of undefined properties for Corporate Body Named Authority List  took 301.61237621307373s
Conciseness | Check Extensional conciseness for Corporate Body Named Authority List  took 3.085958480834961s
Conciseness | Check Intensional conciseness for Corporate Body Named Authority List  took 0.38649582862854004s
Security | Sign check for Corporate Body Named Authority List  took 0.28601884841918945s
Availability | Check URIs Dereferenciability for Corporate Body Named Authority List  took 10.956511735916138s
Completeness | Calculation of interlinking completeness for Corporate Body Named Authority List  took 1.4931581020355225s
Reputation | Calculation of the PageRank for Corporate Body Named Authority List  took 0.021465539932250977s
Interlinking | Calculation of Degree of Connection for Corporate Body Named Authority List  took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Corporate Body Named Authority List  took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Corporate Body Named Authority List  took 5.817413330078125e-05s
Interoperability | Check the re-using of existing vocabs for Corporate Body Named Authority List  took 1.9073486328125e-06s
Believability | Calculation of trust value for Corporate Body Named Authority List  took 1.0013580322265625e-05s
INFO | --- Analysis for corporate-body took 14686.19414305687s
Availability | SPARQL endpoint availability check for Corpus Fibonacci in LiLa took 0.5948793888092041s
Availability | VoID file availability check for Corpus Fibonacci in LiLa took 0.00041675567626953125s
Completeness | Calculation of interlinking completeness for Corpus Fibonacci in LiLa took 0.40222883224487305s
Reputation | Calculation of the PageRank for Corpus Fibonacci in LiLa took 0.021053075790405273s
Interlinking | Calculation of Degree of Connection for Corpus Fibonacci in LiLa took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Corpus Fibonacci in LiLa took 0.0008840560913085938s
Interlinking | Calculation of Clustering coefficient for Corpus Fibonacci in LiLa took 7.200241088867188e-05s
Believability | Calculation of trust value for Corpus Fibonacci in LiLa took 1.0251998901367188e-05s
INFO | --- Analysis for CorpusFibonacci took 4.934586763381958s
Availability | SPARQL endpoint availability check for Country Name Authority List took 0.12205624580383301s
Availability | VoID file availability check for Country Name Authority List took 0.000423431396484375s
Extra | Recovery of all triples for Country Name Authority List took 163.33673810958862s
Performance | Total latancy measurement for Country Name Authority List took 0.6379430294036865s
Amount of data | Number of triples check for Country Name Authority List took 78.71823120117188s
Interoperability | New terms check for Country Name Authority List took 59.75877618789673s
Versatility | Languages check for Country Name Authority List took 300.02872705459595s
Interpretability | Number of blank nodes check for Country Name Authority List took 15.264073610305786s
Security | Check HTTPS for Country Name Authority List took 0.34606099128723145s
Interpretability | RDF structures check for Country Name Authority List took 0.4060709476470947s
Versatility | Serialization formats check for Country Name Authority List took 3.248852491378784s
Availability | RDF dump link check for Country Name Authority List took 0.22086739540100098s
License | MR license check for Country Name Authority List took 0.3635878562927246s
License | HR license check for Country Name Authority List took 300.1054286956787s
Amount of data | Number of property check for Country Name Authority List took 0.16381216049194336s
Understandability | Number of label check for Country Name Authority List took 1.6025116443634033s
Understandability | URI regex check for Country Name Authority List took 0.35784220695495605s
Understandability | Vocabs check for Country Name Authority List took 0.0968170166015625s
Verifiability | Authors check for Country Name Authority List took 0.10707402229309082s
Verifiability | Publishers check for Country Name Authority List took 0.19242286682128906s
Performance | Throughput check for Country Name Authority List took 10.449068069458008s
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.1070713996887207s
Interlinking | sameAs chians check for Country Name Authority List took 6.0659544467926025s
Interlinking | skos check for Country Name Authority List took 0.3371419906616211s
Interlinking | skos check for Country Name Authority List took 0.14361310005187988s
Timeliness | dataset update frequency check for Country Name Authority List took 0.34886956214904785s
Currency | Creation date check for Country Name Authority List took 0.27591872215270996s
Currency | Modification date check for Country Name Authority List took 0.1410973072052002s
Rep.Conc. | URIs length for Country Name Authority List took 414.09918189048767s
Interoperability | New vocabularies check for Country Name Authority List took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for Country Name Authority List took 0.1687459945678711s
Accuracy | Check Functional Property for Country Name Authority List took 0.16727781295776367s
Accuracy | Check Inverse Functional Property for Country Name Authority List took 0.15839242935180664s
Accuracy | Check Empty annotation labels for Country Name Authority List took 38.53882431983948s
Accuracy | Check White space in annotation for Country Name Authority List took 3.187532901763916s
Accuracy | Check Datatype consistency for Country Name Authority List took 2.6837856769561768s
Consistency | Disjoint class check for Country Name Authority List took 0.1301884651184082s
Consistency | Check Misplaced properties for Country Name Authority List took 300.36092615127563s
Consistency | Misplaced classes for Country Name Authority List took 8.54156756401062s
Consistency | Check Ontology hijacking for Country Name Authority List took 61.12779712677002s
Consistency | Check Invalid usage of undefined classes for Country Name Authority List took 1.933669090270996s
Consistency | Check Invalid usage of undefined properties for Country Name Authority List took 301.67552399635315s
Conciseness | Check Extensional conciseness for Country Name Authority List took 3.143800735473633s
Conciseness | Check Intensional conciseness for Country Name Authority List took 0.4248344898223877s
Security | Sign check for Country Name Authority List took 0.3817014694213867s
Availability | Check URIs Dereferenciability for Country Name Authority List took 12.153168201446533s
Completeness | Calculation of interlinking completeness for Country Name Authority List took 0.6880168914794922s
Reputation | Calculation of the PageRank for Country Name Authority List took 0.021530866622924805s
Interlinking | Calculation of Degree of Connection for Country Name Authority List took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Country Name Authority List took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for Country Name Authority List took 6.389617919921875e-05s
Interoperability | Check the re-using of existing vocabs for Country Name Authority List took 2.384185791015625e-06s
Believability | Calculation of trust value for Country Name Authority List took 1.4781951904296875e-05s
INFO | --- Analysis for country-authority-list took 14821.369809627533s
Availability | SPARQL endpoint availability check for Courts thesaurus took 0.07603120803833008s
Availability | VoID file availability check for Courts thesaurus took 0.0005958080291748047s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 0.27710986137390137s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.020780324935913086s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 7.510185241699219e-05s
Believability | Calculation of trust value for Courts thesaurus took 1.3828277587890625e-05s
INFO | --- Analysis for courts-thesaurus took 2.5954055786132812s
Availability | SPARQL endpoint availability check for Covid-on-the-Web Dataset took 20.361077785491943s
Availability | VoID file availability check for Covid-on-the-Web Dataset took 0.0008084774017333984s
Completeness | Calculation of interlinking completeness for Covid-on-the-Web Dataset took 0.27665162086486816s
Reputation | Calculation of the PageRank for Covid-on-the-Web Dataset took 0.020615816116333008s
Interlinking | Calculation of Degree of Connection for Covid-on-the-Web Dataset took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Covid-on-the-Web Dataset took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Covid-on-the-Web Dataset took 8.58306884765625e-05s
Believability | Calculation of trust value for Covid-on-the-Web Dataset took 1.33514404296875e-05s
INFO | --- Analysis for Covid-on-the-Web took 54.96208143234253s
Availability | SPARQL endpoint availability check for CPA 2008 took 29.561636924743652s
Availability | VoID file availability check for CPA 2008 took 0.0009427070617675781s
Completeness | Calculation of interlinking completeness for CPA 2008 took 0.2775111198425293s
Reputation | Calculation of the PageRank for CPA 2008 took 0.02105259895324707s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 4.6253204345703125e-05s
Believability | Calculation of trust value for CPA 2008 took 9.775161743164062e-06s
INFO | --- Analysis for cpa-2008 took 128.24606466293335s
Availability | SPARQL endpoint availability check for Cooperative Patent Classification took 0.3581273555755615s
Availability | VoID file availability check for Cooperative Patent Classification took 0.0006489753723144531s
Extra | Recovery of all triples for Cooperative Patent Classification took 25.385905504226685s
Performance | Total latancy measurement for Cooperative Patent Classification took 1.4258472919464111s
Amount of data | Number of triples check for Cooperative Patent Classification took 90.225332736969s
Versatility | Languages check for Cooperative Patent Classification took 100.17398023605347s
Interpretability | Number of blank nodes check for Cooperative Patent Classification took 90.3004424571991s
Interpretability | RDF structures check for Cooperative Patent Classification took 0.2664451599121094s
Versatility | Serialization formats check for Cooperative Patent Classification took 0.20207738876342773s
Availability | RDF dump link check for Cooperative Patent Classification took 0.19678640365600586s
License | MR license check for Cooperative Patent Classification took 0.18588662147521973s
License | HR license check for Cooperative Patent Classification took 90.17057204246521s
Amount of data | Number of property check for Cooperative Patent Classification took 0.21184206008911133s
Understandability | Number of label check for Cooperative Patent Classification took 90.16034889221191s
Understandability | URI regex check for Cooperative Patent Classification took 0.38236498832702637s
Understandability | Vocabs check for Cooperative Patent Classification took 0.20831704139709473s
Verifiability | Authors check for Cooperative Patent Classification took 0.25920701026916504s
Verifiability | Publishers check for Cooperative Patent Classification took 0.25031185150146484s
Performance | Throughput check for Cooperative Patent Classification took 10.960247039794922s
Amount of data | Check the number of entities for Cooperative Patent Classification took 7.05718994140625e-05s
Verifiability | Contribs. check for Cooperative Patent Classification took 0.17933869361877441s
Interlinking | sameAs chians check for Cooperative Patent Classification took 0.16963624954223633s
Interlinking | skos check for Cooperative Patent Classification took 0.234236478805542s
Interlinking | skos check for Cooperative Patent Classification took 0.1672208309173584s
Timeliness | dataset update frequency check for Cooperative Patent Classification took 0.16598963737487793s
Currency | Creation date check for Cooperative Patent Classification took 0.5162718296051025s
Currency | Modification date check for Cooperative Patent Classification took 0.36259913444519043s
Rep.Conc. | URIs length for Cooperative Patent Classification took 142.23682761192322s
Interoperability | New vocabularies check for Cooperative Patent Classification took 4.5299530029296875e-06s
Consistency | Deprecated classes/propertiers check for Cooperative Patent Classification took 0.2108290195465088s
Accuracy | Check Empty annotation labels for Cooperative Patent Classification took 18.870526790618896s
Accuracy | Check White space in annotation for Cooperative Patent Classification took 3.0035176277160645s
Accuracy | Check Datatype consistency for Cooperative Patent Classification took 5.004977703094482s
Consistency | Disjoint class check for Cooperative Patent Classification took 0.3009769916534424s
Consistency | Check Misplaced properties for Cooperative Patent Classification took 100.45465850830078s
Consistency | Check Ontology hijacking for Cooperative Patent Classification took 22.416769981384277s
Consistency | Check Invalid usage of undefined classes for Cooperative Patent Classification took 1.7836713790893555s
Consistency | Check Invalid usage of undefined properties for Cooperative Patent Classification took 101.85176062583923s
Conciseness | Check Extensional conciseness for Cooperative Patent Classification took 2.8888702392578125s
Conciseness | Check Intensional conciseness for Cooperative Patent Classification took 0.366943359375s
Security | Sign check for Cooperative Patent Classification took 0.2779200077056885s
Availability | Check URIs Dereferenciability for Cooperative Patent Classification took 1.552150011062622s
Completeness | Calculation of interlinking completeness for Cooperative Patent Classification took 0.570518970489502s
Reputation | Calculation of the PageRank for Cooperative Patent Classification took 0.02172398567199707s
Interlinking | Calculation of Degree of Connection for Cooperative Patent Classification took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Cooperative Patent Classification took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Cooperative Patent Classification took 0.0001800060272216797s
Interoperability | Check the re-using of existing vocabs for Cooperative Patent Classification took 1.9073486328125e-06s
Believability | Calculation of trust value for Cooperative Patent Classification took 1.4066696166992188e-05s
INFO | --- Analysis for CPC took 1199.5663890838623s
Availability | SPARQL endpoint availability check for CPC 2008 took 25.06915259361267s
Availability | VoID file availability check for CPC 2008 took 0.0008928775787353516s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.27105069160461426s
Reputation | Calculation of the PageRank for CPC 2008 took 0.023407459259033203s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for CPC 2008 took 0.001115560531616211s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 5.435943603515625e-05s
Believability | Calculation of trust value for CPC 2008 took 1.0251998901367188e-05s
INFO | --- Analysis for cpc-2008 took 123.74433970451355s
Availability | SPARQL endpoint availability check for CPV  2003 took 20.726913928985596s
Availability | VoID file availability check for CPV  2003 took 0.0006947517395019531s
Completeness | Calculation of interlinking completeness for CPV  2003 took 0.3418312072753906s
Reputation | Calculation of the PageRank for CPV  2003 took 0.0207827091217041s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 3.910064697265625e-05s
Believability | Calculation of trust value for CPV  2003 took 6.198883056640625e-06s
INFO | --- Analysis for cpv-2003 took 113.7552011013031s
Availability | SPARQL endpoint availability check for CPV 2008 took 24.525972843170166s
Availability | VoID file availability check for CPV 2008 took 0.000583648681640625s
Completeness | Calculation of interlinking completeness for CPV 2008 took 0.2771177291870117s
Reputation | Calculation of the PageRank for CPV 2008 took 0.02171802520751953s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 5.8650970458984375e-05s
Believability | Calculation of trust value for CPV 2008 took 1.049041748046875e-05s
INFO | --- Analysis for cpv-2008 took 123.2425742149353s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 261.85094451904297s
Availability | VoID file availability check for crowdsourcing-fb took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 0.2697432041168213s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.0221707820892334s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.0011532306671142578s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 6.508827209472656e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 9.775161743164062e-06s
INFO | --- Analysis for crowdsourcing-fb took 536.8418068885803s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 6.572824716567993s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.0005276203155517578s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 0.32900094985961914s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.020978212356567383s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 6.29425048828125e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 9.5367431640625e-06s
INFO | --- Analysis for ctic-public-dataset took 40.749504804611206s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 0.4340987205505371s
Availability | VoID file availability check for CulturaLinkedData took 0.0006318092346191406s
Extra | Recovery of all triples for CulturaLinkedData took 133.33905506134033s
Performance | Total latancy measurement for CulturaLinkedData took 4.313944101333618s
Amount of data | Number of triples check for CulturaLinkedData took 0.8027462959289551s
Interoperability | New terms check for CulturaLinkedData took 4.171727657318115s
Versatility | Languages check for CulturaLinkedData took 61.939101696014404s
Interpretability | Number of blank nodes check for CulturaLinkedData took 0.1694793701171875s
Interpretability | RDF structures check for CulturaLinkedData took 0.4936842918395996s
Versatility | Serialization formats check for CulturaLinkedData took 2.296020030975342s
Availability | RDF dump link check for CulturaLinkedData took 2.021653175354004s
License | MR license check for CulturaLinkedData took 2.4576985836029053s
License | HR license check for CulturaLinkedData took 62.19936776161194s
Amount of data | Number of property check for CulturaLinkedData took 0.17381763458251953s
Understandability | Number of label check for CulturaLinkedData took 2.783313035964966s
Understandability | URI regex check for CulturaLinkedData took 2.3113105297088623s
Understandability | Vocabs check for CulturaLinkedData took 1.9907827377319336s
Verifiability | Authors check for CulturaLinkedData took 0.2841799259185791s
Verifiability | Publishers check for CulturaLinkedData took 0.2387692928314209s
Performance | Throughput check for CulturaLinkedData took 20.83478331565857s
Amount of data | Check the number of entities for CulturaLinkedData took 7.867813110351562e-05s
Verifiability | Contribs. check for CulturaLinkedData took 0.23067522048950195s
Interlinking | sameAs chians check for CulturaLinkedData took 0.32157325744628906s
Interlinking | skos check for CulturaLinkedData took 2.1991872787475586s
Interlinking | skos check for CulturaLinkedData took 0.17009687423706055s
Timeliness | dataset update frequency check for CulturaLinkedData took 2.006523847579956s
Currency | Creation date check for CulturaLinkedData took 2.1983561515808105s
Currency | Modification date check for CulturaLinkedData took 0.34706830978393555s
Rep.Conc. | URIs length for CulturaLinkedData took 55.546632528305054s
Interoperability | New vocabularies check for CulturaLinkedData took 1.2636184692382812e-05s
Consistency | Deprecated classes/propertiers check for CulturaLinkedData took 0.17033171653747559s
Accuracy | Check Functional Property for CulturaLinkedData took 0.17281651496887207s
Accuracy | Check Inverse Functional Property for CulturaLinkedData took 1.9300894737243652s
Accuracy | Check Empty annotation labels for CulturaLinkedData took 40.486058712005615s
Accuracy | Check White space in annotation for CulturaLinkedData took 1.6331381797790527s
Accuracy | Check Datatype consistency for CulturaLinkedData took 1.315462589263916s
Consistency | Disjoint class check for CulturaLinkedData took 0.19971394538879395s
Consistency | Check Misplaced properties for CulturaLinkedData took 8.373149394989014s
Consistency | Misplaced classes for CulturaLinkedData took 4.2823474407196045s
Consistency | Check Ontology hijacking for CulturaLinkedData took 42.52501440048218s
Consistency | Check Invalid usage of undefined classes for CulturaLinkedData took 1.449765682220459s
Consistency | Check Invalid usage of undefined properties for CulturaLinkedData took 11.348932027816772s
Conciseness | Check Extensional conciseness for CulturaLinkedData took 1.3851120471954346s
Conciseness | Check Intensional conciseness for CulturaLinkedData took 1.9978744983673096s
Security | Sign check for CulturaLinkedData took 0.862800121307373s
Availability | Check URIs Dereferenciability for CulturaLinkedData took 9.492949485778809s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 0.3503720760345459s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.02122211456298828s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 4.4345855712890625e-05s
Interoperability | Check the re-using of existing vocabs for CulturaLinkedData took 2.1457672119140625e-06s
Believability | Calculation of trust value for CulturaLinkedData took 1.4066696166992188e-05s
INFO | --- Analysis for culturalinkeddata took 607.912529706955s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.24595165252685547s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0004532337188720703s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.2788689136505127s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.020448923110961914s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 4.887580871582031e-05s
Believability | Calculation of trust value for Data about business entities from the ARES system - business registry of the Czech Republic took 6.4373016357421875e-06s
INFO | --- Analysis for cz-ares-or took 2.9142889976501465s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.10172319412231445s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0007257461547851562s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.2671175003051758s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.020656347274780273s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 3.838539123535156e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 4.76837158203125e-06s
INFO | --- Analysis for cz-ares-rzp took 2.7395758628845215s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 0.10564565658569336s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.0005924701690673828s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.2670328617095947s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.0205843448638916s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.0008039474487304688s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 3.743171691894531e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 6.198883056640625e-06s
INFO | --- Analysis for cz-cenia-irz-chemicals took 2.8614578247070312s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 0.10123014450073242s
Availability | VoID file availability check for Integrated pollution registry took 0.0005497932434082031s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.26895594596862793s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.021118640899658203s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0007836818695068359s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 4.601478576660156e-05s
Believability | Calculation of trust value for Integrated pollution registry took 7.867813110351562e-06s
INFO | --- Analysis for cz-cenia-pollution took 2.8857614994049072s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 0.10157561302185059s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.0005338191986083984s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.27626633644104004s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.022151947021484375s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.000946044921875s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Contracts took 5.245208740234375e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Contracts took 1.0251998901367188e-05s
INFO | --- Analysis for cz-contracts took 2.817863702774048s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 0.10315895080566406s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.0005950927734375s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.2654764652252197s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.02124762535095215s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 3.9577484130859375e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 9.298324584960938e-06s
INFO | --- Analysis for cz-ctia-bans took 5.738617658615112s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 0.10088849067687988s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 0.27495384216308594s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.0205230712890625s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 3.910064697265625e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 1.0728836059570312e-05s
INFO | --- Analysis for cz-ctia-confiscations took 2.802489995956421s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.10131430625915527s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.0008094310760498047s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.27341532707214355s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.022745847702026367s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.000804901123046875s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 4.076957702636719e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 9.298324584960938e-06s
INFO | --- Analysis for cz-ctia-focus took 2.7711079120635986s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 0.10292196273803711s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 0.28185129165649414s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.020793437957763672s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 4.7206878662109375e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 1.0013580322265625e-05s
INFO | --- Analysis for cz-ctia-inspections took 2.8212835788726807s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 0.10232257843017578s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.0005662441253662109s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.2719254493713379s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.021775484085083008s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 4.1961669921875e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 1.0013580322265625e-05s
INFO | --- Analysis for cz-ctia-sanctions took 4.702303409576416s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 0.18214130401611328s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.0012125968933105469s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.26856327056884766s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.02068042755126953s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 4.2438507080078125e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 1.049041748046875e-05s
INFO | --- Analysis for cz-cuzk-cadastre-offices took 2.878584146499634s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 0.10295319557189941s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.0005633831024169922s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.2636597156524658s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.021561622619628906s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 3.814697265625e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 1.0728836059570312e-05s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 2.8196542263031006s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 0.5302114486694336s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.0005397796630859375s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.27094531059265137s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.0204012393951416s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 4.38690185546875e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 1.0728836059570312e-05s
INFO | --- Analysis for cz-czso-average-salaries took 3.399567127227783s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 0.3216257095336914s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 0.27406764030456543s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.021608352661132812s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 4.601478576660156e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 1.0967254638671875e-05s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 3.256308078765869s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.32035231590270996s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0013096332550048828s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.26694655418395996s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.020537853240966797s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 4.1961669921875e-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.1957149505615234s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 0.32398152351379395s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.2702932357788086s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.02268695831298828s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 4.1961669921875e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 9.5367431640625e-06s
INFO | --- Analysis for cz-czso-job-applicants took 3.2182722091674805s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.31911373138427734s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.27253222465515137s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.02056884765625s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 4.172325134277344e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 1.0251998901367188e-05s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 3.2149155139923096s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.3215034008026123s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0008454322814941406s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.2643551826477051s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.021361827850341797s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 4.220008850097656e-05s
Believability | Calculation of trust value for Structure of regions of Czech Republic according to Czech Statistical Office took 9.775161743164062e-06s
INFO | --- Analysis for cz-czso-regions took 2.9803519248962402s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 0.3215057849884033s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 0.2656710147857666s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.021662235260009766s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 4.57763671875e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 9.059906005859375e-06s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 3.2175333499908447s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 0.32155466079711914s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.2654750347137451s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.020811796188354492s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 4.3392181396484375e-05s
Believability | Calculation of trust value for Social service facilities and nursing in districts of Czech republic took 6.198883056640625e-06s
INFO | --- Analysis for cz-czso-social-service-facilities took 3.2549996376037598s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 0.322145938873291s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.2701749801635742s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.02062201499938965s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 4.482269287109375e-05s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 1.0967254638671875e-05s
INFO | --- Analysis for cz-czso-unemployment-rate took 3.2246904373168945s
Availability | SPARQL endpoint availability check for ATC groups took 0.10106587409973145s
Availability | VoID file availability check for ATC groups took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for ATC groups took 0.2666785717010498s
Reputation | Calculation of the PageRank for ATC groups took 0.022644519805908203s
Interlinking | Calculation of Degree of Connection for ATC groups took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.0008571147918701172s
Interlinking | Calculation of Clustering coefficient for ATC groups took 9.393692016601562e-05s
Believability | Calculation of trust value for ATC groups took 1.4781951904296875e-05s
INFO | --- Analysis for cz-eh-1-atc took 2.794142007827759s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.10184383392333984s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0005750656127929688s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.2743210792541504s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.020550012588500977s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Financial fulfillments took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 4.100799560546875e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 7.152557373046875e-06s
INFO | --- Analysis for cz-fulfillments took 2.7601675987243652s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 0.03425860404968262s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.00036525726318359375s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.26467013359069824s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.021387338638305664s
Interlinking | Calculation of Degree of Connection for Czech Business Entity identification numbers and names took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Czech Business Entity identification numbers and names took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 5.7697296142578125e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 1.0728836059570312e-05s
INFO | --- Analysis for cz-ic took 3.098672866821289s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 0.11498689651489258s
Availability | VoID file availability check for List of Czech data boxes took 0.0006501674652099609s
Extra | Recovery of all triples for List of Czech data boxes took 146.6224946975708s
Performance | Total latancy measurement for List of Czech data boxes took 0.5454611778259277s
Amount of data | Number of triples check for List of Czech data boxes took 10.040278911590576s
Interoperability | New terms check for List of Czech data boxes took 10.805452108383179s
Versatility | Languages check for List of Czech data boxes took 300.16571855545044s
Interpretability | Number of blank nodes check for List of Czech data boxes took 1.2096922397613525s
Interpretability | RDF structures check for List of Czech data boxes took 0.15036273002624512s
Versatility | Serialization formats check for List of Czech data boxes took 0.15596389770507812s
Availability | RDF dump link check for List of Czech data boxes took 13.747857570648193s
License | MR license check for List of Czech data boxes took 0.32009291648864746s
License | HR license check for List of Czech data boxes took 53.26115036010742s
Amount of data | Number of property check for List of Czech data boxes took 0.10789728164672852s
Understandability | Number of label check for List of Czech data boxes took 1.805638313293457s
Understandability | URI regex check for List of Czech data boxes took 0.36531949043273926s
Understandability | Vocabs check for List of Czech data boxes took 0.11325860023498535s
Verifiability | Authors check for List of Czech data boxes took 0.11436319351196289s
Verifiability | Publishers check for List of Czech data boxes took 0.11360836029052734s
Performance | Throughput check for List of Czech data boxes took 10.566624641418457s
Amount of data | Check the number of entities for List of Czech data boxes took 3.3111190795898438s
Verifiability | Contribs. check for List of Czech data boxes took 0.11003780364990234s
Interlinking | sameAs chians check for List of Czech data boxes took 0.4348325729370117s
Interlinking | skos check for List of Czech data boxes took 0.18380999565124512s
Interlinking | skos check for List of Czech data boxes took 0.10616660118103027s
Timeliness | dataset update frequency check for List of Czech data boxes took 0.21990752220153809s
Currency | Creation date check for List of Czech data boxes took 0.2326033115386963s
Currency | Modification date check for List of Czech data boxes took 0.11194467544555664s
Rep.Conc. | URIs length for List of Czech data boxes took 109.50557208061218s
Interoperability | New vocabularies check for List of Czech data boxes took 15.531704425811768s
Consistency | Deprecated classes/propertiers check for List of Czech data boxes took 0.3370382785797119s
Accuracy | Check Functional Property for List of Czech data boxes took 0.17913031578063965s
Accuracy | Check Inverse Functional Property for List of Czech data boxes took 0.17924094200134277s
Accuracy | Check Empty annotation labels for List of Czech data boxes took 30.545241355895996s
Accuracy | Check White space in annotation for List of Czech data boxes took 3.084869623184204s
Accuracy | Check Datatype consistency for List of Czech data boxes took 2.6890225410461426s
Consistency | Disjoint class check for List of Czech data boxes took 0.10679411888122559s
Consistency | Check Misplaced properties for List of Czech data boxes took 68.72448348999023s
Consistency | Misplaced classes for List of Czech data boxes took 7.700655937194824s
Consistency | Check Ontology hijacking for List of Czech data boxes took 30.608322620391846s
Consistency | Check Invalid usage of undefined classes for List of Czech data boxes took 1.5841281414031982s
Consistency | Check Invalid usage of undefined properties for List of Czech data boxes took 61.79113960266113s
Conciseness | Check Extensional conciseness for List of Czech data boxes took 2.6995809078216553s
Conciseness | Check Intensional conciseness for List of Czech data boxes took 0.36121654510498047s
Security | Sign check for List of Czech data boxes took 0.14161992073059082s
Availability | Check URIs Dereferenciability for List of Czech data boxes took 379.28482007980347s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 0.837801456451416s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.021796226501464844s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 4.887580871582031e-05s
Interoperability | Check the re-using of existing vocabs for List of Czech data boxes took 54.157400608062744s
Believability | Calculation of trust value for List of Czech data boxes took 5.936622619628906e-05s
INFO | --- Analysis for cz-list-of-databoxes took 1661.3774507045746s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11209750175476074s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0005657672882080078s
Extra | Recovery of all triples for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 143.66240882873535s
Performance | Total latancy measurement for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.6105937957763672s
Amount of data | Number of triples check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 9.9658944606781s
Interoperability | New terms check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.80337929725647s
Versatility | Languages check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 300.16809248924255s
Interpretability | Number of blank nodes check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.208733320236206s
Interpretability | RDF structures check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1065666675567627s
Versatility | Serialization formats check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1721045970916748s
Availability | RDF dump link check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 13.274969816207886s
License | MR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.5322518348693848s
License | HR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 56.83590531349182s
Amount of data | Number of property check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11960291862487793s
Understandability | Number of label check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.6010394096374512s
Understandability | URI regex check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.48096656799316406s
Understandability | Vocabs check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1152195930480957s
Verifiability | Authors check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11618757247924805s
Verifiability | Publishers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11403298377990723s
Performance | Throughput check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.802744150161743s
Amount of data | Check the number of entities for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.5002260208129883s
Verifiability | Contribs. check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1140439510345459s
Interlinking | sameAs chians check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.33896327018737793s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10685920715332031s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10962843894958496s
Timeliness | dataset update frequency check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.20978355407714844s
Currency | Creation date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.2409353256225586s
Currency | Modification date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10883617401123047s
Rep.Conc. | URIs length for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 111.73458361625671s
Interoperability | New vocabularies check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 51.84012818336487s
Consistency | Deprecated classes/propertiers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.33962512016296387s
Accuracy | Check Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1734914779663086s
Accuracy | Check Inverse Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.17328453063964844s
Accuracy | Check Empty annotation labels for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 31.27858281135559s
Accuracy | Check White space in annotation for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.100717544555664s
Accuracy | Check Datatype consistency for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.7638487815856934s
Consistency | Disjoint class check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1064608097076416s
Consistency | Check Misplaced properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 69.94982123374939s
Consistency | Misplaced classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 7.722957134246826s
Consistency | Check Ontology hijacking for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 32.093162536621094s
Consistency | Check Invalid usage of undefined classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.6016819477081299s
Consistency | Check Invalid usage of undefined properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 61.93875765800476s
Conciseness | Check Extensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.762415885925293s
Conciseness | Check Intensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.34694337844848633s
Security | Sign check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1340782642364502s
Availability | Check URIs Dereferenciability for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 373.63894629478455s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.40787577629089355s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0235598087310791s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.001016378402709961s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 5.745887756347656e-05s
Interoperability | Check the re-using of existing vocabs for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 27.788214921951294s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.0013580322265625e-05s
INFO | --- Analysis for cz-nace took 1667.1630194187164s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.28075218200683594s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.0006513595581054688s
Extra | Recovery of all triples for Czech National Open Data Catalog in DCAT-AP v1.1 took 445.58430790901184s
Performance | Total latancy measurement for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.7916648387908936s
Amount of data | Number of triples check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.451704740524292s
Interoperability | New terms check for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.6094088554382324s
Versatility | Languages check for Czech National Open Data Catalog in DCAT-AP v1.1 took 300.16315245628357s
Interpretability | Number of blank nodes check for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.3580851554870605s
Interpretability | RDF structures check for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.8837499618530273s
Versatility | Serialization formats check for Czech National Open Data Catalog in DCAT-AP v1.1 took 6.739749431610107s
Availability | RDF dump link check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.3380568027496338s
License | MR license check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.816138744354248s
License | HR license check for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.3319849967956543s
Amount of data | Number of property check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.1719071865081787s
Understandability | Number of label check for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.8575410842895508s
Understandability | URI regex check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.47942113876342773s
Understandability | Vocabs check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.23493337631225586s
Verifiability | Authors check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.4595651626586914s
Verifiability | Publishers check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.38434600830078125s
Performance | Throughput check for Czech National Open Data Catalog in DCAT-AP v1.1 took 10.96713376045227s
Amount of data | Check the number of entities for Czech National Open Data Catalog in DCAT-AP v1.1 took 7.557868957519531e-05s
Verifiability | Contribs. check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.21712660789489746s
Interlinking | sameAs chians check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.19674921035766602s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.4248161315917969s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.15849661827087402s
Timeliness | dataset update frequency check for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.570429563522339s
Currency | Creation date check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.6202132701873779s
Currency | Modification date check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.4189274311065674s
Rep.Conc. | URIs length for Czech National Open Data Catalog in DCAT-AP v1.1 took 91.41628885269165s
Interoperability | New vocabularies check for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.3113021850585938e-05s
Consistency | Deprecated classes/propertiers check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.16355109214782715s
Accuracy | Check Functional Property for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.33260440826416016s
Accuracy | Check Inverse Functional Property for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.3727760314941406s
Accuracy | Check Empty annotation labels for Czech National Open Data Catalog in DCAT-AP v1.1 took 76.20314359664917s
Accuracy | Check White space in annotation for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.4813313484191895s
Accuracy | Check Datatype consistency for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.7811598777770996s
Consistency | Disjoint class check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.2880971431732178s
Consistency | Check Misplaced properties for Czech National Open Data Catalog in DCAT-AP v1.1 took 4.336481094360352s
Consistency | Misplaced classes for Czech National Open Data Catalog in DCAT-AP v1.1 took 8.383819103240967s
Consistency | Check Ontology hijacking for Czech National Open Data Catalog in DCAT-AP v1.1 took 74.6302752494812s
Consistency | Check Invalid usage of undefined classes for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.9436488151550293s
Consistency | Check Invalid usage of undefined properties for Czech National Open Data Catalog in DCAT-AP v1.1 took 5.344881772994995s
Conciseness | Check Extensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.226454496383667s
Conciseness | Check Intensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.3243582248687744s
Security | Sign check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.43851590156555176s
Availability | Check URIs Dereferenciability for Czech National Open Data Catalog in DCAT-AP v1.1 took 914.9912443161011s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.7405519485473633s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.02800607681274414s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.0008490085601806641s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.1 took 4.673004150390625e-05s
Interoperability | Check the re-using of existing vocabs for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.1457672119140625e-06s
Believability | Calculation of trust value for Czech National Open Data Catalog in DCAT-AP v1.1 took 6.198883056640625e-06s
INFO | --- Analysis for cz-nkod took 23297.078726053238s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 0.1331634521484375s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 0.26583099365234375s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.020816326141357422s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Orders took 4.410743713378906e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Orders took 9.5367431640625e-06s
INFO | --- Analysis for cz-orders took 2.8857576847076416s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 0.16730022430419922s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.0006158351898193359s
Extra | Recovery of all triples for Institutions of public power of the Czech Republic took 143.48164200782776s
Performance | Total latancy measurement for Institutions of public power of the Czech Republic took 0.5355207920074463s
Amount of data | Number of triples check for Institutions of public power of the Czech Republic took 9.884669303894043s
Interoperability | New terms check for Institutions of public power of the Czech Republic took 10.701051235198975s
Versatility | Languages check for Institutions of public power of the Czech Republic took 300.12645053863525s
Interpretability | Number of blank nodes check for Institutions of public power of the Czech Republic took 1.3636715412139893s
Interpretability | RDF structures check for Institutions of public power of the Czech Republic took 0.11751723289489746s
Versatility | Serialization formats check for Institutions of public power of the Czech Republic took 0.16069841384887695s
Availability | RDF dump link check for Institutions of public power of the Czech Republic took 13.27286148071289s
License | MR license check for Institutions of public power of the Czech Republic took 0.47846198081970215s
License | HR license check for Institutions of public power of the Czech Republic took 55.652559757232666s
Amount of data | Number of property check for Institutions of public power of the Czech Republic took 0.10684728622436523s
Understandability | Number of label check for Institutions of public power of the Czech Republic took 1.4507999420166016s
Understandability | URI regex check for Institutions of public power of the Czech Republic took 0.5799415111541748s
Understandability | Vocabs check for Institutions of public power of the Czech Republic took 0.10862207412719727s
Verifiability | Authors check for Institutions of public power of the Czech Republic took 0.11411523818969727s
Verifiability | Publishers check for Institutions of public power of the Czech Republic took 0.11216378211975098s
Performance | Throughput check for Institutions of public power of the Czech Republic took 10.768448829650879s
Amount of data | Check the number of entities for Institutions of public power of the Czech Republic took 3.371699571609497s
Verifiability | Contribs. check for Institutions of public power of the Czech Republic took 0.1035454273223877s
Interlinking | sameAs chians check for Institutions of public power of the Czech Republic took 0.35680627822875977s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.15389585494995117s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.1041717529296875s
Timeliness | dataset update frequency check for Institutions of public power of the Czech Republic took 0.18157958984375s
Currency | Creation date check for Institutions of public power of the Czech Republic took 0.23050594329833984s
Currency | Modification date check for Institutions of public power of the Czech Republic took 0.11643314361572266s
Rep.Conc. | URIs length for Institutions of public power of the Czech Republic took 109.51097416877747s
Interoperability | New vocabularies check for Institutions of public power of the Czech Republic took 17.43204355239868s
Consistency | Deprecated classes/propertiers check for Institutions of public power of the Czech Republic took 0.3405134677886963s
Accuracy | Check Functional Property for Institutions of public power of the Czech Republic took 0.14365148544311523s
Accuracy | Check Inverse Functional Property for Institutions of public power of the Czech Republic took 0.15145182609558105s
Accuracy | Check Empty annotation labels for Institutions of public power of the Czech Republic took 30.782734155654907s
Accuracy | Check White space in annotation for Institutions of public power of the Czech Republic took 3.073324680328369s
Accuracy | Check Datatype consistency for Institutions of public power of the Czech Republic took 2.7211697101593018s
Consistency | Disjoint class check for Institutions of public power of the Czech Republic took 0.10982155799865723s
Consistency | Check Misplaced properties for Institutions of public power of the Czech Republic took 67.75012493133545s
Consistency | Misplaced classes for Institutions of public power of the Czech Republic took 7.866686105728149s
Consistency | Check Ontology hijacking for Institutions of public power of the Czech Republic took 31.673717975616455s
Consistency | Check Invalid usage of undefined classes for Institutions of public power of the Czech Republic took 1.609412431716919s
Consistency | Check Invalid usage of undefined properties for Institutions of public power of the Czech Republic took 62.073126554489136s
Conciseness | Check Extensional conciseness for Institutions of public power of the Czech Republic took 2.7161388397216797s
Conciseness | Check Intensional conciseness for Institutions of public power of the Czech Republic took 0.35848331451416016s
Security | Sign check for Institutions of public power of the Czech Republic took 0.1337282657623291s
Availability | Check URIs Dereferenciability for Institutions of public power of the Czech Republic took 371.2679672241211s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 0.39162468910217285s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.02234816551208496s
Interlinking | Calculation of Degree of Connection for Institutions of public power of the Czech Republic took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Institutions of public power of the Czech Republic took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 5.936622619628906e-05s
Interoperability | Check the re-using of existing vocabs for Institutions of public power of the Czech Republic took 50.19962739944458s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 1.049041748046875e-05s
INFO | --- Analysis for cz-ovm took 1648.6582243442535s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 0.09972929954528809s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.000614166259765625s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 0.27448034286499023s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.021582365036010742s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0009717941284179688s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 4.744529724121094e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 1.0013580322265625e-05s
INFO | --- Analysis for cz-ovm-agendas took 2.801112413406372s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10155606269836426s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0006122589111328125s
Extra | Recovery of all triples for Registry of territorial identification, addresses and real estate of the Czech Republic took 60.78395915031433s
Performance | Total latancy measurement for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.5035750865936279s
Amount of data | Number of triples check for Registry of territorial identification, addresses and real estate of the Czech Republic took 19.09061360359192s
Interoperability | New terms check for Registry of territorial identification, addresses and real estate of the Czech Republic took 33.30999183654785s
Versatility | Languages check for Registry of territorial identification, addresses and real estate of the Czech Republic took 300.08386731147766s
Interpretability | Number of blank nodes check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12252259254455566s
Interpretability | RDF structures check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.4917314052581787s
Versatility | Serialization formats check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11801862716674805s
Availability | RDF dump link check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.7250161170959473s
License | MR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1269235610961914s
License | HR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10414481163024902s
Amount of data | Number of property check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10463118553161621s
Understandability | Number of label check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.8800246715545654s
Understandability | URI regex check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.2039504051208496s
Understandability | Vocabs check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11481666564941406s
Verifiability | Authors check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1983950138092041s
Verifiability | Publishers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.09955286979675293s
Performance | Throughput check for Registry of territorial identification, addresses and real estate of the Czech Republic took 10.335099935531616s
Amount of data | Check the number of entities for Registry of territorial identification, addresses and real estate of the Czech Republic took 7.486343383789062e-05s
Verifiability | Contribs. check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10403609275817871s
Interlinking | sameAs chians check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10250234603881836s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11874103546142578s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10175061225891113s
Timeliness | dataset update frequency check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10669684410095215s
Currency | Creation date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.20503020286560059s
Currency | Modification date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10388469696044922s
Rep.Conc. | URIs length for Registry of territorial identification, addresses and real estate of the Czech Republic took 223.4484314918518s
Interoperability | New vocabularies check for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.5020370483398438e-05s
Consistency | Deprecated classes/propertiers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.16388249397277832s
Accuracy | Check Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11533212661743164s
Accuracy | Check Inverse Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11347007751464844s
Accuracy | Check Empty annotation labels for Registry of territorial identification, addresses and real estate of the Czech Republic took 13.857171773910522s
Accuracy | Check White space in annotation for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.259570360183716s
Accuracy | Check Datatype consistency for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.735839366912842s
Consistency | Disjoint class check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.120330810546875s
Consistency | Check Misplaced properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 168.1069610118866s
Consistency | Misplaced classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 8.605993270874023s
Consistency | Check Ontology hijacking for Registry of territorial identification, addresses and real estate of the Czech Republic took 18.966858625411987s
Consistency | Check Invalid usage of undefined classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.4742140769958496s
Consistency | Check Invalid usage of undefined properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 169.3571846485138s
Conciseness | Check Extensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.971648693084717s
Conciseness | Check Intensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.2590446472167969s
Security | Sign check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10724186897277832s
Availability | Check URIs Dereferenciability for Registry of territorial identification, addresses and real estate of the Czech Republic took 11.928288698196411s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.501154899597168s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.021553993225097656s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.7418136596679688e-05s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 7.677078247070312e-05s
Interoperability | Check the re-using of existing vocabs for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.6689300537109375e-06s
Believability | Calculation of trust value for Registry of territorial identification, addresses and real estate of the Czech Republic took 6.9141387939453125e-06s
INFO | --- Analysis for cz-ruian took 1462.0534689426422s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.7437958717346191s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.27547311782836914s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.020870208740234375s
Interlinking | Calculation of Degree of Connection for Audited subjects of Supreme Audit Office of the Czech Republic took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 7.677078247070312e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 1.0013580322265625e-05s
INFO | --- Analysis for cz-sao-audited-subjects took 3.8207225799560547s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.41503047943115234s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.00029158592224121094s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 0.26962757110595703s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.020818710327148438s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 4.458427429199219e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 9.5367431640625e-06s
INFO | --- Analysis for cz-sao-check-actions took 3.459542751312256s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 0.4241971969604492s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.00029206275939941406s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 0.27198123931884766s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.0206453800201416s
Interlinking | Calculation of Degree of Connection for List of laws used in inspection reports of SAO took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for List of laws used in inspection reports of SAO took 0.0008151531219482422s
Interlinking | Calculation of Clustering coefficient for List of laws used in inspection reports of SAO took 3.528594970703125e-05s
Believability | Calculation of trust value for List of laws used in inspection reports of SAO took 1.1205673217773438e-05s
INFO | --- Analysis for cz-sao-check-actions-law took 3.4981131553649902s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 0.10016965866088867s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.0007307529449462891s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 0.27392029762268066s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.020902633666992188s
Interlinking | Calculation of Degree of Connection for Active ingredients of medicinal products available in Czech Republic took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Active ingredients of medicinal products available in Czech Republic took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 3.4809112548828125e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 1.5735626220703125e-05s
INFO | --- Analysis for cz-sidc-drug-ingredients took 2.798765182495117s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.1016693115234375s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 0.2695920467376709s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.02205824851989746s
Interlinking | Calculation of Degree of Connection for List of prices of reimbursed medicinal products marketed in Czech republic took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 3.600120544433594e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 9.5367431640625e-06s
INFO | --- Analysis for cz-sidc-drug-prices took 2.7934350967407227s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 0.10078954696655273s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.000713348388671875s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 0.2681434154510498s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.020703792572021484s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 3.910064697265625e-05s
Believability | Calculation of trust value for Medicinal products marketed in Czech Republic took 8.821487426757812e-06s
INFO | --- Analysis for cz-sidc-drugs took 2.816540241241455s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 0.17694878578186035s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.0006246566772460938s
Extra | Recovery of all triples for Summary types of Czech institutions of public power took 139.9597144126892s
Performance | Total latancy measurement for Summary types of Czech institutions of public power took 0.5241234302520752s
Amount of data | Number of triples check for Summary types of Czech institutions of public power took 9.888613224029541s
Interoperability | New terms check for Summary types of Czech institutions of public power took 10.546741008758545s
Versatility | Languages check for Summary types of Czech institutions of public power took 300.16406416893005s
Interpretability | Number of blank nodes check for Summary types of Czech institutions of public power took 1.285019874572754s
Interpretability | RDF structures check for Summary types of Czech institutions of public power took 0.12466955184936523s
Versatility | Serialization formats check for Summary types of Czech institutions of public power took 0.18071937561035156s
Availability | RDF dump link check for Summary types of Czech institutions of public power took 13.296862125396729s
License | MR license check for Summary types of Czech institutions of public power took 0.39740514755249023s
License | HR license check for Summary types of Czech institutions of public power took 55.19072413444519s
Amount of data | Number of property check for Summary types of Czech institutions of public power took 0.11520147323608398s
Understandability | Number of label check for Summary types of Czech institutions of public power took 1.3642277717590332s
Understandability | URI regex check for Summary types of Czech institutions of public power took 0.40740084648132324s
Understandability | Vocabs check for Summary types of Czech institutions of public power took 0.11104345321655273s
Verifiability | Authors check for Summary types of Czech institutions of public power took 0.11839151382446289s
Verifiability | Publishers check for Summary types of Czech institutions of public power took 0.10821843147277832s
Performance | Throughput check for Summary types of Czech institutions of public power took 10.711681842803955s
Amount of data | Check the number of entities for Summary types of Czech institutions of public power took 3.4073469638824463s
Verifiability | Contribs. check for Summary types of Czech institutions of public power took 0.11862778663635254s
Interlinking | sameAs chians check for Summary types of Czech institutions of public power took 0.44496655464172363s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.1882002353668213s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.10750412940979004s
Timeliness | dataset update frequency check for Summary types of Czech institutions of public power took 0.2273712158203125s
Currency | Creation date check for Summary types of Czech institutions of public power took 0.23710966110229492s
Currency | Modification date check for Summary types of Czech institutions of public power took 0.10837912559509277s
Rep.Conc. | URIs length for Summary types of Czech institutions of public power took 110.66310214996338s
Interoperability | New vocabularies check for Summary types of Czech institutions of public power took 48.43170380592346s
Consistency | Deprecated classes/propertiers check for Summary types of Czech institutions of public power took 0.34760260581970215s
Accuracy | Check Functional Property for Summary types of Czech institutions of public power took 0.13788437843322754s
Accuracy | Check Inverse Functional Property for Summary types of Czech institutions of public power took 0.13344073295593262s
Accuracy | Check Empty annotation labels for Summary types of Czech institutions of public power took 31.408739805221558s
Accuracy | Check White space in annotation for Summary types of Czech institutions of public power took 3.0917463302612305s
Accuracy | Check Datatype consistency for Summary types of Czech institutions of public power took 2.8597676753997803s
Consistency | Disjoint class check for Summary types of Czech institutions of public power took 0.10630059242248535s
Consistency | Check Misplaced properties for Summary types of Czech institutions of public power took 68.5187520980835s
Consistency | Misplaced classes for Summary types of Czech institutions of public power took 7.97118878364563s
Consistency | Check Ontology hijacking for Summary types of Czech institutions of public power took 31.924190044403076s
Consistency | Check Invalid usage of undefined classes for Summary types of Czech institutions of public power took 1.4544250965118408s
Consistency | Check Invalid usage of undefined properties for Summary types of Czech institutions of public power took 61.83489775657654s
Conciseness | Check Extensional conciseness for Summary types of Czech institutions of public power took 2.7601077556610107s
Conciseness | Check Intensional conciseness for Summary types of Czech institutions of public power took 0.34735107421875s
Security | Sign check for Summary types of Czech institutions of public power took 0.12889981269836426s
Availability | Check URIs Dereferenciability for Summary types of Czech institutions of public power took 366.0215873718262s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 0.7071354389190674s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.02129840850830078s
Interlinking | Calculation of Degree of Connection for Summary types of Czech institutions of public power took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Summary types of Czech institutions of public power took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 4.6253204345703125e-05s
Interoperability | Check the re-using of existing vocabs for Summary types of Czech institutions of public power took 28.967131853103638s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 5.7220458984375e-06s
INFO | --- Analysis for cz-souhrnne-typy-ovm took 1650.0773711204529s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 0.10105443000793457s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.0007603168487548828s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 0.26698970794677734s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.020978212356567383s
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.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 3.6716461181640625e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 9.5367431640625e-06s
INFO | --- Analysis for cz-vavai-evaluation-2013 took 2.8210954666137695s
Availability | SPARQL endpoint availability check for State funding providers took 0.10107660293579102s
Availability | VoID file availability check for State funding providers took 0.0005548000335693359s
Completeness | Calculation of interlinking completeness for State funding providers took 0.275407075881958s
Reputation | Calculation of the PageRank for State funding providers took 0.02071857452392578s
Interlinking | Calculation of Degree of Connection for State funding providers took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for State funding providers took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for State funding providers took 4.7206878662109375e-05s
Believability | Calculation of trust value for State funding providers took 1.0728836059570312e-05s
INFO | --- Analysis for cz-vavai-funding-providers took 2.8731529712677s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 0.10158753395080566s
Availability | VoID file availability check for Organizations active in R&D took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 0.2745788097381592s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.020591020584106445s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 4.363059997558594e-05s
Believability | Calculation of trust value for Organizations active in R&D took 1.0013580322265625e-05s
INFO | --- Analysis for cz-vavai-organizations took 2.9704434871673584s
Availability | SPARQL endpoint availability check for R&D Programmes took 0.1015472412109375s
Availability | VoID file availability check for R&D Programmes took 0.0007631778717041016s
Completeness | Calculation of interlinking completeness for R&D Programmes took 0.2691957950592041s
Reputation | Calculation of the PageRank for R&D Programmes took 0.020688295364379883s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for R&D Programmes took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 4.2438507080078125e-05s
Believability | Calculation of trust value for R&D Programmes took 9.5367431640625e-06s
INFO | --- Analysis for cz-vavai-programmes took 3.0709104537963867s
Availability | SPARQL endpoint availability check for R&D Projects took 0.10065627098083496s
Availability | VoID file availability check for R&D Projects took 0.0006277561187744141s
Completeness | Calculation of interlinking completeness for R&D Projects took 0.27401304244995117s
Reputation | Calculation of the PageRank for R&D Projects took 0.02100086212158203s
Interlinking | Calculation of Degree of Connection for R&D Projects took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for R&D Projects took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 4.291534423828125e-05s
Believability | Calculation of trust value for R&D Projects took 8.821487426757812e-06s
INFO | --- Analysis for cz-vavai-projects took 2.8380143642425537s
Availability | SPARQL endpoint availability check for Institutional research plans took 0.0995340347290039s
Availability | VoID file availability check for Institutional research plans took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for Institutional research plans took 0.2776806354522705s
Reputation | Calculation of the PageRank for Institutional research plans took 0.02185678482055664s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Institutional research plans took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 4.1961669921875e-05s
Believability | Calculation of trust value for Institutional research plans took 1.049041748046875e-05s
INFO | --- Analysis for cz-vavai-research-plans took 2.809033155441284s
Availability | SPARQL endpoint availability check for Results of R&D took 0.10085654258728027s
Availability | VoID file availability check for Results of R&D took 0.0007841587066650391s
Completeness | Calculation of interlinking completeness for Results of R&D took 0.27532362937927246s
Reputation | Calculation of the PageRank for Results of R&D took 0.020893335342407227s
Interlinking | Calculation of Degree of Connection for Results of R&D took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Results of R&D took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 5.173683166503906e-05s
Believability | Calculation of trust value for Results of R&D took 8.58306884765625e-06s
INFO | --- Analysis for cz-vavai-results took 2.8537051677703857s
Availability | SPARQL endpoint availability check for Tenders in R&D took 0.10118651390075684s
Availability | VoID file availability check for Tenders in R&D took 0.0005483627319335938s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.2647514343261719s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.020839214324951172s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Tenders in R&D took 4.482269287109375e-05s
Believability | Calculation of trust value for Tenders in R&D took 1.0251998901367188e-05s
INFO | --- Analysis for cz-vavai-tenders took 2.811124086380005s
Availability | SPARQL endpoint availability check for Czech addresses – Adresy v České republice took 9.107589721679688e-05s
Availability | VoID file availability check for Czech addresses – Adresy v České republice took 0.0006101131439208984s
Completeness | Calculation of interlinking completeness for Czech addresses – Adresy v České republice took 0.2729520797729492s
Reputation | Calculation of the PageRank for Czech addresses – Adresy v České republice took 0.020785093307495117s
Interlinking | Calculation of Degree of Connection for Czech addresses – Adresy v České republice took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Czech addresses – Adresy v České republice took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for Czech addresses – Adresy v České republice took 4.1484832763671875e-05s
Believability | Calculation of trust value for Czech addresses – Adresy v České republice took 1.5020370483398438e-05s
INFO | --- Analysis for czech_addresses took 3.7204794883728027s
Availability | SPARQL endpoint availability check for Dante Latin Loanwords in LiLa took 0.5118834972381592s
Availability | VoID file availability check for Dante Latin Loanwords in LiLa took 0.0007796287536621094s
Completeness | Calculation of interlinking completeness for Dante Latin Loanwords in LiLa took 0.2662632465362549s
Reputation | Calculation of the PageRank for Dante Latin Loanwords in LiLa took 0.020693540573120117s
Interlinking | Calculation of Degree of Connection for Dante Latin Loanwords in LiLa took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Dante Latin Loanwords in LiLa took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Dante Latin Loanwords in LiLa took 4.00543212890625e-05s
Believability | Calculation of trust value for Dante Latin Loanwords in LiLa took 1.4543533325195312e-05s
INFO | --- Analysis for DanteLatinLoanwords took 4.110535383224487s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.350616455078125s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.00066375732421875s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 126.19094896316528s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 1.2055842876434326s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 11.150020599365234s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 4.091175317764282s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 120.34331583976746s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 0.33647608757019043s
Security | Check HTTPS for data.bnf.fr - Bibliothèque nationale de France took 0.11273837089538574s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 0.46086955070495605s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 0.28050994873046875s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.21071124076843262s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 0.22216463088989258s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 120.28569388389587s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.21689581871032715s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 1.5574345588684082s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 0.4139704704284668s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.20938730239868164s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 0.3108687400817871s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 0.20931482315063477s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 10.518769025802612s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 0.00011515617370605469s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 0.20322680473327637s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 0.5053918361663818s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.8327255249023438s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.2129518985748291s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.20443248748779297s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 1.4617416858673096s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 1.3351263999938965s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 82.76011061668396s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 1.2159347534179688e-05s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.20492100715637207s
Accuracy | Check Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.28775596618652344s
Accuracy | Check Inverse Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.2532033920288086s
Accuracy | Check Empty annotation labels for data.bnf.fr - Bibliothèque nationale de France took 41.81500506401062s
Accuracy | Check White space in annotation for data.bnf.fr - Bibliothèque nationale de France took 3.2614550590515137s
Accuracy | Check Datatype consistency for data.bnf.fr - Bibliothèque nationale de France took 2.7612416744232178s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 0.24359130859375s
Consistency | Check Misplaced properties for data.bnf.fr - Bibliothèque nationale de France took 21.94512963294983s
Consistency | Misplaced classes for data.bnf.fr - Bibliothèque nationale de France took 8.80530071258545s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 41.00498604774475s
Consistency | Check Invalid usage of undefined classes for data.bnf.fr - Bibliothèque nationale de France took 1.546147108078003s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 21.41268825531006s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 2.897183895111084s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.22263121604919434s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 0.22055935859680176s
Availability | Check URIs Dereferenciability for data.bnf.fr - Bibliothèque nationale de France took 9.406694173812866s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 0.40398716926574707s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.021512746810913086s
Interlinking | Calculation of Degree of Connection for data.bnf.fr - Bibliothèque nationale de France took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for data.bnf.fr - Bibliothèque nationale de France took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.00014925003051757812s
Interoperability | Check the re-using of existing vocabs for data.bnf.fr - Bibliothèque nationale de France took 2.384185791015625e-06s
Believability | Calculation of trust value for data.bnf.fr - Bibliothèque nationale de France took 1.4781951904296875e-05s
INFO | --- Analysis for data-bnf-fr took 816.3648538589478s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 0.3584470748901367s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.0003552436828613281s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 0.26953577995300293s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.021328449249267578s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.0007953643798828125s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 8.726119995117188e-05s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 1.0728836059570312e-05s
INFO | --- Analysis for data-cnr-it took 3.7414188385009766s
Availability | SPARQL endpoint availability check for Data.gov took 1.6339149475097656s
Availability | VoID file availability check for Data.gov took 0.0006570816040039062s
Completeness | Calculation of interlinking completeness for Data.gov took 0.27483534812927246s
Reputation | Calculation of the PageRank for Data.gov took 0.0210723876953125s
Interlinking | Calculation of Degree of Connection for Data.gov took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Data.gov took 0.0007925033569335938s
Interlinking | Calculation of Clustering coefficient for Data.gov took 3.600120544433594e-05s
Believability | Calculation of trust value for Data.gov took 1.0251998901367188e-05s
INFO | --- Analysis for data-gov took 17.140780687332153s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 0.07122468948364258s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.0005240440368652344s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 0.27654409408569336s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.020685672760009766s
Interlinking | Calculation of Degree of Connection for DataGovIE - Irish Government Data took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for DataGovIE - Irish Government Data took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 7.43865966796875e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 1.0967254638671875e-05s
INFO | --- Analysis for data-gov-ie took 2.7021493911743164s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 8.940696716308594e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 0.2765040397644043s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.020549297332763672s
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.0008640289306640625s
Interlinking | Calculation of Clustering coefficient for data.gov.uk Time Intervals took 8.034706115722656e-05s
Believability | Calculation of trust value for data.gov.uk Time Intervals took 9.059906005859375e-06s
INFO | --- Analysis for data-gov-uk-time-intervals took 2.5088541507720947s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 16.606420755386353s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.00042128562927246094s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 0.2794466018676758s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.02089095115661621s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 2.288818359375e-05s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 6.699562072753906e-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 157.66106510162354s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.10899472236633301s
Availability | VoID file availability check for Climb Dataincubator took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.2705225944519043s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.020662307739257812s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 7.677078247070312e-05s
Believability | Calculation of trust value for Climb Dataincubator took 1.5020370483398438e-05s
INFO | --- Analysis for data-incubator-climb took 2.6281795501708984s
Availability | SPARQL endpoint availability check for Discogs in RDF took 9.5367431640625e-05s
Availability | VoID file availability check for Discogs in RDF took 0.0006124973297119141s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.2820091247558594s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.020997285842895508s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0008885860443115234s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 0.00011610984802246094s
Believability | Calculation of trust value for Discogs in RDF took 9.5367431640625e-06s
INFO | --- Analysis for data-incubator-discogs took 7.736171722412109s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 0.05363202095031738s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.0007607936859130859s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 0.2757105827331543s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.020706653594970703s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.0008156299591064453s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 6.222724914550781e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 1.0251998901367188e-05s
INFO | --- Analysis for data-incubator-metoffice took 7.786501407623291s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.059432029724121094s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.0007345676422119141s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 0.27275943756103516s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.02077174186706543s
Interlinking | Calculation of Degree of Connection for Moseley Folk Festival Data took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Moseley Folk Festival Data took 0.0009036064147949219s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 0.00010061264038085938s
Believability | Calculation of trust value for Moseley Folk Festival Data took 1.4066696166992188e-05s
INFO | --- Analysis for data-incubator-moseley took 20.346972703933716s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.051323890686035156s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 0.2823777198791504s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.021647930145263672s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.0010919570922851562s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 0.00010991096496582031s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 1.430511474609375e-05s
INFO | --- Analysis for data-incubator-musicbrainz took 2.5678815841674805s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 2.60050368309021s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.000980377197265625s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 0.2650418281555176s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.020549774169921875s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for NASA Space Flight & Astronaut data in RDF took 8.7738037109375e-05s
Believability | Calculation of trust value for NASA Space Flight & Astronaut data in RDF took 6.4373016357421875e-06s
INFO | --- Analysis for data-incubator-nasa took 8.558833599090576s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 0.05221295356750488s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 0.2638380527496338s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.02078723907470703s
Interlinking | Calculation of Degree of Connection for Airport data from Our Airports published as RDF took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Airport data from Our Airports published as RDF took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 7.653236389160156e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 1.4543533325195312e-05s
INFO | --- Analysis for data-incubator-our-airports took 2.555217981338501s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 0.058091163635253906s
Availability | VoID file availability check for Pokedex data in RDF took 0.0006129741668701172s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 0.2702040672302246s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.022705793380737305s
Interlinking | Calculation of Degree of Connection for Pokedex data in RDF took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Pokedex data in RDF took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 9.560585021972656e-05s
Believability | Calculation of trust value for Pokedex data in RDF took 1.430511474609375e-05s
INFO | --- Analysis for data-incubator-pokedex took 3.5423693656921387s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.05244183540344238s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 0.2731049060821533s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.02057957649230957s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 9.1552734375e-05s
Believability | Calculation of trust value for Scottish Mountaineering Council Journals Issues 1-36 took 1.621246337890625e-05s
INFO | --- Analysis for data-incubator-smcjournals took 2.688356876373291s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 0.28338146209716797s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.0005176067352294922s
Extra | Recovery of all triples for data.open.ac.uk, Linked Data from the Open University took 29.70016121864319s
Performance | Total latancy measurement for data.open.ac.uk, Linked Data from the Open University took 0.66497802734375s
Amount of data | Number of triples check for data.open.ac.uk, Linked Data from the Open University took 19.86813735961914s
Interoperability | New terms check for data.open.ac.uk, Linked Data from the Open University took 1.5100667476654053s
Versatility | Languages check for data.open.ac.uk, Linked Data from the Open University took 30.137999057769775s
Interpretability | Number of blank nodes check for data.open.ac.uk, Linked Data from the Open University took 30.12690782546997s
Security | Check HTTPS for data.open.ac.uk, Linked Data from the Open University took 0.2846214771270752s
Interpretability | RDF structures check for data.open.ac.uk, Linked Data from the Open University took 0.1866142749786377s
Versatility | Serialization formats check for data.open.ac.uk, Linked Data from the Open University took 0.37217283248901367s
Availability | RDF dump link check for data.open.ac.uk, Linked Data from the Open University took 0.13973641395568848s
License | MR license check for data.open.ac.uk, Linked Data from the Open University took 0.2663850784301758s
License | HR license check for data.open.ac.uk, Linked Data from the Open University took 30.152257919311523s
Amount of data | Number of property check for data.open.ac.uk, Linked Data from the Open University took 0.9823095798492432s
Understandability | Number of label check for data.open.ac.uk, Linked Data from the Open University took 26.688706159591675s
Understandability | URI regex check for data.open.ac.uk, Linked Data from the Open University took 0.9095032215118408s
Understandability | Vocabs check for data.open.ac.uk, Linked Data from the Open University took 0.4849252700805664s
Verifiability | Authors check for data.open.ac.uk, Linked Data from the Open University took 0.7819955348968506s
Verifiability | Publishers check for data.open.ac.uk, Linked Data from the Open University took 0.6833515167236328s
Performance | Throughput check for data.open.ac.uk, Linked Data from the Open University took 11.60647439956665s
Amount of data | Check the number of entities for data.open.ac.uk, Linked Data from the Open University took 7.152557373046875e-05s
Verifiability | Contribs. check for data.open.ac.uk, Linked Data from the Open University took 0.18853187561035156s
Interlinking | sameAs chians check for data.open.ac.uk, Linked Data from the Open University took 0.503044843673706s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.2938673496246338s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.31538963317871094s
Timeliness | dataset update frequency check for data.open.ac.uk, Linked Data from the Open University took 0.5530259609222412s
Currency | Creation date check for data.open.ac.uk, Linked Data from the Open University took 0.482177734375s
Currency | Modification date check for data.open.ac.uk, Linked Data from the Open University took 0.47902512550354004s
Rep.Conc. | URIs length for data.open.ac.uk, Linked Data from the Open University took 38.17927002906799s
Interoperability | New vocabularies check for data.open.ac.uk, Linked Data from the Open University took 297.66728711128235s
Consistency | Deprecated classes/propertiers check for data.open.ac.uk, Linked Data from the Open University took 0.15577054023742676s
Accuracy | Check Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.13640236854553223s
Accuracy | Check Inverse Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.12293338775634766s
Accuracy | Check Empty annotation labels for data.open.ac.uk, Linked Data from the Open University took 12.600369930267334s
Accuracy | Check White space in annotation for data.open.ac.uk, Linked Data from the Open University took 2.9828360080718994s
Accuracy | Check Datatype consistency for data.open.ac.uk, Linked Data from the Open University took 5.242162466049194s
Consistency | Disjoint class check for data.open.ac.uk, Linked Data from the Open University took 0.16461706161499023s
Consistency | Check Misplaced properties for data.open.ac.uk, Linked Data from the Open University took 0.44712185859680176s
Consistency | Misplaced classes for data.open.ac.uk, Linked Data from the Open University took 8.180419683456421s
Consistency | Check Ontology hijacking for data.open.ac.uk, Linked Data from the Open University took 8.433710098266602s
Consistency | Check Invalid usage of undefined classes for data.open.ac.uk, Linked Data from the Open University took 1.5549182891845703s
Consistency | Check Invalid usage of undefined properties for data.open.ac.uk, Linked Data from the Open University took 1.7570831775665283s
Conciseness | Check Extensional conciseness for data.open.ac.uk, Linked Data from the Open University took 2.922499656677246s
Conciseness | Check Intensional conciseness for data.open.ac.uk, Linked Data from the Open University took 0.3287498950958252s
Security | Sign check for data.open.ac.uk, Linked Data from the Open University took 0.12660813331604004s
Availability | Check URIs Dereferenciability for data.open.ac.uk, Linked Data from the Open University took 0.12914109230041504s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 0.36139535903930664s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.02135491371154785s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 7.128715515136719e-05s
Interoperability | Check the re-using of existing vocabs for data.open.ac.uk, Linked Data from the Open University took 268.2865128517151s
Believability | Calculation of trust value for data.open.ac.uk, Linked Data from the Open University took 1.5020370483398438e-05s
INFO | --- Analysis for data-open-ac-uk took 1050.3215885162354s
Availability | SPARQL endpoint availability check for Persée in RDF took 0.7151584625244141s
Availability | VoID file availability check for Persée in RDF took 0.0007052421569824219s
Extra | Recovery of all triples for Persée in RDF took 1.2655770778656006s
Performance | Total latancy measurement for Persée in RDF took 0.5821454524993896s
Amount of data | Number of triples check for Persée in RDF took 0.9289376735687256s
Interoperability | New terms check for Persée in RDF took 2.0644352436065674s
Versatility | Languages check for Persée in RDF took 121.67407250404358s
Interpretability | Number of blank nodes check for Persée in RDF took 0.4329109191894531s
Interpretability | RDF structures check for Persée in RDF took 0.8190534114837646s
Versatility | Serialization formats check for Persée in RDF took 0.9512865543365479s
Availability | RDF dump link check for Persée in RDF took 0.2848174571990967s
License | MR license check for Persée in RDF took 1.3541393280029297s
License | HR license check for Persée in RDF took 40.46441984176636s
Amount of data | Number of property check for Persée in RDF took 0.12465739250183105s
Understandability | Number of label check for Persée in RDF took 1.9177887439727783s
Understandability | URI regex check for Persée in RDF took 0.9015512466430664s
Understandability | Vocabs check for Persée in RDF took 0.42769551277160645s
Verifiability | Authors check for Persée in RDF took 0.12658357620239258s
Verifiability | Publishers check for Persée in RDF took 0.11822080612182617s
Performance | Throughput check for Persée in RDF took 10.53479790687561s
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.11764740943908691s
Interlinking | sameAs chians check for Persée in RDF took 0.1763014793395996s
Interlinking | skos check for Persée in RDF took 0.7322840690612793s
Interlinking | skos check for Persée in RDF took 0.11822700500488281s
Timeliness | dataset update frequency check for Persée in RDF took 0.7130980491638184s
Currency | Creation date check for Persée in RDF took 0.5297236442565918s
Currency | Modification date check for Persée in RDF took 0.24765801429748535s
Rep.Conc. | URIs length for Persée in RDF took 3.5008394718170166s
Interoperability | New vocabularies check for Persée in RDF took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for Persée in RDF took 0.1152350902557373s
Accuracy | Check Functional Property for Persée in RDF took 0.13028454780578613s
Accuracy | Check Inverse Functional Property for Persée in RDF took 0.1311492919921875s
Accuracy | Check Empty annotation labels for Persée in RDF took 0.5010116100311279s
Accuracy | Check White space in annotation for Persée in RDF took 0.03938031196594238s
Accuracy | Check Datatype consistency for Persée in RDF took 0.03230714797973633s
Consistency | Disjoint class check for Persée in RDF took 0.32299160957336426s
Consistency | Check Misplaced properties for Persée in RDF took 2.601703405380249s
Consistency | Misplaced classes for Persée in RDF took 0.21753525733947754s
Consistency | Check Ontology hijacking for Persée in RDF took 1.8935270309448242s
Consistency | Check Invalid usage of undefined classes for Persée in RDF took 1.461902379989624s
Consistency | Check Invalid usage of undefined properties for Persée in RDF took 3.962522506713867s
Conciseness | Check Extensional conciseness for Persée in RDF took 0.034945011138916016s
Conciseness | Check Intensional conciseness for Persée in RDF took 0.15880250930786133s
Security | Sign check for Persée in RDF took 0.8893232345581055s
Availability | Check URIs Dereferenciability for Persée in RDF took 1238.2542576789856s
Completeness | Calculation of interlinking completeness for Persée in RDF took 0.5619747638702393s
Reputation | Calculation of the PageRank for Persée in RDF took 0.021956682205200195s
Interlinking | Calculation of Degree of Connection for Persée in RDF took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for Persée in RDF took 0.0007977485656738281s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 0.00013303756713867188s
Interoperability | Check the re-using of existing vocabs for Persée in RDF took 1.430511474609375e-06s
Believability | Calculation of trust value for Persée in RDF took 1.52587890625e-05s
INFO | --- Analysis for data-persee-fr took 1479.9643499851227s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 1.4011845588684082s
Availability | VoID file availability check for data-szepmuveszeti-hu took 0.0005922317504882812s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 0.26455068588256836s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.02065730094909668s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.00012755393981933594s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 1.430511474609375e-05s
INFO | --- Analysis for data-szepmuveszeti-hu took 8.535822868347168s
Availability | SPARQL endpoint availability check for Open Data Web took 28.86053442955017s
Availability | VoID file availability check for Open Data Web took 0.0003025531768798828s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.2665519714355469s
Reputation | Calculation of the PageRank for Open Data Web took 0.021615028381347656s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.4332275390625e-05s
Believability | Calculation of trust value for Open Data Web took 1.5497207641601562e-05s
INFO | --- Analysis for data.odw.tw took 75.6748685836792s
Availability | SPARQL endpoint availability check for datahub took 4.363059997558594e-05s
Availability | VoID file availability check for datahub took 0.000682830810546875s
Completeness | Calculation of interlinking completeness for datahub took 0.2760324478149414s
Reputation | Calculation of the PageRank for datahub took 0.02083897590637207s
Interlinking | Calculation of Degree of Connection for datahub took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for datahub took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for datahub took 4.982948303222656e-05s
Believability | Calculation of trust value for datahub took 1.5020370483398438e-05s
INFO | --- Analysis for datahub took 4.0850231647491455s
Availability | SPARQL endpoint availability check for Open Datasets in South Korea took 4.6002256870269775s
Availability | VoID file availability check for Open Datasets in South Korea took 0.0007884502410888672s
Completeness | Calculation of interlinking completeness for Open Datasets in South Korea took 0.27289605140686035s
Reputation | Calculation of the PageRank for Open Datasets in South Korea took 0.02055191993713379s
Interlinking | Calculation of Degree of Connection for Open Datasets in South Korea took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Open Datasets in South Korea took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Open Datasets in South Korea took 3.218650817871094e-05s
Believability | Calculation of trust value for Open Datasets in South Korea took 1.4066696166992188e-05s
INFO | --- Analysis for datahub-kr-datamap took 13.162652969360352s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.3208928108215332s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0006887912750244141s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.27382421493530273s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.021777629852294922s
Interlinking | Calculation of Degree of Connection for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 7.462501525878906e-05s
Believability | Calculation of trust value for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.4781951904296875e-05s
INFO | --- Analysis for dataturcyl-lod-for-tourists-in-castilla-y-leon-spain took 4.937153339385986s
Availability | SPARQL endpoint availability check for datos-artium-org took 21.227019786834717s
Availability | VoID file availability check for datos-artium-org took 0.0008263587951660156s
Completeness | Calculation of interlinking completeness for datos-artium-org took 0.37744593620300293s
Reputation | Calculation of the PageRank for datos-artium-org took 0.021190166473388672s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 2.6941299438476562e-05s
Interlinking | Calculation of Centrality for datos-artium-org took 0.0008158683776855469s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.00012826919555664062s
Believability | Calculation of trust value for datos-artium-org took 1.0251998901367188e-05s
INFO | --- Analysis for datos-artium-org took 165.02014446258545s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 1.9612207412719727s
Availability | VoID file availability check for Datos.bcn.cl took 0.0007886886596679688s
Extra | Recovery of all triples for Datos.bcn.cl took 24.62023138999939s
Performance | Total latancy measurement for Datos.bcn.cl took 5.905177593231201s
Amount of data | Number of triples check for Datos.bcn.cl took 4.907395362854004s
Interoperability | New terms check for Datos.bcn.cl took 3.7893965244293213s
Versatility | Languages check for Datos.bcn.cl took 287.15853691101074s
Interpretability | Number of blank nodes check for Datos.bcn.cl took 1.2446012496948242s
Security | Check HTTPS for Datos.bcn.cl took 0.7221236228942871s
Interpretability | RDF structures check for Datos.bcn.cl took 1.2762014865875244s
Versatility | Serialization formats check for Datos.bcn.cl took 1.2184033393859863s
Availability | RDF dump link check for Datos.bcn.cl took 1.2039694786071777s
License | MR license check for Datos.bcn.cl took 1.2044177055358887s
License | HR license check for Datos.bcn.cl took 32.715577363967896s
Amount of data | Number of property check for Datos.bcn.cl took 1.1926283836364746s
Understandability | Number of label check for Datos.bcn.cl took 1.406071662902832s
Understandability | URI regex check for Datos.bcn.cl took 2.3820481300354004s
Understandability | Vocabs check for Datos.bcn.cl took 1.2086520195007324s
Verifiability | Authors check for Datos.bcn.cl took 1.2073140144348145s
Verifiability | Publishers check for Datos.bcn.cl took 1.1947076320648193s
Performance | Throughput check for Datos.bcn.cl took 11.927809476852417s
Amount of data | Check the number of entities for Datos.bcn.cl took 7.581710815429688e-05s
Verifiability | Contribs. check for Datos.bcn.cl took 1.2000749111175537s
Interlinking | sameAs chians check for Datos.bcn.cl took 1.1794610023498535s
Interlinking | skos check for Datos.bcn.cl took 1.2044486999511719s
Interlinking | skos check for Datos.bcn.cl took 1.1861977577209473s
Timeliness | dataset update frequency check for Datos.bcn.cl took 1.186049461364746s
Currency | Creation date check for Datos.bcn.cl took 2.3883392810821533s
Currency | Modification date check for Datos.bcn.cl took 1.2031378746032715s
Rep.Conc. | URIs length for Datos.bcn.cl took 30.132474184036255s
Interoperability | New vocabularies check for Datos.bcn.cl took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Datos.bcn.cl took 1.2014386653900146s
Accuracy | Check Functional Property for Datos.bcn.cl took 1.1863796710968018s
Accuracy | Check Inverse Functional Property for Datos.bcn.cl took 1.2024993896484375s
Accuracy | Check Empty annotation labels for Datos.bcn.cl took 18.48887610435486s
Accuracy | Check White space in annotation for Datos.bcn.cl took 0.32473015785217285s
Accuracy | Check Datatype consistency for Datos.bcn.cl took 0.27106523513793945s
Consistency | Disjoint class check for Datos.bcn.cl took 1.178896427154541s
Consistency | Check Misplaced properties for Datos.bcn.cl took 7.96381139755249s
Consistency | Misplaced classes for Datos.bcn.cl took 2.0509190559387207s
Consistency | Check Ontology hijacking for Datos.bcn.cl took 15.911151647567749s
Consistency | Check Invalid usage of undefined classes for Datos.bcn.cl took 1.281402826309204s
Consistency | Check Invalid usage of undefined properties for Datos.bcn.cl took 7.616767406463623s
Conciseness | Check Extensional conciseness for Datos.bcn.cl took 0.3040809631347656s
Conciseness | Check Intensional conciseness for Datos.bcn.cl took 1.4437274932861328s
Security | Sign check for Datos.bcn.cl took 1.2008373737335205s
Availability | Check URIs Dereferenciability for Datos.bcn.cl took 7332.712761163712s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 0.7196323871612549s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.021135330200195312s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 9.822845458984375e-05s
Interoperability | Check the re-using of existing vocabs for Datos.bcn.cl took 1.6689300537109375e-06s
Believability | Calculation of trust value for Datos.bcn.cl took 6.67572021484375e-06s
INFO | --- Analysis for datos-bcn-cl took 8129.82493686676s
Availability | SPARQL endpoint availability check for datos.bne.es took 0.717949390411377s
Availability | VoID file availability check for datos.bne.es took 0.0007398128509521484s
Extra | Recovery of all triples for datos.bne.es took 129.6499798297882s
Performance | Total latancy measurement for datos.bne.es took 6.512527227401733s
Amount of data | Number of triples check for datos.bne.es took 0.9185736179351807s
Interoperability | New terms check for datos.bne.es took 4.110952854156494s
Versatility | Languages check for datos.bne.es took 62.16279315948486s
Interpretability | Number of blank nodes check for datos.bne.es took 0.27632665634155273s
Security | Check HTTPS for datos.bne.es took 1.8795444965362549s
Interpretability | RDF structures check for datos.bne.es took 0.5706331729888916s
Versatility | Serialization formats check for datos.bne.es took 0.5990149974822998s
Availability | RDF dump link check for datos.bne.es took 2.0900211334228516s
License | MR license check for datos.bne.es took 2.342703342437744s
License | HR license check for datos.bne.es took 63.20743989944458s
Amount of data | Number of property check for datos.bne.es took 0.28507137298583984s
Understandability | Number of label check for datos.bne.es took 1.1805627346038818s
Understandability | URI regex check for datos.bne.es took 0.8008203506469727s
Understandability | Vocabs check for datos.bne.es took 2.097104072570801s
Verifiability | Authors check for datos.bne.es took 0.38793230056762695s
Verifiability | Publishers check for datos.bne.es took 0.3602776527404785s
Performance | Throughput check for datos.bne.es took 20.28831958770752s
Amount of data | Check the number of entities for datos.bne.es took 7.462501525878906e-05s
Verifiability | Contribs. check for datos.bne.es took 0.3555305004119873s
Interlinking | sameAs chians check for datos.bne.es took 0.47877073287963867s
Interlinking | skos check for datos.bne.es took 2.373671293258667s
Interlinking | skos check for datos.bne.es took 2.035881996154785s
Timeliness | dataset update frequency check for datos.bne.es took 4.151907205581665s
Currency | Creation date check for datos.bne.es took 2.3690311908721924s
Currency | Modification date check for datos.bne.es took 4.041626930236816s
Rep.Conc. | URIs length for datos.bne.es took 53.343876123428345s
Interoperability | New vocabularies check for datos.bne.es took 1.1444091796875e-05s
Consistency | Deprecated classes/propertiers check for datos.bne.es took 0.27687597274780273s
Accuracy | Check Functional Property for datos.bne.es took 0.27961111068725586s
Accuracy | Check Inverse Functional Property for datos.bne.es took 2.0202817916870117s
Accuracy | Check Empty annotation labels for datos.bne.es took 39.13988161087036s
Accuracy | Check White space in annotation for datos.bne.es took 1.6320216655731201s
Accuracy | Check Datatype consistency for datos.bne.es took 1.3280198574066162s
Consistency | Disjoint class check for datos.bne.es took 2.093411684036255s
Consistency | Check Misplaced properties for datos.bne.es took 10.584497213363647s
Consistency | Misplaced classes for datos.bne.es took 4.428435564041138s
Consistency | Check Ontology hijacking for datos.bne.es took 39.15887928009033s
Consistency | Check Invalid usage of undefined classes for datos.bne.es took 1.3624186515808105s
Consistency | Check Invalid usage of undefined properties for datos.bne.es took 10.157703638076782s
Conciseness | Check Extensional conciseness for datos.bne.es took 1.3924167156219482s
Conciseness | Check Intensional conciseness for datos.bne.es took 0.2779428958892822s
Security | Sign check for datos.bne.es took 2.9956047534942627s
Availability | Check URIs Dereferenciability for datos.bne.es took 9.918585538864136s
Completeness | Calculation of interlinking completeness for datos.bne.es took 0.4772756099700928s
Reputation | Calculation of the PageRank for datos.bne.es took 0.0224454402923584s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for datos.bne.es took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.00012564659118652344s
Interoperability | Check the re-using of existing vocabs for datos.bne.es took 9.5367431640625e-06s
Believability | Calculation of trust value for datos.bne.es took 1.430511474609375e-05s
INFO | --- Analysis for datos-bne-es took 621.0695903301239s
Availability | SPARQL endpoint availability check for dbacademic took 0.057840585708618164s
Availability | VoID file availability check for dbacademic took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for dbacademic took 0.2680692672729492s
Reputation | Calculation of the PageRank for dbacademic took 0.02345418930053711s
Interlinking | Calculation of Degree of Connection for dbacademic took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for dbacademic took 0.0010139942169189453s
Interlinking | Calculation of Clustering coefficient for dbacademic took 4.315376281738281e-05s
Believability | Calculation of trust value for dbacademic took 7.3909759521484375e-06s
INFO | --- Analysis for dbacademic took 2.5036919116973877s
Availability | SPARQL endpoint availability check for DBkWik took 0.18351101875305176s
Availability | VoID file availability check for DBkWik took 0.00044345855712890625s
Extra | Recovery of all triples for DBkWik took 1.370077133178711s
Performance | Total latancy measurement for DBkWik took 0.39690160751342773s
Amount of data | Number of triples check for DBkWik took 5.140604257583618s
Interoperability | New terms check for DBkWik took 2.034362316131592s
Versatility | Languages check for DBkWik took 61.08659887313843s
Interpretability | Number of blank nodes check for DBkWik took 0.10075545310974121s
Interpretability | RDF structures check for DBkWik took 0.2592580318450928s
Versatility | Serialization formats check for DBkWik took 0.2619020938873291s
Availability | RDF dump link check for DBkWik took 2.6341845989227295s
License | MR license check for DBkWik took 0.4631810188293457s
License | HR license check for DBkWik took 61.70638608932495s
Amount of data | Number of property check for DBkWik took 0.11938810348510742s
Understandability | Number of label check for DBkWik took 2.277040719985962s
Understandability | URI regex check for DBkWik took 0.2977330684661865s
Understandability | Vocabs check for DBkWik took 0.10659646987915039s
Verifiability | Authors check for DBkWik took 0.10522651672363281s
Verifiability | Publishers check for DBkWik took 0.0816197395324707s
Performance | Throughput check for DBkWik took 10.41430401802063s
Amount of data | Check the number of entities for DBkWik took 0.00012993812561035156s
Verifiability | Contribs. check for DBkWik took 0.10156106948852539s
Interlinking | sameAs chians check for DBkWik took 0.45982837677001953s
Interlinking | skos check for DBkWik took 0.5256154537200928s
Interlinking | skos check for DBkWik took 0.07747411727905273s
Timeliness | dataset update frequency check for DBkWik took 0.23238515853881836s
Currency | Creation date check for DBkWik took 0.47829151153564453s
Currency | Modification date check for DBkWik took 0.1824052333831787s
Rep.Conc. | URIs length for DBkWik took 11.112212896347046s
Interoperability | New vocabularies check for DBkWik took 14.555906057357788s
Consistency | Deprecated classes/propertiers check for DBkWik took 0.10512423515319824s
Accuracy | Check Functional Property for DBkWik took 0.3167080879211426s
Accuracy | Check Inverse Functional Property for DBkWik took 0.29536867141723633s
Accuracy | Check Empty annotation labels for DBkWik took 0.7829983234405518s
Accuracy | Check White space in annotation for DBkWik took 0.023141145706176758s
Accuracy | Check Datatype consistency for DBkWik took 0.03860282897949219s
Consistency | Disjoint class check for DBkWik took 0.12114405632019043s
Consistency | Check Misplaced properties for DBkWik took 11.699739933013916s
Consistency | Misplaced classes for DBkWik took 0.5544514656066895s
Consistency | Check Ontology hijacking for DBkWik took 1.6861536502838135s
Consistency | Check Invalid usage of undefined classes for DBkWik took 1.2103099822998047s
Consistency | Check Invalid usage of undefined properties for DBkWik took 11.781752586364746s
Conciseness | Check Extensional conciseness for DBkWik took 0.0332036018371582s
Conciseness | Check Intensional conciseness for DBkWik took 0.6210930347442627s
Security | Sign check for DBkWik took 0.2783229351043701s
Availability | Check URIs Dereferenciability for DBkWik took 10.183934688568115s
Completeness | Calculation of interlinking completeness for DBkWik took 0.3352780342102051s
Reputation | Calculation of the PageRank for DBkWik took 0.02670431137084961s
Interlinking | Calculation of Degree of Connection for DBkWik took 2.288818359375e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.0007913112640380859s
Interlinking | Calculation of Clustering coefficient for DBkWik took 8.273124694824219e-05s
Interoperability | Check the re-using of existing vocabs for DBkWik took 9.837791681289673s
Believability | Calculation of trust value for DBkWik took 1.4781951904296875e-05s
INFO | --- Analysis for dbkwik took 1150.287941455841s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 9.989738464355469e-05s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.0005278587341308594s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 0.2678344249725342s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.020776033401489258s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 0.0001049041748046875s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.0015711784362792969s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.00024700164794921875s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 1.4066696166992188e-05s
INFO | --- Analysis for dblp-deusto-gnoss took 4.0368146896362305s
Availability | SPARQL endpoint availability check for dblp Knowledge Graph took 0.30127573013305664s
Availability | VoID file availability check for dblp Knowledge Graph took 0.0006449222564697266s
Extra | Recovery of all triples for dblp Knowledge Graph took 7.351666450500488s
Performance | Total latancy measurement for dblp Knowledge Graph took 0.6521704196929932s
Amount of data | Number of triples check for dblp Knowledge Graph took 0.12213373184204102s
Interoperability | New terms check for dblp Knowledge Graph took 1.7875382900238037s
Versatility | Languages check for dblp Knowledge Graph took 0.19223332405090332s
Interpretability | Number of blank nodes check for dblp Knowledge Graph took 7.048933982849121s
Interpretability | RDF structures check for dblp Knowledge Graph took 0.13186407089233398s
Versatility | Serialization formats check for dblp Knowledge Graph took 0.13997316360473633s
Availability | RDF dump link check for dblp Knowledge Graph took 0.11844754219055176s
License | MR license check for dblp Knowledge Graph took 0.12853765487670898s
License | HR license check for dblp Knowledge Graph took 30.126116037368774s
Amount of data | Number of property check for dblp Knowledge Graph took 0.12010335922241211s
Understandability | Number of label check for dblp Knowledge Graph took 0.8737490177154541s
Understandability | URI regex check for dblp Knowledge Graph took 0.24820184707641602s
Understandability | Vocabs check for dblp Knowledge Graph took 0.1246941089630127s
Verifiability | Authors check for dblp Knowledge Graph took 0.13094091415405273s
Verifiability | Publishers check for dblp Knowledge Graph took 0.12434911727905273s
Performance | Throughput check for dblp Knowledge Graph took 11.021478176116943s
Amount of data | Check the number of entities for dblp Knowledge Graph took 0.0001995563507080078s
Verifiability | Contribs. check for dblp Knowledge Graph took 0.12372708320617676s
Interlinking | sameAs chians check for dblp Knowledge Graph took 0.19950580596923828s
Interlinking | skos check for dblp Knowledge Graph took 0.12042737007141113s
Interlinking | skos check for dblp Knowledge Graph took 0.1194455623626709s
Timeliness | dataset update frequency check for dblp Knowledge Graph took 0.12799882888793945s
Currency | Creation date check for dblp Knowledge Graph took 0.2473311424255371s
Currency | Modification date check for dblp Knowledge Graph took 0.24399399757385254s
Rep.Conc. | URIs length for dblp Knowledge Graph took 54.54810643196106s
Interoperability | New vocabularies check for dblp Knowledge Graph took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for dblp Knowledge Graph took 0.12370896339416504s
Accuracy | Check Functional Property for dblp Knowledge Graph took 0.11931204795837402s
Accuracy | Check Inverse Functional Property for dblp Knowledge Graph took 0.11945581436157227s
Accuracy | Check Empty annotation labels for dblp Knowledge Graph took 29.27369236946106s
Accuracy | Check White space in annotation for dblp Knowledge Graph took 3.1208555698394775s
Accuracy | Check Datatype consistency for dblp Knowledge Graph took 6.4028480052948s
Consistency | Disjoint class check for dblp Knowledge Graph took 0.12266421318054199s
Consistency | Check Misplaced properties for dblp Knowledge Graph took 0.2566394805908203s
Consistency | Check Ontology hijacking for dblp Knowledge Graph took 50.84996294975281s
Consistency | Check Invalid usage of undefined classes for dblp Knowledge Graph took 21681.77725481987s
Consistency | Check Invalid usage of undefined properties for dblp Knowledge Graph took 4.669124364852905s
Conciseness | Check Extensional conciseness for dblp Knowledge Graph took 2.7498250007629395s
Conciseness | Check Intensional conciseness for dblp Knowledge Graph took 0.158860445022583s
Security | Sign check for dblp Knowledge Graph took 0.12390494346618652s
Availability | Check URIs Dereferenciability for dblp Knowledge Graph took 2.587933301925659s
Completeness | Calculation of interlinking completeness for dblp Knowledge Graph took 0.9240260124206543s
Reputation | Calculation of the PageRank for dblp Knowledge Graph took 0.0214235782623291s
Interlinking | Calculation of Degree of Connection for dblp Knowledge Graph took 2.5510787963867188e-05s
Interlinking | Calculation of Centrality for dblp Knowledge Graph took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for dblp Knowledge Graph took 2.193450927734375e-05s
Interoperability | Check the re-using of existing vocabs for dblp Knowledge Graph took 2.384185791015625e-06s
Believability | Calculation of trust value for dblp Knowledge Graph took 1.049041748046875e-05s
INFO | --- Analysis for dblp-kg took 21952.342130422592s
Availability | SPARQL endpoint availability check for DBnary took 0.3963799476623535s
Availability | VoID file availability check for DBnary took 0.0006055831909179688s
Extra | Recovery of all triples for DBnary took 1.1360924243927002s
Performance | Total latancy measurement for DBnary took 0.34241628646850586s
Amount of data | Number of triples check for DBnary took 1.3048717975616455s
Interoperability | New terms check for DBnary took 3.6666676998138428s
Versatility | Languages check for DBnary took 61.75129842758179s
Interpretability | Number of blank nodes check for DBnary took 4.926408529281616s
Security | Check HTTPS for DBnary took 0.15078163146972656s
Interpretability | RDF structures check for DBnary took 0.23103785514831543s
Versatility | Serialization formats check for DBnary took 0.27158594131469727s
Availability | RDF dump link check for DBnary took 0.1504380702972412s
License | MR license check for DBnary took 0.36717772483825684s
License | HR license check for DBnary took 62.41827130317688s
Amount of data | Number of property check for DBnary took 0.09483146667480469s
Understandability | Number of label check for DBnary took 0.6584186553955078s
Understandability | URI regex check for DBnary took 0.18207621574401855s
Understandability | Vocabs check for DBnary took 0.11298489570617676s
Verifiability | Authors check for DBnary took 0.06726408004760742s
Verifiability | Publishers check for DBnary took 0.06403064727783203s
Performance | Throughput check for DBnary took 10.392642259597778s
Amount of data | Check the number of entities for DBnary took 0.00011181831359863281s
Verifiability | Contribs. check for DBnary took 0.06679677963256836s
Interlinking | sameAs chians check for DBnary took 0.09470915794372559s
Interlinking | skos check for DBnary took 0.16721892356872559s
Interlinking | skos check for DBnary took 0.06373214721679688s
Timeliness | dataset update frequency check for DBnary took 0.1394214630126953s
Currency | Creation date check for DBnary took 0.15525436401367188s
Currency | Modification date check for DBnary took 0.1562819480895996s
Rep.Conc. | URIs length for DBnary took 11.162753820419312s
Interoperability | New vocabularies check for DBnary took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for DBnary took 0.08625459671020508s
Accuracy | Check Functional Property for DBnary took 0.15009570121765137s
Accuracy | Check Inverse Functional Property for DBnary took 0.1341242790222168s
Accuracy | Check Empty annotation labels for DBnary took 0.46601414680480957s
Accuracy | Check White space in annotation for DBnary took 0.030988693237304688s
Accuracy | Check Datatype consistency for DBnary took 0.029912948608398438s
Consistency | Disjoint class check for DBnary took 0.12658357620239258s
Consistency | Check Misplaced properties for DBnary took 8.795328140258789s
Consistency | Misplaced classes for DBnary took 0.21731805801391602s
Consistency | Check Ontology hijacking for DBnary took 1.7975842952728271s
Consistency | Check Invalid usage of undefined classes for DBnary took 1.46980881690979s
Consistency | Check Invalid usage of undefined properties for DBnary took 10.067809343338013s
Conciseness | Check Extensional conciseness for DBnary took 0.03823518753051758s
Conciseness | Check Intensional conciseness for DBnary took 0.1614527702331543s
Security | Sign check for DBnary took 0.08456039428710938s
Availability | Check URIs Dereferenciability for DBnary took 10.416003942489624s
Completeness | Calculation of interlinking completeness for DBnary took 0.2801191806793213s
Reputation | Calculation of the PageRank for DBnary took 0.021104812622070312s
Interlinking | Calculation of Degree of Connection for DBnary took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for DBnary took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for DBnary took 5.817413330078125e-05s
Interoperability | Check the re-using of existing vocabs for DBnary took 1.9073486328125e-06s
Believability | Calculation of trust value for DBnary took 1.5974044799804688e-05s
INFO | --- Analysis for dbnary took 307.9989655017853s
Availability | SPARQL endpoint availability check for DBpedia took 0.8616690635681152s
Availability | VoID file availability check for DBpedia took 0.0006189346313476562s
Extra | Recovery of all triples for DBpedia took 2.6698083877563477s
Performance | Total latancy measurement for DBpedia took 2.646786689758301s
Amount of data | Number of triples check for DBpedia took 1.6851518154144287s
Interoperability | New terms check for DBpedia took 5.574908256530762s
Versatility | Languages check for DBpedia took 30.726223945617676s
Interpretability | Number of blank nodes check for DBpedia took 0.5545790195465088s
Security | Check HTTPS for DBpedia took 0.3247334957122803s
Interpretability | RDF structures check for DBpedia took 0.7521898746490479s
Versatility | Serialization formats check for DBpedia took 0.6216480731964111s
Availability | RDF dump link check for DBpedia took 0.53501296043396s
License | MR license check for DBpedia took 1.221656322479248s
License | HR license check for DBpedia took 31.93177580833435s
Amount of data | Number of property check for DBpedia took 0.5367693901062012s
Understandability | Number of label check for DBpedia took 4.5371294021606445s
Understandability | URI regex check for DBpedia took 1.0723869800567627s
Understandability | Vocabs check for DBpedia took 0.6474158763885498s
Verifiability | Authors check for DBpedia took 0.6858420372009277s
Verifiability | Publishers check for DBpedia took 0.5989346504211426s
Performance | Throughput check for DBpedia took 10.691890001296997s
Amount of data | Check the number of entities for DBpedia took 0.00010538101196289062s
Verifiability | Contribs. check for DBpedia took 0.5395641326904297s
Interlinking | sameAs chians check for DBpedia took 2.4583160877227783s
Interlinking | skos check for DBpedia took 0.9325108528137207s
Interlinking | skos check for DBpedia took 0.5331215858459473s
Timeliness | dataset update frequency check for DBpedia took 0.6108405590057373s
Currency | Creation date check for DBpedia took 1.1685905456542969s
Currency | Modification date check for DBpedia took 1.1022052764892578s
Rep.Conc. | URIs length for DBpedia took 33.18696331977844s
Interoperability | New vocabularies check for DBpedia took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for DBpedia took 0.5440351963043213s
Accuracy | Check Functional Property for DBpedia took 0.5325710773468018s
Accuracy | Check Inverse Functional Property for DBpedia took 0.5446107387542725s
Accuracy | Check Empty annotation labels for DBpedia took 1.6538491249084473s
Accuracy | Check White space in annotation for DBpedia took 0.029395341873168945s
Accuracy | Check Datatype consistency for DBpedia took 0.027866601943969727s
Consistency | Disjoint class check for DBpedia took 0.540308952331543s
Consistency | Check Misplaced properties for DBpedia took 29.56472659111023s
Consistency | Misplaced classes for DBpedia took 2.1191701889038086s
Consistency | Check Ontology hijacking for DBpedia took 2.816387891769409s
Consistency | Check Invalid usage of undefined classes for DBpedia took 1.2153780460357666s
Consistency | Check Invalid usage of undefined properties for DBpedia took 2.6713058948516846s
Conciseness | Check Extensional conciseness for DBpedia took 0.03284168243408203s
Conciseness | Check Intensional conciseness for DBpedia took 13.668980836868286s
Security | Sign check for DBpedia took 0.549018144607544s
Availability | Check URIs Dereferenciability for DBpedia took 8695.181218624115s
Completeness | Calculation of interlinking completeness for DBpedia took 0.6242380142211914s
Reputation | Calculation of the PageRank for DBpedia took 0.024999380111694336s
Interlinking | Calculation of Degree of Connection for DBpedia took 6.079673767089844e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0008339881896972656s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.0009365081787109375s
Interoperability | Check the re-using of existing vocabs for DBpedia took 1.430511474609375e-06s
Believability | Calculation of trust value for DBpedia took 1.0251998901367188e-05s
INFO | --- Analysis for dbpedia took 12221.987648963928s
Availability | SPARQL endpoint availability check for DBpedia abstract corpus took 9.632110595703125e-05s
Availability | VoID file availability check for DBpedia abstract corpus took 0.00042939186096191406s
Completeness | Calculation of interlinking completeness for DBpedia abstract corpus took 0.28186535835266113s
Reputation | Calculation of the PageRank for DBpedia abstract corpus took 0.020964622497558594s
Interlinking | Calculation of Degree of Connection for DBpedia abstract corpus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBpedia abstract corpus took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for DBpedia abstract corpus took 7.319450378417969e-05s
Believability | Calculation of trust value for DBpedia abstract corpus took 9.775161743164062e-06s
INFO | --- Analysis for dbpedia-abstract-corpus took 7.210673093795776s
Availability | SPARQL endpoint availability check for DBpedia Commons took 6.165572881698608s
Availability | VoID file availability check for DBpedia Commons took 0.0005466938018798828s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.26628780364990234s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.020540475845336914s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 7.200241088867188e-05s
Believability | Calculation of trust value for DBpedia Commons took 1.0967254638671875e-05s
INFO | --- Analysis for dbpedia-commons took 16.40764570236206s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 0.36652302742004395s
Availability | VoID file availability check for DBpedia in Greek took 0.0005619525909423828s
Extra | Recovery of all triples for DBpedia in Greek took 1.3320891857147217s
Performance | Total latancy measurement for DBpedia in Greek took 1.0803437232971191s
Amount of data | Number of triples check for DBpedia in Greek took 0.25821685791015625s
Interoperability | New terms check for DBpedia in Greek took 1.6076960563659668s
Versatility | Languages check for DBpedia in Greek took 13.344494819641113s
Interpretability | Number of blank nodes check for DBpedia in Greek took 0.21861958503723145s
Security | Check HTTPS for DBpedia in Greek took 0.13194632530212402s
Interpretability | RDF structures check for DBpedia in Greek took 0.26700758934020996s
Versatility | Serialization formats check for DBpedia in Greek took 0.2344810962677002s
Availability | RDF dump link check for DBpedia in Greek took 0.22415375709533691s
License | MR license check for DBpedia in Greek took 0.2528505325317383s
License | HR license check for DBpedia in Greek took 2.6409049034118652s
Amount of data | Number of property check for DBpedia in Greek took 0.22266578674316406s
Understandability | Number of label check for DBpedia in Greek took 0.2954518795013428s
Understandability | URI regex check for DBpedia in Greek took 0.4462320804595947s
Understandability | Vocabs check for DBpedia in Greek took 0.22226619720458984s
Verifiability | Authors check for DBpedia in Greek took 0.23110318183898926s
Verifiability | Publishers check for DBpedia in Greek took 0.21926212310791016s
Performance | Throughput check for DBpedia in Greek took 10.86068868637085s
Amount of data | Check the number of entities for DBpedia in Greek took 0.0001251697540283203s
Verifiability | Contribs. check for DBpedia in Greek took 0.25252532958984375s
Interlinking | sameAs chians check for DBpedia in Greek took 0.2521359920501709s
Interlinking | skos check for DBpedia in Greek took 0.3820769786834717s
Interlinking | skos check for DBpedia in Greek took 0.21658897399902344s
Timeliness | dataset update frequency check for DBpedia in Greek took 0.28578972816467285s
Currency | Creation date check for DBpedia in Greek took 0.4377095699310303s
Currency | Modification date check for DBpedia in Greek took 0.4356675148010254s
Rep.Conc. | URIs length for DBpedia in Greek took 1.7583792209625244s
Interoperability | New vocabularies check for DBpedia in Greek took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Greek took 0.21756339073181152s
Accuracy | Check Functional Property for DBpedia in Greek took 0.24161887168884277s
Accuracy | Check Inverse Functional Property for DBpedia in Greek took 0.2427356243133545s
Accuracy | Check Empty annotation labels for DBpedia in Greek took 0.6326782703399658s
Accuracy | Check White space in annotation for DBpedia in Greek took 0.031110048294067383s
Accuracy | Check Datatype consistency for DBpedia in Greek took 0.028624296188354492s
Consistency | Disjoint class check for DBpedia in Greek took 0.21370387077331543s
Consistency | Check Misplaced properties for DBpedia in Greek took 1.3062362670898438s
Consistency | Misplaced classes for DBpedia in Greek took 0.6636064052581787s
Consistency | Check Ontology hijacking for DBpedia in Greek took 1.798480749130249s
Consistency | Check Invalid usage of undefined classes for DBpedia in Greek took 1.2180776596069336s
Consistency | Check Invalid usage of undefined properties for DBpedia in Greek took 2.1566951274871826s
Conciseness | Check Extensional conciseness for DBpedia in Greek took 0.034860849380493164s
Conciseness | Check Intensional conciseness for DBpedia in Greek took 0.7352354526519775s
Security | Sign check for DBpedia in Greek took 0.24792098999023438s
Availability | Check URIs Dereferenciability for DBpedia in Greek took 2070.4075005054474s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 0.6943666934967041s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.021550655364990234s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 7.414817810058594e-05s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.000217437744140625s
Interoperability | Check the re-using of existing vocabs for DBpedia in Greek took 2.384185791015625e-06s
Believability | Calculation of trust value for DBpedia in Greek took 9.775161743164062e-06s
INFO | --- Analysis for dbpedia-el took 2280.5097970962524s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 0.4034733772277832s
Availability | VoID file availability check for DBpedia in Spanish took 0.0006985664367675781s
Extra | Recovery of all triples for DBpedia in Spanish took 3.3266828060150146s
Performance | Total latancy measurement for DBpedia in Spanish took 1.124415636062622s
Amount of data | Number of triples check for DBpedia in Spanish took 0.8584344387054443s
Interoperability | New terms check for DBpedia in Spanish took 2.8840878009796143s
Versatility | Languages check for DBpedia in Spanish took 61.51251029968262s
Interpretability | Number of blank nodes check for DBpedia in Spanish took 0.3483555316925049s
Security | Check HTTPS for DBpedia in Spanish took 0.13290715217590332s
Interpretability | RDF structures check for DBpedia in Spanish took 1.552971601486206s
Versatility | Serialization formats check for DBpedia in Spanish took 0.707655668258667s
Availability | RDF dump link check for DBpedia in Spanish took 0.38576459884643555s
License | MR license check for DBpedia in Spanish took 1.0724096298217773s
License | HR license check for DBpedia in Spanish took 60.64380145072937s
Amount of data | Number of property check for DBpedia in Spanish took 0.2967569828033447s
Understandability | Number of label check for DBpedia in Spanish took 2.2187576293945312s
Understandability | URI regex check for DBpedia in Spanish took 0.7835462093353271s
Understandability | Vocabs check for DBpedia in Spanish took 0.42551517486572266s
Verifiability | Authors check for DBpedia in Spanish took 0.3069770336151123s
Verifiability | Publishers check for DBpedia in Spanish took 0.2846500873565674s
Performance | Throughput check for DBpedia in Spanish took 10.606854438781738s
Amount of data | Check the number of entities for DBpedia in Spanish took 7.390975952148438e-05s
Verifiability | Contribs. check for DBpedia in Spanish took 0.2768726348876953s
Interlinking | sameAs chians check for DBpedia in Spanish took 0.7649521827697754s
Interlinking | skos check for DBpedia in Spanish took 0.7663111686706543s
Interlinking | skos check for DBpedia in Spanish took 0.2167513370513916s
Timeliness | dataset update frequency check for DBpedia in Spanish took 0.47423338890075684s
Currency | Creation date check for DBpedia in Spanish took 0.5726871490478516s
Currency | Modification date check for DBpedia in Spanish took 0.5567789077758789s
Rep.Conc. | URIs length for DBpedia in Spanish took 7.433032512664795s
Interoperability | New vocabularies check for DBpedia in Spanish took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Spanish took 0.2957892417907715s
Accuracy | Check Functional Property for DBpedia in Spanish took 0.6625819206237793s
Accuracy | Check Inverse Functional Property for DBpedia in Spanish took 0.5101456642150879s
Accuracy | Check Empty annotation labels for DBpedia in Spanish took 1.0077440738677979s
Accuracy | Check White space in annotation for DBpedia in Spanish took 0.030927181243896484s
Accuracy | Check Datatype consistency for DBpedia in Spanish took 0.034143924713134766s
Consistency | Disjoint class check for DBpedia in Spanish took 0.27996349334716797s
Consistency | Check Misplaced properties for DBpedia in Spanish took 8.621675252914429s
Consistency | Misplaced classes for DBpedia in Spanish took 1.0712900161743164s
Consistency | Check Ontology hijacking for DBpedia in Spanish took 2.1957759857177734s
Consistency | Check Invalid usage of undefined classes for DBpedia in Spanish took 1.2095084190368652s
Consistency | Check Invalid usage of undefined properties for DBpedia in Spanish took 6.773746013641357s
Conciseness | Check Extensional conciseness for DBpedia in Spanish took 0.03431534767150879s
Conciseness | Check Intensional conciseness for DBpedia in Spanish took 1.29001784324646s
Security | Sign check for DBpedia in Spanish took 0.32009363174438477s
Availability | Check URIs Dereferenciability for DBpedia in Spanish took 2.831099510192871s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 0.364504337310791s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.021160125732421875s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 0.0001125335693359375s
Interoperability | Check the re-using of existing vocabs for DBpedia in Spanish took 1.430511474609375e-06s
Believability | Calculation of trust value for DBpedia in Spanish took 1.0728836059570312e-05s
INFO | --- Analysis for dbpedia-es took 2783.2030668258667s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 1.176584005355835s
Availability | VoID file availability check for DBpedia in Basque took 0.0006275177001953125s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.2921323776245117s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.02199554443359375s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 4.315376281738281e-05s
Believability | Calculation of trust value for DBpedia in Basque took 1.049041748046875e-05s
INFO | --- Analysis for dbpedia-eu took 6.702223539352417s
Availability | SPARQL endpoint availability check for DBpedia in French took 0.1458721160888672s
Availability | VoID file availability check for DBpedia in French took 0.0006046295166015625s
Extra | Recovery of all triples for DBpedia in French took 300.1042912006378s
Performance | Total latancy measurement for DBpedia in French took 3.83573055267334s
Amount of data | Number of triples check for DBpedia in French took 82.54741740226746s
Interoperability | New terms check for DBpedia in French took 45.459535360336304s
Versatility | Languages check for DBpedia in French took 300.11181831359863s
Interpretability | Number of blank nodes check for DBpedia in French took 246.54771876335144s
Security | Check HTTPS for DBpedia in French took 14.31310248374939s
Interpretability | RDF structures check for DBpedia in French took 17.243301153182983s
Versatility | Serialization formats check for DBpedia in French took 4.991069555282593s
Availability | RDF dump link check for DBpedia in French took 13.345945596694946s
License | MR license check for DBpedia in French took 2.8842697143554688s
License | HR license check for DBpedia in French took 300.15952730178833s
Amount of data | Number of property check for DBpedia in French took 0.4218869209289551s
Understandability | Number of label check for DBpedia in French took 2.5638561248779297s
Understandability | URI regex check for DBpedia in French took 0.31906795501708984s
Understandability | Vocabs check for DBpedia in French took 0.43724703788757324s
Verifiability | Authors check for DBpedia in French took 1.0837359428405762s
Verifiability | Publishers check for DBpedia in French took 0.13680362701416016s
Performance | Throughput check for DBpedia in French took 10.594220161437988s
Amount of data | Check the number of entities for DBpedia in French took 8.869171142578125e-05s
Verifiability | Contribs. check for DBpedia in French took 0.5070478916168213s
Interlinking | sameAs chians check for DBpedia in French took 2.77911639213562s
Interlinking | skos check for DBpedia in French took 0.3351280689239502s
Interlinking | skos check for DBpedia in French took 0.07572603225708008s
Timeliness | dataset update frequency check for DBpedia in French took 0.4762141704559326s
Currency | Creation date check for DBpedia in French took 0.32377171516418457s
Currency | Modification date check for DBpedia in French took 0.1885530948638916s
Rep.Conc. | URIs length for DBpedia in French took 89.99626588821411s
Interoperability | New vocabularies check for DBpedia in French took 38.35240650177002s
Consistency | Deprecated classes/propertiers check for DBpedia in French took 0.09473180770874023s
Accuracy | Check Functional Property for DBpedia in French took 0.1531665325164795s
Accuracy | Check Inverse Functional Property for DBpedia in French took 0.13511276245117188s
Accuracy | Check Empty annotation labels for DBpedia in French took 29.6544291973114s
Accuracy | Check White space in annotation for DBpedia in French took 3.09623384475708s
Consistency | Disjoint class check for DBpedia in French took 0.3027946949005127s
Consistency | Check Misplaced properties for DBpedia in French took 8.31227159500122s
Consistency | Misplaced classes for DBpedia in French took 0.8279778957366943s
Consistency | Check Ontology hijacking for DBpedia in French took 29.188828229904175s
Consistency | Check Invalid usage of undefined properties for DBpedia in French took 7.976048231124878s
Conciseness | Check Extensional conciseness for DBpedia in French took 0.000186920166015625s
Conciseness | Check Intensional conciseness for DBpedia in French took 1.1620619297027588s
Security | Sign check for DBpedia in French took 0.1825399398803711s
Availability | Check URIs Dereferenciability for DBpedia in French took 2181.6240124702454s
Completeness | Calculation of interlinking completeness for DBpedia in French took 0.7130208015441895s
Reputation | Calculation of the PageRank for DBpedia in French took 0.021559476852416992s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 9.131431579589844e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 0.0001201629638671875s
Interoperability | Check the re-using of existing vocabs for DBpedia in French took 17.475290298461914s
Believability | Calculation of trust value for DBpedia in French took 1.1920928955078125e-05s
INFO | --- Analysis for dbpedia-fr took 4113.782662630081s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 1.874732494354248s
Availability | VoID file availability check for DBpedia in Japanese took 4.003174304962158s
Extra | Recovery of all triples for DBpedia in Japanese took 5.454843282699585s
Performance | Total latancy measurement for DBpedia in Japanese took 6.5586419105529785s
Amount of data | Number of triples check for DBpedia in Japanese took 49.007344007492065s
Interoperability | New terms check for DBpedia in Japanese took 17.29489779472351s
Versatility | Languages check for DBpedia in Japanese took 1.3292691707611084s
Interpretability | Number of blank nodes check for DBpedia in Japanese took 1.3112757205963135s
Security | Check HTTPS for DBpedia in Japanese took 0.793748140335083s
Interpretability | RDF structures check for DBpedia in Japanese took 1.3625707626342773s
Versatility | Serialization formats check for DBpedia in Japanese took 1.7343976497650146s
Availability | RDF dump link check for DBpedia in Japanese took 1.3168177604675293s
License | MR license check for DBpedia in Japanese took 1.3466615676879883s
License | HR license check for DBpedia in Japanese took 121.31619954109192s
Amount of data | Number of property check for DBpedia in Japanese took 1.3220772743225098s
Understandability | Number of label check for DBpedia in Japanese took 8.675583600997925s
Understandability | URI regex check for DBpedia in Japanese took 2.6351308822631836s
Understandability | Vocabs check for DBpedia in Japanese took 1.3201653957366943s
Verifiability | Authors check for DBpedia in Japanese took 1.3299181461334229s
Verifiability | Publishers check for DBpedia in Japanese took 1.31589674949646s
Performance | Throughput check for DBpedia in Japanese took 13.123363494873047s
Amount of data | Check the number of entities for DBpedia in Japanese took 3.457069396972656e-05s
Verifiability | Contribs. check for DBpedia in Japanese took 1.4856507778167725s
Interlinking | sameAs chians check for DBpedia in Japanese took 2.3387396335601807s
Interlinking | skos check for DBpedia in Japanese took 1.31654953956604s
Interlinking | skos check for DBpedia in Japanese took 1.3181066513061523s
Timeliness | dataset update frequency check for DBpedia in Japanese took 1.6165082454681396s
Currency | Creation date check for DBpedia in Japanese took 2.8210227489471436s
Currency | Modification date check for DBpedia in Japanese took 2.6287789344787598s
Rep.Conc. | URIs length for DBpedia in Japanese took 138.66907286643982s
Interoperability | New vocabularies check for DBpedia in Japanese took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Japanese took 1.3127152919769287s
Accuracy | Check Functional Property for DBpedia in Japanese took 1.3390562534332275s
Accuracy | Check Inverse Functional Property for DBpedia in Japanese took 1.3418524265289307s
Accuracy | Check Empty annotation labels for DBpedia in Japanese took 3.2643370628356934s
Accuracy | Check White space in annotation for DBpedia in Japanese took 0.026045799255371094s
Accuracy | Check Datatype consistency for DBpedia in Japanese took 0.032552480697631836s
Consistency | Disjoint class check for DBpedia in Japanese took 1.4398765563964844s
Consistency | Check Misplaced properties for DBpedia in Japanese took 122.62749767303467s
Consistency | Misplaced classes for DBpedia in Japanese took 2.9530587196350098s
Consistency | Check Ontology hijacking for DBpedia in Japanese took 4.358343124389648s
Consistency | Check Invalid usage of undefined classes for DBpedia in Japanese took 1.2244682312011719s
Consistency | Check Invalid usage of undefined properties for DBpedia in Japanese took 122.54499435424805s
Conciseness | Check Extensional conciseness for DBpedia in Japanese took 0.03469395637512207s
Conciseness | Check Intensional conciseness for DBpedia in Japanese took 3.4464950561523438s
Security | Sign check for DBpedia in Japanese took 1.312744140625s
Availability | Check URIs Dereferenciability for DBpedia in Japanese took 8.894656896591187s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 0.3569023609161377s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.02425527572631836s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 0.00011515617370605469s
Interoperability | Check the re-using of existing vocabs for DBpedia in Japanese took 1.6689300537109375e-06s
Believability | Calculation of trust value for DBpedia in Japanese took 9.775161743164062e-06s
INFO | --- Analysis for dbpedia-ja took 1213.4312949180603s
Availability | SPARQL endpoint availability check for dbpedia lite took 4.458427429199219e-05s
Availability | VoID file availability check for dbpedia lite took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for dbpedia lite took 0.27014923095703125s
Reputation | Calculation of the PageRank for dbpedia lite took 0.02107071876525879s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for dbpedia lite took 0.0008268356323242188s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 0.00011277198791503906s
Believability | Calculation of trust value for dbpedia lite took 6.198883056640625e-06s
INFO | --- Analysis for dbpedia-lite took 6.134341478347778s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 0.2538611888885498s
Availability | VoID file availability check for DBpedia in Dutch took 0.0005862712860107422s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 0.2641909122467041s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.020413637161254883s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.00016617774963378906s
Believability | Calculation of trust value for DBpedia in Dutch took 1.049041748046875e-05s
INFO | --- Analysis for dbpedia-nl took 3.2353732585906982s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 5.101885795593262s
Availability | VoID file availability check for DBpedia in Portuguese took 0.0007765293121337891s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 0.2668912410736084s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.020763158798217773s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 8.821487426757812e-05s
Believability | Calculation of trust value for DBpedia in Portuguese took 9.298324584960938e-06s
INFO | --- Analysis for dbpedia-pt took 39.23409104347229s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 0.00010895729064941406s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 0.0006926059722900391s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 0.2662179470062256s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.020551681518554688s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight NIF NER Corpus took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight NIF NER Corpus took 0.0008001327514648438s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight NIF NER Corpus took 8.034706115722656e-05s
Believability | Calculation of trust value for DBpedia Spotlight NIF NER Corpus took 9.298324584960938e-06s
INFO | --- Analysis for dbpedia-spotlight-nif-ner-corpus took 13.532654047012329s
Availability | SPARQL endpoint availability check for DBTropes took 4.5299530029296875e-05s
Availability | VoID file availability check for DBTropes took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for DBTropes took 0.278688907623291s
Reputation | Calculation of the PageRank for DBTropes took 0.02077460289001465s
Interlinking | Calculation of Degree of Connection for DBTropes took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for DBTropes took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for DBTropes took 0.00013136863708496094s
Believability | Calculation of trust value for DBTropes took 9.5367431640625e-06s
INFO | --- Analysis for dbtropes took 3.041133165359497s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 4.506111145019531e-05s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.0006551742553710938s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 0.27880382537841797s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.02225661277770996s
Interlinking | Calculation of Degree of Connection for DBTune.org Artists: Last.fm took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for DBTune.org Artists: Last.fm took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 5.7697296142578125e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 1.239776611328125e-05s
INFO | --- Analysis for dbtune-artists-last-fm took 2.701870918273926s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 7.128715515136719e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.0004057884216308594s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 0.26807284355163574s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.020980119705200195s
Interlinking | Calculation of Degree of Connection for DBTune.org AudioScrobbler RDF Service took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for DBTune.org AudioScrobbler RDF Service took 0.0008022785186767578s
Interlinking | Calculation of Clustering coefficient for DBTune.org AudioScrobbler RDF Service took 4.220008850097656e-05s
Believability | Calculation of trust value for DBTune.org AudioScrobbler RDF Service took 1.239776611328125e-05s
INFO | --- Analysis for dbtune-audioscrobbler took 2.6040358543395996s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 5.537344694137573s
Availability | VoID file availability check for DBTune.org/classical took 0.0006513595581054688s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.2689859867095947s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.022290706634521484s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.00079345703125s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 8.916854858398438e-05s
Believability | Calculation of trust value for DBTune.org/classical took 1.3113021850585938e-05s
INFO | --- Analysis for dbtune-classical took 8.693947792053223s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 5.505310297012329s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.0007412433624267578s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.28348302841186523s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.021455049514770508s
Interlinking | Calculation of Degree of Connection for DBTune.org John Peel sessions RDF server took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for DBTune.org John Peel sessions RDF server took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 7.05718994140625e-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 10.716036081314087s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 5.502558946609497s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.0007684230804443359s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.2675459384918213s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.02072286605834961s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 7.200241088867188e-05s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 1.4066696166992188e-05s
INFO | --- Analysis for dbtune-magnatune took 9.718103647232056s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 0.1315598487854004s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.0005652904510498047s
Extra | Recovery of all triples for DBTune.org Musicbrainz D2R Server took 32.66717886924744s
Performance | Total latancy measurement for DBTune.org Musicbrainz D2R Server took 0.5247063636779785s
Amount of data | Number of triples check for DBTune.org Musicbrainz D2R Server took 0.8486671447753906s
Interoperability | New terms check for DBTune.org Musicbrainz D2R Server took 1.5966403484344482s
Versatility | Languages check for DBTune.org Musicbrainz D2R Server took 1.4528753757476807s
Interpretability | Number of blank nodes check for DBTune.org Musicbrainz D2R Server took 0.7266008853912354s
Interpretability | RDF structures check for DBTune.org Musicbrainz D2R Server took 0.1123056411743164s
Versatility | Serialization formats check for DBTune.org Musicbrainz D2R Server took 0.11205887794494629s
Availability | RDF dump link check for DBTune.org Musicbrainz D2R Server took 0.08496785163879395s
License | MR license check for DBTune.org Musicbrainz D2R Server took 0.09185910224914551s
License | HR license check for DBTune.org Musicbrainz D2R Server took 3.7532215118408203s
Amount of data | Number of property check for DBTune.org Musicbrainz D2R Server took 0.11001396179199219s
Understandability | Number of label check for DBTune.org Musicbrainz D2R Server took 0.24635672569274902s
Understandability | URI regex check for DBTune.org Musicbrainz D2R Server took 0.17006134986877441s
Understandability | Vocabs check for DBTune.org Musicbrainz D2R Server took 0.0843360424041748s
Verifiability | Authors check for DBTune.org Musicbrainz D2R Server took 0.08554673194885254s
Verifiability | Publishers check for DBTune.org Musicbrainz D2R Server took 0.0844261646270752s
Performance | Throughput check for DBTune.org Musicbrainz D2R Server took 10.541892290115356s
Amount of data | Check the number of entities for DBTune.org Musicbrainz D2R Server took 7.176399230957031e-05s
Verifiability | Contribs. check for DBTune.org Musicbrainz D2R Server took 0.08480691909790039s
Interlinking | sameAs chians check for DBTune.org Musicbrainz D2R Server took 0.15272021293640137s
Interlinking | skos check for DBTune.org Musicbrainz D2R Server took 0.08519482612609863s
Interlinking | skos check for DBTune.org Musicbrainz D2R Server took 0.08487677574157715s
Timeliness | dataset update frequency check for DBTune.org Musicbrainz D2R Server took 0.08549761772155762s
Currency | Creation date check for DBTune.org Musicbrainz D2R Server took 0.19796514511108398s
Currency | Modification date check for DBTune.org Musicbrainz D2R Server took 0.1945021152496338s
Rep.Conc. | URIs length for DBTune.org Musicbrainz D2R Server took 8.719323635101318s
Interoperability | New vocabularies check for DBTune.org Musicbrainz D2R Server took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for DBTune.org Musicbrainz D2R Server took 0.11015915870666504s
Accuracy | Check Functional Property for DBTune.org Musicbrainz D2R Server took 0.08752632141113281s
Accuracy | Check Inverse Functional Property for DBTune.org Musicbrainz D2R Server took 0.08461785316467285s
Accuracy | Check Empty annotation labels for DBTune.org Musicbrainz D2R Server took 2.219688892364502s
Accuracy | Check White space in annotation for DBTune.org Musicbrainz D2R Server took 0.09481310844421387s
Accuracy | Check Datatype consistency for DBTune.org Musicbrainz D2R Server took 1.1762712001800537s
Consistency | Disjoint class check for DBTune.org Musicbrainz D2R Server took 0.08590126037597656s
Consistency | Check Misplaced properties for DBTune.org Musicbrainz D2R Server took 1.0858409404754639s
Consistency | Check Ontology hijacking for DBTune.org Musicbrainz D2R Server took 3.7510199546813965s
Consistency | Check Invalid usage of undefined classes for DBTune.org Musicbrainz D2R Server took 1.2505228519439697s
Consistency | Check Invalid usage of undefined properties for DBTune.org Musicbrainz D2R Server took 2.1500818729400635s
Conciseness | Check Extensional conciseness for DBTune.org Musicbrainz D2R Server took 0.6147382259368896s
Security | Sign check for DBTune.org Musicbrainz D2R Server took 0.08521199226379395s
Availability | Check URIs Dereferenciability for DBTune.org Musicbrainz D2R Server took 1197.6785728931427s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 0.46756958961486816s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.021683931350708008s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.0001316070556640625s
Interoperability | Check the re-using of existing vocabs for DBTune.org Musicbrainz D2R Server took 2.6226043701171875e-06s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 1.1682510375976562e-05s
INFO | --- Analysis for dbtune-musicbrainz took 1301.9644565582275s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 0.2992522716522217s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.00029468536376953125s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 0.2660491466522217s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.021096229553222656s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 6.866455078125e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 1.4543533325195312e-05s
INFO | --- Analysis for dbtune-myspace took 3.0516858100891113s
Availability | SPARQL endpoint availability check for data.dcs took 4.482269287109375e-05s
Availability | VoID file availability check for data.dcs took 0.0002849102020263672s
Completeness | Calculation of interlinking completeness for data.dcs took 0.26463985443115234s
Reputation | Calculation of the PageRank for data.dcs took 0.021074771881103516s
Interlinking | Calculation of Degree of Connection for data.dcs took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for data.dcs took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for data.dcs took 7.581710815429688e-05s
Believability | Calculation of trust value for data.dcs took 1.0728836059570312e-05s
INFO | --- Analysis for dcs-sheffield took 2.533418655395508s
Availability | SPARQL endpoint availability check for de-gaap-ontology-lexicon took 4.553794860839844e-05s
Availability | VoID file availability check for de-gaap-ontology-lexicon took 0.0007293224334716797s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 0.2664210796356201s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.021067380905151367s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 4.363059997558594e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 1.3828277587890625e-05s
INFO | --- Analysis for de-gaap-ontology-lexicon took 4.287264108657837s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 9.036064147949219e-05s
Availability | VoID file availability check for Debian Package Tracking System took 0.0006611347198486328s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 0.27372217178344727s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.022313833236694336s
Interlinking | Calculation of Degree of Connection for Debian Package Tracking System took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Debian Package Tracking System took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 4.792213439941406e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 1.3589859008789062e-05s
INFO | --- Analysis for debian-package-tracking-system took 4.033511161804199s
Availability | SPARQL endpoint availability check for Projeto Desaparecidos took 8.940696716308594e-05s
Availability | VoID file availability check for Projeto Desaparecidos took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for Projeto Desaparecidos took 0.2720813751220703s
Reputation | Calculation of the PageRank for Projeto Desaparecidos took 0.021953582763671875s
Interlinking | Calculation of Degree of Connection for Projeto Desaparecidos took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Projeto Desaparecidos took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Projeto Desaparecidos took 3.647804260253906e-05s
Believability | Calculation of trust value for Projeto Desaparecidos took 1.3113021850585938e-05s
INFO | --- Analysis for desaparecidos took 2.7943954467773438s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 8.940696716308594e-05s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.0005543231964111328s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 0.2701265811920166s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.020781278610229492s
Interlinking | Calculation of Degree of Connection for Deusto Entrepreneurship: sharing business knowledge took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Deusto Entrepreneurship: sharing business knowledge took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 0.0001068115234375s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 1.3589859008789062e-05s
INFO | --- Analysis for deustoentrepreneurship took 4.003097295761108s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 9.1552734375e-05s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 0.0007069110870361328s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 0.2670862674713135s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.022185564041137695s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.00011777877807617188s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 1.4066696166992188e-05s
INFO | --- Analysis for deustotech took 4.788715362548828s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 1.3625555038452148s
Availability | VoID file availability check for Deutsche Biographie took 0.0005211830139160156s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 0.2709059715270996s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.020603418350219727s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 4.1484832763671875e-05s
Believability | Calculation of trust value for Deutsche Biographie took 1.3589859008789062e-05s
INFO | --- Analysis for deutsche-biographie took 4.176114082336426s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 4.410743713378906e-05s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.0006780624389648438s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 0.29957056045532227s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.02167654037475586s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 6.008148193359375e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 1.3828277587890625e-05s
INFO | --- Analysis for deutsche-nationalbibliografie-dnb took 6.391673564910889s
Availability | SPARQL endpoint availability check for dev8d took 9.250640869140625e-05s
Availability | VoID file availability check for dev8d took 0.0005948543548583984s
Completeness | Calculation of interlinking completeness for dev8d took 0.27422022819519043s
Reputation | Calculation of the PageRank for dev8d took 0.021756887435913086s
Interlinking | Calculation of Degree of Connection for dev8d took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for dev8d took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for dev8d took 0.00010061264038085938s
Believability | Calculation of trust value for dev8d took 1.4781951904296875e-05s
INFO | --- Analysis for dev8d took 6.650798559188843s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 30.14611029624939s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 0.000732421875s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 0.2694880962371826s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.02153468132019043s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.0009021759033203125s
Interlinking | Calculation of Clustering coefficient for Dewey Decimal Classification (DDC) took 6.580352783203125e-05s
Believability | Calculation of trust value for Dewey Decimal Classification (DDC) took 1.33514404296875e-05s
INFO | --- Analysis for dewey_decimal_classification took 92.677419424057s
Availability | SPARQL endpoint availability check for Distributed Hydrology Soil Vegetation Model took 4.649162292480469e-05s
Availability | VoID file availability check for Distributed Hydrology Soil Vegetation Model took 0.0006916522979736328s
Completeness | Calculation of interlinking completeness for Distributed Hydrology Soil Vegetation Model took 0.28103089332580566s
Reputation | Calculation of the PageRank for Distributed Hydrology Soil Vegetation Model took 0.02068328857421875s
Interlinking | Calculation of Degree of Connection for Distributed Hydrology Soil Vegetation Model took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Distributed Hydrology Soil Vegetation Model took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Distributed Hydrology Soil Vegetation Model took 4.172325134277344e-05s
Believability | Calculation of trust value for Distributed Hydrology Soil Vegetation Model took 1.4066696166992188e-05s
INFO | --- Analysis for DHSVM took 23.88472270965576s
Availability | SPARQL endpoint availability check for Diavgeia took 4.291534423828125e-05s
Availability | VoID file availability check for Diavgeia took 0.0007090568542480469s
Completeness | Calculation of interlinking completeness for Diavgeia took 0.27420496940612793s
Reputation | Calculation of the PageRank for Diavgeia took 0.02076244354248047s
Interlinking | Calculation of Degree of Connection for Diavgeia took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Diavgeia took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 8.96453857421875e-05s
Believability | Calculation of trust value for Diavgeia took 1.0251998901367188e-05s
INFO | --- Analysis for diavgeia took 5.4006993770599365s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 4.57763671875e-05s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.000675201416015625s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.2741522789001465s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.020502090454101562s
Interlinking | Calculation of Degree of Connection for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00011897087097167969s
Believability | Calculation of trust value for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.4066696166992188e-05s
INFO | --- Analysis for didactalia took 15.832488775253296s
Availability | SPARQL endpoint availability check for DisGeNET took 1.6149659156799316s
Availability | VoID file availability check for DisGeNET took 0.00077056884765625s
Completeness | Calculation of interlinking completeness for DisGeNET took 0.26780152320861816s
Reputation | Calculation of the PageRank for DisGeNET took 0.020869016647338867s
Interlinking | Calculation of Degree of Connection for DisGeNET took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for DisGeNET took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.00016260147094726562s
Believability | Calculation of trust value for DisGeNET took 1.3828277587890625e-05s
INFO | --- Analysis for disgenet took 6.9814183712005615s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 9.012222290039062e-05s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 0.0007882118225097656s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 0.27585411071777344s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.020908355712890625s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.0007991790771484375s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 3.7670135498046875e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 1.5020370483398438e-05s
INFO | --- Analysis for dkh-deusto-knowledge-hub took 5.669422626495361s
Availability | SPARQL endpoint availability check for DM2E took 9.417533874511719e-05s
Availability | VoID file availability check for DM2E took 0.0006668567657470703s
Completeness | Calculation of interlinking completeness for DM2E took 0.27422332763671875s
Reputation | Calculation of the PageRank for DM2E took 0.02088761329650879s
Interlinking | Calculation of Degree of Connection for DM2E took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DM2E took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.00010919570922851562s
Believability | Calculation of trust value for DM2E took 1.4781951904296875e-05s
INFO | --- Analysis for dm2e took 3.4107744693756104s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 8.988380432128906e-05s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.0006499290466308594s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 0.32756781578063965s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.020684480667114258s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.0001621246337890625s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 1.3828277587890625e-05s
INFO | --- Analysis for dnb-gemeinsame-normdatei took 7.205418586730957s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 9.250640869140625e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 0.0006973743438720703s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 0.2669494152069092s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.021012544631958008s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.0008795261383056641s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 7.414817810058594e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 1.9311904907226562e-05s
INFO | --- Analysis for doi took 7.6390087604522705s
Availability | SPARQL endpoint availability check for Driggu Florentino took 9.512901306152344e-05s
Availability | VoID file availability check for Driggu Florentino took 0.0006089210510253906s
Completeness | Calculation of interlinking completeness for Driggu Florentino took 0.27358436584472656s
Reputation | Calculation of the PageRank for Driggu Florentino took 0.020868539810180664s
Interlinking | Calculation of Degree of Connection for Driggu Florentino took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Driggu Florentino took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Driggu Florentino took 3.504753112792969e-05s
Believability | Calculation of trust value for Driggu Florentino took 1.239776611328125e-05s
INFO | --- Analysis for Driggu took 3.2897777557373047s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.2982311248779297s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.0005342960357666016s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 0.26528096199035645s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.02044987678527832s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 3.933906555175781e-05s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 1.0251998901367188e-05s
INFO | --- Analysis for drug-data-hifm took 15.72227668762207s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 270.9952323436737s
Availability | VoID file availability check for MetaLex Document Server took 0.0007572174072265625s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.27942967414855957s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.020992279052734375s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 5.412101745605469e-05s
Believability | Calculation of trust value for MetaLex Document Server took 1.430511474609375e-05s
INFO | --- Analysis for dutch-national-regulations-metalex took 554.3588345050812s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 2.2488033771514893s
Availability | VoID file availability check for Dutch Ships and Sailors took 0.0008077621459960938s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 0.27445077896118164s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.02107691764831543s
Interlinking | Calculation of Degree of Connection for Dutch Ships and Sailors took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Dutch Ships and Sailors took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 4.1961669921875e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 1.2159347534179688e-05s
INFO | --- Analysis for dutch-ships-and-sailors took 13.84801435470581s
Availability | SPARQL endpoint availability check for DWS-Group took 4.482269287109375e-05s
Availability | VoID file availability check for DWS-Group took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for DWS-Group took 0.26866817474365234s
Reputation | Calculation of the PageRank for DWS-Group took 0.021147966384887695s
Interlinking | Calculation of Degree of Connection for DWS-Group took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for DWS-Group took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 0.0001220703125s
Believability | Calculation of trust value for DWS-Group took 1.2636184692382812e-05s
INFO | --- Analysis for dws-group took 2.5332558155059814s
Availability | SPARQL endpoint availability check for E1 - Nuvem dados took 9.608268737792969e-05s
Availability | VoID file availability check for E1 - Nuvem dados took 0.0005857944488525391s
Completeness | Calculation of interlinking completeness for E1 - Nuvem dados took 0.3428523540496826s
Reputation | Calculation of the PageRank for E1 - Nuvem dados took 0.02064990997314453s
Interlinking | Calculation of Degree of Connection for E1 - Nuvem dados took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for E1 - Nuvem dados took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for E1 - Nuvem dados took 3.4332275390625e-05s
Believability | Calculation of trust value for E1 - Nuvem dados took 1.3589859008789062e-05s
INFO | --- Analysis for E1 took 3.9509098529815674s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 0.05361580848693848s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.00037384033203125s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 0.27395129203796387s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.020366668701171875s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Alaska Fairbanks took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Alaska Fairbanks took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.00011706352233886719s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 1.5974044799804688e-05s
INFO | --- Analysis for eagle-i-alaska took 2.532729387283325s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 0.04306149482727051s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 0.2710750102996826s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.020365238189697266s
Interlinking | Calculation of Degree of Connection for eagle-i @ Clark Atlanta University took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ Clark Atlanta University took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 5.91278076171875e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 1.4066696166992188e-05s
INFO | --- Analysis for eagle-i-cau took 2.647836685180664s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 0.03284907341003418s
Availability | VoID file availability check for eagle-i @ The City College of New York took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.26592206954956055s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.020708084106445312s
Interlinking | Calculation of Degree of Connection for eagle-i @ The City College of New York took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ The City College of New York took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 6.604194641113281e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 1.3828277587890625e-05s
INFO | --- Analysis for eagle-i-ccny-cuny took 2.554945230484009s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 0.0391240119934082s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 0.28537893295288086s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.02058577537536621s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 9.918212890625e-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.539451837539673s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 0.037162065505981445s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.2704925537109375s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.02270340919494629s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.0001373291015625s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 1.3113021850585938e-05s
INFO | --- Analysis for eagle-i-dartmouth took 2.769009590148926s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.08402132987976074s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.0004553794860839844s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 0.2796213626861572s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.020574331283569336s
Interlinking | Calculation of Degree of Connection for eagle-i @ Florida Agricultural and Mechanical University took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Florida Agricultural and Mechanical University took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 8.916854858398438e-05s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 1.2636184692382812e-05s
INFO | --- Analysis for eagle-i-famu took 2.613001823425293s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 0.06410765647888184s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.2730858325958252s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.020618200302124023s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.0001366138458251953s
Believability | Calculation of trust value for eagle-i @ Harvard University took 1.52587890625e-05s
INFO | --- Analysis for eagle-i-harvard took 2.569603204727173s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 0.05316329002380371s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 0.2653956413269043s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.020911455154418945s
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.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.0001285076141357422s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 2.0503997802734375e-05s
INFO | --- Analysis for eagle-i-hawaii took 2.5197980403900146s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 0.04221916198730469s
Availability | VoID file availability check for eagle-i @ Howard University took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 0.2654745578765869s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.020691871643066406s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 6.628036499023438e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 1.430511474609375e-05s
INFO | --- Analysis for eagle-i-howard took 2.535604953765869s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 0.0427398681640625s
Availability | VoID file availability check for eagle-i @ Hunter College took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 0.2664210796356201s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.020647764205932617s
Interlinking | Calculation of Degree of Connection for eagle-i @ Hunter College took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for eagle-i @ Hunter College took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 7.2479248046875e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 1.4781951904296875e-05s
INFO | --- Analysis for eagle-i-hunter-cuny took 2.550253391265869s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 0.03663825988769531s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 0.2844984531402588s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.020873069763183594s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.0007832050323486328s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.00012683868408203125s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 9.5367431640625e-06s
INFO | --- Analysis for eagle-i-jsu took 2.5374088287353516s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 0.033283233642578125s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 0.26457810401916504s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.0205838680267334s
Interlinking | Calculation of Degree of Connection for eagle-i @ Meharry Medical College took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ Meharry Medical College took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 4.029273986816406e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 1.430511474609375e-05s
INFO | --- Analysis for eagle-i-meharry took 2.5603413581848145s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 0.04084324836730957s
Availability | VoID file availability check for eagle-i @ Montana State University took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 0.2599952220916748s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.020932912826538086s
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.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 0.00010585784912109375s
Believability | Calculation of trust value for eagle-i @ Montana State University took 1.5020370483398438e-05s
INFO | --- Analysis for eagle-i-montana took 2.665097236633301s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 0.03891324996948242s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.0005054473876953125s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 0.29143261909484863s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.021893739700317383s
Interlinking | Calculation of Degree of Connection for eagle-i @ Morehouse School of Medicine took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Morehouse School of Medicine took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 0.00011897087097167969s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 1.430511474609375e-05s
INFO | --- Analysis for eagle-i-msm took 2.5774149894714355s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 0.040064096450805664s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 0.28167223930358887s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.02082061767578125s
Interlinking | Calculation of Degree of Connection for eagle-i @ Oregon Health and Science University took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for eagle-i @ Oregon Health and Science University took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.0001373291015625s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 9.775161743164062e-06s
INFO | --- Analysis for eagle-i-ohsu took 2.5763421058654785s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 0.037729740142822266s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 0.2687664031982422s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.020917654037475586s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 6.723403930664062e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 1.3589859008789062e-05s
INFO | --- Analysis for eagle-i-psm took 2.5507850646972656s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 0.0366055965423584s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 0.26631665229797363s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.020818710327148438s
Interlinking | Calculation of Degree of Connection for eagle-i @ Texas Southern University took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for eagle-i @ Texas Southern University took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Texas Southern University took 6.747245788574219e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 1.4543533325195312e-05s
INFO | --- Analysis for eagle-i-tsu took 2.530566453933716s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 0.04149746894836426s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.00031685829162597656s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 0.3096904754638672s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.020750999450683594s
Interlinking | Calculation of Degree of Connection for eagle-i @ Tuskegee University took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for eagle-i @ Tuskegee University took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 6.842613220214844e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 1.3828277587890625e-05s
INFO | --- Analysis for eagle-i-tuskegee took 2.614703416824341s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 0.0341496467590332s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.0003108978271484375s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 0.26465702056884766s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.022821903228759766s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 0.00010514259338378906s
Believability | Calculation of trust value for eagle-i @ Universidad Central del Caribe took 1.4543533325195312e-05s
INFO | --- Analysis for eagle-i-uccaribe took 2.520334482192993s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.03606915473937988s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.2694408893585205s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0210111141204834s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0001289844512939453s
Believability | Calculation of trust value for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.3589859008789062e-05s
INFO | --- Analysis for eagle-i-upr took 2.5245702266693115s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 0.033115386962890625s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 0.2686729431152344s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.022269010543823242s
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.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 6.628036499023438e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 1.2636184692382812e-05s
INFO | --- Analysis for eagle-i-utep took 2.561490774154663s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 0.0448153018951416s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 0.2736387252807617s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.020840167999267578s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 7.462501525878906e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 1.4543533325195312e-05s
INFO | --- Analysis for eagle-i-utsa took 2.5770835876464844s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 0.16464924812316895s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 0.27014827728271484s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.0212862491607666s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 1.52587890625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.0009772777557373047s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 0.00014400482177734375s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 1.239776611328125e-05s
INFO | --- Analysis for eagle-i-vanderbilt took 2.701730251312256s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 0.040375709533691406s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 0.26682424545288086s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.021231889724731445s
Interlinking | Calculation of Degree of Connection for eagle-i @ Xavier University of Louisiana took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for eagle-i @ Xavier University of Louisiana took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 7.939338684082031e-05s
Believability | Calculation of trust value for eagle-i @ Xavier University of Louisiana took 1.4066696166992188e-05s
INFO | --- Analysis for eagle-i-xula took 2.5731732845306396s
Availability | SPARQL endpoint availability check for Emergency situation took 0.5528616905212402s
Availability | VoID file availability check for Emergency situation took 0.0006556510925292969s
Completeness | Calculation of interlinking completeness for Emergency situation took 0.28205347061157227s
Reputation | Calculation of the PageRank for Emergency situation took 0.021468639373779297s
Interlinking | Calculation of Degree of Connection for Emergency situation took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Emergency situation took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Emergency situation took 5.412101745605469e-05s
Believability | Calculation of trust value for Emergency situation took 1.430511474609375e-05s
INFO | --- Analysis for Earthquake took 3.614609956741333s
Availability | SPARQL endpoint availability check for ESO took 0.4221470355987549s
Availability | VoID file availability check for ESO took 0.0003948211669921875s
Completeness | Calculation of interlinking completeness for ESO took 0.2718195915222168s
Reputation | Calculation of the PageRank for ESO took 0.02070021629333496s
Interlinking | Calculation of Degree of Connection for ESO took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for ESO took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for ESO took 9.1552734375e-05s
Believability | Calculation of trust value for ESO took 1.5020370483398438e-05s
INFO | --- Analysis for Earthquake_case took 3.784672260284424s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 0.10633063316345215s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 0.2731354236602783s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.020593881607055664s
Interlinking | Calculation of Degree of Connection for European Central Bank (ECB) Linked Data took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for European Central Bank (ECB) Linked Data took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 0.00010657310485839844s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 1.049041748046875e-05s
INFO | --- Analysis for ecb-linked-data took 2.597456693649292s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 7.735295534133911s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 0.0006954669952392578s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 0.2737305164337158s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.02047872543334961s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 3.838539123535156e-05s
Believability | Calculation of trust value for European Central Bank Statistics (PublicData.eu) took 9.5367431640625e-06s
INFO | --- Analysis for ecb-statistics-linked-data took 17.20583415031433s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 2.436948776245117s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0006442070007324219s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 0.2750396728515625s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.02094292640686035s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 7.104873657226562e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 1.3589859008789062e-05s
INFO | --- Analysis for ecco-tcp-linked-data took 8.629153966903687s
Availability | SPARQL endpoint availability check for ECLAP took 20.173203468322754s
Availability | VoID file availability check for ECLAP took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for ECLAP took 0.26721620559692383s
Reputation | Calculation of the PageRank for ECLAP took 0.02224898338317871s
Interlinking | Calculation of Degree of Connection for ECLAP took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for ECLAP took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for ECLAP took 4.8160552978515625e-05s
Believability | Calculation of trust value for ECLAP took 1.4543533325195312e-05s
INFO | --- Analysis for eclap took 52.743887186050415s
Availability | SPARQL endpoint availability check for 《老子》译本传播知识图谱 took 0.00012230873107910156s
Availability | VoID file availability check for 《老子》译本传播知识图谱 took 0.000652313232421875s
Completeness | Calculation of interlinking completeness for 《老子》译本传播知识图谱 took 0.27050304412841797s
Reputation | Calculation of the PageRank for 《老子》译本传播知识图谱 took 0.0206298828125s
Interlinking | Calculation of Degree of Connection for 《老子》译本传播知识图谱 took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for 《老子》译本传播知识图谱 took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for 《老子》译本传播知识图谱 took 1.4066696166992188e-05s
Believability | Calculation of trust value for 《老子》译本传播知识图谱 took 1.1920928955078125e-05s
INFO | --- Analysis for ECNU-GISer took 4.360621213912964s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 4.5299530029296875e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.2691769599914551s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.02267909049987793s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 6.866455078125e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 1.4066696166992188e-05s
INFO | --- Analysis for ecs took 2.5190322399139404s
Availability | SPARQL endpoint availability check for Edublogs took 4.410743713378906e-05s
Availability | VoID file availability check for Edublogs took 0.0006272792816162109s
Completeness | Calculation of interlinking completeness for Edublogs took 0.2696099281311035s
Reputation | Calculation of the PageRank for Edublogs took 0.020582199096679688s
Interlinking | Calculation of Degree of Connection for Edublogs took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Edublogs took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Edublogs took 0.00010728836059570312s
Believability | Calculation of trust value for Edublogs took 1.1920928955078125e-05s
INFO | --- Analysis for edublogs took 3.2871687412261963s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 0.531996488571167s
Availability | VoID file availability check for education.data.gov.uk took 0.0005953311920166016s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 0.27007007598876953s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.02089405059814453s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 9.679794311523438e-05s
Believability | Calculation of trust value for education.data.gov.uk took 7.867813110351562e-06s
INFO | --- Analysis for education-data-gov-uk took 4.613877773284912s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 391.5980923175812s
Availability | VoID file availability check for Educational programs - SISVU took 0.0010330677032470703s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 0.4610929489135742s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.021088838577270508s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.0008826255798339844s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 7.796287536621094e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 1.3828277587890625e-05s
INFO | --- Analysis for educationalprograms_sisvu took 1319.883778333664s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 1.1276054382324219s
Availability | VoID file availability check for European Environment Agency Published Products took 0.0007183551788330078s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 0.29639530181884766s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.020735740661621094s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 5.1021575927734375e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 1.1682510375976562e-05s
INFO | --- Analysis for eea took 31.57439136505127s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 0.4847099781036377s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.0005776882171630859s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 0.265897274017334s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.020525693893432617s
Interlinking | Calculation of Degree of Connection for EEA Reporting Obligations Database took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for EEA Reporting Obligations Database took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 5.7220458984375e-05s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 1.1205673217773438e-05s
INFO | --- Analysis for eea-rod took 5.115941762924194s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 0.17676234245300293s
Availability | VoID file availability check for EEA Vocabularies took 0.0007359981536865234s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 0.27916693687438965s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.020495176315307617s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 0.00010395050048828125s
Believability | Calculation of trust value for EEA Vocabularies took 1.430511474609375e-05s
INFO | --- Analysis for eea-vocabularies took 4.9012298583984375s
Availability | SPARQL endpoint availability check for E-Government Ontology took 30.102943658828735s
Availability | VoID file availability check for E-Government Ontology took 0.0005660057067871094s
Completeness | Calculation of interlinking completeness for E-Government Ontology took 0.2765467166900635s
Reputation | Calculation of the PageRank for E-Government Ontology took 0.022843360900878906s
Interlinking | Calculation of Degree of Connection for E-Government Ontology took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for E-Government Ontology took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for E-Government Ontology took 5.412101745605469e-05s
Believability | Calculation of trust value for E-Government Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for EGovOntology took 53.103434801101685s
Availability | SPARQL endpoint availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5204455852508545s
Availability | VoID file availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0006465911865234375s
Extra | Recovery of all triples for Aragon Interoperable Information Structure EI2A - aragon open data took 2.7384235858917236s
Performance | Total latancy measurement for Aragon Interoperable Information Structure EI2A - aragon open data took 1.1854896545410156s
Amount of data | Number of triples check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6087853908538818s
Interoperability | New terms check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.8895432949066162s
Versatility | Languages check for Aragon Interoperable Information Structure EI2A - aragon open data took 60.30513548851013s
Interpretability | Number of blank nodes check for Aragon Interoperable Information Structure EI2A - aragon open data took 3.994389533996582s
Interpretability | RDF structures check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6513118743896484s
Versatility | Serialization formats check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.738619327545166s
Availability | RDF dump link check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.24907445907592773s
License | MR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5048999786376953s
License | HR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 6.378772974014282s
Amount of data | Number of property check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.23719000816345215s
Understandability | Number of label check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4674956798553467s
Understandability | URI regex check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5988731384277344s
Understandability | Vocabs check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.29444313049316406s
Verifiability | Authors check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3401961326599121s
Verifiability | Publishers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2431788444519043s
Performance | Throughput check for Aragon Interoperable Information Structure EI2A - aragon open data took 11.843867540359497s
Amount of data | Check the number of entities for Aragon Interoperable Information Structure EI2A - aragon open data took 7.176399230957031e-05s
Verifiability | Contribs. check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.34607744216918945s
Interlinking | sameAs chians check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.27955079078674316s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.45761656761169434s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2355649471282959s
Timeliness | dataset update frequency check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3246750831604004s
Currency | Creation date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.8917665481567383s
Currency | Modification date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2442612648010254s
Rep.Conc. | URIs length for Aragon Interoperable Information Structure EI2A - aragon open data took 5.6791558265686035s
Interoperability | New vocabularies check for Aragon Interoperable Information Structure EI2A - aragon open data took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.23818254470825195s
Accuracy | Check Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.37737107276916504s
Accuracy | Check Inverse Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3727223873138428s
Accuracy | Check Empty annotation labels for Aragon Interoperable Information Structure EI2A - aragon open data took 0.9871885776519775s
Accuracy | Check White space in annotation for Aragon Interoperable Information Structure EI2A - aragon open data took 0.03015923500061035s
Accuracy | Check Datatype consistency for Aragon Interoperable Information Structure EI2A - aragon open data took 0.029029369354248047s
Consistency | Disjoint class check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2388761043548584s
Consistency | Check Misplaced properties for Aragon Interoperable Information Structure EI2A - aragon open data took 4.103222608566284s
Consistency | Misplaced classes for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4513094425201416s
Consistency | Check Ontology hijacking for Aragon Interoperable Information Structure EI2A - aragon open data took 2.4321365356445312s
Consistency | Check Invalid usage of undefined classes for Aragon Interoperable Information Structure EI2A - aragon open data took 1.190840482711792s
Consistency | Check Invalid usage of undefined properties for Aragon Interoperable Information Structure EI2A - aragon open data took 4.992952108383179s
Conciseness | Check Extensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.03480887413024902s
Conciseness | Check Intensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.38288068771362305s
Security | Sign check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6418008804321289s
Availability | Check URIs Dereferenciability for Aragon Interoperable Information Structure EI2A - aragon open data took 2997.511167049408s
Completeness | Calculation of interlinking completeness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6791448593139648s
Reputation | Calculation of the PageRank for Aragon Interoperable Information Structure EI2A - aragon open data took 0.021571636199951172s
Interlinking | Calculation of Degree of Connection for Aragon Interoperable Information Structure EI2A - aragon open data took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for Aragon Interoperable Information Structure EI2A - aragon open data took 6.246566772460938e-05s
Interoperability | Check the re-using of existing vocabs for Aragon Interoperable Information Structure EI2A - aragon open data took 1.430511474609375e-06s
Believability | Calculation of trust value for Aragon Interoperable Information Structure EI2A - aragon open data took 1.430511474609375e-05s
INFO | --- Analysis for ei2a took 3229.903928756714s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 9.369850158691406e-05s
Availability | VoID file availability check for EIONET RDF Data took 0.0003113746643066406s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 0.2758510112762451s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.020494937896728516s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.0001163482666015625s
Believability | Calculation of trust value for EIONET RDF Data took 6.4373016357421875e-06s
INFO | --- Analysis for eionet-rdf took 3.024346351623535s
Availability | SPARQL endpoint availability check for Google’s Easter Egg i took 9.465217590332031e-05s
Availability | VoID file availability check for Google’s Easter Egg i took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for Google’s Easter Egg i took 0.27674293518066406s
Reputation | Calculation of the PageRank for Google’s Easter Egg i took 0.0207369327545166s
Interlinking | Calculation of Degree of Connection for Google’s Easter Egg i took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Google’s Easter Egg i took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for Google’s Easter Egg i took 3.266334533691406e-05s
Believability | Calculation of trust value for Google’s Easter Egg i took 1.5497207641601562e-05s
INFO | --- Analysis for ElgooG_ took 2.4574902057647705s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 9.159582614898682s
Availability | VoID file availability check for El Viajero's tourism dataset took 0.0012695789337158203s
Completeness | Calculation of interlinking completeness for El Viajero's tourism dataset took 0.28714919090270996s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.021738767623901367s
Interlinking | Calculation of Degree of Connection for El Viajero's tourism dataset took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for El Viajero's tourism dataset took 0.0008425712585449219s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 8.249282836914062e-05s
Believability | Calculation of trust value for El Viajero's tourism dataset took 1.5735626220703125e-05s
INFO | --- Analysis for elviajero took 25.29525852203369s
Availability | SPARQL endpoint availability check for EMN took 8.988380432128906e-05s
Availability | VoID file availability check for EMN took 0.0006542205810546875s
Completeness | Calculation of interlinking completeness for EMN took 0.2727787494659424s
Reputation | Calculation of the PageRank for EMN took 0.02066969871520996s
Interlinking | Calculation of Degree of Connection for EMN took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EMN took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for EMN took 4.220008850097656e-05s
Believability | Calculation of trust value for EMN took 9.5367431640625e-06s
INFO | --- Analysis for emn took 2.6596031188964844s
Availability | SPARQL endpoint availability check for EnAKTing CO2 Emission Dataset took 9.417533874511719e-05s
Availability | VoID file availability check for EnAKTing CO2 Emission Dataset took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 0.2675633430480957s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.020616531372070312s
Interlinking | Calculation of Degree of Connection for EnAKTing CO2 Emission Dataset took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for EnAKTing CO2 Emission Dataset took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 5.4836273193359375e-05s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 8.344650268554688e-06s
INFO | --- Analysis for enakting-co2emission took 2.537970542907715s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 9.1552734375e-05s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.0005502700805664062s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 0.2645583152770996s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.0220034122467041s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 4.315376281738281e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 8.344650268554688e-06s
INFO | --- Analysis for enakting-crime took 2.4708495140075684s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 9.250640869140625e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 0.27147698402404785s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.02250361442565918s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 4.076957702636719e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 9.5367431640625e-06s
INFO | --- Analysis for enakting-energy took 2.474151849746704s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 4.696846008300781e-05s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 0.2686502933502197s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.020603179931640625s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 0.00010085105895996094s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 1.0251998901367188e-05s
INFO | --- Analysis for enakting-mortality took 2.5059468746185303s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 4.601478576660156e-05s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.00028896331787109375s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 0.2682633399963379s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.021993398666381836s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0010325908660888672s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 5.173683166503906e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 9.5367431640625e-06s
INFO | --- Analysis for enakting-nhs took 2.466040849685669s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 4.458427429199219e-05s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 0.27059292793273926s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.02129220962524414s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 5.7220458984375e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 9.059906005859375e-06s
INFO | --- Analysis for enakting-population took 2.490443706512451s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 0.6669032573699951s
Availability | VoID file availability check for English Heritage Periods List took 0.0007734298706054688s
Extra | Recovery of all triples for English Heritage Periods List took 0.4685533046722412s
Performance | Total latancy measurement for English Heritage Periods List took 1.9282283782958984s
Amount of data | Number of triples check for English Heritage Periods List took 0.629918098449707s
Versatility | Languages check for English Heritage Periods List took 0.29384326934814453s
Interpretability | Number of blank nodes check for English Heritage Periods List took 0.5365302562713623s
Security | Check HTTPS for English Heritage Periods List took 0.22623109817504883s
Interpretability | RDF structures check for English Heritage Periods List took 0.2767047882080078s
Versatility | Serialization formats check for English Heritage Periods List took 0.8018937110900879s
Availability | RDF dump link check for English Heritage Periods List took 0.4204823970794678s
License | MR license check for English Heritage Periods List took 0.6235804557800293s
License | HR license check for English Heritage Periods List took 0.3912787437438965s
Amount of data | Number of property check for English Heritage Periods List took 0.46140122413635254s
Understandability | Number of label check for English Heritage Periods List took 0.6010611057281494s
Understandability | URI regex check for English Heritage Periods List took 0.641758918762207s
Understandability | Vocabs check for English Heritage Periods List took 0.5541610717773438s
Verifiability | Authors check for English Heritage Periods List took 0.6101408004760742s
Verifiability | Publishers check for English Heritage Periods List took 0.45270657539367676s
Performance | Throughput check for English Heritage Periods List took 12.428357124328613s
Amount of data | Check the number of entities for English Heritage Periods List took 7.128715515136719e-05s
Verifiability | Contribs. check for English Heritage Periods List took 0.4342796802520752s
Interlinking | sameAs chians check for English Heritage Periods List took 0.4821760654449463s
Interlinking | skos check for English Heritage Periods List took 0.508491039276123s
Interlinking | skos check for English Heritage Periods List took 0.5653989315032959s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.5802183151245117s
Currency | Creation date check for English Heritage Periods List took 0.6456868648529053s
Currency | Modification date check for English Heritage Periods List took 0.7659952640533447s
Rep.Conc. | URIs length for English Heritage Periods List took 0.7829256057739258s
Interoperability | New vocabularies check for English Heritage Periods List took 5.0067901611328125e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Periods List took 0.520125150680542s
Accuracy | Check Functional Property for English Heritage Periods List took 0.29875850677490234s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.3504068851470947s
Consistency | Disjoint class check for English Heritage Periods List took 0.36472368240356445s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.3627622127532959s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.6047337055206299s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.00015044212341308594s
Security | Sign check for English Heritage Periods List took 0.6004512310028076s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 0.2750530242919922s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.020757675170898438s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 4.935264587402344e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Periods List took 1.6689300537109375e-06s
Believability | Calculation of trust value for English Heritage Periods List took 1.430511474609375e-05s
INFO | --- Analysis for english-heritage-periods-list took 70.15892267227173s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 0.3980073928833008s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.0008084774017333984s
Extra | Recovery of all triples for English Index of Multiple Deprivation Ranking 2010 took 1.3030846118927002s
Performance | Total latancy measurement for English Index of Multiple Deprivation Ranking 2010 took 1.2970130443572998s
Amount of data | Number of triples check for English Index of Multiple Deprivation Ranking 2010 took 0.22080683708190918s
Interoperability | New terms check for English Index of Multiple Deprivation Ranking 2010 took 1.5513300895690918s
Versatility | Languages check for English Index of Multiple Deprivation Ranking 2010 took 0.46712684631347656s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Ranking 2010 took 30.15401291847229s
Security | Check HTTPS for English Index of Multiple Deprivation Ranking 2010 took 0.09108233451843262s
Interpretability | RDF structures check for English Index of Multiple Deprivation Ranking 2010 took 0.36199355125427246s
Versatility | Serialization formats check for English Index of Multiple Deprivation Ranking 2010 took 0.12416338920593262s
Availability | RDF dump link check for English Index of Multiple Deprivation Ranking 2010 took 50.373741149902344s
License | MR license check for English Index of Multiple Deprivation Ranking 2010 took 0.2968900203704834s
License | HR license check for English Index of Multiple Deprivation Ranking 2010 took 30.197576999664307s
Amount of data | Number of property check for English Index of Multiple Deprivation Ranking 2010 took 0.13004636764526367s
Understandability | Number of label check for English Index of Multiple Deprivation Ranking 2010 took 0.29659461975097656s
Understandability | URI regex check for English Index of Multiple Deprivation Ranking 2010 took 0.31712985038757324s
Understandability | Vocabs check for English Index of Multiple Deprivation Ranking 2010 took 0.19614911079406738s
Verifiability | Authors check for English Index of Multiple Deprivation Ranking 2010 took 0.18955421447753906s
Verifiability | Publishers check for English Index of Multiple Deprivation Ranking 2010 took 0.5538632869720459s
Performance | Throughput check for English Index of Multiple Deprivation Ranking 2010 took 11.056073427200317s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Ranking 2010 took 7.009506225585938e-05s
Verifiability | Contribs. check for English Index of Multiple Deprivation Ranking 2010 took 0.19116854667663574s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Ranking 2010 took 0.38082456588745117s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.3028695583343506s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.19478440284729004s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Ranking 2010 took 0.13865280151367188s
Currency | Creation date check for English Index of Multiple Deprivation Ranking 2010 took 0.636420488357544s
Currency | Modification date check for English Index of Multiple Deprivation Ranking 2010 took 0.37505149841308594s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Ranking 2010 took 2.4439077377319336s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Ranking 2010 took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Ranking 2010 took 0.13455629348754883s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.13262510299682617s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.13018512725830078s
Consistency | Disjoint class check for English Index of Multiple Deprivation Ranking 2010 took 0.4399442672729492s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Ranking 2010 took 1.1094684600830078s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Ranking 2010 took 2.070162534713745s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Ranking 2010 took 1.4485774040222168s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.0005326271057128906s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.49627113342285156s
Security | Sign check for English Index of Multiple Deprivation Ranking 2010 took 0.1994001865386963s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 0.3459434509277344s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.02092599868774414s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 4.553794860839844e-05s
Interoperability | Check the re-using of existing vocabs for English Index of Multiple Deprivation Ranking 2010 took 1.6689300537109375e-06s
Believability | Calculation of trust value for English Index of Multiple Deprivation Ranking 2010 took 1.0967254638671875e-05s
INFO | --- Analysis for english-index-of-multiple-deprivation-ranking-2010 took 270.2524719238281s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Score 2010 took 0.18833565711975098s
Availability | VoID file availability check for English Index of Multiple Deprivation Score 2010 took 0.0008728504180908203s
Extra | Recovery of all triples for English Index of Multiple Deprivation Score 2010 took 1.0362675189971924s
Performance | Total latancy measurement for English Index of Multiple Deprivation Score 2010 took 0.8204121589660645s
Amount of data | Number of triples check for English Index of Multiple Deprivation Score 2010 took 0.1888432502746582s
Interoperability | New terms check for English Index of Multiple Deprivation Score 2010 took 1.4810452461242676s
Versatility | Languages check for English Index of Multiple Deprivation Score 2010 took 0.3532066345214844s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Score 2010 took 30.220489740371704s
Security | Check HTTPS for English Index of Multiple Deprivation Score 2010 took 0.18194961547851562s
Interpretability | RDF structures check for English Index of Multiple Deprivation Score 2010 took 0.1951901912689209s
Versatility | Serialization formats check for English Index of Multiple Deprivation Score 2010 took 0.4569976329803467s
Availability | RDF dump link check for English Index of Multiple Deprivation Score 2010 took 45.98559904098511s
License | MR license check for English Index of Multiple Deprivation Score 2010 took 0.19588303565979004s
License | HR license check for English Index of Multiple Deprivation Score 2010 took 30.223350763320923s
Amount of data | Number of property check for English Index of Multiple Deprivation Score 2010 took 0.19638657569885254s
Understandability | Number of label check for English Index of Multiple Deprivation Score 2010 took 0.12824320793151855s
Understandability | URI regex check for English Index of Multiple Deprivation Score 2010 took 0.31284475326538086s
Understandability | Vocabs check for English Index of Multiple Deprivation Score 2010 took 0.12346029281616211s
Verifiability | Authors check for English Index of Multiple Deprivation Score 2010 took 0.19291996955871582s
Verifiability | Publishers check for English Index of Multiple Deprivation Score 2010 took 0.1253194808959961s
Performance | Throughput check for English Index of Multiple Deprivation Score 2010 took 11.77597188949585s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Score 2010 took 5.030632019042969e-05s
Verifiability | Contribs. check for English Index of Multiple Deprivation Score 2010 took 0.183213472366333s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Score 2010 took 0.12605047225952148s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.12601065635681152s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.18820500373840332s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Score 2010 took 0.1290435791015625s
Currency | Creation date check for English Index of Multiple Deprivation Score 2010 took 0.32864904403686523s
Currency | Modification date check for English Index of Multiple Deprivation Score 2010 took 0.41611647605895996s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Score 2010 took 1.7746882438659668s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Score 2010 took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Score 2010 took 0.19522404670715332s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Score 2010 took 0.20038843154907227s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Score 2010 took 0.1934053897857666s
Consistency | Disjoint class check for English Index of Multiple Deprivation Score 2010 took 0.12747597694396973s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Score 2010 took 0.3371772766113281s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Score 2010 took 1.0622038841247559s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Score 2010 took 1.4346990585327148s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.00015664100646972656s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.2101583480834961s
Security | Sign check for English Index of Multiple Deprivation Score 2010 took 0.1918046474456787s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Score 2010 took 0.2792937755584717s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Score 2010 took 0.020791292190551758s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Score 2010 took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Score 2010 took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Score 2010 took 4.1484832763671875e-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 9.5367431640625e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-score-2010 took 255.52777361869812s
Availability | SPARQL endpoint availability check for English WordNet took 4.601478576660156e-05s
Availability | VoID file availability check for English WordNet took 0.0006682872772216797s
Completeness | Calculation of interlinking completeness for English WordNet took 0.2766294479370117s
Reputation | Calculation of the PageRank for English WordNet took 0.02065896987915039s
Interlinking | Calculation of Degree of Connection for English WordNet took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for English WordNet took 0.0007836818695068359s
Interlinking | Calculation of Clustering coefficient for English WordNet took 3.6716461181640625e-05s
Believability | Calculation of trust value for English WordNet took 1.33514404296875e-05s
INFO | --- Analysis for english-wordnet took 3.1782546043395996s
Availability | SPARQL endpoint availability check for Enipedia - Energy Industry Data took 0.08948636054992676s
Availability | VoID file availability check for Enipedia - Energy Industry Data took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for Enipedia - Energy Industry Data took 0.268190860748291s
Reputation | Calculation of the PageRank for Enipedia - Energy Industry Data took 0.022397518157958984s
Interlinking | Calculation of Degree of Connection for Enipedia - Energy Industry Data took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Enipedia - Energy Industry Data took 0.0007824897766113281s
Interlinking | Calculation of Clustering coefficient for Enipedia - Energy Industry Data took 9.489059448242188e-05s
Believability | Calculation of trust value for Enipedia - Energy Industry Data took 1.3828277587890625e-05s
INFO | --- Analysis for enipedia took 2.582224130630493s
Availability | SPARQL endpoint availability check for Enslaved.org took 9.036064147949219e-05s
Availability | VoID file availability check for Enslaved.org took 0.0003948211669921875s
Completeness | Calculation of interlinking completeness for Enslaved.org took 0.26932597160339355s
Reputation | Calculation of the PageRank for Enslaved.org took 0.021283626556396484s
Interlinking | Calculation of Degree of Connection for Enslaved.org took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Enslaved.org took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for Enslaved.org took 3.266334533691406e-05s
Believability | Calculation of trust value for Enslaved.org took 1.239776611328125e-05s
INFO | --- Analysis for enslaved.org took 5.154601335525513s
Availability | SPARQL endpoint availability check for ENTICE Educational Episodes Knowledge Graph took 0.33830833435058594s
Availability | VoID file availability check for ENTICE Educational Episodes Knowledge Graph took 0.0005562305450439453s
Completeness | Calculation of interlinking completeness for ENTICE Educational Episodes Knowledge Graph took 0.2596585750579834s
Reputation | Calculation of the PageRank for ENTICE Educational Episodes Knowledge Graph took 0.020554304122924805s
Interlinking | Calculation of Degree of Connection for ENTICE Educational Episodes Knowledge Graph took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for ENTICE Educational Episodes Knowledge Graph took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for ENTICE Educational Episodes Knowledge Graph took 5.125999450683594e-05s
Believability | Calculation of trust value for ENTICE Educational Episodes Knowledge Graph took 1.4781951904296875e-05s
INFO | --- Analysis for entice-graph took 3.0241055488586426s
Availability | SPARQL endpoint availability check for Entrez Gene took 4.9114227294921875e-05s
Availability | VoID file availability check for Entrez Gene took 0.0009057521820068359s
Completeness | Calculation of interlinking completeness for Entrez Gene took 0.27362561225891113s
Reputation | Calculation of the PageRank for Entrez Gene took 0.021070480346679688s
Interlinking | Calculation of Degree of Connection for Entrez Gene took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Entrez Gene took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for Entrez Gene took 4.38690185546875e-05s
Believability | Calculation of trust value for Entrez Gene took 1.4781951904296875e-05s
INFO | --- Analysis for entrez_gene took 49.034483909606934s
Availability | SPARQL endpoint availability check for Environment Agency Bathing Water Quality took 0.9183192253112793s
Availability | VoID file availability check for Environment Agency Bathing Water Quality took 0.000682830810546875s
Completeness | Calculation of interlinking completeness for Environment Agency Bathing Water Quality took 0.269669771194458s
Reputation | Calculation of the PageRank for Environment Agency Bathing Water Quality took 0.020977020263671875s
Interlinking | Calculation of Degree of Connection for Environment Agency Bathing Water Quality took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Environment Agency Bathing Water Quality took 0.0007908344268798828s
Interlinking | Calculation of Clustering coefficient for Environment Agency Bathing Water Quality took 5.245208740234375e-05s
Believability | Calculation of trust value for Environment Agency Bathing Water Quality took 7.3909759521484375e-06s
INFO | --- Analysis for environment-agency-bathing-water-quality took 10.673248767852783s
Availability | SPARQL endpoint availability check for environment.data.gov.uk took 0.27281951904296875s
Availability | VoID file availability check for environment.data.gov.uk took 0.0006747245788574219s
Completeness | Calculation of interlinking completeness for environment.data.gov.uk took 0.2817683219909668s
Reputation | Calculation of the PageRank for environment.data.gov.uk took 0.02052021026611328s
Interlinking | Calculation of Degree of Connection for environment.data.gov.uk took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for environment.data.gov.uk took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for environment.data.gov.uk took 5.030632019042969e-05s
Believability | Calculation of trust value for environment.data.gov.uk took 1.1205673217773438e-05s
INFO | --- Analysis for environment-data-gov-uk took 8.904540061950684s
Availability | SPARQL endpoint availability check for EARTh took 271.1486864089966s
Availability | VoID file availability check for EARTh took 0.0007672309875488281s
Completeness | Calculation of interlinking completeness for EARTh took 0.2711355686187744s
Reputation | Calculation of the PageRank for EARTh took 0.021169185638427734s
Interlinking | Calculation of Degree of Connection for EARTh took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for EARTh took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for EARTh took 0.00011396408081054688s
Believability | Calculation of trust value for EARTh took 1.4066696166992188e-05s
INFO | --- Analysis for environmental-applications-reference-thesaurus took 566.766523361206s
Availability | SPARQL endpoint availability check for Micka (EO metadata) @PSNC took 0.4760005474090576s
Availability | VoID file availability check for Micka (EO metadata) @PSNC took 0.0005447864532470703s
Extra | Recovery of all triples for Micka (EO metadata) @PSNC took 121.50682163238525s
Performance | Total latancy measurement for Micka (EO metadata) @PSNC took 0.8962123394012451s
Amount of data | Number of triples check for Micka (EO metadata) @PSNC took 9.248778581619263s
Interoperability | New terms check for Micka (EO metadata) @PSNC took 14.263396263122559s
Versatility | Languages check for Micka (EO metadata) @PSNC took 300.22495102882385s
Interpretability | Number of blank nodes check for Micka (EO metadata) @PSNC took 2.1658928394317627s
Interpretability | RDF structures check for Micka (EO metadata) @PSNC took 0.31880736351013184s
Versatility | Serialization formats check for Micka (EO metadata) @PSNC took 9.16654348373413s
Availability | RDF dump link check for Micka (EO metadata) @PSNC took 0.2877960205078125s
License | MR license check for Micka (EO metadata) @PSNC took 0.6209747791290283s
License | HR license check for Micka (EO metadata) @PSNC took 300.1957628726959s
Amount of data | Number of property check for Micka (EO metadata) @PSNC took 0.19284749031066895s
Understandability | Number of label check for Micka (EO metadata) @PSNC took 3.2344698905944824s
Understandability | URI regex check for Micka (EO metadata) @PSNC took 1.132204532623291s
Understandability | Vocabs check for Micka (EO metadata) @PSNC took 0.5734097957611084s
Verifiability | Authors check for Micka (EO metadata) @PSNC took 0.1873798370361328s
Verifiability | Publishers check for Micka (EO metadata) @PSNC took 0.23312854766845703s
Performance | Throughput check for Micka (EO metadata) @PSNC took 10.838778018951416s
Amount of data | Check the number of entities for Micka (EO metadata) @PSNC took 7.62939453125e-05s
Verifiability | Contribs. check for Micka (EO metadata) @PSNC took 0.1861107349395752s
Interlinking | sameAs chians check for Micka (EO metadata) @PSNC took 0.18797731399536133s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.4719734191894531s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.4735758304595947s
Timeliness | dataset update frequency check for Micka (EO metadata) @PSNC took 5.597182989120483s
Currency | Creation date check for Micka (EO metadata) @PSNC took 0.44617700576782227s
Currency | Modification date check for Micka (EO metadata) @PSNC took 0.22310519218444824s
Rep.Conc. | URIs length for Micka (EO metadata) @PSNC took 154.05357766151428s
Interoperability | New vocabularies check for Micka (EO metadata) @PSNC took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for Micka (EO metadata) @PSNC took 0.18437743186950684s
Accuracy | Check Functional Property for Micka (EO metadata) @PSNC took 0.3991422653198242s
Accuracy | Check Inverse Functional Property for Micka (EO metadata) @PSNC took 0.28791165351867676s
Accuracy | Check Empty annotation labels for Micka (EO metadata) @PSNC took 28.830994367599487s
Accuracy | Check White space in annotation for Micka (EO metadata) @PSNC took 2.7037200927734375s
Accuracy | Check Datatype consistency for Micka (EO metadata) @PSNC took 2.761974334716797s
Consistency | Disjoint class check for Micka (EO metadata) @PSNC took 0.18451547622680664s
Consistency | Check Misplaced properties for Micka (EO metadata) @PSNC took 87.10961961746216s
Consistency | Misplaced classes for Micka (EO metadata) @PSNC took 8.56980013847351s
Consistency | Check Ontology hijacking for Micka (EO metadata) @PSNC took 37.318761587142944s
Consistency | Check Invalid usage of undefined classes for Micka (EO metadata) @PSNC took 1.4123942852020264s
Consistency | Check Invalid usage of undefined properties for Micka (EO metadata) @PSNC took 87.22344136238098s
Conciseness | Check Extensional conciseness for Micka (EO metadata) @PSNC took 2.776484251022339s
Conciseness | Check Intensional conciseness for Micka (EO metadata) @PSNC took 0.5027740001678467s
Security | Sign check for Micka (EO metadata) @PSNC took 1.1742286682128906s
Availability | Check URIs Dereferenciability for Micka (EO metadata) @PSNC took 8.951529026031494s
Completeness | Calculation of interlinking completeness for Micka (EO metadata) @PSNC took 0.4770967960357666s
Reputation | Calculation of the PageRank for Micka (EO metadata) @PSNC took 0.02720046043395996s
Interlinking | Calculation of Degree of Connection for Micka (EO metadata) @PSNC took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Micka (EO metadata) @PSNC took 0.0007872581481933594s
Interlinking | Calculation of Clustering coefficient for Micka (EO metadata) @PSNC took 4.1961669921875e-05s
Interoperability | Check the re-using of existing vocabs for Micka (EO metadata) @PSNC took 5.9604644775390625e-06s
Believability | Calculation of trust value for Micka (EO metadata) @PSNC took 1.430511474609375e-05s
INFO | --- Analysis for EO_metadata took 2261.8249549865723s
Availability | SPARQL endpoint availability check for Earth Observation Knowledge Packages took 9.870529174804688e-05s
Availability | VoID file availability check for Earth Observation Knowledge Packages took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for Earth Observation Knowledge Packages took 0.2907578945159912s
Reputation | Calculation of the PageRank for Earth Observation Knowledge Packages took 0.020957231521606445s
Interlinking | Calculation of Degree of Connection for Earth Observation Knowledge Packages took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Earth Observation Knowledge Packages took 0.0007910728454589844s
Interlinking | Calculation of Clustering coefficient for Earth Observation Knowledge Packages took 3.62396240234375e-05s
Believability | Calculation of trust value for Earth Observation Knowledge Packages took 1.4543533325195312e-05s
INFO | --- Analysis for EOKP-Datasets took 3.130185604095459s
Availability | SPARQL endpoint availability check for EPA-CDR took 9.226799011230469e-05s
Availability | VoID file availability check for EPA-CDR took 0.000736236572265625s
Completeness | Calculation of interlinking completeness for EPA-CDR took 0.2730391025543213s
Reputation | Calculation of the PageRank for EPA-CDR took 0.020844697952270508s
Interlinking | Calculation of Degree of Connection for EPA-CDR took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for EPA-CDR took 0.0009961128234863281s
Interlinking | Calculation of Clustering coefficient for EPA-CDR took 4.863739013671875e-05s
Believability | Calculation of trust value for EPA-CDR took 9.775161743164062e-06s
INFO | --- Analysis for epa-cdr took 6.829185485839844s
Availability | SPARQL endpoint availability check for EPA-FRS took 8.988380432128906e-05s
Availability | VoID file availability check for EPA-FRS took 0.0007758140563964844s
Completeness | Calculation of interlinking completeness for EPA-FRS took 0.27585792541503906s
Reputation | Calculation of the PageRank for EPA-FRS took 0.02091193199157715s
Interlinking | Calculation of Degree of Connection for EPA-FRS took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EPA-FRS took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for EPA-FRS took 7.653236389160156e-05s
Believability | Calculation of trust value for EPA-FRS took 1.049041748046875e-05s
INFO | --- Analysis for epa-frs took 5.9306299686431885s
Availability | SPARQL endpoint availability check for EPA-RCRA took 4.649162292480469e-05s
Availability | VoID file availability check for EPA-RCRA took 0.001371622085571289s
Completeness | Calculation of interlinking completeness for EPA-RCRA took 0.2759127616882324s
Reputation | Calculation of the PageRank for EPA-RCRA took 0.020781278610229492s
Interlinking | Calculation of Degree of Connection for EPA-RCRA took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for EPA-RCRA took 0.0007920265197753906s
Interlinking | Calculation of Clustering coefficient for EPA-RCRA took 4.029273986816406e-05s
Believability | Calculation of trust value for EPA-RCRA took 1.0728836059570312e-05s
INFO | --- Analysis for epa-rcra took 5.906107664108276s
Availability | SPARQL endpoint availability check for EPA-SRS took 8.845329284667969e-05s
Availability | VoID file availability check for EPA-SRS took 0.00074005126953125s
Completeness | Calculation of interlinking completeness for EPA-SRS took 0.27503156661987305s
Reputation | Calculation of the PageRank for EPA-SRS took 0.02104330062866211s
Interlinking | Calculation of Degree of Connection for EPA-SRS took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for EPA-SRS took 0.0007781982421875s
Interlinking | Calculation of Clustering coefficient for EPA-SRS took 0.0001049041748046875s
Believability | Calculation of trust value for EPA-SRS took 1.0013580322265625e-05s
INFO | --- Analysis for epa-srs took 5.992473125457764s
Availability | SPARQL endpoint availability check for EPA-TRI took 4.482269287109375e-05s
Availability | VoID file availability check for EPA-TRI took 0.0007202625274658203s
Completeness | Calculation of interlinking completeness for EPA-TRI took 0.26593732833862305s
Reputation | Calculation of the PageRank for EPA-TRI took 0.022309064865112305s
Interlinking | Calculation of Degree of Connection for EPA-TRI took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for EPA-TRI took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for EPA-TRI took 3.9577484130859375e-05s
Believability | Calculation of trust value for EPA-TRI took 9.775161743164062e-06s
INFO | --- Analysis for epa-tri took 5.924928426742554s
Availability | SPARQL endpoint availability check for ePrints Harvest (RKBExplorer) took 0.03424477577209473s
Availability | VoID file availability check for ePrints Harvest (RKBExplorer) took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for ePrints Harvest (RKBExplorer) took 0.26593589782714844s
Reputation | Calculation of the PageRank for ePrints Harvest (RKBExplorer) took 0.020827293395996094s
Interlinking | Calculation of Degree of Connection for ePrints Harvest (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ePrints Harvest (RKBExplorer) took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for ePrints Harvest (RKBExplorer) took 0.00013136863708496094s
Believability | Calculation of trust value for ePrints Harvest (RKBExplorer) took 1.3589859008789062e-05s
INFO | --- Analysis for eprints-harvest-rkbexplorer took 2.5214860439300537s
Availability | SPARQL endpoint availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.42015790939331055s
Availability | VoID file availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.00048828125s
Completeness | Calculation of interlinking completeness for European Pollutant Release and Transfer Register (E-PRTR) took 0.2782704830169678s
Reputation | Calculation of the PageRank for European Pollutant Release and Transfer Register (E-PRTR) took 0.0214078426361084s
Interlinking | Calculation of Degree of Connection for European Pollutant Release and Transfer Register (E-PRTR) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for European Pollutant Release and Transfer Register (E-PRTR) took 0.0009448528289794922s
Interlinking | Calculation of Clustering coefficient for European Pollutant Release and Transfer Register (E-PRTR) took 0.0001125335693359375s
Believability | Calculation of trust value for European Pollutant Release and Transfer Register (E-PRTR) took 1.4066696166992188e-05s
INFO | --- Analysis for eprtr took 3.869394540786743s
Availability | SPARQL endpoint availability check for Railway Infrastructure KG took 0.4855766296386719s
Availability | VoID file availability check for Railway Infrastructure KG took 0.0007576942443847656s
Extra | Recovery of all triples for Railway Infrastructure KG took 58.096341371536255s
Performance | Total latancy measurement for Railway Infrastructure KG took 1.068274736404419s
Amount of data | Number of triples check for Railway Infrastructure KG took 0.2272653579711914s
Interoperability | New terms check for Railway Infrastructure KG took 1.5719408988952637s
Versatility | Languages check for Railway Infrastructure KG took 85.99664950370789s
Interpretability | Number of blank nodes check for Railway Infrastructure KG took 0.24091672897338867s
Interpretability | RDF structures check for Railway Infrastructure KG took 0.4325098991394043s
Versatility | Serialization formats check for Railway Infrastructure KG took 0.24651789665222168s
Availability | RDF dump link check for Railway Infrastructure KG took 0.20699334144592285s
License | MR license check for Railway Infrastructure KG took 0.29364728927612305s
License | HR license check for Railway Infrastructure KG took 64.87868237495422s
Amount of data | Number of property check for Railway Infrastructure KG took 0.265169620513916s
Understandability | Number of label check for Railway Infrastructure KG took 0.6057114601135254s
Understandability | URI regex check for Railway Infrastructure KG took 0.46596264839172363s
Understandability | Vocabs check for Railway Infrastructure KG took 0.23199224472045898s
Verifiability | Authors check for Railway Infrastructure KG took 0.31325387954711914s
Verifiability | Publishers check for Railway Infrastructure KG took 0.21614933013916016s
Performance | Throughput check for Railway Infrastructure KG took 11.213570356369019s
Verifiability | Contribs. check for Railway Infrastructure KG took 0.2792651653289795s
Interlinking | sameAs chians check for Railway Infrastructure KG took 0.222611665725708s
Interlinking | skos check for Railway Infrastructure KG took 0.21869802474975586s
Interlinking | skos check for Railway Infrastructure KG took 0.26351237297058105s
Timeliness | dataset update frequency check for Railway Infrastructure KG took 0.23657822608947754s
Currency | Creation date check for Railway Infrastructure KG took 0.5242750644683838s
Currency | Modification date check for Railway Infrastructure KG took 0.21291780471801758s
Rep.Conc. | URIs length for Railway Infrastructure KG took 23.351593017578125s
Interoperability | New vocabularies check for Railway Infrastructure KG took 7.106770038604736s
Consistency | Deprecated classes/propertiers check for Railway Infrastructure KG took 0.25554823875427246s
Accuracy | Check Functional Property for Railway Infrastructure KG took 0.22764158248901367s
Accuracy | Check Inverse Functional Property for Railway Infrastructure KG took 0.22215008735656738s
Accuracy | Check Empty annotation labels for Railway Infrastructure KG took 14.260343790054321s
Accuracy | Check White space in annotation for Railway Infrastructure KG took 2.5913619995117188s
Accuracy | Check Datatype consistency for Railway Infrastructure KG took 2.758878469467163s
Consistency | Disjoint class check for Railway Infrastructure KG took 0.24506449699401855s
Consistency | Check Misplaced properties for Railway Infrastructure KG took 1.6933419704437256s
Consistency | Misplaced classes for Railway Infrastructure KG took 8.67687201499939s
Consistency | Check Ontology hijacking for Railway Infrastructure KG took 19.355478525161743s
Consistency | Check Invalid usage of undefined classes for Railway Infrastructure KG took 1.512233018875122s
Consistency | Check Invalid usage of undefined properties for Railway Infrastructure KG took 2.8749730587005615s
Conciseness | Check Extensional conciseness for Railway Infrastructure KG took 3.0102083683013916s
Conciseness | Check Intensional conciseness for Railway Infrastructure KG took 0.3758392333984375s
Security | Sign check for Railway Infrastructure KG took 0.5548567771911621s
Availability | Check URIs Dereferenciability for Railway Infrastructure KG took 2376.6036903858185s
Completeness | Calculation of interlinking completeness for Railway Infrastructure KG took 0.506763219833374s
Reputation | Calculation of the PageRank for Railway Infrastructure KG took 0.022260189056396484s
Interlinking | Calculation of Degree of Connection for Railway Infrastructure KG took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for Railway Infrastructure KG took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Railway Infrastructure KG took 5.984306335449219e-05s
Interoperability | Check the re-using of existing vocabs for Railway Infrastructure KG took 6.437130928039551s
Believability | Calculation of trust value for Railway Infrastructure KG took 1.5497207641601562e-05s
INFO | --- Analysis for ERAKG took 2803.189415693283s
Availability | SPARQL endpoint availability check for reg took 9.131431579589844e-05s
Availability | VoID file availability check for reg took 0.0005290508270263672s
Completeness | Calculation of interlinking completeness for reg took 0.3025338649749756s
Reputation | Calculation of the PageRank for reg took 0.020760059356689453s
Interlinking | Calculation of Degree of Connection for reg took 1.52587890625e-05s
Interlinking | Calculation of Centrality for reg took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for reg took 1.3828277587890625e-05s
Believability | Calculation of trust value for reg took 1.239776611328125e-05s
INFO | --- Analysis for erg took 2.7633118629455566s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.28273606300354004s
Availability | VoID file availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Kingdom of Spain took 0.30329179763793945s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Kingdom of Spain took 0.022615909576416016s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Kingdom of Spain took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Kingdom of Spain took 0.0007932186126708984s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Kingdom of Spain took 3.5762786865234375e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Kingdom of Spain took 1.239776611328125e-05s
INFO | --- Analysis for es-msssi-drug-prices took 3.3661978244781494s
Availability | SPARQL endpoint availability check for ESD Standards: Controlled lists for the UK public sector took 0.00011515617370605469s
Availability | VoID file availability check for ESD Standards: Controlled lists for the UK public sector took 0.000990152359008789s
Completeness | Calculation of interlinking completeness for ESD Standards: Controlled lists for the UK public sector took 0.3134641647338867s
Reputation | Calculation of the PageRank for ESD Standards: Controlled lists for the UK public sector took 0.020644187927246094s
Interlinking | Calculation of Degree of Connection for ESD Standards: Controlled lists for the UK public sector took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for ESD Standards: Controlled lists for the UK public sector took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for ESD Standards: Controlled lists for the UK public sector took 9.393692016601562e-05s
Believability | Calculation of trust value for ESD Standards: Controlled lists for the UK public sector took 1.049041748046875e-05s
INFO | --- Analysis for esd-standards took 4.560087442398071s
Availability | SPARQL endpoint availability check for ESD-Toolkit took 0.00012063980102539062s
Availability | VoID file availability check for ESD-Toolkit took 0.0007388591766357422s
Completeness | Calculation of interlinking completeness for ESD-Toolkit took 0.2760438919067383s
Reputation | Calculation of the PageRank for ESD-Toolkit took 0.020565032958984375s
Interlinking | Calculation of Degree of Connection for ESD-Toolkit took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for ESD-Toolkit took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for ESD-Toolkit took 7.605552673339844e-05s
Believability | Calculation of trust value for ESD-Toolkit took 9.5367431640625e-06s
INFO | --- Analysis for esd-toolkit took 3.472337245941162s
Availability | SPARQL endpoint availability check for Dataset Esis took 9.274482727050781e-05s
Availability | VoID file availability check for Dataset Esis took 0.0005674362182617188s
Completeness | Calculation of interlinking completeness for Dataset Esis took 0.3054084777832031s
Reputation | Calculation of the PageRank for Dataset Esis took 0.0207672119140625s
Interlinking | Calculation of Degree of Connection for Dataset Esis took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Dataset Esis took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for Dataset Esis took 3.266334533691406e-05s
Believability | Calculation of trust value for Dataset Esis took 1.4066696166992188e-05s
INFO | --- Analysis for esislearning took 3.170944929122925s
Availability | SPARQL endpoint availability check for The European Science Vocabulary (EuroSciVoc) took 9.512901306152344e-05s
Availability | VoID file availability check for The European Science Vocabulary (EuroSciVoc) took 0.0007445812225341797s
Completeness | Calculation of interlinking completeness for The European Science Vocabulary (EuroSciVoc) took 0.2801666259765625s
Reputation | Calculation of the PageRank for The European Science Vocabulary (EuroSciVoc) took 0.021510839462280273s
Interlinking | Calculation of Degree of Connection for The European Science Vocabulary (EuroSciVoc) took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for The European Science Vocabulary (EuroSciVoc) took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for The European Science Vocabulary (EuroSciVoc) took 3.457069396972656e-05s
Believability | Calculation of trust value for The European Science Vocabulary (EuroSciVoc) took 1.4066696166992188e-05s
INFO | --- Analysis for ESV took 4.3189427852630615s
Availability | SPARQL endpoint availability check for Etymological Dictionary of Latin in LiLa took 0.6389613151550293s
Availability | VoID file availability check for Etymological Dictionary of Latin in LiLa took 0.0006763935089111328s
Completeness | Calculation of interlinking completeness for Etymological Dictionary of Latin in LiLa took 0.3354320526123047s
Reputation | Calculation of the PageRank for Etymological Dictionary of Latin in LiLa took 0.020720481872558594s
Interlinking | Calculation of Degree of Connection for Etymological Dictionary of Latin in LiLa took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Etymological Dictionary of Latin in LiLa took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Etymological Dictionary of Latin in LiLa took 3.933906555175781e-05s
Believability | Calculation of trust value for Etymological Dictionary of Latin in LiLa took 1.4066696166992188e-05s
INFO | --- Analysis for EtymologicalDictionaryofLatin took 4.730316638946533s
Availability | SPARQL endpoint availability check for EU Agencies and decentralized bodies (Agencies) took 8.086649179458618s
Availability | VoID file availability check for EU Agencies and decentralized bodies (Agencies) took 0.0007343292236328125s
Completeness | Calculation of interlinking completeness for EU Agencies and decentralized bodies (Agencies) took 0.2802772521972656s
Reputation | Calculation of the PageRank for EU Agencies and decentralized bodies (Agencies) took 0.020764827728271484s
Interlinking | Calculation of Degree of Connection for EU Agencies and decentralized bodies (Agencies) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for EU Agencies and decentralized bodies (Agencies) took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for EU Agencies and decentralized bodies (Agencies) took 7.939338684082031e-05s
Believability | Calculation of trust value for EU Agencies and decentralized bodies (Agencies) took 1.430511474609375e-05s
INFO | --- Analysis for eu-agencies-bodies took 22.16204285621643s
Availability | SPARQL endpoint availability check for Institutions and Bodies of the European Union took 4.38690185546875e-05s
Availability | VoID file availability check for Institutions and Bodies of the European Union took 0.0007202625274658203s
Completeness | Calculation of interlinking completeness for Institutions and Bodies of the European Union took 0.3197286128997803s
Reputation | Calculation of the PageRank for Institutions and Bodies of the European Union took 0.020743131637573242s
Interlinking | Calculation of Degree of Connection for Institutions and Bodies of the European Union took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Institutions and Bodies of the European Union took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for Institutions and Bodies of the European Union took 7.653236389160156e-05s
Believability | Calculation of trust value for Institutions and Bodies of the European Union took 3.695487976074219e-05s
INFO | --- Analysis for eu-institutions took 8.820944786071777s
Availability | SPARQL endpoint availability check for EU Parliament Media Library took 1.5626351833343506s
Availability | VoID file availability check for EU Parliament Media Library took 0.0007565021514892578s
Completeness | Calculation of interlinking completeness for EU Parliament Media Library took 0.2767455577850342s
Reputation | Calculation of the PageRank for EU Parliament Media Library took 0.020933866500854492s
Interlinking | Calculation of Degree of Connection for EU Parliament Media Library took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for EU Parliament Media Library took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for EU Parliament Media Library took 4.315376281738281e-05s
Believability | Calculation of trust value for EU Parliament Media Library took 8.821487426757812e-06s
INFO | --- Analysis for eu-parliament-media took 11.20863127708435s
Availability | SPARQL endpoint availability check for EU Who Is Who took 1.3666367530822754s
Availability | VoID file availability check for EU Who Is Who took 0.0006046295166015625s
Completeness | Calculation of interlinking completeness for EU Who Is Who took 0.311185359954834s
Reputation | Calculation of the PageRank for EU Who Is Who took 0.02069091796875s
Interlinking | Calculation of Degree of Connection for EU Who Is Who took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EU Who Is Who took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for EU Who Is Who took 3.981590270996094e-05s
Believability | Calculation of trust value for EU Who Is Who took 8.344650268554688e-06s
INFO | --- Analysis for eu-who-is-who took 15.815455675125122s
Availability | SPARQL endpoint availability check for EUMIDA as Linked Data took 1.2529690265655518s
Availability | VoID file availability check for EUMIDA as Linked Data took 0.0005915164947509766s
Completeness | Calculation of interlinking completeness for EUMIDA as Linked Data took 0.27989959716796875s
Reputation | Calculation of the PageRank for EUMIDA as Linked Data took 0.020648479461669922s
Interlinking | Calculation of Degree of Connection for EUMIDA as Linked Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for EUMIDA as Linked Data took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for EUMIDA as Linked Data took 4.4345855712890625e-05s
Believability | Calculation of trust value for EUMIDA as Linked Data took 8.58306884765625e-06s
INFO | --- Analysis for eumida-linked-data took 11.953501462936401s
Availability | SPARQL endpoint availability check for European Nature Information System took 0.3307216167449951s
Availability | VoID file availability check for European Nature Information System took 0.0005867481231689453s
Completeness | Calculation of interlinking completeness for European Nature Information System took 0.30089902877807617s
Reputation | Calculation of the PageRank for European Nature Information System took 0.021139860153198242s
Interlinking | Calculation of Degree of Connection for European Nature Information System took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for European Nature Information System took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for European Nature Information System took 0.00011110305786132812s
Believability | Calculation of trust value for European Nature Information System took 1.0251998901367188e-05s
INFO | --- Analysis for eunis took 4.435631275177002s
Availability | SPARQL endpoint availability check for EUR-Lex as Linked Data took 7.1039252281188965s
Availability | VoID file availability check for EUR-Lex as Linked Data took 0.0006582736968994141s
Completeness | Calculation of interlinking completeness for EUR-Lex as Linked Data took 0.27854061126708984s
Reputation | Calculation of the PageRank for EUR-Lex as Linked Data took 0.022717714309692383s
Interlinking | Calculation of Degree of Connection for EUR-Lex as Linked Data took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for EUR-Lex as Linked Data took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for EUR-Lex as Linked Data took 7.915496826171875e-05s
Believability | Calculation of trust value for EUR-Lex as Linked Data took 1.5020370483398438e-05s
INFO | --- Analysis for eur-lex-rdf took 20.155991315841675s
Availability | SPARQL endpoint availability check for Standard Eurobarometer took 1.593412160873413s
Availability | VoID file availability check for Standard Eurobarometer took 0.0007503032684326172s
Completeness | Calculation of interlinking completeness for Standard Eurobarometer took 0.2951798439025879s
Reputation | Calculation of the PageRank for Standard Eurobarometer took 0.02108001708984375s
Interlinking | Calculation of Degree of Connection for Standard Eurobarometer took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Standard Eurobarometer took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for Standard Eurobarometer took 4.792213439941406e-05s
Believability | Calculation of trust value for Standard Eurobarometer took 1.049041748046875e-05s
INFO | --- Analysis for eurobarometer-standard took 12.846108436584473s
Availability | SPARQL endpoint availability check for European Election Results took 1.339331865310669s
Availability | VoID file availability check for European Election Results took 0.0006990432739257812s
Completeness | Calculation of interlinking completeness for European Election Results took 0.30801844596862793s
Reputation | Calculation of the PageRank for European Election Results took 0.023740768432617188s
Interlinking | Calculation of Degree of Connection for European Election Results took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for European Election Results took 0.0014688968658447266s
Interlinking | Calculation of Clustering coefficient for European Election Results took 5.7220458984375e-05s
Believability | Calculation of trust value for European Election Results took 1.0251998901367188e-05s
INFO | --- Analysis for european-election-results took 15.782728910446167s
Availability | SPARQL endpoint availability check for EPO patents took 0.4092717170715332s
Availability | VoID file availability check for EPO patents took 0.0006220340728759766s
Extra | Recovery of all triples for EPO patents took 24.422123908996582s
Performance | Total latancy measurement for EPO patents took 0.9000518321990967s
Amount of data | Number of triples check for EPO patents took 90.17995357513428s
Versatility | Languages check for EPO patents took 100.2496919631958s
Interpretability | Number of blank nodes check for EPO patents took 90.34645509719849s
Interpretability | RDF structures check for EPO patents took 0.2730393409729004s
Versatility | Serialization formats check for EPO patents took 0.22228169441223145s
Availability | RDF dump link check for EPO patents took 0.22040176391601562s
License | MR license check for EPO patents took 0.2592628002166748s
License | HR license check for EPO patents took 90.31460928916931s
Amount of data | Number of property check for EPO patents took 0.2540290355682373s
Understandability | Number of label check for EPO patents took 90.26732397079468s
Understandability | URI regex check for EPO patents took 0.488936185836792s
Understandability | Vocabs check for EPO patents took 0.22288107872009277s
Verifiability | Authors check for EPO patents took 0.23841071128845215s
Verifiability | Publishers check for EPO patents took 0.2625272274017334s
Performance | Throughput check for EPO patents took 10.830752611160278s
Amount of data | Check the number of entities for EPO patents took 5.8650970458984375e-05s
Verifiability | Contribs. check for EPO patents took 0.19713759422302246s
Interlinking | sameAs chians check for EPO patents took 0.22698616981506348s
Interlinking | skos check for EPO patents took 0.23850131034851074s
Interlinking | skos check for EPO patents took 0.16814303398132324s
Timeliness | dataset update frequency check for EPO patents took 0.2206275463104248s
Currency | Creation date check for EPO patents took 0.3927724361419678s
Currency | Modification date check for EPO patents took 0.41782045364379883s
Rep.Conc. | URIs length for EPO patents took 133.71184301376343s
Interoperability | New vocabularies check for EPO patents took 4.76837158203125e-06s
Consistency | Deprecated classes/propertiers check for EPO patents took 0.2391958236694336s
Accuracy | Check Empty annotation labels for EPO patents took 21.082860946655273s
Accuracy | Check White space in annotation for EPO patents took 3.026845932006836s
Accuracy | Check Datatype consistency for EPO patents took 5.0880231857299805s
Consistency | Disjoint class check for EPO patents took 0.1812455654144287s
Consistency | Check Misplaced properties for EPO patents took 100.35839581489563s
Consistency | Check Ontology hijacking for EPO patents took 23.068658590316772s
Consistency | Check Invalid usage of undefined classes for EPO patents took 1.6369538307189941s
Consistency | Check Invalid usage of undefined properties for EPO patents took 101.62501263618469s
Conciseness | Check Extensional conciseness for EPO patents took 2.8721959590911865s
Conciseness | Check Intensional conciseness for EPO patents took 0.3740878105163574s
Security | Sign check for EPO patents took 0.2567722797393799s
Availability | Check URIs Dereferenciability for EPO patents took 1.581648588180542s
Completeness | Calculation of interlinking completeness for EPO patents took 0.7672467231750488s
Reputation | Calculation of the PageRank for EPO patents took 0.021379470825195312s
Interlinking | Calculation of Degree of Connection for EPO patents took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for EPO patents took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for EPO patents took 5.030632019042969e-05s
Interoperability | Check the re-using of existing vocabs for EPO patents took 2.1457672119140625e-06s
Believability | Calculation of trust value for EPO patents took 1.3113021850585938e-05s
INFO | --- Analysis for European_Patent_Information took 1194.034453868866s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data V1.0 took 4.506111145019531e-05s
Availability | VoID file availability check for Europeana Linked Open Data V1.0 took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data V1.0 took 0.3755662441253662s
Reputation | Calculation of the PageRank for Europeana Linked Open Data V1.0 took 0.02111196517944336s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data V1.0 took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data V1.0 took 0.0008084774017333984s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data V1.0 took 0.00011086463928222656s
Believability | Calculation of trust value for Europeana Linked Open Data V1.0 took 1.4066696166992188e-05s
INFO | --- Analysis for europeana-lod-v1 took 8.175193309783936s
Availability | SPARQL endpoint availability check for Europeana SPARQL took 0.3752009868621826s
Availability | VoID file availability check for Europeana SPARQL took 0.00040459632873535156s
Completeness | Calculation of interlinking completeness for Europeana SPARQL took 0.3113534450531006s
Reputation | Calculation of the PageRank for Europeana SPARQL took 0.02065300941467285s
Interlinking | Calculation of Degree of Connection for Europeana SPARQL took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Europeana SPARQL took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Europeana SPARQL took 5.125999450683594e-05s
Believability | Calculation of trust value for Europeana SPARQL took 9.775161743164062e-06s
INFO | --- Analysis for europeana-sparql took 6.580478668212891s
Availability | SPARQL endpoint availability check for EuroSentiment took 0.08777856826782227s
Availability | VoID file availability check for EuroSentiment took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for EuroSentiment took 0.3420381546020508s
Reputation | Calculation of the PageRank for EuroSentiment took 0.020820140838623047s
Interlinking | Calculation of Degree of Connection for EuroSentiment took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for EuroSentiment took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for EuroSentiment took 4.792213439941406e-05s
Believability | Calculation of trust value for EuroSentiment took 1.049041748046875e-05s
INFO | --- Analysis for eurosentiment took 3.4419233798980713s
Availability | SPARQL endpoint availability check for Eurostat RDF datasets took 7.152557373046875e-05s
Availability | VoID file availability check for Eurostat RDF datasets took 0.0007431507110595703s
Completeness | Calculation of interlinking completeness for Eurostat RDF datasets took 0.3314194679260254s
Reputation | Calculation of the PageRank for Eurostat RDF datasets took 0.020725727081298828s
Interlinking | Calculation of Degree of Connection for Eurostat RDF datasets took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Eurostat RDF datasets took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Eurostat RDF datasets took 8.678436279296875e-05s
Believability | Calculation of trust value for Eurostat RDF datasets took 1.049041748046875e-05s
INFO | --- Analysis for eurostat-rdf took 12.721558094024658s
Availability | SPARQL endpoint availability check for EuroVoc took 0.19063019752502441s
Availability | VoID file availability check for EuroVoc took 0.00043654441833496094s
Extra | Recovery of all triples for EuroVoc took 195.1993007659912s
Performance | Total latancy measurement for EuroVoc took 0.5814523696899414s
Amount of data | Number of triples check for EuroVoc took 42.187416791915894s
Interoperability | New terms check for EuroVoc took 54.87946057319641s
Versatility | Languages check for EuroVoc took 300.093416929245s
Interpretability | Number of blank nodes check for EuroVoc took 59.308295011520386s
Security | Check HTTPS for EuroVoc took 0.3861849308013916s
Interpretability | RDF structures check for EuroVoc took 0.5309326648712158s
Versatility | Serialization formats check for EuroVoc took 4.16515851020813s
Availability | RDF dump link check for EuroVoc took 0.23415732383728027s
License | MR license check for EuroVoc took 0.36730051040649414s
License | HR license check for EuroVoc took 300.10491609573364s
Amount of data | Number of property check for EuroVoc took 0.21857833862304688s
Understandability | Number of label check for EuroVoc took 1.956294059753418s
Understandability | URI regex check for EuroVoc took 0.38631701469421387s
Understandability | Vocabs check for EuroVoc took 0.11977124214172363s
Verifiability | Authors check for EuroVoc took 0.18689274787902832s
Verifiability | Publishers check for EuroVoc took 0.23679780960083008s
Performance | Throughput check for EuroVoc took 10.66651177406311s
Amount of data | Check the number of entities for EuroVoc took 3.1948089599609375e-05s
Verifiability | Contribs. check for EuroVoc took 0.2358109951019287s
Interlinking | sameAs chians check for EuroVoc took 7.13043475151062s
Interlinking | skos check for EuroVoc took 0.335463285446167s
Interlinking | skos check for EuroVoc took 0.32834792137145996s
Timeliness | dataset update frequency check for EuroVoc took 0.4389963150024414s
Currency | Creation date check for EuroVoc took 0.5509521961212158s
Currency | Modification date check for EuroVoc took 0.7605211734771729s
Rep.Conc. | URIs length for EuroVoc took 415.32811164855957s
Interoperability | New vocabularies check for EuroVoc took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for EuroVoc took 0.1727445125579834s
Accuracy | Check Functional Property for EuroVoc took 0.1651291847229004s
Accuracy | Check Inverse Functional Property for EuroVoc took 0.18499970436096191s
Accuracy | Check Empty annotation labels for EuroVoc took 41.12112545967102s
Accuracy | Check White space in annotation for EuroVoc took 3.072080135345459s
Accuracy | Check Datatype consistency for EuroVoc took 2.7692384719848633s
Consistency | Disjoint class check for EuroVoc took 0.14806890487670898s
Consistency | Check Misplaced properties for EuroVoc took 300.35522270202637s
Consistency | Misplaced classes for EuroVoc took 8.860632419586182s
Consistency | Check Ontology hijacking for EuroVoc took 35.39337944984436s
Consistency | Check Invalid usage of undefined classes for EuroVoc took 1.758495807647705s
Consistency | Check Invalid usage of undefined properties for EuroVoc took 301.48520612716675s
Conciseness | Check Extensional conciseness for EuroVoc took 3.1210508346557617s
Conciseness | Check Intensional conciseness for EuroVoc took 0.414473295211792s
Security | Sign check for EuroVoc took 0.12608671188354492s
Availability | Check URIs Dereferenciability for EuroVoc took 11.27801251411438s
Completeness | Calculation of interlinking completeness for EuroVoc took 0.7755656242370605s
Reputation | Calculation of the PageRank for EuroVoc took 0.021305322647094727s
Interlinking | Calculation of Degree of Connection for EuroVoc took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for EuroVoc took 0.0007855892181396484s
Interlinking | Calculation of Clustering coefficient for EuroVoc took 9.036064147949219e-05s
Interoperability | Check the re-using of existing vocabs for EuroVoc took 1.430511474609375e-06s
Believability | Calculation of trust value for EuroVoc took 1.5020370483398438e-05s
INFO | --- Analysis for eurovoc took 14621.999021530151s
Availability | SPARQL endpoint availability check for Farmacias en Euskadi took 4.506111145019531e-05s
Availability | VoID file availability check for Farmacias en Euskadi took 0.0006880760192871094s
Completeness | Calculation of interlinking completeness for Farmacias en Euskadi took 0.3234550952911377s
Reputation | Calculation of the PageRank for Farmacias en Euskadi took 0.02284550666809082s
Interlinking | Calculation of Degree of Connection for Farmacias en Euskadi took 8.606910705566406e-05s
Interlinking | Calculation of Centrality for Farmacias en Euskadi took 0.0008130073547363281s
Interlinking | Calculation of Clustering coefficient for Farmacias en Euskadi took 5.4836273193359375e-05s
Believability | Calculation of trust value for Farmacias en Euskadi took 9.775161743164062e-06s
INFO | --- Analysis for euskadi-farmacias took 5.4771459102630615s
Availability | SPARQL endpoint availability check for Research outputs of Eastern University Sri Lanka took 0.691967248916626s
Availability | VoID file availability check for Research outputs of Eastern University Sri Lanka took 0.0006861686706542969s
Completeness | Calculation of interlinking completeness for Research outputs of Eastern University Sri Lanka took 0.30617856979370117s
Reputation | Calculation of the PageRank for Research outputs of Eastern University Sri Lanka took 0.020626068115234375s
Interlinking | Calculation of Degree of Connection for Research outputs of Eastern University Sri Lanka took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Research outputs of Eastern University Sri Lanka took 0.0007796287536621094s
Interlinking | Calculation of Clustering coefficient for Research outputs of Eastern University Sri Lanka took 3.600120544433594e-05s
Believability | Calculation of trust value for Research outputs of Eastern University Sri Lanka took 1.3589859008789062e-05s
INFO | --- Analysis for EUSL-Research-Data-Sri_Lanka took 4.537979602813721s
Availability | SPARQL endpoint availability check for Edinburgh University Theatre Company Productions took 0.5473902225494385s
Availability | VoID file availability check for Edinburgh University Theatre Company Productions took 0.0006718635559082031s
Completeness | Calculation of interlinking completeness for Edinburgh University Theatre Company Productions took 0.42409253120422363s
Reputation | Calculation of the PageRank for Edinburgh University Theatre Company Productions took 0.020879268646240234s
Interlinking | Calculation of Degree of Connection for Edinburgh University Theatre Company Productions took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Edinburgh University Theatre Company Productions took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Edinburgh University Theatre Company Productions took 7.700920104980469e-05s
Believability | Calculation of trust value for Edinburgh University Theatre Company Productions took 9.775161743164062e-06s
INFO | --- Analysis for eutc-productions took 10.06297516822815s
Availability | SPARQL endpoint availability check for EventMedia took 0.37499260902404785s
Availability | VoID file availability check for EventMedia took 0.0004329681396484375s
Completeness | Calculation of interlinking completeness for EventMedia took 0.27216148376464844s
Reputation | Calculation of the PageRank for EventMedia took 0.020783662796020508s
Interlinking | Calculation of Degree of Connection for EventMedia took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for EventMedia took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for EventMedia took 0.0001125335693359375s
Believability | Calculation of trust value for EventMedia took 1.0251998901367188e-05s
INFO | --- Analysis for event-media took 19.43231225013733s
Availability | SPARQL endpoint availability check for EventKG took 6.437301635742188e-05s
Availability | VoID file availability check for EventKG took 0.0007259845733642578s
Completeness | Calculation of interlinking completeness for EventKG took 0.32393479347229004s
Reputation | Calculation of the PageRank for EventKG took 0.020592927932739258s
Interlinking | Calculation of Degree of Connection for EventKG took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EventKG took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for EventKG took 8.845329284667969e-05s
Believability | Calculation of trust value for EventKG took 1.0728836059570312e-05s
INFO | --- Analysis for eventkg took 4.962427139282227s
Availability | SPARQL endpoint availability check for Eventseer took 8.519158363342285s
Availability | VoID file availability check for Eventseer took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for Eventseer took 0.30667543411254883s
Reputation | Calculation of the PageRank for Eventseer took 0.0221097469329834s
Interlinking | Calculation of Degree of Connection for Eventseer took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Eventseer took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Eventseer took 5.555152893066406e-05s
Believability | Calculation of trust value for Eventseer took 1.52587890625e-05s
INFO | --- Analysis for eventseer took 11.217763662338257s
Availability | SPARQL endpoint availability check for Face Link took 8.821487426757812e-05s
Availability | VoID file availability check for Face Link took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for Face Link took 0.28925561904907227s
Reputation | Calculation of the PageRank for Face Link took 0.021694660186767578s
Interlinking | Calculation of Degree of Connection for Face Link took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Face Link took 0.0008237361907958984s
Interlinking | Calculation of Clustering coefficient for Face Link took 4.029273986816406e-05s
Believability | Calculation of trust value for Face Link took 1.5020370483398438e-05s
INFO | --- Analysis for Face_Link took 2.746108055114746s
Availability | SPARQL endpoint availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.48055052757263184s
Availability | VoID file availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0002994537353515625s
Extra | Recovery of all triples for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 113.56926035881042s
Performance | Total latancy measurement for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.9843790531158447s
Amount of data | Number of triples check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 9.482598781585693s
Interoperability | New terms check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 14.044506072998047s
Versatility | Languages check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.2097806930542s
Interpretability | Number of blank nodes check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.1253440380096436s
Interpretability | RDF structures check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.3354189395904541s
Versatility | Serialization formats check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 9.797481536865234s
Availability | RDF dump link check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.37671780586242676s
License | MR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.9253010749816895s
License | HR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.16040420532227s
Amount of data | Number of property check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.2180633544921875s
Understandability | Number of label check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 3.1790571212768555s
Understandability | URI regex check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.2170524597167969s
Understandability | Vocabs check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.6591246128082275s
Verifiability | Authors check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.21558237075805664s
Verifiability | Publishers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.26032185554504395s
Performance | Throughput check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 11.290984630584717s
Amount of data | Check the number of entities for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 7.033348083496094e-05s
Verifiability | Contribs. check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.18578863143920898s
Interlinking | sameAs chians check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.206254243850708s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5245254039764404s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5329544544219971s
Timeliness | dataset update frequency check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 6.756724119186401s
Currency | Creation date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4976787567138672s
Currency | Modification date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.23333740234375s
Rep.Conc. | URIs length for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 154.22816443443298s
Interoperability | New vocabularies check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.2874603271484375e-05s
Consistency | Deprecated classes/propertiers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.20167303085327148s
Accuracy | Check Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4743373394012451s
Accuracy | Check Inverse Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4375452995300293s
Accuracy | Check Empty annotation labels for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 45.29409170150757s
Accuracy | Check White space in annotation for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.691735029220581s
Accuracy | Check Datatype consistency for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.770946741104126s
Consistency | Disjoint class check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.18871569633483887s
Consistency | Check Misplaced properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 86.60680627822876s
Consistency | Misplaced classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.432071208953857s
Consistency | Check Ontology hijacking for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 43.691813707351685s
Consistency | Check Invalid usage of undefined classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.4273297786712646s
Consistency | Check Invalid usage of undefined properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 87.72006034851074s
Conciseness | Check Extensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.8471829891204834s
Conciseness | Check Intensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5932867527008057s
Security | Sign check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.5553779602050781s
Availability | Check URIs Dereferenciability for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 9.571441888809204s
Completeness | Calculation of interlinking completeness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5352640151977539s
Reputation | Calculation of the PageRank for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.021350622177124023s
Interlinking | Calculation of Degree of Connection for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0008015632629394531s
Interlinking | Calculation of Clustering coefficient for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 6.318092346191406e-05s
Interoperability | Check the re-using of existing vocabs for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 3.337860107421875e-06s
Believability | Calculation of trust value for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.52587890625e-05s
INFO | --- Analysis for FADN_(2019) took 2305.472423553467s
Availability | SPARQL endpoint availability check for FAMEData took 4.410743713378906e-05s
Availability | VoID file availability check for FAMEData took 0.0006978511810302734s
Completeness | Calculation of interlinking completeness for FAMEData took 0.295900821685791s
Reputation | Calculation of the PageRank for FAMEData took 0.021042346954345703s
Interlinking | Calculation of Degree of Connection for FAMEData took 0.00013399124145507812s
Interlinking | Calculation of Centrality for FAMEData took 0.0016491413116455078s
Interlinking | Calculation of Clustering coefficient for FAMEData took 6.580352783203125e-05s
Believability | Calculation of trust value for FAMEData took 1.1920928955078125e-05s
INFO | --- Analysis for famedata took 6.884065866470337s
Availability | SPARQL endpoint availability check for FAO geopolitical ontology took 9.489059448242188e-05s
Availability | VoID file availability check for FAO geopolitical ontology took 0.0007083415985107422s
Completeness | Calculation of interlinking completeness for FAO geopolitical ontology took 0.29302072525024414s
Reputation | Calculation of the PageRank for FAO geopolitical ontology took 0.02089691162109375s
Interlinking | Calculation of Degree of Connection for FAO geopolitical ontology took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for FAO geopolitical ontology took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for FAO geopolitical ontology took 0.00010800361633300781s
Believability | Calculation of trust value for FAO geopolitical ontology took 6.4373016357421875e-06s
INFO | --- Analysis for fao-geopolitical-ontology took 10.782265663146973s
Availability | SPARQL endpoint availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.10050082206726074s
Availability | VoID file availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.28136420249938965s
Reputation | Calculation of the PageRank for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.023184537887573242s
Interlinking | Calculation of Degree of Connection for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.00010752677917480469s
Believability | Calculation of trust value for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 6.67572021484375e-06s
INFO | --- Analysis for fao-linked-data took 2.75555682182312s
Availability | SPARQL endpoint availability check for FAO ASFIS classification of biological entities @PSNC took 4.3392181396484375e-05s
Availability | VoID file availability check for FAO ASFIS classification of biological entities @PSNC took 0.0005528926849365234s
Completeness | Calculation of interlinking completeness for FAO ASFIS classification of biological entities @PSNC took 0.31615734100341797s
Reputation | Calculation of the PageRank for FAO ASFIS classification of biological entities @PSNC took 0.020986557006835938s
Interlinking | Calculation of Degree of Connection for FAO ASFIS classification of biological entities @PSNC took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for FAO ASFIS classification of biological entities @PSNC took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for FAO ASFIS classification of biological entities @PSNC took 3.3855438232421875e-05s
Believability | Calculation of trust value for FAO ASFIS classification of biological entities @PSNC took 1.33514404296875e-05s
INFO | --- Analysis for FAO_species took 2.61216402053833s
Availability | SPARQL endpoint availability check for ChEMBL-RDF (@ Uppsala University) took 20.53772807121277s
Availability | VoID file availability check for ChEMBL-RDF (@ Uppsala University) took 0.0005643367767333984s
Completeness | Calculation of interlinking completeness for ChEMBL-RDF (@ Uppsala University) took 0.27649736404418945s
Reputation | Calculation of the PageRank for ChEMBL-RDF (@ Uppsala University) took 0.021091938018798828s
Interlinking | Calculation of Degree of Connection for ChEMBL-RDF (@ Uppsala University) took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for ChEMBL-RDF (@ Uppsala University) took 0.0008208751678466797s
Interlinking | Calculation of Clustering coefficient for ChEMBL-RDF (@ Uppsala University) took 0.00016307830810546875s
Believability | Calculation of trust value for ChEMBL-RDF (@ Uppsala University) took 1.4066696166992188e-05s
INFO | --- Analysis for farmbio-chembl took 65.18456029891968s
Availability | SPARQL endpoint availability check for I4.0-Onto took 9.1552734375e-05s
Availability | VoID file availability check for I4.0-Onto took 0.0005948543548583984s
Completeness | Calculation of interlinking completeness for I4.0-Onto took 0.2660346031188965s
Reputation | Calculation of the PageRank for I4.0-Onto took 0.02093672752380371s
Interlinking | Calculation of Degree of Connection for I4.0-Onto took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for I4.0-Onto took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for I4.0-Onto took 3.790855407714844e-05s
Believability | Calculation of trust value for I4.0-Onto took 1.0251998901367188e-05s
INFO | --- Analysis for fatimazahra took 2.673675537109375s
Availability | SPARQL endpoint availability check for FHIR STU3 took 4.553794860839844e-05s
Availability | VoID file availability check for FHIR STU3 took 0.0006153583526611328s
Completeness | Calculation of interlinking completeness for FHIR STU3 took 0.3139641284942627s
Reputation | Calculation of the PageRank for FHIR STU3 took 0.020837783813476562s
Interlinking | Calculation of Degree of Connection for FHIR STU3 took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for FHIR STU3 took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for FHIR STU3 took 3.5762786865234375e-05s
Believability | Calculation of trust value for FHIR STU3 took 9.775161743164062e-06s
INFO | --- Analysis for FHIR_STU3 took 2.9890682697296143s
Availability | SPARQL endpoint availability check for FiESTA took 6.0558319091796875e-05s
Availability | VoID file availability check for FiESTA took 0.0007812976837158203s
Completeness | Calculation of interlinking completeness for FiESTA took 0.32129693031311035s
Reputation | Calculation of the PageRank for FiESTA took 0.020470380783081055s
Interlinking | Calculation of Degree of Connection for FiESTA took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for FiESTA took 0.0008301734924316406s
Interlinking | Calculation of Clustering coefficient for FiESTA took 5.9604644775390625e-05s
Believability | Calculation of trust value for FiESTA took 1.4543533325195312e-05s
INFO | --- Analysis for fiesta took 12.95579481124878s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 4.506111145019531e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.29216766357421875s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.02257680892944336s
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.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 3.3855438232421875e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.4543533325195312e-05s
INFO | --- Analysis for file:C:UsersaDesktopurn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976.owl took 2.6935133934020996s
Availability | SPARQL endpoint availability check for Finnish municipalities and regional classifications took 4.673004150390625e-05s
Availability | VoID file availability check for Finnish municipalities and regional classifications took 0.0005872249603271484s
Completeness | Calculation of interlinking completeness for Finnish municipalities and regional classifications took 0.31539130210876465s
Reputation | Calculation of the PageRank for Finnish municipalities and regional classifications took 0.020876646041870117s
Interlinking | Calculation of Degree of Connection for Finnish municipalities and regional classifications took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Finnish municipalities and regional classifications took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Finnish municipalities and regional classifications took 7.581710815429688e-05s
Believability | Calculation of trust value for Finnish municipalities and regional classifications took 1.0013580322265625e-05s
INFO | --- Analysis for finnish-municipalities took 3.8022918701171875s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset @PSNC took 0.20739483833312988s
Availability | VoID file availability check for Norway fishery stocks dataset @PSNC took 0.0005168914794921875s
Extra | Recovery of all triples for Norway fishery stocks dataset @PSNC took 114.27024292945862s
Performance | Total latancy measurement for Norway fishery stocks dataset @PSNC took 1.008815050125122s
Amount of data | Number of triples check for Norway fishery stocks dataset @PSNC took 9.061973094940186s
Interoperability | New terms check for Norway fishery stocks dataset @PSNC took 14.582205533981323s
Versatility | Languages check for Norway fishery stocks dataset @PSNC took 300.2247221469879s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset @PSNC took 2.192673444747925s
Interpretability | RDF structures check for Norway fishery stocks dataset @PSNC took 0.3325316905975342s
Versatility | Serialization formats check for Norway fishery stocks dataset @PSNC took 9.331339836120605s
Availability | RDF dump link check for Norway fishery stocks dataset @PSNC took 0.4125521183013916s
License | MR license check for Norway fishery stocks dataset @PSNC took 1.0418870449066162s
License | HR license check for Norway fishery stocks dataset @PSNC took 300.21754240989685s
Amount of data | Number of property check for Norway fishery stocks dataset @PSNC took 0.2023613452911377s
Understandability | Number of label check for Norway fishery stocks dataset @PSNC took 3.4010331630706787s
Understandability | URI regex check for Norway fishery stocks dataset @PSNC took 0.6595702171325684s
Understandability | Vocabs check for Norway fishery stocks dataset @PSNC took 0.6653130054473877s
Verifiability | Authors check for Norway fishery stocks dataset @PSNC took 0.20697236061096191s
Verifiability | Publishers check for Norway fishery stocks dataset @PSNC took 0.2626039981842041s
Performance | Throughput check for Norway fishery stocks dataset @PSNC took 11.231314420700073s
Amount of data | Check the number of entities for Norway fishery stocks dataset @PSNC took 7.867813110351562e-05s
Verifiability | Contribs. check for Norway fishery stocks dataset @PSNC took 0.2025895118713379s
Interlinking | sameAs chians check for Norway fishery stocks dataset @PSNC took 0.218092679977417s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.41186046600341797s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.4346771240234375s
Timeliness | dataset update frequency check for Norway fishery stocks dataset @PSNC took 4.638704538345337s
Currency | Creation date check for Norway fishery stocks dataset @PSNC took 0.48354649543762207s
Currency | Modification date check for Norway fishery stocks dataset @PSNC took 0.23020219802856445s
Rep.Conc. | URIs length for Norway fishery stocks dataset @PSNC took 154.59062957763672s
Interoperability | New vocabularies check for Norway fishery stocks dataset @PSNC took 1.239776611328125e-05s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset @PSNC took 0.19948697090148926s
Accuracy | Check Functional Property for Norway fishery stocks dataset @PSNC took 0.4100656509399414s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset @PSNC took 0.4335334300994873s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset @PSNC took 38.1531867980957s
Accuracy | Check White space in annotation for Norway fishery stocks dataset @PSNC took 2.701925039291382s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset @PSNC took 2.8310770988464355s
Consistency | Disjoint class check for Norway fishery stocks dataset @PSNC took 0.21831965446472168s
Consistency | Check Misplaced properties for Norway fishery stocks dataset @PSNC took 87.1910183429718s
Consistency | Misplaced classes for Norway fishery stocks dataset @PSNC took 8.737494230270386s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset @PSNC took 32.33469319343567s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset @PSNC took 1.4104082584381104s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset @PSNC took 87.43542671203613s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset @PSNC took 2.7881956100463867s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset @PSNC took 0.5729827880859375s
Security | Sign check for Norway fishery stocks dataset @PSNC took 1.4064245223999023s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset @PSNC took 9.978126049041748s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset @PSNC took 0.8120341300964355s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset @PSNC took 0.02135300636291504s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset @PSNC took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset @PSNC took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset @PSNC took 6.532669067382812e-05s
Interoperability | Check the re-using of existing vocabs for Norway fishery stocks dataset @PSNC took 2.384185791015625e-06s
Believability | Calculation of trust value for Norway fishery stocks dataset @PSNC took 1.33514404296875e-05s
INFO | --- Analysis for Fishery_Stock_Dataset took 2280.7444944381714s
Availability | SPARQL endpoint availability check for Fishes of Texas took 6.842613220214844e-05s
Availability | VoID file availability check for Fishes of Texas took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for Fishes of Texas took 0.30655717849731445s
Reputation | Calculation of the PageRank for Fishes of Texas took 0.022490978240966797s
Interlinking | Calculation of Degree of Connection for Fishes of Texas took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Fishes of Texas took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Fishes of Texas took 9.036064147949219e-05s
Believability | Calculation of trust value for Fishes of Texas took 1.4543533325195312e-05s
INFO | --- Analysis for fishes-of-texas took 3.197941780090332s
Availability | SPARQL endpoint availability check for flickr? wrappr took 4.38690185546875e-05s
Availability | VoID file availability check for flickr? wrappr took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for flickr? wrappr took 0.30648326873779297s
Reputation | Calculation of the PageRank for flickr? wrappr took 0.020568370819091797s
Interlinking | Calculation of Degree of Connection for flickr? wrappr took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for flickr? wrappr took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for flickr? wrappr took 0.00013303756713867188s
Believability | Calculation of trust value for flickr? wrappr took 1.5020370483398438e-05s
INFO | --- Analysis for flickr-wrappr took 3.609067916870117s
Availability | SPARQL endpoint availability check for Future land use simulation model took 8.940696716308594e-05s
Availability | VoID file availability check for Future land use simulation model took 0.0006434917449951172s
Completeness | Calculation of interlinking completeness for Future land use simulation model took 0.30575990676879883s
Reputation | Calculation of the PageRank for Future land use simulation model took 0.021036386489868164s
Interlinking | Calculation of Degree of Connection for Future land use simulation model took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Future land use simulation model took 0.0010843276977539062s
Interlinking | Calculation of Clustering coefficient for Future land use simulation model took 4.124641418457031e-05s
Believability | Calculation of trust value for Future land use simulation model took 1.4781951904296875e-05s
INFO | --- Analysis for FLUS took 11.59625244140625s
Availability | SPARQL endpoint availability check for Flybase took 1.3154382705688477s
Availability | VoID file availability check for Flybase took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for Flybase took 0.3031463623046875s
Reputation | Calculation of the PageRank for Flybase took 0.02236342430114746s
Interlinking | Calculation of Degree of Connection for Flybase took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Flybase took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Flybase took 3.981590270996094e-05s
Believability | Calculation of trust value for Flybase took 2.1696090698242188e-05s
INFO | --- Analysis for flybase took 5.79971981048584s
Availability | SPARQL endpoint availability check for Flyted took 0.8706693649291992s
Availability | VoID file availability check for Flyted took 0.0006046295166015625s
Completeness | Calculation of interlinking completeness for Flyted took 0.38537073135375977s
Reputation | Calculation of the PageRank for Flyted took 0.020968198776245117s
Interlinking | Calculation of Degree of Connection for Flyted took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Flyted took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for Flyted took 3.600120544433594e-05s
Believability | Calculation of trust value for Flyted took 1.430511474609375e-05s
INFO | --- Analysis for flyted took 6.131702184677124s
Availability | SPARQL endpoint availability check for Foodista took 1.543142557144165s
Availability | VoID file availability check for Foodista took 0.0007250308990478516s
Completeness | Calculation of interlinking completeness for Foodista took 0.28023648262023926s
Reputation | Calculation of the PageRank for Foodista took 0.02353811264038086s
Interlinking | Calculation of Degree of Connection for Foodista took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Foodista took 0.0007982254028320312s
Interlinking | Calculation of Clustering coefficient for Foodista took 3.743171691894531e-05s
Believability | Calculation of trust value for Foodista took 1.2636184692382812e-05s
INFO | --- Analysis for foodista took 9.654948949813843s
Availability | SPARQL endpoint availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.17975234985351562s
Availability | VoID file availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.00030612945556640625s
Completeness | Calculation of interlinking completeness for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.2754495143890381s
Reputation | Calculation of the PageRank for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.02111029624938965s
Interlinking | Calculation of Degree of Connection for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.82012939453125e-05s
Believability | Calculation of trust value for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.1205673217773438e-05s
INFO | --- Analysis for foodpedia took 2.928295373916626s
Availability | SPARQL endpoint availability check for FrameBase schema took 5.14984130859375e-05s
Availability | VoID file availability check for FrameBase schema took 0.0004267692565917969s
Completeness | Calculation of interlinking completeness for FrameBase schema took 0.29618096351623535s
Reputation | Calculation of the PageRank for FrameBase schema took 0.02050614356994629s
Interlinking | Calculation of Degree of Connection for FrameBase schema took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for FrameBase schema took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for FrameBase schema took 4.601478576660156e-05s
Believability | Calculation of trust value for FrameBase schema took 1.0251998901367188e-05s
INFO | --- Analysis for framebase-schema took 3.149078607559204s
Availability | SPARQL endpoint availability check for Framester took 4.673004150390625e-05s
Availability | VoID file availability check for Framester took 0.0007464885711669922s
Completeness | Calculation of interlinking completeness for Framester took 0.2989835739135742s
Reputation | Calculation of the PageRank for Framester took 0.021030902862548828s
Interlinking | Calculation of Degree of Connection for Framester took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Framester took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Framester took 7.915496826171875e-05s
Believability | Calculation of trust value for Framester took 9.298324584960938e-06s
INFO | --- Analysis for framester took 3.958590507507324s
Availability | SPARQL endpoint availability check for Federal Reserve Board (FRB) Linked Data took 0.059298038482666016s
Availability | VoID file availability check for Federal Reserve Board (FRB) Linked Data took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for Federal Reserve Board (FRB) Linked Data took 0.29242849349975586s
Reputation | Calculation of the PageRank for Federal Reserve Board (FRB) Linked Data took 0.02138519287109375s
Interlinking | Calculation of Degree of Connection for Federal Reserve Board (FRB) Linked Data took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Federal Reserve Board (FRB) Linked Data took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Board (FRB) Linked Data took 8.893013000488281e-05s
Believability | Calculation of trust value for Federal Reserve Board (FRB) Linked Data took 1.33514404296875e-05s
INFO | --- Analysis for frb-linked-data took 2.748931407928467s
Availability | SPARQL endpoint availability check for 1989shack Inc. E-Commerce  took 4.4345855712890625e-05s
Availability | VoID file availability check for 1989shack Inc. E-Commerce  took 0.0005567073822021484s
Completeness | Calculation of interlinking completeness for 1989shack Inc. E-Commerce  took 0.26578617095947266s
Reputation | Calculation of the PageRank for 1989shack Inc. E-Commerce  took 0.021899938583374023s
Interlinking | Calculation of Degree of Connection for 1989shack Inc. E-Commerce  took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for 1989shack Inc. E-Commerce  took 0.000858306884765625s
Interlinking | Calculation of Clustering coefficient for 1989shack Inc. E-Commerce  took 0.0003159046173095703s
Believability | Calculation of trust value for 1989shack Inc. E-Commerce  took 1.4543533325195312e-05s
INFO | --- Analysis for freebase took 4.6493940353393555s
Availability | SPARQL endpoint availability check for Freeyork took 5.91278076171875e-05s
Availability | VoID file availability check for Freeyork took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for Freeyork took 0.2880697250366211s
Reputation | Calculation of the PageRank for Freeyork took 0.020731687545776367s
Interlinking | Calculation of Degree of Connection for Freeyork took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Freeyork took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Freeyork took 0.00010776519775390625s
Believability | Calculation of trust value for Freeyork took 1.33514404296875e-05s
INFO | --- Analysis for freeyork-org took 3.4717817306518555s
Availability | SPARQL endpoint availability check for Community Research and Development Information Service (CORDIS) took 0.7449746131896973s
Availability | VoID file availability check for Community Research and Development Information Service (CORDIS) took 0.0006425380706787109s
Completeness | Calculation of interlinking completeness for Community Research and Development Information Service (CORDIS) took 0.3126089572906494s
Reputation | Calculation of the PageRank for Community Research and Development Information Service (CORDIS) took 0.022176027297973633s
Interlinking | Calculation of Degree of Connection for Community Research and Development Information Service (CORDIS) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Community Research and Development Information Service (CORDIS) took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Community Research and Development Information Service (CORDIS) took 7.939338684082031e-05s
Believability | Calculation of trust value for Community Research and Development Information Service (CORDIS) took 1.1205673217773438e-05s
INFO | --- Analysis for fu-berlin-cordis took 4.913028240203857s
Availability | SPARQL endpoint availability check for DailyMed took 0.6902103424072266s
Availability | VoID file availability check for DailyMed took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for DailyMed took 0.2821478843688965s
Reputation | Calculation of the PageRank for DailyMed took 0.022075176239013672s
Interlinking | Calculation of Degree of Connection for DailyMed took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for DailyMed took 0.0013818740844726562s
Interlinking | Calculation of Clustering coefficient for DailyMed took 0.00014162063598632812s
Believability | Calculation of trust value for DailyMed took 1.430511474609375e-05s
INFO | --- Analysis for fu-berlin-dailymed took 5.823281288146973s
Availability | SPARQL endpoint availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.7035892009735107s
Availability | VoID file availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for DBLP Bibliography Database in RDF (FU Berlin) took 0.3293168544769287s
Reputation | Calculation of the PageRank for DBLP Bibliography Database in RDF (FU Berlin) took 0.020739078521728516s
Interlinking | Calculation of Degree of Connection for DBLP Bibliography Database in RDF (FU Berlin) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBLP Bibliography Database in RDF (FU Berlin) took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for DBLP Bibliography Database in RDF (FU Berlin) took 8.893013000488281e-05s
Believability | Calculation of trust value for DBLP Bibliography Database in RDF (FU Berlin) took 1.0013580322265625e-05s
INFO | --- Analysis for fu-berlin-dblp took 4.781793117523193s
Availability | SPARQL endpoint availability check for Diseasome took 0.6638138294219971s
Availability | VoID file availability check for Diseasome took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for Diseasome took 0.2896277904510498s
Reputation | Calculation of the PageRank for Diseasome took 0.020780324935913086s
Interlinking | Calculation of Degree of Connection for Diseasome took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Diseasome took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Diseasome took 0.00011420249938964844s
Believability | Calculation of trust value for Diseasome took 1.1444091796875e-05s
INFO | --- Analysis for fu-berlin-diseasome took 5.84429669380188s
Availability | SPARQL endpoint availability check for DrugBank took 0.6625504493713379s
Availability | VoID file availability check for DrugBank took 0.0005502700805664062s
Completeness | Calculation of interlinking completeness for DrugBank took 0.2863943576812744s
Reputation | Calculation of the PageRank for DrugBank took 0.021077871322631836s
Interlinking | Calculation of Degree of Connection for DrugBank took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for DrugBank took 0.0007894039154052734s
Interlinking | Calculation of Clustering coefficient for DrugBank took 0.00011944770812988281s
Believability | Calculation of trust value for DrugBank took 1.4543533325195312e-05s
INFO | --- Analysis for fu-berlin-drugbank took 5.902244806289673s
Availability | SPARQL endpoint availability check for European Commission Competition data set (FU Berlin) took 0.6947033405303955s
Availability | VoID file availability check for European Commission Competition data set (FU Berlin) took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for European Commission Competition data set (FU Berlin) took 0.28684210777282715s
Reputation | Calculation of the PageRank for European Commission Competition data set (FU Berlin) took 0.020618200302124023s
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.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for European Commission Competition data set (FU Berlin) took 3.314018249511719e-05s
Believability | Calculation of trust value for European Commission Competition data set (FU Berlin) took 1.4543533325195312e-05s
INFO | --- Analysis for fu-berlin-ec-competition took 4.764181613922119s
Availability | SPARQL endpoint availability check for EURAXESS - Researchers in Motion took 0.7011914253234863s
Availability | VoID file availability check for EURAXESS - Researchers in Motion took 0.0006427764892578125s
Completeness | Calculation of interlinking completeness for EURAXESS - Researchers in Motion took 0.30524182319641113s
Reputation | Calculation of the PageRank for EURAXESS - Researchers in Motion took 0.020554065704345703s
Interlinking | Calculation of Degree of Connection for EURAXESS - Researchers in Motion took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EURAXESS - Researchers in Motion took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for EURAXESS - Researchers in Motion took 7.891654968261719e-05s
Believability | Calculation of trust value for EURAXESS - Researchers in Motion took 1.0728836059570312e-05s
INFO | --- Analysis for fu-berlin-euraxess took 4.625278472900391s
Availability | SPARQL endpoint availability check for European Employment Services (EURES) took 0.6991677284240723s
Availability | VoID file availability check for European Employment Services (EURES) took 0.0007038116455078125s
Completeness | Calculation of interlinking completeness for European Employment Services (EURES) took 0.32899951934814453s
Reputation | Calculation of the PageRank for European Employment Services (EURES) took 0.020711421966552734s
Interlinking | Calculation of Degree of Connection for European Employment Services (EURES) took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for European Employment Services (EURES) took 0.0009033679962158203s
Interlinking | Calculation of Clustering coefficient for European Employment Services (EURES) took 8.893013000488281e-05s
Believability | Calculation of trust value for European Employment Services (EURES) took 7.867813110351562e-06s
INFO | --- Analysis for fu-berlin-eures took 4.736370801925659s
Availability | SPARQL endpoint availability check for Eurostat in RDF (FU Berlin) took 0.69187331199646s
Availability | VoID file availability check for Eurostat in RDF (FU Berlin) took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for Eurostat in RDF (FU Berlin) took 0.2844579219818115s
Reputation | Calculation of the PageRank for Eurostat in RDF (FU Berlin) took 0.02069830894470215s
Interlinking | Calculation of Degree of Connection for Eurostat in RDF (FU Berlin) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Eurostat in RDF (FU Berlin) took 0.0008060932159423828s
Interlinking | Calculation of Clustering coefficient for Eurostat in RDF (FU Berlin) took 0.00010228157043457031s
Believability | Calculation of trust value for Eurostat in RDF (FU Berlin) took 6.198883056640625e-06s
INFO | --- Analysis for fu-berlin-eurostat took 5.122707843780518s
Availability | SPARQL endpoint availability check for MediCare took 0.6728999614715576s
Availability | VoID file availability check for MediCare took 0.0005781650543212891s
Completeness | Calculation of interlinking completeness for MediCare took 0.2964046001434326s
Reputation | Calculation of the PageRank for MediCare took 0.02081155776977539s
Interlinking | Calculation of Degree of Connection for MediCare took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for MediCare took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for MediCare took 4.601478576660156e-05s
Believability | Calculation of trust value for MediCare took 1.4066696166992188e-05s
INFO | --- Analysis for fu-berlin-medicare took 5.371345281600952s
Availability | SPARQL endpoint availability check for Project Gutenberg in RDF (FU Berlin) took 0.680365800857544s
Availability | VoID file availability check for Project Gutenberg in RDF (FU Berlin) took 0.0006363391876220703s
Completeness | Calculation of interlinking completeness for Project Gutenberg in RDF (FU Berlin) took 0.3036079406738281s
Reputation | Calculation of the PageRank for Project Gutenberg in RDF (FU Berlin) took 0.022977828979492188s
Interlinking | Calculation of Degree of Connection for Project Gutenberg in RDF (FU Berlin) took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Project Gutenberg in RDF (FU Berlin) took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg in RDF (FU Berlin) took 7.843971252441406e-05s
Believability | Calculation of trust value for Project Gutenberg in RDF (FU Berlin) took 1.430511474609375e-05s
INFO | --- Analysis for fu-berlin-project-gutenberg took 4.717339754104614s
Availability | SPARQL endpoint availability check for SIDER: Side Effect Resource took 0.6714761257171631s
Availability | VoID file availability check for SIDER: Side Effect Resource took 0.0005342960357666016s
Completeness | Calculation of interlinking completeness for SIDER: Side Effect Resource took 0.3316316604614258s
Reputation | Calculation of the PageRank for SIDER: Side Effect Resource took 0.020601511001586914s
Interlinking | Calculation of Degree of Connection for SIDER: Side Effect Resource took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for SIDER: Side Effect Resource took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for SIDER: Side Effect Resource took 9.393692016601562e-05s
Believability | Calculation of trust value for SIDER: Side Effect Resource took 1.430511474609375e-05s
INFO | --- Analysis for fu-berlin-sider took 5.207520484924316s
Availability | SPARQL endpoint availability check for STITCH: Chemical-Protein Interactions took 0.6809089183807373s
Availability | VoID file availability check for STITCH: Chemical-Protein Interactions took 0.0006823539733886719s
Completeness | Calculation of interlinking completeness for STITCH: Chemical-Protein Interactions took 0.2781352996826172s
Reputation | Calculation of the PageRank for STITCH: Chemical-Protein Interactions took 0.020568132400512695s
Interlinking | Calculation of Degree of Connection for STITCH: Chemical-Protein Interactions took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for STITCH: Chemical-Protein Interactions took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for STITCH: Chemical-Protein Interactions took 8.58306884765625e-05s
Believability | Calculation of trust value for STITCH: Chemical-Protein Interactions took 1.52587890625e-05s
INFO | --- Analysis for fu-berlin-stitch took 4.594064712524414s
Availability | SPARQL endpoint availability check for fvdb took 8.845329284667969e-05s
Availability | VoID file availability check for fvdb took 0.0005464553833007812s
Completeness | Calculation of interlinking completeness for fvdb took 0.29668211936950684s
Reputation | Calculation of the PageRank for fvdb took 0.022383689880371094s
Interlinking | Calculation of Degree of Connection for fvdb took 1.52587890625e-05s
Interlinking | Calculation of Centrality for fvdb took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for fvdb took 3.600120544433594e-05s
Believability | Calculation of trust value for fvdb took 1.5020370483398438e-05s
INFO | --- Analysis for fv took 12.70978331565857s
Availability | SPARQL endpoint availability check for Global Agricultural Concept Space took 9.059906005859375e-05s
Availability | VoID file availability check for Global Agricultural Concept Space took 0.0004050731658935547s
Completeness | Calculation of interlinking completeness for Global Agricultural Concept Space took 0.31812167167663574s
Reputation | Calculation of the PageRank for Global Agricultural Concept Space took 0.021030902862548828s
Interlinking | Calculation of Degree of Connection for Global Agricultural Concept Space took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Global Agricultural Concept Space took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for Global Agricultural Concept Space took 3.62396240234375e-05s
Believability | Calculation of trust value for Global Agricultural Concept Space took 1.33514404296875e-05s
INFO | --- Analysis for GACS took 3.263533592224121s
Availability | SPARQL endpoint availability check for Galician EuroWordNet-lemon lexicon (3.0) took 9.274482727050781e-05s
Availability | VoID file availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.0007383823394775391s
Completeness | Calculation of interlinking completeness for Galician EuroWordNet-lemon lexicon (3.0) took 0.2694699764251709s
Reputation | Calculation of the PageRank for Galician EuroWordNet-lemon lexicon (3.0) took 0.021569013595581055s
Interlinking | Calculation of Degree of Connection for Galician EuroWordNet-lemon lexicon (3.0) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Galician EuroWordNet-lemon lexicon (3.0) took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Galician EuroWordNet-lemon lexicon (3.0) took 4.506111145019531e-05s
Believability | Calculation of trust value for Galician EuroWordNet-lemon lexicon (3.0) took 1.5020370483398438e-05s
INFO | --- Analysis for galician-eurowordnet-lemon-lexicon-3-0 took 5.5469841957092285s
Availability | SPARQL endpoint availability check for Garnica Plywood Catalogue took 9.679794311523438e-05s
Availability | VoID file availability check for Garnica Plywood Catalogue took 0.000286102294921875s
Completeness | Calculation of interlinking completeness for Garnica Plywood Catalogue took 0.31043171882629395s
Reputation | Calculation of the PageRank for Garnica Plywood Catalogue took 0.020667552947998047s
Interlinking | Calculation of Degree of Connection for Garnica Plywood Catalogue took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Garnica Plywood Catalogue took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for Garnica Plywood Catalogue took 0.00010538101196289062s
Believability | Calculation of trust value for Garnica Plywood Catalogue took 1.430511474609375e-05s
INFO | --- Analysis for garnicaplywood took 3.665545701980591s
Availability | SPARQL endpoint availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 6.103515625e-05s
Availability | VoID file availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0004296302795410156s
Completeness | Calculation of interlinking completeness for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.29357028007507324s
Reputation | Calculation of the PageRank for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.021369457244873047s
Interlinking | Calculation of Degree of Connection for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 9.655952453613281e-05s
Believability | Calculation of trust value for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.049041748046875e-05s
INFO | --- Analysis for gemeenschappelijke-thesaurus-audiovisuele-archieven took 8.008693218231201s
Availability | SPARQL endpoint availability check for GEneral Multilingual Environmental Thesaurus took 0.31731414794921875s
Availability | VoID file availability check for GEneral Multilingual Environmental Thesaurus took 0.0007271766662597656s
Completeness | Calculation of interlinking completeness for GEneral Multilingual Environmental Thesaurus took 0.31556200981140137s
Reputation | Calculation of the PageRank for GEneral Multilingual Environmental Thesaurus took 0.020858287811279297s
Interlinking | Calculation of Degree of Connection for GEneral Multilingual Environmental Thesaurus took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for GEneral Multilingual Environmental Thesaurus took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for GEneral Multilingual Environmental Thesaurus took 9.894371032714844e-05s
Believability | Calculation of trust value for GEneral Multilingual Environmental Thesaurus took 1.52587890625e-05s
INFO | --- Analysis for gemet took 5.1112353801727295s
Availability | SPARQL endpoint availability check for gemet-annotated took 0.00010919570922851562s
Availability | VoID file availability check for gemet-annotated took 0.0006606578826904297s
Completeness | Calculation of interlinking completeness for gemet-annotated took 0.4237830638885498s
Reputation | Calculation of the PageRank for gemet-annotated took 0.02177572250366211s
Interlinking | Calculation of Degree of Connection for gemet-annotated took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for gemet-annotated took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for gemet-annotated took 4.172325134277344e-05s
Believability | Calculation of trust value for gemet-annotated took 9.775161743164062e-06s
INFO | --- Analysis for gemet-annotated took 3.4316768646240234s
Availability | SPARQL endpoint availability check for Gene Expression Atlas RDF took 0.8112831115722656s
Availability | VoID file availability check for Gene Expression Atlas RDF took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for Gene Expression Atlas RDF took 0.27423810958862305s
Reputation | Calculation of the PageRank for Gene Expression Atlas RDF took 0.020781993865966797s
Interlinking | Calculation of Degree of Connection for Gene Expression Atlas RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Gene Expression Atlas RDF took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Gene Expression Atlas RDF took 4.0531158447265625e-05s
Believability | Calculation of trust value for Gene Expression Atlas RDF took 1.5974044799804688e-05s
INFO | --- Analysis for gene-expression-atlas-rdf took 4.446479320526123s
Availability | SPARQL endpoint availability check for Super Ontology took 1.1433141231536865s
Availability | VoID file availability check for Super Ontology took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.3001835346221924s
Reputation | Calculation of the PageRank for Super Ontology took 0.020519495010375977s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 3.504753112792969e-05s
Believability | Calculation of trust value for Super Ontology took 1.4781951904296875e-05s
INFO | --- Analysis for Generalized_Super_Ontology took 4.34171724319458s
Availability | SPARQL endpoint availability check for Geographic detector model took 4.57763671875e-05s
Availability | VoID file availability check for Geographic detector model took 0.0004177093505859375s
Completeness | Calculation of interlinking completeness for Geographic detector model took 0.2874257564544678s
Reputation | Calculation of the PageRank for Geographic detector model took 0.021272659301757812s
Interlinking | Calculation of Degree of Connection for Geographic detector model took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Geographic detector model took 0.0007824897766113281s
Interlinking | Calculation of Clustering coefficient for Geographic detector model took 3.5762786865234375e-05s
Believability | Calculation of trust value for Geographic detector model took 1.0013580322265625e-05s
INFO | --- Analysis for GeoDetector took 19.01598310470581s
Availability | SPARQL endpoint availability check for geodomainwn took 4.649162292480469e-05s
Availability | VoID file availability check for geodomainwn took 0.0005650520324707031s
Completeness | Calculation of interlinking completeness for geodomainwn took 0.28671717643737793s
Reputation | Calculation of the PageRank for geodomainwn took 0.020620107650756836s
Interlinking | Calculation of Degree of Connection for geodomainwn took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for geodomainwn took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for geodomainwn took 5.078315734863281e-05s
Believability | Calculation of trust value for geodomainwn took 1.0251998901367188e-05s
INFO | --- Analysis for geodomainwn took 7.030664682388306s
Availability | SPARQL endpoint availability check for GeoEcuador took 0.00010395050048828125s
Availability | VoID file availability check for GeoEcuador took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for GeoEcuador took 0.3262443542480469s
Reputation | Calculation of the PageRank for GeoEcuador took 0.021027088165283203s
Interlinking | Calculation of Degree of Connection for GeoEcuador took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for GeoEcuador took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for GeoEcuador took 7.605552673339844e-05s
Believability | Calculation of trust value for GeoEcuador took 1.4781951904296875e-05s
INFO | --- Analysis for geoecuador took 12.928544759750366s
Availability | SPARQL endpoint availability check for Geographic Names Information System (GNIS) took 2.7309226989746094s
Availability | VoID file availability check for Geographic Names Information System (GNIS) took 0.0007953643798828125s
Completeness | Calculation of interlinking completeness for Geographic Names Information System (GNIS) took 0.31989526748657227s
Reputation | Calculation of the PageRank for Geographic Names Information System (GNIS) took 0.021008014678955078s
Interlinking | Calculation of Degree of Connection for Geographic Names Information System (GNIS) took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for Geographic Names Information System (GNIS) took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for Geographic Names Information System (GNIS) took 7.867813110351562e-05s
Believability | Calculation of trust value for Geographic Names Information System (GNIS) took 1.5020370483398438e-05s
INFO | --- Analysis for geographic-names-information-system-gnis took 47.34664797782898s
Availability | SPARQL endpoint availability check for GeoLinkedData took 0.45806169509887695s
Availability | VoID file availability check for GeoLinkedData took 0.00030684471130371094s
Completeness | Calculation of interlinking completeness for GeoLinkedData took 0.309772253036499s
Reputation | Calculation of the PageRank for GeoLinkedData took 0.02089691162109375s
Interlinking | Calculation of Degree of Connection for GeoLinkedData took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for GeoLinkedData took 0.0008738040924072266s
Interlinking | Calculation of Clustering coefficient for GeoLinkedData took 0.00010156631469726562s
Believability | Calculation of trust value for GeoLinkedData took 5.9604644775390625e-06s
INFO | --- Analysis for geolinkeddata took 4.1397385597229s
Availability | SPARQL endpoint availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.17848682403564453s
Availability | VoID file availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.0005626678466796875s
Extra | Recovery of all triples for Geological Survey of Austria (GBA) - Thesaurus took 8.87483811378479s
Performance | Total latancy measurement for Geological Survey of Austria (GBA) - Thesaurus took 0.3741633892059326s
Amount of data | Number of triples check for Geological Survey of Austria (GBA) - Thesaurus took 0.1391890048980713s
Interoperability | New terms check for Geological Survey of Austria (GBA) - Thesaurus took 1.3996238708496094s
Versatility | Languages check for Geological Survey of Austria (GBA) - Thesaurus took 0.18576264381408691s
Interpretability | Number of blank nodes check for Geological Survey of Austria (GBA) - Thesaurus took 0.16037964820861816s
Security | Check HTTPS for Geological Survey of Austria (GBA) - Thesaurus took 0.20202326774597168s
Interpretability | RDF structures check for Geological Survey of Austria (GBA) - Thesaurus took 0.1016085147857666s
Versatility | Serialization formats check for Geological Survey of Austria (GBA) - Thesaurus took 0.09473156929016113s
Availability | RDF dump link check for Geological Survey of Austria (GBA) - Thesaurus took 0.06922769546508789s
License | MR license check for Geological Survey of Austria (GBA) - Thesaurus took 0.09368681907653809s
License | HR license check for Geological Survey of Austria (GBA) - Thesaurus took 1.8724174499511719s
Amount of data | Number of property check for Geological Survey of Austria (GBA) - Thesaurus took 0.10461020469665527s
Understandability | Number of label check for Geological Survey of Austria (GBA) - Thesaurus took 0.09869384765625s
Understandability | URI regex check for Geological Survey of Austria (GBA) - Thesaurus took 0.1312258243560791s
Understandability | Vocabs check for Geological Survey of Austria (GBA) - Thesaurus took 0.10121941566467285s
Verifiability | Authors check for Geological Survey of Austria (GBA) - Thesaurus took 0.0700218677520752s
Verifiability | Publishers check for Geological Survey of Austria (GBA) - Thesaurus took 0.08575105667114258s
Performance | Throughput check for Geological Survey of Austria (GBA) - Thesaurus took 10.291575908660889s
Amount of data | Check the number of entities for Geological Survey of Austria (GBA) - Thesaurus took 8.273124694824219e-05s
Verifiability | Contribs. check for Geological Survey of Austria (GBA) - Thesaurus took 0.06993365287780762s
Interlinking | sameAs chians check for Geological Survey of Austria (GBA) - Thesaurus took 0.06667685508728027s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.08837461471557617s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.07720088958740234s
Timeliness | dataset update frequency check for Geological Survey of Austria (GBA) - Thesaurus took 0.06945300102233887s
Currency | Creation date check for Geological Survey of Austria (GBA) - Thesaurus took 0.16157150268554688s
Currency | Modification date check for Geological Survey of Austria (GBA) - Thesaurus took 0.16461515426635742s
Rep.Conc. | URIs length for Geological Survey of Austria (GBA) - Thesaurus took 1.2602696418762207s
Interoperability | New vocabularies check for Geological Survey of Austria (GBA) - Thesaurus took 0.665259838104248s
Consistency | Deprecated classes/propertiers check for Geological Survey of Austria (GBA) - Thesaurus took 0.09345197677612305s
Accuracy | Check Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.06904792785644531s
Accuracy | Check Inverse Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.06850385665893555s
Accuracy | Check Empty annotation labels for Geological Survey of Austria (GBA) - Thesaurus took 0.3076333999633789s
Accuracy | Check White space in annotation for Geological Survey of Austria (GBA) - Thesaurus took 0.007312774658203125s
Accuracy | Check Datatype consistency for Geological Survey of Austria (GBA) - Thesaurus took 0.2329854965209961s
Consistency | Disjoint class check for Geological Survey of Austria (GBA) - Thesaurus took 0.0691843032836914s
Consistency | Check Misplaced properties for Geological Survey of Austria (GBA) - Thesaurus took 0.21013426780700684s
Consistency | Misplaced classes for Geological Survey of Austria (GBA) - Thesaurus took 0.5461840629577637s
Consistency | Check Ontology hijacking for Geological Survey of Austria (GBA) - Thesaurus took 3.195848226547241s
Consistency | Check Invalid usage of undefined classes for Geological Survey of Austria (GBA) - Thesaurus took 1.4989056587219238s
Consistency | Check Invalid usage of undefined properties for Geological Survey of Austria (GBA) - Thesaurus took 1.6701841354370117s
Conciseness | Check Extensional conciseness for Geological Survey of Austria (GBA) - Thesaurus took 0.1815800666809082s
Security | Sign check for Geological Survey of Austria (GBA) - Thesaurus took 0.07646536827087402s
Availability | Check URIs Dereferenciability for Geological Survey of Austria (GBA) - Thesaurus took 1.0568013191223145s
Completeness | Calculation of interlinking completeness for Geological Survey of Austria (GBA) - Thesaurus took 0.34717822074890137s
Reputation | Calculation of the PageRank for Geological Survey of Austria (GBA) - Thesaurus took 0.020967483520507812s
Interlinking | Calculation of Degree of Connection for Geological Survey of Austria (GBA) - Thesaurus took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Geological Survey of Austria (GBA) - Thesaurus took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Geological Survey of Austria (GBA) - Thesaurus took 0.00010251998901367188s
Interoperability | Check the re-using of existing vocabs for Geological Survey of Austria (GBA) - Thesaurus took 0.9877138137817383s
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 112.84243750572205s
Availability | SPARQL endpoint availability check for GeoNames Semantic Web took 4.982948303222656e-05s
Availability | VoID file availability check for GeoNames Semantic Web took 0.0006458759307861328s
Completeness | Calculation of interlinking completeness for GeoNames Semantic Web took 0.2971036434173584s
Reputation | Calculation of the PageRank for GeoNames Semantic Web took 0.020588159561157227s
Interlinking | Calculation of Degree of Connection for GeoNames Semantic Web took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for GeoNames Semantic Web took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for GeoNames Semantic Web took 0.0004754066467285156s
Believability | Calculation of trust value for GeoNames Semantic Web took 1.3113021850585938e-05s
INFO | --- Analysis for geonames-semantic-web took 3.486989736557007s
Availability | SPARQL endpoint availability check for Geospatial World  took 4.673004150390625e-05s
Availability | VoID file availability check for Geospatial World  took 0.0005645751953125s
Completeness | Calculation of interlinking completeness for Geospatial World  took 0.30452394485473633s
Reputation | Calculation of the PageRank for Geospatial World  took 0.02064824104309082s
Interlinking | Calculation of Degree of Connection for Geospatial World  took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Geospatial World  took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Geospatial World  took 0.00011110305786132812s
Believability | Calculation of trust value for Geospatial World  took 1.049041748046875e-05s
INFO | --- Analysis for geospatialworld-net took 3.2416622638702393s
Availability | SPARQL endpoint availability check for GeoSpecies Knowledge Base took 0.695411205291748s
Availability | VoID file availability check for GeoSpecies Knowledge Base took 0.0006442070007324219s
Completeness | Calculation of interlinking completeness for GeoSpecies Knowledge Base took 0.3087940216064453s
Reputation | Calculation of the PageRank for GeoSpecies Knowledge Base took 0.020606279373168945s
Interlinking | Calculation of Degree of Connection for GeoSpecies Knowledge Base took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for GeoSpecies Knowledge Base took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Knowledge Base took 0.0001609325408935547s
Believability | Calculation of trust value for GeoSpecies Knowledge Base took 1.3828277587890625e-05s
INFO | --- Analysis for geospecies took 6.371967792510986s
Availability | SPARQL endpoint availability check for GeoWordNet took 9.083747863769531e-05s
Availability | VoID file availability check for GeoWordNet took 0.0006861686706542969s
Completeness | Calculation of interlinking completeness for GeoWordNet took 0.3315408229827881s
Reputation | Calculation of the PageRank for GeoWordNet took 0.020557403564453125s
Interlinking | Calculation of Degree of Connection for GeoWordNet took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for GeoWordNet took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for GeoWordNet took 5.888938903808594e-05s
Believability | Calculation of trust value for GeoWordNet took 1.3113021850585938e-05s
INFO | --- Analysis for geowordnet took 7.4250030517578125s
Availability | SPARQL endpoint availability check for German labor law thesaurus took 0.09340739250183105s
Availability | VoID file availability check for German labor law thesaurus took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for German labor law thesaurus took 0.3292572498321533s
Reputation | Calculation of the PageRank for German labor law thesaurus took 0.020712614059448242s
Interlinking | Calculation of Degree of Connection for German labor law thesaurus took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for German labor law thesaurus took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for German labor law thesaurus took 8.654594421386719e-05s
Believability | Calculation of trust value for German labor law thesaurus took 1.1444091796875e-05s
INFO | --- Analysis for german-labor-law-thesaurus took 2.788572072982788s
Availability | SPARQL endpoint availability check for Linked Old Germanic Dictionaries took 4.38690185546875e-05s
Availability | VoID file availability check for Linked Old Germanic Dictionaries took 0.0005817413330078125s
Completeness | Calculation of interlinking completeness for Linked Old Germanic Dictionaries took 0.3050103187561035s
Reputation | Calculation of the PageRank for Linked Old Germanic Dictionaries took 0.022179365158081055s
Interlinking | Calculation of Degree of Connection for Linked Old Germanic Dictionaries took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Linked Old Germanic Dictionaries took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Linked Old Germanic Dictionaries took 6.961822509765625e-05s
Believability | Calculation of trust value for Linked Old Germanic Dictionaries took 1.4066696166992188e-05s
INFO | --- Analysis for germlex took 3.0632123947143555s
Availability | SPARQL endpoint availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.5387942790985107s
Availability | VoID file availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.2735323905944824s
Reputation | Calculation of the PageRank for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.02069878578186035s
Interlinking | Calculation of Degree of Connection for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0008032321929931641s
Interlinking | Calculation of Clustering coefficient for TheSoz Thesaurus for the Social Sciences (GESIS) took 9.632110595703125e-05s
Believability | Calculation of trust value for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.239776611328125e-05s
INFO | --- Analysis for gesis-thesoz took 5.611421585083008s
Availability | SPARQL endpoint availability check for Art & Architecture Thesaurus took 2.4499430656433105s
Availability | VoID file availability check for Art & Architecture Thesaurus took 0.0006635189056396484s
Completeness | Calculation of interlinking completeness for Art & Architecture Thesaurus took 0.29534482955932617s
Reputation | Calculation of the PageRank for Art & Architecture Thesaurus took 0.020542383193969727s
Interlinking | Calculation of Degree of Connection for Art & Architecture Thesaurus took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Art & Architecture Thesaurus took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for Art & Architecture Thesaurus took 8.320808410644531e-05s
Believability | Calculation of trust value for Art & Architecture Thesaurus took 1.4066696166992188e-05s
INFO | --- Analysis for getty-aat took 16.460631132125854s
Availability | SPARQL endpoint availability check for The Getty Thesaurus of Geographic Names took 1.2903833389282227s
Availability | VoID file availability check for The Getty Thesaurus of Geographic Names took 0.0006406307220458984s
Completeness | Calculation of interlinking completeness for The Getty Thesaurus of Geographic Names took 0.2993588447570801s
Reputation | Calculation of the PageRank for The Getty Thesaurus of Geographic Names took 0.021226882934570312s
Interlinking | Calculation of Degree of Connection for The Getty Thesaurus of Geographic Names took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for The Getty Thesaurus of Geographic Names took 0.0009672641754150391s
Interlinking | Calculation of Clustering coefficient for The Getty Thesaurus of Geographic Names took 6.651878356933594e-05s
Believability | Calculation of trust value for The Getty Thesaurus of Geographic Names took 1.0728836059570312e-05s
INFO | --- Analysis for getty-tgn took 13.232125520706177s
Availability | SPARQL endpoint availability check for Gipuzkoa Demografia took 4.963849067687988s
Availability | VoID file availability check for Gipuzkoa Demografia took 0.0008175373077392578s
Completeness | Calculation of interlinking completeness for Gipuzkoa Demografia took 0.28951096534729004s
Reputation | Calculation of the PageRank for Gipuzkoa Demografia took 0.02100372314453125s
Interlinking | Calculation of Degree of Connection for Gipuzkoa Demografia took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Gipuzkoa Demografia took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Gipuzkoa Demografia took 3.4332275390625e-05s
Believability | Calculation of trust value for Gipuzkoa Demografia took 1.0251998901367188e-05s
INFO | --- Analysis for gipuzkoademografia took 28.028071641921997s
Availability | SPARQL endpoint availability check for Glastonbury 2011 Programme took 9.059906005859375e-05s
Availability | VoID file availability check for Glastonbury 2011 Programme took 0.0006320476531982422s
Completeness | Calculation of interlinking completeness for Glastonbury 2011 Programme took 0.2783536911010742s
Reputation | Calculation of the PageRank for Glastonbury 2011 Programme took 0.02072882652282715s
Interlinking | Calculation of Degree of Connection for Glastonbury 2011 Programme took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Glastonbury 2011 Programme took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Glastonbury 2011 Programme took 3.24249267578125e-05s
Believability | Calculation of trust value for Glastonbury 2011 Programme took 1.430511474609375e-05s
INFO | --- Analysis for glastonbury-2011 took 5.711835861206055s
Availability | SPARQL endpoint availability check for Global Hunger Index (2011) took 9.107589721679688e-05s
Availability | VoID file availability check for Global Hunger Index (2011) took 0.0004298686981201172s
Completeness | Calculation of interlinking completeness for Global Hunger Index (2011) took 0.30717968940734863s
Reputation | Calculation of the PageRank for Global Hunger Index (2011) took 0.0206754207611084s
Interlinking | Calculation of Degree of Connection for Global Hunger Index (2011) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Global Hunger Index (2011) took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Global Hunger Index (2011) took 5.1021575927734375e-05s
Believability | Calculation of trust value for Global Hunger Index (2011) took 1.4543533325195312e-05s
INFO | --- Analysis for global-hunger-index-2011 took 3.5474917888641357s
Availability | SPARQL endpoint availability check for Glottolog took 4.553794860839844e-05s
Availability | VoID file availability check for Glottolog took 0.0009467601776123047s
Completeness | Calculation of interlinking completeness for Glottolog took 0.2769463062286377s
Reputation | Calculation of the PageRank for Glottolog took 0.02173018455505371s
Interlinking | Calculation of Degree of Connection for Glottolog took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Glottolog took 0.0008077621459960938s
Interlinking | Calculation of Clustering coefficient for Glottolog took 5.91278076171875e-05s
Believability | Calculation of trust value for Glottolog took 1.0013580322265625e-05s
INFO | --- Analysis for glottolog took 6.6722118854522705s
Availability | SPARQL endpoint availability check for GNOSS.com, a Social and Semantic Platform took 4.553794860839844e-05s
Availability | VoID file availability check for GNOSS.com, a Social and Semantic Platform took 0.0005035400390625s
Completeness | Calculation of interlinking completeness for GNOSS.com, a Social and Semantic Platform took 0.30947351455688477s
Reputation | Calculation of the PageRank for GNOSS.com, a Social and Semantic Platform took 0.020817279815673828s
Interlinking | Calculation of Degree of Connection for GNOSS.com, a Social and Semantic Platform took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for GNOSS.com, a Social and Semantic Platform took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for GNOSS.com, a Social and Semantic Platform took 0.00011444091796875s
Believability | Calculation of trust value for GNOSS.com, a Social and Semantic Platform took 1.239776611328125e-05s
INFO | --- Analysis for gnoss-com-a-social-and-semantic-platform took 8.551146507263184s
Availability | SPARQL endpoint availability check for 1121 took 4.649162292480469e-05s
Availability | VoID file availability check for 1121 took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for 1121 took 0.29511189460754395s
Reputation | Calculation of the PageRank for 1121 took 0.021228551864624023s
Interlinking | Calculation of Degree of Connection for 1121 took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for 1121 took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for 1121 took 3.4809112548828125e-05s
Believability | Calculation of trust value for 1121 took 1.0013580322265625e-05s
INFO | --- Analysis for God_ took 3.294260263442993s
Availability | SPARQL endpoint availability check for General Ontology of Linguistic Description took 9.083747863769531e-05s
Availability | VoID file availability check for General Ontology of Linguistic Description took 0.00042247772216796875s
Completeness | Calculation of interlinking completeness for General Ontology of Linguistic Description took 0.2758469581604004s
Reputation | Calculation of the PageRank for General Ontology of Linguistic Description took 0.020905017852783203s
Interlinking | Calculation of Degree of Connection for General Ontology of Linguistic Description took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for General Ontology of Linguistic Description took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for General Ontology of Linguistic Description took 5.4836273193359375e-05s
Believability | Calculation of trust value for General Ontology of Linguistic Description took 9.775161743164062e-06s
INFO | --- Analysis for gold took 4.1807777881622314s
Availability | SPARQL endpoint availability check for GoogleArt wrapper took 4.5299530029296875e-05s
Availability | VoID file availability check for GoogleArt wrapper took 0.00037479400634765625s
Completeness | Calculation of interlinking completeness for GoogleArt wrapper took 0.2995474338531494s
Reputation | Calculation of the PageRank for GoogleArt wrapper took 0.0210268497467041s
Interlinking | Calculation of Degree of Connection for GoogleArt wrapper took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for GoogleArt wrapper took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for GoogleArt wrapper took 7.700920104980469e-05s
Believability | Calculation of trust value for GoogleArt wrapper took 9.5367431640625e-06s
INFO | --- Analysis for googleart-wrapper took 2.9911270141601562s
Availability | SPARQL endpoint availability check for GovAgriBus Denmark took 0.09408974647521973s
Availability | VoID file availability check for GovAgriBus Denmark took 0.000614166259765625s
Completeness | Calculation of interlinking completeness for GovAgriBus Denmark took 0.30197644233703613s
Reputation | Calculation of the PageRank for GovAgriBus Denmark took 0.02077794075012207s
Interlinking | Calculation of Degree of Connection for GovAgriBus Denmark took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for GovAgriBus Denmark took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for GovAgriBus Denmark took 7.534027099609375e-05s
Believability | Calculation of trust value for GovAgriBus Denmark took 9.298324584960938e-06s
INFO | --- Analysis for govagribus-denmark took 34.822957277297974s
Availability | SPARQL endpoint availability check for GovWILD - Government Web Integration for Linked Data took 3.433987855911255s
Availability | VoID file availability check for GovWILD - Government Web Integration for Linked Data took 0.0007026195526123047s
Completeness | Calculation of interlinking completeness for GovWILD - Government Web Integration for Linked Data took 0.3173344135284424s
Reputation | Calculation of the PageRank for GovWILD - Government Web Integration for Linked Data took 0.020905256271362305s
Interlinking | Calculation of Degree of Connection for GovWILD - Government Web Integration for Linked Data took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for GovWILD - Government Web Integration for Linked Data took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for GovWILD - Government Web Integration for Linked Data took 0.00010013580322265625s
Believability | Calculation of trust value for GovWILD - Government Web Integration for Linked Data took 1.0251998901367188e-05s
INFO | --- Analysis for government-web-integration-for-linked-data took 24.30534338951111s
Availability | SPARQL endpoint availability check for GovTrack.us U.S Congress Legislative Data took 1.615900993347168s
Availability | VoID file availability check for GovTrack.us U.S Congress Legislative Data took 0.0006272792816162109s
Completeness | Calculation of interlinking completeness for GovTrack.us U.S Congress Legislative Data took 0.3148386478424072s
Reputation | Calculation of the PageRank for GovTrack.us U.S Congress Legislative Data took 0.020490646362304688s
Interlinking | Calculation of Degree of Connection for GovTrack.us U.S Congress Legislative Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for GovTrack.us U.S Congress Legislative Data took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for GovTrack.us U.S Congress Legislative Data took 9.560585021972656e-05s
Believability | Calculation of trust value for GovTrack.us U.S Congress Legislative Data took 1.0728836059570312e-05s
INFO | --- Analysis for govtrack took 10.712322235107422s
Availability | SPARQL endpoint availability check for greek-administrative-geography took 9.012222290039062e-05s
Availability | VoID file availability check for greek-administrative-geography took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for greek-administrative-geography took 0.308626651763916s
Reputation | Calculation of the PageRank for greek-administrative-geography took 0.021517515182495117s
Interlinking | Calculation of Degree of Connection for greek-administrative-geography took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for greek-administrative-geography took 0.0008106231689453125s
Interlinking | Calculation of Clustering coefficient for greek-administrative-geography took 7.2479248046875e-05s
Believability | Calculation of trust value for greek-administrative-geography took 1.3113021850585938e-05s
INFO | --- Analysis for greek-administrative-geography took 2.7257399559020996s
Availability | SPARQL endpoint availability check for Greek Wordnet took 0.16123366355895996s
Availability | VoID file availability check for Greek Wordnet took 0.0005404949188232422s
Completeness | Calculation of interlinking completeness for Greek Wordnet took 0.303891658782959s
Reputation | Calculation of the PageRank for Greek Wordnet took 0.02077651023864746s
Interlinking | Calculation of Degree of Connection for Greek Wordnet took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Greek Wordnet took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Greek Wordnet took 4.38690185546875e-05s
Believability | Calculation of trust value for Greek Wordnet took 1.0013580322265625e-05s
INFO | --- Analysis for greek-wordnet took 2.9008030891418457s
Availability | SPARQL endpoint availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.2631227970123291s
Availability | VoID file availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.0007042884826660156s
Extra | Recovery of all triples for Greek prisons releases Jan 2018 - Dec 2023 took 12.884667158126831s
Performance | Total latancy measurement for Greek prisons releases Jan 2018 - Dec 2023 took 0.6297216415405273s
Amount of data | Number of triples check for Greek prisons releases Jan 2018 - Dec 2023 took 0.6567642688751221s
Interoperability | New terms check for Greek prisons releases Jan 2018 - Dec 2023 took 1.7904446125030518s
Versatility | Languages check for Greek prisons releases Jan 2018 - Dec 2023 took 1.8984434604644775s
Interpretability | Number of blank nodes check for Greek prisons releases Jan 2018 - Dec 2023 took 0.5404233932495117s
Interpretability | RDF structures check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12983012199401855s
Versatility | Serialization formats check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13171124458312988s
Availability | RDF dump link check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11730718612670898s
License | MR license check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12865090370178223s
License | HR license check for Greek prisons releases Jan 2018 - Dec 2023 took 0.6348817348480225s
Amount of data | Number of property check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12346506118774414s
Understandability | Number of label check for Greek prisons releases Jan 2018 - Dec 2023 took 0.17692065238952637s
Understandability | URI regex check for Greek prisons releases Jan 2018 - Dec 2023 took 0.25312089920043945s
Understandability | Vocabs check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12806963920593262s
Verifiability | Authors check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12626385688781738s
Verifiability | Publishers check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1340649127960205s
Performance | Throughput check for Greek prisons releases Jan 2018 - Dec 2023 took 10.408745765686035s
Amount of data | Check the number of entities for Greek prisons releases Jan 2018 - Dec 2023 took 7.82012939453125e-05s
Verifiability | Contribs. check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12251543998718262s
Interlinking | sameAs chians check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11615538597106934s
Interlinking | skos check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12448000907897949s
Interlinking | skos check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13257646560668945s
Timeliness | dataset update frequency check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1170501708984375s
Currency | Creation date check for Greek prisons releases Jan 2018 - Dec 2023 took 0.26099061965942383s
Currency | Modification date check for Greek prisons releases Jan 2018 - Dec 2023 took 0.24551129341125488s
Rep.Conc. | URIs length for Greek prisons releases Jan 2018 - Dec 2023 took 8.01378083229065s
Interoperability | New vocabularies check for Greek prisons releases Jan 2018 - Dec 2023 took 1.2159347534179688e-05s
Consistency | Deprecated classes/propertiers check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1253526210784912s
Accuracy | Check Functional Property for Greek prisons releases Jan 2018 - Dec 2023 took 0.1276226043701172s
Accuracy | Check Inverse Functional Property for Greek prisons releases Jan 2018 - Dec 2023 took 0.12001180648803711s
Accuracy | Check Empty annotation labels for Greek prisons releases Jan 2018 - Dec 2023 took 2.499499559402466s
Accuracy | Check White space in annotation for Greek prisons releases Jan 2018 - Dec 2023 took 0.28721141815185547s
Accuracy | Check Datatype consistency for Greek prisons releases Jan 2018 - Dec 2023 took 4.870483636856079s
Consistency | Disjoint class check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12201547622680664s
Consistency | Check Misplaced properties for Greek prisons releases Jan 2018 - Dec 2023 took 1.2199785709381104s
Consistency | Check Ontology hijacking for Greek prisons releases Jan 2018 - Dec 2023 took 2.9308712482452393s
Consistency | Check Invalid usage of undefined classes for Greek prisons releases Jan 2018 - Dec 2023 took 1.4119594097137451s
Consistency | Check Invalid usage of undefined properties for Greek prisons releases Jan 2018 - Dec 2023 took 2.653465509414673s
Conciseness | Check Extensional conciseness for Greek prisons releases Jan 2018 - Dec 2023 took 2.9202704429626465s
Security | Sign check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12151503562927246s
Availability | Check URIs Dereferenciability for Greek prisons releases Jan 2018 - Dec 2023 took 9.720155239105225s
Completeness | Calculation of interlinking completeness for Greek prisons releases Jan 2018 - Dec 2023 took 0.2872660160064697s
Reputation | Calculation of the PageRank for Greek prisons releases Jan 2018 - Dec 2023 took 0.021603107452392578s
Interlinking | Calculation of Degree of Connection for Greek prisons releases Jan 2018 - Dec 2023 took 3.719329833984375e-05s
Interlinking | Calculation of Centrality for Greek prisons releases Jan 2018 - Dec 2023 took 0.0007905960083007812s
Interlinking | Calculation of Clustering coefficient for Greek prisons releases Jan 2018 - Dec 2023 took 1.5974044799804688e-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 1.1444091796875e-05s
INFO | --- Analysis for greek_prisons_releases took 90.12287616729736s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 0.7372298240661621s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.00042629241943359375s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.3050367832183838s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.02078986167907715s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 8.368492126464844e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 9.298324584960938e-06s
INFO | --- Analysis for greekchildrensartmuseum took 4.791326522827148s
Availability | SPARQL endpoint availability check for Green Competitiveness (GNOSS) took 5.7697296142578125e-05s
Availability | VoID file availability check for Green Competitiveness (GNOSS) took 0.0008177757263183594s
Completeness | Calculation of interlinking completeness for Green Competitiveness (GNOSS) took 0.28626132011413574s
Reputation | Calculation of the PageRank for Green Competitiveness (GNOSS) took 0.020928621292114258s
Interlinking | Calculation of Degree of Connection for Green Competitiveness (GNOSS) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Green Competitiveness (GNOSS) took 0.0007824897766113281s
Interlinking | Calculation of Clustering coefficient for Green Competitiveness (GNOSS) took 0.0001087188720703125s
Believability | Calculation of trust value for Green Competitiveness (GNOSS) took 1.0728836059570312e-05s
INFO | --- Analysis for green-competitiveness-gnoss took 6.825021028518677s
Availability | SPARQL endpoint availability check for Accommodations in Piedmont (LinkedOpenData.it) took 1.3651902675628662s
Availability | VoID file availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for Accommodations in Piedmont (LinkedOpenData.it) took 0.30980491638183594s
Reputation | Calculation of the PageRank for Accommodations in Piedmont (LinkedOpenData.it) took 0.021215200424194336s
Interlinking | Calculation of Degree of Connection for Accommodations in Piedmont (LinkedOpenData.it) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Accommodations in Piedmont (LinkedOpenData.it) took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Accommodations in Piedmont (LinkedOpenData.it) took 5.269050598144531e-05s
Believability | Calculation of trust value for Accommodations in Piedmont (LinkedOpenData.it) took 1.5020370483398438e-05s
INFO | --- Analysis for grrp took 4.239766597747803s
Availability | SPARQL endpoint availability check for Accommodations in Tuscany (LinkedOpenData.it) took 1.2504374980926514s
Availability | VoID file availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for Accommodations in Tuscany (LinkedOpenData.it) took 0.2872638702392578s
Reputation | Calculation of the PageRank for Accommodations in Tuscany (LinkedOpenData.it) took 0.02077341079711914s
Interlinking | Calculation of Degree of Connection for Accommodations in Tuscany (LinkedOpenData.it) took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Accommodations in Tuscany (LinkedOpenData.it) took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for Accommodations in Tuscany (LinkedOpenData.it) took 7.462501525878906e-05s
Believability | Calculation of trust value for Accommodations in Tuscany (LinkedOpenData.it) took 1.0251998901367188e-05s
INFO | --- Analysis for grrt took 3.9840304851531982s
Availability | SPARQL endpoint availability check for Geological Timescale took 1.142855167388916s
Availability | VoID file availability check for Geological Timescale took 0.0007152557373046875s
Extra | Recovery of all triples for Geological Timescale took 2.879729747772217s
Performance | Total latancy measurement for Geological Timescale took 4.9126057624816895s
Amount of data | Number of triples check for Geological Timescale took 1.034168004989624s
Interoperability | New terms check for Geological Timescale took 2.1955173015594482s
Versatility | Languages check for Geological Timescale took 1.0688107013702393s
Interpretability | Number of blank nodes check for Geological Timescale took 1.0542550086975098s
Security | Check HTTPS for Geological Timescale took 0.8976900577545166s
Interpretability | RDF structures check for Geological Timescale took 0.9759302139282227s
Versatility | Serialization formats check for Geological Timescale took 0.9910590648651123s
Availability | RDF dump link check for Geological Timescale took 1.7371742725372314s
License | MR license check for Geological Timescale took 0.9678151607513428s
License | HR license check for Geological Timescale took 0.997117280960083s
Amount of data | Number of property check for Geological Timescale took 0.9508841037750244s
Understandability | Number of label check for Geological Timescale took 1.232485055923462s
Understandability | URI regex check for Geological Timescale took 2.0127384662628174s
Understandability | Vocabs check for Geological Timescale took 0.9873185157775879s
Verifiability | Authors check for Geological Timescale took 0.9908194541931152s
Verifiability | Publishers check for Geological Timescale took 0.9798269271850586s
Performance | Throughput check for Geological Timescale took 13.509532690048218s
Amount of data | Check the number of entities for Geological Timescale took 0.020850658416748047s
Verifiability | Contribs. check for Geological Timescale took 0.9688808917999268s
Interlinking | sameAs chians check for Geological Timescale took 0.9816117286682129s
Interlinking | skos check for Geological Timescale took 0.4089198112487793s
Interlinking | skos check for Geological Timescale took 0.4305698871612549s
Timeliness | dataset update frequency check for Geological Timescale took 0.981410026550293s
Currency | Creation date check for Geological Timescale took 1.3827133178710938s
Currency | Modification date check for Geological Timescale took 0.9449546337127686s
Rep.Conc. | URIs length for Geological Timescale took 2.66469669342041s
Interoperability | New vocabularies check for Geological Timescale took 1.5757217407226562s
Consistency | Deprecated classes/propertiers check for Geological Timescale took 0.9621405601501465s
Accuracy | Check Functional Property for Geological Timescale took 1.3272087574005127s
Accuracy | Check Inverse Functional Property for Geological Timescale took 0.9904646873474121s
Accuracy | Check Empty annotation labels for Geological Timescale took 1.3053858280181885s
Accuracy | Check White space in annotation for Geological Timescale took 0.015527009963989258s
Accuracy | Check Datatype consistency for Geological Timescale took 0.07375621795654297s
Consistency | Disjoint class check for Geological Timescale took 0.9886035919189453s
Consistency | Check Misplaced properties for Geological Timescale took 1.9415943622589111s
Consistency | Misplaced classes for Geological Timescale took 1.1293306350708008s
Consistency | Check Ontology hijacking for Geological Timescale took 1.6852893829345703s
Consistency | Check Invalid usage of undefined classes for Geological Timescale took 1.2108745574951172s
Consistency | Check Invalid usage of undefined properties for Geological Timescale took 2.2508819103240967s
Conciseness | Check Extensional conciseness for Geological Timescale took 0.05159592628479004s
Conciseness | Check Intensional conciseness for Geological Timescale took 1.0034050941467285s
Security | Sign check for Geological Timescale took 0.9944770336151123s
Availability | Check URIs Dereferenciability for Geological Timescale took 2.946030616760254s
Completeness | Calculation of interlinking completeness for Geological Timescale took 0.28564929962158203s
Reputation | Calculation of the PageRank for Geological Timescale took 0.020725727081298828s
Interlinking | Calculation of Degree of Connection for Geological Timescale took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Geological Timescale took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for Geological Timescale took 7.462501525878906e-05s
Interoperability | Check the re-using of existing vocabs for Geological Timescale took 1.585245132446289s
Believability | Calculation of trust value for Geological Timescale took 1.33514404296875e-05s
INFO | --- Analysis for GTS took 125.93374443054199s
Availability | SPARQL endpoint availability check for Geological Timescale Ontology took 4.57763671875e-05s
Availability | VoID file availability check for Geological Timescale Ontology took 0.0007386207580566406s
Completeness | Calculation of interlinking completeness for Geological Timescale Ontology took 0.29151415824890137s
Reputation | Calculation of the PageRank for Geological Timescale Ontology took 0.02078413963317871s
Interlinking | Calculation of Degree of Connection for Geological Timescale Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Geological Timescale Ontology took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Geological Timescale Ontology took 3.814697265625e-05s
Believability | Calculation of trust value for Geological Timescale Ontology took 1.4543533325195312e-05s
INFO | --- Analysis for GTS-ont took 2.944566488265991s
Availability | SPARQL endpoint availability check for GUTSTOK  took 9.632110595703125e-05s
Availability | VoID file availability check for GUTSTOK  took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for GUTSTOK  took 0.26294684410095215s
Reputation | Calculation of the PageRank for GUTSTOK  took 0.02242875099182129s
Interlinking | Calculation of Degree of Connection for GUTSTOK  took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for GUTSTOK  took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for GUTSTOK  took 3.719329833984375e-05s
Believability | Calculation of trust value for GUTSTOK  took 1.4781951904296875e-05s
INFO | --- Analysis for Guillaume_Forget took 2.709768295288086s
Availability | SPARQL endpoint availability check for Project Gutenberg took 8.797645568847656e-05s
Availability | VoID file availability check for Project Gutenberg took 0.0007433891296386719s
Completeness | Calculation of interlinking completeness for Project Gutenberg took 0.2663872241973877s
Reputation | Calculation of the PageRank for Project Gutenberg took 0.022191524505615234s
Interlinking | Calculation of Degree of Connection for Project Gutenberg took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Project Gutenberg took 0.0008435249328613281s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg took 8.0108642578125e-05s
Believability | Calculation of trust value for Project Gutenberg took 1.3589859008789062e-05s
INFO | --- Analysis for gutenberg took 8.73172640800476s
Availability | SPARQL endpoint availability check for Global WordNet Association Interlingual Index took 4.744529724121094e-05s
Availability | VoID file availability check for Global WordNet Association Interlingual Index took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for Global WordNet Association Interlingual Index took 0.2994203567504883s
Reputation | Calculation of the PageRank for Global WordNet Association Interlingual Index took 0.02098393440246582s
Interlinking | Calculation of Degree of Connection for Global WordNet Association Interlingual Index took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Global WordNet Association Interlingual Index took 0.00081634521484375s
Interlinking | Calculation of Clustering coefficient for Global WordNet Association Interlingual Index took 4.00543212890625e-05s
Believability | Calculation of trust value for Global WordNet Association Interlingual Index took 1.0013580322265625e-05s
INFO | --- Analysis for gwa-ili took 6.488724946975708s
Availability | SPARQL endpoint availability check for Geographically Weighted Regression Model took 0.0001621246337890625s
Availability | VoID file availability check for Geographically Weighted Regression Model took 0.0007128715515136719s
Completeness | Calculation of interlinking completeness for Geographically Weighted Regression Model took 0.28907227516174316s
Reputation | Calculation of the PageRank for Geographically Weighted Regression Model took 0.02060723304748535s
Interlinking | Calculation of Degree of Connection for Geographically Weighted Regression Model took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Geographically Weighted Regression Model took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Geographically Weighted Regression Model took 4.100799560546875e-05s
Believability | Calculation of trust value for Geographically Weighted Regression Model took 1.430511474609375e-05s
INFO | --- Analysis for GWR took 17.862417936325073s
Availability | SPARQL endpoint availability check for High Accuracy Surface Modeling took 8.869171142578125e-05s
Availability | VoID file availability check for High Accuracy Surface Modeling took 0.0004012584686279297s
Completeness | Calculation of interlinking completeness for High Accuracy Surface Modeling took 0.28484487533569336s
Reputation | Calculation of the PageRank for High Accuracy Surface Modeling took 0.02097630500793457s
Interlinking | Calculation of Degree of Connection for High Accuracy Surface Modeling took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for High Accuracy Surface Modeling took 0.0007908344268798828s
Interlinking | Calculation of Clustering coefficient for High Accuracy Surface Modeling took 3.6716461181640625e-05s
Believability | Calculation of trust value for High Accuracy Surface Modeling took 9.298324584960938e-06s
INFO | --- Analysis for HASM took 20.43669295310974s
Availability | SPARQL endpoint availability check for HealthCare Ontology took 3.7308852672576904s
Availability | VoID file availability check for HealthCare Ontology took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for HealthCare Ontology took 0.29276466369628906s
Reputation | Calculation of the PageRank for HealthCare Ontology took 0.02055072784423828s
Interlinking | Calculation of Degree of Connection for HealthCare Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for HealthCare Ontology took 0.0008075237274169922s
Interlinking | Calculation of Clustering coefficient for HealthCare Ontology took 3.981590270996094e-05s
Believability | Calculation of trust value for HealthCare Ontology took 1.4066696166992188e-05s
INFO | --- Analysis for HealthCare_Ontology took 6.953262567520142s
Availability | SPARQL endpoint availability check for Meriterm Heart Failure Multilingual Terminology took 9.131431579589844e-05s
Availability | VoID file availability check for Meriterm Heart Failure Multilingual Terminology took 0.0005528926849365234s
Completeness | Calculation of interlinking completeness for Meriterm Heart Failure Multilingual Terminology took 0.2864081859588623s
Reputation | Calculation of the PageRank for Meriterm Heart Failure Multilingual Terminology took 0.02060222625732422s
Interlinking | Calculation of Degree of Connection for Meriterm Heart Failure Multilingual Terminology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Meriterm Heart Failure Multilingual Terminology took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Meriterm Heart Failure Multilingual Terminology took 6.151199340820312e-05s
Believability | Calculation of trust value for Meriterm Heart Failure Multilingual Terminology took 1.5020370483398438e-05s
INFO | --- Analysis for heartfailure took 3.2849323749542236s
Availability | SPARQL endpoint availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 21.792075634002686s
Availability | VoID file availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0008363723754882812s
Completeness | Calculation of interlinking completeness for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.3496677875518799s
Reputation | Calculation of the PageRank for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.021237850189208984s
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.1457672119140625e-05s
Interlinking | Calculation of Centrality for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 6.175041198730469e-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.4543533325195312e-05s
INFO | --- Analysis for hebis-bibliographic-resources took 119.10043168067932s
Availability | SPARQL endpoint availability check for Hedatuz took 0.2619771957397461s
Availability | VoID file availability check for Hedatuz took 0.0005640983581542969s
Completeness | Calculation of interlinking completeness for Hedatuz took 0.2893950939178467s
Reputation | Calculation of the PageRank for Hedatuz took 0.02100396156311035s
Interlinking | Calculation of Degree of Connection for Hedatuz took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Hedatuz took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Hedatuz took 4.0531158447265625e-05s
Believability | Calculation of trust value for Hedatuz took 1.1444091796875e-05s
INFO | --- Analysis for hedatuz took 3.3203747272491455s
Availability | SPARQL endpoint availability check for Hellenic Fire Brigade took 0.1647205352783203s
Availability | VoID file availability check for Hellenic Fire Brigade took 0.0005893707275390625s
Completeness | Calculation of interlinking completeness for Hellenic Fire Brigade took 0.2802562713623047s
Reputation | Calculation of the PageRank for Hellenic Fire Brigade took 0.02099919319152832s
Interlinking | Calculation of Degree of Connection for Hellenic Fire Brigade took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Hellenic Fire Brigade took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Hellenic Fire Brigade took 0.00013184547424316406s
Believability | Calculation of trust value for Hellenic Fire Brigade took 1.0728836059570312e-05s
INFO | --- Analysis for hellenic-fire-brigade took 2.836332321166992s
Availability | SPARQL endpoint availability check for Hellenic Police took 0.025790929794311523s
Availability | VoID file availability check for Hellenic Police took 0.00046062469482421875s
Completeness | Calculation of interlinking completeness for Hellenic Police took 0.3160271644592285s
Reputation | Calculation of the PageRank for Hellenic Police took 0.0219118595123291s
Interlinking | Calculation of Degree of Connection for Hellenic Police took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Hellenic Police took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Hellenic Police took 0.0001323223114013672s
Believability | Calculation of trust value for Hellenic Police took 9.298324584960938e-06s
INFO | --- Analysis for hellenic-police took 2.829505681991577s
Availability | SPARQL endpoint availability check for Hermos took 4.38690185546875e-05s
Availability | VoID file availability check for Hermos took 0.0006394386291503906s
Completeness | Calculation of interlinking completeness for Hermos took 0.31461358070373535s
Reputation | Calculation of the PageRank for Hermos took 0.020621776580810547s
Interlinking | Calculation of Degree of Connection for Hermos took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Hermos took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Hermos took 3.0994415283203125e-05s
Believability | Calculation of trust value for Hermos took 1.239776611328125e-05s
INFO | --- Analysis for Hermos took 3.181248664855957s
Availability | SPARQL endpoint availability check for Himanshu Mahawar took 9.083747863769531e-05s
Availability | VoID file availability check for Himanshu Mahawar took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for Himanshu Mahawar took 0.3440511226654053s
Reputation | Calculation of the PageRank for Himanshu Mahawar took 0.021479368209838867s
Interlinking | Calculation of Degree of Connection for Himanshu Mahawar took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Himanshu Mahawar took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Himanshu Mahawar took 3.24249267578125e-05s
Believability | Calculation of trust value for Himanshu Mahawar took 1.2159347534179688e-05s
INFO | --- Analysis for Himanshu_Mahawar took 2.7178497314453125s
Availability | SPARQL endpoint availability check for HITO took 0.4061436653137207s
Availability | VoID file availability check for HITO took 0.0006341934204101562s
Extra | Recovery of all triples for HITO took 1.7501730918884277s
Performance | Total latancy measurement for HITO took 0.9323713779449463s
Amount of data | Number of triples check for HITO took 0.18563580513000488s
Interoperability | New terms check for HITO took 1.4554426670074463s
Versatility | Languages check for HITO took 0.18950796127319336s
Interpretability | Number of blank nodes check for HITO took 0.1903057098388672s
Interpretability | RDF structures check for HITO took 0.19688653945922852s
Versatility | Serialization formats check for HITO took 0.19284725189208984s
Availability | RDF dump link check for HITO took 0.2094111442565918s
License | MR license check for HITO took 0.1911025047302246s
License | HR license check for HITO took 0.2300276756286621s
Amount of data | Number of property check for HITO took 0.180436372756958s
Understandability | Number of label check for HITO took 0.20630884170532227s
Understandability | URI regex check for HITO took 0.3812093734741211s
Understandability | Vocabs check for HITO took 0.17155051231384277s
Verifiability | Authors check for HITO took 0.18743085861206055s
Verifiability | Publishers check for HITO took 0.2051851749420166s
Performance | Throughput check for HITO took 11.329644680023193s
Amount of data | Check the number of entities for HITO took 7.343292236328125e-05s
Verifiability | Contribs. check for HITO took 0.20169448852539062s
Interlinking | sameAs chians check for HITO took 0.1693263053894043s
Interlinking | skos check for HITO took 0.19630098342895508s
Interlinking | skos check for HITO took 0.18804073333740234s
Timeliness | dataset update frequency check for HITO took 0.1907520294189453s
Currency | Creation date check for HITO took 0.3554050922393799s
Currency | Modification date check for HITO took 0.38955140113830566s
Rep.Conc. | URIs length for HITO took 1.0428528785705566s
Interoperability | New vocabularies check for HITO took 6.4373016357421875e-06s
Consistency | Deprecated classes/propertiers check for HITO took 0.19677448272705078s
Accuracy | Check Functional Property for HITO took 0.1826927661895752s
Accuracy | Check Inverse Functional Property for HITO took 0.1716899871826172s
Accuracy | Check Empty annotation labels for HITO took 0.4869544506072998s
Accuracy | Check White space in annotation for HITO took 0.013388633728027344s
Accuracy | Check Datatype consistency for HITO took 0.07542896270751953s
Consistency | Disjoint class check for HITO took 0.1877155303955078s
Consistency | Check Misplaced properties for HITO took 0.5099339485168457s
Consistency | Misplaced classes for HITO took 0.3825984001159668s
Consistency | Check Ontology hijacking for HITO took 1.6786630153656006s
Consistency | Check Invalid usage of undefined classes for HITO took 1.2283306121826172s
Consistency | Check Invalid usage of undefined properties for HITO took 1.4909374713897705s
Conciseness | Check Extensional conciseness for HITO took 0.06232929229736328s
Conciseness | Check Intensional conciseness for HITO took 0.20865869522094727s
Security | Sign check for HITO took 0.1983036994934082s
Availability | Check URIs Dereferenciability for HITO took 2618.148115634918s
Completeness | Calculation of interlinking completeness for HITO took 0.7562487125396729s
Reputation | Calculation of the PageRank for HITO took 0.020900726318359375s
Interlinking | Calculation of Degree of Connection for HITO took 2.3365020751953125e-05s
Interlinking | Calculation of Centrality for HITO took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for HITO took 9.1552734375e-05s
Interoperability | Check the re-using of existing vocabs for HITO took 1.9073486328125e-06s
Believability | Calculation of trust value for HITO took 1.4781951904296875e-05s
INFO | --- Analysis for hito took 2673.174304008484s
Availability | SPARQL endpoint availability check for Hoa Thịnh Phát took 15.195648908615112s
Availability | VoID file availability check for Hoa Thịnh Phát took 0.0007035732269287109s
Completeness | Calculation of interlinking completeness for Hoa Thịnh Phát took 0.31930065155029297s
Reputation | Calculation of the PageRank for Hoa Thịnh Phát took 0.020744800567626953s
Interlinking | Calculation of Degree of Connection for Hoa Thịnh Phát took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Hoa Thịnh Phát took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for Hoa Thịnh Phát took 4.4345855712890625e-05s
Believability | Calculation of trust value for Hoa Thịnh Phát took 1.3828277587890625e-05s
INFO | --- Analysis for Hoa_Thinh_Phat took 48.74801802635193s
Availability | SPARQL endpoint availability check for gseg took 4.839897155761719e-05s
Availability | VoID file availability check for gseg took 0.0007150173187255859s
Completeness | Calculation of interlinking completeness for gseg took 0.29110097885131836s
Reputation | Calculation of the PageRank for gseg took 0.02064681053161621s
Interlinking | Calculation of Degree of Connection for gseg took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for gseg took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for gseg took 3.409385681152344e-05s
Believability | Calculation of trust value for gseg took 1.3113021850585938e-05s
INFO | --- Analysis for hongse took 3.4214885234832764s
Availability | SPARQL endpoint availability check for COURAGE Dataset took 1.3401148319244385s
Availability | VoID file availability check for COURAGE Dataset took 0.0007982254028320312s
Completeness | Calculation of interlinking completeness for COURAGE Dataset took 0.328632116317749s
Reputation | Calculation of the PageRank for COURAGE Dataset took 0.021986722946166992s
Interlinking | Calculation of Degree of Connection for COURAGE Dataset took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for COURAGE Dataset took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for COURAGE Dataset took 3.4332275390625e-05s
Believability | Calculation of trust value for COURAGE Dataset took 1.2636184692382812e-05s
INFO | --- Analysis for http:cultural-opposition.eu took 5.293052911758423s
Availability | SPARQL endpoint availability check for RoadTrb took 4.410743713378906e-05s
Availability | VoID file availability check for RoadTrb took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for RoadTrb took 0.3191053867340088s
Reputation | Calculation of the PageRank for RoadTrb took 0.020885944366455078s
Interlinking | Calculation of Degree of Connection for RoadTrb took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for RoadTrb took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for RoadTrb took 3.3855438232421875e-05s
Believability | Calculation of trust value for RoadTrb took 1.2636184692382812e-05s
INFO | --- Analysis for http:data.linkedeodata.euroadidStateRoadD010Turkey-1 took 2.788109540939331s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0008673667907714844s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.27805614471435547s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.02095961570739746s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007984638214111328s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 4.1961669921875e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for http:guava.iis.sinica.edu.twr4r took 29.095031261444092s
Availability | SPARQL endpoint availability check for Polictical History of Pakistan took 8.940696716308594e-05s
Availability | VoID file availability check for Polictical History of Pakistan took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for Polictical History of Pakistan took 0.29810571670532227s
Reputation | Calculation of the PageRank for Polictical History of Pakistan took 0.020674705505371094s
Interlinking | Calculation of Degree of Connection for Polictical History of Pakistan took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Polictical History of Pakistan took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for Polictical History of Pakistan took 3.457069396972656e-05s
Believability | Calculation of trust value for Polictical History of Pakistan took 1.0728836059570312e-05s
INFO | --- Analysis for http:pakistan.com took 2.714209794998169s
Availability | SPARQL endpoint availability check for CEDICT took 4.38690185546875e-05s
Availability | VoID file availability check for CEDICT took 0.0006852149963378906s
Completeness | Calculation of interlinking completeness for CEDICT took 0.286435604095459s
Reputation | Calculation of the PageRank for CEDICT took 0.020446300506591797s
Interlinking | Calculation of Degree of Connection for CEDICT took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for CEDICT took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for CEDICT took 3.361701965332031e-05s
Believability | Calculation of trust value for CEDICT took 1.3589859008789062e-05s
INFO | --- Analysis for http:rdf.naturallexicon.orgzhontCedict took 4.070204257965088s
Availability | SPARQL endpoint availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.486877679824829s
Availability | VoID file availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.30780482292175293s
Reputation | Calculation of the PageRank for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.02073502540588379s
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.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 7.367134094238281e-05s
Believability | Calculation of trust value for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.2874603271484375e-05s
INFO | --- Analysis for http:sensormeasurement.appspot.comdatasetnaturopathy-dataset took 5.051793098449707s
Availability | SPARQL endpoint availability check for Pakistan Stock Market Data took 4.220008850097656e-05s
Availability | VoID file availability check for Pakistan Stock Market Data took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for Pakistan Stock Market Data took 0.29105091094970703s
Reputation | Calculation of the PageRank for Pakistan Stock Market Data took 0.022007465362548828s
Interlinking | Calculation of Degree of Connection for Pakistan Stock Market Data took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Pakistan Stock Market Data took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Pakistan Stock Market Data took 3.337860107421875e-05s
Believability | Calculation of trust value for Pakistan Stock Market Data took 1.3113021850585938e-05s
INFO | --- Analysis for http:www.atif-sajjad.comSemster-Project# took 3.2073285579681396s
Availability | SPARQL endpoint availability check for Grand Slam Knowledge Graph took 4.291534423828125e-05s
Availability | VoID file availability check for Grand Slam Knowledge Graph took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Grand Slam Knowledge Graph took 0.294147253036499s
Reputation | Calculation of the PageRank for Grand Slam Knowledge Graph took 0.020434856414794922s
Interlinking | Calculation of Degree of Connection for Grand Slam Knowledge Graph took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Grand Slam Knowledge Graph took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Grand Slam Knowledge Graph took 3.409385681152344e-05s
Believability | Calculation of trust value for Grand Slam Knowledge Graph took 1.1444091796875e-05s
INFO | --- Analysis for http:www.fateh_fahad_adeel.comgrandSlam took 2.759309768676758s
Availability | SPARQL endpoint availability check for Soccer Dataset took 4.3392181396484375e-05s
Availability | VoID file availability check for Soccer Dataset took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for Soccer Dataset took 0.28583359718322754s
Reputation | Calculation of the PageRank for Soccer Dataset took 0.021452665328979492s
Interlinking | Calculation of Degree of Connection for Soccer Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Soccer Dataset took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Soccer Dataset took 3.314018249511719e-05s
Believability | Calculation of trust value for Soccer Dataset took 1.4543533325195312e-05s
INFO | --- Analysis for http:www.msm.com took 2.7007153034210205s
Availability | SPARQL endpoint availability check for Game Ontology took 4.601478576660156e-05s
Availability | VoID file availability check for Game Ontology took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for Game Ontology took 0.28458309173583984s
Reputation | Calculation of the PageRank for Game Ontology took 0.02087259292602539s
Interlinking | Calculation of Degree of Connection for Game Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Game Ontology took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Game Ontology took 3.743171691894531e-05s
Believability | Calculation of trust value for Game Ontology took 1.621246337890625e-05s
INFO | --- Analysis for http:www.RAG.comgameonto# took 3.3847036361694336s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 5.340576171875e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0006535053253173828s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.3098163604736328s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.020778179168701172s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.528594970703125e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.33514404296875e-05s
INFO | --- Analysis for http:www.semanticweb.orgambrishontologies202010untitled-ontology-24 took 3.342082977294922s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 8.630752563476562e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.3134000301361084s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0207064151763916s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.457069396972656e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.2636184692382812e-05s
INFO | --- Analysis for http:www.semanticweb.orgarchanaontologies20215untitled-ontology-6 took 2.6967360973358154s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 9.1552734375e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.3193533420562744s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.021902799606323242s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.4332275390625e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.4543533325195312e-05s
INFO | --- Analysis for http:www.semanticweb.orgmcaontologies20188untitled-ontology-47 took 2.827970504760742s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 0.00011277198791503906s
Availability | VoID file availability check for Indian Biodiversity took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2898681163787842s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02072596549987793s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.6716461181640625e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.7642974853515625e-05s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIO took 2.671703577041626s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 9.036064147949219e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2951340675354004s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.022336483001708984s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.552436828613281e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.239776611328125e-05s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIOp=summary took 2.610139846801758s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 9.34600830078125e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0013859272003173828s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.30119848251342773s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02055191993713379s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.457069396972656e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.4781951904296875e-05s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBDsubmissions1downloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb took 4.235222816467285s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.3392181396484375e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.31211376190185547s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020819425582885742s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.4809112548828125e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.4066696166992188e-05s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBIOsubmissions1downloadapikey=66c2aec1-4044-4900-979d-6f529857554a took 2.76265549659729s
Availability | SPARQL endpoint availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.00010728836059570312s
Availability | VoID file availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0006399154663085938s
Completeness | Calculation of interlinking completeness for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.3027834892272949s
Reputation | Calculation of the PageRank for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.020635128021240234s
Interlinking | Calculation of Degree of Connection for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0008075237274169922s
Interlinking | Calculation of Clustering coefficient for Diretrizes organizacionais de métodos quantitativos e computação científica took 3.743171691894531e-05s
Believability | Calculation of trust value for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.4781951904296875e-05s
INFO | --- Analysis for https:orcid.org0000-0002-6194-9354 took 4.354993581771851s
Availability | SPARQL endpoint availability check for Bookkeeping took 1.0503499507904053s
Availability | VoID file availability check for Bookkeeping took 0.0005855560302734375s
Completeness | Calculation of interlinking completeness for Bookkeeping took 0.3232860565185547s
Reputation | Calculation of the PageRank for Bookkeeping took 0.023186683654785156s
Interlinking | Calculation of Degree of Connection for Bookkeeping took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Bookkeeping took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Bookkeeping took 3.62396240234375e-05s
Believability | Calculation of trust value for Bookkeeping took 1.3828277587890625e-05s
INFO | --- Analysis for https:raw.githubusercontent.comGVogelerbookkeepingmasterbookkeeping.ttl took 4.237756252288818s
Availability | SPARQL endpoint availability check for Legal Ontology took 8.845329284667969e-05s
Availability | VoID file availability check for Legal Ontology took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for Legal Ontology took 0.2799496650695801s
Reputation | Calculation of the PageRank for Legal Ontology took 0.020554542541503906s
Interlinking | Calculation of Degree of Connection for Legal Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Legal Ontology took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Legal Ontology took 4.458427429199219e-05s
Believability | Calculation of trust value for Legal Ontology took 1.3828277587890625e-05s
INFO | --- Analysis for https:w3id.orgdefNyOnLegal# took 3.3998730182647705s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 4.6253204345703125e-05s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.00067138671875s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.30116963386535645s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.021581411361694336s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 8.726119995117188e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 1.4543533325195312e-05s
INFO | --- Analysis for https:www.childrensartmuseum.grLD-project took 2.9752564430236816s
Availability | SPARQL endpoint availability check for Writer Luigi Usai took 8.988380432128906e-05s
Availability | VoID file availability check for Writer Luigi Usai took 0.0007047653198242188s
Completeness | Calculation of interlinking completeness for Writer Luigi Usai took 0.28248047828674316s
Reputation | Calculation of the PageRank for Writer Luigi Usai took 0.02132868766784668s
Interlinking | Calculation of Degree of Connection for Writer Luigi Usai took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Writer Luigi Usai took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for Writer Luigi Usai took 3.933906555175781e-05s
Believability | Calculation of trust value for Writer Luigi Usai took 1.3589859008789062e-05s
INFO | --- Analysis for https:www.luigiusai.itlinked-dataluigiusai took 2.954936981201172s
Availability | SPARQL endpoint availability check for Hungarian National Library (NSZL) catalog took 0.42481136322021484s
Availability | VoID file availability check for Hungarian National Library (NSZL) catalog took 0.0005278587341308594s
Completeness | Calculation of interlinking completeness for Hungarian National Library (NSZL) catalog took 0.3308713436126709s
Reputation | Calculation of the PageRank for Hungarian National Library (NSZL) catalog took 0.020717144012451172s
Interlinking | Calculation of Degree of Connection for Hungarian National Library (NSZL) catalog took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Hungarian National Library (NSZL) catalog took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for Hungarian National Library (NSZL) catalog took 0.00011992454528808594s
Believability | Calculation of trust value for Hungarian National Library (NSZL) catalog took 1.4066696166992188e-05s
INFO | --- Analysis for hungarian-national-library-catalog took 3.075728416442871s
Availability | SPARQL endpoint availability check for IATE RDF took 8.96453857421875e-05s
Availability | VoID file availability check for IATE RDF took 0.0005543231964111328s
Completeness | Calculation of interlinking completeness for IATE RDF took 0.31095314025878906s
Reputation | Calculation of the PageRank for IATE RDF took 0.027663469314575195s
Interlinking | Calculation of Degree of Connection for IATE RDF took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for IATE RDF took 0.0009770393371582031s
Interlinking | Calculation of Clustering coefficient for IATE RDF took 4.7206878662109375e-05s
Believability | Calculation of trust value for IATE RDF took 1.0728836059570312e-05s
INFO | --- Analysis for iate-rdf took 2.9549050331115723s
Availability | SPARQL endpoint availability check for IATI as Linked Data took 6.37792706489563s
Availability | VoID file availability check for IATI as Linked Data took 0.000415802001953125s
Completeness | Calculation of interlinking completeness for IATI as Linked Data took 0.2911825180053711s
Reputation | Calculation of the PageRank for IATI as Linked Data took 0.020496606826782227s
Interlinking | Calculation of Degree of Connection for IATI as Linked Data took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for IATI as Linked Data took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for IATI as Linked Data took 8.869171142578125e-05s
Believability | Calculation of trust value for IATI as Linked Data took 1.4066696166992188e-05s
INFO | --- Analysis for iati-as-linked-data took 13.48576831817627s
Availability | SPARQL endpoint availability check for ICANE took 0.2953605651855469s
Availability | VoID file availability check for ICANE took 0.0009205341339111328s
Completeness | Calculation of interlinking completeness for ICANE took 0.2697124481201172s
Reputation | Calculation of the PageRank for ICANE took 0.021245241165161133s
Interlinking | Calculation of Degree of Connection for ICANE took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ICANE took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for ICANE took 9.584426879882812e-05s
Believability | Calculation of trust value for ICANE took 1.0013580322265625e-05s
INFO | --- Analysis for icane took 3.8234305381774902s
Availability | SPARQL endpoint availability check for ichoose took 0.15596222877502441s
Availability | VoID file availability check for ichoose took 0.0003085136413574219s
Completeness | Calculation of interlinking completeness for ichoose took 0.315868616104126s
Reputation | Calculation of the PageRank for ichoose took 0.020863771438598633s
Interlinking | Calculation of Degree of Connection for ichoose took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ichoose took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for ichoose took 7.486343383789062e-05s
Believability | Calculation of trust value for ichoose took 1.52587890625e-05s
INFO | --- Analysis for ichoose took 42.02879452705383s
Availability | SPARQL endpoint availability check for The Iconology Dataset took 0.41412830352783203s
Availability | VoID file availability check for The Iconology Dataset took 0.0005970001220703125s
Extra | Recovery of all triples for The Iconology Dataset took 3.704145908355713s
Performance | Total latancy measurement for The Iconology Dataset took 0.45003604888916016s
Amount of data | Number of triples check for The Iconology Dataset took 0.17591404914855957s
Interoperability | New terms check for The Iconology Dataset took 1.396559238433838s
Versatility | Languages check for The Iconology Dataset took 0.6569905281066895s
Interpretability | Number of blank nodes check for The Iconology Dataset took 0.17196393013000488s
Interpretability | RDF structures check for The Iconology Dataset took 0.1243734359741211s
Versatility | Serialization formats check for The Iconology Dataset took 0.09766745567321777s
Availability | RDF dump link check for The Iconology Dataset took 0.08502531051635742s
License | MR license check for The Iconology Dataset took 0.11008501052856445s
License | HR license check for The Iconology Dataset took 0.34213829040527344s
Amount of data | Number of property check for The Iconology Dataset took 0.09989809989929199s
Understandability | Number of label check for The Iconology Dataset took 0.14217829704284668s
Understandability | URI regex check for The Iconology Dataset took 0.16484665870666504s
Understandability | Vocabs check for The Iconology Dataset took 0.0947122573852539s
Verifiability | Authors check for The Iconology Dataset took 0.09778118133544922s
Verifiability | Publishers check for The Iconology Dataset took 0.09018850326538086s
Performance | Throughput check for The Iconology Dataset took 10.459753274917603s
Amount of data | Check the number of entities for The Iconology Dataset took 0.00042438507080078125s
Verifiability | Contribs. check for The Iconology Dataset took 0.0895376205444336s
Interlinking | sameAs chians check for The Iconology Dataset took 0.09740352630615234s
Interlinking | skos check for The Iconology Dataset took 0.0924675464630127s
Interlinking | skos check for The Iconology Dataset took 0.08693552017211914s
Timeliness | dataset update frequency check for The Iconology Dataset took 0.09006834030151367s
Currency | Creation date check for The Iconology Dataset took 0.18339014053344727s
Currency | Modification date check for The Iconology Dataset took 0.1908249855041504s
Rep.Conc. | URIs length for The Iconology Dataset took 1.2699837684631348s
Interoperability | New vocabularies check for The Iconology Dataset took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for The Iconology Dataset took 0.08294820785522461s
Accuracy | Check Empty annotation labels for The Iconology Dataset took 0.2613041400909424s
Accuracy | Check White space in annotation for The Iconology Dataset took 0.01635575294494629s
Accuracy | Check Datatype consistency for The Iconology Dataset took 0.4302504062652588s
Consistency | Disjoint class check for The Iconology Dataset took 0.08068323135375977s
Consistency | Check Misplaced properties for The Iconology Dataset took 0.1511220932006836s
Consistency | Misplaced classes for The Iconology Dataset took 0.8703346252441406s
Consistency | Check Ontology hijacking for The Iconology Dataset took 1.5440607070922852s
Consistency | Check Invalid usage of undefined classes for The Iconology Dataset took 1.2249338626861572s
Consistency | Check Invalid usage of undefined properties for The Iconology Dataset took 1.3069846630096436s
Conciseness | Check Extensional conciseness for The Iconology Dataset took 0.29399824142456055s
Security | Sign check for The Iconology Dataset took 0.08553719520568848s
Availability | Check URIs Dereferenciability for The Iconology Dataset took 2628.5620408058167s
Completeness | Calculation of interlinking completeness for The Iconology Dataset took 0.6752042770385742s
Reputation | Calculation of the PageRank for The Iconology Dataset took 0.021456003189086914s
Interlinking | Calculation of Degree of Connection for The Iconology Dataset took 2.7418136596679688e-05s
Interlinking | Calculation of Centrality for The Iconology Dataset took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for The Iconology Dataset took 2.2172927856445312e-05s
Interoperability | Check the re-using of existing vocabs for The Iconology Dataset took 2.1457672119140625e-06s
Believability | Calculation of trust value for The Iconology Dataset took 1.049041748046875e-05s
INFO | --- Analysis for iconology-dataset took 2684.035895586014s
Availability | SPARQL endpoint availability check for IdRef: Sudoc authority data took 6.222724914550781e-05s
Availability | VoID file availability check for IdRef: Sudoc authority data took 0.0007646083831787109s
Completeness | Calculation of interlinking completeness for IdRef: Sudoc authority data took 0.32843637466430664s
Reputation | Calculation of the PageRank for IdRef: Sudoc authority data took 0.02059197425842285s
Interlinking | Calculation of Degree of Connection for IdRef: Sudoc authority data took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for IdRef: Sudoc authority data took 0.0008158683776855469s
Interlinking | Calculation of Clustering coefficient for IdRef: Sudoc authority data took 8.487701416015625e-05s
Believability | Calculation of trust value for IdRef: Sudoc authority data took 1.430511474609375e-05s
INFO | --- Analysis for idreffr took 4.037667512893677s
Availability | SPARQL endpoint availability check for Intercontinental Dictionary Series took 1.5290753841400146s
Availability | VoID file availability check for Intercontinental Dictionary Series took 0.00030541419982910156s
Completeness | Calculation of interlinking completeness for Intercontinental Dictionary Series took 0.2649962902069092s
Reputation | Calculation of the PageRank for Intercontinental Dictionary Series took 0.02092456817626953s
Interlinking | Calculation of Degree of Connection for Intercontinental Dictionary Series took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Intercontinental Dictionary Series took 0.0008018016815185547s
Interlinking | Calculation of Clustering coefficient for Intercontinental Dictionary Series took 5.888938903808594e-05s
Believability | Calculation of trust value for Intercontinental Dictionary Series took 1.4543533325195312e-05s
INFO | --- Analysis for ids took 4.743646621704102s
Availability | SPARQL endpoint availability check for ietflang took 7.033348083496094e-05s
Availability | VoID file availability check for ietflang took 0.0008647441864013672s
Completeness | Calculation of interlinking completeness for ietflang took 0.3089168071746826s
Reputation | Calculation of the PageRank for ietflang took 0.0210115909576416s
Interlinking | Calculation of Degree of Connection for ietflang took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for ietflang took 0.0008475780487060547s
Interlinking | Calculation of Clustering coefficient for ietflang took 5.435943603515625e-05s
Believability | Calculation of trust value for ietflang took 1.2874603271484375e-05s
INFO | --- Analysis for ietflang took 14.614376783370972s
Availability | SPARQL endpoint availability check for Index Graecorum Vocabulorum in LiLa took 0.5524108409881592s
Availability | VoID file availability check for Index Graecorum Vocabulorum in LiLa took 0.00043201446533203125s
Completeness | Calculation of interlinking completeness for Index Graecorum Vocabulorum in LiLa took 0.26102566719055176s
Reputation | Calculation of the PageRank for Index Graecorum Vocabulorum in LiLa took 0.022075414657592773s
Interlinking | Calculation of Degree of Connection for Index Graecorum Vocabulorum in LiLa took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Index Graecorum Vocabulorum in LiLa took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Index Graecorum Vocabulorum in LiLa took 4.3392181396484375e-05s
Believability | Calculation of trust value for Index Graecorum Vocabulorum in LiLa took 1.0251998901367188e-05s
INFO | --- Analysis for IGVLL took 4.17150092124939s
Availability | SPARQL endpoint availability check for 3LGM² IHE Ontology took 0.5896482467651367s
Availability | VoID file availability check for 3LGM² IHE Ontology took 0.0006017684936523438s
Extra | Recovery of all triples for 3LGM² IHE Ontology took 1.137688398361206s
Performance | Total latancy measurement for 3LGM² IHE Ontology took 0.9280006885528564s
Amount of data | Number of triples check for 3LGM² IHE Ontology took 0.18996834754943848s
Interoperability | New terms check for 3LGM² IHE Ontology took 1.4543638229370117s
Versatility | Languages check for 3LGM² IHE Ontology took 0.19623851776123047s
Interpretability | Number of blank nodes check for 3LGM² IHE Ontology took 0.18035078048706055s
Interpretability | RDF structures check for 3LGM² IHE Ontology took 0.20516347885131836s
Versatility | Serialization formats check for 3LGM² IHE Ontology took 0.17348122596740723s
Availability | RDF dump link check for 3LGM² IHE Ontology took 0.20019745826721191s
License | MR license check for 3LGM² IHE Ontology took 0.1905803680419922s
License | HR license check for 3LGM² IHE Ontology took 0.20923900604248047s
Amount of data | Number of property check for 3LGM² IHE Ontology took 0.19315719604492188s
Understandability | Number of label check for 3LGM² IHE Ontology took 0.2214341163635254s
Understandability | URI regex check for 3LGM² IHE Ontology took 0.37891530990600586s
Understandability | Vocabs check for 3LGM² IHE Ontology took 0.18355321884155273s
Verifiability | Authors check for 3LGM² IHE Ontology took 0.18451857566833496s
Verifiability | Publishers check for 3LGM² IHE Ontology took 0.2011277675628662s
Performance | Throughput check for 3LGM² IHE Ontology took 11.40300440788269s
Amount of data | Check the number of entities for 3LGM² IHE Ontology took 7.152557373046875e-05s
Verifiability | Contribs. check for 3LGM² IHE Ontology took 0.1877589225769043s
Interlinking | sameAs chians check for 3LGM² IHE Ontology took 0.18279361724853516s
Interlinking | skos check for 3LGM² IHE Ontology took 0.20253658294677734s
Interlinking | skos check for 3LGM² IHE Ontology took 0.1883080005645752s
Timeliness | dataset update frequency check for 3LGM² IHE Ontology took 0.1917741298675537s
Currency | Creation date check for 3LGM² IHE Ontology took 0.39142417907714844s
Currency | Modification date check for 3LGM² IHE Ontology took 0.3833181858062744s
Rep.Conc. | URIs length for 3LGM² IHE Ontology took 0.8054473400115967s
Interoperability | New vocabularies check for 3LGM² IHE Ontology took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for 3LGM² IHE Ontology took 0.17795133590698242s
Accuracy | Check Functional Property for 3LGM² IHE Ontology took 0.17964792251586914s
Accuracy | Check Inverse Functional Property for 3LGM² IHE Ontology took 0.1900920867919922s
Accuracy | Check Empty annotation labels for 3LGM² IHE Ontology took 0.3379859924316406s
Accuracy | Check White space in annotation for 3LGM² IHE Ontology took 0.0023081302642822266s
Accuracy | Check Datatype consistency for 3LGM² IHE Ontology took 0.050812721252441406s
Consistency | Disjoint class check for 3LGM² IHE Ontology took 0.1898181438446045s
Consistency | Check Misplaced properties for 3LGM² IHE Ontology took 0.4574916362762451s
Consistency | Misplaced classes for 3LGM² IHE Ontology took 0.2678680419921875s
Consistency | Check Ontology hijacking for 3LGM² IHE Ontology took 1.5552723407745361s
Consistency | Check Invalid usage of undefined classes for 3LGM² IHE Ontology took 1.2480316162109375s
Consistency | Check Invalid usage of undefined properties for 3LGM² IHE Ontology took 1.504521369934082s
Conciseness | Check Extensional conciseness for 3LGM² IHE Ontology took 0.032412052154541016s
Conciseness | Check Intensional conciseness for 3LGM² IHE Ontology took 0.18447661399841309s
Security | Sign check for 3LGM² IHE Ontology took 0.18543601036071777s
Availability | Check URIs Dereferenciability for 3LGM² IHE Ontology took 404.34909081459045s
Completeness | Calculation of interlinking completeness for 3LGM² IHE Ontology took 0.3885049819946289s
Reputation | Calculation of the PageRank for 3LGM² IHE Ontology took 0.022645235061645508s
Interlinking | Calculation of Degree of Connection for 3LGM² IHE Ontology took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for 3LGM² IHE Ontology took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for 3LGM² IHE Ontology took 3.647804260253906e-05s
Interoperability | Check the re-using of existing vocabs for 3LGM² IHE Ontology took 1.9073486328125e-06s
Believability | Calculation of trust value for 3LGM² IHE Ontology took 1.2159347534179688e-05s
INFO | --- Analysis for IHE took 451.0174870491028s
Availability | SPARQL endpoint availability check for Test Site, LOD Lab 317 took 2.2987759113311768s
Availability | VoID file availability check for Test Site, LOD Lab 317 took 0.0007772445678710938s
Extra | Recovery of all triples for Test Site, LOD Lab 317 took 6.573779344558716s
Performance | Total latancy measurement for Test Site, LOD Lab 317 took 7.38085675239563s
Amount of data | Number of triples check for Test Site, LOD Lab 317 took 13.583345890045166s
Interoperability | New terms check for Test Site, LOD Lab 317 took 8.601237297058105s
Versatility | Languages check for Test Site, LOD Lab 317 took 61.447749376297s
Interpretability | Number of blank nodes check for Test Site, LOD Lab 317 took 1.6058294773101807s
Security | Check HTTPS for Test Site, LOD Lab 317 took 0.9829401969909668s
Interpretability | RDF structures check for Test Site, LOD Lab 317 took 1.5902314186096191s
Versatility | Serialization formats check for Test Site, LOD Lab 317 took 1.5152034759521484s
Availability | RDF dump link check for Test Site, LOD Lab 317 took 1.4900357723236084s
License | MR license check for Test Site, LOD Lab 317 took 1.5155551433563232s
License | HR license check for Test Site, LOD Lab 317 took 1.8202252388000488s
Amount of data | Number of property check for Test Site, LOD Lab 317 took 1.5207674503326416s
Understandability | Number of label check for Test Site, LOD Lab 317 took 1.6478476524353027s
Understandability | URI regex check for Test Site, LOD Lab 317 took 2.9603610038757324s
Understandability | Vocabs check for Test Site, LOD Lab 317 took 1.4678425788879395s
Verifiability | Authors check for Test Site, LOD Lab 317 took 1.6145813465118408s
Verifiability | Publishers check for Test Site, LOD Lab 317 took 1.457369089126587s
Performance | Throughput check for Test Site, LOD Lab 317 took 14.76565408706665s
Amount of data | Check the number of entities for Test Site, LOD Lab 317 took 0.00010275840759277344s
Verifiability | Contribs. check for Test Site, LOD Lab 317 took 1.5373363494873047s
Interlinking | sameAs chians check for Test Site, LOD Lab 317 took 1.620896816253662s
Interlinking | skos check for Test Site, LOD Lab 317 took 1.550260066986084s
Interlinking | skos check for Test Site, LOD Lab 317 took 1.5172338485717773s
Timeliness | dataset update frequency check for Test Site, LOD Lab 317 took 1.5742506980895996s
Currency | Creation date check for Test Site, LOD Lab 317 took 2.96156644821167s
Currency | Modification date check for Test Site, LOD Lab 317 took 2.9948995113372803s
Rep.Conc. | URIs length for Test Site, LOD Lab 317 took 35.072545528411865s
Interoperability | New vocabularies check for Test Site, LOD Lab 317 took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for Test Site, LOD Lab 317 took 1.4524431228637695s
Accuracy | Check Functional Property for Test Site, LOD Lab 317 took 1.4756910800933838s
Accuracy | Check Inverse Functional Property for Test Site, LOD Lab 317 took 1.4815473556518555s
Accuracy | Check Empty annotation labels for Test Site, LOD Lab 317 took 2.9179489612579346s
Accuracy | Check White space in annotation for Test Site, LOD Lab 317 took 0.03038811683654785s
Accuracy | Check Datatype consistency for Test Site, LOD Lab 317 took 0.02964639663696289s
Consistency | Disjoint class check for Test Site, LOD Lab 317 took 1.4716014862060547s
Consistency | Check Misplaced properties for Test Site, LOD Lab 317 took 22.873748779296875s
Consistency | Misplaced classes for Test Site, LOD Lab 317 took 1.8313519954681396s
Consistency | Check Ontology hijacking for Test Site, LOD Lab 317 took 4.488091468811035s
Consistency | Check Invalid usage of undefined classes for Test Site, LOD Lab 317 took 1.2360084056854248s
Consistency | Check Invalid usage of undefined properties for Test Site, LOD Lab 317 took 24.25253987312317s
Conciseness | Check Extensional conciseness for Test Site, LOD Lab 317 took 0.035570383071899414s
Conciseness | Check Intensional conciseness for Test Site, LOD Lab 317 took 2.041285276412964s
Security | Sign check for Test Site, LOD Lab 317 took 1.5437917709350586s
Availability | Check URIs Dereferenciability for Test Site, LOD Lab 317 took 9.805781841278076s
Completeness | Calculation of interlinking completeness for Test Site, LOD Lab 317 took 0.6169376373291016s
Reputation | Calculation of the PageRank for Test Site, LOD Lab 317 took 0.021959304809570312s
Interlinking | Calculation of Degree of Connection for Test Site, LOD Lab 317 took 2.288818359375e-05s
Interlinking | Calculation of Centrality for Test Site, LOD Lab 317 took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for Test Site, LOD Lab 317 took 4.38690185546875e-05s
Interoperability | Check the re-using of existing vocabs for Test Site, LOD Lab 317 took 1.9073486328125e-06s
Believability | Calculation of trust value for Test Site, LOD Lab 317 took 1.5735626220703125e-05s
INFO | --- Analysis for iislod-test took 492.6934666633606s
Availability | SPARQL endpoint availability check for Interpretation of Land Use Data in Ordos City took 9.393692016601562e-05s
Availability | VoID file availability check for Interpretation of Land Use Data in Ordos City took 0.0007386207580566406s
Completeness | Calculation of interlinking completeness for Interpretation of Land Use Data in Ordos City took 0.2788228988647461s
Reputation | Calculation of the PageRank for Interpretation of Land Use Data in Ordos City took 0.021618127822875977s
Interlinking | Calculation of Degree of Connection for Interpretation of Land Use Data in Ordos City took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Interpretation of Land Use Data in Ordos City took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Interpretation of Land Use Data in Ordos City took 3.361701965332031e-05s
Believability | Calculation of trust value for Interpretation of Land Use Data in Ordos City took 1.33514404296875e-05s
INFO | --- Analysis for ILUSOC took 21.390272617340088s
Availability | SPARQL endpoint availability check for im@sparql took 8.28461217880249s
Availability | VoID file availability check for im@sparql took 0.0007343292236328125s
Completeness | Calculation of interlinking completeness for im@sparql took 0.33891940116882324s
Reputation | Calculation of the PageRank for im@sparql took 0.0230557918548584s
Interlinking | Calculation of Degree of Connection for im@sparql took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for im@sparql took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for im@sparql took 3.504753112792969e-05s
Believability | Calculation of trust value for im@sparql took 1.52587890625e-05s
INFO | --- Analysis for im@sparql took 15.660885572433472s
Availability | SPARQL endpoint availability check for imagery bailingniao took 4.267692565917969e-05s
Availability | VoID file availability check for imagery bailingniao took 0.0008149147033691406s
Completeness | Calculation of interlinking completeness for imagery bailingniao took 0.2773144245147705s
Reputation | Calculation of the PageRank for imagery bailingniao took 0.021164894104003906s
Interlinking | Calculation of Degree of Connection for imagery bailingniao took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for imagery bailingniao took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for imagery bailingniao took 3.337860107421875e-05s
Believability | Calculation of trust value for imagery bailingniao took 1.4543533325195312e-05s
INFO | --- Analysis for imagery_bailingniao took 3.4263617992401123s
Availability | SPARQL endpoint availability check for Imagesnippets Image Descriptions took 1.1131329536437988s
Availability | VoID file availability check for Imagesnippets Image Descriptions took 0.0006825923919677734s
Extra | Recovery of all triples for Imagesnippets Image Descriptions took 21.241057872772217s
Performance | Total latancy measurement for Imagesnippets Image Descriptions took 3.4116148948669434s
Amount of data | Number of triples check for Imagesnippets Image Descriptions took 9.618682146072388s
Interoperability | New terms check for Imagesnippets Image Descriptions took 2.1708147525787354s
Versatility | Languages check for Imagesnippets Image Descriptions took 19.548972368240356s
Interpretability | Number of blank nodes check for Imagesnippets Image Descriptions took 8.176367282867432s
Security | Check HTTPS for Imagesnippets Image Descriptions took 0.6774516105651855s
Interpretability | RDF structures check for Imagesnippets Image Descriptions took 0.7289547920227051s
Versatility | Serialization formats check for Imagesnippets Image Descriptions took 0.7057652473449707s
Availability | RDF dump link check for Imagesnippets Image Descriptions took 0.7157862186431885s
License | MR license check for Imagesnippets Image Descriptions took 0.723823070526123s
License | HR license check for Imagesnippets Image Descriptions took 30.709980487823486s
Amount of data | Number of property check for Imagesnippets Image Descriptions took 0.72149658203125s
Understandability | Number of label check for Imagesnippets Image Descriptions took 2.4963929653167725s
Understandability | URI regex check for Imagesnippets Image Descriptions took 1.490980625152588s
Understandability | Vocabs check for Imagesnippets Image Descriptions took 0.7277872562408447s
Verifiability | Authors check for Imagesnippets Image Descriptions took 0.7483363151550293s
Verifiability | Publishers check for Imagesnippets Image Descriptions took 0.7659194469451904s
Performance | Throughput check for Imagesnippets Image Descriptions took 14.365684032440186s
Amount of data | Check the number of entities for Imagesnippets Image Descriptions took 7.486343383789062e-05s
Verifiability | Contribs. check for Imagesnippets Image Descriptions took 0.7301836013793945s
Interlinking | sameAs chians check for Imagesnippets Image Descriptions took 0.728867769241333s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.7633345127105713s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.6690549850463867s
Timeliness | dataset update frequency check for Imagesnippets Image Descriptions took 0.7243881225585938s
Currency | Creation date check for Imagesnippets Image Descriptions took 1.446666955947876s
Currency | Modification date check for Imagesnippets Image Descriptions took 1.5150566101074219s
Rep.Conc. | URIs length for Imagesnippets Image Descriptions took 32.990238904953s
Interoperability | New vocabularies check for Imagesnippets Image Descriptions took 1.2874603271484375e-05s
Consistency | Deprecated classes/propertiers check for Imagesnippets Image Descriptions took 0.7248973846435547s
Accuracy | Check Functional Property for Imagesnippets Image Descriptions took 0.6890885829925537s
Accuracy | Check Inverse Functional Property for Imagesnippets Image Descriptions took 0.7331335544586182s
Accuracy | Check Empty annotation labels for Imagesnippets Image Descriptions took 12.417414426803589s
Accuracy | Check White space in annotation for Imagesnippets Image Descriptions took 2.2557475566864014s
Accuracy | Check Datatype consistency for Imagesnippets Image Descriptions took 4.472598075866699s
Consistency | Disjoint class check for Imagesnippets Image Descriptions took 0.6924095153808594s
Consistency | Check Misplaced properties for Imagesnippets Image Descriptions took 7.883144378662109s
Consistency | Check Ontology hijacking for Imagesnippets Image Descriptions took 5.247324228286743s
Consistency | Check Invalid usage of undefined classes for Imagesnippets Image Descriptions took 1.4573466777801514s
Consistency | Check Invalid usage of undefined properties for Imagesnippets Image Descriptions took 8.498778104782104s
Conciseness | Check Extensional conciseness for Imagesnippets Image Descriptions took 2.906947374343872s
Security | Sign check for Imagesnippets Image Descriptions took 0.7440576553344727s
Availability | Check URIs Dereferenciability for Imagesnippets Image Descriptions took 19.71382784843445s
Completeness | Calculation of interlinking completeness for Imagesnippets Image Descriptions took 0.35654115676879883s
Reputation | Calculation of the PageRank for Imagesnippets Image Descriptions took 0.023818016052246094s
Interlinking | Calculation of Degree of Connection for Imagesnippets Image Descriptions took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for Imagesnippets Image Descriptions took 0.0007984638214111328s
Interlinking | Calculation of Clustering coefficient for Imagesnippets Image Descriptions took 0.00010848045349121094s
Interoperability | Check the re-using of existing vocabs for Imagesnippets Image Descriptions took 2.384185791015625e-06s
Believability | Calculation of trust value for Imagesnippets Image Descriptions took 1.4543533325195312e-05s
INFO | --- Analysis for imagesnippets took 385.46193051338196s
Availability | SPARQL endpoint availability check for International Monetary Fund (IMF) Linked Data took 0.12601470947265625s
Availability | VoID file availability check for International Monetary Fund (IMF) Linked Data took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for International Monetary Fund (IMF) Linked Data took 0.3392946720123291s
Reputation | Calculation of the PageRank for International Monetary Fund (IMF) Linked Data took 0.02068781852722168s
Interlinking | Calculation of Degree of Connection for International Monetary Fund (IMF) Linked Data took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for International Monetary Fund (IMF) Linked Data took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for International Monetary Fund (IMF) Linked Data took 9.369850158691406e-05s
Believability | Calculation of trust value for International Monetary Fund (IMF) Linked Data took 1.3828277587890625e-05s
INFO | --- Analysis for imf-linked-data took 2.9018571376800537s
Availability | SPARQL endpoint availability check for MD Imtiaz Ahammad took 4.6253204345703125e-05s
Availability | VoID file availability check for MD Imtiaz Ahammad took 0.0005481243133544922s
Completeness | Calculation of interlinking completeness for MD Imtiaz Ahammad took 0.2913999557495117s
Reputation | Calculation of the PageRank for MD Imtiaz Ahammad took 0.02082681655883789s
Interlinking | Calculation of Degree of Connection for MD Imtiaz Ahammad took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for MD Imtiaz Ahammad took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for MD Imtiaz Ahammad took 1.3589859008789062e-05s
Believability | Calculation of trust value for MD Imtiaz Ahammad took 1.1682510375976562e-05s
INFO | --- Analysis for Imtiaz took 2.766649007797241s
Availability | SPARQL endpoint availability check for Royalty Free Music took 5.245208740234375e-05s
Availability | VoID file availability check for Royalty Free Music took 0.0007855892181396484s
Completeness | Calculation of interlinking completeness for Royalty Free Music took 0.3110818862915039s
Reputation | Calculation of the PageRank for Royalty Free Music took 0.020743608474731445s
Interlinking | Calculation of Degree of Connection for Royalty Free Music took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Royalty Free Music took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Royalty Free Music took 3.266334533691406e-05s
Believability | Calculation of trust value for Royalty Free Music took 1.0728836059570312e-05s
INFO | --- Analysis for inaudio.org took 4.315019607543945s
Availability | SPARQL endpoint availability check for Index Thomisticus Treebank in LiLa took 0.4884378910064697s
Availability | VoID file availability check for Index Thomisticus Treebank in LiLa took 0.0006480216979980469s
Completeness | Calculation of interlinking completeness for Index Thomisticus Treebank in LiLa took 0.2933938503265381s
Reputation | Calculation of the PageRank for Index Thomisticus Treebank in LiLa took 0.02312946319580078s
Interlinking | Calculation of Degree of Connection for Index Thomisticus Treebank in LiLa took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Index Thomisticus Treebank in LiLa took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for Index Thomisticus Treebank in LiLa took 4.601478576660156e-05s
Believability | Calculation of trust value for Index Thomisticus Treebank in LiLa took 1.3828277587890625e-05s
INFO | --- Analysis for IndexThomisticusTreebank took 4.122451543807983s
Availability | SPARQL endpoint availability check for IneveryCREA, la comunidad de la creatividad educativa took 4.76837158203125e-05s
Availability | VoID file availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.00041794776916503906s
Completeness | Calculation of interlinking completeness for IneveryCREA, la comunidad de la creatividad educativa took 0.300703763961792s
Reputation | Calculation of the PageRank for IneveryCREA, la comunidad de la creatividad educativa took 0.0206906795501709s
Interlinking | Calculation of Degree of Connection for IneveryCREA, la comunidad de la creatividad educativa took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for IneveryCREA, la comunidad de la creatividad educativa took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for IneveryCREA, la comunidad de la creatividad educativa took 0.00011396408081054688s
Believability | Calculation of trust value for IneveryCREA, la comunidad de la creatividad educativa took 1.4781951904296875e-05s
INFO | --- Analysis for ineverycrea took 19.00260353088379s
Availability | SPARQL endpoint availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 4.744529724121094e-05s
Availability | VoID file availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0007479190826416016s
Completeness | Calculation of interlinking completeness for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.2902555465698242s
Reputation | Calculation of the PageRank for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.020808935165405273s
Interlinking | Calculation of Degree of Connection for IneveryCREA Argentina, la comunidad de la creatividad educativa took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.00012445449829101562s
Believability | Calculation of trust value for IneveryCREA Argentina, la comunidad de la creatividad educativa took 1.3828277587890625e-05s
INFO | --- Analysis for ineverycrea-argentina took 12.036254405975342s
Availability | SPARQL endpoint availability check for Influence Tracker Dataset took 271.7894113063812s
Availability | VoID file availability check for Influence Tracker Dataset took 0.0007650852203369141s
Completeness | Calculation of interlinking completeness for Influence Tracker Dataset took 0.2904200553894043s
Reputation | Calculation of the PageRank for Influence Tracker Dataset took 0.022099733352661133s
Interlinking | Calculation of Degree of Connection for Influence Tracker Dataset took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Influence Tracker Dataset took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Influence Tracker Dataset took 9.322166442871094e-05s
Believability | Calculation of trust value for Influence Tracker Dataset took 1.5735626220703125e-05s
INFO | --- Analysis for influence-tracker-dataset took 567.449033498764s
Availability | SPARQL endpoint availability check for Instance Hub Fiscal Years took 4.673004150390625e-05s
Availability | VoID file availability check for Instance Hub Fiscal Years took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for Instance Hub Fiscal Years took 0.2850065231323242s
Reputation | Calculation of the PageRank for Instance Hub Fiscal Years took 0.020951032638549805s
Interlinking | Calculation of Degree of Connection for Instance Hub Fiscal Years took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Instance Hub Fiscal Years took 0.0008258819580078125s
Interlinking | Calculation of Clustering coefficient for Instance Hub Fiscal Years took 5.91278076171875e-05s
Believability | Calculation of trust value for Instance Hub Fiscal Years took 1.1205673217773438e-05s
INFO | --- Analysis for instance-hub-fiscal-years took 2.848054885864258s
Availability | SPARQL endpoint availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.00011587142944335938s
Availability | VoID file availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0006513595581054688s
Completeness | Calculation of interlinking completeness for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.3929123878479004s
Reputation | Calculation of the PageRank for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.021584510803222656s
Interlinking | Calculation of Degree of Connection for Interactive Maps, a collection of interactive flash maps (GNOSS) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0007448196411132812s
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 1.1444091796875e-05s
INFO | --- Analysis for interactivemaps-gnoss took 15.007805109024048s
Availability | SPARQL endpoint availability check for intervalue took 0.1461491584777832s
Availability | VoID file availability check for intervalue took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for intervalue took 0.2992992401123047s
Reputation | Calculation of the PageRank for intervalue took 0.02087998390197754s
Interlinking | Calculation of Degree of Connection for intervalue took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for intervalue took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for intervalue took 7.510185241699219e-05s
Believability | Calculation of trust value for intervalue took 1.3828277587890625e-05s
INFO | --- Analysis for intervalue took 2.910780429840088s
Availability | SPARQL endpoint availability check for Inztrow took 4.696846008300781e-05s
Availability | VoID file availability check for Inztrow took 0.0007061958312988281s
Completeness | Calculation of interlinking completeness for Inztrow took 0.2928597927093506s
Reputation | Calculation of the PageRank for Inztrow took 0.02062821388244629s
Interlinking | Calculation of Degree of Connection for Inztrow took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Inztrow took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Inztrow took 3.814697265625e-05s
Believability | Calculation of trust value for Inztrow took 1.239776611328125e-05s
INFO | --- Analysis for Inztrow took 4.138923168182373s
Availability | SPARQL endpoint availability check for IPBES Assessments Ontology took 4.982948303222656e-05s
Availability | VoID file availability check for IPBES Assessments Ontology took 0.00041103363037109375s
Completeness | Calculation of interlinking completeness for IPBES Assessments Ontology took 0.2734060287475586s
Reputation | Calculation of the PageRank for IPBES Assessments Ontology took 0.020955562591552734s
Interlinking | Calculation of Degree of Connection for IPBES Assessments Ontology took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for IPBES Assessments Ontology took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for IPBES Assessments Ontology took 3.5762786865234375e-05s
Believability | Calculation of trust value for IPBES Assessments Ontology took 9.775161743164062e-06s
INFO | --- Analysis for ipbes took 3.8164896965026855s
Availability | SPARQL endpoint availability check for IPTC NewsCodes took 0.00010538101196289062s
Availability | VoID file availability check for IPTC NewsCodes took 0.0006554126739501953s
Completeness | Calculation of interlinking completeness for IPTC NewsCodes took 0.325239896774292s
Reputation | Calculation of the PageRank for IPTC NewsCodes took 0.02165961265563965s
Interlinking | Calculation of Degree of Connection for IPTC NewsCodes took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for IPTC NewsCodes took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for IPTC NewsCodes took 4.673004150390625e-05s
Believability | Calculation of trust value for IPTC NewsCodes took 1.4066696166992188e-05s
INFO | --- Analysis for iptc-newscodes took 4.024059772491455s
Availability | SPARQL endpoint availability check for iServe: Linked Services Registry took 2.4319324493408203s
Availability | VoID file availability check for iServe: Linked Services Registry took 0.0008180141448974609s
Completeness | Calculation of interlinking completeness for iServe: Linked Services Registry took 0.2970852851867676s
Reputation | Calculation of the PageRank for iServe: Linked Services Registry took 0.020620107650756836s
Interlinking | Calculation of Degree of Connection for iServe: Linked Services Registry took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for iServe: Linked Services Registry took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for iServe: Linked Services Registry took 9.989738464355469e-05s
Believability | Calculation of trust value for iServe: Linked Services Registry took 1.049041748046875e-05s
INFO | --- Analysis for iserve took 9.273385286331177s
Availability | SPARQL endpoint availability check for ISIC V4 took 20.936410188674927s
Availability | VoID file availability check for ISIC V4 took 0.0009870529174804688s
Completeness | Calculation of interlinking completeness for ISIC V4 took 0.3103163242340088s
Reputation | Calculation of the PageRank for ISIC V4 took 0.022069692611694336s
Interlinking | Calculation of Degree of Connection for ISIC V4 took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for ISIC V4 took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for ISIC V4 took 4.744529724121094e-05s
Believability | Calculation of trust value for ISIC V4 took 1.049041748046875e-05s
INFO | --- Analysis for isic-v4 took 116.0410943031311s
Availability | SPARQL endpoint availability check for ISIL->DBpedia took 5.793571472167969e-05s
Availability | VoID file availability check for ISIL->DBpedia took 0.0007138252258300781s
Completeness | Calculation of interlinking completeness for ISIL->DBpedia took 0.29152727127075195s
Reputation | Calculation of the PageRank for ISIL->DBpedia took 0.020933151245117188s
Interlinking | Calculation of Degree of Connection for ISIL->DBpedia took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for ISIL->DBpedia took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for ISIL->DBpedia took 7.557868957519531e-05s
Believability | Calculation of trust value for ISIL->DBpedia took 1.049041748046875e-05s
INFO | --- Analysis for isil-dbpedia took 4.999101400375366s
Availability | SPARQL endpoint availability check for Published subjects for languages in ISO 639 took 4.553794860839844e-05s
Availability | VoID file availability check for Published subjects for languages in ISO 639 took 0.0007090568542480469s
Completeness | Calculation of interlinking completeness for Published subjects for languages in ISO 639 took 0.2861485481262207s
Reputation | Calculation of the PageRank for Published subjects for languages in ISO 639 took 0.020572900772094727s
Interlinking | Calculation of Degree of Connection for Published subjects for languages in ISO 639 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Published subjects for languages in ISO 639 took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Published subjects for languages in ISO 639 took 4.00543212890625e-05s
Believability | Calculation of trust value for Published subjects for languages in ISO 639 took 1.0251998901367188e-05s
INFO | --- Analysis for iso-639-oasis took 3.4785819053649902s
Availability | SPARQL endpoint availability check for ISOcat took 0.00010395050048828125s
Availability | VoID file availability check for ISOcat took 0.0007441043853759766s
Completeness | Calculation of interlinking completeness for ISOcat took 0.29668474197387695s
Reputation | Calculation of the PageRank for ISOcat took 0.020452499389648438s
Interlinking | Calculation of Degree of Connection for ISOcat took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for ISOcat took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for ISOcat took 6.628036499023438e-05s
Believability | Calculation of trust value for ISOcat took 1.4066696166992188e-05s
INFO | --- Analysis for isocat took 7.967745304107666s
Availability | SPARQL endpoint availability check for ISOcat-metadata took 4.482269287109375e-05s
Availability | VoID file availability check for ISOcat-metadata took 0.0006241798400878906s
Completeness | Calculation of interlinking completeness for ISOcat-metadata took 0.29022789001464844s
Reputation | Calculation of the PageRank for ISOcat-metadata took 0.02086019515991211s
Interlinking | Calculation of Degree of Connection for ISOcat-metadata took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for ISOcat-metadata took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for ISOcat-metadata took 4.00543212890625e-05s
Believability | Calculation of trust value for ISOcat-metadata took 1.4781951904296875e-05s
INFO | --- Analysis for isocat-metadata took 5.135907888412476s
Availability | SPARQL endpoint availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.13603782653808594s
Availability | VoID file availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0007655620574951172s
Extra | Recovery of all triples for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 5.333240032196045s
Performance | Total latancy measurement for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.28002476692199707s
Amount of data | Number of triples check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1434009075164795s
Interoperability | New terms check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.8639721870422363s
Versatility | Languages check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 90.28797054290771s
Interpretability | Number of blank nodes check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09178042411804199s
Security | Check HTTPS for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.03301191329956055s
Interpretability | RDF structures check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.11330437660217285s
Versatility | Serialization formats check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.12819457054138184s
Availability | RDF dump link check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09225749969482422s
License | MR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.14249181747436523s
License | HR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 90.60045027732849s
Amount of data | Number of property check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0932164192199707s
Understandability | Number of label check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.2499830722808838s
Understandability | URI regex check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.30353212356567383s
Understandability | Vocabs check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1294393539428711s
Verifiability | Authors check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.13872170448303223s
Verifiability | Publishers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0910646915435791s
Performance | Throughput check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.419838905334473s
Amount of data | Check the number of entities for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 7.319450378417969e-05s
Verifiability | Contribs. check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.12868905067443848s
Interlinking | sameAs chians check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.18882083892822266s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.37991809844970703s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3403944969177246s
Timeliness | dataset update frequency check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.13295388221740723s
Currency | Creation date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.18625879287719727s
Currency | Modification date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.10246729850769043s
Rep.Conc. | URIs length for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 12.788955926895142s
Interoperability | New vocabularies check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09112977981567383s
Accuracy | Check Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09509563446044922s
Accuracy | Check Inverse Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09481000900268555s
Accuracy | Check Empty annotation labels for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.7804136276245117s
Accuracy | Check White space in annotation for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3135406970977783s
Accuracy | Check Datatype consistency for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2735121250152588s
Consistency | Disjoint class check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08689260482788086s
Consistency | Check Misplaced properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 8.87252163887024s
Consistency | Misplaced classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.9249258041381836s
Consistency | Check Ontology hijacking for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.769988775253296s
Consistency | Check Invalid usage of undefined classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.261498212814331s
Consistency | Check Invalid usage of undefined properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.006572484970093s
Conciseness | Check Extensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.29976916313171387s
Conciseness | Check Intensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.10122489929199219s
Security | Sign check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1062479019165039s
Availability | Check URIs Dereferenciability for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 8.918893575668335s
Completeness | Calculation of interlinking completeness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3673970699310303s
Reputation | Calculation of the PageRank for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.022930383682250977s
Interlinking | Calculation of Degree of Connection for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0007905960083007812s
Interlinking | Calculation of Clustering coefficient for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.00011014938354492188s
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.4066696166992188e-05s
INFO | --- Analysis for ispra-lod-place took 439.22309708595276s
Availability | SPARQL endpoint availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.05695652961730957s
Availability | VoID file availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.0003044605255126953s
Extra | Recovery of all triples for ISPRA - The Italian Data Buoy Network (RON) took 5.280128479003906s
Performance | Total latancy measurement for ISPRA - The Italian Data Buoy Network (RON) took 0.28072667121887207s
Amount of data | Number of triples check for ISPRA - The Italian Data Buoy Network (RON) took 0.14681148529052734s
Interoperability | New terms check for ISPRA - The Italian Data Buoy Network (RON) took 2.837745428085327s
Versatility | Languages check for ISPRA - The Italian Data Buoy Network (RON) took 92.10565662384033s
Interpretability | Number of blank nodes check for ISPRA - The Italian Data Buoy Network (RON) took 0.10207056999206543s
Security | Check HTTPS for ISPRA - The Italian Data Buoy Network (RON) took 0.032314300537109375s
Interpretability | RDF structures check for ISPRA - The Italian Data Buoy Network (RON) took 0.11520695686340332s
Versatility | Serialization formats check for ISPRA - The Italian Data Buoy Network (RON) took 0.09900832176208496s
Availability | RDF dump link check for ISPRA - The Italian Data Buoy Network (RON) took 0.09452414512634277s
License | MR license check for ISPRA - The Italian Data Buoy Network (RON) took 0.1474161148071289s
License | HR license check for ISPRA - The Italian Data Buoy Network (RON) took 90.61587834358215s
Amount of data | Number of property check for ISPRA - The Italian Data Buoy Network (RON) took 0.09312748908996582s
Understandability | Number of label check for ISPRA - The Italian Data Buoy Network (RON) took 1.227787971496582s
Understandability | URI regex check for ISPRA - The Italian Data Buoy Network (RON) took 0.3181600570678711s
Understandability | Vocabs check for ISPRA - The Italian Data Buoy Network (RON) took 0.13533639907836914s
Verifiability | Authors check for ISPRA - The Italian Data Buoy Network (RON) took 0.13467741012573242s
Verifiability | Publishers check for ISPRA - The Italian Data Buoy Network (RON) took 0.09195470809936523s
Performance | Throughput check for ISPRA - The Italian Data Buoy Network (RON) took 10.41136121749878s
Amount of data | Check the number of entities for ISPRA - The Italian Data Buoy Network (RON) took 7.176399230957031e-05s
Verifiability | Contribs. check for ISPRA - The Italian Data Buoy Network (RON) took 0.13408803939819336s
Interlinking | sameAs chians check for ISPRA - The Italian Data Buoy Network (RON) took 0.2010178565979004s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.4178602695465088s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.38198399543762207s
Timeliness | dataset update frequency check for ISPRA - The Italian Data Buoy Network (RON) took 0.13636493682861328s
Currency | Creation date check for ISPRA - The Italian Data Buoy Network (RON) took 0.1788196563720703s
Currency | Modification date check for ISPRA - The Italian Data Buoy Network (RON) took 0.08809733390808105s
Rep.Conc. | URIs length for ISPRA - The Italian Data Buoy Network (RON) took 12.926515817642212s
Interoperability | New vocabularies check for ISPRA - The Italian Data Buoy Network (RON) took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The Italian Data Buoy Network (RON) took 0.09105730056762695s
Accuracy | Check Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.0952455997467041s
Accuracy | Check Inverse Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.0939781665802002s
Accuracy | Check Empty annotation labels for ISPRA - The Italian Data Buoy Network (RON) took 2.877790689468384s
Accuracy | Check White space in annotation for ISPRA - The Italian Data Buoy Network (RON) took 0.3134002685546875s
Accuracy | Check Datatype consistency for ISPRA - The Italian Data Buoy Network (RON) took 0.27480268478393555s
Consistency | Disjoint class check for ISPRA - The Italian Data Buoy Network (RON) took 0.09103989601135254s
Consistency | Check Misplaced properties for ISPRA - The Italian Data Buoy Network (RON) took 8.994531154632568s
Consistency | Misplaced classes for ISPRA - The Italian Data Buoy Network (RON) took 0.9201908111572266s
Consistency | Check Ontology hijacking for ISPRA - The Italian Data Buoy Network (RON) took 2.769845962524414s
Consistency | Check Invalid usage of undefined classes for ISPRA - The Italian Data Buoy Network (RON) took 1.2540867328643799s
Consistency | Check Invalid usage of undefined properties for ISPRA - The Italian Data Buoy Network (RON) took 9.991548299789429s
Conciseness | Check Extensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.29654407501220703s
Conciseness | Check Intensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.10331869125366211s
Security | Sign check for ISPRA - The Italian Data Buoy Network (RON) took 0.1064598560333252s
Availability | Check URIs Dereferenciability for ISPRA - The Italian Data Buoy Network (RON) took 8.643379926681519s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian Data Buoy Network (RON) took 0.4129602909088135s
Reputation | Calculation of the PageRank for ISPRA - The Italian Data Buoy Network (RON) took 0.021481752395629883s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian Data Buoy Network (RON) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian Data Buoy Network (RON) took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian Data Buoy Network (RON) took 4.57763671875e-05s
Interoperability | Check the re-using of existing vocabs for ISPRA - The Italian Data Buoy Network (RON) took 1.9073486328125e-06s
Believability | Calculation of trust value for ISPRA - The Italian Data Buoy Network (RON) took 1.3589859008789062e-05s
INFO | --- Analysis for ispra-lod-ron took 437.8680238723755s
Availability | SPARQL endpoint availability check for ISSA Agritrop Dataset took 0.7178523540496826s
Availability | VoID file availability check for ISSA Agritrop Dataset took 0.0006840229034423828s
Completeness | Calculation of interlinking completeness for ISSA Agritrop Dataset took 0.3207416534423828s
Reputation | Calculation of the PageRank for ISSA Agritrop Dataset took 0.02148127555847168s
Interlinking | Calculation of Degree of Connection for ISSA Agritrop Dataset took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for ISSA Agritrop Dataset took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for ISSA Agritrop Dataset took 0.00012636184692382812s
Believability | Calculation of trust value for ISSA Agritrop Dataset took 1.0728836059570312e-05s
INFO | --- Analysis for issa-agritrop took 5.16326904296875s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.506111145019531e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.2661423683166504s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.020533323287963867s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 3.266334533691406e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 9.5367431640625e-06s
INFO | --- Analysis for ISSN:0080-3626 took 2.555941343307495s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.506111145019531e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0003578662872314453s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.2918739318847656s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.02055978775024414s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 3.361701965332031e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 2.86102294921875e-05s
INFO | --- Analysis for ISSN:_0080-3626 took 3.24042010307312s
Availability | SPARQL endpoint availability check for Aktualne zagadnienia klasyfikacji map took 4.57763671875e-05s
Availability | VoID file availability check for Aktualne zagadnienia klasyfikacji map took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for Aktualne zagadnienia klasyfikacji map took 0.27400636672973633s
Reputation | Calculation of the PageRank for Aktualne zagadnienia klasyfikacji map took 0.02064824104309082s
Interlinking | Calculation of Degree of Connection for Aktualne zagadnienia klasyfikacji map took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Aktualne zagadnienia klasyfikacji map took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Aktualne zagadnienia klasyfikacji map took 3.314018249511719e-05s
Believability | Calculation of trust value for Aktualne zagadnienia klasyfikacji map took 1.239776611328125e-05s
INFO | --- Analysis for ISSN:_0080-3626. took 2.798691987991333s
Availability | SPARQL endpoint availability check for ISTAT Immigration (LinkedOpenData.it) took 1.3994274139404297s
Availability | VoID file availability check for ISTAT Immigration (LinkedOpenData.it) took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for ISTAT Immigration (LinkedOpenData.it) took 0.2768549919128418s
Reputation | Calculation of the PageRank for ISTAT Immigration (LinkedOpenData.it) took 0.020660877227783203s
Interlinking | Calculation of Degree of Connection for ISTAT Immigration (LinkedOpenData.it) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ISTAT Immigration (LinkedOpenData.it) took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigration (LinkedOpenData.it) took 8.869171142578125e-05s
Believability | Calculation of trust value for ISTAT Immigration (LinkedOpenData.it) took 5.4836273193359375e-06s
INFO | --- Analysis for istat-immigration took 4.066641807556152s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Italian Republic took 0.2166893482208252s
Availability | VoID file availability check for List of prices of medicinal products marketed in Italian Republic took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Italian Republic took 0.2866795063018799s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Italian Republic took 0.022492170333862305s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Italian Republic took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Italian Republic took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Italian Republic took 3.7670135498046875e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Italian Republic took 6.67572021484375e-06s
INFO | --- Analysis for it-aifa-drug-prices took 3.1949880123138428s
Availability | SPARQL endpoint availability check for Italian public schools (LinkedOpenData.it) took 1.2572753429412842s
Availability | VoID file availability check for Italian public schools (LinkedOpenData.it) took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for Italian public schools (LinkedOpenData.it) took 0.2946350574493408s
Reputation | Calculation of the PageRank for Italian public schools (LinkedOpenData.it) took 0.02062845230102539s
Interlinking | Calculation of Degree of Connection for Italian public schools (LinkedOpenData.it) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Italian public schools (LinkedOpenData.it) took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Italian public schools (LinkedOpenData.it) took 7.915496826171875e-05s
Believability | Calculation of trust value for Italian public schools (LinkedOpenData.it) took 8.58306884765625e-06s
INFO | --- Analysis for italian-public-schools-linkedopendata-it took 4.015963315963745s
Availability | SPARQL endpoint availability check for IWN took 4.482269287109375e-05s
Availability | VoID file availability check for IWN took 0.0005409717559814453s
Completeness | Calculation of interlinking completeness for IWN took 0.2947990894317627s
Reputation | Calculation of the PageRank for IWN took 0.020720958709716797s
Interlinking | Calculation of Degree of Connection for IWN took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for IWN took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for IWN took 4.0531158447265625e-05s
Believability | Calculation of trust value for IWN took 1.3828277587890625e-05s
INFO | --- Analysis for iwn took 6.3355700969696045s
Availability | SPARQL endpoint availability check for DBTune.org Jamendo RDF Server took 5.76845908164978s
Availability | VoID file availability check for DBTune.org Jamendo RDF Server took 0.0009891986846923828s
Completeness | Calculation of interlinking completeness for DBTune.org Jamendo RDF Server took 0.2961573600769043s
Reputation | Calculation of the PageRank for DBTune.org Jamendo RDF Server took 0.022174358367919922s
Interlinking | Calculation of Degree of Connection for DBTune.org Jamendo RDF Server took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBTune.org Jamendo RDF Server took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for DBTune.org Jamendo RDF Server took 6.413459777832031e-05s
Believability | Calculation of trust value for DBTune.org Jamendo RDF Server took 1.2636184692382812e-05s
INFO | --- Analysis for jamendo-dbtune took 10.2190682888031s
Availability | SPARQL endpoint availability check for National Radioactivity Stat as Linked Data took 8.940696716308594e-05s
Availability | VoID file availability check for National Radioactivity Stat as Linked Data took 0.0006761550903320312s
Completeness | Calculation of interlinking completeness for National Radioactivity Stat as Linked Data took 0.29022669792175293s
Reputation | Calculation of the PageRank for National Radioactivity Stat as Linked Data took 0.020621776580810547s
Interlinking | Calculation of Degree of Connection for National Radioactivity Stat as Linked Data took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for National Radioactivity Stat as Linked Data took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for National Radioactivity Stat as Linked Data took 5.221366882324219e-05s
Believability | Calculation of trust value for National Radioactivity Stat as Linked Data took 8.344650268554688e-06s
INFO | --- Analysis for japan-radioactivity-stat took 5.125402212142944s
Availability | SPARQL endpoint availability check for JEL Classification took 4.5299530029296875e-05s
Availability | VoID file availability check for JEL Classification took 0.0006659030914306641s
Completeness | Calculation of interlinking completeness for JEL Classification took 0.3085601329803467s
Reputation | Calculation of the PageRank for JEL Classification took 0.02097296714782715s
Interlinking | Calculation of Degree of Connection for JEL Classification took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for JEL Classification took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for JEL Classification took 4.100799560546875e-05s
Believability | Calculation of trust value for JEL Classification took 1.1682510375976562e-05s
INFO | --- Analysis for jel-classification took 5.079620599746704s
Availability | SPARQL endpoint availability check for JISC Open Bibliography British National Bibliography dataset took 1.1826002597808838s
Availability | VoID file availability check for JISC Open Bibliography British National Bibliography dataset took 0.0006737709045410156s
Completeness | Calculation of interlinking completeness for JISC Open Bibliography British National Bibliography dataset took 0.2982749938964844s
Reputation | Calculation of the PageRank for JISC Open Bibliography British National Bibliography dataset took 0.02124762535095215s
Interlinking | Calculation of Degree of Connection for JISC Open Bibliography British National Bibliography dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for JISC Open Bibliography British National Bibliography dataset took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for JISC Open Bibliography British National Bibliography dataset took 3.266334533691406e-05s
Believability | Calculation of trust value for JISC Open Bibliography British National Bibliography dataset took 1.3589859008789062e-05s
INFO | --- Analysis for jiscopenbib-bl_bnb-1 took 7.13502836227417s
Availability | SPARQL endpoint availability check for JITA Classification System of Library and Information Science took 262.12566661834717s
Availability | VoID file availability check for JITA Classification System of Library and Information Science took 0.0008480548858642578s
Completeness | Calculation of interlinking completeness for JITA Classification System of Library and Information Science took 0.29788851737976074s
Reputation | Calculation of the PageRank for JITA Classification System of Library and Information Science took 0.021395444869995117s
Interlinking | Calculation of Degree of Connection for JITA Classification System of Library and Information Science took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for JITA Classification System of Library and Information Science took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for JITA Classification System of Library and Information Science took 8.797645568847656e-05s
Believability | Calculation of trust value for JITA Classification System of Library and Information Science took 1.2874603271484375e-05s
INFO | --- Analysis for jita took 541.0197384357452s
Availability | SPARQL endpoint availability check for John Goodwin's Family Tree took 20.058162927627563s
Availability | VoID file availability check for John Goodwin's Family Tree took 0.0007996559143066406s
Completeness | Calculation of interlinking completeness for John Goodwin's Family Tree took 0.37166643142700195s
Reputation | Calculation of the PageRank for John Goodwin's Family Tree took 0.02114129066467285s
Interlinking | Calculation of Degree of Connection for John Goodwin's Family Tree took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for John Goodwin's Family Tree took 0.0007784366607666016s
Interlinking | Calculation of Clustering coefficient for John Goodwin's Family Tree took 0.00010561943054199219s
Believability | Calculation of trust value for John Goodwin's Family Tree took 1.0013580322265625e-05s
INFO | --- Analysis for john-goodwins-family-tree took 62.915520668029785s
Availability | SPARQL endpoint availability check for Japanese Course of Study LOD took 4.839897155761719e-05s
Availability | VoID file availability check for Japanese Course of Study LOD took 0.0006594657897949219s
Completeness | Calculation of interlinking completeness for Japanese Course of Study LOD took 0.2861952781677246s
Reputation | Calculation of the PageRank for Japanese Course of Study LOD took 0.021008729934692383s
Interlinking | Calculation of Degree of Connection for Japanese Course of Study LOD took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Japanese Course of Study LOD took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Japanese Course of Study LOD took 3.7670135498046875e-05s
Believability | Calculation of trust value for Japanese Course of Study LOD took 1.430511474609375e-05s
INFO | --- Analysis for jp-cos took 4.88394570350647s
Availability | SPARQL endpoint availability check for Japanese Textbook LOD took 9.369850158691406e-05s
Availability | VoID file availability check for Japanese Textbook LOD took 0.0007226467132568359s
Completeness | Calculation of interlinking completeness for Japanese Textbook LOD took 0.29009485244750977s
Reputation | Calculation of the PageRank for Japanese Textbook LOD took 0.02067708969116211s
Interlinking | Calculation of Degree of Connection for Japanese Textbook LOD took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Japanese Textbook LOD took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Japanese Textbook LOD took 4.3392181396484375e-05s
Believability | Calculation of trust value for Japanese Textbook LOD took 1.3589859008789062e-05s
INFO | --- Analysis for jp-textbook took 4.5361244678497314s
Availability | SPARQL endpoint availability check for JRC-Names took 9.250640869140625e-05s
Availability | VoID file availability check for JRC-Names took 0.0005507469177246094s
Completeness | Calculation of interlinking completeness for JRC-Names took 0.26860880851745605s
Reputation | Calculation of the PageRank for JRC-Names took 0.02247452735900879s
Interlinking | Calculation of Degree of Connection for JRC-Names took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for JRC-Names took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for JRC-Names took 3.600120544433594e-05s
Believability | Calculation of trust value for JRC-Names took 1.430511474609375e-05s
INFO | --- Analysis for jrc-names-ec took 4.833457946777344s
Availability | SPARQL endpoint availability check for JRC-Names-MLODE took 0.9746477603912354s
Availability | VoID file availability check for JRC-Names-MLODE took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for JRC-Names-MLODE took 0.27029991149902344s
Reputation | Calculation of the PageRank for JRC-Names-MLODE took 0.020564556121826172s
Interlinking | Calculation of Degree of Connection for JRC-Names-MLODE took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for JRC-Names-MLODE took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for JRC-Names-MLODE took 8.249282836914062e-05s
Believability | Calculation of trust value for JRC-Names-MLODE took 1.4781951904296875e-05s
INFO | --- Analysis for jrc-names-mlode took 3.825329065322876s
Availability | SPARQL endpoint availability check for JudaicaLink took 9.131431579589844e-05s
Availability | VoID file availability check for JudaicaLink took 0.0006861686706542969s
Completeness | Calculation of interlinking completeness for JudaicaLink took 0.2769472599029541s
Reputation | Calculation of the PageRank for JudaicaLink took 0.020867347717285156s
Interlinking | Calculation of Degree of Connection for JudaicaLink took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for JudaicaLink took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for JudaicaLink took 0.00010967254638671875s
Believability | Calculation of trust value for JudaicaLink took 1.049041748046875e-05s
INFO | --- Analysis for judaicalink took 4.503539800643921s
Availability | SPARQL endpoint availability check for Kallikratis municipalities took 0.06844615936279297s
Availability | VoID file availability check for Kallikratis municipalities took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for Kallikratis municipalities took 0.3383207321166992s
Reputation | Calculation of the PageRank for Kallikratis municipalities took 0.021828651428222656s
Interlinking | Calculation of Degree of Connection for Kallikratis municipalities took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Kallikratis municipalities took 0.00118255615234375s
Interlinking | Calculation of Clustering coefficient for Kallikratis municipalities took 0.00012612342834472656s
Believability | Calculation of trust value for Kallikratis municipalities took 1.1205673217773438e-05s
INFO | --- Analysis for kallikratis-municipalities took 2.888763666152954s
Availability | SPARQL endpoint availability check for EU Soccer League took 9.608268737792969e-05s
Availability | VoID file availability check for EU Soccer League took 0.0007824897766113281s
Completeness | Calculation of interlinking completeness for EU Soccer League took 0.2760791778564453s
Reputation | Calculation of the PageRank for EU Soccer League took 0.021359920501708984s
Interlinking | Calculation of Degree of Connection for EU Soccer League took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for EU Soccer League took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for EU Soccer League took 3.123283386230469e-05s
Believability | Calculation of trust value for EU Soccer League took 1.33514404296875e-05s
INFO | --- Analysis for KG:Course_Submission took 5.40917444229126s
Availability | SPARQL endpoint availability check for Legal Knowledge Graph took 9.489059448242188e-05s
Availability | VoID file availability check for Legal Knowledge Graph took 0.0006608963012695312s
Completeness | Calculation of interlinking completeness for Legal Knowledge Graph took 0.2923424243927002s
Reputation | Calculation of the PageRank for Legal Knowledge Graph took 0.02097296714782715s
Interlinking | Calculation of Degree of Connection for Legal Knowledge Graph took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Legal Knowledge Graph took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for Legal Knowledge Graph took 1.33514404296875e-05s
Believability | Calculation of trust value for Legal Knowledge Graph took 1.430511474609375e-05s
INFO | --- Analysis for KING took 2.904116153717041s
Availability | SPARQL endpoint availability check for Klappstuhlclub took 0.00010585784912109375s
Availability | VoID file availability check for Klappstuhlclub took 0.0008006095886230469s
Completeness | Calculation of interlinking completeness for Klappstuhlclub took 0.3187096118927002s
Reputation | Calculation of the PageRank for Klappstuhlclub took 0.020570755004882812s
Interlinking | Calculation of Degree of Connection for Klappstuhlclub took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Klappstuhlclub took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Klappstuhlclub took 7.200241088867188e-05s
Believability | Calculation of trust value for Klappstuhlclub took 1.0013580322265625e-05s
INFO | --- Analysis for klappstuhlclub took 12.902759075164795s
Availability | SPARQL endpoint availability check for Linked Sensor Data (Kno.e.sis) took 10.907727718353271s
Availability | VoID file availability check for Linked Sensor Data (Kno.e.sis) took 0.0005426406860351562s
Completeness | Calculation of interlinking completeness for Linked Sensor Data (Kno.e.sis) took 0.34499096870422363s
Reputation | Calculation of the PageRank for Linked Sensor Data (Kno.e.sis) took 0.022397518157958984s
Interlinking | Calculation of Degree of Connection for Linked Sensor Data (Kno.e.sis) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Linked Sensor Data (Kno.e.sis) took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for Linked Sensor Data (Kno.e.sis) took 6.4849853515625e-05s
Believability | Calculation of trust value for Linked Sensor Data (Kno.e.sis) took 1.3113021850585938e-05s
INFO | --- Analysis for knoesis-linked-sensor-data took 23.740150928497314s
Availability | SPARQL endpoint availability check for Knowledge Forest took 9.1552734375e-05s
Availability | VoID file availability check for Knowledge Forest took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.28695011138916016s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.02103900909423828s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 3.3855438232421875e-05s
Believability | Calculation of trust value for Knowledge Forest took 1.5497207641601562e-05s
INFO | --- Analysis for KnowledgeFusion took 2.695876121520996s
Availability | SPARQL endpoint availability check for KORE 50 NIF NER Corpus took 8.940696716308594e-05s
Availability | VoID file availability check for KORE 50 NIF NER Corpus took 0.0008285045623779297s
Completeness | Calculation of interlinking completeness for KORE 50 NIF NER Corpus took 0.4100942611694336s
Reputation | Calculation of the PageRank for KORE 50 NIF NER Corpus took 0.020624637603759766s
Interlinking | Calculation of Degree of Connection for KORE 50 NIF NER Corpus took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for KORE 50 NIF NER Corpus took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for KORE 50 NIF NER Corpus took 7.2479248046875e-05s
Believability | Calculation of trust value for KORE 50 NIF NER Corpus took 1.430511474609375e-05s
INFO | --- Analysis for kore-50-nif-ner-corpus took 14.688372611999512s
Availability | SPARQL endpoint availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 9.632110595703125e-05s
Availability | VoID file availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0005757808685302734s
Completeness | Calculation of interlinking completeness for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.32150888442993164s
Reputation | Calculation of the PageRank for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.021065235137939453s
Interlinking | Calculation of Degree of Connection for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 5.698204040527344e-05s
Believability | Calculation of trust value for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.4066696166992188e-05s
INFO | --- Analysis for Kronika_naukowa_Biblioteki_Jagiellońskiej took 2.742969512939453s
Availability | SPARQL endpoint availability check for Informatics Studies took 5.030632019042969e-05s
Availability | VoID file availability check for Informatics Studies took 0.0005884170532226562s
Completeness | Calculation of interlinking completeness for Informatics Studies took 0.32324767112731934s
Reputation | Calculation of the PageRank for Informatics Studies took 0.020967483520507812s
Interlinking | Calculation of Degree of Connection for Informatics Studies took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Informatics Studies took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Informatics Studies took 3.4332275390625e-05s
Believability | Calculation of trust value for Informatics Studies took 8.821487426757812e-06s
INFO | --- Analysis for Kumar,_Gireesh__and_Singh,_Anand took 3.279003143310547s
Availability | SPARQL endpoint availability check for Kidney and Urinary Pathway Knowledge Base took 0.06859040260314941s
Availability | VoID file availability check for Kidney and Urinary Pathway Knowledge Base took 0.00044226646423339844s
Completeness | Calculation of interlinking completeness for Kidney and Urinary Pathway Knowledge Base took 0.2963404655456543s
Reputation | Calculation of the PageRank for Kidney and Urinary Pathway Knowledge Base took 0.02086949348449707s
Interlinking | Calculation of Degree of Connection for Kidney and Urinary Pathway Knowledge Base took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Kidney and Urinary Pathway Knowledge Base took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for Kidney and Urinary Pathway Knowledge Base took 4.4345855712890625e-05s
Believability | Calculation of trust value for Kidney and Urinary Pathway Knowledge Base took 1.0013580322265625e-05s
INFO | --- Analysis for kupkb took 9.917412042617798s
Availability | SPARQL endpoint availability check for DBLP in RDF (L3S) took 9.747023820877075s
Availability | VoID file availability check for DBLP in RDF (L3S) took 0.0006911754608154297s
Completeness | Calculation of interlinking completeness for DBLP in RDF (L3S) took 0.2914235591888428s
Reputation | Calculation of the PageRank for DBLP in RDF (L3S) took 0.020723581314086914s
Interlinking | Calculation of Degree of Connection for DBLP in RDF (L3S) took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for DBLP in RDF (L3S) took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for DBLP in RDF (L3S) took 8.58306884765625e-05s
Believability | Calculation of trust value for DBLP in RDF (L3S) took 1.430511474609375e-05s
INFO | --- Analysis for l3s-dblp took 44.108051776885986s
Availability | SPARQL endpoint availability check for Learning Analytics and Knowledge (LAK) Dataset took 26.00361442565918s
Availability | VoID file availability check for Learning Analytics and Knowledge (LAK) Dataset took 0.0005869865417480469s
Completeness | Calculation of interlinking completeness for Learning Analytics and Knowledge (LAK) Dataset took 0.29502201080322266s
Reputation | Calculation of the PageRank for Learning Analytics and Knowledge (LAK) Dataset took 0.02121591567993164s
Interlinking | Calculation of Degree of Connection for Learning Analytics and Knowledge (LAK) Dataset took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Learning Analytics and Knowledge (LAK) Dataset took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Learning Analytics and Knowledge (LAK) Dataset took 8.368492126464844e-05s
Believability | Calculation of trust value for Learning Analytics and Knowledge (LAK) Dataset took 9.5367431640625e-06s
INFO | --- Analysis for lak-dataset took 69.37952971458435s
Availability | SPARQL endpoint availability check for  Language Name Authority List  took 0.2038717269897461s
Availability | VoID file availability check for  Language Name Authority List  took 0.0007472038269042969s
Extra | Recovery of all triples for  Language Name Authority List  took 201.02621722221375s
Performance | Total latancy measurement for  Language Name Authority List  took 0.590876579284668s
Amount of data | Number of triples check for  Language Name Authority List  took 85.09927988052368s
Interoperability | New terms check for  Language Name Authority List  took 55.726834535598755s
Versatility | Languages check for  Language Name Authority List  took 300.098375082016s
Interpretability | Number of blank nodes check for  Language Name Authority List  took 19.35240602493286s
Security | Check HTTPS for  Language Name Authority List  took 0.36346936225891113s
Interpretability | RDF structures check for  Language Name Authority List  took 0.5237388610839844s
Versatility | Serialization formats check for  Language Name Authority List  took 3.5183823108673096s
Availability | RDF dump link check for  Language Name Authority List  took 0.2469944953918457s
License | MR license check for  Language Name Authority List  took 0.383342981338501s
License | HR license check for  Language Name Authority List  took 300.10230779647827s
Amount of data | Number of property check for  Language Name Authority List  took 0.19019556045532227s
Understandability | Number of label check for  Language Name Authority List  took 1.8564934730529785s
Understandability | URI regex check for  Language Name Authority List  took 0.4677894115447998s
Understandability | Vocabs check for  Language Name Authority List  took 0.11802124977111816s
Verifiability | Authors check for  Language Name Authority List  took 0.25438499450683594s
Verifiability | Publishers check for  Language Name Authority List  took 0.2562577724456787s
Performance | Throughput check for  Language Name Authority List  took 10.460897207260132s
Amount of data | Check the number of entities for  Language Name Authority List  took 8.487701416015625e-05s
Verifiability | Contribs. check for  Language Name Authority List  took 0.185377836227417s
Interlinking | sameAs chians check for  Language Name Authority List  took 6.880742788314819s
Interlinking | skos check for  Language Name Authority List  took 0.16721510887145996s
Interlinking | skos check for  Language Name Authority List  took 0.3380119800567627s
Timeliness | dataset update frequency check for  Language Name Authority List  took 0.3189716339111328s
Currency | Creation date check for  Language Name Authority List  took 0.3242974281311035s
Currency | Modification date check for  Language Name Authority List  took 0.17474913597106934s
Rep.Conc. | URIs length for  Language Name Authority List  took 406.90451979637146s
Interoperability | New vocabularies check for  Language Name Authority List  took 5.4836273193359375e-06s
Consistency | Deprecated classes/propertiers check for  Language Name Authority List  took 0.18322467803955078s
Accuracy | Check Functional Property for  Language Name Authority List  took 0.2141268253326416s
Accuracy | Check Inverse Functional Property for  Language Name Authority List  took 0.1914217472076416s
Accuracy | Check Empty annotation labels for  Language Name Authority List  took 39.5239098072052s
Accuracy | Check White space in annotation for  Language Name Authority List  took 3.104964017868042s
Accuracy | Check Datatype consistency for  Language Name Authority List  took 2.816181182861328s
Consistency | Disjoint class check for  Language Name Authority List  took 0.14674615859985352s
Consistency | Check Misplaced properties for  Language Name Authority List  took 300.41464495658875s
Consistency | Misplaced classes for  Language Name Authority List  took 8.716894149780273s
Consistency | Check Ontology hijacking for  Language Name Authority List  took 36.74119019508362s
Consistency | Check Invalid usage of undefined classes for  Language Name Authority List  took 1.7506914138793945s
Consistency | Check Invalid usage of undefined properties for  Language Name Authority List  took 301.42948603630066s
Conciseness | Check Extensional conciseness for  Language Name Authority List  took 3.1520209312438965s
Conciseness | Check Intensional conciseness for  Language Name Authority List  took 0.45548295974731445s
Security | Sign check for  Language Name Authority List  took 0.2717442512512207s
Availability | Check URIs Dereferenciability for  Language Name Authority List  took 10.914147138595581s
Completeness | Calculation of interlinking completeness for  Language Name Authority List  took 0.7632286548614502s
Reputation | Calculation of the PageRank for  Language Name Authority List  took 0.026607990264892578s
Interlinking | Calculation of Degree of Connection for  Language Name Authority List  took 2.3603439331054688e-05s
Interlinking | Calculation of Centrality for  Language Name Authority List  took 0.0008101463317871094s
Interlinking | Calculation of Clustering coefficient for  Language Name Authority List  took 9.632110595703125e-05s
Interoperability | Check the re-using of existing vocabs for  Language Name Authority List  took 1.6689300537109375e-06s
Believability | Calculation of trust value for  Language Name Authority List  took 1.430511474609375e-05s
INFO | --- Analysis for language-authority-list took 14945.476886749268s
Availability | SPARQL endpoint availability check for Lark took 384.652658700943s
Availability | VoID file availability check for Lark took 0.0005767345428466797s
Completeness | Calculation of interlinking completeness for Lark took 0.4827902317047119s
Reputation | Calculation of the PageRank for Lark took 0.021196842193603516s
Interlinking | Calculation of Degree of Connection for Lark took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Lark took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Lark took 9.942054748535156e-05s
Believability | Calculation of trust value for Lark took 1.3113021850585938e-05s
INFO | --- Analysis for LARK took 1676.337960243225s
Availability | SPARQL endpoint availability check for LASLA corpus in LiLa took 0.48326730728149414s
Availability | VoID file availability check for LASLA corpus in LiLa took 0.0007524490356445312s
Completeness | Calculation of interlinking completeness for LASLA corpus in LiLa took 0.2799670696258545s
Reputation | Calculation of the PageRank for LASLA corpus in LiLa took 0.020813465118408203s
Interlinking | Calculation of Degree of Connection for LASLA corpus in LiLa took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for LASLA corpus in LiLa took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for LASLA corpus in LiLa took 4.3392181396484375e-05s
Believability | Calculation of trust value for LASLA corpus in LiLa took 1.430511474609375e-05s
INFO | --- Analysis for LASLA took 4.131425142288208s
Availability | SPARQL endpoint availability check for Latin Vallex 2.0 in LiLa took 0.4661374092102051s
Availability | VoID file availability check for Latin Vallex 2.0 in LiLa took 0.0006825923919677734s
Completeness | Calculation of interlinking completeness for Latin Vallex 2.0 in LiLa took 0.2957611083984375s
Reputation | Calculation of the PageRank for Latin Vallex 2.0 in LiLa took 0.020412445068359375s
Interlinking | Calculation of Degree of Connection for Latin Vallex 2.0 in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Latin Vallex 2.0 in LiLa took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for Latin Vallex 2.0 in LiLa took 4.315376281738281e-05s
Believability | Calculation of trust value for Latin Vallex 2.0 in LiLa took 1.4066696166992188e-05s
INFO | --- Analysis for Latin_Vallex2.0 took 4.1591269969940186s
Availability | SPARQL endpoint availability check for LatinAffectus in LiLa took 0.4170718193054199s
Availability | VoID file availability check for LatinAffectus in LiLa took 0.0003609657287597656s
Completeness | Calculation of interlinking completeness for LatinAffectus in LiLa took 0.2848203182220459s
Reputation | Calculation of the PageRank for LatinAffectus in LiLa took 0.020609140396118164s
Interlinking | Calculation of Degree of Connection for LatinAffectus in LiLa took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for LatinAffectus in LiLa took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for LatinAffectus in LiLa took 3.9577484130859375e-05s
Believability | Calculation of trust value for LatinAffectus in LiLa took 1.52587890625e-05s
INFO | --- Analysis for LatinAffectus took 4.142040252685547s
Availability | SPARQL endpoint availability check for Latin WordNet Revision in LiLa took 0.4577052593231201s
Availability | VoID file availability check for Latin WordNet Revision in LiLa took 0.0007650852203369141s
Completeness | Calculation of interlinking completeness for Latin WordNet Revision in LiLa took 0.27600765228271484s
Reputation | Calculation of the PageRank for Latin WordNet Revision in LiLa took 0.022856473922729492s
Interlinking | Calculation of Degree of Connection for Latin WordNet Revision in LiLa took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Latin WordNet Revision in LiLa took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Latin WordNet Revision in LiLa took 4.2438507080078125e-05s
Believability | Calculation of trust value for Latin WordNet Revision in LiLa took 1.5735626220703125e-05s
INFO | --- Analysis for LatinWordnetLiLa took 4.431862115859985s
Availability | SPARQL endpoint availability check for Library of Congress Subject Headings took 6.246566772460938e-05s
Availability | VoID file availability check for Library of Congress Subject Headings took 0.0015115737915039062s
Completeness | Calculation of interlinking completeness for Library of Congress Subject Headings took 0.3035712242126465s
Reputation | Calculation of the PageRank for Library of Congress Subject Headings took 0.0224456787109375s
Interlinking | Calculation of Degree of Connection for Library of Congress Subject Headings took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Library of Congress Subject Headings took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Library of Congress Subject Headings took 0.0001232624053955078s
Believability | Calculation of trust value for Library of Congress Subject Headings took 9.5367431640625e-06s
INFO | --- Analysis for lcsh took 7.572618722915649s
Availability | SPARQL endpoint availability check for LCSubjects.org Library of Congress Subject Headings took 9.226799011230469e-05s
Availability | VoID file availability check for LCSubjects.org Library of Congress Subject Headings took 0.0006577968597412109s
Completeness | Calculation of interlinking completeness for LCSubjects.org Library of Congress Subject Headings took 0.3068392276763916s
Reputation | Calculation of the PageRank for LCSubjects.org Library of Congress Subject Headings took 0.021823644638061523s
Interlinking | Calculation of Degree of Connection for LCSubjects.org Library of Congress Subject Headings took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for LCSubjects.org Library of Congress Subject Headings took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for LCSubjects.org Library of Congress Subject Headings took 9.083747863769531e-05s
Believability | Calculation of trust value for LCSubjects.org Library of Congress Subject Headings took 1.3828277587890625e-05s
INFO | --- Analysis for lcsubjects took 3.3082387447357178s
Availability | SPARQL endpoint availability check for Linked Open Data Taiwan @ Library took 9.020688533782959s
Availability | VoID file availability check for Linked Open Data Taiwan @ Library took 0.0007085800170898438s
Completeness | Calculation of interlinking completeness for Linked Open Data Taiwan @ Library took 0.30193400382995605s
Reputation | Calculation of the PageRank for Linked Open Data Taiwan @ Library took 0.020483732223510742s
Interlinking | Calculation of Degree of Connection for Linked Open Data Taiwan @ Library took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Linked Open Data Taiwan @ Library took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Linked Open Data Taiwan @ Library took 4.792213439941406e-05s
Believability | Calculation of trust value for Linked Open Data Taiwan @ Library took 1.52587890625e-05s
INFO | --- Analysis for ldt@library took 36.5585196018219s
Availability | SPARQL endpoint availability check for U ime Legije took 0.00012350082397460938s
Availability | VoID file availability check for U ime Legije took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for U ime Legije took 0.31096386909484863s
Reputation | Calculation of the PageRank for U ime Legije took 0.02058696746826172s
Interlinking | Calculation of Degree of Connection for U ime Legije took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for U ime Legije took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for U ime Legije took 3.409385681152344e-05s
Believability | Calculation of trust value for U ime Legije took 1.5020370483398438e-05s
INFO | --- Analysis for LEGIJA_STRANACA took 2.8936665058135986s
Availability | SPARQL endpoint availability check for LiLa Lemma Bank took 0.46305418014526367s
Availability | VoID file availability check for LiLa Lemma Bank took 0.0007159709930419922s
Completeness | Calculation of interlinking completeness for LiLa Lemma Bank took 0.33286523818969727s
Reputation | Calculation of the PageRank for LiLa Lemma Bank took 0.020602703094482422s
Interlinking | Calculation of Degree of Connection for LiLa Lemma Bank took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for LiLa Lemma Bank took 0.0007898807525634766s
Interlinking | Calculation of Clustering coefficient for LiLa Lemma Bank took 7.700920104980469e-05s
Believability | Calculation of trust value for LiLa Lemma Bank took 1.430511474609375e-05s
INFO | --- Analysis for LemmaBank took 4.575742244720459s
Availability | SPARQL endpoint availability check for lemonUby took 9.202957153320312e-05s
Availability | VoID file availability check for lemonUby took 0.0006337165832519531s
Completeness | Calculation of interlinking completeness for lemonUby took 0.2692387104034424s
Reputation | Calculation of the PageRank for lemonUby took 0.020715713500976562s
Interlinking | Calculation of Degree of Connection for lemonUby took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for lemonUby took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for lemonUby took 6.818771362304688e-05s
Believability | Calculation of trust value for lemonUby took 1.4543533325195312e-05s
INFO | --- Analysis for lemonuby took 3.3849916458129883s
Availability | SPARQL endpoint availability check for LemonWiktionary took 4.38690185546875e-05s
Availability | VoID file availability check for LemonWiktionary took 0.0005509853363037109s
Completeness | Calculation of interlinking completeness for LemonWiktionary took 0.30019307136535645s
Reputation | Calculation of the PageRank for LemonWiktionary took 0.021127700805664062s
Interlinking | Calculation of Degree of Connection for LemonWiktionary took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for LemonWiktionary took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for LemonWiktionary took 4.029273986816406e-05s
Believability | Calculation of trust value for LemonWiktionary took 1.5974044799804688e-05s
INFO | --- Analysis for lemonwiktionary took 4.866211891174316s
Availability | SPARQL endpoint availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.4500613212585449s
Availability | VoID file availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.0007376670837402344s
Completeness | Calculation of interlinking completeness for Lewis and Short Latin-English Dictionary in LiLa took 0.29297327995300293s
Reputation | Calculation of the PageRank for Lewis and Short Latin-English Dictionary in LiLa took 0.02091217041015625s
Interlinking | Calculation of Degree of Connection for Lewis and Short Latin-English Dictionary in LiLa took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Lewis and Short Latin-English Dictionary in LiLa took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Lewis and Short Latin-English Dictionary in LiLa took 4.076957702636719e-05s
Believability | Calculation of trust value for Lewis and Short Latin-English Dictionary in LiLa took 1.4781951904296875e-05s
INFO | --- Analysis for LewisShort took 4.124725818634033s
Availability | SPARQL endpoint availability check for LEXIN-RDF took 1.039884090423584s
Availability | VoID file availability check for LEXIN-RDF took 0.0006010532379150391s
Completeness | Calculation of interlinking completeness for LEXIN-RDF took 0.32188844680786133s
Reputation | Calculation of the PageRank for LEXIN-RDF took 0.021954774856567383s
Interlinking | Calculation of Degree of Connection for LEXIN-RDF took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for LEXIN-RDF took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for LEXIN-RDF took 3.4809112548828125e-05s
Believability | Calculation of trust value for LEXIN-RDF took 1.4543533325195312e-05s
INFO | --- Analysis for lexin-rdf took 6.078840017318726s
Availability | SPARQL endpoint availability check for lexinfo took 0.00010776519775390625s
Availability | VoID file availability check for lexinfo took 0.0006835460662841797s
Completeness | Calculation of interlinking completeness for lexinfo took 0.28943490982055664s
Reputation | Calculation of the PageRank for lexinfo took 0.020769119262695312s
Interlinking | Calculation of Degree of Connection for lexinfo took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for lexinfo took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for lexinfo took 9.34600830078125e-05s
Believability | Calculation of trust value for lexinfo took 1.4781951904296875e-05s
INFO | --- Analysis for lexinfo took 3.2593679428100586s
Availability | SPARQL endpoint availability check for Lexvo took 6.532669067382812e-05s
Availability | VoID file availability check for Lexvo took 0.0006070137023925781s
Completeness | Calculation of interlinking completeness for Lexvo took 0.29514455795288086s
Reputation | Calculation of the PageRank for Lexvo took 0.02133965492248535s
Interlinking | Calculation of Degree of Connection for Lexvo took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Lexvo took 0.0007832050323486328s
Interlinking | Calculation of Clustering coefficient for Lexvo took 0.0001804828643798828s
Believability | Calculation of trust value for Lexvo took 1.4781951904296875e-05s
INFO | --- Analysis for lexvo took 3.418600559234619s
Availability | SPARQL endpoint availability check for Lexvo.org took 4.38690185546875e-05s
Availability | VoID file availability check for Lexvo.org took 0.0011048316955566406s
Completeness | Calculation of interlinking completeness for Lexvo.org took 0.27573156356811523s
Reputation | Calculation of the PageRank for Lexvo.org took 0.020711421966552734s
Interlinking | Calculation of Degree of Connection for Lexvo.org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Lexvo.org took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Lexvo.org took 7.82012939453125e-05s
Believability | Calculation of trust value for Lexvo.org took 1.2636184692382812e-05s
INFO | --- Analysis for lexvo-org took 2.808994770050049s
Availability | SPARQL endpoint availability check for LIBRIS took 0.3776247501373291s
Availability | VoID file availability check for LIBRIS took 0.0007281303405761719s
Extra | Recovery of all triples for LIBRIS took 6.068254232406616s
Performance | Total latancy measurement for LIBRIS took 0.7217769622802734s
Amount of data | Number of triples check for LIBRIS took 21.085012197494507s
Interoperability | New terms check for LIBRIS took 17.38691210746765s
Versatility | Languages check for LIBRIS took 0.2014467716217041s
Interpretability | Number of blank nodes check for LIBRIS took 300.03767013549805s
Security | Check HTTPS for LIBRIS took 0.35746026039123535s
Interpretability | RDF structures check for LIBRIS took 3.0731148719787598s
Versatility | Serialization formats check for LIBRIS took 0.23917841911315918s
Availability | RDF dump link check for LIBRIS took 0.14244866371154785s
License | MR license check for LIBRIS took 0.20169663429260254s
License | HR license check for LIBRIS took 0.2547116279602051s
Amount of data | Number of property check for LIBRIS took 0.20714902877807617s
Understandability | Number of label check for LIBRIS took 0.41532421112060547s
Understandability | URI regex check for LIBRIS took 0.3315107822418213s
Understandability | Vocabs check for LIBRIS took 0.1442089080810547s
Verifiability | Authors check for LIBRIS took 0.15941858291625977s
Verifiability | Publishers check for LIBRIS took 0.15758895874023438s
Performance | Throughput check for LIBRIS took 10.664308786392212s
Amount of data | Check the number of entities for LIBRIS took 8.678436279296875e-05s
Verifiability | Contribs. check for LIBRIS took 0.16185665130615234s
Interlinking | sameAs chians check for LIBRIS took 0.15642333030700684s
Interlinking | skos check for LIBRIS took 0.24841547012329102s
Interlinking | skos check for LIBRIS took 0.13455677032470703s
Timeliness | dataset update frequency check for LIBRIS took 0.13742804527282715s
Currency | Creation date check for LIBRIS took 0.42195868492126465s
Currency | Modification date check for LIBRIS took 0.6991512775421143s
Rep.Conc. | URIs length for LIBRIS took 91.0429458618164s
Interoperability | New vocabularies check for LIBRIS took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for LIBRIS took 0.20090341567993164s
Accuracy | Check Functional Property for LIBRIS took 0.27787041664123535s
Accuracy | Check Inverse Functional Property for LIBRIS took 0.20473074913024902s
Accuracy | Check Datatype consistency for LIBRIS took 0.2810664176940918s
Consistency | Disjoint class check for LIBRIS took 0.23154902458190918s
Consistency | Check Misplaced properties for LIBRIS took 69.97617769241333s
Consistency | Misplaced classes for LIBRIS took 1.164020299911499s
Consistency | Check Ontology hijacking for LIBRIS took 3.148287773132324s
Consistency | Check Invalid usage of undefined classes for LIBRIS took 1.2237040996551514s
Consistency | Check Invalid usage of undefined properties for LIBRIS took 71.02363157272339s
Conciseness | Check Extensional conciseness for LIBRIS took 0.28546857833862305s
Conciseness | Check Intensional conciseness for LIBRIS took 0.39403653144836426s
Security | Sign check for LIBRIS took 0.26678037643432617s
Availability | Check URIs Dereferenciability for LIBRIS took 10.15088415145874s
Completeness | Calculation of interlinking completeness for LIBRIS took 0.39508676528930664s
Reputation | Calculation of the PageRank for LIBRIS took 0.02069091796875s
Interlinking | Calculation of Degree of Connection for LIBRIS took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for LIBRIS took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for LIBRIS took 9.942054748535156e-05s
Interoperability | Check the re-using of existing vocabs for LIBRIS took 1.1920928955078125e-06s
Believability | Calculation of trust value for LIBRIS took 1.4781951904296875e-05s
INFO | --- Analysis for libris took 1096.6799890995026s
Availability | SPARQL endpoint availability check for Public Library of Veroia took 0.17448902130126953s
Availability | VoID file availability check for Public Library of Veroia took 0.0007317066192626953s
Completeness | Calculation of interlinking completeness for Public Library of Veroia took 0.29483556747436523s
Reputation | Calculation of the PageRank for Public Library of Veroia took 0.02073192596435547s
Interlinking | Calculation of Degree of Connection for Public Library of Veroia took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Public Library of Veroia took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Public Library of Veroia took 7.700920104980469e-05s
Believability | Calculation of trust value for Public Library of Veroia took 1.5020370483398438e-05s
INFO | --- Analysis for libver took 4.011802434921265s
Availability | SPARQL endpoint availability check for Lichfield District Council - Spending took 0.1383073329925537s
Availability | VoID file availability check for Lichfield District Council - Spending took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for Lichfield District Council - Spending took 0.3044404983520508s
Reputation | Calculation of the PageRank for Lichfield District Council - Spending took 0.02184915542602539s
Interlinking | Calculation of Degree of Connection for Lichfield District Council - Spending took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Lichfield District Council - Spending took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Lichfield District Council - Spending took 8.654594421386719e-05s
Believability | Calculation of trust value for Lichfield District Council - Spending took 1.0728836059570312e-05s
INFO | --- Analysis for lichfield-spending took 2.8511927127838135s
Availability | SPARQL endpoint availability check for Linguistic Metadata (LIME) vocabulary took 0.00013327598571777344s
Availability | VoID file availability check for Linguistic Metadata (LIME) vocabulary took 0.0007586479187011719s
Completeness | Calculation of interlinking completeness for Linguistic Metadata (LIME) vocabulary took 0.30625391006469727s
Reputation | Calculation of the PageRank for Linguistic Metadata (LIME) vocabulary took 0.020882844924926758s
Interlinking | Calculation of Degree of Connection for Linguistic Metadata (LIME) vocabulary took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Linguistic Metadata (LIME) vocabulary took 0.0008089542388916016s
Interlinking | Calculation of Clustering coefficient for Linguistic Metadata (LIME) vocabulary took 3.933906555175781e-05s
Believability | Calculation of trust value for Linguistic Metadata (LIME) vocabulary took 1.1205673217773438e-05s
INFO | --- Analysis for lime took 6.8964221477508545s
Availability | SPARQL endpoint availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 4.696846008300781e-05s
Availability | VoID file availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.46659064292907715s
Completeness | Calculation of interlinking completeness for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.3031923770904541s
Reputation | Calculation of the PageRank for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.020820140838623047s
Interlinking | Calculation of Degree of Connection for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0001404285430908203s
Believability | Calculation of trust value for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.430511474609375e-05s
INFO | --- Analysis for lingvoj took 7.018385887145996s
Availability | SPARQL endpoint availability check for Linked Crunchbase took 9.107589721679688e-05s
Availability | VoID file availability check for Linked Crunchbase took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for Linked Crunchbase took 0.2866511344909668s
Reputation | Calculation of the PageRank for Linked Crunchbase took 0.02097153663635254s
Interlinking | Calculation of Degree of Connection for Linked Crunchbase took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Linked Crunchbase took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for Linked Crunchbase took 8.821487426757812e-05s
Believability | Calculation of trust value for Linked Crunchbase took 1.5497207641601562e-05s
INFO | --- Analysis for linked-crunchbase took 15.14776873588562s
Availability | SPARQL endpoint availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.9616572856903076s
Availability | VoID file availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0006117820739746094s
Completeness | Calculation of interlinking completeness for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.31894826889038086s
Reputation | Calculation of the PageRank for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.02088308334350586s
Interlinking | Calculation of Degree of Connection for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.52587890625e-05s
Interlinking | Calculation of Centrality for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0008394718170166016s
Interlinking | Calculation of Clustering coefficient for LinkedDrugs: Linked Drug Product Data on a Global Scale took 9.274482727050781e-05s
Believability | Calculation of trust value for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.4066696166992188e-05s
INFO | --- Analysis for linked-drugs took 8.761133909225464s
Availability | SPARQL endpoint availability check for Linked EDGAR (OntologyCentral) took 4.601478576660156e-05s
Availability | VoID file availability check for Linked EDGAR (OntologyCentral) took 0.0012085437774658203s
Completeness | Calculation of interlinking completeness for Linked EDGAR (OntologyCentral) took 0.30487942695617676s
Reputation | Calculation of the PageRank for Linked EDGAR (OntologyCentral) took 0.02078104019165039s
Interlinking | Calculation of Degree of Connection for Linked EDGAR (OntologyCentral) took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Linked EDGAR (OntologyCentral) took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Linked EDGAR (OntologyCentral) took 0.0001373291015625s
Believability | Calculation of trust value for Linked EDGAR (OntologyCentral) took 1.1444091796875e-05s
INFO | --- Analysis for linked-edgar took 4.530383586883545s
Availability | SPARQL endpoint availability check for Linked Eurostat (OntologyCentral) took 8.916854858398438e-05s
Availability | VoID file availability check for Linked Eurostat (OntologyCentral) took 0.0007426738739013672s
Completeness | Calculation of interlinking completeness for Linked Eurostat (OntologyCentral) took 0.3354818820953369s
Reputation | Calculation of the PageRank for Linked Eurostat (OntologyCentral) took 0.020596027374267578s
Interlinking | Calculation of Degree of Connection for Linked Eurostat (OntologyCentral) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Linked Eurostat (OntologyCentral) took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Linked Eurostat (OntologyCentral) took 0.00010251998901367188s
Believability | Calculation of trust value for Linked Eurostat (OntologyCentral) took 1.3828277587890625e-05s
INFO | --- Analysis for linked-eurostat took 3.8616201877593994s
Availability | SPARQL endpoint availability check for linked hypernyms took 4.601478576660156e-05s
Availability | VoID file availability check for linked hypernyms took 0.00037980079650878906s
Completeness | Calculation of interlinking completeness for linked hypernyms took 0.3026583194732666s
Reputation | Calculation of the PageRank for linked hypernyms took 0.020674467086791992s
Interlinking | Calculation of Degree of Connection for linked hypernyms took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for linked hypernyms took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for linked hypernyms took 8.392333984375e-05s
Believability | Calculation of trust value for linked hypernyms took 1.5497207641601562e-05s
INFO | --- Analysis for linked-hypernyms took 3.669894218444824s
Availability | SPARQL endpoint availability check for Linked Life Data took 207.66624450683594s
Availability | VoID file availability check for Linked Life Data took 0.0008165836334228516s
Completeness | Calculation of interlinking completeness for Linked Life Data took 0.7790436744689941s
Reputation | Calculation of the PageRank for Linked Life Data took 0.026772260665893555s
Interlinking | Calculation of Degree of Connection for Linked Life Data took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Linked Life Data took 0.0008034706115722656s
Interlinking | Calculation of Clustering coefficient for Linked Life Data took 5.888938903808594e-05s
Believability | Calculation of trust value for Linked Life Data took 1.3113021850585938e-05s
INFO | --- Analysis for linked-life-data took 682.9329578876495s
Availability | SPARQL endpoint availability check for Linked Logainm took 0.3086831569671631s
Availability | VoID file availability check for Linked Logainm took 0.0005843639373779297s
Extra | Recovery of all triples for Linked Logainm took 1.6456413269042969s
Performance | Total latancy measurement for Linked Logainm took 0.5918514728546143s
Amount of data | Number of triples check for Linked Logainm took 0.24677181243896484s
Interoperability | New terms check for Linked Logainm took 1.3631737232208252s
Versatility | Languages check for Linked Logainm took 1.4442825317382812s
Interpretability | Number of blank nodes check for Linked Logainm took 0.1423346996307373s
Security | Check HTTPS for Linked Logainm took 0.27254223823547363s
Interpretability | RDF structures check for Linked Logainm took 0.2488558292388916s
Versatility | Serialization formats check for Linked Logainm took 0.15182733535766602s
Availability | RDF dump link check for Linked Logainm took 0.11497974395751953s
License | MR license check for Linked Logainm took 0.15238404273986816s
License | HR license check for Linked Logainm took 0.1266777515411377s
Amount of data | Number of property check for Linked Logainm took 0.15544414520263672s
Understandability | Number of label check for Linked Logainm took 0.20264792442321777s
Understandability | URI regex check for Linked Logainm took 0.23223161697387695s
Understandability | Vocabs check for Linked Logainm took 0.11405086517333984s
Verifiability | Authors check for Linked Logainm took 0.11242079734802246s
Verifiability | Publishers check for Linked Logainm took 0.1224362850189209s
Performance | Throughput check for Linked Logainm took 10.412320852279663s
Amount of data | Check the number of entities for Linked Logainm took 7.224082946777344e-05s
Verifiability | Contribs. check for Linked Logainm took 0.1174933910369873s
Interlinking | sameAs chians check for Linked Logainm took 0.14856553077697754s
Interlinking | skos check for Linked Logainm took 0.16072463989257812s
Interlinking | skos check for Linked Logainm took 0.11412167549133301s
Timeliness | dataset update frequency check for Linked Logainm took 0.11361479759216309s
Currency | Creation date check for Linked Logainm took 0.2699143886566162s
Currency | Modification date check for Linked Logainm took 0.25591015815734863s
Rep.Conc. | URIs length for Linked Logainm took 0.9114556312561035s
Interoperability | New vocabularies check for Linked Logainm took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for Linked Logainm took 0.15209197998046875s
Accuracy | Check Functional Property for Linked Logainm took 0.21203017234802246s
Accuracy | Check Inverse Functional Property for Linked Logainm took 0.18924736976623535s
Accuracy | Check Empty annotation labels for Linked Logainm took 0.5085864067077637s
Accuracy | Check White space in annotation for Linked Logainm took 0.024277687072753906s
Accuracy | Check Datatype consistency for Linked Logainm took 0.028869152069091797s
Consistency | Disjoint class check for Linked Logainm took 0.17659330368041992s
Consistency | Check Misplaced properties for Linked Logainm took 0.33633947372436523s
Consistency | Misplaced classes for Linked Logainm took 0.300739049911499s
Consistency | Check Ontology hijacking for Linked Logainm took 1.7580623626708984s
Consistency | Check Invalid usage of undefined classes for Linked Logainm took 1.2154886722564697s
Consistency | Check Invalid usage of undefined properties for Linked Logainm took 1.4353468418121338s
Conciseness | Check Extensional conciseness for Linked Logainm took 0.03329133987426758s
Conciseness | Check Intensional conciseness for Linked Logainm took 0.19705986976623535s
Security | Sign check for Linked Logainm took 0.12621116638183594s
Availability | Check URIs Dereferenciability for Linked Logainm took 1028.3575282096863s
Completeness | Calculation of interlinking completeness for Linked Logainm took 0.4565858840942383s
Reputation | Calculation of the PageRank for Linked Logainm took 0.021448135375976562s
Interlinking | Calculation of Degree of Connection for Linked Logainm took 8.344650268554688e-05s
Interlinking | Calculation of Centrality for Linked Logainm took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Linked Logainm took 9.012222290039062e-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.4781951904296875e-05s
INFO | --- Analysis for linked-logainm took 1084.1265580654144s
Availability | SPARQL endpoint availability check for Linked NUTS took 0.00017881393432617188s
Availability | VoID file availability check for Linked NUTS took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for Linked NUTS took 0.3190288543701172s
Reputation | Calculation of the PageRank for Linked NUTS took 0.02258920669555664s
Interlinking | Calculation of Degree of Connection for Linked NUTS took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Linked NUTS took 0.0008738040924072266s
Interlinking | Calculation of Clustering coefficient for Linked NUTS took 6.008148193359375e-05s
Believability | Calculation of trust value for Linked NUTS took 1.0251998901367188e-05s
INFO | --- Analysis for linked-nuts took 2.880728006362915s
Availability | SPARQL endpoint availability check for Linked Open Camera (LinkedOpenData.it) took 1.456427812576294s
Availability | VoID file availability check for Linked Open Camera (LinkedOpenData.it) took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for Linked Open Camera (LinkedOpenData.it) took 0.28479456901550293s
Reputation | Calculation of the PageRank for Linked Open Camera (LinkedOpenData.it) took 0.020717620849609375s
Interlinking | Calculation of Degree of Connection for Linked Open Camera (LinkedOpenData.it) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Linked Open Camera (LinkedOpenData.it) took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Linked Open Camera (LinkedOpenData.it) took 4.100799560546875e-05s
Believability | Calculation of trust value for Linked Open Camera (LinkedOpenData.it) took 9.775161743164062e-06s
INFO | --- Analysis for linked-open-camera took 4.29031777381897s
Availability | SPARQL endpoint availability check for Linked Open Commerce took 4.6647703647613525s
Availability | VoID file availability check for Linked Open Commerce took 0.0007009506225585938s
Completeness | Calculation of interlinking completeness for Linked Open Commerce took 0.2971060276031494s
Reputation | Calculation of the PageRank for Linked Open Commerce took 0.021244287490844727s
Interlinking | Calculation of Degree of Connection for Linked Open Commerce took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Linked Open Commerce took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Linked Open Commerce took 3.4332275390625e-05s
Believability | Calculation of trust value for Linked Open Commerce took 1.52587890625e-05s
INFO | --- Analysis for linked-open-commerce took 15.548975706100464s
Availability | SPARQL endpoint availability check for Linked Open Data of Ecology took 1.713362455368042s
Availability | VoID file availability check for Linked Open Data of Ecology took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for Linked Open Data of Ecology took 0.27539563179016113s
Reputation | Calculation of the PageRank for Linked Open Data of Ecology took 0.02092885971069336s
Interlinking | Calculation of Degree of Connection for Linked Open Data of Ecology took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Linked Open Data of Ecology took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for Linked Open Data of Ecology took 0.00011277198791503906s
Believability | Calculation of trust value for Linked Open Data of Ecology took 1.3589859008789062e-05s
INFO | --- Analysis for linked-open-data-of-ecology took 4.447035551071167s
Availability | SPARQL endpoint availability check for Linked Open Numbers took 4.38690185546875e-05s
Availability | VoID file availability check for Linked Open Numbers took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for Linked Open Numbers took 0.29995012283325195s
Reputation | Calculation of the PageRank for Linked Open Numbers took 0.020714998245239258s
Interlinking | Calculation of Degree of Connection for Linked Open Numbers took 4.9114227294921875e-05s
Interlinking | Calculation of Centrality for Linked Open Numbers took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Linked Open Numbers took 9.942054748535156e-05s
Believability | Calculation of trust value for Linked Open Numbers took 1.4781951904296875e-05s
INFO | --- Analysis for linked-open-numbers took 2.971989154815674s
Availability | SPARQL endpoint availability check for Linked Open Piracy took 5.078315734863281e-05s
Availability | VoID file availability check for Linked Open Piracy took 0.0006418228149414062s
Completeness | Calculation of interlinking completeness for Linked Open Piracy took 0.31890201568603516s
Reputation | Calculation of the PageRank for Linked Open Piracy took 0.020940780639648438s
Interlinking | Calculation of Degree of Connection for Linked Open Piracy took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Linked Open Piracy took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Linked Open Piracy took 3.4809112548828125e-05s
Believability | Calculation of trust value for Linked Open Piracy took 6.9141387939453125e-06s
INFO | --- Analysis for linked-open-piracy took 7.31046199798584s
Availability | SPARQL endpoint availability check for Linked Open Vocabularies (LOV) took 1.7170078754425049s
Availability | VoID file availability check for Linked Open Vocabularies (LOV) took 0.0006585121154785156s
Extra | Recovery of all triples for Linked Open Vocabularies (LOV) took 66.76170134544373s
Performance | Total latancy measurement for Linked Open Vocabularies (LOV) took 1.0607788562774658s
Amount of data | Number of triples check for Linked Open Vocabularies (LOV) took 1.9934720993041992s
Interoperability | New terms check for Linked Open Vocabularies (LOV) took 2.2103359699249268s
Versatility | Languages check for Linked Open Vocabularies (LOV) took 12.52577543258667s
Interpretability | Number of blank nodes check for Linked Open Vocabularies (LOV) took 1.8633489608764648s
Interpretability | RDF structures check for Linked Open Vocabularies (LOV) took 0.21909523010253906s
Versatility | Serialization formats check for Linked Open Vocabularies (LOV) took 0.21057820320129395s
Availability | RDF dump link check for Linked Open Vocabularies (LOV) took 0.9231836795806885s
License | MR license check for Linked Open Vocabularies (LOV) took 0.1897575855255127s
License | HR license check for Linked Open Vocabularies (LOV) took 45.01413702964783s
Amount of data | Number of property check for Linked Open Vocabularies (LOV) took 0.20921897888183594s
Understandability | Number of label check for Linked Open Vocabularies (LOV) took 0.7349209785461426s
Understandability | URI regex check for Linked Open Vocabularies (LOV) took 0.3827519416809082s
Understandability | Vocabs check for Linked Open Vocabularies (LOV) took 0.2127516269683838s
Verifiability | Authors check for Linked Open Vocabularies (LOV) took 0.22860956192016602s
Verifiability | Publishers check for Linked Open Vocabularies (LOV) took 0.2728085517883301s
Performance | Throughput check for Linked Open Vocabularies (LOV) took 11.631792306900024s
Amount of data | Check the number of entities for Linked Open Vocabularies (LOV) took 1.1551697254180908s
Verifiability | Contribs. check for Linked Open Vocabularies (LOV) took 0.22565579414367676s
Interlinking | sameAs chians check for Linked Open Vocabularies (LOV) took 0.1909499168395996s
Interlinking | skos check for Linked Open Vocabularies (LOV) took 0.19582247734069824s
Interlinking | skos check for Linked Open Vocabularies (LOV) took 0.19531035423278809s
Timeliness | dataset update frequency check for Linked Open Vocabularies (LOV) took 0.33845996856689453s
Currency | Creation date check for Linked Open Vocabularies (LOV) took 1.408707857131958s
Currency | Modification date check for Linked Open Vocabularies (LOV) took 0.21204805374145508s
Rep.Conc. | URIs length for Linked Open Vocabularies (LOV) took 24.431476593017578s
Interoperability | New vocabularies check for Linked Open Vocabularies (LOV) took 15.731310606002808s
Consistency | Deprecated classes/propertiers check for Linked Open Vocabularies (LOV) took 0.25835394859313965s
Accuracy | Check Functional Property for Linked Open Vocabularies (LOV) took 0.19538593292236328s
Accuracy | Check Inverse Functional Property for Linked Open Vocabularies (LOV) took 0.33089470863342285s
Accuracy | Check Empty annotation labels for Linked Open Vocabularies (LOV) took 6.857276678085327s
Accuracy | Check White space in annotation for Linked Open Vocabularies (LOV) took 0.6944043636322021s
Accuracy | Check Datatype consistency for Linked Open Vocabularies (LOV) took 4.887050628662109s
Consistency | Disjoint class check for Linked Open Vocabularies (LOV) took 0.4991428852081299s
Consistency | Check Misplaced properties for Linked Open Vocabularies (LOV) took 6.796837568283081s
Consistency | Misplaced classes for Linked Open Vocabularies (LOV) took 0.2041938304901123s
Consistency | Check Ontology hijacking for Linked Open Vocabularies (LOV) took 6.574084758758545s
Consistency | Check Invalid usage of undefined classes for Linked Open Vocabularies (LOV) took 1.3763620853424072s
Conciseness | Check Extensional conciseness for Linked Open Vocabularies (LOV) took 2.9106249809265137s
Conciseness | Check Intensional conciseness for Linked Open Vocabularies (LOV) took 2.2720282077789307s
Security | Sign check for Linked Open Vocabularies (LOV) took 0.19425010681152344s
Availability | Check URIs Dereferenciability for Linked Open Vocabularies (LOV) took 6349.300173997879s
Completeness | Calculation of interlinking completeness for Linked Open Vocabularies (LOV) took 1.149587869644165s
Reputation | Calculation of the PageRank for Linked Open Vocabularies (LOV) took 0.023154020309448242s
Interlinking | Calculation of Degree of Connection for Linked Open Vocabularies (LOV) took 7.05718994140625e-05s
Interlinking | Calculation of Centrality for Linked Open Vocabularies (LOV) took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Linked Open Vocabularies (LOV) took 7.271766662597656e-05s
Interoperability | Check the re-using of existing vocabs for Linked Open Vocabularies (LOV) took 16.380470514297485s
Believability | Calculation of trust value for Linked Open Vocabularies (LOV) took 1.5974044799804688e-05s
INFO | --- Analysis for linked-open-vocabularies-lov took 7376.3606724739075s
Availability | SPARQL endpoint availability check for Linked Periodicals Database took 4.57763671875e-05s
Availability | VoID file availability check for Linked Periodicals Database took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for Linked Periodicals Database took 0.3018057346343994s
Reputation | Calculation of the PageRank for Linked Periodicals Database took 0.021084308624267578s
Interlinking | Calculation of Degree of Connection for Linked Periodicals Database took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Linked Periodicals Database took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Linked Periodicals Database took 4.649162292480469e-05s
Believability | Calculation of trust value for Linked Periodicals Database took 1.0251998901367188e-05s
INFO | --- Analysis for linked-periodicals took 2.9908900260925293s
Availability | SPARQL endpoint availability check for Linked Index took 4.38690185546875e-05s
Availability | VoID file availability check for Linked Index took 0.0006506443023681641s
Completeness | Calculation of interlinking completeness for Linked Index took 0.2846870422363281s
Reputation | Calculation of the PageRank for Linked Index took 0.02087712287902832s
Interlinking | Calculation of Degree of Connection for Linked Index took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Linked Index took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Linked Index took 8.893013000488281e-05s
Believability | Calculation of trust value for Linked Index took 1.4543533325195312e-05s
INFO | --- Analysis for linked-stockindex took 3.6061768531799316s
Availability | SPARQL endpoint availability check for Linked Structured Product Labels took 5.01610803604126s
Availability | VoID file availability check for Linked Structured Product Labels took 0.0006287097930908203s
Completeness | Calculation of interlinking completeness for Linked Structured Product Labels took 0.2936689853668213s
Reputation | Calculation of the PageRank for Linked Structured Product Labels took 0.02099132537841797s
Interlinking | Calculation of Degree of Connection for Linked Structured Product Labels took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Linked Structured Product Labels took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Linked Structured Product Labels took 4.291534423828125e-05s
Believability | Calculation of trust value for Linked Structured Product Labels took 1.2636184692382812e-05s
INFO | --- Analysis for linked-structured-product-labels took 19.10287308692932s
Availability | SPARQL endpoint availability check for Linked Taiwan Geo-Names took 0.04616856575012207s
Availability | VoID file availability check for Linked Taiwan Geo-Names took 0.00031828880310058594s
Completeness | Calculation of interlinking completeness for Linked Taiwan Geo-Names took 0.29570841789245605s
Reputation | Calculation of the PageRank for Linked Taiwan Geo-Names took 0.021319150924682617s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Geo-Names took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Geo-Names took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Geo-Names took 4.553794860839844e-05s
Believability | Calculation of trust value for Linked Taiwan Geo-Names took 9.5367431640625e-06s
INFO | --- Analysis for linked-taiwan-geo-names took 2.824571132659912s
Availability | SPARQL endpoint availability check for Linked TCGA took 20.26007390022278s
Availability | VoID file availability check for Linked TCGA took 0.0007650852203369141s
Completeness | Calculation of interlinking completeness for Linked TCGA took 0.2891824245452881s
Reputation | Calculation of the PageRank for Linked TCGA took 0.020839214324951172s
Interlinking | Calculation of Degree of Connection for Linked TCGA took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Linked TCGA took 0.0007967948913574219s
Interlinking | Calculation of Clustering coefficient for Linked TCGA took 9.369850158691406e-05s
Believability | Calculation of trust value for Linked TCGA took 1.3828277587890625e-05s
INFO | --- Analysis for linked-tcga took 63.68909788131714s
Availability | SPARQL endpoint availability check for Linked User Feedback took 0.08063530921936035s
Availability | VoID file availability check for Linked User Feedback took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for Linked User Feedback took 0.2896862030029297s
Reputation | Calculation of the PageRank for Linked User Feedback took 0.02107405662536621s
Interlinking | Calculation of Degree of Connection for Linked User Feedback took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Linked User Feedback took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Linked User Feedback took 5.125999450683594e-05s
Believability | Calculation of trust value for Linked User Feedback took 1.33514404296875e-05s
INFO | --- Analysis for linked-user-feedback took 2.8765718936920166s
Availability | SPARQL endpoint availability check for USPTO Patent data took 9.822845458984375e-05s
Availability | VoID file availability check for USPTO Patent data took 0.0006201267242431641s
Completeness | Calculation of interlinking completeness for USPTO Patent data took 0.32865095138549805s
Reputation | Calculation of the PageRank for USPTO Patent data took 0.021593093872070312s
Interlinking | Calculation of Degree of Connection for USPTO Patent data took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for USPTO Patent data took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for USPTO Patent data took 9.393692016601562e-05s
Believability | Calculation of trust value for USPTO Patent data took 9.775161743164062e-06s
INFO | --- Analysis for linked-uspto-patent-data took 53.55226993560791s
Availability | SPARQL endpoint availability check for Linked Crowdsourced Data took 0.09428548812866211s
Availability | VoID file availability check for Linked Crowdsourced Data took 0.0005877017974853516s
Completeness | Calculation of interlinking completeness for Linked Crowdsourced Data took 0.29971909523010254s
Reputation | Calculation of the PageRank for Linked Crowdsourced Data took 0.021039962768554688s
Interlinking | Calculation of Degree of Connection for Linked Crowdsourced Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Linked Crowdsourced Data took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Linked Crowdsourced Data took 3.838539123535156e-05s
Believability | Calculation of trust value for Linked Crowdsourced Data took 9.5367431640625e-06s
INFO | --- Analysis for linkedcrowdsourceddata took 3.1056673526763916s
Availability | SPARQL endpoint availability check for LinkedCT took 1.1897494792938232s
Availability | VoID file availability check for LinkedCT took 0.0006291866302490234s
Completeness | Calculation of interlinking completeness for LinkedCT took 0.2794966697692871s
Reputation | Calculation of the PageRank for LinkedCT took 0.020694255828857422s
Interlinking | Calculation of Degree of Connection for LinkedCT took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for LinkedCT took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for LinkedCT took 0.0001049041748046875s
Believability | Calculation of trust value for LinkedCT took 1.4066696166992188e-05s
INFO | --- Analysis for linkedct took 5.292689561843872s
Availability | SPARQL endpoint availability check for LinkedGeoData took 0.16190719604492188s
Availability | VoID file availability check for LinkedGeoData took 0.0006136894226074219s
Extra | Recovery of all triples for LinkedGeoData took 6.952179431915283s
Performance | Total latancy measurement for LinkedGeoData took 0.6785624027252197s
Amount of data | Number of triples check for LinkedGeoData took 94.77301096916199s
Interoperability | New terms check for LinkedGeoData took 91.759268283844s
Versatility | Languages check for LinkedGeoData took 182.14109659194946s
Interpretability | Number of blank nodes check for LinkedGeoData took 0.22609543800354004s
Security | Check HTTPS for LinkedGeoData took 0.30735158920288086s
Interpretability | RDF structures check for LinkedGeoData took 0.9159321784973145s
Versatility | Serialization formats check for LinkedGeoData took 0.37038230895996094s
Availability | RDF dump link check for LinkedGeoData took 0.15210700035095215s
License | MR license check for LinkedGeoData took 0.6650495529174805s
License | HR license check for LinkedGeoData took 118.58174419403076s
Amount of data | Number of property check for LinkedGeoData took 0.2519855499267578s
Understandability | Number of label check for LinkedGeoData took 2.1811599731445312s
Understandability | URI regex check for LinkedGeoData took 0.38370203971862793s
Understandability | Vocabs check for LinkedGeoData took 0.16783642768859863s
Verifiability | Authors check for LinkedGeoData took 0.16580915451049805s
Verifiability | Publishers check for LinkedGeoData took 0.12928152084350586s
Performance | Throughput check for LinkedGeoData took 10.302165508270264s
Amount of data | Check the number of entities for LinkedGeoData took 0.06918478012084961s
Verifiability | Contribs. check for LinkedGeoData took 2.1627535820007324s
Interlinking | sameAs chians check for LinkedGeoData took 0.574068546295166s
Interlinking | skos check for LinkedGeoData took 0.4219980239868164s
Interlinking | skos check for LinkedGeoData took 0.11883139610290527s
Timeliness | dataset update frequency check for LinkedGeoData took 0.39292311668395996s
Currency | Creation date check for LinkedGeoData took 0.47718071937561035s
Currency | Modification date check for LinkedGeoData took 2.6318275928497314s
Rep.Conc. | URIs length for LinkedGeoData took 272.0366063117981s
Interoperability | New vocabularies check for LinkedGeoData took 14.105792760848999s
Consistency | Deprecated classes/propertiers check for LinkedGeoData took 0.16719818115234375s
Accuracy | Check Functional Property for LinkedGeoData took 0.23407840728759766s
Accuracy | Check Inverse Functional Property for LinkedGeoData took 0.1984550952911377s
Accuracy | Check Empty annotation labels for LinkedGeoData took 1.8478403091430664s
Accuracy | Check White space in annotation for LinkedGeoData took 0.15825152397155762s
Accuracy | Check Datatype consistency for LinkedGeoData took 0.13859915733337402s
Consistency | Disjoint class check for LinkedGeoData took 0.25102925300598145s
Consistency | Check Misplaced properties for LinkedGeoData took 180.73160123825073s
Consistency | Misplaced classes for LinkedGeoData took 0.6590237617492676s
Consistency | Check Ontology hijacking for LinkedGeoData took 3.7734546661376953s
Consistency | Check Invalid usage of undefined classes for LinkedGeoData took 1.4110870361328125s
Consistency | Check Invalid usage of undefined properties for LinkedGeoData took 182.19865226745605s
Conciseness | Check Extensional conciseness for LinkedGeoData took 0.153090238571167s
Conciseness | Check Intensional conciseness for LinkedGeoData took 0.39227795600891113s
Security | Sign check for LinkedGeoData took 0.7711293697357178s
Availability | Check URIs Dereferenciability for LinkedGeoData took 17.11299467086792s
Completeness | Calculation of interlinking completeness for LinkedGeoData took 0.5546994209289551s
Reputation | Calculation of the PageRank for LinkedGeoData took 0.026598453521728516s
Interlinking | Calculation of Degree of Connection for LinkedGeoData took 8.797645568847656e-05s
Interlinking | Calculation of Centrality for LinkedGeoData took 0.0010862350463867188s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData took 0.00015211105346679688s
Interoperability | Check the re-using of existing vocabs for LinkedGeoData took 14.859215497970581s
Believability | Calculation of trust value for LinkedGeoData took 1.4781951904296875e-05s
INFO | --- Analysis for linkedgeodata took 2255.8534367084503s
Availability | SPARQL endpoint availability check for LinkedLCCN took 14.985697746276855s
Availability | VoID file availability check for LinkedLCCN took 0.0005757808685302734s
Completeness | Calculation of interlinking completeness for LinkedLCCN took 0.34062957763671875s
Reputation | Calculation of the PageRank for LinkedLCCN took 0.02091050148010254s
Interlinking | Calculation of Degree of Connection for LinkedLCCN took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LinkedLCCN took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for LinkedLCCN took 0.00011301040649414062s
Believability | Calculation of trust value for LinkedLCCN took 9.298324584960938e-06s
INFO | --- Analysis for linkedlccn took 31.10250163078308s
Availability | SPARQL endpoint availability check for LinkedMarkMail took 9.202957153320312e-05s
Availability | VoID file availability check for LinkedMarkMail took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for LinkedMarkMail took 0.31891322135925293s
Reputation | Calculation of the PageRank for LinkedMarkMail took 0.021985530853271484s
Interlinking | Calculation of Degree of Connection for LinkedMarkMail took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LinkedMarkMail took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for LinkedMarkMail took 3.933906555175781e-05s
Believability | Calculation of trust value for LinkedMarkMail took 1.430511474609375e-05s
INFO | --- Analysis for linkedmarkmail took 2.9130587577819824s
Availability | SPARQL endpoint availability check for Linked Movie DataBase took 60.05591368675232s
Availability | VoID file availability check for Linked Movie DataBase took 0.0008480548858642578s
Completeness | Calculation of interlinking completeness for Linked Movie DataBase took 0.2837095260620117s
Reputation | Calculation of the PageRank for Linked Movie DataBase took 0.02125263214111328s
Interlinking | Calculation of Degree of Connection for Linked Movie DataBase took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Linked Movie DataBase took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for Linked Movie DataBase took 0.00014781951904296875s
Believability | Calculation of trust value for Linked Movie DataBase took 1.3828277587890625e-05s
INFO | --- Analysis for linkedmdb took 153.20522141456604s
Availability | SPARQL endpoint availability check for LinkedSpending took 0.525277853012085s
Availability | VoID file availability check for LinkedSpending took 0.0006206035614013672s
Completeness | Calculation of interlinking completeness for LinkedSpending took 0.304401159286499s
Reputation | Calculation of the PageRank for LinkedSpending took 0.022564411163330078s
Interlinking | Calculation of Degree of Connection for LinkedSpending took 1.52587890625e-05s
Interlinking | Calculation of Centrality for LinkedSpending took 0.0007851123809814453s
Interlinking | Calculation of Clustering coefficient for LinkedSpending took 8.7738037109375e-05s
Believability | Calculation of trust value for LinkedSpending took 1.3828277587890625e-05s
INFO | --- Analysis for linkedspending took 4.466917276382446s
Availability | SPARQL endpoint availability check for LinkLion - A Link Repository for the Web of Data took 0.06010031700134277s
Availability | VoID file availability check for LinkLion - A Link Repository for the Web of Data took 0.0003123283386230469s
Completeness | Calculation of interlinking completeness for LinkLion - A Link Repository for the Web of Data took 0.3322618007659912s
Reputation | Calculation of the PageRank for LinkLion - A Link Repository for the Web of Data took 0.023485183715820312s
Interlinking | Calculation of Degree of Connection for LinkLion - A Link Repository for the Web of Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LinkLion - A Link Repository for the Web of Data took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for LinkLion - A Link Repository for the Web of Data took 0.00011205673217773438s
Believability | Calculation of trust value for LinkLion - A Link Repository for the Web of Data took 1.049041748046875e-05s
INFO | --- Analysis for linklion took 2.794543981552124s
Availability | SPARQL endpoint availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 600.386271238327s
Availability | VoID file availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0005769729614257812s
Completeness | Calculation of interlinking completeness for Lista de  Encabezamientos de Materia as Linked Open Data took 0.27551960945129395s
Reputation | Calculation of the PageRank for Lista de  Encabezamientos de Materia as Linked Open Data took 0.021294832229614258s
Interlinking | Calculation of Degree of Connection for Lista de  Encabezamientos de Materia as Linked Open Data took 6.890296936035156e-05s
Interlinking | Calculation of Centrality for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Lista de  Encabezamientos de Materia as Linked Open Data took 6.699562072753906e-05s
Believability | Calculation of trust value for Lista de  Encabezamientos de Materia as Linked Open Data took 8.821487426757812e-06s
INFO | --- Analysis for lista-encabezamientos-materia took 1215.092213153839s
Availability | SPARQL endpoint availability check for lobid-organisations took 0.9624330997467041s
Availability | VoID file availability check for lobid-organisations took 0.0006213188171386719s
Completeness | Calculation of interlinking completeness for lobid-organisations took 0.3048861026763916s
Reputation | Calculation of the PageRank for lobid-organisations took 0.02103137969970703s
Interlinking | Calculation of Degree of Connection for lobid-organisations took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for lobid-organisations took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for lobid-organisations took 9.846687316894531e-05s
Believability | Calculation of trust value for lobid-organisations took 1.430511474609375e-05s
INFO | --- Analysis for lobid-organisations took 5.669928312301636s
Availability | SPARQL endpoint availability check for lobid-Bibliographic Resources took 0.788306474685669s
Availability | VoID file availability check for lobid-Bibliographic Resources took 0.0005998611450195312s
Completeness | Calculation of interlinking completeness for lobid-Bibliographic Resources took 0.291672945022583s
Reputation | Calculation of the PageRank for lobid-Bibliographic Resources took 0.020835161209106445s
Interlinking | Calculation of Degree of Connection for lobid-Bibliographic Resources took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for lobid-Bibliographic Resources took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for lobid-Bibliographic Resources took 0.00011181831359863281s
Believability | Calculation of trust value for lobid-Bibliographic Resources took 1.2874603271484375e-05s
INFO | --- Analysis for lobid-resources took 7.869860410690308s
Availability | SPARQL endpoint availability check for Linked Open Colors took 9.012222290039062e-05s
Availability | VoID file availability check for Linked Open Colors took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for Linked Open Colors took 0.32798194885253906s
Reputation | Calculation of the PageRank for Linked Open Colors took 0.021134138107299805s
Interlinking | Calculation of Degree of Connection for Linked Open Colors took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Linked Open Colors took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Linked Open Colors took 7.963180541992188e-05s
Believability | Calculation of trust value for Linked Open Colors took 1.5020370483398438e-05s
INFO | --- Analysis for loc took 7.567165374755859s
Availability | SPARQL endpoint availability check for Location Ontology took 5.698204040527344e-05s
Availability | VoID file availability check for Location Ontology took 0.0014696121215820312s
Completeness | Calculation of interlinking completeness for Location Ontology took 0.2680377960205078s
Reputation | Calculation of the PageRank for Location Ontology took 0.020873069763183594s
Interlinking | Calculation of Degree of Connection for Location Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Location Ontology took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Location Ontology took 3.218650817871094e-05s
Believability | Calculation of trust value for Location Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for Location_Ontology took 5.018323659896851s
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.0005934238433837891s
Completeness | Calculation of interlinking completeness for Linked Open Computer Vision took 0.30032825469970703s
Reputation | Calculation of the PageRank for Linked Open Computer Vision took 0.020525217056274414s
Interlinking | Calculation of Degree of Connection for Linked Open Computer Vision took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Linked Open Computer Vision took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Linked Open Computer Vision took 3.1948089599609375e-05s
Believability | Calculation of trust value for Linked Open Computer Vision took 1.1444091796875e-05s
INFO | --- Analysis for locv took 34.44282531738281s
Availability | SPARQL endpoint availability check for LOD-a-lot took 0.7825863361358643s
Availability | VoID file availability check for LOD-a-lot took 0.0007677078247070312s
Completeness | Calculation of interlinking completeness for LOD-a-lot took 0.30596113204956055s
Reputation | Calculation of the PageRank for LOD-a-lot took 0.020779132843017578s
Interlinking | Calculation of Degree of Connection for LOD-a-lot took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for LOD-a-lot took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for LOD-a-lot took 3.266334533691406e-05s
Believability | Calculation of trust value for LOD-a-lot took 1.2874603271484375e-05s
INFO | --- Analysis for lod-a-lot took 14.370455503463745s
Availability | SPARQL endpoint availability check for LOD2 Project Wiki took 9.083747863769531e-05s
Availability | VoID file availability check for LOD2 Project Wiki took 0.0007486343383789062s
Completeness | Calculation of interlinking completeness for LOD2 Project Wiki took 0.28752756118774414s
Reputation | Calculation of the PageRank for LOD2 Project Wiki took 0.020697832107543945s
Interlinking | Calculation of Degree of Connection for LOD2 Project Wiki took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for LOD2 Project Wiki took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for LOD2 Project Wiki took 9.870529174804688e-05s
Believability | Calculation of trust value for LOD2 Project Wiki took 1.4543533325195312e-05s
INFO | --- Analysis for lod2-project-wiki took 3.6018471717834473s
Availability | SPARQL endpoint availability check for LODAC BDLS took 2.6899795532226562s
Availability | VoID file availability check for LODAC BDLS took 0.0005843639373779297s
Completeness | Calculation of interlinking completeness for LODAC BDLS took 0.36774635314941406s
Reputation | Calculation of the PageRank for LODAC BDLS took 0.02105259895324707s
Interlinking | Calculation of Degree of Connection for LODAC BDLS took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for LODAC BDLS took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for LODAC BDLS took 8.0108642578125e-05s
Believability | Calculation of trust value for LODAC BDLS took 1.5020370483398438e-05s
INFO | --- Analysis for lodac-bdls took 14.135374307632446s
Availability | SPARQL endpoint availability check for lofd took 0.14108586311340332s
Availability | VoID file availability check for lofd took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for lofd took 0.3218693733215332s
Reputation | Calculation of the PageRank for lofd took 0.02167963981628418s
Interlinking | Calculation of Degree of Connection for lofd took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for lofd took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for lofd took 3.457069396972656e-05s
Believability | Calculation of trust value for lofd took 1.5497207641601562e-05s
INFO | --- Analysis for lofd took 2.9590678215026855s
Availability | SPARQL endpoint availability check for Linking Italian University Statistics Project took 270.7903571128845s
Availability | VoID file availability check for Linking Italian University Statistics Project took 0.0008959770202636719s
Completeness | Calculation of interlinking completeness for Linking Italian University Statistics Project took 0.36527013778686523s
Reputation | Calculation of the PageRank for Linking Italian University Statistics Project took 0.021277666091918945s
Interlinking | Calculation of Degree of Connection for Linking Italian University Statistics Project took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Linking Italian University Statistics Project took 0.000789642333984375s
Interlinking | Calculation of Clustering coefficient for Linking Italian University Statistics Project took 7.319450378417969e-05s
Believability | Calculation of trust value for Linking Italian University Statistics Project took 1.0728836059570312e-05s
INFO | --- Analysis for loius took 584.932808637619s
Availability | SPARQL endpoint availability check for The London Gazette - Gazettes Data took 0.5862908363342285s
Availability | VoID file availability check for The London Gazette - Gazettes Data took 0.0005981922149658203s
Completeness | Calculation of interlinking completeness for The London Gazette - Gazettes Data took 0.29107093811035156s
Reputation | Calculation of the PageRank for The London Gazette - Gazettes Data took 0.020944833755493164s
Interlinking | Calculation of Degree of Connection for The London Gazette - Gazettes Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for The London Gazette - Gazettes Data took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for The London Gazette - Gazettes Data took 5.745887756347656e-05s
Believability | Calculation of trust value for The London Gazette - Gazettes Data took 1.0967254638671875e-05s
INFO | --- Analysis for london-gazette took 4.4534454345703125s
Availability | SPARQL endpoint availability check for Weather Stations took 4.7206878662109375e-05s
Availability | VoID file availability check for Weather Stations took 0.0006444454193115234s
Completeness | Calculation of interlinking completeness for Weather Stations took 0.291790246963501s
Reputation | Calculation of the PageRank for Weather Stations took 0.020632505416870117s
Interlinking | Calculation of Degree of Connection for Weather Stations took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Weather Stations took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Weather Stations took 8.368492126464844e-05s
Believability | Calculation of trust value for Weather Stations took 1.1444091796875e-05s
INFO | --- Analysis for los_metar took 8.897429943084717s
Availability | SPARQL endpoint availability check for Lotico took 0.5529861450195312s
Availability | VoID file availability check for Lotico took 0.0005795955657958984s
Completeness | Calculation of interlinking completeness for Lotico took 0.2956089973449707s
Reputation | Calculation of the PageRank for Lotico took 0.02095198631286621s
Interlinking | Calculation of Degree of Connection for Lotico took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Lotico took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Lotico took 8.7738037109375e-05s
Believability | Calculation of trust value for Lotico took 1.4543533325195312e-05s
INFO | --- Analysis for lotico took 4.89766526222229s
Availability | SPARQL endpoint availability check for Lower Layer Super Output Areas took 0.2758944034576416s
Availability | VoID file availability check for Lower Layer Super Output Areas took 0.0006375312805175781s
Extra | Recovery of all triples for Lower Layer Super Output Areas took 1.7062859535217285s
Performance | Total latancy measurement for Lower Layer Super Output Areas took 0.808476448059082s
Amount of data | Number of triples check for Lower Layer Super Output Areas took 0.21338772773742676s
Interoperability | New terms check for Lower Layer Super Output Areas took 1.919306755065918s
Versatility | Languages check for Lower Layer Super Output Areas took 0.5532393455505371s
Interpretability | Number of blank nodes check for Lower Layer Super Output Areas took 30.213688373565674s
Security | Check HTTPS for Lower Layer Super Output Areas took 0.5943901538848877s
Interpretability | RDF structures check for Lower Layer Super Output Areas took 0.14400124549865723s
Versatility | Serialization formats check for Lower Layer Super Output Areas took 0.21870136260986328s
Availability | RDF dump link check for Lower Layer Super Output Areas took 55.751932859420776s
License | MR license check for Lower Layer Super Output Areas took 0.1498396396636963s
License | HR license check for Lower Layer Super Output Areas took 30.233182907104492s
Amount of data | Number of property check for Lower Layer Super Output Areas took 0.2284996509552002s
Understandability | Number of label check for Lower Layer Super Output Areas took 0.14807915687561035s
Understandability | URI regex check for Lower Layer Super Output Areas took 0.5207657814025879s
Understandability | Vocabs check for Lower Layer Super Output Areas took 0.15383362770080566s
Verifiability | Authors check for Lower Layer Super Output Areas took 0.13892030715942383s
Verifiability | Publishers check for Lower Layer Super Output Areas took 0.19704151153564453s
Performance | Throughput check for Lower Layer Super Output Areas took 11.52747392654419s
Amount of data | Check the number of entities for Lower Layer Super Output Areas took 5.936622619628906e-05s
Verifiability | Contribs. check for Lower Layer Super Output Areas took 0.1432490348815918s
Interlinking | sameAs chians check for Lower Layer Super Output Areas took 0.14126825332641602s
Interlinking | skos check for Lower Layer Super Output Areas took 0.2069089412689209s
Interlinking | skos check for Lower Layer Super Output Areas took 0.20778703689575195s
Timeliness | dataset update frequency check for Lower Layer Super Output Areas took 0.14315271377563477s
Currency | Creation date check for Lower Layer Super Output Areas took 0.30145835876464844s
Currency | Modification date check for Lower Layer Super Output Areas took 0.22023582458496094s
Rep.Conc. | URIs length for Lower Layer Super Output Areas took 1.616910696029663s
Interoperability | New vocabularies check for Lower Layer Super Output Areas took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for Lower Layer Super Output Areas took 0.21367192268371582s
Accuracy | Check Functional Property for Lower Layer Super Output Areas took 0.1944901943206787s
Accuracy | Check Inverse Functional Property for Lower Layer Super Output Areas took 0.15016436576843262s
Consistency | Disjoint class check for Lower Layer Super Output Areas took 0.23805904388427734s
Consistency | Check Misplaced properties for Lower Layer Super Output Areas took 0.799537181854248s
Consistency | Check Ontology hijacking for Lower Layer Super Output Areas took 1.4246065616607666s
Consistency | Check Invalid usage of undefined properties for Lower Layer Super Output Areas took 1.7274982929229736s
Conciseness | Check Extensional conciseness for Lower Layer Super Output Areas took 0.00015687942504882812s
Conciseness | Check Intensional conciseness for Lower Layer Super Output Areas took 0.42430877685546875s
Security | Sign check for Lower Layer Super Output Areas took 0.5045418739318848s
Completeness | Calculation of interlinking completeness for Lower Layer Super Output Areas took 0.29181981086730957s
Reputation | Calculation of the PageRank for Lower Layer Super Output Areas took 0.02224254608154297s
Interlinking | Calculation of Degree of Connection for Lower Layer Super Output Areas took 2.5510787963867188e-05s
Interlinking | Calculation of Centrality for Lower Layer Super Output Areas took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Lower Layer Super Output Areas took 5.53131103515625e-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.4543533325195312e-05s
INFO | --- Analysis for lower-layer-super-output-areas took 275.9943013191223s
Availability | SPARQL endpoint availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.6386401653289795s
Availability | VoID file availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.000308990478515625s
Extra | Recovery of all triples for Polish Land Parcel Information System (LPIS) dataset @PSNC took 120.51608514785767s
Performance | Total latancy measurement for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.9757602214813232s
Amount of data | Number of triples check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 9.288512229919434s
Interoperability | New terms check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 14.829902648925781s
Versatility | Languages check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.2233695983887s
Interpretability | Number of blank nodes check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.095564842224121s
Interpretability | RDF structures check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.32878780364990234s
Versatility | Serialization formats check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 7.236990928649902s
Availability | RDF dump link check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.37558889389038086s
License | MR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.616063117980957s
License | HR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.17938446998596s
Amount of data | Number of property check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.21159696578979492s
Understandability | Number of label check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.487086296081543s
Understandability | URI regex check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.280656337738037s
Understandability | Vocabs check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.58355712890625s
Verifiability | Authors check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.20906996726989746s
Verifiability | Publishers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.22463059425354004s
Performance | Throughput check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 11.594535827636719s
Amount of data | Check the number of entities for Polish Land Parcel Information System (LPIS) dataset @PSNC took 7.43865966796875e-05s
Verifiability | Contribs. check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.22095370292663574s
Interlinking | sameAs chians check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2038719654083252s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.49754953384399414s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.4195568561553955s
Timeliness | dataset update frequency check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 4.916027545928955s
Currency | Creation date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.4803323745727539s
Currency | Modification date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.25147056579589844s
Rep.Conc. | URIs length for Polish Land Parcel Information System (LPIS) dataset @PSNC took 155.17390394210815s
Interoperability | New vocabularies check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.3589859008789062e-05s
Consistency | Deprecated classes/propertiers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.20393729209899902s
Accuracy | Check Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.48000383377075195s
Accuracy | Check Inverse Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.428936243057251s
Accuracy | Check Empty annotation labels for Polish Land Parcel Information System (LPIS) dataset @PSNC took 41.56946635246277s
Accuracy | Check White space in annotation for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.6950111389160156s
Accuracy | Check Datatype consistency for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.850970506668091s
Consistency | Disjoint class check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.18662285804748535s
Consistency | Check Misplaced properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 86.51831603050232s
Consistency | Misplaced classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.598801136016846s
Consistency | Check Ontology hijacking for Polish Land Parcel Information System (LPIS) dataset @PSNC took 27.295762538909912s
Consistency | Check Invalid usage of undefined classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.610666275024414s
Consistency | Check Invalid usage of undefined properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 87.5537474155426s
Conciseness | Check Extensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.81125807762146s
Conciseness | Check Intensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.544095516204834s
Security | Sign check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.6263580322265625s
Availability | Check URIs Dereferenciability for Polish Land Parcel Information System (LPIS) dataset @PSNC took 17.435933113098145s
Completeness | Calculation of interlinking completeness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5191307067871094s
Reputation | Calculation of the PageRank for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.02154827117919922s
Interlinking | Calculation of Degree of Connection for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Polish Land Parcel Information System (LPIS) dataset @PSNC took 4.57763671875e-05s
Interoperability | Check the re-using of existing vocabs for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.384185791015625e-06s
Believability | Calculation of trust value for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.3589859008789062e-05s
INFO | --- Analysis for LPIS_(Poland) took 2412.672269821167s
Availability | SPARQL endpoint availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 4.38690185546875e-05s
Availability | VoID file availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0006251335144042969s
Completeness | Calculation of interlinking completeness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 20.14269256591797s
Reputation | Calculation of the PageRank for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.020968198776245117s
Interlinking | Calculation of Degree of Connection for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Land parcel dataset (LPIS) from Czech Republic @PSNC took 4.0531158447265625e-05s
Believability | Calculation of trust value for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.52587890625e-05s
INFO | --- Analysis for LPIS_Czech_Republic took 182.3765881061554s
Availability | SPARQL endpoint availability check for A collection of Authors for LREC2014 and related Workshops took 9.131431579589844e-05s
Availability | VoID file availability check for A collection of Authors for LREC2014 and related Workshops took 0.0006558895111083984s
Completeness | Calculation of interlinking completeness for A collection of Authors for LREC2014 and related Workshops took 0.29677534103393555s
Reputation | Calculation of the PageRank for A collection of Authors for LREC2014 and related Workshops took 0.021003246307373047s
Interlinking | Calculation of Degree of Connection for A collection of Authors for LREC2014 and related Workshops took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for A collection of Authors for LREC2014 and related Workshops took 0.000789642333984375s
Interlinking | Calculation of Clustering coefficient for A collection of Authors for LREC2014 and related Workshops took 3.504753112792969e-05s
Believability | Calculation of trust value for A collection of Authors for LREC2014 and related Workshops took 1.5497207641601562e-05s
INFO | --- Analysis for lremap-auth took 3.4904379844665527s
Availability | SPARQL endpoint availability check for LREC2014 and related Workshops took 8.940696716308594e-05s
Availability | VoID file availability check for LREC2014 and related Workshops took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for LREC2014 and related Workshops took 0.26671719551086426s
Reputation | Calculation of the PageRank for LREC2014 and related Workshops took 0.020687103271484375s
Interlinking | Calculation of Degree of Connection for LREC2014 and related Workshops took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LREC2014 and related Workshops took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for LREC2014 and related Workshops took 3.0994415283203125e-05s
Believability | Calculation of trust value for LREC2014 and related Workshops took 1.3113021850585938e-05s
INFO | --- Analysis for lremap-conf took 2.9250144958496094s
Availability | SPARQL endpoint availability check for First not-normalized set of language resources from LREC2014 took 8.797645568847656e-05s
Availability | VoID file availability check for First not-normalized set of language resources from LREC2014 took 0.0005686283111572266s
Completeness | Calculation of interlinking completeness for First not-normalized set of language resources from LREC2014 took 0.33467698097229004s
Reputation | Calculation of the PageRank for First not-normalized set of language resources from LREC2014 took 0.02078413963317871s
Interlinking | Calculation of Degree of Connection for First not-normalized set of language resources from LREC2014 took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for First not-normalized set of language resources from LREC2014 took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for First not-normalized set of language resources from LREC2014 took 3.457069396972656e-05s
Believability | Calculation of trust value for First not-normalized set of language resources from LREC2014 took 9.059906005859375e-06s
INFO | --- Analysis for lremap-ri took 2.8189847469329834s
Availability | SPARQL endpoint availability check for A collection of Submissions for LREC2014 and related Workshops took 4.482269287109375e-05s
Availability | VoID file availability check for A collection of Submissions for LREC2014 and related Workshops took 0.0005428791046142578s
Completeness | Calculation of interlinking completeness for A collection of Submissions for LREC2014 and related Workshops took 0.2945411205291748s
Reputation | Calculation of the PageRank for A collection of Submissions for LREC2014 and related Workshops took 0.020725488662719727s
Interlinking | Calculation of Degree of Connection for A collection of Submissions for LREC2014 and related Workshops took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for A collection of Submissions for LREC2014 and related Workshops took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for A collection of Submissions for LREC2014 and related Workshops took 3.1948089599609375e-05s
Believability | Calculation of trust value for A collection of Submissions for LREC2014 and related Workshops took 1.0013580322265625e-05s
INFO | --- Analysis for lremap-sub took 2.8641183376312256s
Availability | SPARQL endpoint availability check for LSQ took 5.125999450683594e-05s
Availability | VoID file availability check for LSQ took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for LSQ took 0.2806715965270996s
Reputation | Calculation of the PageRank for LSQ took 0.02073812484741211s
Interlinking | Calculation of Degree of Connection for LSQ took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for LSQ took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for LSQ took 3.266334533691406e-05s
Believability | Calculation of trust value for LSQ took 1.52587890625e-05s
INFO | --- Analysis for lsq took 4.092797517776489s
Availability | SPARQL endpoint availability check for Lucani Pharsalia in LiLa took 0.5846679210662842s
Availability | VoID file availability check for Lucani Pharsalia in LiLa took 0.0007069110870361328s
Completeness | Calculation of interlinking completeness for Lucani Pharsalia in LiLa took 0.28014421463012695s
Reputation | Calculation of the PageRank for Lucani Pharsalia in LiLa took 0.022119998931884766s
Interlinking | Calculation of Degree of Connection for Lucani Pharsalia in LiLa took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Lucani Pharsalia in LiLa took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Lucani Pharsalia in LiLa took 4.220008850097656e-05s
Believability | Calculation of trust value for Lucani Pharsalia in LiLa took 9.5367431640625e-06s
INFO | --- Analysis for LucaniPharsalia took 4.313401937484741s
Availability | SPARQL endpoint availability check for Linked rules took 4.458427429199219e-05s
Availability | VoID file availability check for Linked rules took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for Linked rules took 0.2942190170288086s
Reputation | Calculation of the PageRank for Linked rules took 0.020668745040893555s
Interlinking | Calculation of Degree of Connection for Linked rules took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Linked rules took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Linked rules took 3.457069396972656e-05s
Believability | Calculation of trust value for Linked rules took 1.33514404296875e-05s
INFO | --- Analysis for Luminaires_senlis took 2.724191665649414s
Availability | SPARQL endpoint availability check for Microsoft Academic Knowledge Graph took 30.2348210811615s
Availability | VoID file availability check for Microsoft Academic Knowledge Graph took 0.0006768703460693359s
Completeness | Calculation of interlinking completeness for Microsoft Academic Knowledge Graph took 0.2919156551361084s
Reputation | Calculation of the PageRank for Microsoft Academic Knowledge Graph took 0.020768165588378906s
Interlinking | Calculation of Degree of Connection for Microsoft Academic Knowledge Graph took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Microsoft Academic Knowledge Graph took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Microsoft Academic Knowledge Graph took 3.218650817871094e-05s
Believability | Calculation of trust value for Microsoft Academic Knowledge Graph took 1.4543533325195312e-05s
INFO | --- Analysis for makg took 64.03164052963257s
Availability | SPARQL endpoint availability check for Manchester University Reading Lists took 4.553794860839844e-05s
Availability | VoID file availability check for Manchester University Reading Lists took 0.0007102489471435547s
Completeness | Calculation of interlinking completeness for Manchester University Reading Lists took 0.3415801525115967s
Reputation | Calculation of the PageRank for Manchester University Reading Lists took 0.022432565689086914s
Interlinking | Calculation of Degree of Connection for Manchester University Reading Lists took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Manchester University Reading Lists took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Manchester University Reading Lists took 4.029273986816406e-05s
Believability | Calculation of trust value for Manchester University Reading Lists took 1.5020370483398438e-05s
INFO | --- Analysis for manchester-university-reading-lists took 3.8688132762908936s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 9.1552734375e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.0006849765777587891s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.31871867179870605s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.022953510284423828s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 3.2901763916015625e-05s
Believability | Calculation of trust value for engineering equipment ontology took 1.2874603271484375e-05s
INFO | --- Analysis for manish took 2.8273086547851562s
Availability | SPARQL endpoint availability check for MARC Codes List took 9.012222290039062e-05s
Availability | VoID file availability check for MARC Codes List took 0.0003616809844970703s
Completeness | Calculation of interlinking completeness for MARC Codes List took 0.30310893058776855s
Reputation | Calculation of the PageRank for MARC Codes List took 0.021088838577270508s
Interlinking | Calculation of Degree of Connection for MARC Codes List took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for MARC Codes List took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for MARC Codes List took 0.00012922286987304688s
Believability | Calculation of trust value for MARC Codes List took 1.4066696166992188e-05s
INFO | --- Analysis for marc-codes took 13.796372890472412s
Availability | SPARQL endpoint availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 9.202957153320312e-05s
Availability | VoID file availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.000640869140625s
Completeness | Calculation of interlinking completeness for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.3054826259613037s
Reputation | Calculation of the PageRank for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.02082538604736328s
Interlinking | Calculation of Degree of Connection for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 4.553794860839844e-05s
Believability | Calculation of trust value for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.52587890625e-05s
INFO | --- Analysis for masc took 6.2547712326049805s
Availability | SPARQL endpoint availability check for MASC-BN-NIF took 4.506111145019531e-05s
Availability | VoID file availability check for MASC-BN-NIF took 0.0005536079406738281s
Completeness | Calculation of interlinking completeness for MASC-BN-NIF took 0.2703096866607666s
Reputation | Calculation of the PageRank for MASC-BN-NIF took 0.02082228660583496s
Interlinking | Calculation of Degree of Connection for MASC-BN-NIF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for MASC-BN-NIF took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for MASC-BN-NIF took 4.029273986816406e-05s
Believability | Calculation of trust value for MASC-BN-NIF took 1.52587890625e-05s
INFO | --- Analysis for masc-bn-nif took 2.7378904819488525s
Availability | SPARQL endpoint availability check for Mass Observation Archive catalogue took 0.1318652629852295s
Availability | VoID file availability check for Mass Observation Archive catalogue took 0.0004558563232421875s
Completeness | Calculation of interlinking completeness for Mass Observation Archive catalogue took 0.2768983840942383s
Reputation | Calculation of the PageRank for Mass Observation Archive catalogue took 0.021017074584960938s
Interlinking | Calculation of Degree of Connection for Mass Observation Archive catalogue took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Mass Observation Archive catalogue took 0.0007882118225097656s
Interlinking | Calculation of Clustering coefficient for Mass Observation Archive catalogue took 3.600120544433594e-05s
Believability | Calculation of trust value for Mass Observation Archive catalogue took 1.33514404296875e-05s
INFO | --- Analysis for massobservationarchivecatalogue took 3.025303840637207s
Availability | SPARQL endpoint availability check for medline took 8.988380432128906e-05s
Availability | VoID file availability check for medline took 0.0008220672607421875s
Completeness | Calculation of interlinking completeness for medline took 0.33167076110839844s
Reputation | Calculation of the PageRank for medline took 0.0210421085357666s
Interlinking | Calculation of Degree of Connection for medline took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for medline took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for medline took 4.458427429199219e-05s
Believability | Calculation of trust value for medline took 1.4066696166992188e-05s
INFO | --- Analysis for medline took 7.25307297706604s
Availability | SPARQL endpoint availability check for mEducator: Linked Educational Resources took 1.700397253036499s
Availability | VoID file availability check for mEducator: Linked Educational Resources took 0.0008256435394287109s
Completeness | Calculation of interlinking completeness for mEducator: Linked Educational Resources took 0.2927830219268799s
Reputation | Calculation of the PageRank for mEducator: Linked Educational Resources took 0.022458314895629883s
Interlinking | Calculation of Degree of Connection for mEducator: Linked Educational Resources took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for mEducator: Linked Educational Resources took 0.0008563995361328125s
Interlinking | Calculation of Clustering coefficient for mEducator: Linked Educational Resources took 7.176399230957031e-05s
Believability | Calculation of trust value for mEducator: Linked Educational Resources took 1.4543533325195312e-05s
INFO | --- Analysis for meducator took 12.48292350769043s
Availability | SPARQL endpoint availability check for MetaShare metadata model took 8.821487426757812e-05s
Availability | VoID file availability check for MetaShare metadata model took 0.0005331039428710938s
Completeness | Calculation of interlinking completeness for MetaShare metadata model took 0.3096797466278076s
Reputation | Calculation of the PageRank for MetaShare metadata model took 0.020697355270385742s
Interlinking | Calculation of Degree of Connection for MetaShare metadata model took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for MetaShare metadata model took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for MetaShare metadata model took 7.987022399902344e-05s
Believability | Calculation of trust value for MetaShare metadata model took 1.430511474609375e-05s
INFO | --- Analysis for metashare took 2.7528083324432373s
Availability | SPARQL endpoint availability check for MExiCo took 4.57763671875e-05s
Availability | VoID file availability check for MExiCo took 0.0007801055908203125s
Completeness | Calculation of interlinking completeness for MExiCo took 0.2830953598022461s
Reputation | Calculation of the PageRank for MExiCo took 0.021558761596679688s
Interlinking | Calculation of Degree of Connection for MExiCo took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for MExiCo took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for MExiCo took 5.221366882324219e-05s
Believability | Calculation of trust value for MExiCo took 1.5020370483398438e-05s
INFO | --- Analysis for mexico took 22.93924832344055s
Availability | SPARQL endpoint availability check for Coronavirus dataset took 1.0536932945251465s
Availability | VoID file availability check for Coronavirus dataset took 0.0005283355712890625s
Extra | Recovery of all triples for Coronavirus dataset took 5.9950478076934814s
Performance | Total latancy measurement for Coronavirus dataset took 2.537813663482666s
Amount of data | Number of triples check for Coronavirus dataset took 1.1577961444854736s
Interoperability | New terms check for Coronavirus dataset took 2.772334337234497s
Versatility | Languages check for Coronavirus dataset took 60.5285108089447s
Interpretability | Number of blank nodes check for Coronavirus dataset took 3.4463961124420166s
Interpretability | RDF structures check for Coronavirus dataset took 0.5460615158081055s
Versatility | Serialization formats check for Coronavirus dataset took 0.5518832206726074s
Availability | RDF dump link check for Coronavirus dataset took 0.5716273784637451s
License | MR license check for Coronavirus dataset took 0.5614113807678223s
License | HR license check for Coronavirus dataset took 42.19868087768555s
Amount of data | Number of property check for Coronavirus dataset took 0.5258095264434814s
Understandability | Number of label check for Coronavirus dataset took 1.4492077827453613s
Understandability | URI regex check for Coronavirus dataset took 1.0019471645355225s
Understandability | Vocabs check for Coronavirus dataset took 0.5084903240203857s
Verifiability | Authors check for Coronavirus dataset took 0.5046441555023193s
Verifiability | Publishers check for Coronavirus dataset took 0.4925692081451416s
Performance | Throughput check for Coronavirus dataset took 14.3548424243927s
Amount of data | Check the number of entities for Coronavirus dataset took 3.361701965332031e-05s
Verifiability | Contribs. check for Coronavirus dataset took 0.5014369487762451s
Interlinking | sameAs chians check for Coronavirus dataset took 0.538048505783081s
Interlinking | skos check for Coronavirus dataset took 0.5529987812042236s
Interlinking | skos check for Coronavirus dataset took 0.4892570972442627s
Timeliness | dataset update frequency check for Coronavirus dataset took 0.500579833984375s
Currency | Creation date check for Coronavirus dataset took 1.029247522354126s
Currency | Modification date check for Coronavirus dataset took 1.0186896324157715s
Rep.Conc. | URIs length for Coronavirus dataset took 8.446548700332642s
Interoperability | New vocabularies check for Coronavirus dataset took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Coronavirus dataset took 0.5273938179016113s
Accuracy | Check Functional Property for Coronavirus dataset took 0.6997768878936768s
Accuracy | Check Inverse Functional Property for Coronavirus dataset took 0.5352988243103027s
Accuracy | Check Empty annotation labels for Coronavirus dataset took 2.0995538234710693s
Accuracy | Check White space in annotation for Coronavirus dataset took 0.022435665130615234s
Accuracy | Check Datatype consistency for Coronavirus dataset took 0.028501272201538086s
Consistency | Disjoint class check for Coronavirus dataset took 0.9342122077941895s
Consistency | Check Misplaced properties for Coronavirus dataset took 7.616019010543823s
Consistency | Misplaced classes for Coronavirus dataset took 0.6263113021850586s
Consistency | Check Ontology hijacking for Coronavirus dataset took 3.528519868850708s
Consistency | Check Invalid usage of undefined classes for Coronavirus dataset took 1.4198644161224365s
Consistency | Check Invalid usage of undefined properties for Coronavirus dataset took 6.877202033996582s
Conciseness | Check Extensional conciseness for Coronavirus dataset took 0.03269600868225098s
Conciseness | Check Intensional conciseness for Coronavirus dataset took 0.5389857292175293s
Security | Sign check for Coronavirus dataset took 0.5175595283508301s
Availability | Check URIs Dereferenciability for Coronavirus dataset took 3191.0994675159454s
Completeness | Calculation of interlinking completeness for Coronavirus dataset took 0.6142582893371582s
Reputation | Calculation of the PageRank for Coronavirus dataset took 0.021211624145507812s
Interlinking | Calculation of Degree of Connection for Coronavirus dataset took 7.796287536621094e-05s
Interlinking | Calculation of Centrality for Coronavirus dataset took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Coronavirus dataset took 8.249282836914062e-05s
Interoperability | Check the re-using of existing vocabs for Coronavirus dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for Coronavirus dataset took 1.3828277587890625e-05s
INFO | --- Analysis for micro-coronavirus took 3426.8858206272125s
Availability | SPARQL endpoint availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 6.031990051269531e-05s
Availability | VoID file availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0005512237548828125s
Completeness | Calculation of interlinking completeness for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.4369852542877197s
Reputation | Calculation of the PageRank for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.02035975456237793s
Interlinking | Calculation of Degree of Connection for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0001068115234375s
Believability | Calculation of trust value for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 1.3828277587890625e-05s
INFO | --- Analysis for miguiadeviajes-gnoss took 5.428851842880249s
Availability | SPARQL endpoint availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 9.512901306152344e-05s
Availability | VoID file availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.000720977783203125s
Completeness | Calculation of interlinking completeness for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.3047816753387451s
Reputation | Calculation of the PageRank for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.02084827423095703s
Interlinking | Calculation of Degree of Connection for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.00014543533325195312s
Believability | Calculation of trust value for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 1.049041748046875e-05s
INFO | --- Analysis for mismuseos-gnoss took 14.130846738815308s
Availability | SPARQL endpoint availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.10030984878540039s
Availability | VoID file availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0003046989440917969s
Completeness | Calculation of interlinking completeness for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.2774312496185303s
Reputation | Calculation of the PageRank for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.020963191986083984s
Interlinking | Calculation of Degree of Connection for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0007872581481933594s
Interlinking | Calculation of Clustering coefficient for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 4.9591064453125e-05s
Believability | Calculation of trust value for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 1.3828277587890625e-05s
INFO | --- Analysis for mlsa took 3.3638603687286377s
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.0006844997406005859s
Completeness | Calculation of interlinking completeness for Atmospheric Correction of High Resolution Optical Images model took 0.2976541519165039s
Reputation | Calculation of the PageRank for Atmospheric Correction of High Resolution Optical Images model took 0.021929264068603516s
Interlinking | Calculation of Degree of Connection for Atmospheric Correction of High Resolution Optical Images model took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Atmospheric Correction of High Resolution Optical Images model took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Atmospheric Correction of High Resolution Optical Images model took 3.314018249511719e-05s
Believability | Calculation of trust value for Atmospheric Correction of High Resolution Optical Images model took 1.5020370483398438e-05s
INFO | --- Analysis for model took 34.651402711868286s
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 0.00010013580322265625s
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.0006406307220458984s
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.31594300270080566s
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.023210763931274414s
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.0007581710815429688s
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 3.075599670410156e-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.4543533325195312e-05s
INFO | --- Analysis for model1 took 20.812676191329956s
Availability | SPARQL endpoint availability check for MORElab took 1.0568327903747559s
Availability | VoID file availability check for MORElab took 0.0007646083831787109s
Completeness | Calculation of interlinking completeness for MORElab took 0.28639912605285645s
Reputation | Calculation of the PageRank for MORElab took 0.02077341079711914s
Interlinking | Calculation of Degree of Connection for MORElab took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for MORElab took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for MORElab took 9.560585021972656e-05s
Believability | Calculation of trust value for MORElab took 1.5020370483398438e-05s
INFO | --- Analysis for morelab took 5.388138055801392s
Availability | SPARQL endpoint availability check for Mathematics Subject Classification took 3.0194578170776367s
Availability | VoID file availability check for Mathematics Subject Classification took 0.0008089542388916016s
Completeness | Calculation of interlinking completeness for Mathematics Subject Classification took 0.28988170623779297s
Reputation | Calculation of the PageRank for Mathematics Subject Classification took 0.028827190399169922s
Interlinking | Calculation of Degree of Connection for Mathematics Subject Classification took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Mathematics Subject Classification took 0.0013339519500732422s
Interlinking | Calculation of Clustering coefficient for Mathematics Subject Classification took 0.00012540817260742188s
Believability | Calculation of trust value for Mathematics Subject Classification took 1.4066696166992188e-05s
INFO | --- Analysis for msc took 18.435885190963745s
Availability | SPARQL endpoint availability check for Multext-East took 9.441375732421875e-05s
Availability | VoID file availability check for Multext-East took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for Multext-East took 0.2816965579986572s
Reputation | Calculation of the PageRank for Multext-East took 0.020421981811523438s
Interlinking | Calculation of Degree of Connection for Multext-East took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Multext-East took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Multext-East took 3.743171691894531e-05s
Believability | Calculation of trust value for Multext-East took 9.059906005859375e-06s
INFO | --- Analysis for multext-east took 3.080601215362549s
Availability | SPARQL endpoint availability check for Multimedia Lab took 9.393692016601562e-05s
Availability | VoID file availability check for Multimedia Lab took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for Multimedia Lab took 0.2906327247619629s
Reputation | Calculation of the PageRank for Multimedia Lab took 0.020765304565429688s
Interlinking | Calculation of Degree of Connection for Multimedia Lab took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Multimedia Lab took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Multimedia Lab took 3.8623809814453125e-05s
Believability | Calculation of trust value for Multimedia Lab took 1.4781951904296875e-05s
INFO | --- Analysis for multimedia-lab took 2.858429193496704s
Availability | SPARQL endpoint availability check for Muninn World War I took 1.7246675491333008s
Availability | VoID file availability check for Muninn World War I took 0.0005438327789306641s
Completeness | Calculation of interlinking completeness for Muninn World War I took 0.3423731327056885s
Reputation | Calculation of the PageRank for Muninn World War I took 0.020733118057250977s
Interlinking | Calculation of Degree of Connection for Muninn World War I took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Muninn World War I took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for Muninn World War I took 8.606910705566406e-05s
Believability | Calculation of trust value for Muninn World War I took 1.4066696166992188e-05s
INFO | --- Analysis for muninn-world-war-i took 11.285828351974487s
Availability | SPARQL endpoint availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.00011348724365234375s
Availability | VoID file availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0005857944488525391s
Completeness | Calculation of interlinking completeness for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.2925758361816406s
Reputation | Calculation of the PageRank for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.021327495574951172s
Interlinking | Calculation of Degree of Connection for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0007910728454589844s
Interlinking | Calculation of Clustering coefficient for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.00011944770812988281s
Believability | Calculation of trust value for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.4543533325195312e-05s
INFO | --- Analysis for museosespania-gnoss took 67.18781638145447s
Availability | SPARQL endpoint availability check for Italian Museums took 1.4843382835388184s
Availability | VoID file availability check for Italian Museums took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for Italian Museums took 0.28739309310913086s
Reputation | Calculation of the PageRank for Italian Museums took 0.02108001708984375s
Interlinking | Calculation of Degree of Connection for Italian Museums took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Italian Museums took 0.0007946491241455078s
Interlinking | Calculation of Clustering coefficient for Italian Museums took 8.7738037109375e-05s
Believability | Calculation of trust value for Italian Museums took 1.3828277587890625e-05s
INFO | --- Analysis for museums-in-italy took 4.332802772521973s
Availability | SPARQL endpoint availability check for Muziekweb took 0.7279746532440186s
Availability | VoID file availability check for Muziekweb took 0.0006721019744873047s
Extra | Recovery of all triples for Muziekweb took 1.4703912734985352s
Performance | Total latancy measurement for Muziekweb took 1.5127513408660889s
Amount of data | Number of triples check for Muziekweb took 0.4306480884552002s
Interoperability | New terms check for Muziekweb took 1.8550078868865967s
Versatility | Languages check for Muziekweb took 53.558035373687744s
Interpretability | Number of blank nodes check for Muziekweb took 0.3314974308013916s
Interpretability | RDF structures check for Muziekweb took 0.3281559944152832s
Versatility | Serialization formats check for Muziekweb took 0.31113457679748535s
Availability | RDF dump link check for Muziekweb took 0.30519986152648926s
License | MR license check for Muziekweb took 0.3356485366821289s
License | HR license check for Muziekweb took 10.987143278121948s
Amount of data | Number of property check for Muziekweb took 0.3080286979675293s
Understandability | Number of label check for Muziekweb took 0.3405947685241699s
Understandability | URI regex check for Muziekweb took 0.6157848834991455s
Understandability | Vocabs check for Muziekweb took 0.30271339416503906s
Verifiability | Authors check for Muziekweb took 0.3109302520751953s
Verifiability | Publishers check for Muziekweb took 0.35926365852355957s
Performance | Throughput check for Muziekweb took 12.05435848236084s
Amount of data | Check the number of entities for Muziekweb took 7.343292236328125e-05s
Verifiability | Contribs. check for Muziekweb took 0.3526725769042969s
Interlinking | sameAs chians check for Muziekweb took 0.32912707328796387s
Interlinking | skos check for Muziekweb took 0.3137929439544678s
Interlinking | skos check for Muziekweb took 0.30286192893981934s
Timeliness | dataset update frequency check for Muziekweb took 0.34435534477233887s
Currency | Creation date check for Muziekweb took 0.8679530620574951s
Currency | Modification date check for Muziekweb took 0.8742308616638184s
Rep.Conc. | URIs length for Muziekweb took 1.940406084060669s
Interoperability | New vocabularies check for Muziekweb took 5.245208740234375e-06s
Consistency | Deprecated classes/propertiers check for Muziekweb took 0.29167771339416504s
Accuracy | Check Functional Property for Muziekweb took 0.5867223739624023s
Accuracy | Check Inverse Functional Property for Muziekweb took 0.5192410945892334s
Accuracy | Check Empty annotation labels for Muziekweb took 2.397805690765381s
Accuracy | Check White space in annotation for Muziekweb took 0.029083728790283203s
Accuracy | Check Datatype consistency for Muziekweb took 0.029646873474121094s
Consistency | Disjoint class check for Muziekweb took 0.47823071479797363s
Consistency | Check Misplaced properties for Muziekweb took 1.1815803050994873s
Consistency | Check Ontology hijacking for Muziekweb took 2.1166136264801025s
Consistency | Check Invalid usage of undefined classes for Muziekweb took 1.4138154983520508s
Consistency | Check Invalid usage of undefined properties for Muziekweb took 1.7532570362091064s
Conciseness | Check Extensional conciseness for Muziekweb took 0.03363227844238281s
Conciseness | Check Intensional conciseness for Muziekweb took 0.3145029544830322s
Security | Sign check for Muziekweb took 0.31492090225219727s
Availability | Check URIs Dereferenciability for Muziekweb took 2013.9526224136353s
Completeness | Calculation of interlinking completeness for Muziekweb took 0.5186970233917236s
Reputation | Calculation of the PageRank for Muziekweb took 0.022032737731933594s
Interlinking | Calculation of Degree of Connection for Muziekweb took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Muziekweb took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Muziekweb took 7.176399230957031e-05s
Interoperability | Check the re-using of existing vocabs for Muziekweb took 1.430511474609375e-06s
Believability | Calculation of trust value for Muziekweb took 1.1682510375976562e-05s
INFO | --- Analysis for muziekweb took 2142.628987312317s
Availability | SPARQL endpoint availability check for myExperiment took 130.79702854156494s
Availability | VoID file availability check for myExperiment took 0.0007309913635253906s
Completeness | Calculation of interlinking completeness for myExperiment took 0.35446977615356445s
Reputation | Calculation of the PageRank for myExperiment took 0.021169424057006836s
Interlinking | Calculation of Degree of Connection for myExperiment took 6.890296936035156e-05s
Interlinking | Calculation of Centrality for myExperiment took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for myExperiment took 0.00013375282287597656s
Believability | Calculation of trust value for myExperiment took 1.2636184692382812e-05s
INFO | --- Analysis for my-experiment took 1181.8207640647888s
Availability | SPARQL endpoint availability check for My Family Lineage took 0.07790970802307129s
Availability | VoID file availability check for My Family Lineage took 0.0006122589111328125s
Completeness | Calculation of interlinking completeness for My Family Lineage took 0.28972411155700684s
Reputation | Calculation of the PageRank for My Family Lineage took 0.021327733993530273s
Interlinking | Calculation of Degree of Connection for My Family Lineage took 1.52587890625e-05s
Interlinking | Calculation of Centrality for My Family Lineage took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for My Family Lineage took 0.00010204315185546875s
Believability | Calculation of trust value for My Family Lineage took 1.3828277587890625e-05s
INFO | --- Analysis for my-family-lineage took 3.9996707439422607s
Availability | SPARQL endpoint availability check for My ontology test took 1.2538118362426758s
Availability | VoID file availability check for My ontology test took 0.0005676746368408203s
Completeness | Calculation of interlinking completeness for My ontology test took 0.28833770751953125s
Reputation | Calculation of the PageRank for My ontology test took 0.02056598663330078s
Interlinking | Calculation of Degree of Connection for My ontology test took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for My ontology test took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for My ontology test took 3.457069396972656e-05s
Believability | Calculation of trust value for My ontology test took 1.33514404296875e-05s
INFO | --- Analysis for myontologytest took 4.053528070449829s
Availability | SPARQL endpoint availability check for myopenlink dataspaces took 9.083747863769531e-05s
Availability | VoID file availability check for myopenlink dataspaces took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for myopenlink dataspaces took 0.3134291172027588s
Reputation | Calculation of the PageRank for myopenlink dataspaces took 0.020936965942382812s
Interlinking | Calculation of Degree of Connection for myopenlink dataspaces took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for myopenlink dataspaces took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for myopenlink dataspaces took 0.000110626220703125s
Believability | Calculation of trust value for myopenlink dataspaces took 8.821487426757812e-06s
INFO | --- Analysis for myopenlink-dataspaces took 3.388434648513794s
Availability | SPARQL endpoint availability check for N-Lex as Linked Data took 7.545586109161377s
Availability | VoID file availability check for N-Lex as Linked Data took 0.0006539821624755859s
Completeness | Calculation of interlinking completeness for N-Lex as Linked Data took 0.3106667995452881s
Reputation | Calculation of the PageRank for N-Lex as Linked Data took 0.02164459228515625s
Interlinking | Calculation of Degree of Connection for N-Lex as Linked Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for N-Lex as Linked Data took 0.0007965564727783203s
Interlinking | Calculation of Clustering coefficient for N-Lex as Linked Data took 7.653236389160156e-05s
Believability | Calculation of trust value for N-Lex as Linked Data took 1.049041748046875e-05s
INFO | --- Analysis for n-lex-as-linked-data took 19.63362431526184s
Availability | SPARQL endpoint availability check for NAICS 2007 took 27.235552310943604s
Availability | VoID file availability check for NAICS 2007 took 0.0008823871612548828s
Completeness | Calculation of interlinking completeness for NAICS 2007 took 0.43390440940856934s
Reputation | Calculation of the PageRank for NAICS 2007 took 0.020744800567626953s
Interlinking | Calculation of Degree of Connection for NAICS 2007 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for NAICS 2007 took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for NAICS 2007 took 5.650520324707031e-05s
Believability | Calculation of trust value for NAICS 2007 took 9.298324584960938e-06s
INFO | --- Analysis for naics-2007 took 127.41622829437256s
Availability | SPARQL endpoint availability check for NAICS 2012 took 24.907231330871582s
Availability | VoID file availability check for NAICS 2012 took 0.0009257793426513672s
Completeness | Calculation of interlinking completeness for NAICS 2012 took 0.2819056510925293s
Reputation | Calculation of the PageRank for NAICS 2012 took 0.021038293838500977s
Interlinking | Calculation of Degree of Connection for NAICS 2012 took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for NAICS 2012 took 0.0008323192596435547s
Interlinking | Calculation of Clustering coefficient for NAICS 2012 took 6.461143493652344e-05s
Believability | Calculation of trust value for NAICS 2012 took 9.775161743164062e-06s
INFO | --- Analysis for naics-2012 took 123.6413562297821s
Availability | SPARQL endpoint availability check for Usernames  took 9.369850158691406e-05s
Availability | VoID file availability check for Usernames  took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for Usernames  took 0.3066718578338623s
Reputation | Calculation of the PageRank for Usernames  took 0.02114558219909668s
Interlinking | Calculation of Degree of Connection for Usernames  took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Usernames  took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Usernames  took 3.62396240234375e-05s
Believability | Calculation of trust value for Usernames  took 1.4066696166992188e-05s
INFO | --- Analysis for Names took 2.694582939147949s
Availability | SPARQL endpoint availability check for Web NDL Authorities - National Diet Library of Japan took 0.7618141174316406s
Availability | VoID file availability check for Web NDL Authorities - National Diet Library of Japan took 0.0006854534149169922s
Extra | Recovery of all triples for Web NDL Authorities - National Diet Library of Japan took 0.9472277164459229s
Performance | Total latancy measurement for Web NDL Authorities - National Diet Library of Japan took 3.2018561363220215s
Amount of data | Number of triples check for Web NDL Authorities - National Diet Library of Japan took 11.941879272460938s
Interoperability | New terms check for Web NDL Authorities - National Diet Library of Japan took 15.636032342910767s
Versatility | Languages check for Web NDL Authorities - National Diet Library of Japan took 0.8097140789031982s
Interpretability | Number of blank nodes check for Web NDL Authorities - National Diet Library of Japan took 13.716924667358398s
Security | Check HTTPS for Web NDL Authorities - National Diet Library of Japan took 0.8305037021636963s
Interpretability | RDF structures check for Web NDL Authorities - National Diet Library of Japan took 0.37174034118652344s
Versatility | Serialization formats check for Web NDL Authorities - National Diet Library of Japan took 0.7941842079162598s
Availability | RDF dump link check for Web NDL Authorities - National Diet Library of Japan took 0.3569753170013428s
License | MR license check for Web NDL Authorities - National Diet Library of Japan took 0.34775209426879883s
License | HR license check for Web NDL Authorities - National Diet Library of Japan took 91.35778331756592s
Amount of data | Number of property check for Web NDL Authorities - National Diet Library of Japan took 0.3906567096710205s
Understandability | Number of label check for Web NDL Authorities - National Diet Library of Japan took 6.184996843338013s
Understandability | URI regex check for Web NDL Authorities - National Diet Library of Japan took 1.1892833709716797s
Understandability | Vocabs check for Web NDL Authorities - National Diet Library of Japan took 0.8285200595855713s
Verifiability | Authors check for Web NDL Authorities - National Diet Library of Japan took 0.3851203918457031s
Verifiability | Publishers check for Web NDL Authorities - National Diet Library of Japan took 0.3299105167388916s
Performance | Throughput check for Web NDL Authorities - National Diet Library of Japan took 13.413505792617798s
Amount of data | Check the number of entities for Web NDL Authorities - National Diet Library of Japan took 0.00010704994201660156s
Verifiability | Contribs. check for Web NDL Authorities - National Diet Library of Japan took 0.8313097953796387s
Interlinking | sameAs chians check for Web NDL Authorities - National Diet Library of Japan took 0.4603893756866455s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 2.1538021564483643s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.0883216857910156s
Timeliness | dataset update frequency check for Web NDL Authorities - National Diet Library of Japan took 0.35782408714294434s
Currency | Creation date check for Web NDL Authorities - National Diet Library of Japan took 1.0188422203063965s
Currency | Modification date check for Web NDL Authorities - National Diet Library of Japan took 0.7068428993225098s
Rep.Conc. | URIs length for Web NDL Authorities - National Diet Library of Japan took 0.6953272819519043s
Interoperability | New vocabularies check for Web NDL Authorities - National Diet Library of Japan took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Web NDL Authorities - National Diet Library of Japan took 0.3388509750366211s
Accuracy | Check Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.3813135623931885s
Accuracy | Check Inverse Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.3449978828430176s
Accuracy | Check Empty annotation labels for Web NDL Authorities - National Diet Library of Japan took 0.8301947116851807s
Accuracy | Check White space in annotation for Web NDL Authorities - National Diet Library of Japan took 0.0007491111755371094s
Accuracy | Check Datatype consistency for Web NDL Authorities - National Diet Library of Japan took 0.0004820823669433594s
Consistency | Disjoint class check for Web NDL Authorities - National Diet Library of Japan took 0.7789316177368164s
Consistency | Check Misplaced properties for Web NDL Authorities - National Diet Library of Japan took 0.7468135356903076s
Consistency | Misplaced classes for Web NDL Authorities - National Diet Library of Japan took 0.3637852668762207s
Consistency | Check Ontology hijacking for Web NDL Authorities - National Diet Library of Japan took 1.784665584564209s
Consistency | Check Invalid usage of undefined classes for Web NDL Authorities - National Diet Library of Japan took 1.4343481063842773s
Consistency | Check Invalid usage of undefined properties for Web NDL Authorities - National Diet Library of Japan took 1.7758526802062988s
Conciseness | Check Extensional conciseness for Web NDL Authorities - National Diet Library of Japan took 0.0006077289581298828s
Security | Sign check for Web NDL Authorities - National Diet Library of Japan took 0.33736681938171387s
Availability | Check URIs Dereferenciability for Web NDL Authorities - National Diet Library of Japan took 4.552695035934448s
Completeness | Calculation of interlinking completeness for Web NDL Authorities - National Diet Library of Japan took 0.5038957595825195s
Reputation | Calculation of the PageRank for Web NDL Authorities - National Diet Library of Japan took 0.02104020118713379s
Interlinking | Calculation of Degree of Connection for Web NDL Authorities - National Diet Library of Japan took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Web NDL Authorities - National Diet Library of Japan took 0.0008902549743652344s
Interlinking | Calculation of Clustering coefficient for Web NDL Authorities - National Diet Library of Japan took 7.891654968261719e-05s
Interoperability | Check the re-using of existing vocabs for Web NDL Authorities - National Diet Library of Japan took 1.430511474609375e-06s
Believability | Calculation of trust value for Web NDL Authorities - National Diet Library of Japan took 1.049041748046875e-05s
INFO | --- Analysis for national-diet-library-authorities took 239.51883244514465s
Availability | SPARQL endpoint availability check for National Diet Library of Japan subject headings took 0.3616149425506592s
Availability | VoID file availability check for National Diet Library of Japan subject headings took 0.0006978511810302734s
Extra | Recovery of all triples for National Diet Library of Japan subject headings took 1.3900809288024902s
Performance | Total latancy measurement for National Diet Library of Japan subject headings took 2.705038547515869s
Amount of data | Number of triples check for National Diet Library of Japan subject headings took 11.870083570480347s
Interoperability | New terms check for National Diet Library of Japan subject headings took 15.910509586334229s
Versatility | Languages check for National Diet Library of Japan subject headings took 0.804013729095459s
Interpretability | Number of blank nodes check for National Diet Library of Japan subject headings took 13.347263813018799s
Security | Check HTTPS for National Diet Library of Japan subject headings took 0.35033750534057617s
Interpretability | RDF structures check for National Diet Library of Japan subject headings took 0.3196260929107666s
Versatility | Serialization formats check for National Diet Library of Japan subject headings took 0.3607490062713623s
Availability | RDF dump link check for National Diet Library of Japan subject headings took 0.814455509185791s
License | MR license check for National Diet Library of Japan subject headings took 0.8043944835662842s
License | HR license check for National Diet Library of Japan subject headings took 91.75503611564636s
Amount of data | Number of property check for National Diet Library of Japan subject headings took 0.8934094905853271s
Understandability | Number of label check for National Diet Library of Japan subject headings took 4.837295770645142s
Understandability | URI regex check for National Diet Library of Japan subject headings took 0.7075726985931396s
Understandability | Vocabs check for National Diet Library of Japan subject headings took 0.35550594329833984s
Verifiability | Authors check for National Diet Library of Japan subject headings took 0.3490729331970215s
Verifiability | Publishers check for National Diet Library of Japan subject headings took 0.3637204170227051s
Performance | Throughput check for National Diet Library of Japan subject headings took 12.050110101699829s
Amount of data | Check the number of entities for National Diet Library of Japan subject headings took 8.893013000488281e-05s
Verifiability | Contribs. check for National Diet Library of Japan subject headings took 0.7977721691131592s
Interlinking | sameAs chians check for National Diet Library of Japan subject headings took 0.4651930332183838s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.336409568786621s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.2952136993408203s
Timeliness | dataset update frequency check for National Diet Library of Japan subject headings took 0.34650492668151855s
Currency | Creation date check for National Diet Library of Japan subject headings took 1.445631504058838s
Currency | Modification date check for National Diet Library of Japan subject headings took 0.7393090724945068s
Rep.Conc. | URIs length for National Diet Library of Japan subject headings took 0.7086355686187744s
Interoperability | New vocabularies check for National Diet Library of Japan subject headings took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for National Diet Library of Japan subject headings took 0.794921875s
Accuracy | Check Functional Property for National Diet Library of Japan subject headings took 0.39485597610473633s
Accuracy | Check Inverse Functional Property for National Diet Library of Japan subject headings took 0.3728199005126953s
Accuracy | Check Empty annotation labels for National Diet Library of Japan subject headings took 0.3802351951599121s
Accuracy | Check White space in annotation for National Diet Library of Japan subject headings took 0.0007627010345458984s
Accuracy | Check Datatype consistency for National Diet Library of Japan subject headings took 0.0010726451873779297s
Consistency | Disjoint class check for National Diet Library of Japan subject headings took 0.3961305618286133s
Consistency | Check Misplaced properties for National Diet Library of Japan subject headings took 0.7192826271057129s
Consistency | Misplaced classes for National Diet Library of Japan subject headings took 0.3486306667327881s
Consistency | Check Ontology hijacking for National Diet Library of Japan subject headings took 1.8345279693603516s
Consistency | Check Invalid usage of undefined classes for National Diet Library of Japan subject headings took 1.429290533065796s
Consistency | Check Invalid usage of undefined properties for National Diet Library of Japan subject headings took 1.7976353168487549s
Conciseness | Check Extensional conciseness for National Diet Library of Japan subject headings took 0.0006115436553955078s
Security | Sign check for National Diet Library of Japan subject headings took 0.8051784038543701s
Availability | Check URIs Dereferenciability for National Diet Library of Japan subject headings took 5.204684734344482s
Completeness | Calculation of interlinking completeness for National Diet Library of Japan subject headings took 0.4502260684967041s
Reputation | Calculation of the PageRank for National Diet Library of Japan subject headings took 0.021208763122558594s
Interlinking | Calculation of Degree of Connection for National Diet Library of Japan subject headings took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for National Diet Library of Japan subject headings took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for National Diet Library of Japan subject headings took 6.413459777832031e-05s
Interoperability | Check the re-using of existing vocabs for National Diet Library of Japan subject headings took 1.9073486328125e-06s
Believability | Calculation of trust value for National Diet Library of Japan subject headings took 1.3828277587890625e-05s
INFO | --- Analysis for national-diet-library-subject-headings took 231.10655403137207s
Availability | SPARQL endpoint availability check for National Library of Greece Authority Records took 1.063859224319458s
Availability | VoID file availability check for National Library of Greece Authority Records took 0.0006983280181884766s
Completeness | Calculation of interlinking completeness for National Library of Greece Authority Records took 0.2906670570373535s
Reputation | Calculation of the PageRank for National Library of Greece Authority Records took 0.022025585174560547s
Interlinking | Calculation of Degree of Connection for National Library of Greece Authority Records took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for National Library of Greece Authority Records took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for National Library of Greece Authority Records took 5.269050598144531e-05s
Believability | Calculation of trust value for National Library of Greece Authority Records took 1.4543533325195312e-05s
INFO | --- Analysis for national-library-of-greece-authority-records took 5.872097492218018s
Availability | SPARQL endpoint availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 5.125999450683594e-05s
Availability | VoID file availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.3011143207550049s
Reputation | Calculation of the PageRank for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.021923542022705078s
Interlinking | Calculation of Degree of Connection for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 7.081031799316406e-05s
Believability | Calculation of trust value for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.5497207641601562e-05s
INFO | --- Analysis for Naturopathy took 3.430018186569214s
Availability | SPARQL endpoint availability check for COVID-19 Data took 3.4131217002868652s
Availability | VoID file availability check for COVID-19 Data took 0.0006785392761230469s
Completeness | Calculation of interlinking completeness for COVID-19 Data took 0.30553245544433594s
Reputation | Calculation of the PageRank for COVID-19 Data took 0.021050453186035156s
Interlinking | Calculation of Degree of Connection for COVID-19 Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for COVID-19 Data took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for COVID-19 Data took 3.4809112548828125e-05s
Believability | Calculation of trust value for COVID-19 Data took 1.4066696166992188e-05s
INFO | --- Analysis for NCMI-COVID-19 took 7.577249050140381s
Availability | SPARQL endpoint availability check for NCMI-COVID-19 took 2.4047441482543945s
Availability | VoID file availability check for NCMI-COVID-19 took 0.0006315708160400391s
Completeness | Calculation of interlinking completeness for NCMI-COVID-19 took 0.32989048957824707s
Reputation | Calculation of the PageRank for NCMI-COVID-19 took 0.0207822322845459s
Interlinking | Calculation of Degree of Connection for NCMI-COVID-19 took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for NCMI-COVID-19 took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for NCMI-COVID-19 took 1.5735626220703125e-05s
Believability | Calculation of trust value for NCMI-COVID-19 took 9.775161743164062e-06s
INFO | --- Analysis for NCMICOVID-19 took 6.689941644668579s
Availability | SPARQL endpoint availability check for Near took 9.369850158691406e-05s
Availability | VoID file availability check for Near took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Near took 0.39504456520080566s
Reputation | Calculation of the PageRank for Near took 0.020807981491088867s
Interlinking | Calculation of Degree of Connection for Near took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Near took 0.0008404254913330078s
Interlinking | Calculation of Clustering coefficient for Near took 0.000102996826171875s
Believability | Calculation of trust value for Near took 1.4066696166992188e-05s
INFO | --- Analysis for near took 9.418048620223999s
Availability | SPARQL endpoint availability check for NeuroLex Wiki took 0.00011134147644042969s
Availability | VoID file availability check for NeuroLex Wiki took 0.0005636215209960938s
Completeness | Calculation of interlinking completeness for NeuroLex Wiki took 0.27473926544189453s
Reputation | Calculation of the PageRank for NeuroLex Wiki took 0.020729541778564453s
Interlinking | Calculation of Degree of Connection for NeuroLex Wiki took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for NeuroLex Wiki took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for NeuroLex Wiki took 3.457069396972656e-05s
Believability | Calculation of trust value for NeuroLex Wiki took 1.4066696166992188e-05s
INFO | --- Analysis for neurolex-wiki took 2.726590871810913s
Availability | SPARQL endpoint availability check for Shivani Goyal Photography took 4.506111145019531e-05s
Availability | VoID file availability check for Shivani Goyal Photography took 0.0013537406921386719s
Completeness | Calculation of interlinking completeness for Shivani Goyal Photography took 0.29369401931762695s
Reputation | Calculation of the PageRank for Shivani Goyal Photography took 0.020781993865966797s
Interlinking | Calculation of Degree of Connection for Shivani Goyal Photography took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Shivani Goyal Photography took 0.0007765293121337891s
Interlinking | Calculation of Clustering coefficient for Shivani Goyal Photography took 5.125999450683594e-05s
Believability | Calculation of trust value for Shivani Goyal Photography took 1.430511474609375e-05s
INFO | --- Analysis for newborn-photography-maternity-photoshoot-shivani-goyal took 4.305744647979736s
Availability | SPARQL endpoint availability check for News-100 NIF NER Corpus took 6.961822509765625e-05s
Availability | VoID file availability check for News-100 NIF NER Corpus took 0.0007393360137939453s
Completeness | Calculation of interlinking completeness for News-100 NIF NER Corpus took 0.32234644889831543s
Reputation | Calculation of the PageRank for News-100 NIF NER Corpus took 0.02222466468811035s
Interlinking | Calculation of Degree of Connection for News-100 NIF NER Corpus took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for News-100 NIF NER Corpus took 0.0009207725524902344s
Interlinking | Calculation of Clustering coefficient for News-100 NIF NER Corpus took 9.274482727050781e-05s
Believability | Calculation of trust value for News-100 NIF NER Corpus took 1.049041748046875e-05s
INFO | --- Analysis for news-100-nif-ner-corpus took 4.421760082244873s
Availability | SPARQL endpoint availability check for neXtProt took 1.707036018371582s
Availability | VoID file availability check for neXtProt took 0.0003542900085449219s
Completeness | Calculation of interlinking completeness for neXtProt took 0.3148386478424072s
Reputation | Calculation of the PageRank for neXtProt took 0.02146601676940918s
Interlinking | Calculation of Degree of Connection for neXtProt took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for neXtProt took 0.0010471343994140625s
Interlinking | Calculation of Clustering coefficient for neXtProt took 5.14984130859375e-05s
Believability | Calculation of trust value for neXtProt took 1.33514404296875e-05s
INFO | --- Analysis for nextprot took 5.028492450714111s
Availability | SPARQL endpoint availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 5.53131103515625e-05s
Availability | VoID file availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0008251667022705078s
Completeness | Calculation of interlinking completeness for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.28000926971435547s
Reputation | Calculation of the PageRank for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.020807266235351562s
Interlinking | Calculation of Degree of Connection for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.00079345703125s
Interlinking | Calculation of Clustering coefficient for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.00011134147644042969s
Believability | Calculation of trust value for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.5020370483398438e-05s
INFO | --- Analysis for nextweb-gnoss took 8.64831280708313s
Availability | SPARQL endpoint availability check for NHS Jargon RDF took 9.107589721679688e-05s
Availability | VoID file availability check for NHS Jargon RDF took 0.0007030963897705078s
Completeness | Calculation of interlinking completeness for NHS Jargon RDF took 0.30463671684265137s
Reputation | Calculation of the PageRank for NHS Jargon RDF took 0.023329496383666992s
Interlinking | Calculation of Degree of Connection for NHS Jargon RDF took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for NHS Jargon RDF took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for NHS Jargon RDF took 8.606910705566406e-05s
Believability | Calculation of trust value for NHS Jargon RDF took 9.5367431640625e-06s
INFO | --- Analysis for nhs-jargon took 3.1846249103546143s
Availability | SPARQL endpoint availability check for NIT Patna took 9.226799011230469e-05s
Availability | VoID file availability check for NIT Patna took 0.0006406307220458984s
Completeness | Calculation of interlinking completeness for NIT Patna took 0.30284619331359863s
Reputation | Calculation of the PageRank for NIT Patna took 0.02179121971130371s
Interlinking | Calculation of Degree of Connection for NIT Patna took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for NIT Patna took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for NIT Patna took 6.937980651855469e-05s
Believability | Calculation of trust value for NIT Patna took 1.239776611328125e-05s
INFO | --- Analysis for NITP took 3.7525734901428223s
Availability | SPARQL endpoint availability check for National Library of Russia BibCore Dataset took 0.00011849403381347656s
Availability | VoID file availability check for National Library of Russia BibCore Dataset took 0.0005314350128173828s
Completeness | Calculation of interlinking completeness for National Library of Russia BibCore Dataset took 0.2726733684539795s
Reputation | Calculation of the PageRank for National Library of Russia BibCore Dataset took 0.02064681053161621s
Interlinking | Calculation of Degree of Connection for National Library of Russia BibCore Dataset took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for National Library of Russia BibCore Dataset took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for National Library of Russia BibCore Dataset took 3.1948089599609375e-05s
Believability | Calculation of trust value for National Library of Russia BibCore Dataset took 1.0251998901367188e-05s
INFO | --- Analysis for nlr-dataset-mod took 4.079413414001465s
Availability | SPARQL endpoint availability check for Neulateinische Wortliste in LiLa took 0.6030716896057129s
Availability | VoID file availability check for Neulateinische Wortliste in LiLa took 0.00039315223693847656s
Completeness | Calculation of interlinking completeness for Neulateinische Wortliste in LiLa took 0.27605724334716797s
Reputation | Calculation of the PageRank for Neulateinische Wortliste in LiLa took 0.02067708969116211s
Interlinking | Calculation of Degree of Connection for Neulateinische Wortliste in LiLa took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Neulateinische Wortliste in LiLa took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Neulateinische Wortliste in LiLa took 4.124641418457031e-05s
Believability | Calculation of trust value for Neulateinische Wortliste in LiLa took 1.3828277587890625e-05s
INFO | --- Analysis for NLW took 4.574493408203125s
Availability | SPARQL endpoint availability check for Nobel Prizes took 3.687007427215576s
Availability | VoID file availability check for Nobel Prizes took 0.0007429122924804688s
Completeness | Calculation of interlinking completeness for Nobel Prizes took 0.28578758239746094s
Reputation | Calculation of the PageRank for Nobel Prizes took 0.02086806297302246s
Interlinking | Calculation of Degree of Connection for Nobel Prizes took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Nobel Prizes took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Nobel Prizes took 9.703636169433594e-05s
Believability | Calculation of trust value for Nobel Prizes took 1.4781951904296875e-05s
INFO | --- Analysis for nobelprizes took 9.760206460952759s
Availability | SPARQL endpoint availability check for NoiPA took 0.29260921478271484s
Availability | VoID file availability check for NoiPA took 0.0005214214324951172s
Extra | Recovery of all triples for NoiPA took 1.1417264938354492s
Performance | Total latancy measurement for NoiPA took 0.5171287059783936s
Amount of data | Number of triples check for NoiPA took 5.803057909011841s
Interoperability | New terms check for NoiPA took 2.891089677810669s
Versatility | Languages check for NoiPA took 60.15616798400879s
Interpretability | Number of blank nodes check for NoiPA took 0.17252302169799805s
Interpretability | RDF structures check for NoiPA took 0.535834550857544s
Versatility | Serialization formats check for NoiPA took 0.2770562171936035s
Availability | RDF dump link check for NoiPA took 0.26242971420288086s
License | MR license check for NoiPA took 0.6160526275634766s
License | HR license check for NoiPA took 60.325679063797s
Amount of data | Number of property check for NoiPA took 0.18003034591674805s
Understandability | Number of label check for NoiPA took 1.4197354316711426s
Understandability | URI regex check for NoiPA took 0.41362619400024414s
Understandability | Vocabs check for NoiPA took 0.21612763404846191s
Verifiability | Authors check for NoiPA took 0.33651232719421387s
Verifiability | Publishers check for NoiPA took 0.34586262702941895s
Performance | Throughput check for NoiPA took 10.744682788848877s
Amount of data | Check the number of entities for NoiPA took 3.3855438232421875e-05s
Verifiability | Contribs. check for NoiPA took 0.17612838745117188s
Interlinking | sameAs chians check for NoiPA took 0.11275887489318848s
Interlinking | skos check for NoiPA took 0.6793441772460938s
Interlinking | skos check for NoiPA took 0.13153862953186035s
Timeliness | dataset update frequency check for NoiPA took 0.35161447525024414s
Currency | Creation date check for NoiPA took 0.5288171768188477s
Currency | Modification date check for NoiPA took 0.2243177890777588s
Rep.Conc. | URIs length for NoiPA took 18.03523564338684s
Interoperability | New vocabularies check for NoiPA took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for NoiPA took 0.16892600059509277s
Accuracy | Check Functional Property for NoiPA took 0.15322542190551758s
Accuracy | Check Inverse Functional Property for NoiPA took 0.1882491111755371s
Accuracy | Check Empty annotation labels for NoiPA took 0.3672454357147217s
Accuracy | Check White space in annotation for NoiPA took 0.026057004928588867s
Accuracy | Check Datatype consistency for NoiPA took 0.02906513214111328s
Consistency | Disjoint class check for NoiPA took 0.23081707954406738s
Consistency | Check Misplaced properties for NoiPA took 15.77814793586731s
Consistency | Misplaced classes for NoiPA took 0.2214217185974121s
Consistency | Check Ontology hijacking for NoiPA took 1.788078784942627s
Consistency | Check Invalid usage of undefined classes for NoiPA took 1.4216523170471191s
Consistency | Check Invalid usage of undefined properties for NoiPA took 17.53243851661682s
Conciseness | Check Extensional conciseness for NoiPA took 0.03629565238952637s
Conciseness | Check Intensional conciseness for NoiPA took 0.16100764274597168s
Security | Sign check for NoiPA took 0.12121343612670898s
Availability | Check URIs Dereferenciability for NoiPA took 22.55868172645569s
Completeness | Calculation of interlinking completeness for NoiPA took 0.41594767570495605s
Reputation | Calculation of the PageRank for NoiPA took 0.021189451217651367s
Interlinking | Calculation of Degree of Connection for NoiPA took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NoiPA took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for NoiPA took 4.220008850097656e-05s
Interoperability | Check the re-using of existing vocabs for NoiPA took 1.430511474609375e-06s
Believability | Calculation of trust value for NoiPA took 1.1682510375976562e-05s
INFO | --- Analysis for NoiPA took 533.3121871948242s
Availability | SPARQL endpoint availability check for Nomenclature for Museum Cataloging took 0.8972537517547607s
Availability | VoID file availability check for Nomenclature for Museum Cataloging took 0.00074005126953125s
Completeness | Calculation of interlinking completeness for Nomenclature for Museum Cataloging took 0.3399031162261963s
Reputation | Calculation of the PageRank for Nomenclature for Museum Cataloging took 0.021065950393676758s
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.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Nomenclature for Museum Cataloging took 0.000102996826171875s
Believability | Calculation of trust value for Nomenclature for Museum Cataloging took 1.4543533325195312e-05s
INFO | --- Analysis for nom took 8.618439197540283s
Availability | SPARQL endpoint availability check for Nomenclator Asturias took 25.686055183410645s
Availability | VoID file availability check for Nomenclator Asturias took 0.0009112358093261719s
Completeness | Calculation of interlinking completeness for Nomenclator Asturias took 0.291642427444458s
Reputation | Calculation of the PageRank for Nomenclator Asturias took 0.021243572235107422s
Interlinking | Calculation of Degree of Connection for Nomenclator Asturias took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Nomenclator Asturias took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for Nomenclator Asturias took 8.416175842285156e-05s
Believability | Calculation of trust value for Nomenclator Asturias took 1.049041748046875e-05s
INFO | --- Analysis for nomenclator-asturias took 138.27081274986267s
Availability | SPARQL endpoint availability check for Nomisma.org  took 0.4932382106781006s
Availability | VoID file availability check for Nomisma.org  took 0.0007123947143554688s
Extra | Recovery of all triples for Nomisma.org  took 300.06981778144836s
Performance | Total latancy measurement for Nomisma.org  took 2.0127809047698975s
Amount of data | Number of triples check for Nomisma.org  took 40.07815909385681s
Interoperability | New terms check for Nomisma.org  took 7.7499566078186035s
Versatility | Languages check for Nomisma.org  took 170.92961621284485s
Interpretability | Number of blank nodes check for Nomisma.org  took 50.74061989784241s
Security | Check HTTPS for Nomisma.org  took 0.7951555252075195s
Interpretability | RDF structures check for Nomisma.org  took 0.4185807704925537s
Versatility | Serialization formats check for Nomisma.org  took 0.38647031784057617s
Availability | RDF dump link check for Nomisma.org  took 1128.4799513816833s
License | MR license check for Nomisma.org  took 0.8921144008636475s
License | HR license check for Nomisma.org  took 65.0495994091034s
Amount of data | Number of property check for Nomisma.org  took 0.42788147926330566s
Understandability | Number of label check for Nomisma.org  took 6.898674964904785s
Understandability | URI regex check for Nomisma.org  took 0.7349929809570312s
Understandability | Vocabs check for Nomisma.org  took 0.3580968379974365s
Verifiability | Authors check for Nomisma.org  took 0.4077324867248535s
Verifiability | Publishers check for Nomisma.org  took 0.39690113067626953s
Performance | Throughput check for Nomisma.org  took 11.71579647064209s
Amount of data | Check the number of entities for Nomisma.org  took 0.0006594657897949219s
Verifiability | Contribs. check for Nomisma.org  took 0.4082503318786621s
Interlinking | sameAs chians check for Nomisma.org  took 0.3886423110961914s
Interlinking | skos check for Nomisma.org  took 1.2217347621917725s
Interlinking | skos check for Nomisma.org  took 1.2282018661499023s
Timeliness | dataset update frequency check for Nomisma.org  took 0.3901336193084717s
Currency | Creation date check for Nomisma.org  took 0.8249280452728271s
Currency | Modification date check for Nomisma.org  took 0.786182165145874s
Rep.Conc. | URIs length for Nomisma.org  took 468.1292688846588s
Interoperability | New vocabularies check for Nomisma.org  took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Nomisma.org  took 0.3965611457824707s
Accuracy | Check Functional Property for Nomisma.org  took 0.42412471771240234s
Accuracy | Check Inverse Functional Property for Nomisma.org  took 0.3775975704193115s
Accuracy | Check Empty annotation labels for Nomisma.org  took 467.743106842041s
Accuracy | Check White space in annotation for Nomisma.org  took 2.7405617237091064s
Consistency | Disjoint class check for Nomisma.org  took 0.4104945659637451s
Consistency | Check Misplaced properties for Nomisma.org  took 27.939957857131958s
Consistency | Check Ontology hijacking for Nomisma.org  took 407.8403708934784s
Consistency | Check Invalid usage of undefined properties for Nomisma.org  took 28.254154682159424s
Conciseness | Check Extensional conciseness for Nomisma.org  took 0.0001723766326904297s
Conciseness | Check Intensional conciseness for Nomisma.org  took 0.4511542320251465s
Security | Sign check for Nomisma.org  took 0.3826632499694824s
Availability | Check URIs Dereferenciability for Nomisma.org  took 2096.9137432575226s
Completeness | Calculation of interlinking completeness for Nomisma.org  took 0.7379777431488037s
Reputation | Calculation of the PageRank for Nomisma.org  took 0.021677494049072266s
Interlinking | Calculation of Degree of Connection for Nomisma.org  took 6.580352783203125e-05s
Interlinking | Calculation of Centrality for Nomisma.org  took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for Nomisma.org  took 5.698204040527344e-05s
Interoperability | Check the re-using of existing vocabs for Nomisma.org  took 1.5735626220703125e-05s
Believability | Calculation of trust value for Nomisma.org  took 1.52587890625e-05s
INFO | --- Analysis for nomisma_org took 9775.750919103622s
Availability | SPARQL endpoint availability check for Curriculum Vitae took 0.3436317443847656s
Availability | VoID file availability check for Curriculum Vitae took 0.0005116462707519531s
Extra | Recovery of all triples for Curriculum Vitae took 0.7426519393920898s
Performance | Total latancy measurement for Curriculum Vitae took 1.05665922164917s
Amount of data | Number of triples check for Curriculum Vitae took 0.14837193489074707s
Interoperability | New terms check for Curriculum Vitae took 1.6892943382263184s
Versatility | Languages check for Curriculum Vitae took 0.2570152282714844s
Interpretability | Number of blank nodes check for Curriculum Vitae took 0.13474750518798828s
Interpretability | RDF structures check for Curriculum Vitae took 0.1311051845550537s
Versatility | Serialization formats check for Curriculum Vitae took 0.12551522254943848s
Availability | RDF dump link check for Curriculum Vitae took 0.1780853271484375s
License | MR license check for Curriculum Vitae took 0.12428021430969238s
License | HR license check for Curriculum Vitae took 0.16710758209228516s
Amount of data | Number of property check for Curriculum Vitae took 0.19154071807861328s
Understandability | Number of label check for Curriculum Vitae took 0.2609992027282715s
Understandability | URI regex check for Curriculum Vitae took 0.40580201148986816s
Understandability | Vocabs check for Curriculum Vitae took 0.27964210510253906s
Verifiability | Authors check for Curriculum Vitae took 0.17966365814208984s
Verifiability | Publishers check for Curriculum Vitae took 0.24998760223388672s
Performance | Throughput check for Curriculum Vitae took 11.023265838623047s
Amount of data | Check the number of entities for Curriculum Vitae took 7.43865966796875e-05s
Verifiability | Contribs. check for Curriculum Vitae took 0.14613008499145508s
Interlinking | sameAs chians check for Curriculum Vitae took 0.14469695091247559s
Interlinking | skos check for Curriculum Vitae took 0.163590669631958s
Interlinking | skos check for Curriculum Vitae took 0.15739083290100098s
Timeliness | dataset update frequency check for Curriculum Vitae took 0.14749503135681152s
Currency | Creation date check for Curriculum Vitae took 0.28218603134155273s
Currency | Modification date check for Curriculum Vitae took 0.38225865364074707s
Rep.Conc. | URIs length for Curriculum Vitae took 0.3234434127807617s
Interoperability | New vocabularies check for Curriculum Vitae took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Curriculum Vitae took 0.12102746963500977s
Accuracy | Check Functional Property for Curriculum Vitae took 0.1419076919555664s
Accuracy | Check Inverse Functional Property for Curriculum Vitae took 0.15427494049072266s
Accuracy | Check Empty annotation labels for Curriculum Vitae took 0.15163397789001465s
Accuracy | Check White space in annotation for Curriculum Vitae took 0.00011658668518066406s
Accuracy | Check Datatype consistency for Curriculum Vitae took 0.0038042068481445312s
Consistency | Disjoint class check for Curriculum Vitae took 0.24848175048828125s
Consistency | Check Misplaced properties for Curriculum Vitae took 0.2870807647705078s
Consistency | Check Ontology hijacking for Curriculum Vitae took 1.6227929592132568s
Consistency | Check Invalid usage of undefined classes for Curriculum Vitae took 1.438164234161377s
Consistency | Check Invalid usage of undefined properties for Curriculum Vitae took 1.5923781394958496s
Conciseness | Check Extensional conciseness for Curriculum Vitae took 0.0019001960754394531s
Security | Sign check for Curriculum Vitae took 0.12245750427246094s
Availability | Check URIs Dereferenciability for Curriculum Vitae took 19.77950954437256s
Completeness | Calculation of interlinking completeness for Curriculum Vitae took 0.28130316734313965s
Reputation | Calculation of the PageRank for Curriculum Vitae took 0.02161407470703125s
Interlinking | Calculation of Degree of Connection for Curriculum Vitae took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Curriculum Vitae took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Curriculum Vitae took 4.100799560546875e-05s
Interoperability | Check the re-using of existing vocabs for Curriculum Vitae took 1.9073486328125e-06s
Believability | Calculation of trust value for Curriculum Vitae took 1.430511474609375e-05s
INFO | --- Analysis for Nordine_Bittich took 59.656190633773804s
Availability | SPARQL endpoint availability check for NorPark took 0.06807303428649902s
Availability | VoID file availability check for NorPark took 0.0005705356597900391s
Completeness | Calculation of interlinking completeness for NorPark took 0.2871212959289551s
Reputation | Calculation of the PageRank for NorPark took 0.02252817153930664s
Interlinking | Calculation of Degree of Connection for NorPark took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for NorPark took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for NorPark took 4.673004150390625e-05s
Believability | Calculation of trust value for NorPark took 1.4066696166992188e-05s
INFO | --- Analysis for norpark took 2.990330219268799s
Availability | SPARQL endpoint availability check for Parking Dataset took 0.017903566360473633s
Availability | VoID file availability check for Parking Dataset took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for Parking Dataset took 0.30014848709106445s
Reputation | Calculation of the PageRank for Parking Dataset took 0.02039957046508789s
Interlinking | Calculation of Degree of Connection for Parking Dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Parking Dataset took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Parking Dataset took 4.8160552978515625e-05s
Believability | Calculation of trust value for Parking Dataset took 1.2636184692382812e-05s
INFO | --- Analysis for norpark2 took 2.7575504779815674s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset took 5.531497001647949s
Availability | VoID file availability check for Norway fishery stocks dataset took 0.0005409717559814453s
Extra | Recovery of all triples for Norway fishery stocks dataset took 117.33204889297485s
Performance | Total latancy measurement for Norway fishery stocks dataset took 0.9653117656707764s
Amount of data | Number of triples check for Norway fishery stocks dataset took 9.069307804107666s
Interoperability | New terms check for Norway fishery stocks dataset took 14.433354377746582s
Versatility | Languages check for Norway fishery stocks dataset took 300.2036507129669s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset took 2.1306395530700684s
Interpretability | RDF structures check for Norway fishery stocks dataset took 0.2994060516357422s
Versatility | Serialization formats check for Norway fishery stocks dataset took 8.345282316207886s
Availability | RDF dump link check for Norway fishery stocks dataset took 0.4380066394805908s
License | MR license check for Norway fishery stocks dataset took 0.7975149154663086s
License | HR license check for Norway fishery stocks dataset took 300.2291593551636s
Amount of data | Number of property check for Norway fishery stocks dataset took 0.20944976806640625s
Understandability | Number of label check for Norway fishery stocks dataset took 2.394195079803467s
Understandability | URI regex check for Norway fishery stocks dataset took 0.9666135311126709s
Understandability | Vocabs check for Norway fishery stocks dataset took 0.6242642402648926s
Verifiability | Authors check for Norway fishery stocks dataset took 0.20465421676635742s
Verifiability | Publishers check for Norway fishery stocks dataset took 0.2670919895172119s
Performance | Throughput check for Norway fishery stocks dataset took 10.82564902305603s
Amount of data | Check the number of entities for Norway fishery stocks dataset took 0.00017881393432617188s
Verifiability | Contribs. check for Norway fishery stocks dataset took 0.18190360069274902s
Interlinking | sameAs chians check for Norway fishery stocks dataset took 0.20124292373657227s
Interlinking | skos check for Norway fishery stocks dataset took 0.5482196807861328s
Interlinking | skos check for Norway fishery stocks dataset took 0.4146697521209717s
Timeliness | dataset update frequency check for Norway fishery stocks dataset took 4.529980421066284s
Currency | Creation date check for Norway fishery stocks dataset took 0.48298192024230957s
Currency | Modification date check for Norway fishery stocks dataset took 0.24145054817199707s
Rep.Conc. | URIs length for Norway fishery stocks dataset took 152.07019686698914s
Interoperability | New vocabularies check for Norway fishery stocks dataset took 1.1682510375976562e-05s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset took 0.18417739868164062s
Accuracy | Check Functional Property for Norway fishery stocks dataset took 0.46739721298217773s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset took 0.43450093269348145s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset took 37.466344594955444s
Accuracy | Check White space in annotation for Norway fishery stocks dataset took 2.6685075759887695s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset took 2.828310966491699s
Consistency | Disjoint class check for Norway fishery stocks dataset took 0.1945812702178955s
Consistency | Check Misplaced properties for Norway fishery stocks dataset took 87.49271988868713s
Consistency | Misplaced classes for Norway fishery stocks dataset took 8.518865585327148s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset took 34.9692485332489s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset took 1.600679874420166s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset took 87.37059020996094s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset took 2.7997219562530518s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset took 0.5591528415679932s
Security | Sign check for Norway fishery stocks dataset took 1.4637212753295898s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset took 9.873260259628296s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset took 0.4462118148803711s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset took 0.022168874740600586s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset took 5.412101745605469e-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.430511474609375e-05s
INFO | --- Analysis for Norway_Fishery_ took 2289.1623542308807s
Availability | SPARQL endpoint availability check for Norwegian geo-divisions took 0.5263135433197021s
Availability | VoID file availability check for Norwegian geo-divisions took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for Norwegian geo-divisions took 0.2982137203216553s
Reputation | Calculation of the PageRank for Norwegian geo-divisions took 0.020825624465942383s
Interlinking | Calculation of Degree of Connection for Norwegian geo-divisions took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Norwegian geo-divisions took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Norwegian geo-divisions took 5.698204040527344e-05s
Believability | Calculation of trust value for Norwegian geo-divisions took 1.52587890625e-05s
INFO | --- Analysis for norwegian-geo-divisions took 4.6444618701934814s
Availability | SPARQL endpoint availability check for NITP took 8.96453857421875e-05s
Availability | VoID file availability check for NITP took 0.0007255077362060547s
Completeness | Calculation of interlinking completeness for NITP took 0.39255213737487793s
Reputation | Calculation of the PageRank for NITP took 0.02100849151611328s
Interlinking | Calculation of Degree of Connection for NITP took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for NITP took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for NITP took 0.00010824203491210938s
Believability | Calculation of trust value for NITP took 1.0013580322265625e-05s
INFO | --- Analysis for notIdentifier took 3.4344871044158936s
Availability | SPARQL endpoint availability check for Nottingham Trent University Resource Lists took 4.410743713378906e-05s
Availability | VoID file availability check for Nottingham Trent University Resource Lists took 0.0006580352783203125s
Completeness | Calculation of interlinking completeness for Nottingham Trent University Resource Lists took 0.3006911277770996s
Reputation | Calculation of the PageRank for Nottingham Trent University Resource Lists took 0.02157306671142578s
Interlinking | Calculation of Degree of Connection for Nottingham Trent University Resource Lists took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Nottingham Trent University Resource Lists took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for Nottingham Trent University Resource Lists took 4.00543212890625e-05s
Believability | Calculation of trust value for Nottingham Trent University Resource Lists took 1.5497207641601562e-05s
INFO | --- Analysis for nottingham-trent-university-resource-lists took 3.1250641345977783s
Availability | SPARQL endpoint availability check for NPM took 4.4345855712890625e-05s
Availability | VoID file availability check for NPM took 0.0006356239318847656s
Completeness | Calculation of interlinking completeness for NPM took 0.3266899585723877s
Reputation | Calculation of the PageRank for NPM took 0.020678281784057617s
Interlinking | Calculation of Degree of Connection for NPM took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for NPM took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for NPM took 4.363059997558594e-05s
Believability | Calculation of trust value for NPM took 1.430511474609375e-05s
INFO | --- Analysis for npm took 3.8152568340301514s
Availability | SPARQL endpoint availability check for NTNU special collections took 0.039023637771606445s
Availability | VoID file availability check for NTNU special collections took 0.0006909370422363281s
Completeness | Calculation of interlinking completeness for NTNU special collections took 0.31888437271118164s
Reputation | Calculation of the PageRank for NTNU special collections took 0.02053380012512207s
Interlinking | Calculation of Degree of Connection for NTNU special collections took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for NTNU special collections took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for NTNU special collections took 6.198883056640625e-05s
Believability | Calculation of trust value for NTNU special collections took 1.4781951904296875e-05s
INFO | --- Analysis for ntnusc took 5.478181600570679s
Availability | SPARQL endpoint availability check for links took 0.00013303756713867188s
Availability | VoID file availability check for links took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for links took 0.3276090621948242s
Reputation | Calculation of the PageRank for links took 0.023457765579223633s
Interlinking | Calculation of Degree of Connection for links took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for links took 0.0008006095886230469s
Interlinking | Calculation of Clustering coefficient for links took 1.4781951904296875e-05s
Believability | Calculation of trust value for links took 1.430511474609375e-05s
INFO | --- Analysis for nugmyanmar took 2.806838274002075s
Availability | SPARQL endpoint availability check for NUTS (GeoVocab) took 0.00011110305786132812s
Availability | VoID file availability check for NUTS (GeoVocab) took 0.0004916191101074219s
Completeness | Calculation of interlinking completeness for NUTS (GeoVocab) took 0.301469087600708s
Reputation | Calculation of the PageRank for NUTS (GeoVocab) took 0.02100205421447754s
Interlinking | Calculation of Degree of Connection for NUTS (GeoVocab) took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for NUTS (GeoVocab) took 0.0009953975677490234s
Interlinking | Calculation of Clustering coefficient for NUTS (GeoVocab) took 0.00012683868408203125s
Believability | Calculation of trust value for NUTS (GeoVocab) took 1.049041748046875e-05s
INFO | --- Analysis for nuts-geovocab took 2.626131534576416s
Availability | SPARQL endpoint availability check for Norsk inndeling av vitenskapsdisipliner took 0.4093959331512451s
Availability | VoID file availability check for Norsk inndeling av vitenskapsdisipliner took 0.0006651878356933594s
Completeness | Calculation of interlinking completeness for Norsk inndeling av vitenskapsdisipliner took 0.3183741569519043s
Reputation | Calculation of the PageRank for Norsk inndeling av vitenskapsdisipliner took 0.020528078079223633s
Interlinking | Calculation of Degree of Connection for Norsk inndeling av vitenskapsdisipliner took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Norsk inndeling av vitenskapsdisipliner took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Norsk inndeling av vitenskapsdisipliner took 7.009506225585938e-05s
Believability | Calculation of trust value for Norsk inndeling av vitenskapsdisipliner took 1.3828277587890625e-05s
INFO | --- Analysis for nvd took 4.446794271469116s
Availability | SPARQL endpoint availability check for NERC Vocabulary Server 2.0 took 0.8149418830871582s
Availability | VoID file availability check for NERC Vocabulary Server 2.0 took 0.0003139972686767578s
Completeness | Calculation of interlinking completeness for NERC Vocabulary Server 2.0 took 0.3420374393463135s
Reputation | Calculation of the PageRank for NERC Vocabulary Server 2.0 took 0.020442485809326172s
Interlinking | Calculation of Degree of Connection for NERC Vocabulary Server 2.0 took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for NERC Vocabulary Server 2.0 took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for NERC Vocabulary Server 2.0 took 8.106231689453125e-05s
Believability | Calculation of trust value for NERC Vocabulary Server 2.0 took 1.33514404296875e-05s
INFO | --- Analysis for nvs took 8.948143720626831s
Availability | SPARQL endpoint availability check for New York Times - Linked Open Data took 8.511543273925781e-05s
Availability | VoID file availability check for New York Times - Linked Open Data took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for New York Times - Linked Open Data took 0.28365612030029297s
Reputation | Calculation of the PageRank for New York Times - Linked Open Data took 0.022328853607177734s
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.0008065700531005859s
Interlinking | Calculation of Clustering coefficient for New York Times - Linked Open Data took 0.00019741058349609375s
Believability | Calculation of trust value for New York Times - Linked Open Data took 1.33514404296875e-05s
INFO | --- Analysis for nytimes-linked-open-data took 2.7670540809631348s
Availability | SPARQL endpoint availability check for Italian Chamber of Deputies - official dataset took 0.5242495536804199s
Availability | VoID file availability check for Italian Chamber of Deputies - official dataset took 0.0007786750793457031s
Extra | Recovery of all triples for Italian Chamber of Deputies - official dataset took 1.5350561141967773s
Performance | Total latancy measurement for Italian Chamber of Deputies - official dataset took 1.8249843120574951s
Amount of data | Number of triples check for Italian Chamber of Deputies - official dataset took 2.5898077487945557s
Interoperability | New terms check for Italian Chamber of Deputies - official dataset took 3.9172120094299316s
Versatility | Languages check for Italian Chamber of Deputies - official dataset took 58.204155683517456s
Interpretability | Number of blank nodes check for Italian Chamber of Deputies - official dataset took 2.4221513271331787s
Security | Check HTTPS for Italian Chamber of Deputies - official dataset took 0.24091506004333496s
Interpretability | RDF structures check for Italian Chamber of Deputies - official dataset took 0.3451731204986572s
Versatility | Serialization formats check for Italian Chamber of Deputies - official dataset took 0.5005178451538086s
Availability | RDF dump link check for Italian Chamber of Deputies - official dataset took 0.41110777854919434s
License | MR license check for Italian Chamber of Deputies - official dataset took 0.35257840156555176s
License | HR license check for Italian Chamber of Deputies - official dataset took 58.233612060546875s
Amount of data | Number of property check for Italian Chamber of Deputies - official dataset took 0.3754384517669678s
Understandability | Number of label check for Italian Chamber of Deputies - official dataset took 0.6120443344116211s
Understandability | URI regex check for Italian Chamber of Deputies - official dataset took 0.7330441474914551s
Understandability | Vocabs check for Italian Chamber of Deputies - official dataset took 0.41436243057250977s
Verifiability | Authors check for Italian Chamber of Deputies - official dataset took 0.3576962947845459s
Verifiability | Publishers check for Italian Chamber of Deputies - official dataset took 0.4019172191619873s
Performance | Throughput check for Italian Chamber of Deputies - official dataset took 11.188058376312256s
Amount of data | Check the number of entities for Italian Chamber of Deputies - official dataset took 0.00011110305786132812s
Verifiability | Contribs. check for Italian Chamber of Deputies - official dataset took 0.4159090518951416s
Interlinking | sameAs chians check for Italian Chamber of Deputies - official dataset took 0.36778926849365234s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.36177992820739746s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.38127779960632324s
Timeliness | dataset update frequency check for Italian Chamber of Deputies - official dataset took 0.3989675045013428s
Currency | Creation date check for Italian Chamber of Deputies - official dataset took 0.7443923950195312s
Currency | Modification date check for Italian Chamber of Deputies - official dataset took 0.37210512161254883s
Rep.Conc. | URIs length for Italian Chamber of Deputies - official dataset took 16.69282579421997s
Interoperability | New vocabularies check for Italian Chamber of Deputies - official dataset took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for Italian Chamber of Deputies - official dataset took 0.3678274154663086s
Accuracy | Check Functional Property for Italian Chamber of Deputies - official dataset took 0.36762142181396484s
Accuracy | Check Inverse Functional Property for Italian Chamber of Deputies - official dataset took 0.35344672203063965s
Accuracy | Check Empty annotation labels for Italian Chamber of Deputies - official dataset took 0.7243573665618896s
Accuracy | Check White space in annotation for Italian Chamber of Deputies - official dataset took 0.023662805557250977s
Accuracy | Check Datatype consistency for Italian Chamber of Deputies - official dataset took 0.028889894485473633s
Consistency | Disjoint class check for Italian Chamber of Deputies - official dataset took 0.36452412605285645s
Consistency | Check Misplaced properties for Italian Chamber of Deputies - official dataset took 12.712756633758545s
Consistency | Misplaced classes for Italian Chamber of Deputies - official dataset took 0.45991992950439453s
Consistency | Check Ontology hijacking for Italian Chamber of Deputies - official dataset took 2.3569493293762207s
Consistency | Check Invalid usage of undefined classes for Italian Chamber of Deputies - official dataset took 1.4237868785858154s
Consistency | Check Invalid usage of undefined properties for Italian Chamber of Deputies - official dataset took 13.702060461044312s
Conciseness | Check Extensional conciseness for Italian Chamber of Deputies - official dataset took 0.032537221908569336s
Conciseness | Check Intensional conciseness for Italian Chamber of Deputies - official dataset took 0.4299290180206299s
Security | Sign check for Italian Chamber of Deputies - official dataset took 0.3551492691040039s
Availability | Check URIs Dereferenciability for Italian Chamber of Deputies - official dataset took 9.783604145050049s
Completeness | Calculation of interlinking completeness for Italian Chamber of Deputies - official dataset took 0.48920178413391113s
Reputation | Calculation of the PageRank for Italian Chamber of Deputies - official dataset took 0.02125716209411621s
Interlinking | Calculation of Degree of Connection for Italian Chamber of Deputies - official dataset took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Italian Chamber of Deputies - official dataset took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Italian Chamber of Deputies - official dataset took 0.00010752677917480469s
Interoperability | Check the re-using of existing vocabs for Italian Chamber of Deputies - official dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for Italian Chamber of Deputies - official dataset took 1.4543533325195312e-05s
INFO | --- Analysis for ocd took 383.24225425720215s
Availability | SPARQL endpoint availability check for oceandrilling-borehole took 4.291534423828125e-05s
Availability | VoID file availability check for oceandrilling-borehole took 0.0005965232849121094s
Completeness | Calculation of interlinking completeness for oceandrilling-borehole took 0.28830599784851074s
Reputation | Calculation of the PageRank for oceandrilling-borehole took 0.020092487335205078s
Interlinking | Calculation of Degree of Connection for oceandrilling-borehole took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for oceandrilling-borehole took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for oceandrilling-borehole took 4.220008850097656e-05s
Believability | Calculation of trust value for oceandrilling-borehole took 1.6927719116210938e-05s
INFO | --- Analysis for oceandrilling-borehole took 3.5108895301818848s
Availability | SPARQL endpoint availability check for Ocean Drilling - Codices took 3.2065906524658203s
Availability | VoID file availability check for Ocean Drilling - Codices took 0.0007417201995849609s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Codices took 0.2886378765106201s
Reputation | Calculation of the PageRank for Ocean Drilling - Codices took 0.020735979080200195s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Codices took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Codices took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Codices took 9.226799011230469e-05s
Believability | Calculation of trust value for Ocean Drilling - Codices took 1.3589859008789062e-05s
INFO | --- Analysis for oceandrilling-codices took 9.54816746711731s
Availability | SPARQL endpoint availability check for Ocean Drilling - dbSEABED took 2.8842685222625732s
Availability | VoID file availability check for Ocean Drilling - dbSEABED took 0.0005414485931396484s
Completeness | Calculation of interlinking completeness for Ocean Drilling - dbSEABED took 0.27600979804992676s
Reputation | Calculation of the PageRank for Ocean Drilling - dbSEABED took 0.02122664451599121s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - dbSEABED took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - dbSEABED took 0.0008616447448730469s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - dbSEABED took 3.981590270996094e-05s
Believability | Calculation of trust value for Ocean Drilling - dbSEABED took 1.4543533325195312e-05s
INFO | --- Analysis for oceandrilling-dbseabed took 7.372292757034302s
Availability | SPARQL endpoint availability check for Ocean Drilling - Forams took 3.0197577476501465s
Availability | VoID file availability check for Ocean Drilling - Forams took 0.0008816719055175781s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Forams took 0.3226499557495117s
Reputation | Calculation of the PageRank for Ocean Drilling - Forams took 0.021900653839111328s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Forams took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Forams took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Forams took 3.790855407714844e-05s
Believability | Calculation of trust value for Ocean Drilling - Forams took 1.2159347534179688e-05s
INFO | --- Analysis for oceandrilling-forams took 8.291949272155762s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus LOD took 2.9799439907073975s
Availability | VoID file availability check for Ocean Drilling - Janus LOD took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus LOD took 0.29543614387512207s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus LOD took 0.022574901580810547s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus LOD took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus LOD took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus LOD took 3.647804260253906e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus LOD took 1.621246337890625e-05s
INFO | --- Analysis for oceandrilling-janus took 7.945789813995361s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus Age Models took 12.521759033203125s
Availability | VoID file availability check for Ocean Drilling - Janus Age Models took 0.0007970333099365234s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus Age Models took 0.3000609874725342s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus Age Models took 0.020918607711791992s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus Age Models took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus Age Models took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus Age Models took 3.981590270996094e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus Age Models took 1.4781951904296875e-05s
INFO | --- Analysis for oceandrilling-janusamp took 17.875999450683594s
Availability | SPARQL endpoint availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 2.9632673263549805s
Availability | VoID file availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0008444786071777344s
Completeness | Calculation of interlinking completeness for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.3136451244354248s
Reputation | Calculation of the PageRank for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.020650863647460938s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 3.504753112792969e-05s
Believability | Calculation of trust value for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.4781951904296875e-05s
INFO | --- Analysis for oceandrilling-ldeo took 7.978241443634033s
Availability | SPARQL endpoint availability check for Faceted Application of Subject Terminology took 8.916854858398438e-05s
Availability | VoID file availability check for Faceted Application of Subject Terminology took 0.0008058547973632812s
Completeness | Calculation of interlinking completeness for Faceted Application of Subject Terminology took 0.2898261547088623s
Reputation | Calculation of the PageRank for Faceted Application of Subject Terminology took 0.022872209548950195s
Interlinking | Calculation of Degree of Connection for Faceted Application of Subject Terminology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Faceted Application of Subject Terminology took 0.0007796287536621094s
Interlinking | Calculation of Clustering coefficient for Faceted Application of Subject Terminology took 6.246566772460938e-05s
Believability | Calculation of trust value for Faceted Application of Subject Terminology took 1.5020370483398438e-05s
INFO | --- Analysis for oclc-fast took 9.291208267211914s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 9.72747802734375e-05s
Availability | VoID file availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.2911703586578369s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.020676612854003906s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 3.123283386230469e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 1.0728836059570312e-05s
INFO | --- Analysis for odc-imd-environment-score took 6.289366245269775s
Availability | SPARQL endpoint availability check for Open Data Communities - Lower layer Super Output Areas took 0.20966196060180664s
Availability | VoID file availability check for Open Data Communities - Lower layer Super Output Areas took 0.0006439685821533203s
Extra | Recovery of all triples for Open Data Communities - Lower layer Super Output Areas took 1.0837175846099854s
Performance | Total latancy measurement for Open Data Communities - Lower layer Super Output Areas took 1.0535151958465576s
Amount of data | Number of triples check for Open Data Communities - Lower layer Super Output Areas took 0.1351020336151123s
Interoperability | New terms check for Open Data Communities - Lower layer Super Output Areas took 1.7112541198730469s
Versatility | Languages check for Open Data Communities - Lower layer Super Output Areas took 0.4501776695251465s
Interpretability | Number of blank nodes check for Open Data Communities - Lower layer Super Output Areas took 30.250024795532227s
Security | Check HTTPS for Open Data Communities - Lower layer Super Output Areas took 0.5253422260284424s
Interpretability | RDF structures check for Open Data Communities - Lower layer Super Output Areas took 0.14458203315734863s
Versatility | Serialization formats check for Open Data Communities - Lower layer Super Output Areas took 0.20564508438110352s
Availability | RDF dump link check for Open Data Communities - Lower layer Super Output Areas took 51.62390065193176s
License | MR license check for Open Data Communities - Lower layer Super Output Areas took 0.21031689643859863s
License | HR license check for Open Data Communities - Lower layer Super Output Areas took 30.24004364013672s
Amount of data | Number of property check for Open Data Communities - Lower layer Super Output Areas took 0.13687348365783691s
Understandability | Number of label check for Open Data Communities - Lower layer Super Output Areas took 0.2202451229095459s
Understandability | URI regex check for Open Data Communities - Lower layer Super Output Areas took 0.6683838367462158s
Understandability | Vocabs check for Open Data Communities - Lower layer Super Output Areas took 0.1632530689239502s
Verifiability | Authors check for Open Data Communities - Lower layer Super Output Areas took 0.21227359771728516s
Verifiability | Publishers check for Open Data Communities - Lower layer Super Output Areas took 0.15371084213256836s
Performance | Throughput check for Open Data Communities - Lower layer Super Output Areas took 11.033074617385864s
Amount of data | Check the number of entities for Open Data Communities - Lower layer Super Output Areas took 6.103515625e-05s
Verifiability | Contribs. check for Open Data Communities - Lower layer Super Output Areas took 0.15590476989746094s
Interlinking | sameAs chians check for Open Data Communities - Lower layer Super Output Areas took 0.20133185386657715s
Interlinking | skos check for Open Data Communities - Lower layer Super Output Areas took 0.20744943618774414s
Interlinking | skos check for Open Data Communities - Lower layer Super Output Areas took 0.14888453483581543s
Timeliness | dataset update frequency check for Open Data Communities - Lower layer Super Output Areas took 0.14796948432922363s
Currency | Creation date check for Open Data Communities - Lower layer Super Output Areas took 0.3513810634613037s
Currency | Modification date check for Open Data Communities - Lower layer Super Output Areas took 0.20340871810913086s
Rep.Conc. | URIs length for Open Data Communities - Lower layer Super Output Areas took 1.9026899337768555s
Interoperability | New vocabularies check for Open Data Communities - Lower layer Super Output Areas took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for Open Data Communities - Lower layer Super Output Areas took 0.20605683326721191s
Accuracy | Check Functional Property for Open Data Communities - Lower layer Super Output Areas took 0.19911646842956543s
Accuracy | Check Inverse Functional Property for Open Data Communities - Lower layer Super Output Areas took 0.151045560836792s
Consistency | Disjoint class check for Open Data Communities - Lower layer Super Output Areas took 0.22467255592346191s
Consistency | Check Misplaced properties for Open Data Communities - Lower layer Super Output Areas took 0.6409940719604492s
Consistency | Check Ontology hijacking for Open Data Communities - Lower layer Super Output Areas took 0.972710371017456s
Consistency | Check Invalid usage of undefined properties for Open Data Communities - Lower layer Super Output Areas took 1.6469879150390625s
Conciseness | Check Extensional conciseness for Open Data Communities - Lower layer Super Output Areas took 0.0001533031463623047s
Conciseness | Check Intensional conciseness for Open Data Communities - Lower layer Super Output Areas took 0.4068562984466553s
Security | Sign check for Open Data Communities - Lower layer Super Output Areas took 0.20317387580871582s
Completeness | Calculation of interlinking completeness for Open Data Communities - Lower layer Super Output Areas took 0.3305039405822754s
Reputation | Calculation of the PageRank for Open Data Communities - Lower layer Super Output Areas took 0.021059751510620117s
Interlinking | Calculation of Degree of Connection for Open Data Communities - Lower layer Super Output Areas took 2.2172927856445312e-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.5299530029296875e-05s
Interoperability | Check the re-using of existing vocabs for Open Data Communities - Lower layer Super Output Areas took 2.384185791015625e-06s
Believability | Calculation of trust value for Open Data Communities - Lower layer Super Output Areas took 1.0728836059570312e-05s
INFO | --- Analysis for odc-lsoa took 268.72489619255066s
Availability | SPARQL endpoint availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.10761356353759766s
Availability | VoID file availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.3004631996154785s
Reputation | Calculation of the PageRank for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.02165389060974121s
Interlinking | Calculation of Degree of Connection for Organisation for Economic Co-operation and Development (OECD) Linked Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Organisation for Economic Co-operation and Development (OECD) Linked Data took 9.870529174804688e-05s
Believability | Calculation of trust value for Organisation for Economic Co-operation and Development (OECD) Linked Data took 1.049041748046875e-05s
INFO | --- Analysis for oecd-linked-data took 2.9150118827819824s
Availability | SPARQL endpoint availability check for Orthology and Diseases Information - OGO took 30.22548222541809s
Availability | VoID file availability check for Orthology and Diseases Information - OGO took 0.0008168220520019531s
Completeness | Calculation of interlinking completeness for Orthology and Diseases Information - OGO took 0.33121275901794434s
Reputation | Calculation of the PageRank for Orthology and Diseases Information - OGO took 0.021010875701904297s
Interlinking | Calculation of Degree of Connection for Orthology and Diseases Information - OGO took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Orthology and Diseases Information - OGO took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Orthology and Diseases Information - OGO took 5.3882598876953125e-05s
Believability | Calculation of trust value for Orthology and Diseases Information - OGO took 1.430511474609375e-05s
INFO | --- Analysis for ogolod took 103.102548122406s
Availability | SPARQL endpoint availability check for OLAC Metadata took 4.673004150390625e-05s
Availability | VoID file availability check for OLAC Metadata took 0.0008542537689208984s
Completeness | Calculation of interlinking completeness for OLAC Metadata took 0.29642629623413086s
Reputation | Calculation of the PageRank for OLAC Metadata took 0.02109694480895996s
Interlinking | Calculation of Degree of Connection for OLAC Metadata took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OLAC Metadata took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for OLAC Metadata took 4.124641418457031e-05s
Believability | Calculation of trust value for OLAC Metadata took 1.2874603271484375e-05s
INFO | --- Analysis for olac took 22.94666600227356s
Availability | SPARQL endpoint availability check for OLiA took 9.274482727050781e-05s
Availability | VoID file availability check for OLiA took 0.0007402896881103516s
Completeness | Calculation of interlinking completeness for OLiA took 0.3011770248413086s
Reputation | Calculation of the PageRank for OLiA took 0.022052764892578125s
Interlinking | Calculation of Degree of Connection for OLiA took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OLiA took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for OLiA took 0.0001316070556640625s
Believability | Calculation of trust value for OLiA took 1.430511474609375e-05s
INFO | --- Analysis for olia took 14.881456851959229s
Availability | SPARQL endpoint availability check for OLiA Discourse took 4.458427429199219e-05s
Availability | VoID file availability check for OLiA Discourse took 0.00083160400390625s
Completeness | Calculation of interlinking completeness for OLiA Discourse took 0.32025790214538574s
Reputation | Calculation of the PageRank for OLiA Discourse took 0.020621776580810547s
Interlinking | Calculation of Degree of Connection for OLiA Discourse took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for OLiA Discourse took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for OLiA Discourse took 4.506111145019531e-05s
Believability | Calculation of trust value for OLiA Discourse took 1.4066696166992188e-05s
INFO | --- Analysis for olia-discourse took 7.952579498291016s
Availability | SPARQL endpoint availability check for Open Land Use took 0.1811978816986084s
Availability | VoID file availability check for Open Land Use took 0.0005199909210205078s
Extra | Recovery of all triples for Open Land Use took 116.72078204154968s
Performance | Total latancy measurement for Open Land Use took 0.9777729511260986s
Amount of data | Number of triples check for Open Land Use took 8.98867416381836s
Interoperability | New terms check for Open Land Use took 14.389232635498047s
Versatility | Languages check for Open Land Use took 300.2265317440033s
Interpretability | Number of blank nodes check for Open Land Use took 2.0607333183288574s
Interpretability | RDF structures check for Open Land Use took 0.3581075668334961s
Versatility | Serialization formats check for Open Land Use took 10.511221647262573s
Availability | RDF dump link check for Open Land Use took 0.3968989849090576s
License | MR license check for Open Land Use took 0.9997067451477051s
License | HR license check for Open Land Use took 300.1790728569031s
Amount of data | Number of property check for Open Land Use took 0.23024392127990723s
Understandability | Number of label check for Open Land Use took 3.3661956787109375s
Understandability | URI regex check for Open Land Use took 1.4066708087921143s
Understandability | Vocabs check for Open Land Use took 0.7056035995483398s
Verifiability | Authors check for Open Land Use took 0.19304966926574707s
Verifiability | Publishers check for Open Land Use took 0.24488401412963867s
Performance | Throughput check for Open Land Use took 11.462644577026367s
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.20245862007141113s
Interlinking | sameAs chians check for Open Land Use took 0.2157154083251953s
Interlinking | skos check for Open Land Use took 0.4497532844543457s
Interlinking | skos check for Open Land Use took 0.3896644115447998s
Timeliness | dataset update frequency check for Open Land Use took 5.319357872009277s
Currency | Creation date check for Open Land Use took 0.5118560791015625s
Currency | Modification date check for Open Land Use took 0.25205087661743164s
Rep.Conc. | URIs length for Open Land Use took 159.6544530391693s
Interoperability | New vocabularies check for Open Land Use took 1.1682510375976562e-05s
Consistency | Deprecated classes/propertiers check for Open Land Use took 0.20636963844299316s
Accuracy | Check Functional Property for Open Land Use took 0.5993709564208984s
Accuracy | Check Inverse Functional Property for Open Land Use took 0.5133545398712158s
Accuracy | Check Empty annotation labels for Open Land Use took 40.160722970962524s
Accuracy | Check White space in annotation for Open Land Use took 2.687379837036133s
Accuracy | Check Datatype consistency for Open Land Use took 2.8586390018463135s
Consistency | Disjoint class check for Open Land Use took 0.18900442123413086s
Consistency | Check Misplaced properties for Open Land Use took 86.19925141334534s
Consistency | Misplaced classes for Open Land Use took 8.609581708908081s
Consistency | Check Ontology hijacking for Open Land Use took 36.55385899543762s
Consistency | Check Invalid usage of undefined classes for Open Land Use took 1.6136231422424316s
Consistency | Check Invalid usage of undefined properties for Open Land Use took 86.87210440635681s
Conciseness | Check Extensional conciseness for Open Land Use took 2.763767719268799s
Conciseness | Check Intensional conciseness for Open Land Use took 0.5071372985839844s
Security | Sign check for Open Land Use took 1.7113637924194336s
Availability | Check URIs Dereferenciability for Open Land Use took 9.406537294387817s
Completeness | Calculation of interlinking completeness for Open Land Use took 0.7206435203552246s
Reputation | Calculation of the PageRank for Open Land Use took 0.0265195369720459s
Interlinking | Calculation of Degree of Connection for Open Land Use took 2.3603439331054688e-05s
Interlinking | Calculation of Centrality for Open Land Use took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for Open Land Use took 4.792213439941406e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use took 2.6226043701171875e-06s
Believability | Calculation of trust value for Open Land Use took 1.4066696166992188e-05s
INFO | --- Analysis for OLU took 2281.427771091461s
Availability | SPARQL endpoint availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.6819009780883789s
Availability | VoID file availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for Albanet WordNet (as part of Open Multilingual WordNet) took 0.37603259086608887s
Reputation | Calculation of the PageRank for Albanet WordNet (as part of Open Multilingual WordNet) took 0.024327993392944336s
Interlinking | Calculation of Degree of Connection for Albanet WordNet (as part of Open Multilingual WordNet) took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0011851787567138672s
Interlinking | Calculation of Clustering coefficient for Albanet WordNet (as part of Open Multilingual WordNet) took 6.031990051269531e-05s
Believability | Calculation of trust value for Albanet WordNet (as part of Open Multilingual WordNet) took 1.4781951904296875e-05s
INFO | --- Analysis for omwn-als took 4.080702304840088s
Availability | SPARQL endpoint availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.25661587715148926s
Availability | VoID file availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Arabic WordNet (as part of Open Multilingual WordNet) took 0.28761720657348633s
Reputation | Calculation of the PageRank for Arabic WordNet (as part of Open Multilingual WordNet) took 0.02102804183959961s
Interlinking | Calculation of Degree of Connection for Arabic WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Arabic WordNet (as part of Open Multilingual WordNet) took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Arabic WordNet (as part of Open Multilingual WordNet) took 4.029273986816406e-05s
Believability | Calculation of trust value for Arabic WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
INFO | --- Analysis for omwn-arb took 3.565962076187134s
Availability | SPARQL endpoint availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.2681698799133301s
Availability | VoID file availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0002856254577636719s
Completeness | Calculation of interlinking completeness for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.29064369201660156s
Reputation | Calculation of the PageRank for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.020967721939086914s
Interlinking | Calculation of Degree of Connection for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0008771419525146484s
Interlinking | Calculation of Clustering coefficient for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 4.57763671875e-05s
Believability | Calculation of trust value for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
INFO | --- Analysis for omwn-bul took 3.293644905090332s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2895374298095703s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.3055872917175293s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.02045273780822754s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 4.363059997558594e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 1.430511474609375e-05s
INFO | --- Analysis for omwn-cow took 3.4375522136688232s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.23726224899291992s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.3130009174346924s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.020915508270263672s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 4.38690185546875e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
INFO | --- Analysis for omwn-cwn took 3.4776551723480225s
Availability | SPARQL endpoint availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.2528550624847412s
Availability | VoID file availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for DanNet WordNet (as part of Open Multilingual WordNet) took 0.26749348640441895s
Reputation | Calculation of the PageRank for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0205228328704834s
Interlinking | Calculation of Degree of Connection for DanNet WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for DanNet WordNet (as part of Open Multilingual WordNet) took 4.00543212890625e-05s
Believability | Calculation of trust value for DanNet WordNet (as part of Open Multilingual WordNet) took 9.059906005859375e-06s
INFO | --- Analysis for omwn-dan took 3.3058886528015137s
Availability | SPARQL endpoint availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.2708871364593506s
Availability | VoID file availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for Greek WordNet (as part of Open Multilingual WordNet) took 0.298933744430542s
Reputation | Calculation of the PageRank for Greek WordNet (as part of Open Multilingual WordNet) took 0.022434711456298828s
Interlinking | Calculation of Degree of Connection for Greek WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Greek WordNet (as part of Open Multilingual WordNet) took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Greek WordNet (as part of Open Multilingual WordNet) took 4.38690185546875e-05s
Believability | Calculation of trust value for Greek WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
INFO | --- Analysis for omwn-ell took 3.211472749710083s
Availability | SPARQL endpoint availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.27149438858032227s
Availability | VoID file availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.000278472900390625s
Completeness | Calculation of interlinking completeness for Princeton WordNet (as part of Open Multilingual WordNet) took 0.31276392936706543s
Reputation | Calculation of the PageRank for Princeton WordNet (as part of Open Multilingual WordNet) took 0.02036452293395996s
Interlinking | Calculation of Degree of Connection for Princeton WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Princeton WordNet (as part of Open Multilingual WordNet) took 4.029273986816406e-05s
Believability | Calculation of trust value for Princeton WordNet (as part of Open Multilingual WordNet) took 9.059906005859375e-06s
INFO | --- Analysis for omwn-eng took 3.3881592750549316s
Availability | SPARQL endpoint availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.24894118309020996s
Availability | VoID file availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for Persian WordNet (as part of Open Multilingual WordNet) took 0.3199954032897949s
Reputation | Calculation of the PageRank for Persian WordNet (as part of Open Multilingual WordNet) took 0.020845413208007812s
Interlinking | Calculation of Degree of Connection for Persian WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Persian WordNet (as part of Open Multilingual WordNet) took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Persian WordNet (as part of Open Multilingual WordNet) took 4.076957702636719e-05s
Believability | Calculation of trust value for Persian WordNet (as part of Open Multilingual WordNet) took 8.821487426757812e-06s
INFO | --- Analysis for omwn-fas took 3.3215858936309814s
Availability | SPARQL endpoint availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.257061243057251s
Availability | VoID file availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0005195140838623047s
Completeness | Calculation of interlinking completeness for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.3177011013031006s
Reputation | Calculation of the PageRank for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.02088332176208496s
Interlinking | Calculation of Degree of Connection for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 4.3392181396484375e-05s
Believability | Calculation of trust value for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 1.4066696166992188e-05s
INFO | --- Analysis for omwn-fin took 3.4191620349884033s
Availability | SPARQL endpoint availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.27704310417175293s
Availability | VoID file availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0004582405090332031s
Completeness | Calculation of interlinking completeness for WOLF WordNet (as part of Open Multilingual WordNet) took 0.29036974906921387s
Reputation | Calculation of the PageRank for WOLF WordNet (as part of Open Multilingual WordNet) took 0.020705699920654297s
Interlinking | Calculation of Degree of Connection for WOLF WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for WOLF WordNet (as part of Open Multilingual WordNet) took 4.172325134277344e-05s
Believability | Calculation of trust value for WOLF WordNet (as part of Open Multilingual WordNet) took 1.5497207641601562e-05s
INFO | --- Analysis for omwn-fra took 3.304342269897461s
Availability | SPARQL endpoint availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.2451472282409668s
Availability | VoID file availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.29358410835266113s
Reputation | Calculation of the PageRank for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.020912647247314453s
Interlinking | Calculation of Degree of Connection for Hebrew WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Hebrew WordNet (as part of Open Multilingual WordNet) took 4.1961669921875e-05s
Believability | Calculation of trust value for Hebrew WordNet (as part of Open Multilingual WordNet) took 1.3113021850585938e-05s
INFO | --- Analysis for omwn-heb took 3.3444180488586426s
Availability | SPARQL endpoint availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.2528038024902344s
Availability | VoID file availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for Croatian WordNet (as part of Open Multilingual WordNet) took 0.29086732864379883s
Reputation | Calculation of the PageRank for Croatian WordNet (as part of Open Multilingual WordNet) took 0.022418975830078125s
Interlinking | Calculation of Degree of Connection for Croatian WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Croatian WordNet (as part of Open Multilingual WordNet) took 4.029273986816406e-05s
Believability | Calculation of trust value for Croatian WordNet (as part of Open Multilingual WordNet) took 1.33514404296875e-05s
INFO | --- Analysis for omwn-hrv took 3.3368635177612305s
Availability | SPARQL endpoint availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.2228071689605713s
Availability | VoID file availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.30617690086364746s
Reputation | Calculation of the PageRank for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.02101755142211914s
Interlinking | Calculation of Degree of Connection for IceWordNet WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for IceWordNet WordNet (as part of Open Multilingual WordNet) took 4.482269287109375e-05s
Believability | Calculation of trust value for IceWordNet WordNet (as part of Open Multilingual WordNet) took 1.5974044799804688e-05s
INFO | --- Analysis for omwn-isl took 3.2833118438720703s
Availability | SPARQL endpoint availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.262615442276001s
Availability | VoID file availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0005445480346679688s
Completeness | Calculation of interlinking completeness for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.32021570205688477s
Reputation | Calculation of the PageRank for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.020639657974243164s
Interlinking | Calculation of Degree of Connection for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 4.172325134277344e-05s
Believability | Calculation of trust value for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 1.4066696166992188e-05s
INFO | --- Analysis for omwn-ita took 3.348654270172119s
Availability | SPARQL endpoint availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.25400280952453613s
Availability | VoID file availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.3003199100494385s
Reputation | Calculation of the PageRank for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.020994901657104492s
Interlinking | Calculation of Degree of Connection for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 4.267692565917969e-05s
Believability | Calculation of trust value for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 1.4066696166992188e-05s
INFO | --- Analysis for omwn-iwn took 3.339106559753418s
Availability | SPARQL endpoint availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.24651050567626953s
Availability | VoID file availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for Japanese WordNet (as part of Open Multilingual WordNet) took 0.30182480812072754s
Reputation | Calculation of the PageRank for Japanese WordNet (as part of Open Multilingual WordNet) took 0.020869970321655273s
Interlinking | Calculation of Degree of Connection for Japanese WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Japanese WordNet (as part of Open Multilingual WordNet) took 4.291534423828125e-05s
Believability | Calculation of trust value for Japanese WordNet (as part of Open Multilingual WordNet) took 1.5020370483398438e-05s
INFO | --- Analysis for omwn-jpn took 3.6982057094573975s
Availability | SPARQL endpoint availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.2693359851837158s
Availability | VoID file availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.32123899459838867s
Reputation | Calculation of the PageRank for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.020867109298706055s
Interlinking | Calculation of Degree of Connection for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Multilingual Central Repository (as part of Open Multilingual WordNet) took 3.9577484130859375e-05s
Believability | Calculation of trust value for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.4781951904296875e-05s
INFO | --- Analysis for omwn-mcr took 3.3384954929351807s
Availability | SPARQL endpoint availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.23200201988220215s
Availability | VoID file availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.2915005683898926s
Reputation | Calculation of the PageRank for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.03191828727722168s
Interlinking | Calculation of Degree of Connection for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0012862682342529297s
Interlinking | Calculation of Clustering coefficient for Wordnet WordNet (as part of Open Multilingual WordNet) took 5.7697296142578125e-05s
Believability | Calculation of trust value for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.4781951904296875e-05s
INFO | --- Analysis for omwn-msa took 3.3308136463165283s
Availability | SPARQL endpoint availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.2534761428833008s
Availability | VoID file availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for Open WordNet (as part of Open Multilingual WordNet) took 0.29025769233703613s
Reputation | Calculation of the PageRank for Open WordNet (as part of Open Multilingual WordNet) took 0.02259540557861328s
Interlinking | Calculation of Degree of Connection for Open WordNet (as part of Open Multilingual WordNet) took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Open WordNet (as part of Open Multilingual WordNet) took 0.0008287429809570312s
Interlinking | Calculation of Clustering coefficient for Open WordNet (as part of Open Multilingual WordNet) took 4.673004150390625e-05s
Believability | Calculation of trust value for Open WordNet (as part of Open Multilingual WordNet) took 1.5974044799804688e-05s
INFO | --- Analysis for omwn-nld took 3.3667356967926025s
Availability | SPARQL endpoint availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.2532227039337158s
Availability | VoID file availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0005035400390625s
Completeness | Calculation of interlinking completeness for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.2775254249572754s
Reputation | Calculation of the PageRank for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.020731210708618164s
Interlinking | Calculation of Degree of Connection for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0008122920989990234s
Interlinking | Calculation of Clustering coefficient for Norwegian WordNet (as part of Open Multilingual WordNet) took 4.5299530029296875e-05s
Believability | Calculation of trust value for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
INFO | --- Analysis for omwn-nor took 3.4155728816986084s
Availability | SPARQL endpoint availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.2574436664581299s
Availability | VoID file availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.00045180320739746094s
Completeness | Calculation of interlinking completeness for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.2960214614868164s
Reputation | Calculation of the PageRank for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.020560264587402344s
Interlinking | Calculation of Degree of Connection for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for plWordNet WordNet (as part of Open Multilingual WordNet) took 3.981590270996094e-05s
Believability | Calculation of trust value for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.4066696166992188e-05s
INFO | --- Analysis for omwn-pol took 3.2899553775787354s
Availability | SPARQL endpoint availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.2628452777862549s
Availability | VoID file availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.3383045196533203s
Reputation | Calculation of the PageRank for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.02132415771484375s
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.0007784366607666016s
Interlinking | Calculation of Clustering coefficient for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 4.315376281738281e-05s
Believability | Calculation of trust value for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
INFO | --- Analysis for omwn-por took 3.4269814491271973s
Availability | SPARQL endpoint availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.23482728004455566s
Availability | VoID file availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for Romanian WordNet (as part of Open Multilingual WordNet) took 0.294327974319458s
Reputation | Calculation of the PageRank for Romanian WordNet (as part of Open Multilingual WordNet) took 0.020684242248535156s
Interlinking | Calculation of Degree of Connection for Romanian WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Romanian WordNet (as part of Open Multilingual WordNet) took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Romanian WordNet (as part of Open Multilingual WordNet) took 3.981590270996094e-05s
Believability | Calculation of trust value for Romanian WordNet (as part of Open Multilingual WordNet) took 1.4781951904296875e-05s
INFO | --- Analysis for omwn-ron took 3.535252571105957s
Availability | SPARQL endpoint availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.2525653839111328s
Availability | VoID file availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.00032901763916015625s
Completeness | Calculation of interlinking completeness for Slovak WordNet (as part of Open Multilingual WordNet) took 0.30910778045654297s
Reputation | Calculation of the PageRank for Slovak WordNet (as part of Open Multilingual WordNet) took 0.020759105682373047s
Interlinking | Calculation of Degree of Connection for Slovak WordNet (as part of Open Multilingual WordNet) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Slovak WordNet (as part of Open Multilingual WordNet) took 4.315376281738281e-05s
Believability | Calculation of trust value for Slovak WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
INFO | --- Analysis for omwn-slk took 3.255634069442749s
Availability | SPARQL endpoint availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.2639305591583252s
Availability | VoID file availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0005025863647460938s
Completeness | Calculation of interlinking completeness for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.3268892765045166s
Reputation | Calculation of the PageRank for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0207827091217041s
Interlinking | Calculation of Degree of Connection for sloWNet WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for sloWNet WordNet (as part of Open Multilingual WordNet) took 4.172325134277344e-05s
Believability | Calculation of trust value for sloWNet WordNet (as part of Open Multilingual WordNet) took 1.6689300537109375e-05s
INFO | --- Analysis for omwn-slv took 3.317915201187134s
Availability | SPARQL endpoint availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.24881339073181152s
Availability | VoID file availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for Swedish WordNet (as part of Open Multilingual WordNet) took 0.3166956901550293s
Reputation | Calculation of the PageRank for Swedish WordNet (as part of Open Multilingual WordNet) took 0.020877361297607422s
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.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Swedish WordNet (as part of Open Multilingual WordNet) took 4.38690185546875e-05s
Believability | Calculation of trust value for Swedish WordNet (as part of Open Multilingual WordNet) took 1.5020370483398438e-05s
INFO | --- Analysis for omwn-swe took 3.386411666870117s
Availability | SPARQL endpoint availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.2614924907684326s
Availability | VoID file availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for Thai WordNet (as part of Open Multilingual WordNet) took 0.3156893253326416s
Reputation | Calculation of the PageRank for Thai WordNet (as part of Open Multilingual WordNet) took 0.021696090698242188s
Interlinking | Calculation of Degree of Connection for Thai WordNet (as part of Open Multilingual WordNet) took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Thai WordNet (as part of Open Multilingual WordNet) took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Thai WordNet (as part of Open Multilingual WordNet) took 5.412101745605469e-05s
Believability | Calculation of trust value for Thai WordNet (as part of Open Multilingual WordNet) took 1.430511474609375e-05s
INFO | --- Analysis for omwn-tha took 3.4056241512298584s
Availability | SPARQL endpoint availability check for OntoBeef Domain took 5.105693101882935s
Availability | VoID file availability check for OntoBeef Domain took 0.0006897449493408203s
Completeness | Calculation of interlinking completeness for OntoBeef Domain took 0.30243873596191406s
Reputation | Calculation of the PageRank for OntoBeef Domain took 0.022260427474975586s
Interlinking | Calculation of Degree of Connection for OntoBeef Domain took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for OntoBeef Domain took 0.0007953643798828125s
Interlinking | Calculation of Clustering coefficient for OntoBeef Domain took 5.888938903808594e-05s
Believability | Calculation of trust value for OntoBeef Domain took 1.3113021850585938e-05s
INFO | --- Analysis for ontobeef-domain took 36.439409255981445s
Availability | SPARQL endpoint availability check for Ontos News Portal took 4.458427429199219e-05s
Availability | VoID file availability check for Ontos News Portal took 0.0006368160247802734s
Completeness | Calculation of interlinking completeness for Ontos News Portal took 0.3319563865661621s
Reputation | Calculation of the PageRank for Ontos News Portal took 0.02078866958618164s
Interlinking | Calculation of Degree of Connection for Ontos News Portal took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ontos News Portal took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Ontos News Portal took 9.489059448242188e-05s
Believability | Calculation of trust value for Ontos News Portal took 1.4781951904296875e-05s
INFO | --- Analysis for ontos-news-portal took 4.743561744689941s
Availability | SPARQL endpoint availability check for Ookaboo RDF dump took 4.458427429199219e-05s
Availability | VoID file availability check for Ookaboo RDF dump took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for Ookaboo RDF dump took 0.27036380767822266s
Reputation | Calculation of the PageRank for Ookaboo RDF dump took 0.021024465560913086s
Interlinking | Calculation of Degree of Connection for Ookaboo RDF dump took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Ookaboo RDF dump took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for Ookaboo RDF dump took 3.3855438232421875e-05s
Believability | Calculation of trust value for Ookaboo RDF dump took 1.1682510375976562e-05s
INFO | --- Analysis for ookaboo-rdf-dump took 2.7960503101348877s
Availability | SPARQL endpoint availability check for Open Bantu isiXhosa Lexicon took 4.482269287109375e-05s
Availability | VoID file availability check for Open Bantu isiXhosa Lexicon took 0.0005278587341308594s
Completeness | Calculation of interlinking completeness for Open Bantu isiXhosa Lexicon took 0.3193240165710449s
Reputation | Calculation of the PageRank for Open Bantu isiXhosa Lexicon took 0.02111530303955078s
Interlinking | Calculation of Degree of Connection for Open Bantu isiXhosa Lexicon took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Open Bantu isiXhosa Lexicon took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for Open Bantu isiXhosa Lexicon took 4.6253204345703125e-05s
Believability | Calculation of trust value for Open Bantu isiXhosa Lexicon took 1.4066696166992188e-05s
INFO | --- Analysis for open-bantu-isixhosa-lexicon took 10.541454553604126s
Availability | SPARQL endpoint availability check for Open Data Euskadi took 4.410743713378906e-05s
Availability | VoID file availability check for Open Data Euskadi took 0.0007176399230957031s
Completeness | Calculation of interlinking completeness for Open Data Euskadi took 0.33300352096557617s
Reputation | Calculation of the PageRank for Open Data Euskadi took 0.020471572875976562s
Interlinking | Calculation of Degree of Connection for Open Data Euskadi took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Data Euskadi took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Open Data Euskadi took 5.0067901611328125e-05s
Believability | Calculation of trust value for Open Data Euskadi took 6.4373016357421875e-06s
INFO | --- Analysis for open-data-euskadi took 8.325705528259277s
Availability | SPARQL endpoint availability check for Open Data RISP, the Spanish Open Data community took 9.131431579589844e-05s
Availability | VoID file availability check for Open Data RISP, the Spanish Open Data community took 0.0007910728454589844s
Completeness | Calculation of interlinking completeness for Open Data RISP, the Spanish Open Data community took 0.28885316848754883s
Reputation | Calculation of the PageRank for Open Data RISP, the Spanish Open Data community took 0.02072453498840332s
Interlinking | Calculation of Degree of Connection for Open Data RISP, the Spanish Open Data community took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Data RISP, the Spanish Open Data community took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Open Data RISP, the Spanish Open Data community took 0.00010609626770019531s
Believability | Calculation of trust value for Open Data RISP, the Spanish Open Data community took 1.3113021850585938e-05s
INFO | --- Analysis for open-data-risp took 6.59612774848938s
Availability | SPARQL endpoint availability check for Open Data Thesaurus took 0.18054890632629395s
Availability | VoID file availability check for Open Data Thesaurus took 0.0006916522979736328s
Extra | Recovery of all triples for Open Data Thesaurus took 1.1589198112487793s
Performance | Total latancy measurement for Open Data Thesaurus took 0.4568908214569092s
Amount of data | Number of triples check for Open Data Thesaurus took 0.13284945487976074s
Interoperability | New terms check for Open Data Thesaurus took 1.5546138286590576s
Versatility | Languages check for Open Data Thesaurus took 0.12297868728637695s
Interpretability | Number of blank nodes check for Open Data Thesaurus took 0.11319661140441895s
Security | Check HTTPS for Open Data Thesaurus took 0.33210253715515137s
Interpretability | RDF structures check for Open Data Thesaurus took 0.1269974708557129s
Versatility | Serialization formats check for Open Data Thesaurus took 0.11738109588623047s
Availability | RDF dump link check for Open Data Thesaurus took 1.088019609451294s
License | MR license check for Open Data Thesaurus took 0.12674617767333984s
License | HR license check for Open Data Thesaurus took 0.09203934669494629s
Amount of data | Number of property check for Open Data Thesaurus took 0.11154508590698242s
Understandability | Number of label check for Open Data Thesaurus took 0.11237835884094238s
Understandability | URI regex check for Open Data Thesaurus took 0.16762351989746094s
Understandability | Vocabs check for Open Data Thesaurus took 0.11843442916870117s
Verifiability | Authors check for Open Data Thesaurus took 0.11406493186950684s
Verifiability | Publishers check for Open Data Thesaurus took 0.1216423511505127s
Performance | Throughput check for Open Data Thesaurus took 10.580424308776855s
Amount of data | Check the number of entities for Open Data Thesaurus took 0.00011348724365234375s
Verifiability | Contribs. check for Open Data Thesaurus took 0.11441993713378906s
Interlinking | sameAs chians check for Open Data Thesaurus took 0.12428045272827148s
Interlinking | skos check for Open Data Thesaurus took 0.11168360710144043s
Interlinking | skos check for Open Data Thesaurus took 0.08780407905578613s
Timeliness | dataset update frequency check for Open Data Thesaurus took 0.07997536659240723s
Currency | Creation date check for Open Data Thesaurus took 0.1959519386291504s
Currency | Modification date check for Open Data Thesaurus took 0.19249248504638672s
Rep.Conc. | URIs length for Open Data Thesaurus took 0.4581034183502197s
Interoperability | New vocabularies check for Open Data Thesaurus took 0.9392268657684326s
Consistency | Deprecated classes/propertiers check for Open Data Thesaurus took 0.12029623985290527s
Accuracy | Check Functional Property for Open Data Thesaurus took 0.09502816200256348s
Accuracy | Check Inverse Functional Property for Open Data Thesaurus took 0.08768582344055176s
Accuracy | Check Empty annotation labels for Open Data Thesaurus took 0.18674302101135254s
Accuracy | Check White space in annotation for Open Data Thesaurus took 0.0011105537414550781s
Consistency | Disjoint class check for Open Data Thesaurus took 0.09493064880371094s
Consistency | Check Misplaced properties for Open Data Thesaurus took 0.1840362548828125s
Consistency | Misplaced classes for Open Data Thesaurus took 0.09671759605407715s
Consistency | Check Ontology hijacking for Open Data Thesaurus took 1.5898399353027344s
Consistency | Check Invalid usage of undefined properties for Open Data Thesaurus took 1.526533842086792s
Conciseness | Check Extensional conciseness for Open Data Thesaurus took 0.0001583099365234375s
Security | Sign check for Open Data Thesaurus took 0.09422636032104492s
Completeness | Calculation of interlinking completeness for Open Data Thesaurus took 0.28209424018859863s
Reputation | Calculation of the PageRank for Open Data Thesaurus took 0.021127939224243164s
Interlinking | Calculation of Degree of Connection for Open Data Thesaurus took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Open Data Thesaurus took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Open Data Thesaurus took 8.344650268554688e-05s
Interoperability | Check the re-using of existing vocabs for Open Data Thesaurus took 0.47072291374206543s
Believability | Calculation of trust value for Open Data Thesaurus took 1.5497207641601562e-05s
INFO | --- Analysis for open-data-thesaurus took 72.52502536773682s
Availability | SPARQL endpoint availability check for Open Election Data Project took 4.673004150390625e-05s
Availability | VoID file availability check for Open Election Data Project took 0.0008139610290527344s
Completeness | Calculation of interlinking completeness for Open Election Data Project took 0.3407769203186035s
Reputation | Calculation of the PageRank for Open Election Data Project took 0.020885467529296875s
Interlinking | Calculation of Degree of Connection for Open Election Data Project took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Open Election Data Project took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Open Election Data Project took 8.225440979003906e-05s
Believability | Calculation of trust value for Open Election Data Project took 1.239776611328125e-05s
INFO | --- Analysis for open-election-data-project took 42.8297176361084s
Availability | SPARQL endpoint availability check for OpenEI - Open Energy Info took 3.9965884685516357s
Availability | VoID file availability check for OpenEI - Open Energy Info took 0.0007479190826416016s
Completeness | Calculation of interlinking completeness for OpenEI - Open Energy Info took 0.35840582847595215s
Reputation | Calculation of the PageRank for OpenEI - Open Energy Info took 0.02048468589782715s
Interlinking | Calculation of Degree of Connection for OpenEI - Open Energy Info took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for OpenEI - Open Energy Info took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for OpenEI - Open Energy Info took 8.845329284667969e-05s
Believability | Calculation of trust value for OpenEI - Open Energy Info took 1.049041748046875e-05s
INFO | --- Analysis for open-energy-info-wiki took 17.926944732666016s
Availability | SPARQL endpoint availability check for Open Library took 4.410743713378906e-05s
Availability | VoID file availability check for Open Library took 0.0007920265197753906s
Completeness | Calculation of interlinking completeness for Open Library took 0.30374813079833984s
Reputation | Calculation of the PageRank for Open Library took 0.021031856536865234s
Interlinking | Calculation of Degree of Connection for Open Library took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Open Library took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Open Library took 7.557868957519531e-05s
Believability | Calculation of trust value for Open Library took 1.0251998901367188e-05s
INFO | --- Analysis for open-library took 11.716657400131226s
Availability | SPARQL endpoint availability check for Open Land Use @PSNC took 0.20243620872497559s
Availability | VoID file availability check for Open Land Use @PSNC took 0.0005366802215576172s
Extra | Recovery of all triples for Open Land Use @PSNC took 110.88222289085388s
Performance | Total latancy measurement for Open Land Use @PSNC took 1.1163620948791504s
Amount of data | Number of triples check for Open Land Use @PSNC took 9.054536819458008s
Interoperability | New terms check for Open Land Use @PSNC took 14.587642431259155s
Versatility | Languages check for Open Land Use @PSNC took 300.2076880931854s
Interpretability | Number of blank nodes check for Open Land Use @PSNC took 2.04475736618042s
Interpretability | RDF structures check for Open Land Use @PSNC took 0.2774512767791748s
Versatility | Serialization formats check for Open Land Use @PSNC took 9.890433073043823s
Availability | RDF dump link check for Open Land Use @PSNC took 0.40256285667419434s
License | MR license check for Open Land Use @PSNC took 0.9902389049530029s
License | HR license check for Open Land Use @PSNC took 300.2448019981384s
Amount of data | Number of property check for Open Land Use @PSNC took 0.21181154251098633s
Understandability | Number of label check for Open Land Use @PSNC took 3.5461323261260986s
Understandability | URI regex check for Open Land Use @PSNC took 1.1162264347076416s
Understandability | Vocabs check for Open Land Use @PSNC took 0.6247642040252686s
Verifiability | Authors check for Open Land Use @PSNC took 0.20569062232971191s
Verifiability | Publishers check for Open Land Use @PSNC took 0.253521203994751s
Performance | Throughput check for Open Land Use @PSNC took 11.58091950416565s
Amount of data | Check the number of entities for Open Land Use @PSNC took 7.033348083496094e-05s
Verifiability | Contribs. check for Open Land Use @PSNC took 0.17988872528076172s
Interlinking | sameAs chians check for Open Land Use @PSNC took 0.18378090858459473s
Interlinking | skos check for Open Land Use @PSNC took 0.426166296005249s
Interlinking | skos check for Open Land Use @PSNC took 0.41196203231811523s
Timeliness | dataset update frequency check for Open Land Use @PSNC took 4.44780421257019s
Currency | Creation date check for Open Land Use @PSNC took 0.48165225982666016s
Currency | Modification date check for Open Land Use @PSNC took 0.22408080101013184s
Rep.Conc. | URIs length for Open Land Use @PSNC took 165.50952672958374s
Interoperability | New vocabularies check for Open Land Use @PSNC took 1.239776611328125e-05s
Consistency | Deprecated classes/propertiers check for Open Land Use @PSNC took 0.19830107688903809s
Accuracy | Check Functional Property for Open Land Use @PSNC took 0.5219030380249023s
Accuracy | Check Inverse Functional Property for Open Land Use @PSNC took 0.50826096534729s
Accuracy | Check Empty annotation labels for Open Land Use @PSNC took 39.29783582687378s
Accuracy | Check White space in annotation for Open Land Use @PSNC took 2.680184841156006s
Accuracy | Check Datatype consistency for Open Land Use @PSNC took 2.8057308197021484s
Consistency | Disjoint class check for Open Land Use @PSNC took 0.18666696548461914s
Consistency | Check Misplaced properties for Open Land Use @PSNC took 87.29580569267273s
Consistency | Misplaced classes for Open Land Use @PSNC took 8.714330434799194s
Consistency | Check Ontology hijacking for Open Land Use @PSNC took 36.30115032196045s
Consistency | Check Invalid usage of undefined classes for Open Land Use @PSNC took 1.6218931674957275s
Consistency | Check Invalid usage of undefined properties for Open Land Use @PSNC took 87.86180138587952s
Conciseness | Check Extensional conciseness for Open Land Use @PSNC took 2.7861685752868652s
Conciseness | Check Intensional conciseness for Open Land Use @PSNC took 0.689643383026123s
Security | Sign check for Open Land Use @PSNC took 1.4493725299835205s
Availability | Check URIs Dereferenciability for Open Land Use @PSNC took 10.38552188873291s
Completeness | Calculation of interlinking completeness for Open Land Use @PSNC took 0.5111334323883057s
Reputation | Calculation of the PageRank for Open Land Use @PSNC took 0.02335953712463379s
Interlinking | Calculation of Degree of Connection for Open Land Use @PSNC took 7.271766662597656e-05s
Interlinking | Calculation of Centrality for Open Land Use @PSNC took 0.0008604526519775391s
Interlinking | Calculation of Clustering coefficient for Open Land Use @PSNC took 4.7206878662109375e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use @PSNC took 2.86102294921875e-06s
Believability | Calculation of trust value for Open Land Use @PSNC took 1.430511474609375e-05s
INFO | --- Analysis for Open_Land_Use took 2290.1703453063965s
Availability | SPARQL endpoint availability check for flyatlas took 1.1965548992156982s
Availability | VoID file availability check for flyatlas took 0.0006384849548339844s
Completeness | Calculation of interlinking completeness for flyatlas took 0.32763028144836426s
Reputation | Calculation of the PageRank for flyatlas took 0.021413087844848633s
Interlinking | Calculation of Degree of Connection for flyatlas took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for flyatlas took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for flyatlas took 4.1961669921875e-05s
Believability | Calculation of trust value for flyatlas took 1.621246337890625e-05s
INFO | --- Analysis for openbiomed-flyatlas took 5.915239095687866s
Availability | SPARQL endpoint availability check for OpenCalais took 8.797645568847656e-05s
Availability | VoID file availability check for OpenCalais took 0.000736236572265625s
Completeness | Calculation of interlinking completeness for OpenCalais took 0.2916224002838135s
Reputation | Calculation of the PageRank for OpenCalais took 0.021189212799072266s
Interlinking | Calculation of Degree of Connection for OpenCalais took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for OpenCalais took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for OpenCalais took 0.00011396408081054688s
Believability | Calculation of trust value for OpenCalais took 1.4543533325195312e-05s
INFO | --- Analysis for opencalais took 6.861241340637207s
Availability | SPARQL endpoint availability check for OpenCorporates - The Open Database Of The Corporate World took 0.00011205673217773438s
Availability | VoID file availability check for OpenCorporates - The Open Database Of The Corporate World took 0.0007016658782958984s
Completeness | Calculation of interlinking completeness for OpenCorporates - The Open Database Of The Corporate World took 0.28185129165649414s
Reputation | Calculation of the PageRank for OpenCorporates - The Open Database Of The Corporate World took 0.0207979679107666s
Interlinking | Calculation of Degree of Connection for OpenCorporates - The Open Database Of The Corporate World took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for OpenCorporates - The Open Database Of The Corporate World took 0.0007908344268798828s
Interlinking | Calculation of Clustering coefficient for OpenCorporates - The Open Database Of The Corporate World took 8.082389831542969e-05s
Believability | Calculation of trust value for OpenCorporates - The Open Database Of The Corporate World took 1.1205673217773438e-05s
INFO | --- Analysis for opencorporates took 2.913651943206787s
Availability | SPARQL endpoint availability check for OpenCyc took 9.1552734375e-05s
Availability | VoID file availability check for OpenCyc took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for OpenCyc took 0.28435635566711426s
Reputation | Calculation of the PageRank for OpenCyc took 0.022964000701904297s
Interlinking | Calculation of Degree of Connection for OpenCyc took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OpenCyc took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for OpenCyc took 0.00011157989501953125s
Believability | Calculation of trust value for OpenCyc took 1.3589859008789062e-05s
INFO | --- Analysis for opencyc took 2.729491710662842s
Availability | SPARQL endpoint availability check for opendatacommunities-dev-local-authority-services took 0.00015401840209960938s
Availability | VoID file availability check for opendatacommunities-dev-local-authority-services took 0.0007112026214599609s
Completeness | Calculation of interlinking completeness for opendatacommunities-dev-local-authority-services took 0.33107757568359375s
Reputation | Calculation of the PageRank for opendatacommunities-dev-local-authority-services took 0.021059036254882812s
Interlinking | Calculation of Degree of Connection for opendatacommunities-dev-local-authority-services took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for opendatacommunities-dev-local-authority-services took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-dev-local-authority-services took 5.030632019042969e-05s
Believability | Calculation of trust value for opendatacommunities-dev-local-authority-services took 1.430511474609375e-05s
INFO | --- Analysis for opendatacommunities-dev-local-authority-services took 3.8377106189727783s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-acceptances-per-1000 took 5.555152893066406e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-acceptances-per-1000 took 0.0006473064422607422s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-acceptances-per-1000 took 0.3159830570220947s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-acceptances-per-1000 took 0.020563840866088867s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-acceptances-per-1000 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-acceptances-per-1000 took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-acceptances-per-1000 took 4.363059997558594e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-acceptances-per-1000 took 1.52587890625e-05s
INFO | --- Analysis for opendatacommunities-homelessness-acceptances-per-1000 took 4.7614521980285645s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 9.34600830078125e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0007939338684082031s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.31874799728393555s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.02075958251953125s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 4.410743713378906e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.4543533325195312e-05s
INFO | --- Analysis for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 3.371251106262207s
Availability | SPARQL endpoint availability check for opendatacommunities-households-2008 took 9.083747863769531e-05s
Availability | VoID file availability check for opendatacommunities-households-2008 took 0.0005435943603515625s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-2008 took 0.3300929069519043s
Reputation | Calculation of the PageRank for opendatacommunities-households-2008 took 0.022241830825805664s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-2008 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-2008 took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-2008 took 4.1961669921875e-05s
Believability | Calculation of trust value for opendatacommunities-households-2008 took 1.4543533325195312e-05s
INFO | --- Analysis for opendatacommunities-households-2008 took 2.6540510654449463s
Availability | SPARQL endpoint availability check for opendatacommunities-households-accommodated-per-1000 took 9.34600830078125e-05s
Availability | VoID file availability check for opendatacommunities-households-accommodated-per-1000 took 0.0006690025329589844s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-accommodated-per-1000 took 0.30504679679870605s
Reputation | Calculation of the PageRank for opendatacommunities-households-accommodated-per-1000 took 0.020919084548950195s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-accommodated-per-1000 took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-accommodated-per-1000 took 0.0008399486541748047s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-accommodated-per-1000 took 4.8160552978515625e-05s
Believability | Calculation of trust value for opendatacommunities-households-accommodated-per-1000 took 1.3589859008789062e-05s
INFO | --- Analysis for opendatacommunities-households-accommodated-per-1000 took 3.4366705417633057s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-population took 5.316734313964844e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-population took 0.0006897449493408203s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-population took 0.3463284969329834s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-population took 0.02221226692199707s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-population took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-population took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-population took 4.267692565917969e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-population took 1.4781951904296875e-05s
INFO | --- Analysis for opendatacommunities-households-projections-population took 3.574399948120117s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-totalhouseolds took 4.601478576660156e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-totalhouseolds took 0.0006690025329589844s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-totalhouseolds took 0.28298282623291016s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-totalhouseolds took 0.021066665649414062s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-totalhouseolds took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-totalhouseolds took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-totalhouseolds took 4.029273986816406e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-totalhouseolds took 1.4066696166992188e-05s
INFO | --- Analysis for opendatacommunities-households-projections-totalhouseolds took 4.067591667175293s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 8.96453857421875e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.2921872138977051s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.020838499069213867s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 4.458427429199219e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.3828277587890625e-05s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 2.7354345321655273s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.00010466575622558594s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0007114410400390625s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.28582763671875s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.02076268196105957s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 4.124641418457031e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.4781951904296875e-05s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 3.3590316772460938s
Availability | SPARQL endpoint availability check for opendatacommunities-housing-market took 9.751319885253906e-05s
Availability | VoID file availability check for opendatacommunities-housing-market took 0.0006587505340576172s
Completeness | Calculation of interlinking completeness for opendatacommunities-housing-market took 0.33818840980529785s
Reputation | Calculation of the PageRank for opendatacommunities-housing-market took 0.021511316299438477s
Interlinking | Calculation of Degree of Connection for opendatacommunities-housing-market took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-housing-market took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-housing-market took 4.100799560546875e-05s
Believability | Calculation of trust value for opendatacommunities-housing-market took 1.4543533325195312e-05s
INFO | --- Analysis for opendatacommunities-housing-market took 3.536202907562256s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-crime-rank-2010 took 4.744529724121094e-05s
Availability | VoID file availability check for opendatacommunities-imd-crime-rank-2010 took 0.0006802082061767578s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-crime-rank-2010 took 0.3180546760559082s
Reputation | Calculation of the PageRank for opendatacommunities-imd-crime-rank-2010 took 0.020864009857177734s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-crime-rank-2010 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-crime-rank-2010 took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-crime-rank-2010 took 4.506111145019531e-05s
Believability | Calculation of trust value for opendatacommunities-imd-crime-rank-2010 took 1.3828277587890625e-05s
INFO | --- Analysis for opendatacommunities-imd-crime-rank-2010 took 3.629997491836548s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-environment-rank-2010 took 9.250640869140625e-05s
Availability | VoID file availability check for opendatacommunities-imd-environment-rank-2010 took 0.0006539821624755859s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-environment-rank-2010 took 0.31413817405700684s
Reputation | Calculation of the PageRank for opendatacommunities-imd-environment-rank-2010 took 0.02267622947692871s
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.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-environment-rank-2010 took 4.124641418457031e-05s
Believability | Calculation of trust value for opendatacommunities-imd-environment-rank-2010 took 1.52587890625e-05s
INFO | --- Analysis for opendatacommunities-imd-environment-rank-2010 took 4.739541053771973s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-income-rank-la-2010 took 4.8160552978515625e-05s
Availability | VoID file availability check for opendatacommunities-imd-income-rank-la-2010 took 0.0008149147033691406s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-income-rank-la-2010 took 0.27768802642822266s
Reputation | Calculation of the PageRank for opendatacommunities-imd-income-rank-la-2010 took 0.020564556121826172s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-income-rank-la-2010 took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-income-rank-la-2010 took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-income-rank-la-2010 took 4.7206878662109375e-05s
Believability | Calculation of trust value for opendatacommunities-imd-income-rank-la-2010 took 1.3828277587890625e-05s
INFO | --- Analysis for opendatacommunities-imd-income-rank-la-2010 took 3.3655972480773926s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-rank-2010 took 8.821487426757812e-05s
Availability | VoID file availability check for opendatacommunities-imd-rank-2010 took 0.0005888938903808594s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-rank-2010 took 0.30321407318115234s
Reputation | Calculation of the PageRank for opendatacommunities-imd-rank-2010 took 0.02486443519592285s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-rank-2010 took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-rank-2010 took 0.0013396739959716797s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-rank-2010 took 5.817413330078125e-05s
Believability | Calculation of trust value for opendatacommunities-imd-rank-2010 took 1.4781951904296875e-05s
INFO | --- Analysis for opendatacommunities-imd-rank-2010 took 2.8687095642089844s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-score-2010 took 0.00012254714965820312s
Availability | VoID file availability check for opendatacommunities-imd-score-2010 took 0.0006587505340576172s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-score-2010 took 0.2793998718261719s
Reputation | Calculation of the PageRank for opendatacommunities-imd-score-2010 took 0.02104496955871582s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-score-2010 took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-score-2010 took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-score-2010 took 4.482269287109375e-05s
Believability | Calculation of trust value for opendatacommunities-imd-score-2010 took 1.0728836059570312e-05s
INFO | --- Analysis for opendatacommunities-imd-score-2010 took 3.476358652114868s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 4.458427429199219e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0007627010345458984s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-affordable-housing-starts took 0.28948235511779785s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-affordable-housing-starts took 0.021046161651611328s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-affordable-housing-starts took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0008504390716552734s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-affordable-housing-starts took 4.863739013671875e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-affordable-housing-starts took 1.430511474609375e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-affordable-housing-starts took 3.4595658779144287s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.9591064453125e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0003974437713623047s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.30344700813293457s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.020847082138061523s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.458427429199219e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.3828277587890625e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 3.4889461994171143s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-housing-starts took 8.749961853027344e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-housing-starts took 0.0006158351898193359s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-housing-starts took 0.29217028617858887s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-housing-starts took 0.02070903778076172s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-housing-starts took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-housing-starts took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-housing-starts took 4.4345855712890625e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-housing-starts took 1.430511474609375e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-housing-starts took 3.41192889213562s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-planning-applications-granted took 4.458427429199219e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-planning-applications-granted took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-planning-applications-granted took 0.3057677745819092s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-planning-applications-granted took 0.020995616912841797s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-planning-applications-granted took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-planning-applications-granted took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-planning-applications-granted took 4.458427429199219e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-planning-applications-granted took 1.4066696166992188e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-planning-applications-granted took 2.610401153564453s
Availability | SPARQL endpoint availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 7.939338684082031e-05s
Availability | VoID file availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0004267692565917969s
Completeness | Calculation of interlinking completeness for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.28978657722473145s
Reputation | Calculation of the PageRank for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.020717620849609375s
Interlinking | Calculation of Degree of Connection for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 5.1975250244140625e-05s
Believability | Calculation of trust value for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.0251998901367188e-05s
INFO | --- Analysis for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.441162347793579s
Availability | SPARQL endpoint availability check for opendatacommunities-net-additional-dwellings took 4.57763671875e-05s
Availability | VoID file availability check for opendatacommunities-net-additional-dwellings took 0.0003561973571777344s
Completeness | Calculation of interlinking completeness for opendatacommunities-net-additional-dwellings took 0.2747647762298584s
Reputation | Calculation of the PageRank for opendatacommunities-net-additional-dwellings took 0.021208763122558594s
Interlinking | Calculation of Degree of Connection for opendatacommunities-net-additional-dwellings took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-net-additional-dwellings took 0.0008270740509033203s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-net-additional-dwellings took 4.839897155761719e-05s
Believability | Calculation of trust value for opendatacommunities-net-additional-dwellings took 1.4781951904296875e-05s
INFO | --- Analysis for opendatacommunities-net-additional-dwellings took 4.436819553375244s
Availability | SPARQL endpoint availability check for opendatacommunities-service-expenditure took 8.7738037109375e-05s
Availability | VoID file availability check for opendatacommunities-service-expenditure took 0.0007188320159912109s
Completeness | Calculation of interlinking completeness for opendatacommunities-service-expenditure took 0.2770993709564209s
Reputation | Calculation of the PageRank for opendatacommunities-service-expenditure took 0.021078824996948242s
Interlinking | Calculation of Degree of Connection for opendatacommunities-service-expenditure took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for opendatacommunities-service-expenditure took 0.000820159912109375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-service-expenditure took 4.315376281738281e-05s
Believability | Calculation of trust value for opendatacommunities-service-expenditure took 1.0013580322265625e-05s
INFO | --- Analysis for opendatacommunities-service-expenditure took 4.174707889556885s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0006601810455322266s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.3117809295654297s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.020635366439819336s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.8160552978515625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.4066696166992188e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.034322738647461s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 9.274482727050781e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0007135868072509766s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.3114168643951416s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.020583629608154297s
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.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.5299530029296875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.5020370483398438e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.189059019088745s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 5.555152893066406e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0006654262542724609s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.3308553695678711s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.021581411361694336s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.00089263916015625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 5.2928924560546875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.3828277587890625e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 3.9365758895874023s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0007441043853759766s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.3096024990081787s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.02098703384399414s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.982948303222656e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.0013580322265625e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.95781946182251s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.00010395050048828125s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0004296302795410156s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.29297947883605957s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.020968198776245117s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.458427429199219e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.0013580322265625e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.054241895675659s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 9.036064147949219e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0006778240203857422s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.28813743591308594s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.02216053009033203s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0007982254028320312s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.744529724121094e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.4543533325195312e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 6.472442626953125s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 8.916854858398438e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0004189014434814453s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.28157758712768555s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.02091217041015625s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 5.626678466796875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.430511474609375e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 5.236654996871948s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.673004150390625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.00043654441833496094s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.3074455261230469s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.02130603790283203s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0007998943328857422s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 5.340576171875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.3828277587890625e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 3.823580265045166s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 5.459785461425781e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0005888938903808594s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.2968268394470215s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.020792245864868164s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.220008850097656e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.4781951904296875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 3.9913723468780518s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 9.799003601074219e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007879734039306641s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.3300342559814453s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.020968914031982422s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.76837158203125e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 1.4066696166992188e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 3.990186929702759s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 5.8650970458984375e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0006968975067138672s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.32141900062561035s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.021381616592407227s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0008370876312255859s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 5.364418029785156e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.0967254638671875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 3.931972026824951s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.553794860839844e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.00033092498779296875s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.321291446685791s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.02062511444091797s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 5.125999450683594e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.0251998901367188e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 2.7042510509490967s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.5299530029296875e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0002918243408203125s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.2693600654602051s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.020809412002563477s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.76837158203125e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.1682510375976562e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 2.630967378616333s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 4.482269287109375e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0007314682006835938s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-housing-starts took 0.30273938179016113s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-housing-starts took 0.02073192596435547s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-housing-starts took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-housing-starts took 4.935264587402344e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-housing-starts took 1.4543533325195312e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-housing-starts took 4.911657810211182s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.38690185546875e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0006635189056396484s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.3090674877166748s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.02079606056213379s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.649162292480469e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.4543533325195312e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 3.761781930923462s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 9.059906005859375e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0008080005645751953s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-troubled-families took 0.33060479164123535s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-troubled-families took 0.02225184440612793s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-troubled-families took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-troubled-families took 4.887580871582031e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-troubled-families took 1.5020370483398438e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-troubled-families took 4.504615783691406s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 8.821487426757812e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0005695819854736328s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.2874484062194824s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.022621870040893555s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.887580871582031e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 9.298324584960938e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 3.3858888149261475s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 5.14984130859375e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0007386207580566406s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.32850217819213867s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0206756591796875s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 5.0067901611328125e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.52587890625e-05s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 3.8971564769744873s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 9.1552734375e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0007011890411376953s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.28924059867858887s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.024542570114135742s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0011758804321289062s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 5.817413330078125e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.4543533325195312e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 3.8432514667510986s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.00010466575622558594s
Availability | VoID file availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0006978511810302734s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.3461177349090576s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.020877599716186523s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 4.1484832763671875e-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.354397535324097s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-worthwhile-mean took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-worthwhile-mean took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-worthwhile-mean took 0.2913799285888672s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-worthwhile-mean took 0.020641326904296875s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-worthwhile-mean took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-worthwhile-mean took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-worthwhile-mean took 4.100799560546875e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-worthwhile-mean took 1.4781951904296875e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-worthwhile-mean took 3.1208832263946533s
Availability | SPARQL endpoint availability check for Open Data of Ecuador took 3.998443365097046s
Availability | VoID file availability check for Open Data of Ecuador took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for Open Data of Ecuador took 0.2760345935821533s
Reputation | Calculation of the PageRank for Open Data of Ecuador took 0.022105932235717773s
Interlinking | Calculation of Degree of Connection for Open Data of Ecuador took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Data of Ecuador took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Open Data of Ecuador took 9.059906005859375e-05s
Believability | Calculation of trust value for Open Data of Ecuador took 1.5020370483398438e-05s
INFO | --- Analysis for opendataec took 10.538445234298706s
Availability | SPARQL endpoint availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 9.131431579589844e-05s
Availability | VoID file availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0006074905395507812s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.2840757369995117s
Reputation | Calculation of the PageRank for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.020745277404785156s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-education-pupils-by-school-and-datazone took 4.38690185546875e-05s
Believability | Calculation of trust value for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.4781951904296875e-05s
INFO | --- Analysis for opendatascotland-graph-education-pupils-by-school-and-datazone took 4.8940722942352295s
Availability | SPARQL endpoint availability check for opendatascotland-graph-simd-rank took 4.482269287109375e-05s
Availability | VoID file availability check for opendatascotland-graph-simd-rank took 0.0007762908935546875s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-simd-rank took 0.3060421943664551s
Reputation | Calculation of the PageRank for opendatascotland-graph-simd-rank took 0.020803451538085938s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-simd-rank took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-simd-rank took 0.0007851123809814453s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-simd-rank took 4.5299530029296875e-05s
Believability | Calculation of trust value for opendatascotland-graph-simd-rank took 1.4781951904296875e-05s
INFO | --- Analysis for opendatascotland-graph-simd-rank took 3.8449575901031494s
Availability | SPARQL endpoint availability check for opendatascotland-simd-crime-rank took 9.179115295410156e-05s
Availability | VoID file availability check for opendatascotland-simd-crime-rank took 0.0005140304565429688s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-crime-rank took 0.3136265277862549s
Reputation | Calculation of the PageRank for opendatascotland-simd-crime-rank took 0.02361321449279785s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-crime-rank took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-crime-rank took 0.0012476444244384766s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-crime-rank took 5.8650970458984375e-05s
Believability | Calculation of trust value for opendatascotland-simd-crime-rank took 1.430511474609375e-05s
INFO | --- Analysis for opendatascotland-simd-crime-rank took 3.7684597969055176s
Availability | SPARQL endpoint availability check for opendatascotland-simd-education-rank took 6.651878356933594e-05s
Availability | VoID file availability check for opendatascotland-simd-education-rank took 0.000560760498046875s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-education-rank took 0.29580140113830566s
Reputation | Calculation of the PageRank for opendatascotland-simd-education-rank took 0.02156662940979004s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-education-rank took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-education-rank took 0.0009086132049560547s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-education-rank took 4.792213439941406e-05s
Believability | Calculation of trust value for opendatascotland-simd-education-rank took 1.0967254638671875e-05s
INFO | --- Analysis for opendatascotland-simd-education-rank took 3.608328104019165s
Availability | SPARQL endpoint availability check for opendatascotland-simd-employment-rank took 6.246566772460938e-05s
Availability | VoID file availability check for opendatascotland-simd-employment-rank took 0.0003707408905029297s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-employment-rank took 0.3145308494567871s
Reputation | Calculation of the PageRank for opendatascotland-simd-employment-rank took 0.020669221878051758s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-employment-rank took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-employment-rank took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-employment-rank took 4.291534423828125e-05s
Believability | Calculation of trust value for opendatascotland-simd-employment-rank took 1.4543533325195312e-05s
INFO | --- Analysis for opendatascotland-simd-employment-rank took 3.7031872272491455s
Availability | SPARQL endpoint availability check for opendatascotland-simd-geographic-access-rank took 4.601478576660156e-05s
Availability | VoID file availability check for opendatascotland-simd-geographic-access-rank took 0.0006072521209716797s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-geographic-access-rank took 0.3207540512084961s
Reputation | Calculation of the PageRank for opendatascotland-simd-geographic-access-rank took 0.023111581802368164s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-geographic-access-rank took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-geographic-access-rank took 0.0007958412170410156s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-geographic-access-rank took 4.649162292480469e-05s
Believability | Calculation of trust value for opendatascotland-simd-geographic-access-rank took 3.337860107421875e-05s
INFO | --- Analysis for opendatascotland-simd-geographic-access-rank took 3.9238688945770264s
Availability | SPARQL endpoint availability check for opendatascotland-simd-health-rank took 8.678436279296875e-05s
Availability | VoID file availability check for opendatascotland-simd-health-rank took 0.0005986690521240234s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-health-rank took 0.33282899856567383s
Reputation | Calculation of the PageRank for opendatascotland-simd-health-rank took 0.02091836929321289s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-health-rank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-health-rank took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-health-rank took 4.291534423828125e-05s
Believability | Calculation of trust value for opendatascotland-simd-health-rank took 1.52587890625e-05s
INFO | --- Analysis for opendatascotland-simd-health-rank took 3.7037627696990967s
Availability | SPARQL endpoint availability check for opendatascotland-simd-housing-rank took 9.822845458984375e-05s
Availability | VoID file availability check for opendatascotland-simd-housing-rank took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-housing-rank took 0.3228628635406494s
Reputation | Calculation of the PageRank for opendatascotland-simd-housing-rank took 0.02265334129333496s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-housing-rank took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-housing-rank took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-housing-rank took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatascotland-simd-housing-rank took 1.4781951904296875e-05s
INFO | --- Analysis for opendatascotland-simd-housing-rank took 3.6796462535858154s
Availability | SPARQL endpoint availability check for opendatascotland-simd-income-rank took 6.008148193359375e-05s
Availability | VoID file availability check for opendatascotland-simd-income-rank took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-income-rank took 0.2789163589477539s
Reputation | Calculation of the PageRank for opendatascotland-simd-income-rank took 0.02108168601989746s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-income-rank took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-income-rank took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-income-rank took 4.291534423828125e-05s
Believability | Calculation of trust value for opendatascotland-simd-income-rank took 1.52587890625e-05s
INFO | --- Analysis for opendatascotland-simd-income-rank took 2.701409339904785s
Availability | SPARQL endpoint availability check for OpenLink Software LOD Cache took 30.523061513900757s
Availability | VoID file availability check for OpenLink Software LOD Cache took 0.0005357265472412109s
Completeness | Calculation of interlinking completeness for OpenLink Software LOD Cache took 0.29927515983581543s
Reputation | Calculation of the PageRank for OpenLink Software LOD Cache took 0.0207064151763916s
Interlinking | Calculation of Degree of Connection for OpenLink Software LOD Cache took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for OpenLink Software LOD Cache took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for OpenLink Software LOD Cache took 4.076957702636719e-05s
Believability | Calculation of trust value for OpenLink Software LOD Cache took 1.4781951904296875e-05s
INFO | --- Analysis for openlink-lod-cache took 64.22527432441711s
Availability | SPARQL endpoint availability check for openlinksw dataspaces took 9.036064147949219e-05s
Availability | VoID file availability check for openlinksw dataspaces took 0.0008156299591064453s
Completeness | Calculation of interlinking completeness for openlinksw dataspaces took 0.30236387252807617s
Reputation | Calculation of the PageRank for openlinksw dataspaces took 0.020891904830932617s
Interlinking | Calculation of Degree of Connection for openlinksw dataspaces took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for openlinksw dataspaces took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for openlinksw dataspaces took 0.00010251998901367188s
Believability | Calculation of trust value for openlinksw dataspaces took 1.1444091796875e-05s
INFO | --- Analysis for openlinksw-dataspaces took 3.249403953552246s
Availability | SPARQL endpoint availability check for Openly Local :: Making Local Government More Transparent took 4.57763671875e-05s
Availability | VoID file availability check for Openly Local :: Making Local Government More Transparent took 0.0007886886596679688s
Completeness | Calculation of interlinking completeness for Openly Local :: Making Local Government More Transparent took 0.2983567714691162s
Reputation | Calculation of the PageRank for Openly Local :: Making Local Government More Transparent took 0.020737648010253906s
Interlinking | Calculation of Degree of Connection for Openly Local :: Making Local Government More Transparent took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Openly Local :: Making Local Government More Transparent took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Openly Local :: Making Local Government More Transparent took 9.703636169433594e-05s
Believability | Calculation of trust value for Openly Local :: Making Local Government More Transparent took 6.198883056640625e-06s
INFO | --- Analysis for openlylocal took 6.736680269241333s
Availability | SPARQL endpoint availability check for OpenMobileNetwork took 1.947394609451294s
Availability | VoID file availability check for OpenMobileNetwork took 0.0007350444793701172s
Completeness | Calculation of interlinking completeness for OpenMobileNetwork took 0.3199748992919922s
Reputation | Calculation of the PageRank for OpenMobileNetwork took 0.020563840866088867s
Interlinking | Calculation of Degree of Connection for OpenMobileNetwork took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenMobileNetwork took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for OpenMobileNetwork took 7.700920104980469e-05s
Believability | Calculation of trust value for OpenMobileNetwork took 1.52587890625e-05s
INFO | --- Analysis for openmobilenetwork took 6.145752191543579s
Availability | SPARQL endpoint availability check for Ordnance Survey Linked Data took 0.7329285144805908s
Availability | VoID file availability check for Ordnance Survey Linked Data took 0.0005905628204345703s
Completeness | Calculation of interlinking completeness for Ordnance Survey Linked Data took 0.28759241104125977s
Reputation | Calculation of the PageRank for Ordnance Survey Linked Data took 0.02055835723876953s
Interlinking | Calculation of Degree of Connection for Ordnance Survey Linked Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Ordnance Survey Linked Data took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey Linked Data took 0.00010609626770019531s
Believability | Calculation of trust value for Ordnance Survey Linked Data took 1.4066696166992188e-05s
INFO | --- Analysis for ordnance-survey-linked-data took 5.166997194290161s
Availability | SPARQL endpoint availability check for oreilly took 4.38690185546875e-05s
Availability | VoID file availability check for oreilly took 0.0006604194641113281s
Completeness | Calculation of interlinking completeness for oreilly took 0.30610227584838867s
Reputation | Calculation of the PageRank for oreilly took 0.021773815155029297s
Interlinking | Calculation of Degree of Connection for oreilly took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for oreilly took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for oreilly took 5.817413330078125e-05s
Believability | Calculation of trust value for oreilly took 1.52587890625e-05s
INFO | --- Analysis for oreilly took 5.207988739013672s
Availability | SPARQL endpoint availability check for Medicine and Natural Product Data took 3.399146556854248s
Availability | VoID file availability check for Medicine and Natural Product Data took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for Medicine and Natural Product Data took 0.28494906425476074s
Reputation | Calculation of the PageRank for Medicine and Natural Product Data took 0.02085280418395996s
Interlinking | Calculation of Degree of Connection for Medicine and Natural Product Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Medicine and Natural Product Data took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Medicine and Natural Product Data took 3.62396240234375e-05s
Believability | Calculation of trust value for Medicine and Natural Product Data took 1.2636184692382812e-05s
INFO | --- Analysis for Organchem-Data took 7.529818534851074s
Availability | SPARQL endpoint availability check for Organic Edunet Linked Open Data took 0.06219482421875s
Availability | VoID file availability check for Organic Edunet Linked Open Data took 0.0005819797515869141s
Completeness | Calculation of interlinking completeness for Organic Edunet Linked Open Data took 0.2854888439178467s
Reputation | Calculation of the PageRank for Organic Edunet Linked Open Data took 0.02078104019165039s
Interlinking | Calculation of Degree of Connection for Organic Edunet Linked Open Data took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Organic Edunet Linked Open Data took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Organic Edunet Linked Open Data took 7.081031799316406e-05s
Believability | Calculation of trust value for Organic Edunet Linked Open Data took 1.0013580322265625e-05s
INFO | --- Analysis for organic-edunet took 9.046275615692139s
Availability | SPARQL endpoint availability check for Open Research Knowledge Graph (ORKG) took 0.5250663757324219s
Availability | VoID file availability check for Open Research Knowledge Graph (ORKG) took 0.0006816387176513672s
Extra | Recovery of all triples for Open Research Knowledge Graph (ORKG) took 5.96600866317749s
Performance | Total latancy measurement for Open Research Knowledge Graph (ORKG) took 0.7039532661437988s
Amount of data | Number of triples check for Open Research Knowledge Graph (ORKG) took 0.18324065208435059s
Interoperability | New terms check for Open Research Knowledge Graph (ORKG) took 1.8080215454101562s
Versatility | Languages check for Open Research Knowledge Graph (ORKG) took 5.400381088256836s
Interpretability | Number of blank nodes check for Open Research Knowledge Graph (ORKG) took 0.1608278751373291s
Interpretability | RDF structures check for Open Research Knowledge Graph (ORKG) took 0.26593756675720215s
Versatility | Serialization formats check for Open Research Knowledge Graph (ORKG) took 0.15585780143737793s
Availability | RDF dump link check for Open Research Knowledge Graph (ORKG) took 0.15819764137268066s
License | MR license check for Open Research Knowledge Graph (ORKG) took 0.12261772155761719s
License | HR license check for Open Research Knowledge Graph (ORKG) took 3.1030282974243164s
Amount of data | Number of property check for Open Research Knowledge Graph (ORKG) took 0.16533994674682617s
Understandability | Number of label check for Open Research Knowledge Graph (ORKG) took 0.19755959510803223s
Understandability | URI regex check for Open Research Knowledge Graph (ORKG) took 0.24236345291137695s
Understandability | Vocabs check for Open Research Knowledge Graph (ORKG) took 0.16029143333435059s
Verifiability | Authors check for Open Research Knowledge Graph (ORKG) took 0.1616220474243164s
Verifiability | Publishers check for Open Research Knowledge Graph (ORKG) took 0.16406035423278809s
Performance | Throughput check for Open Research Knowledge Graph (ORKG) took 10.548290491104126s
Amount of data | Check the number of entities for Open Research Knowledge Graph (ORKG) took 7.486343383789062e-05s
Verifiability | Contribs. check for Open Research Knowledge Graph (ORKG) took 0.1449892520904541s
Interlinking | sameAs chians check for Open Research Knowledge Graph (ORKG) took 0.13616299629211426s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.15035271644592285s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.14371275901794434s
Timeliness | dataset update frequency check for Open Research Knowledge Graph (ORKG) took 0.15265631675720215s
Currency | Creation date check for Open Research Knowledge Graph (ORKG) took 0.399036169052124s
Currency | Modification date check for Open Research Knowledge Graph (ORKG) took 0.40317368507385254s
Rep.Conc. | URIs length for Open Research Knowledge Graph (ORKG) took 3.715399980545044s
Interoperability | New vocabularies check for Open Research Knowledge Graph (ORKG) took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for Open Research Knowledge Graph (ORKG) took 0.15987396240234375s
Accuracy | Check Functional Property for Open Research Knowledge Graph (ORKG) took 0.2510247230529785s
Accuracy | Check Inverse Functional Property for Open Research Knowledge Graph (ORKG) took 0.222944974899292s
Accuracy | Check Empty annotation labels for Open Research Knowledge Graph (ORKG) took 2.4140372276306152s
Accuracy | Check White space in annotation for Open Research Knowledge Graph (ORKG) took 0.29679298400878906s
Accuracy | Check Datatype consistency for Open Research Knowledge Graph (ORKG) took 0.28534531593322754s
Consistency | Disjoint class check for Open Research Knowledge Graph (ORKG) took 0.18627333641052246s
Consistency | Check Misplaced properties for Open Research Knowledge Graph (ORKG) took 1.3204047679901123s
Consistency | Misplaced classes for Open Research Knowledge Graph (ORKG) took 0.9325323104858398s
Consistency | Check Ontology hijacking for Open Research Knowledge Graph (ORKG) took 3.4119086265563965s
Consistency | Check Invalid usage of undefined classes for Open Research Knowledge Graph (ORKG) took 1.4851267337799072s
Consistency | Check Invalid usage of undefined properties for Open Research Knowledge Graph (ORKG) took 2.3195509910583496s
Conciseness | Check Extensional conciseness for Open Research Knowledge Graph (ORKG) took 0.29369544982910156s
Conciseness | Check Intensional conciseness for Open Research Knowledge Graph (ORKG) took 0.16480088233947754s
Security | Sign check for Open Research Knowledge Graph (ORKG) took 0.14644265174865723s
Availability | Check URIs Dereferenciability for Open Research Knowledge Graph (ORKG) took 2021.1086149215698s
Completeness | Calculation of interlinking completeness for Open Research Knowledge Graph (ORKG) took 0.5008952617645264s
Reputation | Calculation of the PageRank for Open Research Knowledge Graph (ORKG) took 0.025516748428344727s
Interlinking | Calculation of Degree of Connection for Open Research Knowledge Graph (ORKG) took 2.5272369384765625e-05s
Interlinking | Calculation of Centrality for Open Research Knowledge Graph (ORKG) took 0.0007851123809814453s
Interlinking | Calculation of Clustering coefficient for Open Research Knowledge Graph (ORKG) took 2.2172927856445312e-05s
Interoperability | Check the re-using of existing vocabs for Open Research Knowledge Graph (ORKG) took 2.6226043701171875e-06s
Believability | Calculation of trust value for Open Research Knowledge Graph (ORKG) took 1.5020370483398438e-05s
INFO | --- Analysis for orkg took 2252.3432681560516s
Availability | SPARQL endpoint availability check for The Orlando Women's Writing Linked Open Data Set took 2.0471982955932617s
Availability | VoID file availability check for The Orlando Women's Writing Linked Open Data Set took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for The Orlando Women's Writing Linked Open Data Set took 0.28012895584106445s
Reputation | Calculation of the PageRank for The Orlando Women's Writing Linked Open Data Set took 0.020946025848388672s
Interlinking | Calculation of Degree of Connection for The Orlando Women's Writing Linked Open Data Set took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for The Orlando Women's Writing Linked Open Data Set took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for The Orlando Women's Writing Linked Open Data Set took 9.822845458984375e-05s
Believability | Calculation of trust value for The Orlando Women's Writing Linked Open Data Set took 1.0251998901367188e-05s
INFO | --- Analysis for orlando-womens-writing-linked-open-data-set took 28.183310747146606s
Availability | SPARQL endpoint availability check for OSM Semantic Network took 1.6235191822052002s
Availability | VoID file availability check for OSM Semantic Network took 0.0006406307220458984s
Completeness | Calculation of interlinking completeness for OSM Semantic Network took 0.2837345600128174s
Reputation | Calculation of the PageRank for OSM Semantic Network took 0.020696640014648438s
Interlinking | Calculation of Degree of Connection for OSM Semantic Network took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for OSM Semantic Network took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for OSM Semantic Network took 4.220008850097656e-05s
Believability | Calculation of trust value for OSM Semantic Network took 1.3828277587890625e-05s
INFO | --- Analysis for osm-semantic-network took 8.60800051689148s
Availability | SPARQL endpoint availability check for Open Transport Map @PSNC took 0.3264634609222412s
Availability | VoID file availability check for Open Transport Map @PSNC took 0.00052642822265625s
Extra | Recovery of all triples for Open Transport Map @PSNC took 116.61662530899048s
Performance | Total latancy measurement for Open Transport Map @PSNC took 1.1873195171356201s
Amount of data | Number of triples check for Open Transport Map @PSNC took 9.206365823745728s
Interoperability | New terms check for Open Transport Map @PSNC took 14.202394008636475s
Versatility | Languages check for Open Transport Map @PSNC took 300.1804230213165s
Interpretability | Number of blank nodes check for Open Transport Map @PSNC took 2.488133430480957s
Interpretability | RDF structures check for Open Transport Map @PSNC took 0.28885793685913086s
Versatility | Serialization formats check for Open Transport Map @PSNC took 6.856596946716309s
Availability | RDF dump link check for Open Transport Map @PSNC took 0.2899627685546875s
License | MR license check for Open Transport Map @PSNC took 0.60247802734375s
License | HR license check for Open Transport Map @PSNC took 300.2333402633667s
Amount of data | Number of property check for Open Transport Map @PSNC took 0.198469877243042s
Understandability | Number of label check for Open Transport Map @PSNC took 2.90220308303833s
Understandability | URI regex check for Open Transport Map @PSNC took 1.0780658721923828s
Understandability | Vocabs check for Open Transport Map @PSNC took 0.5793325901031494s
Verifiability | Authors check for Open Transport Map @PSNC took 0.20458459854125977s
Verifiability | Publishers check for Open Transport Map @PSNC took 0.2458972930908203s
Performance | Throughput check for Open Transport Map @PSNC took 10.964366436004639s
Amount of data | Check the number of entities for Open Transport Map @PSNC took 7.867813110351562e-05s
Verifiability | Contribs. check for Open Transport Map @PSNC took 0.20293641090393066s
Interlinking | sameAs chians check for Open Transport Map @PSNC took 0.20807766914367676s
Interlinking | skos check for Open Transport Map @PSNC took 0.4365661144256592s
Interlinking | skos check for Open Transport Map @PSNC took 0.41579461097717285s
Timeliness | dataset update frequency check for Open Transport Map @PSNC took 4.743804454803467s
Currency | Creation date check for Open Transport Map @PSNC took 0.45678162574768066s
Currency | Modification date check for Open Transport Map @PSNC took 0.2367103099822998s
Rep.Conc. | URIs length for Open Transport Map @PSNC took 159.67562007904053s
Interoperability | New vocabularies check for Open Transport Map @PSNC took 1.3589859008789062e-05s
Consistency | Deprecated classes/propertiers check for Open Transport Map @PSNC took 0.18610095977783203s
Accuracy | Check Functional Property for Open Transport Map @PSNC took 0.40342164039611816s
Accuracy | Check Inverse Functional Property for Open Transport Map @PSNC took 0.4358384609222412s
Accuracy | Check Empty annotation labels for Open Transport Map @PSNC took 41.659693479537964s
Accuracy | Check White space in annotation for Open Transport Map @PSNC took 2.709808111190796s
Accuracy | Check Datatype consistency for Open Transport Map @PSNC took 2.8234317302703857s
Consistency | Disjoint class check for Open Transport Map @PSNC took 0.2141869068145752s
Consistency | Check Misplaced properties for Open Transport Map @PSNC took 87.01443576812744s
Consistency | Misplaced classes for Open Transport Map @PSNC took 8.596123933792114s
Consistency | Check Ontology hijacking for Open Transport Map @PSNC took 35.118218660354614s
Consistency | Check Invalid usage of undefined classes for Open Transport Map @PSNC took 1.6186139583587646s
Consistency | Check Invalid usage of undefined properties for Open Transport Map @PSNC took 89.20671653747559s
Conciseness | Check Extensional conciseness for Open Transport Map @PSNC took 2.773587226867676s
Conciseness | Check Intensional conciseness for Open Transport Map @PSNC took 0.5463318824768066s
Security | Sign check for Open Transport Map @PSNC took 1.4156334400177002s
Availability | Check URIs Dereferenciability for Open Transport Map @PSNC took 10.45122241973877s
Completeness | Calculation of interlinking completeness for Open Transport Map @PSNC took 0.5745069980621338s
Reputation | Calculation of the PageRank for Open Transport Map @PSNC took 0.025242328643798828s
Interlinking | Calculation of Degree of Connection for Open Transport Map @PSNC took 2.4080276489257812e-05s
Interlinking | Calculation of Centrality for Open Transport Map @PSNC took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Open Transport Map @PSNC took 4.4345855712890625e-05s
Interoperability | Check the re-using of existing vocabs for Open Transport Map @PSNC took 2.384185791015625e-06s
Believability | Calculation of trust value for Open Transport Map @PSNC took 1.049041748046875e-05s
INFO | --- Analysis for OTM took 2292.86438536644s
Availability | SPARQL endpoint availability check for Pali English Lexicon took 1.7096302509307861s
Availability | VoID file availability check for Pali English Lexicon took 0.0008044242858886719s
Completeness | Calculation of interlinking completeness for Pali English Lexicon took 0.3240702152252197s
Reputation | Calculation of the PageRank for Pali English Lexicon took 0.02144932746887207s
Interlinking | Calculation of Degree of Connection for Pali English Lexicon took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Pali English Lexicon took 0.0008261203765869141s
Interlinking | Calculation of Clustering coefficient for Pali English Lexicon took 3.790855407714844e-05s
Believability | Calculation of trust value for Pali English Lexicon took 1.4066696166992188e-05s
INFO | --- Analysis for pali-english-lexicon took 8.304135799407959s
Availability | SPARQL endpoint availability check for PanLex took 2.0037453174591064s
Availability | VoID file availability check for PanLex took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for PanLex took 0.2985992431640625s
Reputation | Calculation of the PageRank for PanLex took 0.02104020118713379s
Interlinking | Calculation of Degree of Connection for PanLex took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for PanLex took 0.0008969306945800781s
Interlinking | Calculation of Clustering coefficient for PanLex took 9.989738464355469e-05s
Believability | Calculation of trust value for PanLex took 1.239776611328125e-05s
INFO | --- Analysis for panlex took 4.735961437225342s
Availability | SPARQL endpoint availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 8.726119995117188e-05s
Availability | VoID file availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0005512237548828125s
Completeness | Calculation of interlinking completeness for Parole/Simple 'lexinfo' Ontology & lexicons took 0.3162984848022461s
Reputation | Calculation of the PageRank for Parole/Simple 'lexinfo' Ontology & lexicons took 0.02258753776550293s
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.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Parole/Simple 'lexinfo' Ontology & lexicons took 4.1484832763671875e-05s
Believability | Calculation of trust value for Parole/Simple 'lexinfo' Ontology & lexicons took 1.4543533325195312e-05s
INFO | --- Analysis for parole-simple-lexinfo-ontology-lexicons took 5.411354064941406s
Availability | SPARQL endpoint availability check for patents.data.gov.uk took 0.06253647804260254s
Availability | VoID file availability check for patents.data.gov.uk took 0.0005438327789306641s
Completeness | Calculation of interlinking completeness for patents.data.gov.uk took 0.26688528060913086s
Reputation | Calculation of the PageRank for patents.data.gov.uk took 0.020790576934814453s
Interlinking | Calculation of Degree of Connection for patents.data.gov.uk took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for patents.data.gov.uk took 0.0010597705841064453s
Interlinking | Calculation of Clustering coefficient for patents.data.gov.uk took 7.104873657226562e-05s
Believability | Calculation of trust value for patents.data.gov.uk took 1.0967254638671875e-05s
INFO | --- Analysis for patents-data-gov-uk took 2.690908193588257s
Availability | SPARQL endpoint availability check for PDEV-Lemon took 4.57763671875e-05s
Availability | VoID file availability check for PDEV-Lemon took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for PDEV-Lemon took 0.28676772117614746s
Reputation | Calculation of the PageRank for PDEV-Lemon took 0.02077031135559082s
Interlinking | Calculation of Degree of Connection for PDEV-Lemon took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for PDEV-Lemon took 0.0007927417755126953s
Interlinking | Calculation of Clustering coefficient for PDEV-Lemon took 4.1961669921875e-05s
Believability | Calculation of trust value for PDEV-Lemon took 9.059906005859375e-06s
INFO | --- Analysis for pdev-lemon took 4.0556933879852295s
Availability | SPARQL endpoint availability check for pdevlemon took 4.482269287109375e-05s
Availability | VoID file availability check for pdevlemon took 0.0005834102630615234s
Completeness | Calculation of interlinking completeness for pdevlemon took 0.2812955379486084s
Reputation | Calculation of the PageRank for pdevlemon took 0.020586013793945312s
Interlinking | Calculation of Degree of Connection for pdevlemon took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for pdevlemon took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for pdevlemon took 3.123283386230469e-05s
Believability | Calculation of trust value for pdevlemon took 1.049041748046875e-05s
INFO | --- Analysis for pdevlemon took 3.2564446926116943s
Availability | SPARQL endpoint availability check for PeriodO Period Gazetteer took 4.410743713378906e-05s
Availability | VoID file availability check for PeriodO Period Gazetteer took 0.0008878707885742188s
Completeness | Calculation of interlinking completeness for PeriodO Period Gazetteer took 0.3336608409881592s
Reputation | Calculation of the PageRank for PeriodO Period Gazetteer took 0.020633697509765625s
Interlinking | Calculation of Degree of Connection for PeriodO Period Gazetteer took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for PeriodO Period Gazetteer took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for PeriodO Period Gazetteer took 8.344650268554688e-05s
Believability | Calculation of trust value for PeriodO Period Gazetteer took 1.5020370483398438e-05s
INFO | --- Analysis for periodo took 18.828209161758423s
Availability | SPARQL endpoint availability check for Personal_Homepages took 8.749961853027344e-05s
Availability | VoID file availability check for Personal_Homepages took 0.0005869865417480469s
Completeness | Calculation of interlinking completeness for Personal_Homepages took 0.29295873641967773s
Reputation | Calculation of the PageRank for Personal_Homepages took 0.0206451416015625s
Interlinking | Calculation of Degree of Connection for Personal_Homepages took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Personal_Homepages took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Personal_Homepages took 0.00039315223693847656s
Believability | Calculation of trust value for Personal_Homepages took 1.5497207641601562e-05s
INFO | --- Analysis for personal-homepages took 2.60038423538208s
Availability | SPARQL endpoint availability check for Ontology of University People took 8.821487426757812e-05s
Availability | VoID file availability check for Ontology of University People took 0.0004086494445800781s
Completeness | Calculation of interlinking completeness for Ontology of University People took 0.32398080825805664s
Reputation | Calculation of the PageRank for Ontology of University People took 0.020920276641845703s
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.0007963180541992188s
Interlinking | Calculation of Clustering coefficient for Ontology of University People took 4.100799560546875e-05s
Believability | Calculation of trust value for Ontology of University People took 1.430511474609375e-05s
INFO | --- Analysis for PersonOnto took 2.6994292736053467s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 3.860262155532837s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0003962516784667969s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.3159620761871338s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.020840883255004883s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0008072853088378906s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.4543533325195312e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.430511474609375e-05s
INFO | --- Analysis for PFKHS took 8.165103197097778s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 2.0407681465148926s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0006244182586669922s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.27770185470581055s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.020978689193725586s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.3828277587890625e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 9.298324584960938e-06s
INFO | --- Analysis for PFRPPH took 7.887346029281616s
Availability | SPARQL endpoint availability check for PGxLOD took 30.2669575214386s
Availability | VoID file availability check for PGxLOD took 0.0006222724914550781s
Completeness | Calculation of interlinking completeness for PGxLOD took 0.2897019386291504s
Reputation | Calculation of the PageRank for PGxLOD took 0.02221536636352539s
Interlinking | Calculation of Degree of Connection for PGxLOD took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for PGxLOD took 0.0008282661437988281s
Interlinking | Calculation of Clustering coefficient for PGxLOD took 5.6743621826171875e-05s
Believability | Calculation of trust value for PGxLOD took 1.4066696166992188e-05s
INFO | --- Analysis for PGxLOD took 73.12206435203552s
Availability | SPARQL endpoint availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.9977834224700928s
Availability | VoID file availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0004086494445800781s
Completeness | Calculation of interlinking completeness for Phonetics Information Base and Lexicon (PHOIBLE) took 0.32859349250793457s
Reputation | Calculation of the PageRank for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0211336612701416s
Interlinking | Calculation of Degree of Connection for Phonetics Information Base and Lexicon (PHOIBLE) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Phonetics Information Base and Lexicon (PHOIBLE) took 4.649162292480469e-05s
Believability | Calculation of trust value for Phonetics Information Base and Lexicon (PHOIBLE) took 1.71661376953125e-05s
INFO | --- Analysis for phoible took 4.775172710418701s
Availability | SPARQL endpoint availability check for Parallel ice sheet model took 4.458427429199219e-05s
Availability | VoID file availability check for Parallel ice sheet model took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for Parallel ice sheet model took 0.2899665832519531s
Reputation | Calculation of the PageRank for Parallel ice sheet model took 0.02107095718383789s
Interlinking | Calculation of Degree of Connection for Parallel ice sheet model took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Parallel ice sheet model took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for Parallel ice sheet model took 3.409385681152344e-05s
Believability | Calculation of trust value for Parallel ice sheet model took 1.0251998901367188e-05s
INFO | --- Analysis for PISM took 16.40247130393982s
Availability | SPARQL endpoint availability check for PlanetData Project Wiki took 8.96453857421875e-05s
Availability | VoID file availability check for PlanetData Project Wiki took 0.0005431175231933594s
Completeness | Calculation of interlinking completeness for PlanetData Project Wiki took 0.29973673820495605s
Reputation | Calculation of the PageRank for PlanetData Project Wiki took 0.0206146240234375s
Interlinking | Calculation of Degree of Connection for PlanetData Project Wiki took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for PlanetData Project Wiki took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for PlanetData Project Wiki took 9.298324584960938e-05s
Believability | Calculation of trust value for PlanetData Project Wiki took 1.430511474609375e-05s
INFO | --- Analysis for planetdata-project-wiki took 2.6949856281280518s
Availability | SPARQL endpoint availability check for digitized plant specimen took 0.9838318824768066s
Availability | VoID file availability check for digitized plant specimen took 0.0005393028259277344s
Completeness | Calculation of interlinking completeness for digitized plant specimen took 0.30425167083740234s
Reputation | Calculation of the PageRank for digitized plant specimen took 0.020771265029907227s
Interlinking | Calculation of Degree of Connection for digitized plant specimen took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for digitized plant specimen took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for digitized plant specimen took 7.367134094238281e-05s
Believability | Calculation of trust value for digitized plant specimen took 9.5367431640625e-06s
INFO | --- Analysis for plant-specimen took 3.7476272583007812s
Availability | SPARQL endpoint availability check for Pleiades took 9.083747863769531e-05s
Availability | VoID file availability check for Pleiades took 0.0006144046783447266s
Completeness | Calculation of interlinking completeness for Pleiades took 0.3404073715209961s
Reputation | Calculation of the PageRank for Pleiades took 0.021147489547729492s
Interlinking | Calculation of Degree of Connection for Pleiades took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Pleiades took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for Pleiades took 9.226799011230469e-05s
Believability | Calculation of trust value for Pleiades took 1.0013580322265625e-05s
INFO | --- Analysis for pleiades took 14.180304050445557s
Availability | SPARQL endpoint availability check for podorozhnyk.com took 4.601478576660156e-05s
Availability | VoID file availability check for podorozhnyk.com took 0.0004527568817138672s
Completeness | Calculation of interlinking completeness for podorozhnyk.com took 0.2929370403289795s
Reputation | Calculation of the PageRank for podorozhnyk.com took 0.020787954330444336s
Interlinking | Calculation of Degree of Connection for podorozhnyk.com took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for podorozhnyk.com took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for podorozhnyk.com took 3.504753112792969e-05s
Believability | Calculation of trust value for podorozhnyk.com took 1.3828277587890625e-05s
INFO | --- Analysis for podorozhnyk took 3.3163435459136963s
Availability | SPARQL endpoint availability check for Poképédia took 4.9591064453125e-05s
Availability | VoID file availability check for Poképédia took 0.0003237724304199219s
Completeness | Calculation of interlinking completeness for Poképédia took 0.2789733409881592s
Reputation | Calculation of the PageRank for Poképédia took 0.020826339721679688s
Interlinking | Calculation of Degree of Connection for Poképédia took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Poképédia took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Poképédia took 8.058547973632812e-05s
Believability | Calculation of trust value for Poképédia took 9.059906005859375e-06s
INFO | --- Analysis for pokepedia-fr took 2.8417606353759766s
Availability | SPARQL endpoint availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 5.4836273193359375e-05s
Availability | VoID file availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0004215240478515625s
Completeness | Calculation of interlinking completeness for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.2767832279205322s
Reputation | Calculation of the PageRank for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.02060532569885254s
Interlinking | Calculation of Degree of Connection for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 7.891654968261719e-05s
Believability | Calculation of trust value for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.049041748046875e-05s
INFO | --- Analysis for polymath-virtual-library took 6.161067962646484s
Availability | SPARQL endpoint availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.3078014850616455s
Availability | VoID file availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0007207393646240234s
Extra | Recovery of all triples for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 10.777704000473022s
Performance | Total latancy measurement for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.606109619140625s
Amount of data | Number of triples check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.4494307041168213s
Interoperability | New terms check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.7354340553283691s
Versatility | Languages check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.4353382587432861s
Interpretability | Number of blank nodes check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.4465823173522949s
Interpretability | RDF structures check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1275322437286377s
Versatility | Serialization formats check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12692928314208984s
Availability | RDF dump link check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12429428100585938s
License | MR license check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12510299682617188s
License | HR license check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.6798553466796875s
Amount of data | Number of property check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11639833450317383s
Understandability | Number of label check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.17452383041381836s
Understandability | URI regex check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.2464916706085205s
Understandability | Vocabs check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.13185596466064453s
Verifiability | Authors check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.13303136825561523s
Verifiability | Publishers check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12468457221984863s
Performance | Throughput check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 10.829773664474487s
Amount of data | Check the number of entities for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 7.343292236328125e-05s
Verifiability | Contribs. check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12364912033081055s
Interlinking | sameAs chians check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12158656120300293s
Interlinking | skos check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12284231185913086s
Interlinking | skos check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12920022010803223s
Timeliness | dataset update frequency check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12190914154052734s
Currency | Creation date check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.23583054542541504s
Currency | Modification date check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.24280953407287598s
Rep.Conc. | URIs length for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 6.548198223114014s
Interoperability | New vocabularies check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12447500228881836s
Accuracy | Check Functional Property for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1196904182434082s
Accuracy | Check Inverse Functional Property for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12754535675048828s
Accuracy | Check Empty annotation labels for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.1214070320129395s
Accuracy | Check White space in annotation for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.19672131538391113s
Accuracy | Check Datatype consistency for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 3.964008331298828s
Consistency | Disjoint class check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11634111404418945s
Consistency | Check Misplaced properties for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.8425335884094238s
Consistency | Check Ontology hijacking for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 3.7274653911590576s
Consistency | Check Invalid usage of undefined classes for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.47064208984375s
Consistency | Check Invalid usage of undefined properties for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.249019145965576s
Conciseness | Check Extensional conciseness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.5215885639190674s
Security | Sign check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12046122550964355s
Availability | Check URIs Dereferenciability for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 4903.396131515503s
Completeness | Calculation of interlinking completeness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.699622392654419s
Reputation | Calculation of the PageRank for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.02094125747680664s
Interlinking | Calculation of Degree of Connection for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 7.963180541992188e-05s
Interlinking | Calculation of Centrality for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.47955322265625e-05s
Interoperability | Check the re-using of existing vocabs for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.6226043701171875e-06s
Believability | Calculation of trust value for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.5735626220703125e-05s
INFO | --- Analysis for portuguese_prisons_releases took 4976.667576313019s
Availability | SPARQL endpoint availability check for prefix.cc took 9.751319885253906e-05s
Availability | VoID file availability check for prefix.cc took 0.0005772113800048828s
Completeness | Calculation of interlinking completeness for prefix.cc took 0.3160514831542969s
Reputation | Calculation of the PageRank for prefix.cc took 0.021881818771362305s
Interlinking | Calculation of Degree of Connection for prefix.cc took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for prefix.cc took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for prefix.cc took 4.38690185546875e-05s
Believability | Calculation of trust value for prefix.cc took 1.6927719116210938e-05s
INFO | --- Analysis for prefix-cc took 3.5006303787231445s
Availability | SPARQL endpoint availability check for PREJUST4WOMEN Knowledge Graph took 1.6301379203796387s
Availability | VoID file availability check for PREJUST4WOMEN Knowledge Graph took 0.0007023811340332031s
Completeness | Calculation of interlinking completeness for PREJUST4WOMEN Knowledge Graph took 0.2782416343688965s
Reputation | Calculation of the PageRank for PREJUST4WOMEN Knowledge Graph took 0.02204751968383789s
Interlinking | Calculation of Degree of Connection for PREJUST4WOMEN Knowledge Graph took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for PREJUST4WOMEN Knowledge Graph took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for PREJUST4WOMEN Knowledge Graph took 5.555152893066406e-05s
Believability | Calculation of trust value for PREJUST4WOMEN Knowledge Graph took 1.33514404296875e-05s
INFO | --- Analysis for PREJUST4WOMAN_PROJECT took 7.752338409423828s
Availability | SPARQL endpoint availability check for PreLex took 6.7490458488464355s
Availability | VoID file availability check for PreLex took 0.0006303787231445312s
Completeness | Calculation of interlinking completeness for PreLex took 0.33077335357666016s
Reputation | Calculation of the PageRank for PreLex took 0.020639896392822266s
Interlinking | Calculation of Degree of Connection for PreLex took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for PreLex took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for PreLex took 7.510185241699219e-05s
Believability | Calculation of trust value for PreLex took 1.33514404296875e-05s
INFO | --- Analysis for prelex took 20.29280734062195s
Availability | SPARQL endpoint availability check for Prelinger Archives took 1.6542043685913086s
Availability | VoID file availability check for Prelinger Archives took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for Prelinger Archives took 0.322735071182251s
Reputation | Calculation of the PageRank for Prelinger Archives took 0.0207061767578125s
Interlinking | Calculation of Degree of Connection for Prelinger Archives took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Prelinger Archives took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Prelinger Archives took 3.337860107421875e-05s
Believability | Calculation of trust value for Prelinger Archives took 1.33514404296875e-05s
INFO | --- Analysis for prelinger_archives took 14.933379888534546s
Availability | SPARQL endpoint availability check for PreMOn took 0.6175637245178223s
Availability | VoID file availability check for PreMOn took 0.0005533695220947266s
Completeness | Calculation of interlinking completeness for PreMOn took 0.3116617202758789s
Reputation | Calculation of the PageRank for PreMOn took 0.02075934410095215s
Interlinking | Calculation of Degree of Connection for PreMOn took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for PreMOn took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for PreMOn took 5.3882598876953125e-05s
Believability | Calculation of trust value for PreMOn took 1.3589859008789062e-05s
INFO | --- Analysis for premon took 5.799605846405029s
Availability | SPARQL endpoint availability check for Princeton Library FindingAids took 9.441375732421875e-05s
Availability | VoID file availability check for Princeton Library FindingAids took 0.0005619525909423828s
Completeness | Calculation of interlinking completeness for Princeton Library FindingAids took 0.29435205459594727s
Reputation | Calculation of the PageRank for Princeton Library FindingAids took 0.02065253257751465s
Interlinking | Calculation of Degree of Connection for Princeton Library FindingAids took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Princeton Library FindingAids took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Princeton Library FindingAids took 6.127357482910156e-05s
Believability | Calculation of trust value for Princeton Library FindingAids took 1.4781951904296875e-05s
INFO | --- Analysis for princeton-library-findingaids took 3.9169647693634033s
Availability | SPARQL endpoint availability check for PrinParLat in LiLa took 0.6326601505279541s
Availability | VoID file availability check for PrinParLat in LiLa took 0.0006854534149169922s
Completeness | Calculation of interlinking completeness for PrinParLat in LiLa took 0.31174135208129883s
Reputation | Calculation of the PageRank for PrinParLat in LiLa took 0.020875215530395508s
Interlinking | Calculation of Degree of Connection for PrinParLat in LiLa took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for PrinParLat in LiLa took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for PrinParLat in LiLa took 4.935264587402344e-05s
Believability | Calculation of trust value for PrinParLat in LiLa took 1.430511474609375e-05s
INFO | --- Analysis for PrinParLat took 4.613255977630615s
Availability | SPARQL endpoint availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.36389899253845215s
Availability | VoID file availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0005097389221191406s
Completeness | Calculation of interlinking completeness for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.3017404079437256s
Reputation | Calculation of the PageRank for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.021376609802246094s
Interlinking | Calculation of Degree of Connection for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 8.988380432128906e-05s
Believability | Calculation of trust value for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.2636184692382812e-05s
INFO | --- Analysis for printed-book-auction-catalogues took 3.438262462615967s
Availability | SPARQL endpoint availability check for Prior Panel took 8.916854858398438e-05s
Availability | VoID file availability check for Prior Panel took 0.0003085136413574219s
Completeness | Calculation of interlinking completeness for Prior Panel took 0.31293296813964844s
Reputation | Calculation of the PageRank for Prior Panel took 0.022522926330566406s
Interlinking | Calculation of Degree of Connection for Prior Panel took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for Prior Panel took 0.0014312267303466797s
Interlinking | Calculation of Clustering coefficient for Prior Panel took 5.316734313964844e-05s
Believability | Calculation of trust value for Prior Panel took 1.4543533325195312e-05s
INFO | --- Analysis for Prior_Panel took 2.8011739253997803s
Availability | SPARQL endpoint availability check for ProductDB took 0.7549684047698975s
Availability | VoID file availability check for ProductDB took 0.0007345676422119141s
Completeness | Calculation of interlinking completeness for ProductDB took 0.28820347785949707s
Reputation | Calculation of the PageRank for ProductDB took 0.0205991268157959s
Interlinking | Calculation of Degree of Connection for ProductDB took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ProductDB took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for ProductDB took 7.724761962890625e-05s
Believability | Calculation of trust value for ProductDB took 1.430511474609375e-05s
INFO | --- Analysis for productdb took 4.036936044692993s
Availability | SPARQL endpoint availability check for Product Types Ontology took 9.083747863769531e-05s
Availability | VoID file availability check for Product Types Ontology took 0.0006821155548095703s
Completeness | Calculation of interlinking completeness for Product Types Ontology took 0.28823089599609375s
Reputation | Calculation of the PageRank for Product Types Ontology took 0.023429155349731445s
Interlinking | Calculation of Degree of Connection for Product Types Ontology took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Product Types Ontology took 0.0008020401000976562s
Interlinking | Calculation of Clustering coefficient for Product Types Ontology took 8.702278137207031e-05s
Believability | Calculation of trust value for Product Types Ontology took 1.3589859008789062e-05s
INFO | --- Analysis for productontology took 3.8018879890441895s
Availability | SPARQL endpoint availability check for Prospects and Trends (GNOSS) took 9.226799011230469e-05s
Availability | VoID file availability check for Prospects and Trends (GNOSS) took 0.0007505416870117188s
Completeness | Calculation of interlinking completeness for Prospects and Trends (GNOSS) took 0.2683980464935303s
Reputation | Calculation of the PageRank for Prospects and Trends (GNOSS) took 0.021149873733520508s
Interlinking | Calculation of Degree of Connection for Prospects and Trends (GNOSS) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Prospects and Trends (GNOSS) took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for Prospects and Trends (GNOSS) took 0.00010848045349121094s
Believability | Calculation of trust value for Prospects and Trends (GNOSS) took 1.430511474609375e-05s
INFO | --- Analysis for prospects-and-trends-gnoss took 7.046530485153198s
Availability | SPARQL endpoint availability check for provenanceweb took 0.05928850173950195s
Availability | VoID file availability check for provenanceweb took 0.0003108978271484375s
Completeness | Calculation of interlinking completeness for provenanceweb took 0.30748963356018066s
Reputation | Calculation of the PageRank for provenanceweb took 0.021392822265625s
Interlinking | Calculation of Degree of Connection for provenanceweb took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for provenanceweb took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for provenanceweb took 8.153915405273438e-05s
Believability | Calculation of trust value for provenanceweb took 1.430511474609375e-05s
INFO | --- Analysis for provenanceweb took 51.1895866394043s
Availability | SPARQL endpoint availability check for Proyecto Apadrina,  Marketing Punto de Venta took 9.202957153320312e-05s
Availability | VoID file availability check for Proyecto Apadrina,  Marketing Punto de Venta took 0.0004000663757324219s
Completeness | Calculation of interlinking completeness for Proyecto Apadrina,  Marketing Punto de Venta took 0.3305997848510742s
Reputation | Calculation of the PageRank for Proyecto Apadrina,  Marketing Punto de Venta took 0.020751476287841797s
Interlinking | Calculation of Degree of Connection for Proyecto Apadrina,  Marketing Punto de Venta took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Proyecto Apadrina,  Marketing Punto de Venta took 0.0007901191711425781s
Interlinking | Calculation of Clustering coefficient for Proyecto Apadrina,  Marketing Punto de Venta took 0.0001087188720703125s
Believability | Calculation of trust value for Proyecto Apadrina,  Marketing Punto de Venta took 1.4066696166992188e-05s
INFO | --- Analysis for proyectoapadrina took 6.848644018173218s
Availability | SPARQL endpoint availability check for Product Scheme Classifications Catalogue took 26.510585069656372s
Availability | VoID file availability check for Product Scheme Classifications Catalogue took 0.0009133815765380859s
Completeness | Calculation of interlinking completeness for Product Scheme Classifications Catalogue took 0.32134127616882324s
Reputation | Calculation of the PageRank for Product Scheme Classifications Catalogue took 0.02177596092224121s
Interlinking | Calculation of Degree of Connection for Product Scheme Classifications Catalogue took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Product Scheme Classifications Catalogue took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Product Scheme Classifications Catalogue took 4.458427429199219e-05s
Believability | Calculation of trust value for Product Scheme Classifications Catalogue took 1.1205673217773438e-05s
INFO | --- Analysis for pscs-catalogue took 129.50183033943176s
Availability | SPARQL endpoint availability check for Polythematic Structured Subject Heading System took 0.00010609626770019531s
Availability | VoID file availability check for Polythematic Structured Subject Heading System took 0.0006163120269775391s
Completeness | Calculation of interlinking completeness for Polythematic Structured Subject Heading System took 0.30095553398132324s
Reputation | Calculation of the PageRank for Polythematic Structured Subject Heading System took 0.021135330200195312s
Interlinking | Calculation of Degree of Connection for Polythematic Structured Subject Heading System took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Polythematic Structured Subject Heading System took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Polythematic Structured Subject Heading System took 8.821487426757812e-05s
Believability | Calculation of trust value for Polythematic Structured Subject Heading System took 1.52587890625e-05s
INFO | --- Analysis for psh-subject-headings took 3.4536473751068115s
Availability | SPARQL endpoint availability check for Depression took 0.7137479782104492s
Availability | VoID file availability check for Depression took 0.0006275177001953125s
Completeness | Calculation of interlinking completeness for Depression took 0.27240848541259766s
Reputation | Calculation of the PageRank for Depression took 0.020795583724975586s
Interlinking | Calculation of Degree of Connection for Depression took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Depression took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for Depression took 3.409385681152344e-05s
Believability | Calculation of trust value for Depression took 1.5497207641601562e-05s
INFO | --- Analysis for Psychology took 3.437016248703003s
Availability | SPARQL endpoint availability check for PubChem RDF took 8.988380432128906e-05s
Availability | VoID file availability check for PubChem RDF took 0.0006709098815917969s
Completeness | Calculation of interlinking completeness for PubChem RDF took 0.28004956245422363s
Reputation | Calculation of the PageRank for PubChem RDF took 0.020807743072509766s
Interlinking | Calculation of Degree of Connection for PubChem RDF took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for PubChem RDF took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for PubChem RDF took 4.38690185546875e-05s
Believability | Calculation of trust value for PubChem RDF took 1.2874603271484375e-05s
INFO | --- Analysis for PubChem_RDF took 5.371082782745361s
Availability | SPARQL endpoint availability check for Public Spending in Greece took 60.0511953830719s
Availability | VoID file availability check for Public Spending in Greece took 0.0006878376007080078s
Completeness | Calculation of interlinking completeness for Public Spending in Greece took 0.293550968170166s
Reputation | Calculation of the PageRank for Public Spending in Greece took 0.021456241607666016s
Interlinking | Calculation of Degree of Connection for Public Spending in Greece took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Public Spending in Greece took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Public Spending in Greece took 9.179115295410156e-05s
Believability | Calculation of trust value for Public Spending in Greece took 1.3113021850585938e-05s
INFO | --- Analysis for public-spending-in-greece took 147.61899328231812s
Availability | SPARQL endpoint availability check for Publications Office Authority tables took 0.2000269889831543s
Availability | VoID file availability check for Publications Office Authority tables took 0.0006701946258544922s
Extra | Recovery of all triples for Publications Office Authority tables took 154.0187795162201s
Performance | Total latancy measurement for Publications Office Authority tables took 0.5835752487182617s
Amount of data | Number of triples check for Publications Office Authority tables took 39.78370928764343s
Interoperability | New terms check for Publications Office Authority tables took 57.26074433326721s
Versatility | Languages check for Publications Office Authority tables took 300.1516869068146s
Interpretability | Number of blank nodes check for Publications Office Authority tables took 69.23227858543396s
Security | Check HTTPS for Publications Office Authority tables took 0.4098362922668457s
Interpretability | RDF structures check for Publications Office Authority tables took 0.30835676193237305s
Versatility | Serialization formats check for Publications Office Authority tables took 3.9494266510009766s
Availability | RDF dump link check for Publications Office Authority tables took 0.21812033653259277s
License | MR license check for Publications Office Authority tables took 0.5013730525970459s
License | HR license check for Publications Office Authority tables took 300.08061838150024s
Amount of data | Number of property check for Publications Office Authority tables took 0.3560335636138916s
Understandability | Number of label check for Publications Office Authority tables took 1.6909658908843994s
Understandability | URI regex check for Publications Office Authority tables took 0.381009578704834s
Understandability | Vocabs check for Publications Office Authority tables took 0.12540197372436523s
Verifiability | Authors check for Publications Office Authority tables took 0.22243833541870117s
Verifiability | Publishers check for Publications Office Authority tables took 0.18806147575378418s
Performance | Throughput check for Publications Office Authority tables took 10.835419416427612s
Amount of data | Check the number of entities for Publications Office Authority tables took 7.009506225585938e-05s
Verifiability | Contribs. check for Publications Office Authority tables took 0.10505342483520508s
Interlinking | sameAs chians check for Publications Office Authority tables took 6.551582098007202s
Interlinking | skos check for Publications Office Authority tables took 0.1857759952545166s
Interlinking | skos check for Publications Office Authority tables took 0.16350913047790527s
Timeliness | dataset update frequency check for Publications Office Authority tables took 0.3052406311035156s
Currency | Creation date check for Publications Office Authority tables took 0.4246997833251953s
Currency | Modification date check for Publications Office Authority tables took 0.15394282341003418s
Rep.Conc. | URIs length for Publications Office Authority tables took 430.06178283691406s
Interoperability | New vocabularies check for Publications Office Authority tables took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for Publications Office Authority tables took 0.14195656776428223s
Accuracy | Check Functional Property for Publications Office Authority tables took 0.18823456764221191s
Accuracy | Check Inverse Functional Property for Publications Office Authority tables took 0.15573716163635254s
Accuracy | Check Empty annotation labels for Publications Office Authority tables took 43.07784366607666s
Accuracy | Check White space in annotation for Publications Office Authority tables took 3.220093250274658s
Accuracy | Check Datatype consistency for Publications Office Authority tables took 2.7845723628997803s
Consistency | Disjoint class check for Publications Office Authority tables took 0.12751293182373047s
Consistency | Check Misplaced properties for Publications Office Authority tables took 300.4370903968811s
Consistency | Misplaced classes for Publications Office Authority tables took 8.78010606765747s
Consistency | Check Ontology hijacking for Publications Office Authority tables took 45.67050361633301s
Consistency | Check Invalid usage of undefined classes for Publications Office Authority tables took 1.9583444595336914s
Consistency | Check Invalid usage of undefined properties for Publications Office Authority tables took 301.6248023509979s
Conciseness | Check Extensional conciseness for Publications Office Authority tables took 3.1372311115264893s
Conciseness | Check Intensional conciseness for Publications Office Authority tables took 0.4019160270690918s
Security | Sign check for Publications Office Authority tables took 0.1511211395263672s
Availability | Check URIs Dereferenciability for Publications Office Authority tables took 11.357933521270752s
Completeness | Calculation of interlinking completeness for Publications Office Authority tables took 1.5246644020080566s
Reputation | Calculation of the PageRank for Publications Office Authority tables took 0.021707773208618164s
Interlinking | Calculation of Degree of Connection for Publications Office Authority tables took 2.5033950805664062e-05s
Interlinking | Calculation of Centrality for Publications Office Authority tables took 0.0008249282836914062s
Interlinking | Calculation of Clustering coefficient for Publications Office Authority tables took 6.127357482910156e-05s
Interoperability | Check the re-using of existing vocabs for Publications Office Authority tables took 2.384185791015625e-06s
Believability | Calculation of trust value for Publications Office Authority tables took 1.1682510375976562e-05s
INFO | --- Analysis for publications_office_authority_tables took 14769.95800614357s
Availability | SPARQL endpoint availability check for QBOAirbase took 9.441375732421875e-05s
Availability | VoID file availability check for QBOAirbase took 0.0010421276092529297s
Completeness | Calculation of interlinking completeness for QBOAirbase took 0.39418888092041016s
Reputation | Calculation of the PageRank for QBOAirbase took 0.020992517471313477s
Interlinking | Calculation of Degree of Connection for QBOAirbase took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for QBOAirbase took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for QBOAirbase took 8.940696716308594e-05s
Believability | Calculation of trust value for QBOAirbase took 1.5020370483398438e-05s
INFO | --- Analysis for qboairbase took 137.23212337493896s
Availability | SPARQL endpoint availability check for Qualité de l'air took 9.34600830078125e-05s
Availability | VoID file availability check for Qualité de l'air took 0.0006322860717773438s
Completeness | Calculation of interlinking completeness for Qualité de l'air took 0.28022074699401855s
Reputation | Calculation of the PageRank for Qualité de l'air took 0.02079296112060547s
Interlinking | Calculation of Degree of Connection for Qualité de l'air took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Qualité de l'air took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air took 3.3855438232421875e-05s
Believability | Calculation of trust value for Qualité de l'air took 1.3828277587890625e-05s
INFO | --- Analysis for Qualité_de_l'air took 3.0479910373687744s
Availability | SPARQL endpoint availability check for Qualité de l'air dans le monde took 5.984306335449219e-05s
Availability | VoID file availability check for Qualité de l'air dans le monde took 0.0007340908050537109s
Completeness | Calculation of interlinking completeness for Qualité de l'air dans le monde took 0.3043065071105957s
Reputation | Calculation of the PageRank for Qualité de l'air dans le monde took 0.020998477935791016s
Interlinking | Calculation of Degree of Connection for Qualité de l'air dans le monde took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Qualité de l'air dans le monde took 0.0007843971252441406s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air dans le monde took 4.0531158447265625e-05s
Believability | Calculation of trust value for Qualité de l'air dans le monde took 9.5367431640625e-06s
INFO | --- Analysis for Qualité_de_l'air_dans_le_monde took 48.01785707473755s
Availability | SPARQL endpoint availability check for Querolus in LiLa took 0.5956501960754395s
Availability | VoID file availability check for Querolus in LiLa took 0.0007114410400390625s
Completeness | Calculation of interlinking completeness for Querolus in LiLa took 0.29268455505371094s
Reputation | Calculation of the PageRank for Querolus in LiLa took 0.020752429962158203s
Interlinking | Calculation of Degree of Connection for Querolus in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Querolus in LiLa took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for Querolus in LiLa took 4.744529724121094e-05s
Believability | Calculation of trust value for Querolus in LiLa took 1.4066696166992188e-05s
INFO | --- Analysis for Querolus took 4.351332426071167s
Availability | SPARQL endpoint availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.40671277046203613s
Availability | VoID file availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0006766319274902344s
Extra | Recovery of all triples for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 29.238569021224976s
Performance | Total latancy measurement for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.6894936561584473s
Amount of data | Number of triples check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 3.2746357917785645s
Interoperability | New terms check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.0371434688568115s
Versatility | Languages check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 9.530781745910645s
Interpretability | Number of blank nodes check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.559457540512085s
Interpretability | RDF structures check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1958451271057129s
Versatility | Serialization formats check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1560673713684082s
Availability | RDF dump link check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13031268119812012s
License | MR license check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1310725212097168s
License | HR license check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.19020414352416992s
Amount of data | Number of property check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.16277384757995605s
Understandability | Number of label check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15409636497497559s
Understandability | URI regex check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.2824440002441406s
Understandability | Vocabs check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14248061180114746s
Verifiability | Authors check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14221644401550293s
Verifiability | Publishers check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14224600791931152s
Performance | Throughput check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 10.56715726852417s
Amount of data | Check the number of entities for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 7.843971252441406e-05s
Verifiability | Contribs. check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14374232292175293s
Interlinking | sameAs chians check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14224553108215332s
Interlinking | skos check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1417372226715088s
Interlinking | skos check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14833593368530273s
Timeliness | dataset update frequency check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14205169677734375s
Currency | Creation date check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.2943837642669678s
Currency | Modification date check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.3389933109283447s
Rep.Conc. | URIs length for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 20.922706604003906s
Interoperability | New vocabularies check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15290355682373047s
Accuracy | Check Functional Property for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15074944496154785s
Accuracy | Check Inverse Functional Property for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14263582229614258s
Accuracy | Check Empty annotation labels for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14264178276062012s
Accuracy | Check White space in annotation for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.7642974853515625e-05s
Accuracy | Check Datatype consistency for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.308362007141113s
Consistency | Disjoint class check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14629220962524414s
Consistency | Check Misplaced properties for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 5.601426601409912s
Consistency | Check Ontology hijacking for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 5.071654558181763s
Consistency | Check Invalid usage of undefined classes for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.6061460971832275s
Consistency | Check Invalid usage of undefined properties for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 6.92958664894104s
Conciseness | Check Extensional conciseness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.909013509750366s
Security | Sign check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13089728355407715s
Availability | Check URIs Dereferenciability for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 14.830900192260742s
Completeness | Calculation of interlinking completeness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.3051421642303467s
Reputation | Calculation of the PageRank for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0218353271484375s
Interlinking | Calculation of Degree of Connection for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0010221004486083984s
Interlinking | Calculation of Clustering coefficient for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 7.200241088867188e-05s
Interoperability | Check the re-using of existing vocabs for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.384185791015625e-06s
Believability | Calculation of trust value for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.0967254638671875e-05s
INFO | --- Analysis for racai-legalnero took 160.5624179840088s
Availability | SPARQL endpoint availability check for Romanian CoRoLa Word Embeddings took 9.059906005859375e-05s
Availability | VoID file availability check for Romanian CoRoLa Word Embeddings took 0.0006661415100097656s
Completeness | Calculation of interlinking completeness for Romanian CoRoLa Word Embeddings took 0.3145027160644531s
Reputation | Calculation of the PageRank for Romanian CoRoLa Word Embeddings took 0.020846128463745117s
Interlinking | Calculation of Degree of Connection for Romanian CoRoLa Word Embeddings took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Romanian CoRoLa Word Embeddings took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for Romanian CoRoLa Word Embeddings took 4.291534423828125e-05s
Believability | Calculation of trust value for Romanian CoRoLa Word Embeddings took 1.3828277587890625e-05s
INFO | --- Analysis for racai-llod-corola-we took 3.059471368789673s
Availability | SPARQL endpoint availability check for PARSEME-Ro corpus took 0.13400721549987793s
Availability | VoID file availability check for PARSEME-Ro corpus took 0.0006177425384521484s
Extra | Recovery of all triples for PARSEME-Ro corpus took 31.126712560653687s
Performance | Total latancy measurement for PARSEME-Ro corpus took 0.6773045063018799s
Amount of data | Number of triples check for PARSEME-Ro corpus took 6.84594988822937s
Interoperability | New terms check for PARSEME-Ro corpus took 2.380411148071289s
Versatility | Languages check for PARSEME-Ro corpus took 17.96763300895691s
Interpretability | Number of blank nodes check for PARSEME-Ro corpus took 5.589456081390381s
Interpretability | RDF structures check for PARSEME-Ro corpus took 0.14464616775512695s
Versatility | Serialization formats check for PARSEME-Ro corpus took 0.15287232398986816s
Availability | RDF dump link check for PARSEME-Ro corpus took 0.14125609397888184s
License | MR license check for PARSEME-Ro corpus took 0.15376949310302734s
License | HR license check for PARSEME-Ro corpus took 10.142687559127808s
Amount of data | Number of property check for PARSEME-Ro corpus took 0.1295795440673828s
Understandability | Number of label check for PARSEME-Ro corpus took 0.1884312629699707s
Understandability | URI regex check for PARSEME-Ro corpus took 0.2832012176513672s
Understandability | Vocabs check for PARSEME-Ro corpus took 0.13051724433898926s
Verifiability | Authors check for PARSEME-Ro corpus took 0.14246749877929688s
Verifiability | Publishers check for PARSEME-Ro corpus took 0.13114023208618164s
Performance | Throughput check for PARSEME-Ro corpus took 10.682067632675171s
Amount of data | Check the number of entities for PARSEME-Ro corpus took 8.416175842285156e-05s
Verifiability | Contribs. check for PARSEME-Ro corpus took 0.14174747467041016s
Interlinking | sameAs chians check for PARSEME-Ro corpus took 0.15371394157409668s
Interlinking | skos check for PARSEME-Ro corpus took 0.15429377555847168s
Interlinking | skos check for PARSEME-Ro corpus took 0.14224505424499512s
Timeliness | dataset update frequency check for PARSEME-Ro corpus took 0.13231205940246582s
Currency | Creation date check for PARSEME-Ro corpus took 0.29509496688842773s
Currency | Modification date check for PARSEME-Ro corpus took 0.27543139457702637s
Rep.Conc. | URIs length for PARSEME-Ro corpus took 80.53129124641418s
Interoperability | New vocabularies check for PARSEME-Ro corpus took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for PARSEME-Ro corpus took 0.13211560249328613s
Accuracy | Check Functional Property for PARSEME-Ro corpus took 0.15344595909118652s
Accuracy | Check Inverse Functional Property for PARSEME-Ro corpus took 0.14175009727478027s
Accuracy | Check Empty annotation labels for PARSEME-Ro corpus took 1.9788260459899902s
Accuracy | Check White space in annotation for PARSEME-Ro corpus took 0.235975980758667s
Accuracy | Check Datatype consistency for PARSEME-Ro corpus took 4.141248464584351s
Consistency | Disjoint class check for PARSEME-Ro corpus took 0.14419221878051758s
Consistency | Check Misplaced properties for PARSEME-Ro corpus took 11.162437200546265s
Consistency | Check Ontology hijacking for PARSEME-Ro corpus took 31.299744129180908s
Consistency | Check Invalid usage of undefined classes for PARSEME-Ro corpus took 1.8565256595611572s
Consistency | Check Invalid usage of undefined properties for PARSEME-Ro corpus took 13.401443004608154s
Conciseness | Check Extensional conciseness for PARSEME-Ro corpus took 2.921566963195801s
Security | Sign check for PARSEME-Ro corpus took 0.13013553619384766s
Availability | Check URIs Dereferenciability for PARSEME-Ro corpus took 7.538656234741211s
Completeness | Calculation of interlinking completeness for PARSEME-Ro corpus took 0.5059146881103516s
Reputation | Calculation of the PageRank for PARSEME-Ro corpus took 0.02043294906616211s
Interlinking | Calculation of Degree of Connection for PARSEME-Ro corpus took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for PARSEME-Ro corpus took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for PARSEME-Ro corpus took 4.267692565917969e-05s
Interoperability | Check the re-using of existing vocabs for PARSEME-Ro corpus took 2.384185791015625e-06s
Believability | Calculation of trust value for PARSEME-Ro corpus took 1.5020370483398438e-05s
INFO | --- Analysis for racai-llod-parseme-ro took 283.3161699771881s
Availability | SPARQL endpoint availability check for RoLEX took 0.14122343063354492s
Availability | VoID file availability check for RoLEX took 0.0007557868957519531s
Extra | Recovery of all triples for RoLEX took 34.890297651290894s
Performance | Total latancy measurement for RoLEX took 0.7131500244140625s
Amount of data | Number of triples check for RoLEX took 1.6021907329559326s
Interoperability | New terms check for RoLEX took 1.8872346878051758s
Versatility | Languages check for RoLEX took 4.100019693374634s
Interpretability | Number of blank nodes check for RoLEX took 1.1452171802520752s
Interpretability | RDF structures check for RoLEX took 0.14353561401367188s
Versatility | Serialization formats check for RoLEX took 0.1539163589477539s
Availability | RDF dump link check for RoLEX took 0.15317249298095703s
License | MR license check for RoLEX took 0.13229846954345703s
License | HR license check for RoLEX took 0.1427304744720459s
Amount of data | Number of property check for RoLEX took 0.15269041061401367s
Understandability | Number of label check for RoLEX took 0.1432030200958252s
Understandability | URI regex check for RoLEX took 0.30576586723327637s
Understandability | Vocabs check for RoLEX took 0.15138006210327148s
Verifiability | Authors check for RoLEX took 0.14220690727233887s
Verifiability | Publishers check for RoLEX took 0.1400444507598877s
Performance | Throughput check for RoLEX took 10.6151864528656s
Amount of data | Check the number of entities for RoLEX took 7.843971252441406e-05s
Verifiability | Contribs. check for RoLEX took 0.13076496124267578s
Interlinking | sameAs chians check for RoLEX took 0.14186644554138184s
Interlinking | skos check for RoLEX took 0.15292954444885254s
Interlinking | skos check for RoLEX took 0.1533658504486084s
Timeliness | dataset update frequency check for RoLEX took 0.13065886497497559s
Currency | Creation date check for RoLEX took 0.272998571395874s
Currency | Modification date check for RoLEX took 0.2840437889099121s
Rep.Conc. | URIs length for RoLEX took 57.615058183670044s
Interoperability | New vocabularies check for RoLEX took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for RoLEX took 0.1531076431274414s
Accuracy | Check Functional Property for RoLEX took 0.12990140914916992s
Accuracy | Check Inverse Functional Property for RoLEX took 0.14239072799682617s
Accuracy | Check Datatype consistency for RoLEX took 4.311864852905273s
Consistency | Disjoint class check for RoLEX took 0.1559755802154541s
Consistency | Check Misplaced properties for RoLEX took 2.6627328395843506s
Consistency | Check Ontology hijacking for RoLEX took 9.092325687408447s
Consistency | Check Invalid usage of undefined classes for RoLEX took 2.1542038917541504s
Consistency | Check Invalid usage of undefined properties for RoLEX took 4.196142673492432s
Conciseness | Check Extensional conciseness for RoLEX took 3.1839473247528076s
Security | Sign check for RoLEX took 0.1310257911682129s
Availability | Check URIs Dereferenciability for RoLEX took 7.573001384735107s
Completeness | Calculation of interlinking completeness for RoLEX took 0.38928699493408203s
Reputation | Calculation of the PageRank for RoLEX took 0.021068096160888672s
Interlinking | Calculation of Degree of Connection for RoLEX took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for RoLEX took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for RoLEX took 3.790855407714844e-05s
Interoperability | Check the re-using of existing vocabs for RoLEX took 2.6226043701171875e-06s
Believability | Calculation of trust value for RoLEX took 1.5020370483398438e-05s
INFO | --- Analysis for racai-llod-rolex took 172.35273671150208s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 9.036064147949219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0006792545318603516s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.32055187225341797s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.021024227142333984s
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.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 3.528594970703125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 1.430511474609375e-05s
INFO | --- Analysis for racai-llod-romanian-treebank took 2.9204189777374268s
Availability | SPARQL endpoint availability check for JSON Romanian Wordnet took 4.38690185546875e-05s
Availability | VoID file availability check for JSON Romanian Wordnet took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for JSON Romanian Wordnet took 0.3024711608886719s
Reputation | Calculation of the PageRank for JSON Romanian Wordnet took 0.022617816925048828s
Interlinking | Calculation of Degree of Connection for JSON Romanian Wordnet took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for JSON Romanian Wordnet took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for JSON Romanian Wordnet took 3.743171691894531e-05s
Believability | Calculation of trust value for JSON Romanian Wordnet took 1.3828277587890625e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-json took 2.9339163303375244s
Availability | SPARQL endpoint availability check for LMF Romanian Wordnet took 5.316734313964844e-05s
Availability | VoID file availability check for LMF Romanian Wordnet took 0.0007214546203613281s
Completeness | Calculation of interlinking completeness for LMF Romanian Wordnet took 0.2891576290130615s
Reputation | Calculation of the PageRank for LMF Romanian Wordnet took 0.022327184677124023s
Interlinking | Calculation of Degree of Connection for LMF Romanian Wordnet took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for LMF Romanian Wordnet took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for LMF Romanian Wordnet took 3.7670135498046875e-05s
Believability | Calculation of trust value for LMF Romanian Wordnet took 1.0013580322265625e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-lmf took 2.8202152252197266s
Availability | SPARQL endpoint availability check for Turtle-RDF Romanian Wordnet took 9.059906005859375e-05s
Availability | VoID file availability check for Turtle-RDF Romanian Wordnet took 0.0006644725799560547s
Completeness | Calculation of interlinking completeness for Turtle-RDF Romanian Wordnet took 0.2781646251678467s
Reputation | Calculation of the PageRank for Turtle-RDF Romanian Wordnet took 0.020859241485595703s
Interlinking | Calculation of Degree of Connection for Turtle-RDF Romanian Wordnet took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Turtle-RDF Romanian Wordnet took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Turtle-RDF Romanian Wordnet took 3.528594970703125e-05s
Believability | Calculation of trust value for Turtle-RDF Romanian Wordnet took 1.3589859008789062e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-ttl took 2.9234442710876465s
Availability | SPARQL endpoint availability check for ROBIN Technical Acquisition Speech Corpus took 0.13367438316345215s
Availability | VoID file availability check for ROBIN Technical Acquisition Speech Corpus took 0.0007178783416748047s
Extra | Recovery of all triples for ROBIN Technical Acquisition Speech Corpus took 9.485478639602661s
Performance | Total latancy measurement for ROBIN Technical Acquisition Speech Corpus took 0.6717123985290527s
Amount of data | Number of triples check for ROBIN Technical Acquisition Speech Corpus took 0.31153225898742676s
Interoperability | New terms check for ROBIN Technical Acquisition Speech Corpus took 1.6418895721435547s
Versatility | Languages check for ROBIN Technical Acquisition Speech Corpus took 0.6067543029785156s
Interpretability | Number of blank nodes check for ROBIN Technical Acquisition Speech Corpus took 0.24595975875854492s
Interpretability | RDF structures check for ROBIN Technical Acquisition Speech Corpus took 0.152374267578125s
Versatility | Serialization formats check for ROBIN Technical Acquisition Speech Corpus took 0.14284849166870117s
Availability | RDF dump link check for ROBIN Technical Acquisition Speech Corpus took 0.1500687599182129s
License | MR license check for ROBIN Technical Acquisition Speech Corpus took 0.14227819442749023s
License | HR license check for ROBIN Technical Acquisition Speech Corpus took 0.13489866256713867s
Amount of data | Number of property check for ROBIN Technical Acquisition Speech Corpus took 0.13986635208129883s
Understandability | Number of label check for ROBIN Technical Acquisition Speech Corpus took 0.1446981430053711s
Understandability | URI regex check for ROBIN Technical Acquisition Speech Corpus took 0.2684340476989746s
Understandability | Vocabs check for ROBIN Technical Acquisition Speech Corpus took 0.14096283912658691s
Verifiability | Authors check for ROBIN Technical Acquisition Speech Corpus took 0.15320420265197754s
Verifiability | Publishers check for ROBIN Technical Acquisition Speech Corpus took 0.15155529975891113s
Performance | Throughput check for ROBIN Technical Acquisition Speech Corpus took 11.031654596328735s
Amount of data | Check the number of entities for ROBIN Technical Acquisition Speech Corpus took 7.486343383789062e-05s
Verifiability | Contribs. check for ROBIN Technical Acquisition Speech Corpus took 0.15401840209960938s
Interlinking | sameAs chians check for ROBIN Technical Acquisition Speech Corpus took 0.15251922607421875s
Interlinking | skos check for ROBIN Technical Acquisition Speech Corpus took 0.14293360710144043s
Interlinking | skos check for ROBIN Technical Acquisition Speech Corpus took 0.14252662658691406s
Timeliness | dataset update frequency check for ROBIN Technical Acquisition Speech Corpus took 0.1541914939880371s
Currency | Creation date check for ROBIN Technical Acquisition Speech Corpus took 0.30807065963745117s
Currency | Modification date check for ROBIN Technical Acquisition Speech Corpus took 0.2864499092102051s
Rep.Conc. | URIs length for ROBIN Technical Acquisition Speech Corpus took 2.6568920612335205s
Interoperability | New vocabularies check for ROBIN Technical Acquisition Speech Corpus took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for ROBIN Technical Acquisition Speech Corpus took 0.14108967781066895s
Accuracy | Check Functional Property for ROBIN Technical Acquisition Speech Corpus took 0.13837218284606934s
Accuracy | Check Inverse Functional Property for ROBIN Technical Acquisition Speech Corpus took 0.15062952041625977s
Accuracy | Check Empty annotation labels for ROBIN Technical Acquisition Speech Corpus took 0.4173238277435303s
Accuracy | Check White space in annotation for ROBIN Technical Acquisition Speech Corpus took 0.009969472885131836s
Accuracy | Check Datatype consistency for ROBIN Technical Acquisition Speech Corpus took 1.2556946277618408s
Consistency | Disjoint class check for ROBIN Technical Acquisition Speech Corpus took 0.14300537109375s
Consistency | Check Misplaced properties for ROBIN Technical Acquisition Speech Corpus took 0.5653195381164551s
Consistency | Check Ontology hijacking for ROBIN Technical Acquisition Speech Corpus took 2.2372186183929443s
Consistency | Check Invalid usage of undefined classes for ROBIN Technical Acquisition Speech Corpus took 1.4972591400146484s
Consistency | Check Invalid usage of undefined properties for ROBIN Technical Acquisition Speech Corpus took 1.860123872756958s
Conciseness | Check Extensional conciseness for ROBIN Technical Acquisition Speech Corpus took 0.8461117744445801s
Security | Sign check for ROBIN Technical Acquisition Speech Corpus took 0.15394091606140137s
Availability | Check URIs Dereferenciability for ROBIN Technical Acquisition Speech Corpus took 7.206973552703857s
Completeness | Calculation of interlinking completeness for ROBIN Technical Acquisition Speech Corpus took 0.3097255229949951s
Reputation | Calculation of the PageRank for ROBIN Technical Acquisition Speech Corpus took 0.020749568939208984s
Interlinking | Calculation of Degree of Connection for ROBIN Technical Acquisition Speech Corpus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ROBIN Technical Acquisition Speech Corpus took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for ROBIN Technical Acquisition Speech Corpus took 3.457069396972656e-05s
Interoperability | Check the re-using of existing vocabs for ROBIN Technical Acquisition Speech Corpus took 1.430511474609375e-06s
Believability | Calculation of trust value for ROBIN Technical Acquisition Speech Corpus took 1.4781951904296875e-05s
INFO | --- Analysis for racai-llod-rtasc took 64.08002233505249s
Availability | SPARQL endpoint availability check for SiMoNERo - the Romanian medical treebank took 0.1319568157196045s
Availability | VoID file availability check for SiMoNERo - the Romanian medical treebank took 0.0006654262542724609s
Extra | Recovery of all triples for SiMoNERo - the Romanian medical treebank took 34.52468419075012s
Performance | Total latancy measurement for SiMoNERo - the Romanian medical treebank took 0.7032759189605713s
Amount of data | Number of triples check for SiMoNERo - the Romanian medical treebank took 1.0983219146728516s
Interoperability | New terms check for SiMoNERo - the Romanian medical treebank took 1.69820237159729s
Versatility | Languages check for SiMoNERo - the Romanian medical treebank took 2.442971706390381s
Interpretability | Number of blank nodes check for SiMoNERo - the Romanian medical treebank took 0.7815206050872803s
Interpretability | RDF structures check for SiMoNERo - the Romanian medical treebank took 0.14183664321899414s
Versatility | Serialization formats check for SiMoNERo - the Romanian medical treebank took 0.1526038646697998s
Availability | RDF dump link check for SiMoNERo - the Romanian medical treebank took 0.13938355445861816s
License | MR license check for SiMoNERo - the Romanian medical treebank took 0.14107394218444824s
License | HR license check for SiMoNERo - the Romanian medical treebank took 4.638838768005371s
Amount of data | Number of property check for SiMoNERo - the Romanian medical treebank took 0.1403491497039795s
Understandability | Number of label check for SiMoNERo - the Romanian medical treebank took 0.13452792167663574s
Understandability | URI regex check for SiMoNERo - the Romanian medical treebank took 0.28041839599609375s
Understandability | Vocabs check for SiMoNERo - the Romanian medical treebank took 0.12979531288146973s
Verifiability | Authors check for SiMoNERo - the Romanian medical treebank took 0.14346957206726074s
Verifiability | Publishers check for SiMoNERo - the Romanian medical treebank took 0.14346027374267578s
Performance | Throughput check for SiMoNERo - the Romanian medical treebank took 11.039128065109253s
Amount of data | Check the number of entities for SiMoNERo - the Romanian medical treebank took 0.00011110305786132812s
Verifiability | Contribs. check for SiMoNERo - the Romanian medical treebank took 0.1517777442932129s
Interlinking | sameAs chians check for SiMoNERo - the Romanian medical treebank took 0.13010549545288086s
Interlinking | skos check for SiMoNERo - the Romanian medical treebank took 0.15274691581726074s
Interlinking | skos check for SiMoNERo - the Romanian medical treebank took 0.13022112846374512s
Timeliness | dataset update frequency check for SiMoNERo - the Romanian medical treebank took 0.15371227264404297s
Currency | Creation date check for SiMoNERo - the Romanian medical treebank took 0.28443479537963867s
Currency | Modification date check for SiMoNERo - the Romanian medical treebank took 0.2938356399536133s
Rep.Conc. | URIs length for SiMoNERo - the Romanian medical treebank took 9.285329103469849s
Interoperability | New vocabularies check for SiMoNERo - the Romanian medical treebank took 1.1682510375976562e-05s
Consistency | Deprecated classes/propertiers check for SiMoNERo - the Romanian medical treebank took 0.15279293060302734s
Accuracy | Check Functional Property for SiMoNERo - the Romanian medical treebank took 0.14187169075012207s
Accuracy | Check Inverse Functional Property for SiMoNERo - the Romanian medical treebank took 0.14155149459838867s
Accuracy | Check Empty annotation labels for SiMoNERo - the Romanian medical treebank took 0.7597403526306152s
Accuracy | Check White space in annotation for SiMoNERo - the Romanian medical treebank took 0.0191342830657959s
Accuracy | Check Datatype consistency for SiMoNERo - the Romanian medical treebank took 4.152251958847046s
Consistency | Disjoint class check for SiMoNERo - the Romanian medical treebank took 0.13223576545715332s
Consistency | Check Misplaced properties for SiMoNERo - the Romanian medical treebank took 1.7443835735321045s
Consistency | Check Ontology hijacking for SiMoNERo - the Romanian medical treebank took 4.783440589904785s
Consistency | Check Invalid usage of undefined classes for SiMoNERo - the Romanian medical treebank took 1.523498296737671s
Consistency | Check Invalid usage of undefined properties for SiMoNERo - the Romanian medical treebank took 3.067833423614502s
Conciseness | Check Extensional conciseness for SiMoNERo - the Romanian medical treebank took 2.9687979221343994s
Security | Sign check for SiMoNERo - the Romanian medical treebank took 0.14229130744934082s
Availability | Check URIs Dereferenciability for SiMoNERo - the Romanian medical treebank took 1539.6691544055939s
Completeness | Calculation of interlinking completeness for SiMoNERo - the Romanian medical treebank took 0.5584757328033447s
Reputation | Calculation of the PageRank for SiMoNERo - the Romanian medical treebank took 0.021753787994384766s
Interlinking | Calculation of Degree of Connection for SiMoNERo - the Romanian medical treebank took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for SiMoNERo - the Romanian medical treebank took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for SiMoNERo - the Romanian medical treebank took 5.3882598876953125e-05s
Interoperability | Check the re-using of existing vocabs for SiMoNERo - the Romanian medical treebank took 3.337860107421875e-06s
Believability | Calculation of trust value for SiMoNERo - the Romanian medical treebank took 1.5974044799804688e-05s
INFO | --- Analysis for racai-llod-simonero took 1645.8744242191315s
Availability | SPARQL endpoint availability check for Rådata nå! took 0.11149716377258301s
Availability | VoID file availability check for Rådata nå! took 0.0006759166717529297s
Completeness | Calculation of interlinking completeness for Rådata nå! took 0.29142332077026367s
Reputation | Calculation of the PageRank for Rådata nå! took 0.020679473876953125s
Interlinking | Calculation of Degree of Connection for Rådata nå! took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Rådata nå! took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Rådata nå! took 8.440017700195312e-05s
Believability | Calculation of trust value for Rådata nå! took 1.2874603271484375e-05s
INFO | --- Analysis for radatana took 4.650649547576904s
Availability | SPARQL endpoint availability check for "Rainis and Aspazija" Linked Digital Collection took 0.00010180473327636719s
Availability | VoID file availability check for "Rainis and Aspazija" Linked Digital Collection took 0.0008053779602050781s
Completeness | Calculation of interlinking completeness for "Rainis and Aspazija" Linked Digital Collection took 0.27414965629577637s
Reputation | Calculation of the PageRank for "Rainis and Aspazija" Linked Digital Collection took 0.021173715591430664s
Interlinking | Calculation of Degree of Connection for "Rainis and Aspazija" Linked Digital Collection took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for "Rainis and Aspazija" Linked Digital Collection took 0.0008006095886230469s
Interlinking | Calculation of Clustering coefficient for "Rainis and Aspazija" Linked Digital Collection took 4.792213439941406e-05s
Believability | Calculation of trust value for "Rainis and Aspazija" Linked Digital Collection took 1.3828277587890625e-05s
INFO | --- Analysis for rainis-and-aspazija-linked-digital-collection took 17.4120876789093s
Availability | SPARQL endpoint availability check for Ravensburg Local Shopping Graph took 12.643434524536133s
Availability | VoID file availability check for Ravensburg Local Shopping Graph took 0.0006489753723144531s
Completeness | Calculation of interlinking completeness for Ravensburg Local Shopping Graph took 0.2796463966369629s
Reputation | Calculation of the PageRank for Ravensburg Local Shopping Graph took 0.02167963981628418s
Interlinking | Calculation of Degree of Connection for Ravensburg Local Shopping Graph took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Ravensburg Local Shopping Graph took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Ravensburg Local Shopping Graph took 3.5762786865234375e-05s
Believability | Calculation of trust value for Ravensburg Local Shopping Graph took 1.430511474609375e-05s
INFO | --- Analysis for ravensburg-local-shopping-graph took 27.571080684661865s
Availability | SPARQL endpoint availability check for Polish LGU financial statements took 392.2423768043518s
Availability | VoID file availability check for Polish LGU financial statements took 0.0002765655517578125s
Completeness | Calculation of interlinking completeness for Polish LGU financial statements took 0.3011324405670166s
Reputation | Calculation of the PageRank for Polish LGU financial statements took 0.021152734756469727s
Interlinking | Calculation of Degree of Connection for Polish LGU financial statements took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Polish LGU financial statements took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Polish LGU financial statements took 4.3392181396484375e-05s
Believability | Calculation of trust value for Polish LGU financial statements took 9.298324584960938e-06s
INFO | --- Analysis for Rb_PL_LGU took 667.2783496379852s
Availability | SPARQL endpoint availability check for RDF Book Mashup took 4.57763671875e-05s
Availability | VoID file availability check for RDF Book Mashup took 0.0006003379821777344s
Completeness | Calculation of interlinking completeness for RDF Book Mashup took 0.2945218086242676s
Reputation | Calculation of the PageRank for RDF Book Mashup took 0.02142810821533203s
Interlinking | Calculation of Degree of Connection for RDF Book Mashup took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for RDF Book Mashup took 0.0008502006530761719s
Interlinking | Calculation of Clustering coefficient for RDF Book Mashup took 9.5367431640625e-05s
Believability | Calculation of trust value for RDF Book Mashup took 1.7881393432617188e-05s
INFO | --- Analysis for rdf-book-mashup took 3.597327709197998s
Availability | SPARQL endpoint availability check for Last.FM RDFization of Events, Artists, and Users took 9.34600830078125e-05s
Availability | VoID file availability check for Last.FM RDFization of Events, Artists, and Users took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for Last.FM RDFization of Events, Artists, and Users took 0.2985701560974121s
Reputation | Calculation of the PageRank for Last.FM RDFization of Events, Artists, and Users took 0.02114248275756836s
Interlinking | Calculation of Degree of Connection for Last.FM RDFization of Events, Artists, and Users took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Last.FM RDFization of Events, Artists, and Users took 0.0007827281951904297s
Interlinking | Calculation of Clustering coefficient for Last.FM RDFization of Events, Artists, and Users took 0.00010967254638671875s
Believability | Calculation of trust value for Last.FM RDFization of Events, Artists, and Users took 1.52587890625e-05s
INFO | --- Analysis for rdfize-lastfm took 2.8052875995635986s
Availability | SPARQL endpoint availability check for RDFLicense took 260.8227880001068s
Availability | VoID file availability check for RDFLicense took 0.0005869865417480469s
Completeness | Calculation of interlinking completeness for RDFLicense took 0.309417724609375s
Reputation | Calculation of the PageRank for RDFLicense took 0.021289825439453125s
Interlinking | Calculation of Degree of Connection for RDFLicense took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for RDFLicense took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for RDFLicense took 5.221366882324219e-05s
Believability | Calculation of trust value for RDFLicense took 1.5020370483398438e-05s
INFO | --- Analysis for rdflicense took 535.8298301696777s
Availability | SPARQL endpoint availability check for RDFohloh took 4.5299530029296875e-05s
Availability | VoID file availability check for RDFohloh took 0.0006859302520751953s
Completeness | Calculation of interlinking completeness for RDFohloh took 0.3126709461212158s
Reputation | Calculation of the PageRank for RDFohloh took 0.021623611450195312s
Interlinking | Calculation of Degree of Connection for RDFohloh took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for RDFohloh took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for RDFohloh took 0.00010037422180175781s
Believability | Calculation of trust value for RDFohloh took 1.52587890625e-05s
INFO | --- Analysis for rdfohloh took 7.230128288269043s
Availability | SPARQL endpoint availability check for Reactome RDF took 0.6710958480834961s
Availability | VoID file availability check for Reactome RDF took 0.0006389617919921875s
Completeness | Calculation of interlinking completeness for Reactome RDF took 0.2920048236846924s
Reputation | Calculation of the PageRank for Reactome RDF took 0.02094125747680664s
Interlinking | Calculation of Degree of Connection for Reactome RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Reactome RDF took 0.0007774829864501953s
Interlinking | Calculation of Clustering coefficient for Reactome RDF took 4.315376281738281e-05s
Believability | Calculation of trust value for Reactome RDF took 1.4781951904296875e-05s
INFO | --- Analysis for reactome-rdf took 4.107395887374878s
Availability | SPARQL endpoint availability check for Rechtspraak.nl took 0.11269330978393555s
Availability | VoID file availability check for Rechtspraak.nl took 0.00028324127197265625s
Completeness | Calculation of interlinking completeness for Rechtspraak.nl took 0.3266780376434326s
Reputation | Calculation of the PageRank for Rechtspraak.nl took 0.02073216438293457s
Interlinking | Calculation of Degree of Connection for Rechtspraak.nl took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Rechtspraak.nl took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Rechtspraak.nl took 0.00010347366333007812s
Believability | Calculation of trust value for Rechtspraak.nl took 7.152557373046875e-06s
INFO | --- Analysis for rechtspraak took 2.9394826889038086s
Availability | SPARQL endpoint availability check for Red Uno Internacional (Santillana) took 9.918212890625e-05s
Availability | VoID file availability check for Red Uno Internacional (Santillana) took 0.0007355213165283203s
Completeness | Calculation of interlinking completeness for Red Uno Internacional (Santillana) took 0.30626964569091797s
Reputation | Calculation of the PageRank for Red Uno Internacional (Santillana) took 0.021182537078857422s
Interlinking | Calculation of Degree of Connection for Red Uno Internacional (Santillana) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Red Uno Internacional (Santillana) took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Red Uno Internacional (Santillana) took 9.584426879882812e-05s
Believability | Calculation of trust value for Red Uno Internacional (Santillana) took 1.52587890625e-05s
INFO | --- Analysis for red-uno-internacional-santillana took 9.1742684841156s
Availability | SPARQL endpoint availability check for reference.data.gov.uk took 0.05269622802734375s
Availability | VoID file availability check for reference.data.gov.uk took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for reference.data.gov.uk took 0.28731417655944824s
Reputation | Calculation of the PageRank for reference.data.gov.uk took 0.020864009857177734s
Interlinking | Calculation of Degree of Connection for reference.data.gov.uk took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for reference.data.gov.uk took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for reference.data.gov.uk took 0.0001685619354248047s
Believability | Calculation of trust value for reference.data.gov.uk took 1.1444091796875e-05s
INFO | --- Analysis for reference-data-gov-uk took 2.935410261154175s
Availability | SPARQL endpoint availability check for RELD took 0.6827130317687988s
Availability | VoID file availability check for RELD took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for RELD took 0.27704334259033203s
Reputation | Calculation of the PageRank for RELD took 0.02071523666381836s
Interlinking | Calculation of Degree of Connection for RELD took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RELD took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for RELD took 3.457069396972656e-05s
Believability | Calculation of trust value for RELD took 1.33514404296875e-05s
INFO | --- Analysis for RELD took 4.081824541091919s
Availability | SPARQL endpoint availability check for Repository for Linked Open Archival Data took 0.20224928855895996s
Availability | VoID file availability check for Repository for Linked Open Archival Data took 0.0007908344268798828s
Extra | Recovery of all triples for Repository for Linked Open Archival Data took 1.1346583366394043s
Performance | Total latancy measurement for Repository for Linked Open Archival Data took 0.4353172779083252s
Amount of data | Number of triples check for Repository for Linked Open Archival Data took 1.309096097946167s
Interoperability | New terms check for Repository for Linked Open Archival Data took 1.8045997619628906s
Versatility | Languages check for Repository for Linked Open Archival Data took 18.659379482269287s
Interpretability | Number of blank nodes check for Repository for Linked Open Archival Data took 11.93790054321289s
Security | Check HTTPS for Repository for Linked Open Archival Data took 0.22600722312927246s
Interpretability | RDF structures check for Repository for Linked Open Archival Data took 0.2048947811126709s
Versatility | Serialization formats check for Repository for Linked Open Archival Data took 0.22083282470703125s
Availability | RDF dump link check for Repository for Linked Open Archival Data took 0.13405942916870117s
License | MR license check for Repository for Linked Open Archival Data took 0.3005537986755371s
License | HR license check for Repository for Linked Open Archival Data took 8.379858255386353s
Amount of data | Number of property check for Repository for Linked Open Archival Data took 0.13302397727966309s
Understandability | Number of label check for Repository for Linked Open Archival Data took 0.8048021793365479s
Understandability | URI regex check for Repository for Linked Open Archival Data took 0.3392174243927002s
Understandability | Vocabs check for Repository for Linked Open Archival Data took 0.11084532737731934s
Verifiability | Authors check for Repository for Linked Open Archival Data took 0.12473225593566895s
Verifiability | Publishers check for Repository for Linked Open Archival Data took 0.1537320613861084s
Performance | Throughput check for Repository for Linked Open Archival Data took 10.299262523651123s
Amount of data | Check the number of entities for Repository for Linked Open Archival Data took 7.987022399902344e-05s
Verifiability | Contribs. check for Repository for Linked Open Archival Data took 0.10329890251159668s
Interlinking | sameAs chians check for Repository for Linked Open Archival Data took 0.12461233139038086s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.18226122856140137s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.06614255905151367s
Timeliness | dataset update frequency check for Repository for Linked Open Archival Data took 0.1995530128479004s
Currency | Creation date check for Repository for Linked Open Archival Data took 0.1887214183807373s
Currency | Modification date check for Repository for Linked Open Archival Data took 0.15449285507202148s
Rep.Conc. | URIs length for Repository for Linked Open Archival Data took 2.704235553741455s
Interoperability | New vocabularies check for Repository for Linked Open Archival Data took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Repository for Linked Open Archival Data took 0.1105341911315918s
Accuracy | Check Functional Property for Repository for Linked Open Archival Data took 0.12355756759643555s
Accuracy | Check Inverse Functional Property for Repository for Linked Open Archival Data took 0.0777730941772461s
Accuracy | Check Empty annotation labels for Repository for Linked Open Archival Data took 0.34410929679870605s
Accuracy | Check White space in annotation for Repository for Linked Open Archival Data took 0.02795100212097168s
Accuracy | Check Datatype consistency for Repository for Linked Open Archival Data took 0.029073476791381836s
Consistency | Disjoint class check for Repository for Linked Open Archival Data took 0.1688370704650879s
Consistency | Check Misplaced properties for Repository for Linked Open Archival Data took 1.8830406665802002s
Consistency | Misplaced classes for Repository for Linked Open Archival Data took 0.1820688247680664s
Consistency | Check Ontology hijacking for Repository for Linked Open Archival Data took 1.8220837116241455s
Consistency | Check Invalid usage of undefined classes for Repository for Linked Open Archival Data took 1.4411978721618652s
Consistency | Check Invalid usage of undefined properties for Repository for Linked Open Archival Data took 3.7036921977996826s
Conciseness | Check Extensional conciseness for Repository for Linked Open Archival Data took 0.03469109535217285s
Conciseness | Check Intensional conciseness for Repository for Linked Open Archival Data took 0.14613604545593262s
Security | Sign check for Repository for Linked Open Archival Data took 0.34972047805786133s
Availability | Check URIs Dereferenciability for Repository for Linked Open Archival Data took 1021.7513341903687s
Completeness | Calculation of interlinking completeness for Repository for Linked Open Archival Data took 0.5837225914001465s
Reputation | Calculation of the PageRank for Repository for Linked Open Archival Data took 0.026341915130615234s
Interlinking | Calculation of Degree of Connection for Repository for Linked Open Archival Data took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for Repository for Linked Open Archival Data took 0.0008893013000488281s
Interlinking | Calculation of Clustering coefficient for Repository for Linked Open Archival Data took 0.00011110305786132812s
Interoperability | Check the re-using of existing vocabs for Repository for Linked Open Archival Data took 2.6226043701171875e-06s
Believability | Calculation of trust value for Repository for Linked Open Archival Data took 1.4781951904296875e-05s
INFO | --- Analysis for reload took 1156.338101863861s
Availability | SPARQL endpoint availability check for Land use merced dataset took 4.3392181396484375e-05s
Availability | VoID file availability check for Land use merced dataset took 0.0005476474761962891s
Completeness | Calculation of interlinking completeness for Land use merced dataset took 0.2851428985595703s
Reputation | Calculation of the PageRank for Land use merced dataset took 0.02110457420349121s
Interlinking | Calculation of Degree of Connection for Land use merced dataset took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Land use merced dataset took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Land use merced dataset took 3.409385681152344e-05s
Believability | Calculation of trust value for Land use merced dataset took 1.4781951904296875e-05s
INFO | --- Analysis for remote_Sensing took 3.4107210636138916s
Availability | SPARQL endpoint availability check for Renewable Energy Generators took 1.9546818733215332s
Availability | VoID file availability check for Renewable Energy Generators took 0.0006132125854492188s
Completeness | Calculation of interlinking completeness for Renewable Energy Generators took 0.28859734535217285s
Reputation | Calculation of the PageRank for Renewable Energy Generators took 0.020932912826538086s
Interlinking | Calculation of Degree of Connection for Renewable Energy Generators took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Renewable Energy Generators took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Renewable Energy Generators took 4.8160552978515625e-05s
Believability | Calculation of trust value for Renewable Energy Generators took 9.775161743164062e-06s
INFO | --- Analysis for renewable_energy_generators took 12.381478071212769s
Availability | SPARQL endpoint availability check for research.data.gov.uk took 0.05361294746398926s
Availability | VoID file availability check for research.data.gov.uk took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for research.data.gov.uk took 0.3154110908508301s
Reputation | Calculation of the PageRank for research.data.gov.uk took 0.020816802978515625s
Interlinking | Calculation of Degree of Connection for research.data.gov.uk took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for research.data.gov.uk took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for research.data.gov.uk took 9.775161743164062e-05s
Believability | Calculation of trust value for research.data.gov.uk took 9.298324584960938e-06s
INFO | --- Analysis for research-data-gov-uk took 2.802917718887329s
Availability | SPARQL endpoint availability check for Reuters-128 NIF NER Corpus took 9.298324584960938e-05s
Availability | VoID file availability check for Reuters-128 NIF NER Corpus took 0.0006062984466552734s
Completeness | Calculation of interlinking completeness for Reuters-128 NIF NER Corpus took 0.3187062740325928s
Reputation | Calculation of the PageRank for Reuters-128 NIF NER Corpus took 0.023159503936767578s
Interlinking | Calculation of Degree of Connection for Reuters-128 NIF NER Corpus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Reuters-128 NIF NER Corpus took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Reuters-128 NIF NER Corpus took 7.081031799316406e-05s
Believability | Calculation of trust value for Reuters-128 NIF NER Corpus took 1.4066696166992188e-05s
INFO | --- Analysis for reuters-128-nif-ner-corpus took 4.408398866653442s
Availability | SPARQL endpoint availability check for Revista Excelencias Turísticas took 0.04861259460449219s
Availability | VoID file availability check for Revista Excelencias Turísticas took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for Revista Excelencias Turísticas took 0.30582547187805176s
Reputation | Calculation of the PageRank for Revista Excelencias Turísticas took 0.021611928939819336s
Interlinking | Calculation of Degree of Connection for Revista Excelencias Turísticas took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Revista Excelencias Turísticas took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Revista Excelencias Turísticas took 3.4809112548828125e-05s
Believability | Calculation of trust value for Revista Excelencias Turísticas took 1.4066696166992188e-05s
INFO | --- Analysis for revistas_turismo took 2.8453142642974854s
Availability | SPARQL endpoint availability check for Revyu.com - Review Anything took 0.28485822677612305s
Availability | VoID file availability check for Revyu.com - Review Anything took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for Revyu.com - Review Anything took 0.28183579444885254s
Reputation | Calculation of the PageRank for Revyu.com - Review Anything took 0.020678997039794922s
Interlinking | Calculation of Degree of Connection for Revyu.com - Review Anything took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Revyu.com - Review Anything took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Revyu.com - Review Anything took 0.00011873245239257812s
Believability | Calculation of trust value for Revyu.com - Review Anything took 1.430511474609375e-05s
INFO | --- Analysis for revyu took 3.172477960586548s
Availability | SPARQL endpoint availability check for sdafsadf took 0.24796843528747559s
Availability | VoID file availability check for sdafsadf took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for sdafsadf took 0.337421178817749s
Reputation | Calculation of the PageRank for sdafsadf took 0.02086162567138672s
Interlinking | Calculation of Degree of Connection for sdafsadf took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for sdafsadf took 0.0007905960083007812s
Interlinking | Calculation of Clustering coefficient for sdafsadf took 3.457069396972656e-05s
Believability | Calculation of trust value for sdafsadf took 1.3828277587890625e-05s
INFO | --- Analysis for rgsdfg took 3.1407668590545654s
Availability | SPARQL endpoint availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 9.822845458984375e-05s
Availability | VoID file availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0007939338684082031s
Completeness | Calculation of interlinking completeness for RDFizing and Interlinking the EuroStat Data Set Effort took 0.26839661598205566s
Reputation | Calculation of the PageRank for RDFizing and Interlinking the EuroStat Data Set Effort took 0.020862817764282227s
Interlinking | Calculation of Degree of Connection for RDFizing and Interlinking the EuroStat Data Set Effort took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for RDFizing and Interlinking the EuroStat Data Set Effort took 5.602836608886719e-05s
Believability | Calculation of trust value for RDFizing and Interlinking the EuroStat Data Set Effort took 1.2874603271484375e-05s
INFO | --- Analysis for riese took 22.940589666366577s
Availability | SPARQL endpoint availability check for Répertoire International des Sources Musicales - RISM took 0.2704493999481201s
Availability | VoID file availability check for Répertoire International des Sources Musicales - RISM took 0.0006957054138183594s
Extra | Recovery of all triples for Répertoire International des Sources Musicales - RISM took 23.57537055015564s
Performance | Total latancy measurement for Répertoire International des Sources Musicales - RISM took 0.5061910152435303s
Amount of data | Number of triples check for Répertoire International des Sources Musicales - RISM took 51.913209199905396s
Interoperability | New terms check for Répertoire International des Sources Musicales - RISM took 2.1308035850524902s
Versatility | Languages check for Répertoire International des Sources Musicales - RISM took 148.2676727771759s
Interpretability | Number of blank nodes check for Répertoire International des Sources Musicales - RISM took 46.623366355895996s
Security | Check HTTPS for Répertoire International des Sources Musicales - RISM took 0.24378252029418945s
Interpretability | RDF structures check for Répertoire International des Sources Musicales - RISM took 0.14664340019226074s
Versatility | Serialization formats check for Répertoire International des Sources Musicales - RISM took 0.148956298828125s
Availability | RDF dump link check for Répertoire International des Sources Musicales - RISM took 0.10576915740966797s
License | MR license check for Répertoire International des Sources Musicales - RISM took 0.13752532005310059s
License | HR license check for Répertoire International des Sources Musicales - RISM took 300.10400891304016s
Amount of data | Number of property check for Répertoire International des Sources Musicales - RISM took 0.12506651878356934s
Understandability | Number of label check for Répertoire International des Sources Musicales - RISM took 7.678137302398682s
Understandability | URI regex check for Répertoire International des Sources Musicales - RISM took 0.24010252952575684s
Understandability | Vocabs check for Répertoire International des Sources Musicales - RISM took 0.10856366157531738s
Verifiability | Authors check for Répertoire International des Sources Musicales - RISM took 0.12281632423400879s
Verifiability | Publishers check for Répertoire International des Sources Musicales - RISM took 0.09275150299072266s
Performance | Throughput check for Répertoire International des Sources Musicales - RISM took 10.683217287063599s
Amount of data | Check the number of entities for Répertoire International des Sources Musicales - RISM took 0.0001373291015625s
Verifiability | Contribs. check for Répertoire International des Sources Musicales - RISM took 0.10933685302734375s
Interlinking | sameAs chians check for Répertoire International des Sources Musicales - RISM took 1.1633381843566895s
Interlinking | skos check for Répertoire International des Sources Musicales - RISM took 0.16071152687072754s
Interlinking | skos check for Répertoire International des Sources Musicales - RISM took 0.11062264442443848s
Timeliness | dataset update frequency check for Répertoire International des Sources Musicales - RISM took 0.08775115013122559s
Currency | Creation date check for Répertoire International des Sources Musicales - RISM took 0.23578858375549316s
Currency | Modification date check for Répertoire International des Sources Musicales - RISM took 0.24777579307556152s
Rep.Conc. | URIs length for Répertoire International des Sources Musicales - RISM took 73.63663148880005s
Interoperability | New vocabularies check for Répertoire International des Sources Musicales - RISM took 1.2874603271484375e-05s
Consistency | Deprecated classes/propertiers check for Répertoire International des Sources Musicales - RISM took 0.15694832801818848s
Accuracy | Check Functional Property for Répertoire International des Sources Musicales - RISM took 0.12198925018310547s
Accuracy | Check Inverse Functional Property for Répertoire International des Sources Musicales - RISM took 0.11456656455993652s
Accuracy | Check Empty annotation labels for Répertoire International des Sources Musicales - RISM took 16.592777729034424s
Accuracy | Check White space in annotation for Répertoire International des Sources Musicales - RISM took 2.42854642868042s
Accuracy | Check Datatype consistency for Répertoire International des Sources Musicales - RISM took 3.9104502201080322s
Consistency | Disjoint class check for Répertoire International des Sources Musicales - RISM took 0.10801339149475098s
Consistency | Check Misplaced properties for Répertoire International des Sources Musicales - RISM took 45.44373393058777s
Consistency | Check Ontology hijacking for Répertoire International des Sources Musicales - RISM took 5.234084844589233s
Consistency | Check Invalid usage of undefined classes for Répertoire International des Sources Musicales - RISM took 1.5876548290252686s
Consistency | Check Invalid usage of undefined properties for Répertoire International des Sources Musicales - RISM took 46.462361335754395s
Conciseness | Check Extensional conciseness for Répertoire International des Sources Musicales - RISM took 2.8409624099731445s
Security | Sign check for Répertoire International des Sources Musicales - RISM took 0.1117713451385498s
Availability | Check URIs Dereferenciability for Répertoire International des Sources Musicales - RISM took 1.341024398803711s
Completeness | Calculation of interlinking completeness for Répertoire International des Sources Musicales - RISM took 0.47307491302490234s
Reputation | Calculation of the PageRank for Répertoire International des Sources Musicales - RISM took 0.021605730056762695s
Interlinking | Calculation of Degree of Connection for Répertoire International des Sources Musicales - RISM took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for Répertoire International des Sources Musicales - RISM took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Répertoire International des Sources Musicales - RISM took 7.033348083496094e-05s
Interoperability | Check the re-using of existing vocabs for Répertoire International des Sources Musicales - RISM took 2.1457672119140625e-06s
Believability | Calculation of trust value for Répertoire International des Sources Musicales - RISM took 1.6927719116210938e-05s
INFO | --- Analysis for rism took 1213.5052111148834s
Availability | SPARQL endpoint availability check for RISM Authority data took 0.09398365020751953s
Availability | VoID file availability check for RISM Authority data took 0.0006463527679443359s
Extra | Recovery of all triples for RISM Authority data took 23.494728565216064s
Performance | Total latancy measurement for RISM Authority data took 0.5122711658477783s
Amount of data | Number of triples check for RISM Authority data took 51.19449830055237s
Interoperability | New terms check for RISM Authority data took 1.7135391235351562s
Versatility | Languages check for RISM Authority data took 300.0551025867462s
Interpretability | Number of blank nodes check for RISM Authority data took 46.322176456451416s
Security | Check HTTPS for RISM Authority data took 0.1445603370666504s
Interpretability | RDF structures check for RISM Authority data took 0.13622665405273438s
Versatility | Serialization formats check for RISM Authority data took 0.12229037284851074s
Availability | RDF dump link check for RISM Authority data took 0.10280990600585938s
License | MR license check for RISM Authority data took 0.13939452171325684s
License | HR license check for RISM Authority data took 300.0235574245453s
Amount of data | Number of property check for RISM Authority data took 0.12579107284545898s
Understandability | Number of label check for RISM Authority data took 6.4503912925720215s
Understandability | URI regex check for RISM Authority data took 0.24117350578308105s
Understandability | Vocabs check for RISM Authority data took 0.10224652290344238s
Verifiability | Authors check for RISM Authority data took 0.10001897811889648s
Verifiability | Publishers check for RISM Authority data took 0.11292576789855957s
Performance | Throughput check for RISM Authority data took 10.504638195037842s
Amount of data | Check the number of entities for RISM Authority data took 8.749961853027344e-05s
Verifiability | Contribs. check for RISM Authority data took 0.1019899845123291s
Interlinking | sameAs chians check for RISM Authority data took 1.1762478351593018s
Interlinking | skos check for RISM Authority data took 0.1258258819580078s
Interlinking | skos check for RISM Authority data took 0.11167764663696289s
Timeliness | dataset update frequency check for RISM Authority data took 0.10465407371520996s
Currency | Creation date check for RISM Authority data took 0.21770215034484863s
Currency | Modification date check for RISM Authority data took 0.22243547439575195s
Rep.Conc. | URIs length for RISM Authority data took 73.58861517906189s
Interoperability | New vocabularies check for RISM Authority data took 1.3589859008789062e-05s
Consistency | Deprecated classes/propertiers check for RISM Authority data took 0.11531543731689453s
Accuracy | Check Functional Property for RISM Authority data took 0.11774802207946777s
Accuracy | Check Inverse Functional Property for RISM Authority data took 0.09495329856872559s
Accuracy | Check Empty annotation labels for RISM Authority data took 12.841214418411255s
Accuracy | Check White space in annotation for RISM Authority data took 2.434828996658325s
Accuracy | Check Datatype consistency for RISM Authority data took 3.988220691680908s
Consistency | Disjoint class check for RISM Authority data took 0.09137964248657227s
Consistency | Check Misplaced properties for RISM Authority data took 46.09600114822388s
Consistency | Check Ontology hijacking for RISM Authority data took 5.269968509674072s
Consistency | Check Invalid usage of undefined classes for RISM Authority data took 1.5703020095825195s
Consistency | Check Invalid usage of undefined properties for RISM Authority data took 47.075063943862915s
Conciseness | Check Extensional conciseness for RISM Authority data took 2.977083683013916s
Security | Sign check for RISM Authority data took 0.11344671249389648s
Availability | Check URIs Dereferenciability for RISM Authority data took 1.3687331676483154s
Completeness | Calculation of interlinking completeness for RISM Authority data took 0.7571840286254883s
Reputation | Calculation of the PageRank for RISM Authority data took 0.021728992462158203s
Interlinking | Calculation of Degree of Connection for RISM Authority data took 2.4557113647460938e-05s
Interlinking | Calculation of Centrality for RISM Authority data took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for RISM Authority data took 6.532669067382812e-05s
Interoperability | Check the re-using of existing vocabs for RISM Authority data took 2.6226043701171875e-06s
Believability | Calculation of trust value for RISM Authority data took 1.1205673217773438e-05s
INFO | --- Analysis for rism-authorities took 1366.4066371917725s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 4.673004150390625e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.0005660057067871094s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.3167552947998047s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.021880388259887695s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 4.029273986816406e-05s
Believability | Calculation of trust value for engineering equipment ontology took 1.4781951904296875e-05s
INFO | --- Analysis for rk took 2.674083709716797s
Availability | SPARQL endpoint availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.06595540046691895s
Availability | VoID file availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for Association for Computing Machinery (ACM) (RKBExplorer) took 0.28553342819213867s
Reputation | Calculation of the PageRank for Association for Computing Machinery (ACM) (RKBExplorer) took 0.021482467651367188s
Interlinking | Calculation of Degree of Connection for Association for Computing Machinery (ACM) (RKBExplorer) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Association for Computing Machinery (ACM) (RKBExplorer) took 0.00024056434631347656s
Believability | Calculation of trust value for Association for Computing Machinery (ACM) (RKBExplorer) took 1.52587890625e-05s
INFO | --- Analysis for rkb-explorer-acm took 2.792792558670044s
Availability | SPARQL endpoint availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.04159259796142578s
Availability | VoID file availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for Budapest University of Technology and Economics (RKBExplorer) took 0.33846616744995117s
Reputation | Calculation of the PageRank for Budapest University of Technology and Economics (RKBExplorer) took 0.021126270294189453s
Interlinking | Calculation of Degree of Connection for Budapest University of Technology and Economics (RKBExplorer) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Budapest University of Technology and Economics (RKBExplorer) took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Budapest University of Technology and Economics (RKBExplorer) took 0.0001499652862548828s
Believability | Calculation of trust value for Budapest University of Technology and Economics (RKBExplorer) took 1.4543533325195312e-05s
INFO | --- Analysis for rkb-explorer-budapest took 2.7469539642333984s
Availability | SPARQL endpoint availability check for CiteSeer (Research Index) (RKBExplorer) took 0.0398557186126709s
Availability | VoID file availability check for CiteSeer (Research Index) (RKBExplorer) took 0.0005838871002197266s
Completeness | Calculation of interlinking completeness for CiteSeer (Research Index) (RKBExplorer) took 0.27901411056518555s
Reputation | Calculation of the PageRank for CiteSeer (Research Index) (RKBExplorer) took 0.021042346954345703s
Interlinking | Calculation of Degree of Connection for CiteSeer (Research Index) (RKBExplorer) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for CiteSeer (Research Index) (RKBExplorer) took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for CiteSeer (Research Index) (RKBExplorer) took 0.000202178955078125s
Believability | Calculation of trust value for CiteSeer (Research Index) (RKBExplorer) took 1.5735626220703125e-05s
INFO | --- Analysis for rkb-explorer-citeseer took 2.731172800064087s
Availability | SPARQL endpoint availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.03807568550109863s
Availability | VoID file availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0004324913024902344s
Completeness | Calculation of interlinking completeness for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.32291698455810547s
Reputation | Calculation of the PageRank for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.020700454711914062s
Interlinking | Calculation of Degree of Connection for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0001704692840576172s
Believability | Calculation of trust value for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.3589859008789062e-05s
INFO | --- Analysis for rkb-explorer-cordis took 2.7808425426483154s
Availability | SPARQL endpoint availability check for Resilient Computing Courseware (RKBExplorer) took 0.03719806671142578s
Availability | VoID file availability check for Resilient Computing Courseware (RKBExplorer) took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for Resilient Computing Courseware (RKBExplorer) took 0.27691221237182617s
Reputation | Calculation of the PageRank for Resilient Computing Courseware (RKBExplorer) took 0.023752212524414062s
Interlinking | Calculation of Degree of Connection for Resilient Computing Courseware (RKBExplorer) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Resilient Computing Courseware (RKBExplorer) took 0.0008227825164794922s
Interlinking | Calculation of Clustering coefficient for Resilient Computing Courseware (RKBExplorer) took 0.00017189979553222656s
Believability | Calculation of trust value for Resilient Computing Courseware (RKBExplorer) took 1.5020370483398438e-05s
INFO | --- Analysis for rkb-explorer-courseware took 2.783000946044922s
Availability | SPARQL endpoint availability check for Street level crime reports for England and Wales took 0.04348325729370117s
Availability | VoID file availability check for Street level crime reports for England and Wales took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for Street level crime reports for England and Wales took 0.28915882110595703s
Reputation | Calculation of the PageRank for Street level crime reports for England and Wales took 0.020841121673583984s
Interlinking | Calculation of Degree of Connection for Street level crime reports for England and Wales took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Street level crime reports for England and Wales took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Street level crime reports for England and Wales took 3.933906555175781e-05s
Believability | Calculation of trust value for Street level crime reports for England and Wales took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-crime took 2.8096954822540283s
Availability | SPARQL endpoint availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.02811908721923828s
Availability | VoID file availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.2827122211456299s
Reputation | Calculation of the PageRank for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.02286052703857422s
Interlinking | Calculation of Degree of Connection for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0001227855682373047s
Believability | Calculation of trust value for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.4066696166992188e-05s
INFO | --- Analysis for rkb-explorer-curriculum took 2.806051015853882s
Availability | SPARQL endpoint availability check for Technische Universität Darmstadt (RKBExplorer) took 0.03468203544616699s
Availability | VoID file availability check for Technische Universität Darmstadt (RKBExplorer) took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for Technische Universität Darmstadt (RKBExplorer) took 0.33997416496276855s
Reputation | Calculation of the PageRank for Technische Universität Darmstadt (RKBExplorer) took 0.021394729614257812s
Interlinking | Calculation of Degree of Connection for Technische Universität Darmstadt (RKBExplorer) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Technische Universität Darmstadt (RKBExplorer) took 0.0007998943328857422s
Interlinking | Calculation of Clustering coefficient for Technische Universität Darmstadt (RKBExplorer) took 6.008148193359375e-05s
Believability | Calculation of trust value for Technische Universität Darmstadt (RKBExplorer) took 1.52587890625e-05s
INFO | --- Analysis for rkb-explorer-darmstadt took 2.918879270553589s
Availability | SPARQL endpoint availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.03879809379577637s
Availability | VoID file availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for DBLP Computer Science Bibliography (RKBExplorer) took 0.284991979598999s
Reputation | Calculation of the PageRank for DBLP Computer Science Bibliography (RKBExplorer) took 0.022793292999267578s
Interlinking | Calculation of Degree of Connection for DBLP Computer Science Bibliography (RKBExplorer) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for DBLP Computer Science Bibliography (RKBExplorer) took 0.0008139610290527344s
Interlinking | Calculation of Clustering coefficient for DBLP Computer Science Bibliography (RKBExplorer) took 0.0002574920654296875s
Believability | Calculation of trust value for DBLP Computer Science Bibliography (RKBExplorer) took 1.5497207641601562e-05s
INFO | --- Analysis for rkb-explorer-dblp took 2.8767144680023193s
Availability | SPARQL endpoint availability check for Deep Blue (RKBExplorer) took 0.041872262954711914s
Availability | VoID file availability check for Deep Blue (RKBExplorer) took 0.0004379749298095703s
Completeness | Calculation of interlinking completeness for Deep Blue (RKBExplorer) took 0.27963995933532715s
Reputation | Calculation of the PageRank for Deep Blue (RKBExplorer) took 0.02102804183959961s
Interlinking | Calculation of Degree of Connection for Deep Blue (RKBExplorer) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Deep Blue (RKBExplorer) took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Deep Blue (RKBExplorer) took 7.915496826171875e-05s
Believability | Calculation of trust value for Deep Blue (RKBExplorer) took 1.4543533325195312e-05s
INFO | --- Analysis for rkb-explorer-deepblue took 2.7879605293273926s
Availability | SPARQL endpoint availability check for DEPLOY (RKBExplorer) took 0.36489295959472656s
Availability | VoID file availability check for DEPLOY (RKBExplorer) took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for DEPLOY (RKBExplorer) took 0.32265591621398926s
Reputation | Calculation of the PageRank for DEPLOY (RKBExplorer) took 0.02082514762878418s
Interlinking | Calculation of Degree of Connection for DEPLOY (RKBExplorer) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for DEPLOY (RKBExplorer) took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for DEPLOY (RKBExplorer) took 0.00010275840759277344s
Believability | Calculation of trust value for DEPLOY (RKBExplorer) took 1.4543533325195312e-05s
INFO | --- Analysis for rkb-explorer-deploy took 4.238269805908203s
Availability | SPARQL endpoint availability check for digitaleconomy took 0.04111504554748535s
Availability | VoID file availability check for digitaleconomy took 0.0004923343658447266s
Completeness | Calculation of interlinking completeness for digitaleconomy took 0.3215765953063965s
Reputation | Calculation of the PageRank for digitaleconomy took 0.021004438400268555s
Interlinking | Calculation of Degree of Connection for digitaleconomy took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for digitaleconomy took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for digitaleconomy took 3.361701965332031e-05s
Believability | Calculation of trust value for digitaleconomy took 1.5497207641601562e-05s
INFO | --- Analysis for rkb-explorer-digitaleconomy took 2.7117021083831787s
Availability | SPARQL endpoint availability check for dotAC (RKBExplorer) took 0.03743886947631836s
Availability | VoID file availability check for dotAC (RKBExplorer) took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for dotAC (RKBExplorer) took 0.31413722038269043s
Reputation | Calculation of the PageRank for dotAC (RKBExplorer) took 0.020555973052978516s
Interlinking | Calculation of Degree of Connection for dotAC (RKBExplorer) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for dotAC (RKBExplorer) took 0.0008370876312255859s
Interlinking | Calculation of Clustering coefficient for dotAC (RKBExplorer) took 0.0001513957977294922s
Believability | Calculation of trust value for dotAC (RKBExplorer) took 1.3828277587890625e-05s
INFO | --- Analysis for rkb-explorer-dotac took 2.791813850402832s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 0.03361701965332031s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.000579833984375s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.29665350914001465s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.022295236587524414s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 4.887580871582031e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-ecs took 3.4129841327667236s
Availability | SPARQL endpoint availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.03333759307861328s
Availability | VoID file availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.29000377655029297s
Reputation | Calculation of the PageRank for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.02056288719177246s
Interlinking | Calculation of Degree of Connection for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0001842975616455078s
Believability | Calculation of trust value for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.4543533325195312e-05s
INFO | --- Analysis for rkb-explorer-eprints took 2.698310375213623s
Availability | SPARQL endpoint availability check for epsrc took 0.02852463722229004s
Availability | VoID file availability check for epsrc took 0.00038313865661621094s
Completeness | Calculation of interlinking completeness for epsrc took 0.3097810745239258s
Reputation | Calculation of the PageRank for epsrc took 0.02113795280456543s
Interlinking | Calculation of Degree of Connection for epsrc took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for epsrc took 0.0008058547973632812s
Interlinking | Calculation of Clustering coefficient for epsrc took 6.699562072753906e-05s
Believability | Calculation of trust value for epsrc took 1.430511474609375e-05s
INFO | --- Analysis for rkb-explorer-epsrc took 2.844255208969116s
Availability | SPARQL endpoint availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.03594040870666504s
Availability | VoID file availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.2847123146057129s
Reputation | Calculation of the PageRank for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.020774126052856445s
Interlinking | Calculation of Degree of Connection for ERA - Australian Research Council publication ratings (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for ERA - Australian Research Council publication ratings (RKBExplorer) took 8.487701416015625e-05s
Believability | Calculation of trust value for ERA - Australian Research Council publication ratings (RKBExplorer) took 1.4543533325195312e-05s
INFO | --- Analysis for rkb-explorer-era took 2.78908634185791s
Availability | SPARQL endpoint availability check for Institut Eurécom (RKBExplorer) took 0.04425859451293945s
Availability | VoID file availability check for Institut Eurécom (RKBExplorer) took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for Institut Eurécom (RKBExplorer) took 0.31156182289123535s
Reputation | Calculation of the PageRank for Institut Eurécom (RKBExplorer) took 0.020929813385009766s
Interlinking | Calculation of Degree of Connection for Institut Eurécom (RKBExplorer) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Institut Eurécom (RKBExplorer) took 0.0010764598846435547s
Interlinking | Calculation of Clustering coefficient for Institut Eurécom (RKBExplorer) took 0.00012230873107910156s
Believability | Calculation of trust value for Institut Eurécom (RKBExplorer) took 1.6689300537109375e-05s
INFO | --- Analysis for rkb-explorer-eurecom took 2.814697265625s
Availability | SPARQL endpoint availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.410722017288208s
Availability | VoID file availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.0006146430969238281s
Completeness | Calculation of interlinking completeness for France Telecom Recherche et Développement (RKBExplorer) took 0.32119321823120117s
Reputation | Calculation of the PageRank for France Telecom Recherche et Développement (RKBExplorer) took 0.02067852020263672s
Interlinking | Calculation of Degree of Connection for France Telecom Recherche et Développement (RKBExplorer) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for France Telecom Recherche et Développement (RKBExplorer) took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for France Telecom Recherche et Développement (RKBExplorer) took 9.655952453613281e-05s
Believability | Calculation of trust value for France Telecom Recherche et Développement (RKBExplorer) took 1.430511474609375e-05s
INFO | --- Analysis for rkb-explorer-ft took 4.407820701599121s
Availability | SPARQL endpoint availability check for fun took 0.033312082290649414s
Availability | VoID file availability check for fun took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for fun took 0.29820680618286133s
Reputation | Calculation of the PageRank for fun took 0.023467063903808594s
Interlinking | Calculation of Degree of Connection for fun took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for fun took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for fun took 8.296966552734375e-05s
Believability | Calculation of trust value for fun took 1.5497207641601562e-05s
INFO | --- Analysis for rkb-explorer-fun took 2.8017427921295166s
Availability | SPARQL endpoint availability check for gdlc took 0.03378868103027344s
Availability | VoID file availability check for gdlc took 0.0003905296325683594s
Completeness | Calculation of interlinking completeness for gdlc took 0.33553099632263184s
Reputation | Calculation of the PageRank for gdlc took 0.020784616470336914s
Interlinking | Calculation of Degree of Connection for gdlc took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for gdlc took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for gdlc took 7.224082946777344e-05s
Believability | Calculation of trust value for gdlc took 1.5497207641601562e-05s
INFO | --- Analysis for rkb-explorer-gdlc took 2.64369797706604s
Availability | SPARQL endpoint availability check for IBM Research GmbH (RKBExplorer) took 0.032258033752441406s
Availability | VoID file availability check for IBM Research GmbH (RKBExplorer) took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for IBM Research GmbH (RKBExplorer) took 0.2897965908050537s
Reputation | Calculation of the PageRank for IBM Research GmbH (RKBExplorer) took 0.02114105224609375s
Interlinking | Calculation of Degree of Connection for IBM Research GmbH (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for IBM Research GmbH (RKBExplorer) took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for IBM Research GmbH (RKBExplorer) took 0.00012564659118652344s
Believability | Calculation of trust value for IBM Research GmbH (RKBExplorer) took 1.4543533325195312e-05s
INFO | --- Analysis for rkb-explorer-ibm took 2.752988815307617s
Availability | SPARQL endpoint availability check for IEEE Papers (RKBExplorer) took 0.02205038070678711s
Availability | VoID file availability check for IEEE Papers (RKBExplorer) took 0.0002918243408203125s
Completeness | Calculation of interlinking completeness for IEEE Papers (RKBExplorer) took 0.3085048198699951s
Reputation | Calculation of the PageRank for IEEE Papers (RKBExplorer) took 0.020864486694335938s
Interlinking | Calculation of Degree of Connection for IEEE Papers (RKBExplorer) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for IEEE Papers (RKBExplorer) took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for IEEE Papers (RKBExplorer) took 0.00014543533325195312s
Believability | Calculation of trust value for IEEE Papers (RKBExplorer) took 1.0967254638671875e-05s
INFO | --- Analysis for rkb-explorer-ieee took 2.7187108993530273s
Availability | SPARQL endpoint availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.03141164779663086s
Availability | VoID file availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.30332064628601074s
Reputation | Calculation of the PageRank for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.020740747451782227s
Interlinking | Calculation of Degree of Connection for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.00014781951904296875s
Believability | Calculation of trust value for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-irit took 2.71948504447937s
Availability | SPARQL endpoint availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.036843299865722656s
Availability | VoID file availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.2876913547515869s
Reputation | Calculation of the PageRank for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.021244287490844727s
Interlinking | Calculation of Degree of Connection for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 7.009506225585938e-05s
Believability | Calculation of trust value for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 1.430511474609375e-05s
INFO | --- Analysis for rkb-explorer-italy took 2.6700689792633057s
Availability | SPARQL endpoint availability check for UK JISC (RKBExplorer) took 0.031324148178100586s
Availability | VoID file availability check for UK JISC (RKBExplorer) took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for UK JISC (RKBExplorer) took 0.30745434761047363s
Reputation | Calculation of the PageRank for UK JISC (RKBExplorer) took 0.021098852157592773s
Interlinking | Calculation of Degree of Connection for UK JISC (RKBExplorer) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for UK JISC (RKBExplorer) took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for UK JISC (RKBExplorer) took 0.000102996826171875s
Believability | Calculation of trust value for UK JISC (RKBExplorer) took 1.4781951904296875e-05s
INFO | --- Analysis for rkb-explorer-jisc took 2.786501407623291s
Availability | SPARQL endpoint availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.036722660064697266s
Availability | VoID file availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.00044846534729003906s
Completeness | Calculation of interlinking completeness for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.304182767868042s
Reputation | Calculation of the PageRank for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.02078104019165039s
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.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Vytautas Magnus University, Kaunas (RKBExplorer) took 4.76837158203125e-05s
Believability | Calculation of trust value for Vytautas Magnus University, Kaunas (RKBExplorer) took 1.3589859008789062e-05s
INFO | --- Analysis for rkb-explorer-kaunas took 2.8009066581726074s
Availability | SPARQL endpoint availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.036843061447143555s
Availability | VoID file availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for Korean Institute of Science Technology and Information (RKBExplorer) took 0.2871086597442627s
Reputation | Calculation of the PageRank for Korean Institute of Science Technology and Information (RKBExplorer) took 0.022548675537109375s
Interlinking | Calculation of Degree of Connection for Korean Institute of Science Technology and Information (RKBExplorer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0009052753448486328s
Interlinking | Calculation of Clustering coefficient for Korean Institute of Science Technology and Information (RKBExplorer) took 0.00018835067749023438s
Believability | Calculation of trust value for Korean Institute of Science Technology and Information (RKBExplorer) took 1.4543533325195312e-05s
INFO | --- Analysis for rkb-explorer-kisti took 2.741023063659668s
Availability | SPARQL endpoint availability check for LAAS-CNRS (RKBExplorer) took 0.03700971603393555s
Availability | VoID file availability check for LAAS-CNRS (RKBExplorer) took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for LAAS-CNRS (RKBExplorer) took 0.304577112197876s
Reputation | Calculation of the PageRank for LAAS-CNRS (RKBExplorer) took 0.020811080932617188s
Interlinking | Calculation of Degree of Connection for LAAS-CNRS (RKBExplorer) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for LAAS-CNRS (RKBExplorer) took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for LAAS-CNRS (RKBExplorer) took 0.00015473365783691406s
Believability | Calculation of trust value for LAAS-CNRS (RKBExplorer) took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-laas took 2.8135383129119873s
Availability | SPARQL endpoint availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.04162192344665527s
Availability | VoID file availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0005357265472412109s
Completeness | Calculation of interlinking completeness for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.28484654426574707s
Reputation | Calculation of the PageRank for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.02108168601989746s
Interlinking | Calculation of Degree of Connection for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 6.985664367675781e-05s
Believability | Calculation of trust value for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.0967254638671875e-05s
INFO | --- Analysis for rkb-explorer-lisbon took 2.7728419303894043s
Availability | SPARQL endpoint availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.03311324119567871s
Availability | VoID file availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.00020742416381835938s
Completeness | Calculation of interlinking completeness for University of Newcastle upon Tyne (RKBExplorer) took 0.3295552730560303s
Reputation | Calculation of the PageRank for University of Newcastle upon Tyne (RKBExplorer) took 0.020473241806030273s
Interlinking | Calculation of Degree of Connection for University of Newcastle upon Tyne (RKBExplorer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for University of Newcastle upon Tyne (RKBExplorer) took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for University of Newcastle upon Tyne (RKBExplorer) took 0.00017333030700683594s
Believability | Calculation of trust value for University of Newcastle upon Tyne (RKBExplorer) took 1.621246337890625e-05s
INFO | --- Analysis for rkb-explorer-newcastle took 2.794818639755249s
Availability | SPARQL endpoint availability check for notube took 0.041307926177978516s
Availability | VoID file availability check for notube took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for notube took 0.28865790367126465s
Reputation | Calculation of the PageRank for notube took 0.021770000457763672s
Interlinking | Calculation of Degree of Connection for notube took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for notube took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for notube took 4.863739013671875e-05s
Believability | Calculation of trust value for notube took 1.5020370483398438e-05s
INFO | --- Analysis for rkb-explorer-notube took 2.7155182361602783s
Availability | SPARQL endpoint availability check for National Science Foundation (RKBExplorer) took 0.03387737274169922s
Availability | VoID file availability check for National Science Foundation (RKBExplorer) took 0.0004658699035644531s
Completeness | Calculation of interlinking completeness for National Science Foundation (RKBExplorer) took 0.3033487796783447s
Reputation | Calculation of the PageRank for National Science Foundation (RKBExplorer) took 0.022061586380004883s
Interlinking | Calculation of Degree of Connection for National Science Foundation (RKBExplorer) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for National Science Foundation (RKBExplorer) took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for National Science Foundation (RKBExplorer) took 0.00014257431030273438s
Believability | Calculation of trust value for National Science Foundation (RKBExplorer) took 1.0967254638671875e-05s
INFO | --- Analysis for rkb-explorer-nsf took 2.7916955947875977s
Availability | SPARQL endpoint availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.04050612449645996s
Availability | VoID file availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.3054351806640625s
Reputation | Calculation of the PageRank for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.023419618606567383s
Interlinking | Calculation of Degree of Connection for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0008630752563476562s
Interlinking | Calculation of Clustering coefficient for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.00017952919006347656s
Believability | Calculation of trust value for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.4781951904296875e-05s
INFO | --- Analysis for rkb-explorer-oai took 2.8372175693511963s
Availability | SPARQL endpoint availability check for Ordnance Survey (RKBExplorer) took 0.037432193756103516s
Availability | VoID file availability check for Ordnance Survey (RKBExplorer) took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for Ordnance Survey (RKBExplorer) took 0.29722023010253906s
Reputation | Calculation of the PageRank for Ordnance Survey (RKBExplorer) took 0.020970582962036133s
Interlinking | Calculation of Degree of Connection for Ordnance Survey (RKBExplorer) took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Ordnance Survey (RKBExplorer) took 0.000782012939453125s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey (RKBExplorer) took 9.202957153320312e-05s
Believability | Calculation of trust value for Ordnance Survey (RKBExplorer) took 1.5497207641601562e-05s
INFO | --- Analysis for rkb-explorer-os took 2.7333414554595947s
Availability | SPARQL endpoint availability check for photos took 0.03422665596008301s
Availability | VoID file availability check for photos took 0.0005640983581542969s
Completeness | Calculation of interlinking completeness for photos took 0.3120238780975342s
Reputation | Calculation of the PageRank for photos took 0.02079176902770996s
Interlinking | Calculation of Degree of Connection for photos took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for photos took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for photos took 7.987022399902344e-05s
Believability | Calculation of trust value for photos took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-photos took 2.6839582920074463s
Availability | SPARQL endpoint availability check for Università di Pisa (RKBExplorer) took 0.04215669631958008s
Availability | VoID file availability check for Università di Pisa (RKBExplorer) took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for Università di Pisa (RKBExplorer) took 0.28614187240600586s
Reputation | Calculation of the PageRank for Università di Pisa (RKBExplorer) took 0.023255109786987305s
Interlinking | Calculation of Degree of Connection for Università di Pisa (RKBExplorer) took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Università di Pisa (RKBExplorer) took 0.0009768009185791016s
Interlinking | Calculation of Clustering coefficient for Università di Pisa (RKBExplorer) took 0.00013971328735351562s
Believability | Calculation of trust value for Università di Pisa (RKBExplorer) took 1.6927719116210938e-05s
INFO | --- Analysis for rkb-explorer-pisa took 2.71366548538208s
Availability | SPARQL endpoint availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.036772966384887695s
Availability | VoID file availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.000301361083984375s
Completeness | Calculation of interlinking completeness for Research Assessment Exercise 2001 (RKBExplorer) took 0.30032896995544434s
Reputation | Calculation of the PageRank for Research Assessment Exercise 2001 (RKBExplorer) took 0.020740985870361328s
Interlinking | Calculation of Degree of Connection for Research Assessment Exercise 2001 (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Research Assessment Exercise 2001 (RKBExplorer) took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Research Assessment Exercise 2001 (RKBExplorer) took 0.00019741058349609375s
Believability | Calculation of trust value for Research Assessment Exercise 2001 (RKBExplorer) took 9.298324584960938e-06s
INFO | --- Analysis for rkb-explorer-rae2001 took 2.742107391357422s
Availability | SPARQL endpoint availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.032768964767456055s
Availability | VoID file availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0002396106719970703s
Completeness | Calculation of interlinking completeness for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.2801680564880371s
Reputation | Calculation of the PageRank for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.02068471908569336s
Interlinking | Calculation of Degree of Connection for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.00013971328735351562s
Believability | Calculation of trust value for ReSIST Resilience Mechanisms (RKBExplorer.com) took 9.775161743164062e-06s
INFO | --- Analysis for rkb-explorer-resex took 2.6881790161132812s
Availability | SPARQL endpoint availability check for RISKS Digest (RKBExplorer) took 0.04021406173706055s
Availability | VoID file availability check for RISKS Digest (RKBExplorer) took 0.0005102157592773438s
Completeness | Calculation of interlinking completeness for RISKS Digest (RKBExplorer) took 0.3282334804534912s
Reputation | Calculation of the PageRank for RISKS Digest (RKBExplorer) took 0.02158832550048828s
Interlinking | Calculation of Degree of Connection for RISKS Digest (RKBExplorer) took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for RISKS Digest (RKBExplorer) took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for RISKS Digest (RKBExplorer) took 0.00010132789611816406s
Believability | Calculation of trust value for RISKS Digest (RKBExplorer) took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-risks took 2.8198275566101074s
Availability | SPARQL endpoint availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.05012822151184082s
Availability | VoID file availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.2773778438568115s
Reputation | Calculation of the PageRank for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.02092909812927246s
Interlinking | Calculation of Degree of Connection for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.00013327598571777344s
Believability | Calculation of trust value for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 1.4781951904296875e-05s
INFO | --- Analysis for rkb-explorer-roma took 2.7457284927368164s
Availability | SPARQL endpoint availability check for roni took 0.03201127052307129s
Availability | VoID file availability check for roni took 0.0007572174072265625s
Completeness | Calculation of interlinking completeness for roni took 0.2989633083343506s
Reputation | Calculation of the PageRank for roni took 0.02102184295654297s
Interlinking | Calculation of Degree of Connection for roni took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for roni took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for roni took 3.409385681152344e-05s
Believability | Calculation of trust value for roni took 1.4066696166992188e-05s
INFO | --- Analysis for rkb-explorer-roni took 2.7653560638427734s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.04067111015319824s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.3186771869659424s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.02086353302001953s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.52587890625e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0008080005645751953s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0002415180206298828s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.2874603271484375e-05s
INFO | --- Analysis for rkb-explorer-southampton took 2.7614970207214355s
Availability | SPARQL endpoint availability check for Universität Ulm (RKBExplorer) took 0.03475356101989746s
Availability | VoID file availability check for Universität Ulm (RKBExplorer) took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for Universität Ulm (RKBExplorer) took 0.27997779846191406s
Reputation | Calculation of the PageRank for Universität Ulm (RKBExplorer) took 0.020722627639770508s
Interlinking | Calculation of Degree of Connection for Universität Ulm (RKBExplorer) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Universität Ulm (RKBExplorer) took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Universität Ulm (RKBExplorer) took 0.00012040138244628906s
Believability | Calculation of trust value for Universität Ulm (RKBExplorer) took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-ulm took 2.7349839210510254s
Availability | SPARQL endpoint availability check for UN/LOCODE (RKBExplorer) took 0.0374908447265625s
Availability | VoID file availability check for UN/LOCODE (RKBExplorer) took 0.00035762786865234375s
Completeness | Calculation of interlinking completeness for UN/LOCODE (RKBExplorer) took 0.28975868225097656s
Reputation | Calculation of the PageRank for UN/LOCODE (RKBExplorer) took 0.021932125091552734s
Interlinking | Calculation of Degree of Connection for UN/LOCODE (RKBExplorer) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for UN/LOCODE (RKBExplorer) took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for UN/LOCODE (RKBExplorer) took 0.00010251998901367188s
Believability | Calculation of trust value for UN/LOCODE (RKBExplorer) took 1.33514404296875e-05s
INFO | --- Analysis for rkb-explorer-unlocode took 2.7145328521728516s
Availability | SPARQL endpoint availability check for webconf took 0.04828500747680664s
Availability | VoID file availability check for webconf took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for webconf took 0.3035862445831299s
Reputation | Calculation of the PageRank for webconf took 0.02084040641784668s
Interlinking | Calculation of Degree of Connection for webconf took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for webconf took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for webconf took 0.00010728836059570312s
Believability | Calculation of trust value for webconf took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-webconf took 13.12387466430664s
Availability | SPARQL endpoint availability check for Web Science Conference (RKBExplorer) took 0.041298627853393555s
Availability | VoID file availability check for Web Science Conference (RKBExplorer) took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for Web Science Conference (RKBExplorer) took 0.2927417755126953s
Reputation | Calculation of the PageRank for Web Science Conference (RKBExplorer) took 0.020726680755615234s
Interlinking | Calculation of Degree of Connection for Web Science Conference (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Web Science Conference (RKBExplorer) took 0.000751495361328125s
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.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-webscience took 2.7906179428100586s
Availability | SPARQL endpoint availability check for ReSIST Project Wiki (RKBExplorer) took 0.03857135772705078s
Availability | VoID file availability check for ReSIST Project Wiki (RKBExplorer) took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for ReSIST Project Wiki (RKBExplorer) took 0.3024773597717285s
Reputation | Calculation of the PageRank for ReSIST Project Wiki (RKBExplorer) took 0.02119135856628418s
Interlinking | Calculation of Degree of Connection for ReSIST Project Wiki (RKBExplorer) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for ReSIST Project Wiki (RKBExplorer) took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for ReSIST Project Wiki (RKBExplorer) took 0.0002086162567138672s
Believability | Calculation of trust value for ReSIST Project Wiki (RKBExplorer) took 1.33514404296875e-05s
INFO | --- Analysis for rkb-explorer-wiki took 2.759653329849243s
Availability | SPARQL endpoint availability check for WordNet (RKBExplorer) took 0.03692269325256348s
Availability | VoID file availability check for WordNet (RKBExplorer) took 0.00043010711669921875s
Completeness | Calculation of interlinking completeness for WordNet (RKBExplorer) took 0.29263734817504883s
Reputation | Calculation of the PageRank for WordNet (RKBExplorer) took 0.02094268798828125s
Interlinking | Calculation of Degree of Connection for WordNet (RKBExplorer) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for WordNet (RKBExplorer) took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for WordNet (RKBExplorer) took 9.799003601074219e-05s
Believability | Calculation of trust value for WordNet (RKBExplorer) took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-wordnet took 2.7758970260620117s
Availability | SPARQL endpoint availability check for ROCEEH Out of Africa Database (ROAD) took 0.2516803741455078s
Availability | VoID file availability check for ROCEEH Out of Africa Database (ROAD) took 0.0005178451538085938s
Extra | Recovery of all triples for ROCEEH Out of Africa Database (ROAD) took 48.80108094215393s
Performance | Total latancy measurement for ROCEEH Out of Africa Database (ROAD) took 0.43659162521362305s
Amount of data | Number of triples check for ROCEEH Out of Africa Database (ROAD) took 1.4283747673034668s
Interoperability | New terms check for ROCEEH Out of Africa Database (ROAD) took 1.7281336784362793s
Versatility | Languages check for ROCEEH Out of Africa Database (ROAD) took 4.487814426422119s
Interpretability | Number of blank nodes check for ROCEEH Out of Africa Database (ROAD) took 1.279585599899292s
Interpretability | RDF structures check for ROCEEH Out of Africa Database (ROAD) took 0.0899498462677002s
Versatility | Serialization formats check for ROCEEH Out of Africa Database (ROAD) took 0.09021234512329102s
Availability | RDF dump link check for ROCEEH Out of Africa Database (ROAD) took 0.08666825294494629s
License | MR license check for ROCEEH Out of Africa Database (ROAD) took 0.08777165412902832s
License | HR license check for ROCEEH Out of Africa Database (ROAD) took 0.08795404434204102s
Amount of data | Number of property check for ROCEEH Out of Africa Database (ROAD) took 0.09421515464782715s
Understandability | Number of label check for ROCEEH Out of Africa Database (ROAD) took 0.0976564884185791s
Understandability | URI regex check for ROCEEH Out of Africa Database (ROAD) took 0.16589999198913574s
Understandability | Vocabs check for ROCEEH Out of Africa Database (ROAD) took 0.08052325248718262s
Verifiability | Authors check for ROCEEH Out of Africa Database (ROAD) took 0.09569525718688965s
Verifiability | Publishers check for ROCEEH Out of Africa Database (ROAD) took 0.09521842002868652s
Performance | Throughput check for ROCEEH Out of Africa Database (ROAD) took 10.47582483291626s
Amount of data | Check the number of entities for ROCEEH Out of Africa Database (ROAD) took 7.2479248046875e-05s
Verifiability | Contribs. check for ROCEEH Out of Africa Database (ROAD) took 0.07934117317199707s
Interlinking | sameAs chians check for ROCEEH Out of Africa Database (ROAD) took 0.0865030288696289s
Interlinking | skos check for ROCEEH Out of Africa Database (ROAD) took 0.08646297454833984s
Interlinking | skos check for ROCEEH Out of Africa Database (ROAD) took 0.09388852119445801s
Timeliness | dataset update frequency check for ROCEEH Out of Africa Database (ROAD) took 0.09458661079406738s
Currency | Creation date check for ROCEEH Out of Africa Database (ROAD) took 0.16590166091918945s
Currency | Modification date check for ROCEEH Out of Africa Database (ROAD) took 0.16675996780395508s
Rep.Conc. | URIs length for ROCEEH Out of Africa Database (ROAD) took 18.819250345230103s
Interoperability | New vocabularies check for ROCEEH Out of Africa Database (ROAD) took 1.1682510375976562e-05s
Consistency | Deprecated classes/propertiers check for ROCEEH Out of Africa Database (ROAD) took 0.0809168815612793s
Accuracy | Check Functional Property for ROCEEH Out of Africa Database (ROAD) took 0.09385013580322266s
Accuracy | Check Inverse Functional Property for ROCEEH Out of Africa Database (ROAD) took 0.0861814022064209s
Accuracy | Check Datatype consistency for ROCEEH Out of Africa Database (ROAD) took 3.8806374073028564s
Consistency | Disjoint class check for ROCEEH Out of Africa Database (ROAD) took 0.09443187713623047s
Consistency | Check Misplaced properties for ROCEEH Out of Africa Database (ROAD) took 2.781719207763672s
Consistency | Check Ontology hijacking for ROCEEH Out of Africa Database (ROAD) took 6.742764711380005s
Consistency | Check Invalid usage of undefined classes for ROCEEH Out of Africa Database (ROAD) took 1.6440136432647705s
Consistency | Check Invalid usage of undefined properties for ROCEEH Out of Africa Database (ROAD) took 4.290165424346924s
Conciseness | Check Extensional conciseness for ROCEEH Out of Africa Database (ROAD) took 3.1156980991363525s
Security | Sign check for ROCEEH Out of Africa Database (ROAD) took 0.09283971786499023s
Availability | Check URIs Dereferenciability for ROCEEH Out of Africa Database (ROAD) took 503.768673658371s
Completeness | Calculation of interlinking completeness for ROCEEH Out of Africa Database (ROAD) took 0.3653743267059326s
Reputation | Calculation of the PageRank for ROCEEH Out of Africa Database (ROAD) took 0.021396398544311523s
Interlinking | Calculation of Degree of Connection for ROCEEH Out of Africa Database (ROAD) took 2.384185791015625e-05s
Interlinking | Calculation of Centrality for ROCEEH Out of Africa Database (ROAD) took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for ROCEEH Out of Africa Database (ROAD) took 8.988380432128906e-05s
Interoperability | Check the re-using of existing vocabs for ROCEEH Out of Africa Database (ROAD) took 5.4836273193359375e-06s
Believability | Calculation of trust value for ROCEEH Out of Africa Database (ROAD) took 8.344650268554688e-06s
INFO | --- Analysis for roceeh-road took 634.9906067848206s
Availability | SPARQL endpoint availability check for ontology terrorist attack took 9.250640869140625e-05s
Availability | VoID file availability check for ontology terrorist attack took 0.0007104873657226562s
Completeness | Calculation of interlinking completeness for ontology terrorist attack took 0.3036806583404541s
Reputation | Calculation of the PageRank for ontology terrorist attack took 0.020990848541259766s
Interlinking | Calculation of Degree of Connection for ontology terrorist attack took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ontology terrorist attack took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for ontology terrorist attack took 3.4332275390625e-05s
Believability | Calculation of trust value for ontology terrorist attack took 1.3113021850585938e-05s
INFO | --- Analysis for ROSHANI took 5.364501476287842s
Availability | SPARQL endpoint availability check for TERRORIST ATTACK ONTOLOGY took 9.512901306152344e-05s
Availability | VoID file availability check for TERRORIST ATTACK ONTOLOGY took 0.0002865791320800781s
Completeness | Calculation of interlinking completeness for TERRORIST ATTACK ONTOLOGY took 0.2829763889312744s
Reputation | Calculation of the PageRank for TERRORIST ATTACK ONTOLOGY took 0.02106499671936035s
Interlinking | Calculation of Degree of Connection for TERRORIST ATTACK ONTOLOGY took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for TERRORIST ATTACK ONTOLOGY took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for TERRORIST ATTACK ONTOLOGY took 4.124641418457031e-05s
Believability | Calculation of trust value for TERRORIST ATTACK ONTOLOGY took 1.0013580322265625e-05s
INFO | --- Analysis for ROSHANI_SAHU took 2.6151130199432373s
Availability | SPARQL endpoint availability check for x took 8.130073547363281e-05s
Availability | VoID file availability check for x took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for x took 0.30942559242248535s
Reputation | Calculation of the PageRank for x took 0.021052837371826172s
Interlinking | Calculation of Degree of Connection for x took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for x took 0.0007917881011962891s
Interlinking | Calculation of Clustering coefficient for x took 3.504753112792969e-05s
Believability | Calculation of trust value for x took 1.4066696166992188e-05s
INFO | --- Analysis for Rozprawa,_artykuł took 2.7012321949005127s
Availability | SPARQL endpoint availability check for RSS-500 NIF NER CORPUS took 8.988380432128906e-05s
Availability | VoID file availability check for RSS-500 NIF NER CORPUS took 0.0006771087646484375s
Completeness | Calculation of interlinking completeness for RSS-500 NIF NER CORPUS took 0.2782621383666992s
Reputation | Calculation of the PageRank for RSS-500 NIF NER CORPUS took 0.021988391876220703s
Interlinking | Calculation of Degree of Connection for RSS-500 NIF NER CORPUS took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for RSS-500 NIF NER CORPUS took 0.0007815361022949219s
Interlinking | Calculation of Clustering coefficient for RSS-500 NIF NER CORPUS took 7.62939453125e-05s
Believability | Calculation of trust value for RSS-500 NIF NER CORPUS took 1.4066696166992188e-05s
INFO | --- Analysis for rss-500-nif-ner-corpus took 4.08315896987915s
Availability | SPARQL endpoint availability check for Ruben Taelman's Data took 4.553794860839844e-05s
Availability | VoID file availability check for Ruben Taelman's Data took 0.0007538795471191406s
Completeness | Calculation of interlinking completeness for Ruben Taelman's Data took 0.283707857131958s
Reputation | Calculation of the PageRank for Ruben Taelman's Data took 0.021064281463623047s
Interlinking | Calculation of Degree of Connection for Ruben Taelman's Data took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Ruben Taelman's Data took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Ruben Taelman's Data took 7.605552673339844e-05s
Believability | Calculation of trust value for Ruben Taelman's Data took 2.3603439331054688e-05s
INFO | --- Analysis for rubentaelman took 3.344250440597534s
Availability | SPARQL endpoint availability check for Ruben Verborgh's data took 8.654594421386719e-05s
Availability | VoID file availability check for Ruben Verborgh's data took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for Ruben Verborgh's data took 0.3187723159790039s
Reputation | Calculation of the PageRank for Ruben Verborgh's data took 0.021143674850463867s
Interlinking | Calculation of Degree of Connection for Ruben Verborgh's data took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Ruben Verborgh's data took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Ruben Verborgh's data took 9.560585021972656e-05s
Believability | Calculation of trust value for Ruben Verborgh's data took 1.4066696166992188e-05s
INFO | --- Analysis for rubenverborgh took 3.45515775680542s
Availability | SPARQL endpoint availability check for Russian Universities Specialities took 391.94961524009705s
Availability | VoID file availability check for Russian Universities Specialities took 0.0007615089416503906s
Completeness | Calculation of interlinking completeness for Russian Universities Specialities took 0.35160064697265625s
Reputation | Calculation of the PageRank for Russian Universities Specialities took 0.022127866744995117s
Interlinking | Calculation of Degree of Connection for Russian Universities Specialities took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Russian Universities Specialities took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Russian Universities Specialities took 4.76837158203125e-05s
Believability | Calculation of trust value for Russian Universities Specialities took 1.4781951904296875e-05s
INFO | --- Analysis for russian-universities-specialities took 677.1725392341614s
Availability | SPARQL endpoint availability check for SADI Semantic Web Services framework registry took 3.293315887451172s
Availability | VoID file availability check for SADI Semantic Web Services framework registry took 0.0005474090576171875s
Completeness | Calculation of interlinking completeness for SADI Semantic Web Services framework registry took 0.30382204055786133s
Reputation | Calculation of the PageRank for SADI Semantic Web Services framework registry took 0.021131515502929688s
Interlinking | Calculation of Degree of Connection for SADI Semantic Web Services framework registry took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for SADI Semantic Web Services framework registry took 0.000827789306640625s
Interlinking | Calculation of Clustering coefficient for SADI Semantic Web Services framework registry took 4.291534423828125e-05s
Believability | Calculation of trust value for SADI Semantic Web Services framework registry took 1.4543533325195312e-05s
INFO | --- Analysis for sadi-semantic-web-services-framework-registry took 8.128532648086548s
Availability | SPARQL endpoint availability check for SALDO-RDF took 1.0197029113769531s
Availability | VoID file availability check for SALDO-RDF took 0.0007987022399902344s
Completeness | Calculation of interlinking completeness for SALDO-RDF took 0.31458449363708496s
Reputation | Calculation of the PageRank for SALDO-RDF took 0.021136999130249023s
Interlinking | Calculation of Degree of Connection for SALDO-RDF took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for SALDO-RDF took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for SALDO-RDF took 4.2438507080078125e-05s
Believability | Calculation of trust value for SALDO-RDF took 9.059906005859375e-06s
INFO | --- Analysis for saldo-rdf took 5.891389846801758s
Availability | SPARQL endpoint availability check for SALDOM-RDF took 0.6426756381988525s
Availability | VoID file availability check for SALDOM-RDF took 0.0004134178161621094s
Completeness | Calculation of interlinking completeness for SALDOM-RDF took 0.27822136878967285s
Reputation | Calculation of the PageRank for SALDOM-RDF took 0.02249622344970703s
Interlinking | Calculation of Degree of Connection for SALDOM-RDF took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for SALDOM-RDF took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for SALDOM-RDF took 3.886222839355469e-05s
Believability | Calculation of trust value for SALDOM-RDF took 1.52587890625e-05s
INFO | --- Analysis for saldom-rdf took 5.2299582958221436s
Availability | SPARQL endpoint availability check for Salzburgerland DE took 9.131431579589844e-05s
Availability | VoID file availability check for Salzburgerland DE took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for Salzburgerland DE took 0.2888450622558594s
Reputation | Calculation of the PageRank for Salzburgerland DE took 0.020960569381713867s
Interlinking | Calculation of Degree of Connection for Salzburgerland DE took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Salzburgerland DE took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Salzburgerland DE took 0.00011205673217773438s
Believability | Calculation of trust value for Salzburgerland DE took 1.52587890625e-05s
INFO | --- Analysis for salzburgerland-com-de took 3.312433958053589s
Availability | SPARQL endpoint availability check for Salzburgerland EN took 8.702278137207031e-05s
Availability | VoID file availability check for Salzburgerland EN took 0.0005674362182617188s
Completeness | Calculation of interlinking completeness for Salzburgerland EN took 0.29038429260253906s
Reputation | Calculation of the PageRank for Salzburgerland EN took 0.02100396156311035s
Interlinking | Calculation of Degree of Connection for Salzburgerland EN took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Salzburgerland EN took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Salzburgerland EN took 0.000110626220703125s
Believability | Calculation of trust value for Salzburgerland EN took 1.4066696166992188e-05s
INFO | --- Analysis for salzburgerland-com-en took 3.1971042156219482s
Availability | SPARQL endpoint availability check for Salzburgerland IT took 4.38690185546875e-05s
Availability | VoID file availability check for Salzburgerland IT took 0.00031256675720214844s
Completeness | Calculation of interlinking completeness for Salzburgerland IT took 0.30405187606811523s
Reputation | Calculation of the PageRank for Salzburgerland IT took 0.02105879783630371s
Interlinking | Calculation of Degree of Connection for Salzburgerland IT took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Salzburgerland IT took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Salzburgerland IT took 0.00011038780212402344s
Believability | Calculation of trust value for Salzburgerland IT took 1.5497207641601562e-05s
INFO | --- Analysis for salzburgerland-com-it took 3.4364185333251953s
Availability | SPARQL endpoint availability check for sandrart.net took 5.793571472167969e-05s
Availability | VoID file availability check for sandrart.net took 0.0006361007690429688s
Completeness | Calculation of interlinking completeness for sandrart.net took 0.3089008331298828s
Reputation | Calculation of the PageRank for sandrart.net took 0.0226593017578125s
Interlinking | Calculation of Degree of Connection for sandrart.net took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for sandrart.net took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for sandrart.net took 7.557868957519531e-05s
Believability | Calculation of trust value for sandrart.net took 1.049041748046875e-05s
INFO | --- Analysis for sandrart-net took 3.9931466579437256s
Availability | SPARQL endpoint availability check for Taxons  took 0.34867429733276367s
Availability | VoID file availability check for Taxons  took 0.0005676746368408203s
Extra | Recovery of all triples for Taxons  took 19.019378185272217s
Performance | Total latancy measurement for Taxons  took 0.43818187713623047s
Amount of data | Number of triples check for Taxons  took 2.4307408332824707s
Interoperability | New terms check for Taxons  took 1.9561305046081543s
Versatility | Languages check for Taxons  took 40.98879075050354s
Interpretability | Number of blank nodes check for Taxons  took 1.0067832469940186s
Security | Check HTTPS for Taxons  took 0.1940608024597168s
Interpretability | RDF structures check for Taxons  took 2.900301694869995s
Versatility | Serialization formats check for Taxons  took 1.1548757553100586s
Availability | RDF dump link check for Taxons  took 0.45843982696533203s
License | MR license check for Taxons  took 2.644010066986084s
License | HR license check for Taxons  took 2.3978304862976074s
Amount of data | Number of property check for Taxons  took 0.14339804649353027s
Understandability | Number of label check for Taxons  took 4.374239683151245s
Understandability | URI regex check for Taxons  took 1.1849324703216553s
Understandability | Vocabs check for Taxons  took 0.3189530372619629s
Verifiability | Authors check for Taxons  took 0.4418942928314209s
Verifiability | Publishers check for Taxons  took 0.26555442810058594s
Performance | Throughput check for Taxons  took 10.427598714828491s
Amount of data | Check the number of entities for Taxons  took 8.654594421386719e-05s
Verifiability | Contribs. check for Taxons  took 0.25774288177490234s
Interlinking | sameAs chians check for Taxons  took 0.1463172435760498s
Interlinking | skos check for Taxons  took 0.1611497402191162s
Interlinking | skos check for Taxons  took 0.09050297737121582s
Timeliness | dataset update frequency check for Taxons  took 0.6130990982055664s
Currency | Creation date check for Taxons  took 0.5324983596801758s
Currency | Modification date check for Taxons  took 0.23430204391479492s
Rep.Conc. | URIs length for Taxons  took 8.854448556900024s
Interoperability | New vocabularies check for Taxons  took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for Taxons  took 0.11072802543640137s
Accuracy | Check Functional Property for Taxons  took 0.4388296604156494s
Accuracy | Check Inverse Functional Property for Taxons  took 0.4318201541900635s
Accuracy | Check Empty annotation labels for Taxons  took 3.6759300231933594s
Accuracy | Check White space in annotation for Taxons  took 0.3070995807647705s
Accuracy | Check Datatype consistency for Taxons  took 0.2755587100982666s
Consistency | Disjoint class check for Taxons  took 0.12047910690307617s
Consistency | Check Misplaced properties for Taxons  took 4.580840110778809s
Consistency | Misplaced classes for Taxons  took 0.9769942760467529s
Consistency | Check Ontology hijacking for Taxons  took 3.898590326309204s
Consistency | Check Invalid usage of undefined classes for Taxons  took 1.4605803489685059s
Consistency | Check Invalid usage of undefined properties for Taxons  took 6.234751462936401s
Conciseness | Check Extensional conciseness for Taxons  took 0.2897365093231201s
Conciseness | Check Intensional conciseness for Taxons  took 0.17497730255126953s
Security | Sign check for Taxons  took 1.134770154953003s
Availability | Check URIs Dereferenciability for Taxons  took 2038.5741238594055s
Completeness | Calculation of interlinking completeness for Taxons  took 0.6562395095825195s
Reputation | Calculation of the PageRank for Taxons  took 0.021388530731201172s
Interlinking | Calculation of Degree of Connection for Taxons  took 6.866455078125e-05s
Interlinking | Calculation of Centrality for Taxons  took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Taxons  took 9.012222290039062e-05s
Interoperability | Check the re-using of existing vocabs for Taxons  took 1.6689300537109375e-06s
Believability | Calculation of trust value for Taxons  took 1.4543533325195312e-05s
INFO | --- Analysis for sandre took 2238.0776031017303s
Availability | SPARQL endpoint availability check for Sanskrit English Lexicon took 1.905665397644043s
Availability | VoID file availability check for Sanskrit English Lexicon took 0.0006558895111083984s
Completeness | Calculation of interlinking completeness for Sanskrit English Lexicon took 0.3169529438018799s
Reputation | Calculation of the PageRank for Sanskrit English Lexicon took 0.022531986236572266s
Interlinking | Calculation of Degree of Connection for Sanskrit English Lexicon took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Sanskrit English Lexicon took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Sanskrit English Lexicon took 3.457069396972656e-05s
Believability | Calculation of trust value for Sanskrit English Lexicon took 1.4781951904296875e-05s
INFO | --- Analysis for sanskrit-english-lexicon took 9.345373153686523s
Availability | SPARQL endpoint availability check for Santillana Guide Dataset took 264.10753321647644s
Availability | VoID file availability check for Santillana Guide Dataset took 0.0008828639984130859s
Completeness | Calculation of interlinking completeness for Santillana Guide Dataset took 0.3855748176574707s
Reputation | Calculation of the PageRank for Santillana Guide Dataset took 0.020963430404663086s
Interlinking | Calculation of Degree of Connection for Santillana Guide Dataset took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Santillana Guide Dataset took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Santillana Guide Dataset took 4.38690185546875e-05s
Believability | Calculation of trust value for Santillana Guide Dataset took 1.4543533325195312e-05s
INFO | --- Analysis for santillana_guide_dataset took 668.9426574707031s
Availability | SPARQL endpoint availability check for SATAR test  took 0.00010156631469726562s
Availability | VoID file availability check for SATAR test  took 0.0008392333984375s
Completeness | Calculation of interlinking completeness for SATAR test  took 0.29101014137268066s
Reputation | Calculation of the PageRank for SATAR test  took 0.02124333381652832s
Interlinking | Calculation of Degree of Connection for SATAR test  took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SATAR test  took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for SATAR test  took 4.1484832763671875e-05s
Believability | Calculation of trust value for SATAR test  took 1.2636184692382812e-05s
INFO | --- Analysis for SATAR_test took 4.928365230560303s
Availability | SPARQL endpoint availability check for SCBG Data took 21.620521306991577s
Availability | VoID file availability check for SCBG Data took 0.0005509853363037109s
Completeness | Calculation of interlinking completeness for SCBG Data took 0.28971338272094727s
Reputation | Calculation of the PageRank for SCBG Data took 0.020987272262573242s
Interlinking | Calculation of Degree of Connection for SCBG Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SCBG Data took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for SCBG Data took 8.487701416015625e-05s
Believability | Calculation of trust value for SCBG Data took 1.52587890625e-05s
INFO | --- Analysis for SCBG-Data took 54.43330121040344s
Availability | SPARQL endpoint availability check for Schemantra took 4.5299530029296875e-05s
Availability | VoID file availability check for Schemantra took 0.0006144046783447266s
Completeness | Calculation of interlinking completeness for Schemantra took 0.2781860828399658s
Reputation | Calculation of the PageRank for Schemantra took 0.022170066833496094s
Interlinking | Calculation of Degree of Connection for Schemantra took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Schemantra took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Schemantra took 3.4809112548828125e-05s
Believability | Calculation of trust value for Schemantra took 1.4543533325195312e-05s
INFO | --- Analysis for Schemantra took 2.7111823558807373s
Availability | SPARQL endpoint availability check for Schemapedia: RDF schema compendium took 0.6402699947357178s
Availability | VoID file availability check for Schemapedia: RDF schema compendium took 0.000560760498046875s
Completeness | Calculation of interlinking completeness for Schemapedia: RDF schema compendium took 0.3133363723754883s
Reputation | Calculation of the PageRank for Schemapedia: RDF schema compendium took 0.021085023880004883s
Interlinking | Calculation of Degree of Connection for Schemapedia: RDF schema compendium took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Schemapedia: RDF schema compendium took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Schemapedia: RDF schema compendium took 3.719329833984375e-05s
Believability | Calculation of trust value for Schemapedia: RDF schema compendium took 1.8358230590820312e-05s
INFO | --- Analysis for schemapedia took 3.660176992416382s
Availability | SPARQL endpoint availability check for Scholarometer took 9.417533874511719e-05s
Availability | VoID file availability check for Scholarometer took 0.0007028579711914062s
Completeness | Calculation of interlinking completeness for Scholarometer took 0.280881404876709s
Reputation | Calculation of the PageRank for Scholarometer took 0.025115489959716797s
Interlinking | Calculation of Degree of Connection for Scholarometer took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Scholarometer took 0.0009129047393798828s
Interlinking | Calculation of Clustering coefficient for Scholarometer took 0.00010561943054199219s
Believability | Calculation of trust value for Scholarometer took 1.52587890625e-05s
INFO | --- Analysis for scholarometer took 8.301231861114502s
Availability | SPARQL endpoint availability check for The Digital Agenda Scoreboard of the European Commission took 4.506111145019531e-05s
Availability | VoID file availability check for The Digital Agenda Scoreboard of the European Commission took 0.0006115436553955078s
Completeness | Calculation of interlinking completeness for The Digital Agenda Scoreboard of the European Commission took 0.2973473072052002s
Reputation | Calculation of the PageRank for The Digital Agenda Scoreboard of the European Commission took 0.02161264419555664s
Interlinking | Calculation of Degree of Connection for The Digital Agenda Scoreboard of the European Commission took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for The Digital Agenda Scoreboard of the European Commission took 0.0007903575897216797s
Interlinking | Calculation of Clustering coefficient for The Digital Agenda Scoreboard of the European Commission took 3.886222839355469e-05s
Believability | Calculation of trust value for The Digital Agenda Scoreboard of the European Commission took 1.049041748046875e-05s
INFO | --- Analysis for scoreboard took 4.765242576599121s
Availability | SPARQL endpoint availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 4.5299530029296875e-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.000675201416015625s
Completeness | Calculation of interlinking completeness for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.2890596389770508s
Reputation | Calculation of the PageRank for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.02084636688232422s
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.8835067749023438e-05s
Interlinking | Calculation of Centrality for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 3.4332275390625e-05s
Believability | Calculation of trust value for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 1.5020370483398438e-05s
INFO | --- Analysis for SDDEC took 29.224132299423218s
Availability | SPARQL endpoint availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 9.107589721679688e-05s
Availability | VoID file availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0006525516510009766s
Completeness | Calculation of interlinking completeness for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.3001749515533447s
Reputation | Calculation of the PageRank for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0208132266998291s
Interlinking | Calculation of Degree of Connection for A Knowledge Organization System for the United Nations Sustainable Development Goals took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for A Knowledge Organization System for the United Nations Sustainable Development Goals took 3.1948089599609375e-05s
Believability | Calculation of trust value for A Knowledge Organization System for the United Nations Sustainable Development Goals took 1.0728836059570312e-05s
INFO | --- Analysis for SDG took 3.54886794090271s
Availability | SPARQL endpoint availability check for sears.com took 4.267692565917969e-05s
Availability | VoID file availability check for sears.com took 0.0007202625274658203s
Completeness | Calculation of interlinking completeness for sears.com took 0.28913235664367676s
Reputation | Calculation of the PageRank for sears.com took 0.02093505859375s
Interlinking | Calculation of Degree of Connection for sears.com took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for sears.com took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for sears.com took 7.343292236328125e-05s
Believability | Calculation of trust value for sears.com took 9.775161743164062e-06s
INFO | --- Analysis for sears took 5.729692697525024s
Availability | SPARQL endpoint availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.09663748741149902s
Availability | VoID file availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0007426738739013672s
Completeness | Calculation of interlinking completeness for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.2729451656341553s
Reputation | Calculation of the PageRank for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.020995378494262695s
Interlinking | Calculation of Degree of Connection for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0009922981262207031s
Interlinking | Calculation of Clustering coefficient for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 9.1552734375e-05s
Believability | Calculation of trust value for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 9.775161743164062e-06s
INFO | --- Analysis for sec-rdfabout took 6.502346515655518s
Availability | SPARQL endpoint availability check for Source Code Ecosystem Linked Data took 31.638655185699463s
Availability | VoID file availability check for Source Code Ecosystem Linked Data took 0.0007975101470947266s
Completeness | Calculation of interlinking completeness for Source Code Ecosystem Linked Data took 0.3276224136352539s
Reputation | Calculation of the PageRank for Source Code Ecosystem Linked Data took 0.02129220962524414s
Interlinking | Calculation of Degree of Connection for Source Code Ecosystem Linked Data took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Source Code Ecosystem Linked Data took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for Source Code Ecosystem Linked Data took 0.00010395050048828125s
Believability | Calculation of trust value for Source Code Ecosystem Linked Data took 1.3828277587890625e-05s
INFO | --- Analysis for secold took 168.11643838882446s
Availability | SPARQL endpoint availability check for semanlink took 4.673004150390625e-05s
Availability | VoID file availability check for semanlink took 0.0006244182586669922s
Completeness | Calculation of interlinking completeness for semanlink took 0.28733134269714355s
Reputation | Calculation of the PageRank for semanlink took 0.023031949996948242s
Interlinking | Calculation of Degree of Connection for semanlink took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for semanlink took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for semanlink took 0.00015282630920410156s
Believability | Calculation of trust value for semanlink took 1.3828277587890625e-05s
INFO | --- Analysis for semanlink took 3.8020944595336914s
Availability | SPARQL endpoint availability check for Semantic Universe Data took 0.08063459396362305s
Availability | VoID file availability check for Semantic Universe Data took 0.0010066032409667969s
Completeness | Calculation of interlinking completeness for Semantic Universe Data took 0.32886242866516113s
Reputation | Calculation of the PageRank for Semantic Universe Data took 0.020684242248535156s
Interlinking | Calculation of Degree of Connection for Semantic Universe Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Semantic Universe Data took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Semantic Universe Data took 3.2901763916015625e-05s
Believability | Calculation of trust value for Semantic Universe Data took 1.0013580322265625e-05s
INFO | --- Analysis for semantic-universe took 2.764524459838867s
Availability | SPARQL endpoint availability check for Semantic Web Dog Food Corpus took 30.553035736083984s
Availability | VoID file availability check for Semantic Web Dog Food Corpus took 0.0008795261383056641s
Completeness | Calculation of interlinking completeness for Semantic Web Dog Food Corpus took 0.2864961624145508s
Reputation | Calculation of the PageRank for Semantic Web Dog Food Corpus took 0.020827531814575195s
Interlinking | Calculation of Degree of Connection for Semantic Web Dog Food Corpus took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Semantic Web Dog Food Corpus took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Semantic Web Dog Food Corpus took 0.0001163482666015625s
Believability | Calculation of trust value for Semantic Web Dog Food Corpus took 1.430511474609375e-05s
INFO | --- Analysis for semantic-web-dog-food took 83.47717332839966s
Availability | SPARQL endpoint availability check for semantic-web-grundlagen took 9.274482727050781e-05s
Availability | VoID file availability check for semantic-web-grundlagen took 0.0006468296051025391s
Completeness | Calculation of interlinking completeness for semantic-web-grundlagen took 0.31403064727783203s
Reputation | Calculation of the PageRank for semantic-web-grundlagen took 0.020928382873535156s
Interlinking | Calculation of Degree of Connection for semantic-web-grundlagen took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for semantic-web-grundlagen took 0.0007898807525634766s
Interlinking | Calculation of Clustering coefficient for semantic-web-grundlagen took 5.1021575927734375e-05s
Believability | Calculation of trust value for semantic-web-grundlagen took 1.4066696166992188e-05s
INFO | --- Analysis for semantic-web-grundlagen took 3.188814878463745s
Availability | SPARQL endpoint availability check for Semantic XBRL Financial Data took 4.982948303222656e-05s
Availability | VoID file availability check for Semantic XBRL Financial Data took 0.0006873607635498047s
Completeness | Calculation of interlinking completeness for Semantic XBRL Financial Data took 0.29044008255004883s
Reputation | Calculation of the PageRank for Semantic XBRL Financial Data took 0.0209805965423584s
Interlinking | Calculation of Degree of Connection for Semantic XBRL Financial Data took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Semantic XBRL Financial Data took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Semantic XBRL Financial Data took 9.131431579589844e-05s
Believability | Calculation of trust value for Semantic XBRL Financial Data took 1.0251998901367188e-05s
INFO | --- Analysis for semantic-xbrl took 3.6351423263549805s
Availability | SPARQL endpoint availability check for Semantic Quran took 7.138563871383667s
Availability | VoID file availability check for Semantic Quran took 0.0006089210510253906s
Completeness | Calculation of interlinking completeness for Semantic Quran took 0.31341099739074707s
Reputation | Calculation of the PageRank for Semantic Quran took 0.020893096923828125s
Interlinking | Calculation of Degree of Connection for Semantic Quran took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Semantic Quran took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for Semantic Quran took 8.0108642578125e-05s
Believability | Calculation of trust value for Semantic Quran took 1.4781951904296875e-05s
INFO | --- Analysis for semanticquran took 16.937859773635864s
Availability | SPARQL endpoint availability check for SemanticTweet took 8.797645568847656e-05s
Availability | VoID file availability check for SemanticTweet took 0.0006258487701416016s
Completeness | Calculation of interlinking completeness for SemanticTweet took 0.3174464702606201s
Reputation | Calculation of the PageRank for SemanticTweet took 0.021734237670898438s
Interlinking | Calculation of Degree of Connection for SemanticTweet took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for SemanticTweet took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for SemanticTweet took 6.127357482910156e-05s
Believability | Calculation of trust value for SemanticTweet took 1.4543533325195312e-05s
INFO | --- Analysis for semantictweet took 2.8505184650421143s
Availability | SPARQL endpoint availability check for semanticweb.org took 8.940696716308594e-05s
Availability | VoID file availability check for semanticweb.org took 0.0007259845733642578s
Completeness | Calculation of interlinking completeness for semanticweb.org took 0.3010239601135254s
Reputation | Calculation of the PageRank for semanticweb.org took 0.02097010612487793s
Interlinking | Calculation of Degree of Connection for semanticweb.org took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for semanticweb.org took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for semanticweb.org took 8.296966552734375e-05s
Believability | Calculation of trust value for semanticweb.org took 1.2159347534179688e-05s
INFO | --- Analysis for semanticweb-org took 23.17253541946411s
Availability | SPARQL endpoint availability check for Semantic CrunchBase took 0.09799695014953613s
Availability | VoID file availability check for Semantic CrunchBase took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for Semantic CrunchBase took 0.3166518211364746s
Reputation | Calculation of the PageRank for Semantic CrunchBase took 0.020975112915039062s
Interlinking | Calculation of Degree of Connection for Semantic CrunchBase took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Semantic CrunchBase took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Semantic CrunchBase took 6.961822509765625e-05s
Believability | Calculation of trust value for Semantic CrunchBase took 1.2636184692382812e-05s
INFO | --- Analysis for semsol-crunchbase took 2.9352505207061768s
Availability | SPARQL endpoint availability check for SentimentWortschatz took 0.253948450088501s
Availability | VoID file availability check for SentimentWortschatz took 0.00031113624572753906s
Completeness | Calculation of interlinking completeness for SentimentWortschatz took 0.29892492294311523s
Reputation | Calculation of the PageRank for SentimentWortschatz took 0.02122950553894043s
Interlinking | Calculation of Degree of Connection for SentimentWortschatz took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SentimentWortschatz took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for SentimentWortschatz took 5.245208740234375e-05s
Believability | Calculation of trust value for SentimentWortschatz took 1.4066696166992188e-05s
INFO | --- Analysis for sentiws took 4.39475679397583s
Availability | SPARQL endpoint availability check for seoul-bike-data took 30.173482656478882s
Availability | VoID file availability check for seoul-bike-data took 0.0008020401000976562s
Completeness | Calculation of interlinking completeness for seoul-bike-data took 0.28948330879211426s
Reputation | Calculation of the PageRank for seoul-bike-data took 0.02154231071472168s
Interlinking | Calculation of Degree of Connection for seoul-bike-data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for seoul-bike-data took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for seoul-bike-data took 3.5762786865234375e-05s
Believability | Calculation of trust value for seoul-bike-data took 1.239776611328125e-05s
INFO | --- Analysis for seoul-bike-data took 72.91050362586975s
Availability | SPARQL endpoint availability check for Serendipity took 3.895359754562378s
Availability | VoID file availability check for Serendipity took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for Serendipity took 0.2879304885864258s
Reputation | Calculation of the PageRank for Serendipity took 0.021712541580200195s
Interlinking | Calculation of Degree of Connection for Serendipity took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Serendipity took 0.0010080337524414062s
Interlinking | Calculation of Clustering coefficient for Serendipity took 9.274482727050781e-05s
Believability | Calculation of trust value for Serendipity took 1.5020370483398438e-05s
INFO | --- Analysis for serendipity took 10.415976285934448s
Availability | SPARQL endpoint availability check for Sherry Wine Vocabulary took 8.821487426757812e-05s
Availability | VoID file availability check for Sherry Wine Vocabulary took 0.0005071163177490234s
Completeness | Calculation of interlinking completeness for Sherry Wine Vocabulary took 0.31236696243286133s
Reputation | Calculation of the PageRank for Sherry Wine Vocabulary took 0.021146535873413086s
Interlinking | Calculation of Degree of Connection for Sherry Wine Vocabulary took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Sherry Wine Vocabulary took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Sherry Wine Vocabulary took 3.838539123535156e-05s
Believability | Calculation of trust value for Sherry Wine Vocabulary took 1.5020370483398438e-05s
INFO | --- Analysis for Sherry_Wine took 2.751746416091919s
Availability | SPARQL endpoint availability check for Sherry Wine took 9.918212890625e-05s
Availability | VoID file availability check for Sherry Wine took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for Sherry Wine took 0.28598809242248535s
Reputation | Calculation of the PageRank for Sherry Wine took 0.021111726760864258s
Interlinking | Calculation of Degree of Connection for Sherry Wine took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Sherry Wine took 0.0008704662322998047s
Interlinking | Calculation of Clustering coefficient for Sherry Wine took 4.100799560546875e-05s
Believability | Calculation of trust value for Sherry Wine took 1.52587890625e-05s
INFO | --- Analysis for Sherry_Wine_ took 2.578139066696167s
Availability | SPARQL endpoint availability check for Shoah victims? names took 0.34349489212036133s
Availability | VoID file availability check for Shoah victims? names took 0.2547450065612793s
Extra | Recovery of all triples for Shoah victims? names took 0.9236493110656738s
Performance | Total latancy measurement for Shoah victims? names took 0.4378054141998291s
Amount of data | Number of triples check for Shoah victims? names took 1.299736738204956s
Interoperability | New terms check for Shoah victims? names took 1.8386139869689941s
Versatility | Languages check for Shoah victims? names took 19.093710899353027s
Interpretability | Number of blank nodes check for Shoah victims? names took 3.1715047359466553s
Security | Check HTTPS for Shoah victims? names took 0.21464800834655762s
Interpretability | RDF structures check for Shoah victims? names took 0.20819330215454102s
Versatility | Serialization formats check for Shoah victims? names took 0.2858259677886963s
Availability | RDF dump link check for Shoah victims? names took 0.1400773525238037s
License | MR license check for Shoah victims? names took 0.3039970397949219s
License | HR license check for Shoah victims? names took 8.090599536895752s
Amount of data | Number of property check for Shoah victims? names took 0.131941556930542s
Understandability | Number of label check for Shoah victims? names took 0.8610959053039551s
Understandability | URI regex check for Shoah victims? names took 0.39107394218444824s
Understandability | Vocabs check for Shoah victims? names took 0.10869216918945312s
Verifiability | Authors check for Shoah victims? names took 0.1278994083404541s
Verifiability | Publishers check for Shoah victims? names took 0.19370436668395996s
Performance | Throughput check for Shoah victims? names took 10.995530843734741s
Amount of data | Check the number of entities for Shoah victims? names took 3.886222839355469e-05s
Verifiability | Contribs. check for Shoah victims? names took 0.06909847259521484s
Interlinking | sameAs chians check for Shoah victims? names took 0.14073920249938965s
Interlinking | skos check for Shoah victims? names took 0.2290019989013672s
Interlinking | skos check for Shoah victims? names took 0.06701016426086426s
Timeliness | dataset update frequency check for Shoah victims? names took 0.18111729621887207s
Currency | Creation date check for Shoah victims? names took 0.18538880348205566s
Currency | Modification date check for Shoah victims? names took 0.14850878715515137s
Rep.Conc. | URIs length for Shoah victims? names took 2.5915420055389404s
Interoperability | New vocabularies check for Shoah victims? names took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Shoah victims? names took 0.11446213722229004s
Accuracy | Check Functional Property for Shoah victims? names took 0.10632729530334473s
Accuracy | Check Inverse Functional Property for Shoah victims? names took 0.05955243110656738s
Accuracy | Check Empty annotation labels for Shoah victims? names took 0.35413527488708496s
Accuracy | Check White space in annotation for Shoah victims? names took 0.02842092514038086s
Accuracy | Check Datatype consistency for Shoah victims? names took 0.02929830551147461s
Consistency | Disjoint class check for Shoah victims? names took 0.18070292472839355s
Consistency | Check Misplaced properties for Shoah victims? names took 2.0526723861694336s
Consistency | Misplaced classes for Shoah victims? names took 0.18971633911132812s
Consistency | Check Ontology hijacking for Shoah victims? names took 1.807173252105713s
Consistency | Check Invalid usage of undefined classes for Shoah victims? names took 1.458254337310791s
Consistency | Check Invalid usage of undefined properties for Shoah victims? names took 3.3001842498779297s
Conciseness | Check Extensional conciseness for Shoah victims? names took 0.03433680534362793s
Conciseness | Check Intensional conciseness for Shoah victims? names took 0.13177490234375s
Security | Sign check for Shoah victims? names took 0.3824880123138428s
Availability | Check URIs Dereferenciability for Shoah victims? names took 1029.2012977600098s
Completeness | Calculation of interlinking completeness for Shoah victims? names took 0.49935483932495117s
Reputation | Calculation of the PageRank for Shoah victims? names took 0.02129387855529785s
Interlinking | Calculation of Degree of Connection for Shoah victims? names took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Shoah victims? names took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Shoah victims? names took 4.410743713378906e-05s
Interoperability | Check the re-using of existing vocabs for Shoah victims? names took 1.6689300537109375e-06s
Believability | Calculation of trust value for Shoah victims? names took 1.6689300537109375e-05s
INFO | --- Analysis for shoah-victims-names took 1146.897126674652s
Availability | SPARQL endpoint availability check for Person took 5.7220458984375e-05s
Availability | VoID file availability check for Person took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for Person took 0.27922582626342773s
Reputation | Calculation of the PageRank for Person took 0.02244257926940918s
Interlinking | Calculation of Degree of Connection for Person took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Person took 0.0009019374847412109s
Interlinking | Calculation of Clustering coefficient for Person took 4.291534423828125e-05s
Believability | Calculation of trust value for Person took 1.5735626220703125e-05s
INFO | --- Analysis for Shripriya_Dubey took 2.6557819843292236s
Availability | SPARQL endpoint availability check for Jishnu Raghavan (1976-2016) took 9.012222290039062e-05s
Availability | VoID file availability check for Jishnu Raghavan (1976-2016) took 0.0005421638488769531s
Completeness | Calculation of interlinking completeness for Jishnu Raghavan (1976-2016) took 0.3327674865722656s
Reputation | Calculation of the PageRank for Jishnu Raghavan (1976-2016) took 0.023456335067749023s
Interlinking | Calculation of Degree of Connection for Jishnu Raghavan (1976-2016) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Jishnu Raghavan (1976-2016) took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Jishnu Raghavan (1976-2016) took 3.6716461181640625e-05s
Believability | Calculation of trust value for Jishnu Raghavan (1976-2016) took 1.33514404296875e-05s
INFO | --- Analysis for Shutterstock took 2.7795217037200928s
Availability | SPARQL endpoint availability check for SIMPLE took 4.601478576660156e-05s
Availability | VoID file availability check for SIMPLE took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for SIMPLE took 0.3176908493041992s
Reputation | Calculation of the PageRank for SIMPLE took 0.02192974090576172s
Interlinking | Calculation of Degree of Connection for SIMPLE took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for SIMPLE took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for SIMPLE took 4.744529724121094e-05s
Believability | Calculation of trust value for SIMPLE took 1.3828277587890625e-05s
INFO | --- Analysis for simple took 8.196754217147827s
Availability | SPARQL endpoint availability check for SITC-V4 took 25.347015619277954s
Availability | VoID file availability check for SITC-V4 took 0.0006287097930908203s
Completeness | Calculation of interlinking completeness for SITC-V4 took 0.29766249656677246s
Reputation | Calculation of the PageRank for SITC-V4 took 0.021477222442626953s
Interlinking | Calculation of Degree of Connection for SITC-V4 took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for SITC-V4 took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for SITC-V4 took 4.57763671875e-05s
Believability | Calculation of trust value for SITC-V4 took 6.9141387939453125e-06s
INFO | --- Analysis for sitc-v4 took 124.84761381149292s
Availability | SPARQL endpoint availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 5.888938903808594e-05s
Availability | VoID file availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0008006095886230469s
Completeness | Calculation of interlinking completeness for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.28995728492736816s
Reputation | Calculation of the PageRank for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.020990848541259766s
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.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 4.935264587402344e-05s
Believability | Calculation of trust value for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 1.4781951904296875e-05s
INFO | --- Analysis for sli_galnet_rdf took 12.886954307556152s
Availability | SPARQL endpoint availability check for Slideshare2RDF Server took 4.482269287109375e-05s
Availability | VoID file availability check for Slideshare2RDF Server took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for Slideshare2RDF Server took 0.3633091449737549s
Reputation | Calculation of the PageRank for Slideshare2RDF Server took 0.020925283432006836s
Interlinking | Calculation of Degree of Connection for Slideshare2RDF Server took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Slideshare2RDF Server took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Slideshare2RDF Server took 3.695487976074219e-05s
Believability | Calculation of trust value for Slideshare2RDF Server took 1.1205673217773438e-05s
INFO | --- Analysis for slideshare2rdf took 2.659911870956421s
Availability | SPARQL endpoint availability check for Linked Stage Graph took 0.4666008949279785s
Availability | VoID file availability check for Linked Stage Graph took 0.00030922889709472656s
Extra | Recovery of all triples for Linked Stage Graph took 1.962312936782837s
Performance | Total latancy measurement for Linked Stage Graph took 1.2656619548797607s
Amount of data | Number of triples check for Linked Stage Graph took 0.26290130615234375s
Interoperability | New terms check for Linked Stage Graph took 1.7603199481964111s
Versatility | Languages check for Linked Stage Graph took 0.737861156463623s
Interpretability | Number of blank nodes check for Linked Stage Graph took 0.261735200881958s
Security | Check HTTPS for Linked Stage Graph took 0.18276166915893555s
Interpretability | RDF structures check for Linked Stage Graph took 0.4889397621154785s
Versatility | Serialization formats check for Linked Stage Graph took 0.36834239959716797s
Availability | RDF dump link check for Linked Stage Graph took 0.25282883644104004s
License | MR license check for Linked Stage Graph took 0.5027391910552979s
License | HR license check for Linked Stage Graph took 1.7806618213653564s
Amount of data | Number of property check for Linked Stage Graph took 0.23878693580627441s
Understandability | Number of label check for Linked Stage Graph took 0.7448225021362305s
Understandability | URI regex check for Linked Stage Graph took 0.716801643371582s
Understandability | Vocabs check for Linked Stage Graph took 0.34832334518432617s
Verifiability | Authors check for Linked Stage Graph took 0.26111888885498047s
Verifiability | Publishers check for Linked Stage Graph took 0.2661757469177246s
Performance | Throughput check for Linked Stage Graph took 10.563952207565308s
Amount of data | Check the number of entities for Linked Stage Graph took 8.0108642578125e-05s
Verifiability | Contribs. check for Linked Stage Graph took 0.2514622211456299s
Interlinking | sameAs chians check for Linked Stage Graph took 0.3269062042236328s
Interlinking | skos check for Linked Stage Graph took 0.31913185119628906s
Interlinking | skos check for Linked Stage Graph took 0.2591671943664551s
Timeliness | dataset update frequency check for Linked Stage Graph took 0.426654577255249s
Currency | Creation date check for Linked Stage Graph took 0.5330233573913574s
Currency | Modification date check for Linked Stage Graph took 0.5099139213562012s
Rep.Conc. | URIs length for Linked Stage Graph took 1.605900764465332s
Interoperability | New vocabularies check for Linked Stage Graph took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for Linked Stage Graph took 0.23233652114868164s
Accuracy | Check Functional Property for Linked Stage Graph took 0.46804261207580566s
Accuracy | Check Inverse Functional Property for Linked Stage Graph took 0.46774888038635254s
Accuracy | Check Empty annotation labels for Linked Stage Graph took 0.900944709777832s
Accuracy | Check White space in annotation for Linked Stage Graph took 0.02398824691772461s
Accuracy | Check Datatype consistency for Linked Stage Graph took 0.029139280319213867s
Consistency | Disjoint class check for Linked Stage Graph took 0.267317533493042s
Consistency | Check Misplaced properties for Linked Stage Graph took 1.079117774963379s
Consistency | Misplaced classes for Linked Stage Graph took 0.6801168918609619s
Consistency | Check Ontology hijacking for Linked Stage Graph took 2.145153760910034s
Consistency | Check Invalid usage of undefined classes for Linked Stage Graph took 1.4234445095062256s
Consistency | Check Invalid usage of undefined properties for Linked Stage Graph took 1.9539213180541992s
Conciseness | Check Extensional conciseness for Linked Stage Graph took 0.02774214744567871s
Conciseness | Check Intensional conciseness for Linked Stage Graph took 0.5977814197540283s
Security | Sign check for Linked Stage Graph took 0.636509895324707s
Availability | Check URIs Dereferenciability for Linked Stage Graph took 4833.5811405181885s
Completeness | Calculation of interlinking completeness for Linked Stage Graph took 0.7060558795928955s
Reputation | Calculation of the PageRank for Linked Stage Graph took 0.0207979679107666s
Interlinking | Calculation of Degree of Connection for Linked Stage Graph took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Linked Stage Graph took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Linked Stage Graph took 0.00012111663818359375s
Interoperability | Check the re-using of existing vocabs for Linked Stage Graph took 2.384185791015625e-06s
Believability | Calculation of trust value for Linked Stage Graph took 1.4543533325195312e-05s
INFO | --- Analysis for slod took 4902.907032012939s
Availability | SPARQL endpoint availability check for Smart Points Of Interest @PSNC took 0.5979256629943848s
Availability | VoID file availability check for Smart Points Of Interest @PSNC took 0.0005681514739990234s
Extra | Recovery of all triples for Smart Points Of Interest @PSNC took 115.77207136154175s
Performance | Total latancy measurement for Smart Points Of Interest @PSNC took 0.9726793766021729s
Amount of data | Number of triples check for Smart Points Of Interest @PSNC took 9.126729011535645s
Interoperability | New terms check for Smart Points Of Interest @PSNC took 14.292521238327026s
Versatility | Languages check for Smart Points Of Interest @PSNC took 300.2240569591522s
Interpretability | Number of blank nodes check for Smart Points Of Interest @PSNC took 2.090508460998535s
Interpretability | RDF structures check for Smart Points Of Interest @PSNC took 0.3179631233215332s
Versatility | Serialization formats check for Smart Points Of Interest @PSNC took 9.785916805267334s
Availability | RDF dump link check for Smart Points Of Interest @PSNC took 0.38243722915649414s
License | MR license check for Smart Points Of Interest @PSNC took 0.9955925941467285s
License | HR license check for Smart Points Of Interest @PSNC took 300.1909329891205s
Amount of data | Number of property check for Smart Points Of Interest @PSNC took 0.19764041900634766s
Understandability | Number of label check for Smart Points Of Interest @PSNC took 3.1614339351654053s
Understandability | URI regex check for Smart Points Of Interest @PSNC took 1.147141933441162s
Understandability | Vocabs check for Smart Points Of Interest @PSNC took 0.5889232158660889s
Verifiability | Authors check for Smart Points Of Interest @PSNC took 0.21058320999145508s
Verifiability | Publishers check for Smart Points Of Interest @PSNC took 0.2534816265106201s
Performance | Throughput check for Smart Points Of Interest @PSNC took 11.118362188339233s
Amount of data | Check the number of entities for Smart Points Of Interest @PSNC took 8.749961853027344e-05s
Verifiability | Contribs. check for Smart Points Of Interest @PSNC took 0.20197629928588867s
Interlinking | sameAs chians check for Smart Points Of Interest @PSNC took 0.21672606468200684s
Interlinking | skos check for Smart Points Of Interest @PSNC took 0.4986460208892822s
Interlinking | skos check for Smart Points Of Interest @PSNC took 0.47231316566467285s
Timeliness | dataset update frequency check for Smart Points Of Interest @PSNC took 4.082052946090698s
Currency | Creation date check for Smart Points Of Interest @PSNC took 0.49149179458618164s
Currency | Modification date check for Smart Points Of Interest @PSNC took 0.23637676239013672s
Rep.Conc. | URIs length for Smart Points Of Interest @PSNC took 152.8778591156006s
Interoperability | New vocabularies check for Smart Points Of Interest @PSNC took 1.1682510375976562e-05s
Consistency | Deprecated classes/propertiers check for Smart Points Of Interest @PSNC took 0.2004842758178711s
Accuracy | Check Functional Property for Smart Points Of Interest @PSNC took 0.47287964820861816s
Accuracy | Check Inverse Functional Property for Smart Points Of Interest @PSNC took 0.4747464656829834s
Accuracy | Check Empty annotation labels for Smart Points Of Interest @PSNC took 43.02882933616638s
Accuracy | Check White space in annotation for Smart Points Of Interest @PSNC took 2.716017246246338s
Accuracy | Check Datatype consistency for Smart Points Of Interest @PSNC took 2.801656723022461s
Consistency | Disjoint class check for Smart Points Of Interest @PSNC took 0.20276212692260742s
Consistency | Check Misplaced properties for Smart Points Of Interest @PSNC took 87.17468762397766s
Consistency | Misplaced classes for Smart Points Of Interest @PSNC took 8.73490023612976s
Consistency | Check Ontology hijacking for Smart Points Of Interest @PSNC took 34.90239095687866s
Consistency | Check Invalid usage of undefined classes for Smart Points Of Interest @PSNC took 1.597917079925537s
Consistency | Check Invalid usage of undefined properties for Smart Points Of Interest @PSNC took 88.32827305793762s
Conciseness | Check Extensional conciseness for Smart Points Of Interest @PSNC took 2.7821762561798096s
Conciseness | Check Intensional conciseness for Smart Points Of Interest @PSNC took 0.5445282459259033s
Security | Sign check for Smart Points Of Interest @PSNC took 1.4784021377563477s
Availability | Check URIs Dereferenciability for Smart Points Of Interest @PSNC took 8.726407289505005s
Completeness | Calculation of interlinking completeness for Smart Points Of Interest @PSNC took 0.40566563606262207s
Reputation | Calculation of the PageRank for Smart Points Of Interest @PSNC took 0.021398544311523438s
Interlinking | Calculation of Degree of Connection for Smart Points Of Interest @PSNC took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Smart Points Of Interest @PSNC took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Smart Points Of Interest @PSNC took 0.00010967254638671875s
Interoperability | Check the re-using of existing vocabs for Smart Points Of Interest @PSNC took 5.4836273193359375e-06s
Believability | Calculation of trust value for Smart Points Of Interest @PSNC took 1.4066696166992188e-05s
INFO | --- Analysis for Smart_POI_dataset took 2280.556340932846s
Availability | SPARQL endpoint availability check for SmartLink: Linked Services Non-Functional Properties took 4.513302326202393s
Availability | VoID file availability check for SmartLink: Linked Services Non-Functional Properties took 0.0006959438323974609s
Completeness | Calculation of interlinking completeness for SmartLink: Linked Services Non-Functional Properties took 0.29991960525512695s
Reputation | Calculation of the PageRank for SmartLink: Linked Services Non-Functional Properties took 0.02118372917175293s
Interlinking | Calculation of Degree of Connection for SmartLink: Linked Services Non-Functional Properties took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for SmartLink: Linked Services Non-Functional Properties took 0.0007903575897216797s
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.049041748046875e-05s
INFO | --- Analysis for smartlink took 11.140613555908203s
Availability | SPARQL endpoint availability check for SNIK took 32.8132700920105s
Availability | VoID file availability check for SNIK took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for SNIK took 0.2824990749359131s
Reputation | Calculation of the PageRank for SNIK took 0.02080845832824707s
Interlinking | Calculation of Degree of Connection for SNIK took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for SNIK took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for SNIK took 7.796287536621094e-05s
Believability | Calculation of trust value for SNIK took 1.0013580322265625e-05s
INFO | --- Analysis for snik took 49.6559944152832s
Availability | SPARQL endpoint availability check for SocialLink took 1.18328857421875s
Availability | VoID file availability check for SocialLink took 0.0005936622619628906s
Completeness | Calculation of interlinking completeness for SocialLink took 0.3178856372833252s
Reputation | Calculation of the PageRank for SocialLink took 0.020615816116333008s
Interlinking | Calculation of Degree of Connection for SocialLink took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for SocialLink took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for SocialLink took 7.581710815429688e-05s
Believability | Calculation of trust value for SocialLink took 1.3828277587890625e-05s
INFO | --- Analysis for SocialLink took 5.692986011505127s
Availability | SPARQL endpoint availability check for FamilyRelations as SocialRole took 8.96453857421875e-05s
Availability | VoID file availability check for FamilyRelations as SocialRole took 0.0007278919219970703s
Completeness | Calculation of interlinking completeness for FamilyRelations as SocialRole took 0.2783787250518799s
Reputation | Calculation of the PageRank for FamilyRelations as SocialRole took 0.020894765853881836s
Interlinking | Calculation of Degree of Connection for FamilyRelations as SocialRole took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for FamilyRelations as SocialRole took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for FamilyRelations as SocialRole took 3.552436828613281e-05s
Believability | Calculation of trust value for FamilyRelations as SocialRole took 1.1444091796875e-05s
INFO | --- Analysis for SocialRoles took 10.02297592163086s
Availability | SPARQL endpoint availability check for Social Semantic Web Thesaurus took 0.2389082908630371s
Availability | VoID file availability check for Social Semantic Web Thesaurus took 0.0008602142333984375s
Extra | Recovery of all triples for Social Semantic Web Thesaurus took 16.874475479125977s
Performance | Total latancy measurement for Social Semantic Web Thesaurus took 0.46498703956604004s
Amount of data | Number of triples check for Social Semantic Web Thesaurus took 0.18592476844787598s
Interoperability | New terms check for Social Semantic Web Thesaurus took 1.682023286819458s
Versatility | Languages check for Social Semantic Web Thesaurus took 0.33220434188842773s
Interpretability | Number of blank nodes check for Social Semantic Web Thesaurus took 0.16584205627441406s
Security | Check HTTPS for Social Semantic Web Thesaurus took 0.3349616527557373s
Interpretability | RDF structures check for Social Semantic Web Thesaurus took 0.11197972297668457s
Versatility | Serialization formats check for Social Semantic Web Thesaurus took 0.11895370483398438s
Availability | RDF dump link check for Social Semantic Web Thesaurus took 0.7066335678100586s
License | MR license check for Social Semantic Web Thesaurus took 0.12147951126098633s
License | HR license check for Social Semantic Web Thesaurus took 0.11201596260070801s
Amount of data | Number of property check for Social Semantic Web Thesaurus took 0.12361836433410645s
Understandability | Number of label check for Social Semantic Web Thesaurus took 0.11897063255310059s
Understandability | URI regex check for Social Semantic Web Thesaurus took 0.17591500282287598s
Understandability | Vocabs check for Social Semantic Web Thesaurus took 0.11747860908508301s
Verifiability | Authors check for Social Semantic Web Thesaurus took 0.13836264610290527s
Verifiability | Publishers check for Social Semantic Web Thesaurus took 0.12526893615722656s
Performance | Throughput check for Social Semantic Web Thesaurus took 10.554630994796753s
Amount of data | Check the number of entities for Social Semantic Web Thesaurus took 8.296966552734375e-05s
Verifiability | Contribs. check for Social Semantic Web Thesaurus took 0.12681174278259277s
Interlinking | sameAs chians check for Social Semantic Web Thesaurus took 0.11795306205749512s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.11610150337219238s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.08240032196044922s
Timeliness | dataset update frequency check for Social Semantic Web Thesaurus took 0.08891034126281738s
Currency | Creation date check for Social Semantic Web Thesaurus took 0.18543076515197754s
Currency | Modification date check for Social Semantic Web Thesaurus took 0.19813990592956543s
Rep.Conc. | URIs length for Social Semantic Web Thesaurus took 1.531578540802002s
Interoperability | New vocabularies check for Social Semantic Web Thesaurus took 0.7371211051940918s
Consistency | Deprecated classes/propertiers check for Social Semantic Web Thesaurus took 0.13655829429626465s
Accuracy | Check Functional Property for Social Semantic Web Thesaurus took 0.08687257766723633s
Accuracy | Check Inverse Functional Property for Social Semantic Web Thesaurus took 0.09520888328552246s
Accuracy | Check Empty annotation labels for Social Semantic Web Thesaurus took 0.4770686626434326s
Accuracy | Check White space in annotation for Social Semantic Web Thesaurus took 0.01226663589477539s
Consistency | Disjoint class check for Social Semantic Web Thesaurus took 0.09386610984802246s
Consistency | Check Misplaced properties for Social Semantic Web Thesaurus took 0.2993137836456299s
Consistency | Misplaced classes for Social Semantic Web Thesaurus took 0.07973337173461914s
Consistency | Check Ontology hijacking for Social Semantic Web Thesaurus took 2.2579281330108643s
Consistency | Check Invalid usage of undefined properties for Social Semantic Web Thesaurus took 1.6699345111846924s
Conciseness | Check Extensional conciseness for Social Semantic Web Thesaurus took 0.0001842975616455078s
Security | Sign check for Social Semantic Web Thesaurus took 0.08936071395874023s
Availability | Check URIs Dereferenciability for Social Semantic Web Thesaurus took 104.23854541778564s
Completeness | Calculation of interlinking completeness for Social Semantic Web Thesaurus took 0.29998230934143066s
Reputation | Calculation of the PageRank for Social Semantic Web Thesaurus took 0.02109360694885254s
Interlinking | Calculation of Degree of Connection for Social Semantic Web Thesaurus took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Social Semantic Web Thesaurus took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Social Semantic Web Thesaurus took 9.989738464355469e-05s
Interoperability | Check the re-using of existing vocabs for Social Semantic Web Thesaurus took 0.5539014339447021s
Believability | Calculation of trust value for Social Semantic Web Thesaurus took 1.52587890625e-05s
INFO | --- Analysis for socialsemweb-thesaurus took 280.91847705841064s
Availability | SPARQL endpoint availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.21220111846923828s
Availability | VoID file availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0005168914794921875s
Extra | Recovery of all triples for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 120.02775835990906s
Performance | Total latancy measurement for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.0258879661560059s
Amount of data | Number of triples check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.818429946899414s
Interoperability | New terms check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 14.292365789413452s
Versatility | Languages check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 300.2437813282013s
Interpretability | Number of blank nodes check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.2390637397766113s
Interpretability | RDF structures check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2152566909790039s
Versatility | Serialization formats check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 11.041918992996216s
Availability | RDF dump link check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.35762643814086914s
License | MR license check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.8178305625915527s
License | HR license check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 300.1665692329407s
Amount of data | Number of property check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2050011157989502s
Understandability | Number of label check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 3.2300093173980713s
Understandability | URI regex check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.22023606300354s
Understandability | Vocabs check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.619849681854248s
Verifiability | Authors check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.21031498908996582s
Verifiability | Publishers check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.25690126419067383s
Performance | Throughput check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 11.079895257949829s
Amount of data | Check the number of entities for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 7.557868957519531e-05s
Verifiability | Contribs. check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2032914161682129s
Interlinking | sameAs chians check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.21729183197021484s
Interlinking | skos check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.4456820487976074s
Interlinking | skos check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.47960972785949707s
Timeliness | dataset update frequency check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 7.063549041748047s
Currency | Creation date check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.48801636695861816s
Currency | Modification date check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.24860000610351562s
Rep.Conc. | URIs length for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 159.11319780349731s
Interoperability | New vocabularies check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.2159347534179688e-05s
Consistency | Deprecated classes/propertiers check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.20343351364135742s
Accuracy | Check Functional Property for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.5390732288360596s
Accuracy | Check Inverse Functional Property for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.5257670879364014s
Accuracy | Check Empty annotation labels for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 41.96790385246277s
Accuracy | Check White space in annotation for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.700136661529541s
Accuracy | Check Datatype consistency for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.8270628452301025s
Consistency | Disjoint class check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.21548128128051758s
Consistency | Check Misplaced properties for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 87.12038731575012s
Consistency | Misplaced classes for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.735414505004883s
Consistency | Check Ontology hijacking for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 34.65994381904602s
Consistency | Check Invalid usage of undefined classes for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.5969998836517334s
Consistency | Check Invalid usage of undefined properties for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 88.57315111160278s
Conciseness | Check Extensional conciseness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.7853519916534424s
Conciseness | Check Intensional conciseness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.5651853084564209s
Security | Sign check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.2484197616577148s
Availability | Check URIs Dereferenciability for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 10.242993354797363s
Completeness | Calculation of interlinking completeness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.6446259021759033s
Reputation | Calculation of the PageRank for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.021405935287475586s
Interlinking | Calculation of Degree of Connection for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0007872581481933594s
Interlinking | Calculation of Clustering coefficient for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 4.9591064453125e-05s
Interoperability | Check the re-using of existing vocabs for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.384185791015625e-06s
Believability | Calculation of trust value for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.1444091796875e-05s
INFO | --- Analysis for Soil_maps took 2290.336782693863s
Availability | SPARQL endpoint availability check for terrorrist ontology took 0.00010395050048828125s
Availability | VoID file availability check for terrorrist ontology took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for terrorrist ontology took 0.27504539489746094s
Reputation | Calculation of the PageRank for terrorrist ontology took 0.021242856979370117s
Interlinking | Calculation of Degree of Connection for terrorrist ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for terrorrist ontology took 0.0007872581481933594s
Interlinking | Calculation of Clustering coefficient for terrorrist ontology took 3.743171691894531e-05s
Believability | Calculation of trust value for terrorrist ontology took 1.5020370483398438e-05s
INFO | --- Analysis for somya_omer took 2.7524619102478027s
Availability | SPARQL endpoint availability check for Sonclubcx took 0.000110626220703125s
Availability | VoID file availability check for Sonclubcx took 0.0005834102630615234s
Completeness | Calculation of interlinking completeness for Sonclubcx took 0.33345818519592285s
Reputation | Calculation of the PageRank for Sonclubcx took 0.022472620010375977s
Interlinking | Calculation of Degree of Connection for Sonclubcx took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Sonclubcx took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Sonclubcx took 1.4781951904296875e-05s
Believability | Calculation of trust value for Sonclubcx took 1.52587890625e-05s
INFO | --- Analysis for sonclubcx took 4.11129903793335s
Availability | SPARQL endpoint availability check for SORS took 9.298324584960938e-05s
Availability | VoID file availability check for SORS took 0.0006835460662841797s
Completeness | Calculation of interlinking completeness for SORS took 0.28789448738098145s
Reputation | Calculation of the PageRank for SORS took 0.02045750617980957s
Interlinking | Calculation of Degree of Connection for SORS took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SORS took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for SORS took 5.125999450683594e-05s
Believability | Calculation of trust value for SORS took 1.0013580322265625e-05s
INFO | --- Analysis for sors took 12.910269737243652s
Availability | SPARQL endpoint availability check for southampton-ac-uk took 4.410743713378906e-05s
Availability | VoID file availability check for southampton-ac-uk took 0.0005614757537841797s
Completeness | Calculation of interlinking completeness for southampton-ac-uk took 0.2874743938446045s
Reputation | Calculation of the PageRank for southampton-ac-uk took 0.022017717361450195s
Interlinking | Calculation of Degree of Connection for southampton-ac-uk took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for southampton-ac-uk took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for southampton-ac-uk took 9.322166442871094e-05s
Believability | Calculation of trust value for southampton-ac-uk took 1.4543533325195312e-05s
INFO | --- Analysis for southampton-ac-uk took 3.9822447299957275s
Availability | SPARQL endpoint availability check for Apps using our data (University of Southampton) took 3.28701114654541s
Availability | VoID file availability check for Apps using our data (University of Southampton) took 0.0006368160247802734s
Completeness | Calculation of interlinking completeness for Apps using our data (University of Southampton) took 0.298980712890625s
Reputation | Calculation of the PageRank for Apps using our data (University of Southampton) took 0.02212214469909668s
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.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Apps using our data (University of Southampton) took 3.600120544433594e-05s
Believability | Calculation of trust value for Apps using our data (University of Southampton) took 1.4781951904296875e-05s
INFO | --- Analysis for southampton-ac-uk-apps took 10.878865003585815s
Availability | SPARQL endpoint availability check for ECS Southampton EPrints took 8.988380432128906e-05s
Availability | VoID file availability check for ECS Southampton EPrints took 0.0005552768707275391s
Completeness | Calculation of interlinking completeness for ECS Southampton EPrints took 0.29294633865356445s
Reputation | Calculation of the PageRank for ECS Southampton EPrints took 0.021059751510620117s
Interlinking | Calculation of Degree of Connection for ECS Southampton EPrints took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ECS Southampton EPrints took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for ECS Southampton EPrints took 0.00010132789611816406s
Believability | Calculation of trust value for ECS Southampton EPrints took 1.6689300537109375e-05s
INFO | --- Analysis for southampton-ecs-eprints took 2.743147611618042s
Availability | SPARQL endpoint availability check for Spanish Linguistic Datasets took 0.47682952880859375s
Availability | VoID file availability check for Spanish Linguistic Datasets took 0.0005834102630615234s
Extra | Recovery of all triples for Spanish Linguistic Datasets took 162.81572556495667s
Performance | Total latancy measurement for Spanish Linguistic Datasets took 1.2182490825653076s
Amount of data | Number of triples check for Spanish Linguistic Datasets took 2.1533114910125732s
Interoperability | New terms check for Spanish Linguistic Datasets took 3.2154548168182373s
Versatility | Languages check for Spanish Linguistic Datasets took 44.5180401802063s
Interpretability | Number of blank nodes check for Spanish Linguistic Datasets took 1.178018569946289s
Security | Check HTTPS for Spanish Linguistic Datasets took 0.12276506423950195s
Interpretability | RDF structures check for Spanish Linguistic Datasets took 0.28609395027160645s
Versatility | Serialization formats check for Spanish Linguistic Datasets took 0.28393101692199707s
Availability | RDF dump link check for Spanish Linguistic Datasets took 0.2861597537994385s
License | MR license check for Spanish Linguistic Datasets took 0.2894589900970459s
License | HR license check for Spanish Linguistic Datasets took 0.39774322509765625s
Amount of data | Number of property check for Spanish Linguistic Datasets took 0.2964763641357422s
Understandability | Number of label check for Spanish Linguistic Datasets took 0.3336973190307617s
Understandability | URI regex check for Spanish Linguistic Datasets took 0.5715880393981934s
Understandability | Vocabs check for Spanish Linguistic Datasets took 0.30168581008911133s
Verifiability | Authors check for Spanish Linguistic Datasets took 0.2790079116821289s
Verifiability | Publishers check for Spanish Linguistic Datasets took 0.2871408462524414s
Performance | Throughput check for Spanish Linguistic Datasets took 11.33157730102539s
Amount of data | Check the number of entities for Spanish Linguistic Datasets took 0.00011205673217773438s
Verifiability | Contribs. check for Spanish Linguistic Datasets took 0.31137990951538086s
Interlinking | sameAs chians check for Spanish Linguistic Datasets took 0.2758479118347168s
Interlinking | skos check for Spanish Linguistic Datasets took 0.2748420238494873s
Interlinking | skos check for Spanish Linguistic Datasets took 0.23067593574523926s
Timeliness | dataset update frequency check for Spanish Linguistic Datasets took 0.3005242347717285s
Currency | Creation date check for Spanish Linguistic Datasets took 0.5621011257171631s
Currency | Modification date check for Spanish Linguistic Datasets took 0.5902791023254395s
Rep.Conc. | URIs length for Spanish Linguistic Datasets took 58.647106409072876s
Interoperability | New vocabularies check for Spanish Linguistic Datasets took 1.1920928955078125e-05s
Consistency | Deprecated classes/propertiers check for Spanish Linguistic Datasets took 0.2806839942932129s
Accuracy | Check Functional Property for Spanish Linguistic Datasets took 0.2778756618499756s
Accuracy | Check Inverse Functional Property for Spanish Linguistic Datasets took 0.2687358856201172s
Accuracy | Check Empty annotation labels for Spanish Linguistic Datasets took 1.0051860809326172s
Accuracy | Check White space in annotation for Spanish Linguistic Datasets took 0.010422468185424805s
Accuracy | Check Datatype consistency for Spanish Linguistic Datasets took 2.75042462348938s
Consistency | Disjoint class check for Spanish Linguistic Datasets took 0.2770509719848633s
Consistency | Check Misplaced properties for Spanish Linguistic Datasets took 4.64146089553833s
Consistency | Misplaced classes for Spanish Linguistic Datasets took 8.759209156036377s
Consistency | Check Ontology hijacking for Spanish Linguistic Datasets took 44.93741035461426s
Consistency | Check Invalid usage of undefined classes for Spanish Linguistic Datasets took 1.7392539978027344s
Consistency | Check Invalid usage of undefined properties for Spanish Linguistic Datasets took 6.055948972702026s
Conciseness | Check Extensional conciseness for Spanish Linguistic Datasets took 2.9685144424438477s
Conciseness | Check Intensional conciseness for Spanish Linguistic Datasets took 0.33705854415893555s
Security | Sign check for Spanish Linguistic Datasets took 0.29863762855529785s
Availability | Check URIs Dereferenciability for Spanish Linguistic Datasets took 10.062305450439453s
Completeness | Calculation of interlinking completeness for Spanish Linguistic Datasets took 0.54390549659729s
Reputation | Calculation of the PageRank for Spanish Linguistic Datasets took 0.021213293075561523s
Interlinking | Calculation of Degree of Connection for Spanish Linguistic Datasets took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Spanish Linguistic Datasets took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Spanish Linguistic Datasets took 4.100799560546875e-05s
Interoperability | Check the re-using of existing vocabs for Spanish Linguistic Datasets took 2.1457672119140625e-06s
Believability | Calculation of trust value for Spanish Linguistic Datasets took 1.33514404296875e-05s
INFO | --- Analysis for spanish-linguistic-datasets took 416.6242604255676s
Availability | SPARQL endpoint availability check for SPARQL Endpoint Status took 0.0539395809173584s
Availability | VoID file availability check for SPARQL Endpoint Status took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for SPARQL Endpoint Status took 0.3167288303375244s
Reputation | Calculation of the PageRank for SPARQL Endpoint Status took 0.02264690399169922s
Interlinking | Calculation of Degree of Connection for SPARQL Endpoint Status took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for SPARQL Endpoint Status took 0.0008022785186767578s
Interlinking | Calculation of Clustering coefficient for SPARQL Endpoint Status took 5.936622619628906e-05s
Believability | Calculation of trust value for SPARQL Endpoint Status took 1.6927719116210938e-05s
INFO | --- Analysis for sparql-endpoint-status took 2.8419244289398193s
Availability | SPARQL endpoint availability check for Springer Nature SciGraph took 0.00015401840209960938s
Availability | VoID file availability check for Springer Nature SciGraph took 0.0006363391876220703s
Completeness | Calculation of interlinking completeness for Springer Nature SciGraph took 0.2926337718963623s
Reputation | Calculation of the PageRank for Springer Nature SciGraph took 0.020829200744628906s
Interlinking | Calculation of Degree of Connection for Springer Nature SciGraph took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Springer Nature SciGraph took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for Springer Nature SciGraph took 9.226799011230469e-05s
Believability | Calculation of trust value for Springer Nature SciGraph took 1.2159347534179688e-05s
INFO | --- Analysis for springernaturescigraph took 3.229252338409424s
Availability | SPARQL endpoint availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 9.083747863769531e-05s
Availability | VoID file availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0006663799285888672s
Completeness | Calculation of interlinking completeness for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.27649378776550293s
Reputation | Calculation of the PageRank for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.020954370498657227s
Interlinking | Calculation of Degree of Connection for Syntactic Reference Corpus of Medieval French (SRCMF) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for Syntactic Reference Corpus of Medieval French (SRCMF) took 3.361701965332031e-05s
Believability | Calculation of trust value for Syntactic Reference Corpus of Medieval French (SRCMF) took 1.6927719116210938e-05s
INFO | --- Analysis for srcmf took 6.572784900665283s
Availability | SPARQL endpoint availability check for Lexicon of Syntactic and Semantic Framework took 0.34092235565185547s
Availability | VoID file availability check for Lexicon of Syntactic and Semantic Framework took 0.0005578994750976562s
Extra | Recovery of all triples for Lexicon of Syntactic and Semantic Framework took 1.096968173980713s
Performance | Total latancy measurement for Lexicon of Syntactic and Semantic Framework took 0.7649421691894531s
Amount of data | Number of triples check for Lexicon of Syntactic and Semantic Framework took 0.16231155395507812s
Interoperability | New terms check for Lexicon of Syntactic and Semantic Framework took 1.535745620727539s
Versatility | Languages check for Lexicon of Syntactic and Semantic Framework took 0.16468477249145508s
Interpretability | Number of blank nodes check for Lexicon of Syntactic and Semantic Framework took 0.15462541580200195s
Security | Check HTTPS for Lexicon of Syntactic and Semantic Framework took 0.10090923309326172s
Interpretability | RDF structures check for Lexicon of Syntactic and Semantic Framework took 0.15977239608764648s
Versatility | Serialization formats check for Lexicon of Syntactic and Semantic Framework took 0.14796829223632812s
Availability | RDF dump link check for Lexicon of Syntactic and Semantic Framework took 0.14975214004516602s
License | MR license check for Lexicon of Syntactic and Semantic Framework took 0.15660333633422852s
License | HR license check for Lexicon of Syntactic and Semantic Framework took 0.15862798690795898s
Amount of data | Number of property check for Lexicon of Syntactic and Semantic Framework took 0.1640915870666504s
Understandability | Number of label check for Lexicon of Syntactic and Semantic Framework took 0.1719205379486084s
Understandability | URI regex check for Lexicon of Syntactic and Semantic Framework took 0.29999446868896484s
Understandability | Vocabs check for Lexicon of Syntactic and Semantic Framework took 0.15807819366455078s
Verifiability | Authors check for Lexicon of Syntactic and Semantic Framework took 0.1672360897064209s
Verifiability | Publishers check for Lexicon of Syntactic and Semantic Framework took 0.16498589515686035s
Performance | Throughput check for Lexicon of Syntactic and Semantic Framework took 10.719680309295654s
Amount of data | Check the number of entities for Lexicon of Syntactic and Semantic Framework took 8.463859558105469e-05s
Verifiability | Contribs. check for Lexicon of Syntactic and Semantic Framework took 0.14160966873168945s
Interlinking | sameAs chians check for Lexicon of Syntactic and Semantic Framework took 0.15131783485412598s
Interlinking | skos check for Lexicon of Syntactic and Semantic Framework took 0.16107821464538574s
Interlinking | skos check for Lexicon of Syntactic and Semantic Framework took 0.15131545066833496s
Timeliness | dataset update frequency check for Lexicon of Syntactic and Semantic Framework took 0.159104585647583s
Currency | Creation date check for Lexicon of Syntactic and Semantic Framework took 0.3368067741394043s
Currency | Modification date check for Lexicon of Syntactic and Semantic Framework took 0.2849888801574707s
Rep.Conc. | URIs length for Lexicon of Syntactic and Semantic Framework took 0.4933500289916992s
Interoperability | New vocabularies check for Lexicon of Syntactic and Semantic Framework took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for Lexicon of Syntactic and Semantic Framework took 0.1312415599822998s
Accuracy | Check Functional Property for Lexicon of Syntactic and Semantic Framework took 0.1378192901611328s
Accuracy | Check Inverse Functional Property for Lexicon of Syntactic and Semantic Framework took 0.16220855712890625s
Accuracy | Check Empty annotation labels for Lexicon of Syntactic and Semantic Framework took 0.14067769050598145s
Accuracy | Check White space in annotation for Lexicon of Syntactic and Semantic Framework took 0.0003161430358886719s
Accuracy | Check Datatype consistency for Lexicon of Syntactic and Semantic Framework took 0.0347139835357666s
Consistency | Disjoint class check for Lexicon of Syntactic and Semantic Framework took 0.13893628120422363s
Consistency | Check Misplaced properties for Lexicon of Syntactic and Semantic Framework took 0.3185842037200928s
Consistency | Misplaced classes for Lexicon of Syntactic and Semantic Framework took 0.21464991569519043s
Consistency | Check Ontology hijacking for Lexicon of Syntactic and Semantic Framework took 1.6141352653503418s
Consistency | Check Invalid usage of undefined classes for Lexicon of Syntactic and Semantic Framework took 1.4397997856140137s
Consistency | Check Invalid usage of undefined properties for Lexicon of Syntactic and Semantic Framework took 1.63942551612854s
Conciseness | Check Extensional conciseness for Lexicon of Syntactic and Semantic Framework took 0.020065784454345703s
Conciseness | Check Intensional conciseness for Lexicon of Syntactic and Semantic Framework took 0.16347527503967285s
Security | Sign check for Lexicon of Syntactic and Semantic Framework took 0.15205073356628418s
Availability | Check URIs Dereferenciability for Lexicon of Syntactic and Semantic Framework took 272.6242582798004s
Completeness | Calculation of interlinking completeness for Lexicon of Syntactic and Semantic Framework took 0.3491530418395996s
Reputation | Calculation of the PageRank for Lexicon of Syntactic and Semantic Framework took 0.02097344398498535s
Interlinking | Calculation of Degree of Connection for Lexicon of Syntactic and Semantic Framework took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Lexicon of Syntactic and Semantic Framework took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Lexicon of Syntactic and Semantic Framework took 6.008148193359375e-05s
Interoperability | Check the re-using of existing vocabs for Lexicon of Syntactic and Semantic Framework took 1.6689300537109375e-06s
Believability | Calculation of trust value for Lexicon of Syntactic and Semantic Framework took 1.4781951904296875e-05s
INFO | --- Analysis for ssf took 314.6883885860443s
Availability | SPARQL endpoint availability check for St. Andrews University Resource Lists took 9.393692016601562e-05s
Availability | VoID file availability check for St. Andrews University Resource Lists took 0.0007181167602539062s
Completeness | Calculation of interlinking completeness for St. Andrews University Resource Lists took 0.29925537109375s
Reputation | Calculation of the PageRank for St. Andrews University Resource Lists took 0.021116971969604492s
Interlinking | Calculation of Degree of Connection for St. Andrews University Resource Lists took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for St. Andrews University Resource Lists took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for St. Andrews University Resource Lists took 4.3392181396484375e-05s
Believability | Calculation of trust value for St. Andrews University Resource Lists took 1.0013580322265625e-05s
INFO | --- Analysis for st-andrews-resource-lists took 3.0720717906951904s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 4.553794860839844e-05s
Availability | VoID file availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0005285739898681641s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.29093098640441895s
Reputation | Calculation of the PageRank for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.02238631248474121s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 3.719329833984375e-05s
Believability | Calculation of trust value for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 1.0967254638671875e-05s
INFO | --- Analysis for staff-organograms-and-pay-thurrock-thames-gateway-development-corporation took 3.3979437351226807s
Availability | SPARQL endpoint availability check for Stammbuch took 9.298324584960938e-05s
Availability | VoID file availability check for Stammbuch took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for Stammbuch took 0.2919938564300537s
Reputation | Calculation of the PageRank for Stammbuch took 0.022711515426635742s
Interlinking | Calculation of Degree of Connection for Stammbuch took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Stammbuch took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for Stammbuch took 3.719329833984375e-05s
Believability | Calculation of trust value for Stammbuch took 1.430511474609375e-05s
INFO | --- Analysis for Stammbuch took 2.7000439167022705s
Availability | SPARQL endpoint availability check for statistics.data.gov.uk took 1.1080198287963867s
Availability | VoID file availability check for statistics.data.gov.uk took 0.0005521774291992188s
Completeness | Calculation of interlinking completeness for statistics.data.gov.uk took 0.2944653034210205s
Reputation | Calculation of the PageRank for statistics.data.gov.uk took 0.021355152130126953s
Interlinking | Calculation of Degree of Connection for statistics.data.gov.uk took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for statistics.data.gov.uk took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for statistics.data.gov.uk took 0.00011372566223144531s
Believability | Calculation of trust value for statistics.data.gov.uk took 1.1205673217773438e-05s
INFO | --- Analysis for statistics-data-gov-uk took 4.109176397323608s
Availability | SPARQL endpoint availability check for statusnet-1w6-org took 9.703636169433594e-05s
Availability | VoID file availability check for statusnet-1w6-org took 0.0006747245788574219s
Completeness | Calculation of interlinking completeness for statusnet-1w6-org took 0.3344614505767822s
Reputation | Calculation of the PageRank for statusnet-1w6-org took 0.02229166030883789s
Interlinking | Calculation of Degree of Connection for statusnet-1w6-org took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-1w6-org took 0.0007805824279785156s
Interlinking | Calculation of Clustering coefficient for statusnet-1w6-org took 0.00011372566223144531s
Believability | Calculation of trust value for statusnet-1w6-org took 1.4543533325195312e-05s
INFO | --- Analysis for statusnet-1w6-org took 4.237282752990723s
Availability | SPARQL endpoint availability check for statusnet-20100-org took 9.489059448242188e-05s
Availability | VoID file availability check for statusnet-20100-org took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for statusnet-20100-org took 0.3139650821685791s
Reputation | Calculation of the PageRank for statusnet-20100-org took 0.020764827728271484s
Interlinking | Calculation of Degree of Connection for statusnet-20100-org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-20100-org took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for statusnet-20100-org took 6.604194641113281e-05s
Believability | Calculation of trust value for statusnet-20100-org took 1.4066696166992188e-05s
INFO | --- Analysis for statusnet-20100-org took 2.8909010887145996s
Availability | SPARQL endpoint availability check for statusnet-alexandrefranke-com took 4.673004150390625e-05s
Availability | VoID file availability check for statusnet-alexandrefranke-com took 0.0006182193756103516s
Completeness | Calculation of interlinking completeness for statusnet-alexandrefranke-com took 0.318897008895874s
Reputation | Calculation of the PageRank for statusnet-alexandrefranke-com took 0.02137279510498047s
Interlinking | Calculation of Degree of Connection for statusnet-alexandrefranke-com took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-alexandrefranke-com took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for statusnet-alexandrefranke-com took 7.605552673339844e-05s
Believability | Calculation of trust value for statusnet-alexandrefranke-com took 1.5020370483398438e-05s
INFO | --- Analysis for statusnet-alexandrefranke-com took 3.1618456840515137s
Availability | SPARQL endpoint availability check for statusnet-atari-frosch-de took 9.799003601074219e-05s
Availability | VoID file availability check for statusnet-atari-frosch-de took 0.0005555152893066406s
Completeness | Calculation of interlinking completeness for statusnet-atari-frosch-de took 0.31075143814086914s
Reputation | Calculation of the PageRank for statusnet-atari-frosch-de took 0.02120828628540039s
Interlinking | Calculation of Degree of Connection for statusnet-atari-frosch-de took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-atari-frosch-de took 0.0008165836334228516s
Interlinking | Calculation of Clustering coefficient for statusnet-atari-frosch-de took 9.393692016601562e-05s
Believability | Calculation of trust value for statusnet-atari-frosch-de took 1.4543533325195312e-05s
INFO | --- Analysis for statusnet-atari-frosch-de took 2.7199718952178955s
Availability | SPARQL endpoint availability check for statusnet-belfalas-org took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-belfalas-org took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for statusnet-belfalas-org took 0.3060643672943115s
Reputation | Calculation of the PageRank for statusnet-belfalas-org took 0.020664215087890625s
Interlinking | Calculation of Degree of Connection for statusnet-belfalas-org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-belfalas-org took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for statusnet-belfalas-org took 9.417533874511719e-05s
Believability | Calculation of trust value for statusnet-belfalas-org took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-belfalas-org took 2.854179620742798s
Availability | SPARQL endpoint availability check for statusnet-bka-li took 8.988380432128906e-05s
Availability | VoID file availability check for statusnet-bka-li took 0.0007185935974121094s
Completeness | Calculation of interlinking completeness for statusnet-bka-li took 0.3021512031555176s
Reputation | Calculation of the PageRank for statusnet-bka-li took 0.020882129669189453s
Interlinking | Calculation of Degree of Connection for statusnet-bka-li took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-bka-li took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for statusnet-bka-li took 0.00012922286987304688s
Believability | Calculation of trust value for statusnet-bka-li took 1.4066696166992188e-05s
INFO | --- Analysis for statusnet-bka-li took 12.881693363189697s
Availability | SPARQL endpoint availability check for statusnet-bonifaz-ec took 8.916854858398438e-05s
Availability | VoID file availability check for statusnet-bonifaz-ec took 0.0005819797515869141s
Completeness | Calculation of interlinking completeness for statusnet-bonifaz-ec took 0.2935829162597656s
Reputation | Calculation of the PageRank for statusnet-bonifaz-ec took 0.02213263511657715s
Interlinking | Calculation of Degree of Connection for statusnet-bonifaz-ec took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-bonifaz-ec took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for statusnet-bonifaz-ec took 4.267692565917969e-05s
Believability | Calculation of trust value for statusnet-bonifaz-ec took 1.52587890625e-05s
INFO | --- Analysis for statusnet-bonifaz-ec took 3.853532552719116s
Availability | SPARQL endpoint availability check for statusnet-ced117-net took 4.482269287109375e-05s
Availability | VoID file availability check for statusnet-ced117-net took 0.0006036758422851562s
Completeness | Calculation of interlinking completeness for statusnet-ced117-net took 0.2808957099914551s
Reputation | Calculation of the PageRank for statusnet-ced117-net took 0.0221707820892334s
Interlinking | Calculation of Degree of Connection for statusnet-ced117-net took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for statusnet-ced117-net took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for statusnet-ced117-net took 5.841255187988281e-05s
Believability | Calculation of trust value for statusnet-ced117-net took 1.4543533325195312e-05s
INFO | --- Analysis for statusnet-ced117-net took 4.682126760482788s
Availability | SPARQL endpoint availability check for statusnet-chickenkiller-com took 9.179115295410156e-05s
Availability | VoID file availability check for statusnet-chickenkiller-com took 0.0005745887756347656s
Completeness | Calculation of interlinking completeness for statusnet-chickenkiller-com took 0.3023240566253662s
Reputation | Calculation of the PageRank for statusnet-chickenkiller-com took 0.021595478057861328s
Interlinking | Calculation of Degree of Connection for statusnet-chickenkiller-com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-chickenkiller-com took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for statusnet-chickenkiller-com took 5.53131103515625e-05s
Believability | Calculation of trust value for statusnet-chickenkiller-com took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-chickenkiller-com took 2.7979347705841064s
Availability | SPARQL endpoint availability check for statusnet-chromic-org took 9.703636169433594e-05s
Availability | VoID file availability check for statusnet-chromic-org took 0.0005426406860351562s
Completeness | Calculation of interlinking completeness for statusnet-chromic-org took 0.3197808265686035s
Reputation | Calculation of the PageRank for statusnet-chromic-org took 0.02097916603088379s
Interlinking | Calculation of Degree of Connection for statusnet-chromic-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-chromic-org took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for statusnet-chromic-org took 0.00011706352233886719s
Believability | Calculation of trust value for statusnet-chromic-org took 1.430511474609375e-05s
INFO | --- Analysis for statusnet-chromic-org took 2.8485774993896484s
Availability | SPARQL endpoint availability check for statusnet-cooleysekula-net took 9.131431579589844e-05s
Availability | VoID file availability check for statusnet-cooleysekula-net took 0.0006802082061767578s
Completeness | Calculation of interlinking completeness for statusnet-cooleysekula-net took 0.2931995391845703s
Reputation | Calculation of the PageRank for statusnet-cooleysekula-net took 0.020941495895385742s
Interlinking | Calculation of Degree of Connection for statusnet-cooleysekula-net took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-cooleysekula-net took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for statusnet-cooleysekula-net took 8.58306884765625e-05s
Believability | Calculation of trust value for statusnet-cooleysekula-net took 1.430511474609375e-05s
INFO | --- Analysis for statusnet-cooleysekula-net took 6.354971170425415s
Availability | SPARQL endpoint availability check for statusnet-coreyavis-com took 8.797645568847656e-05s
Availability | VoID file availability check for statusnet-coreyavis-com took 0.0006384849548339844s
Completeness | Calculation of interlinking completeness for statusnet-coreyavis-com took 0.30964064598083496s
Reputation | Calculation of the PageRank for statusnet-coreyavis-com took 0.02239370346069336s
Interlinking | Calculation of Degree of Connection for statusnet-coreyavis-com took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-coreyavis-com took 0.0008118152618408203s
Interlinking | Calculation of Clustering coefficient for statusnet-coreyavis-com took 5.936622619628906e-05s
Believability | Calculation of trust value for statusnet-coreyavis-com took 1.4543533325195312e-05s
INFO | --- Analysis for statusnet-coreyavis-com took 2.764521598815918s
Availability | SPARQL endpoint availability check for statusnet-datenfahrt-org took 9.131431579589844e-05s
Availability | VoID file availability check for statusnet-datenfahrt-org took 0.000652313232421875s
Completeness | Calculation of interlinking completeness for statusnet-datenfahrt-org took 0.3289926052093506s
Reputation | Calculation of the PageRank for statusnet-datenfahrt-org took 0.021050453186035156s
Interlinking | Calculation of Degree of Connection for statusnet-datenfahrt-org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-datenfahrt-org took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for statusnet-datenfahrt-org took 7.104873657226562e-05s
Believability | Calculation of trust value for statusnet-datenfahrt-org took 1.4781951904296875e-05s
INFO | --- Analysis for statusnet-datenfahrt-org took 3.6114940643310547s
Availability | SPARQL endpoint availability check for statusnet-davidhaberthuer-ch took 9.202957153320312e-05s
Availability | VoID file availability check for statusnet-davidhaberthuer-ch took 0.0005481243133544922s
Completeness | Calculation of interlinking completeness for statusnet-davidhaberthuer-ch took 0.28784799575805664s
Reputation | Calculation of the PageRank for statusnet-davidhaberthuer-ch took 0.020532608032226562s
Interlinking | Calculation of Degree of Connection for statusnet-davidhaberthuer-ch took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-davidhaberthuer-ch took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for statusnet-davidhaberthuer-ch took 0.0001068115234375s
Believability | Calculation of trust value for statusnet-davidhaberthuer-ch took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-davidhaberthuer-ch took 2.7776854038238525s
Availability | SPARQL endpoint availability check for statusnet-deuxpi-ca took 8.96453857421875e-05s
Availability | VoID file availability check for statusnet-deuxpi-ca took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for statusnet-deuxpi-ca took 0.29471588134765625s
Reputation | Calculation of the PageRank for statusnet-deuxpi-ca took 0.020720243453979492s
Interlinking | Calculation of Degree of Connection for statusnet-deuxpi-ca took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-deuxpi-ca took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for statusnet-deuxpi-ca took 6.461143493652344e-05s
Believability | Calculation of trust value for statusnet-deuxpi-ca took 1.5497207641601562e-05s
INFO | --- Analysis for statusnet-deuxpi-ca took 2.699669122695923s
Availability | SPARQL endpoint availability check for statusnet-doomicile-de took 0.00010752677917480469s
Availability | VoID file availability check for statusnet-doomicile-de took 0.0007236003875732422s
Completeness | Calculation of interlinking completeness for statusnet-doomicile-de took 0.30582523345947266s
Reputation | Calculation of the PageRank for statusnet-doomicile-de took 0.02067089080810547s
Interlinking | Calculation of Degree of Connection for statusnet-doomicile-de took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-doomicile-de took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for statusnet-doomicile-de took 5.7220458984375e-05s
Believability | Calculation of trust value for statusnet-doomicile-de took 1.430511474609375e-05s
INFO | --- Analysis for statusnet-doomicile-de took 4.914652585983276s
Availability | SPARQL endpoint availability check for statusnet-dtdns-net took 0.00010466575622558594s
Availability | VoID file availability check for statusnet-dtdns-net took 0.0005731582641601562s
Completeness | Calculation of interlinking completeness for statusnet-dtdns-net took 0.33121347427368164s
Reputation | Calculation of the PageRank for statusnet-dtdns-net took 0.020804405212402344s
Interlinking | Calculation of Degree of Connection for statusnet-dtdns-net took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-dtdns-net took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for statusnet-dtdns-net took 6.413459777832031e-05s
Believability | Calculation of trust value for statusnet-dtdns-net took 1.5020370483398438e-05s
INFO | --- Analysis for statusnet-dtdns-net took 2.9252145290374756s
Availability | SPARQL endpoint availability check for statusnet-equestriarp-net took 9.393692016601562e-05s
Availability | VoID file availability check for statusnet-equestriarp-net took 0.0005106925964355469s
Completeness | Calculation of interlinking completeness for statusnet-equestriarp-net took 0.28713560104370117s
Reputation | Calculation of the PageRank for statusnet-equestriarp-net took 0.022298812866210938s
Interlinking | Calculation of Degree of Connection for statusnet-equestriarp-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-equestriarp-net took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for statusnet-equestriarp-net took 4.100799560546875e-05s
Believability | Calculation of trust value for statusnet-equestriarp-net took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-equestriarp-net took 2.7054600715637207s
Availability | SPARQL endpoint availability check for statusnet-exdc-net took 9.274482727050781e-05s
Availability | VoID file availability check for statusnet-exdc-net took 0.00057220458984375s
Completeness | Calculation of interlinking completeness for statusnet-exdc-net took 0.3392810821533203s
Reputation | Calculation of the PageRank for statusnet-exdc-net took 0.020549535751342773s
Interlinking | Calculation of Degree of Connection for statusnet-exdc-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-exdc-net took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for statusnet-exdc-net took 7.224082946777344e-05s
Believability | Calculation of trust value for statusnet-exdc-net took 1.4543533325195312e-05s
INFO | --- Analysis for statusnet-exdc-net took 2.901212692260742s
Availability | SPARQL endpoint availability check for statusnet-fcac-com took 9.202957153320312e-05s
Availability | VoID file availability check for statusnet-fcac-com took 0.0003609657287597656s
Completeness | Calculation of interlinking completeness for statusnet-fcac-com took 0.28668856620788574s
Reputation | Calculation of the PageRank for statusnet-fcac-com took 0.02101445198059082s
Interlinking | Calculation of Degree of Connection for statusnet-fcac-com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-fcac-com took 0.0007936954498291016s
Interlinking | Calculation of Clustering coefficient for statusnet-fcac-com took 9.679794311523438e-05s
Believability | Calculation of trust value for statusnet-fcac-com took 1.811981201171875e-05s
INFO | --- Analysis for statusnet-fcac-com took 3.174217700958252s
Availability | SPARQL endpoint availability check for statusnet-fcestrada-com took 9.393692016601562e-05s
Availability | VoID file availability check for statusnet-fcestrada-com took 0.0006797313690185547s
Completeness | Calculation of interlinking completeness for statusnet-fcestrada-com took 0.3185460567474365s
Reputation | Calculation of the PageRank for statusnet-fcestrada-com took 0.022066116333007812s
Interlinking | Calculation of Degree of Connection for statusnet-fcestrada-com took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for statusnet-fcestrada-com took 0.0007834434509277344s
Interlinking | Calculation of Clustering coefficient for statusnet-fcestrada-com took 6.699562072753906e-05s
Believability | Calculation of trust value for statusnet-fcestrada-com took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-fcestrada-com took 3.535407543182373s
Availability | SPARQL endpoint availability check for statusnet-fragdev-com took 4.887580871582031e-05s
Availability | VoID file availability check for statusnet-fragdev-com took 0.0006053447723388672s
Completeness | Calculation of interlinking completeness for statusnet-fragdev-com took 0.30999016761779785s
Reputation | Calculation of the PageRank for statusnet-fragdev-com took 0.020903348922729492s
Interlinking | Calculation of Degree of Connection for statusnet-fragdev-com took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-fragdev-com took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for statusnet-fragdev-com took 0.00018286705017089844s
Believability | Calculation of trust value for statusnet-fragdev-com took 1.3828277587890625e-05s
INFO | --- Analysis for statusnet-fragdev-com took 3.6455156803131104s
Availability | SPARQL endpoint availability check for statusnet-freelish-us took 9.202957153320312e-05s
Availability | VoID file availability check for statusnet-freelish-us took 0.0007002353668212891s
Completeness | Calculation of interlinking completeness for statusnet-freelish-us took 0.3034474849700928s
Reputation | Calculation of the PageRank for statusnet-freelish-us took 0.020923852920532227s
Interlinking | Calculation of Degree of Connection for statusnet-freelish-us took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-freelish-us took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for statusnet-freelish-us took 7.963180541992188e-05s
Believability | Calculation of trust value for statusnet-freelish-us took 1.5020370483398438e-05s
INFO | --- Analysis for statusnet-freelish-us took 3.1255388259887695s
Availability | SPARQL endpoint availability check for statusnet-gegeweb-org took 8.916854858398438e-05s
Availability | VoID file availability check for statusnet-gegeweb-org took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for statusnet-gegeweb-org took 0.291745662689209s
Reputation | Calculation of the PageRank for statusnet-gegeweb-org took 0.02211737632751465s
Interlinking | Calculation of Degree of Connection for statusnet-gegeweb-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-gegeweb-org took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for statusnet-gegeweb-org took 0.00011134147644042969s
Believability | Calculation of trust value for statusnet-gegeweb-org took 1.4543533325195312e-05s
INFO | --- Analysis for statusnet-gegeweb-org took 2.911384344100952s
Availability | SPARQL endpoint availability check for statusnet-glou-org took 8.869171142578125e-05s
Availability | VoID file availability check for statusnet-glou-org took 0.00044655799865722656s
Completeness | Calculation of interlinking completeness for statusnet-glou-org took 0.28862547874450684s
Reputation | Calculation of the PageRank for statusnet-glou-org took 0.021051645278930664s
Interlinking | Calculation of Degree of Connection for statusnet-glou-org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-glou-org took 0.0008051395416259766s
Interlinking | Calculation of Clustering coefficient for statusnet-glou-org took 7.343292236328125e-05s
Believability | Calculation of trust value for statusnet-glou-org took 1.430511474609375e-05s
INFO | --- Analysis for statusnet-glou-org took 2.9194161891937256s
Availability | SPARQL endpoint availability check for statusnet-gomertronic-com took 4.76837158203125e-05s
Availability | VoID file availability check for statusnet-gomertronic-com took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for statusnet-gomertronic-com took 0.27365612983703613s
Reputation | Calculation of the PageRank for statusnet-gomertronic-com took 0.020914554595947266s
Interlinking | Calculation of Degree of Connection for statusnet-gomertronic-com took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for statusnet-gomertronic-com took 0.0008695125579833984s
Interlinking | Calculation of Clustering coefficient for statusnet-gomertronic-com took 0.0001430511474609375s
Believability | Calculation of trust value for statusnet-gomertronic-com took 1.5020370483398438e-05s
INFO | --- Analysis for statusnet-gomertronic-com took 2.6599948406219482s
Availability | SPARQL endpoint availability check for statusnet-hackerposse-com took 9.608268737792969e-05s
Availability | VoID file availability check for statusnet-hackerposse-com took 0.0004279613494873047s
Completeness | Calculation of interlinking completeness for statusnet-hackerposse-com took 0.2671949863433838s
Reputation | Calculation of the PageRank for statusnet-hackerposse-com took 0.020761728286743164s
Interlinking | Calculation of Degree of Connection for statusnet-hackerposse-com took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for statusnet-hackerposse-com took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for statusnet-hackerposse-com took 0.00011110305786132812s
Believability | Calculation of trust value for statusnet-hackerposse-com took 1.3828277587890625e-05s
INFO | --- Analysis for statusnet-hackerposse-com took 3.171553611755371s
Availability | SPARQL endpoint availability check for statusnet-hii-co-il took 9.012222290039062e-05s
Availability | VoID file availability check for statusnet-hii-co-il took 0.00037550926208496094s
Completeness | Calculation of interlinking completeness for statusnet-hii-co-il took 0.2776799201965332s
Reputation | Calculation of the PageRank for statusnet-hii-co-il took 0.021088600158691406s
Interlinking | Calculation of Degree of Connection for statusnet-hii-co-il took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-hii-co-il took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for statusnet-hii-co-il took 5.3882598876953125e-05s
Believability | Calculation of trust value for statusnet-hii-co-il took 1.5020370483398438e-05s
INFO | --- Analysis for statusnet-hii-co-il took 3.8424060344696045s
Availability | SPARQL endpoint availability check for statusnet-ilikefreedom-ro took 4.6253204345703125e-05s
Availability | VoID file availability check for statusnet-ilikefreedom-ro took 0.0006401538848876953s
Completeness | Calculation of interlinking completeness for statusnet-ilikefreedom-ro took 0.3178367614746094s
Reputation | Calculation of the PageRank for statusnet-ilikefreedom-ro took 0.02144932746887207s
Interlinking | Calculation of Degree of Connection for statusnet-ilikefreedom-ro took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-ilikefreedom-ro took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for statusnet-ilikefreedom-ro took 9.918212890625e-05s
Believability | Calculation of trust value for statusnet-ilikefreedom-ro took 1.430511474609375e-05s
INFO | --- Analysis for statusnet-ilikefreedom-ro took 3.0597267150878906s
Availability | SPARQL endpoint availability check for statusnet-imirhil-fr took 9.059906005859375e-05s
Availability | VoID file availability check for statusnet-imirhil-fr took 0.0005240440368652344s
Completeness | Calculation of interlinking completeness for statusnet-imirhil-fr took 0.2778904438018799s
Reputation | Calculation of the PageRank for statusnet-imirhil-fr took 0.020725011825561523s
Interlinking | Calculation of Degree of Connection for statusnet-imirhil-fr took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-imirhil-fr took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for statusnet-imirhil-fr took 6.556510925292969e-05s
Believability | Calculation of trust value for statusnet-imirhil-fr took 1.3828277587890625e-05s
INFO | --- Analysis for statusnet-imirhil-fr took 2.736530303955078s
Availability | SPARQL endpoint availability check for statusnet-integralblue-com took 5.316734313964844e-05s
Availability | VoID file availability check for statusnet-integralblue-com took 0.0006527900695800781s
Completeness | Calculation of interlinking completeness for statusnet-integralblue-com took 0.2893524169921875s
Reputation | Calculation of the PageRank for statusnet-integralblue-com took 0.02200913429260254s
Interlinking | Calculation of Degree of Connection for statusnet-integralblue-com took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-integralblue-com took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for statusnet-integralblue-com took 4.458427429199219e-05s
Believability | Calculation of trust value for statusnet-integralblue-com took 1.5020370483398438e-05s
INFO | --- Analysis for statusnet-integralblue-com took 2.9167919158935547s
Availability | SPARQL endpoint availability check for statusnet-johndrinkwater-name took 9.34600830078125e-05s
Availability | VoID file availability check for statusnet-johndrinkwater-name took 0.0007989406585693359s
Completeness | Calculation of interlinking completeness for statusnet-johndrinkwater-name took 0.2684652805328369s
Reputation | Calculation of the PageRank for statusnet-johndrinkwater-name took 0.020998001098632812s
Interlinking | Calculation of Degree of Connection for statusnet-johndrinkwater-name took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-johndrinkwater-name took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for statusnet-johndrinkwater-name took 6.771087646484375e-05s
Believability | Calculation of trust value for statusnet-johndrinkwater-name took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-johndrinkwater-name took 22.721374034881592s
Availability | SPARQL endpoint availability check for statusnet-jonkman-ca took 5.030632019042969e-05s
Availability | VoID file availability check for statusnet-jonkman-ca took 0.0005366802215576172s
Completeness | Calculation of interlinking completeness for statusnet-jonkman-ca took 0.26961636543273926s
Reputation | Calculation of the PageRank for statusnet-jonkman-ca took 0.02092719078063965s
Interlinking | Calculation of Degree of Connection for statusnet-jonkman-ca took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-jonkman-ca took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for statusnet-jonkman-ca took 0.0001163482666015625s
Believability | Calculation of trust value for statusnet-jonkman-ca took 1.4543533325195312e-05s
INFO | --- Analysis for statusnet-jonkman-ca took 5.0212461948394775s
Availability | SPARQL endpoint availability check for statusnet-kaimi-cc took 8.940696716308594e-05s
Availability | VoID file availability check for statusnet-kaimi-cc took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for statusnet-kaimi-cc took 0.28272461891174316s
Reputation | Calculation of the PageRank for statusnet-kaimi-cc took 0.022236108779907227s
Interlinking | Calculation of Degree of Connection for statusnet-kaimi-cc took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-kaimi-cc took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for statusnet-kaimi-cc took 0.00010204315185546875s
Believability | Calculation of trust value for statusnet-kaimi-cc took 1.4543533325195312e-05s
INFO | --- Analysis for statusnet-kaimi-cc took 2.7961175441741943s
Availability | SPARQL endpoint availability check for statusnet-kathryl-fr took 9.012222290039062e-05s
Availability | VoID file availability check for statusnet-kathryl-fr took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for statusnet-kathryl-fr took 0.28967881202697754s
Reputation | Calculation of the PageRank for statusnet-kathryl-fr took 0.020850181579589844s
Interlinking | Calculation of Degree of Connection for statusnet-kathryl-fr took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-kathryl-fr took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for statusnet-kathryl-fr took 5.7220458984375e-05s
Believability | Calculation of trust value for statusnet-kathryl-fr took 1.4066696166992188e-05s
INFO | --- Analysis for statusnet-kathryl-fr took 2.717942953109741s
Availability | SPARQL endpoint availability check for statusnet-kenzoid-com took 5.984306335449219e-05s
Availability | VoID file availability check for statusnet-kenzoid-com took 0.0005578994750976562s
Completeness | Calculation of interlinking completeness for statusnet-kenzoid-com took 0.318955659866333s
Reputation | Calculation of the PageRank for statusnet-kenzoid-com took 0.021205663681030273s
Interlinking | Calculation of Degree of Connection for statusnet-kenzoid-com took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-kenzoid-com took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for statusnet-kenzoid-com took 4.601478576660156e-05s
Believability | Calculation of trust value for statusnet-kenzoid-com took 1.4066696166992188e-05s
INFO | --- Analysis for statusnet-kenzoid-com took 3.632561683654785s
Availability | SPARQL endpoint availability check for statusnet-keuser-fr took 0.00010800361633300781s
Availability | VoID file availability check for statusnet-keuser-fr took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for statusnet-keuser-fr took 0.3018605709075928s
Reputation | Calculation of the PageRank for statusnet-keuser-fr took 0.021087646484375s
Interlinking | Calculation of Degree of Connection for statusnet-keuser-fr took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-keuser-fr took 0.0007827281951904297s
Interlinking | Calculation of Clustering coefficient for statusnet-keuser-fr took 8.487701416015625e-05s
Believability | Calculation of trust value for statusnet-keuser-fr took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-keuser-fr took 2.727095603942871s
Availability | SPARQL endpoint availability check for statusnet-ldn-fai-net took 8.749961853027344e-05s
Availability | VoID file availability check for statusnet-ldn-fai-net took 0.0005795955657958984s
Completeness | Calculation of interlinking completeness for statusnet-ldn-fai-net took 0.2776455879211426s
Reputation | Calculation of the PageRank for statusnet-ldn-fai-net took 0.021144628524780273s
Interlinking | Calculation of Degree of Connection for statusnet-ldn-fai-net took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-ldn-fai-net took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for statusnet-ldn-fai-net took 5.0067901611328125e-05s
Believability | Calculation of trust value for statusnet-ldn-fai-net took 1.4781951904296875e-05s
INFO | --- Analysis for statusnet-ldn-fai-net took 2.79529070854187s
Availability | SPARQL endpoint availability check for statusnet-lebsanft-org took 9.608268737792969e-05s
Availability | VoID file availability check for statusnet-lebsanft-org took 0.0005929470062255859s
Completeness | Calculation of interlinking completeness for statusnet-lebsanft-org took 0.3185606002807617s
Reputation | Calculation of the PageRank for statusnet-lebsanft-org took 0.02100372314453125s
Interlinking | Calculation of Degree of Connection for statusnet-lebsanft-org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-lebsanft-org took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for statusnet-lebsanft-org took 6.365776062011719e-05s
Believability | Calculation of trust value for statusnet-lebsanft-org took 1.4066696166992188e-05s
INFO | --- Analysis for statusnet-lebsanft-org took 3.099587917327881s
Availability | SPARQL endpoint availability check for statusnet-legadolibre-com-ar took 8.821487426757812e-05s
Availability | VoID file availability check for statusnet-legadolibre-com-ar took 0.0006973743438720703s
Completeness | Calculation of interlinking completeness for statusnet-legadolibre-com-ar took 0.2887856960296631s
Reputation | Calculation of the PageRank for statusnet-legadolibre-com-ar took 0.020510435104370117s
Interlinking | Calculation of Degree of Connection for statusnet-legadolibre-com-ar took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-legadolibre-com-ar took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for statusnet-legadolibre-com-ar took 9.608268737792969e-05s
Believability | Calculation of trust value for statusnet-legadolibre-com-ar took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-legadolibre-com-ar took 3.4844584465026855s
Availability | SPARQL endpoint availability check for statusnet-linuxwrangling-com took 8.940696716308594e-05s
Availability | VoID file availability check for statusnet-linuxwrangling-com took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for statusnet-linuxwrangling-com took 0.33171629905700684s
Reputation | Calculation of the PageRank for statusnet-linuxwrangling-com took 0.021307945251464844s
Interlinking | Calculation of Degree of Connection for statusnet-linuxwrangling-com took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-linuxwrangling-com took 0.0008029937744140625s
Interlinking | Calculation of Clustering coefficient for statusnet-linuxwrangling-com took 0.00012421607971191406s
Believability | Calculation of trust value for statusnet-linuxwrangling-com took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-linuxwrangling-com took 2.6672773361206055s
Availability | SPARQL endpoint availability check for statusnet-ludost-net took 4.482269287109375e-05s
Availability | VoID file availability check for statusnet-ludost-net took 0.0007429122924804688s
Completeness | Calculation of interlinking completeness for statusnet-ludost-net took 0.3309907913208008s
Reputation | Calculation of the PageRank for statusnet-ludost-net took 0.02068161964416504s
Interlinking | Calculation of Degree of Connection for statusnet-ludost-net took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-ludost-net took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for statusnet-ludost-net took 6.103515625e-05s
Believability | Calculation of trust value for statusnet-ludost-net took 1.3828277587890625e-05s
INFO | --- Analysis for statusnet-ludost-net took 4.142568588256836s
Availability | SPARQL endpoint availability check for statusnet-lydiastench-com took 0.0001461505889892578s
Availability | VoID file availability check for statusnet-lydiastench-com took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for statusnet-lydiastench-com took 0.31024622917175293s
Reputation | Calculation of the PageRank for statusnet-lydiastench-com took 0.022182226181030273s
Interlinking | Calculation of Degree of Connection for statusnet-lydiastench-com took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-lydiastench-com took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for statusnet-lydiastench-com took 0.000102996826171875s
Believability | Calculation of trust value for statusnet-lydiastench-com took 1.4066696166992188e-05s
INFO | --- Analysis for statusnet-lydiastench-com took 2.7940495014190674s
Availability | SPARQL endpoint availability check for statusnet-m-kuttner-com took 6.699562072753906e-05s
Availability | VoID file availability check for statusnet-m-kuttner-com took 0.0006163120269775391s
Completeness | Calculation of interlinking completeness for statusnet-m-kuttner-com took 0.27968406677246094s
Reputation | Calculation of the PageRank for statusnet-m-kuttner-com took 0.020823240280151367s
Interlinking | Calculation of Degree of Connection for statusnet-m-kuttner-com took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-m-kuttner-com took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for statusnet-m-kuttner-com took 5.7697296142578125e-05s
Believability | Calculation of trust value for statusnet-m-kuttner-com took 1.621246337890625e-05s
INFO | --- Analysis for statusnet-m-kuttner-com took 3.6677160263061523s
Availability | SPARQL endpoint availability check for statusnet-macno-org took 4.506111145019531e-05s
Availability | VoID file availability check for statusnet-macno-org took 0.0002970695495605469s
Completeness | Calculation of interlinking completeness for statusnet-macno-org took 0.28536462783813477s
Reputation | Calculation of the PageRank for statusnet-macno-org took 0.02137136459350586s
Interlinking | Calculation of Degree of Connection for statusnet-macno-org took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-macno-org took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for statusnet-macno-org took 0.00015687942504882812s
Believability | Calculation of trust value for statusnet-macno-org took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-macno-org took 2.7768588066101074s
Availability | SPARQL endpoint availability check for statusnet-mamalibre-com-ar took 6.4849853515625e-05s
Availability | VoID file availability check for statusnet-mamalibre-com-ar took 0.0005674362182617188s
Completeness | Calculation of interlinking completeness for statusnet-mamalibre-com-ar took 0.30065345764160156s
Reputation | Calculation of the PageRank for statusnet-mamalibre-com-ar took 0.02086925506591797s
Interlinking | Calculation of Degree of Connection for statusnet-mamalibre-com-ar took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-mamalibre-com-ar took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for statusnet-mamalibre-com-ar took 8.082389831542969e-05s
Believability | Calculation of trust value for statusnet-mamalibre-com-ar took 1.430511474609375e-05s
INFO | --- Analysis for statusnet-mamalibre-com-ar took 2.6712894439697266s
Availability | SPARQL endpoint availability check for statusnet-maymay-net took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-maymay-net took 0.0007197856903076172s
Completeness | Calculation of interlinking completeness for statusnet-maymay-net took 0.29283928871154785s
Reputation | Calculation of the PageRank for statusnet-maymay-net took 0.02142167091369629s
Interlinking | Calculation of Degree of Connection for statusnet-maymay-net took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for statusnet-maymay-net took 0.0008597373962402344s
Interlinking | Calculation of Clustering coefficient for statusnet-maymay-net took 9.250640869140625e-05s
Believability | Calculation of trust value for statusnet-maymay-net took 1.4781951904296875e-05s
INFO | --- Analysis for statusnet-maymay-net took 42.62812900543213s
Availability | SPARQL endpoint availability check for statusnet-morphtown-de took 6.985664367675781e-05s
Availability | VoID file availability check for statusnet-morphtown-de took 0.0006000995635986328s
Completeness | Calculation of interlinking completeness for statusnet-morphtown-de took 0.3176112174987793s
Reputation | Calculation of the PageRank for statusnet-morphtown-de took 0.02132129669189453s
Interlinking | Calculation of Degree of Connection for statusnet-morphtown-de took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-morphtown-de took 0.00084686279296875s
Interlinking | Calculation of Clustering coefficient for statusnet-morphtown-de took 0.000171661376953125s
Believability | Calculation of trust value for statusnet-morphtown-de took 1.5974044799804688e-05s
INFO | --- Analysis for statusnet-morphtown-de took 2.8093504905700684s
Availability | SPARQL endpoint availability check for statusnet-mrblog-nl took 4.863739013671875e-05s
Availability | VoID file availability check for statusnet-mrblog-nl took 0.0005402565002441406s
Completeness | Calculation of interlinking completeness for statusnet-mrblog-nl took 0.3187110424041748s
Reputation | Calculation of the PageRank for statusnet-mrblog-nl took 0.022264719009399414s
Interlinking | Calculation of Degree of Connection for statusnet-mrblog-nl took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-mrblog-nl took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for statusnet-mrblog-nl took 0.00010704994201660156s
Believability | Calculation of trust value for statusnet-mrblog-nl took 1.4781951904296875e-05s
INFO | --- Analysis for statusnet-mrblog-nl took 2.8411364555358887s
Availability | SPARQL endpoint availability check for statusnet-mulestable-net took 9.179115295410156e-05s
Availability | VoID file availability check for statusnet-mulestable-net took 0.0005338191986083984s
Completeness | Calculation of interlinking completeness for statusnet-mulestable-net took 0.31538915634155273s
Reputation | Calculation of the PageRank for statusnet-mulestable-net took 0.02078986167907715s
Interlinking | Calculation of Degree of Connection for statusnet-mulestable-net took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-mulestable-net took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for statusnet-mulestable-net took 5.91278076171875e-05s
Believability | Calculation of trust value for statusnet-mulestable-net took 1.5497207641601562e-05s
INFO | --- Analysis for statusnet-mulestable-net took 2.764840841293335s
Availability | SPARQL endpoint availability check for statusnet-my-status-tk took 0.00013184547424316406s
Availability | VoID file availability check for statusnet-my-status-tk took 0.0005748271942138672s
Completeness | Calculation of interlinking completeness for statusnet-my-status-tk took 0.32723140716552734s
Reputation | Calculation of the PageRank for statusnet-my-status-tk took 0.021067380905151367s
Interlinking | Calculation of Degree of Connection for statusnet-my-status-tk took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-my-status-tk took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for statusnet-my-status-tk took 5.91278076171875e-05s
Believability | Calculation of trust value for statusnet-my-status-tk took 1.4781951904296875e-05s
INFO | --- Analysis for statusnet-my-status-tk took 2.9052226543426514s
Availability | SPARQL endpoint availability check for statusnet-opensim-chat-eu took 8.797645568847656e-05s
Availability | VoID file availability check for statusnet-opensim-chat-eu took 0.0007798671722412109s
Completeness | Calculation of interlinking completeness for statusnet-opensim-chat-eu took 0.3126492500305176s
Reputation | Calculation of the PageRank for statusnet-opensim-chat-eu took 0.02126336097717285s
Interlinking | Calculation of Degree of Connection for statusnet-opensim-chat-eu took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-opensim-chat-eu took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for statusnet-opensim-chat-eu took 0.000118255615234375s
Believability | Calculation of trust value for statusnet-opensim-chat-eu took 1.5020370483398438e-05s
INFO | --- Analysis for statusnet-opensim-chat-eu took 2.8154492378234863s
Availability | SPARQL endpoint availability check for statusnet-orangeseeds-org took 9.012222290039062e-05s
Availability | VoID file availability check for statusnet-orangeseeds-org took 0.0006275177001953125s
Completeness | Calculation of interlinking completeness for statusnet-orangeseeds-org took 0.3002176284790039s
Reputation | Calculation of the PageRank for statusnet-orangeseeds-org took 0.021480083465576172s
Interlinking | Calculation of Degree of Connection for statusnet-orangeseeds-org took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for statusnet-orangeseeds-org took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for statusnet-orangeseeds-org took 6.508827209472656e-05s
Believability | Calculation of trust value for statusnet-orangeseeds-org took 1.4781951904296875e-05s
INFO | --- Analysis for statusnet-orangeseeds-org took 2.874586343765259s
Availability | SPARQL endpoint availability check for statusnet-otbm-fr took 4.57763671875e-05s
Availability | VoID file availability check for statusnet-otbm-fr took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for statusnet-otbm-fr took 0.31255030632019043s
Reputation | Calculation of the PageRank for statusnet-otbm-fr took 0.022565603256225586s
Interlinking | Calculation of Degree of Connection for statusnet-otbm-fr took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for statusnet-otbm-fr took 0.0010046958923339844s
Interlinking | Calculation of Clustering coefficient for statusnet-otbm-fr took 8.392333984375e-05s
Believability | Calculation of trust value for statusnet-otbm-fr took 1.52587890625e-05s
INFO | --- Analysis for statusnet-otbm-fr took 2.7303309440612793s
Availability | SPARQL endpoint availability check for statusnet-ourcoffs-org-au took 0.0001952648162841797s
Availability | VoID file availability check for statusnet-ourcoffs-org-au took 0.0005362033843994141s
Completeness | Calculation of interlinking completeness for statusnet-ourcoffs-org-au took 0.311368465423584s
Reputation | Calculation of the PageRank for statusnet-ourcoffs-org-au took 0.02107095718383789s
Interlinking | Calculation of Degree of Connection for statusnet-ourcoffs-org-au took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-ourcoffs-org-au took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for statusnet-ourcoffs-org-au took 9.250640869140625e-05s
Believability | Calculation of trust value for statusnet-ourcoffs-org-au took 1.52587890625e-05s
INFO | --- Analysis for statusnet-ourcoffs-org-au took 2.7957770824432373s
Availability | SPARQL endpoint availability check for statusnet-panda-id-au took 8.940696716308594e-05s
Availability | VoID file availability check for statusnet-panda-id-au took 0.0006699562072753906s
Completeness | Calculation of interlinking completeness for statusnet-panda-id-au took 0.28933024406433105s
Reputation | Calculation of the PageRank for statusnet-panda-id-au took 0.020591020584106445s
Interlinking | Calculation of Degree of Connection for statusnet-panda-id-au took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-panda-id-au took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for statusnet-panda-id-au took 5.054473876953125e-05s
Believability | Calculation of trust value for statusnet-panda-id-au took 1.430511474609375e-05s
INFO | --- Analysis for statusnet-panda-id-au took 3.332078695297241s
Availability | SPARQL endpoint availability check for statusnet-piana-eu took 9.369850158691406e-05s
Availability | VoID file availability check for statusnet-piana-eu took 0.000598907470703125s
Completeness | Calculation of interlinking completeness for statusnet-piana-eu took 0.3183705806732178s
Reputation | Calculation of the PageRank for statusnet-piana-eu took 0.0219724178314209s
Interlinking | Calculation of Degree of Connection for statusnet-piana-eu took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-piana-eu took 0.0007908344268798828s
Interlinking | Calculation of Clustering coefficient for statusnet-piana-eu took 0.000102996826171875s
Believability | Calculation of trust value for statusnet-piana-eu took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-piana-eu took 2.794402599334717s
Availability | SPARQL endpoint availability check for statusnet-planet-libre-org took 9.202957153320312e-05s
Availability | VoID file availability check for statusnet-planet-libre-org took 0.0008032321929931641s
Completeness | Calculation of interlinking completeness for statusnet-planet-libre-org took 0.3040163516998291s
Reputation | Calculation of the PageRank for statusnet-planet-libre-org took 0.020559072494506836s
Interlinking | Calculation of Degree of Connection for statusnet-planet-libre-org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-planet-libre-org took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for statusnet-planet-libre-org took 8.20159912109375e-05s
Believability | Calculation of trust value for statusnet-planet-libre-org took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-planet-libre-org took 2.8457021713256836s
Availability | SPARQL endpoint availability check for statusnet-postblue-info took 9.202957153320312e-05s
Availability | VoID file availability check for statusnet-postblue-info took 0.0004923343658447266s
Completeness | Calculation of interlinking completeness for statusnet-postblue-info took 0.2908511161804199s
Reputation | Calculation of the PageRank for statusnet-postblue-info took 0.022693634033203125s
Interlinking | Calculation of Degree of Connection for statusnet-postblue-info took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-postblue-info took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for statusnet-postblue-info took 0.0002334117889404297s
Believability | Calculation of trust value for statusnet-postblue-info took 1.4543533325195312e-05s
INFO | --- Analysis for statusnet-postblue-info took 2.9793083667755127s
Availability | SPARQL endpoint availability check for statusnet-progval-net took 9.059906005859375e-05s
Availability | VoID file availability check for statusnet-progval-net took 0.0005700588226318359s
Completeness | Calculation of interlinking completeness for statusnet-progval-net took 0.29117822647094727s
Reputation | Calculation of the PageRank for statusnet-progval-net took 0.021825313568115234s
Interlinking | Calculation of Degree of Connection for statusnet-progval-net took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-progval-net took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for statusnet-progval-net took 7.271766662597656e-05s
Believability | Calculation of trust value for statusnet-progval-net took 1.4066696166992188e-05s
INFO | --- Analysis for statusnet-progval-net took 2.906449317932129s
Availability | SPARQL endpoint availability check for statusnet-qdnx-org took 8.940696716308594e-05s
Availability | VoID file availability check for statusnet-qdnx-org took 0.0006682872772216797s
Completeness | Calculation of interlinking completeness for statusnet-qdnx-org took 0.3040285110473633s
Reputation | Calculation of the PageRank for statusnet-qdnx-org took 0.021017789840698242s
Interlinking | Calculation of Degree of Connection for statusnet-qdnx-org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-qdnx-org took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for statusnet-qdnx-org took 0.00012111663818359375s
Believability | Calculation of trust value for statusnet-qdnx-org took 1.5735626220703125e-05s
INFO | --- Analysis for statusnet-qdnx-org took 3.2289657592773438s
Availability | SPARQL endpoint availability check for statusnet-qth-fr took 0.00010561943054199219s
Availability | VoID file availability check for statusnet-qth-fr took 0.0006585121154785156s
Completeness | Calculation of interlinking completeness for statusnet-qth-fr took 0.33685922622680664s
Reputation | Calculation of the PageRank for statusnet-qth-fr took 0.02141118049621582s
Interlinking | Calculation of Degree of Connection for statusnet-qth-fr took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for statusnet-qth-fr took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for statusnet-qth-fr took 7.128715515136719e-05s
Believability | Calculation of trust value for statusnet-qth-fr took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-qth-fr took 5.9497034549713135s
Availability | SPARQL endpoint availability check for statusnet-quitter-se took 9.608268737792969e-05s
Availability | VoID file availability check for statusnet-quitter-se took 0.0007269382476806641s
Completeness | Calculation of interlinking completeness for statusnet-quitter-se took 0.32128429412841797s
Reputation | Calculation of the PageRank for statusnet-quitter-se took 0.021955251693725586s
Interlinking | Calculation of Degree of Connection for statusnet-quitter-se took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-quitter-se took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for statusnet-quitter-se took 0.0002231597900390625s
Believability | Calculation of trust value for statusnet-quitter-se took 1.5020370483398438e-05s
INFO | --- Analysis for statusnet-quitter-se took 5.991786479949951s
Availability | SPARQL endpoint availability check for statusnet-rainbowdash-net took 9.393692016601562e-05s
Availability | VoID file availability check for statusnet-rainbowdash-net took 0.000576019287109375s
Completeness | Calculation of interlinking completeness for statusnet-rainbowdash-net took 0.2898135185241699s
Reputation | Calculation of the PageRank for statusnet-rainbowdash-net took 0.020823955535888672s
Interlinking | Calculation of Degree of Connection for statusnet-rainbowdash-net took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-rainbowdash-net took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for statusnet-rainbowdash-net took 0.00010848045349121094s
Believability | Calculation of trust value for statusnet-rainbowdash-net took 1.5735626220703125e-05s
INFO | --- Analysis for statusnet-rainbowdash-net took 2.9746551513671875s
Availability | SPARQL endpoint availability check for statusnet-recit-org took 4.5299530029296875e-05s
Availability | VoID file availability check for statusnet-recit-org took 0.0007376670837402344s
Completeness | Calculation of interlinking completeness for statusnet-recit-org took 0.29756784439086914s
Reputation | Calculation of the PageRank for statusnet-recit-org took 0.021241188049316406s
Interlinking | Calculation of Degree of Connection for statusnet-recit-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-recit-org took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for statusnet-recit-org took 6.151199340820312e-05s
Believability | Calculation of trust value for statusnet-recit-org took 1.3828277587890625e-05s
INFO | --- Analysis for statusnet-recit-org took 13.13314414024353s
Availability | SPARQL endpoint availability check for statusnet-russwurm-org took 4.57763671875e-05s
Availability | VoID file availability check for statusnet-russwurm-org took 0.0005428791046142578s
Completeness | Calculation of interlinking completeness for statusnet-russwurm-org took 0.32987213134765625s
Reputation | Calculation of the PageRank for statusnet-russwurm-org took 0.02141857147216797s
Interlinking | Calculation of Degree of Connection for statusnet-russwurm-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-russwurm-org took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for statusnet-russwurm-org took 0.0001652240753173828s
Believability | Calculation of trust value for statusnet-russwurm-org took 1.4543533325195312e-05s
INFO | --- Analysis for statusnet-russwurm-org took 3.5962069034576416s
Availability | SPARQL endpoint availability check for statusnet-samnoble-org took 4.482269287109375e-05s
Availability | VoID file availability check for statusnet-samnoble-org took 0.0006475448608398438s
Completeness | Calculation of interlinking completeness for statusnet-samnoble-org took 0.28399181365966797s
Reputation | Calculation of the PageRank for statusnet-samnoble-org took 0.020719289779663086s
Interlinking | Calculation of Degree of Connection for statusnet-samnoble-org took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-samnoble-org took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for statusnet-samnoble-org took 9.131431579589844e-05s
Believability | Calculation of trust value for statusnet-samnoble-org took 1.3589859008789062e-05s
INFO | --- Analysis for statusnet-samnoble-org took 5.1130430698394775s
Availability | SPARQL endpoint availability check for statusnet-schiessle-org took 0.00011491775512695312s
Availability | VoID file availability check for statusnet-schiessle-org took 0.0005469322204589844s
Completeness | Calculation of interlinking completeness for statusnet-schiessle-org took 0.27608156204223633s
Reputation | Calculation of the PageRank for statusnet-schiessle-org took 0.020836591720581055s
Interlinking | Calculation of Degree of Connection for statusnet-schiessle-org took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-schiessle-org took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for statusnet-schiessle-org took 8.893013000488281e-05s
Believability | Calculation of trust value for statusnet-schiessle-org took 1.430511474609375e-05s
INFO | --- Analysis for statusnet-schiessle-org took 2.7563271522521973s
Availability | SPARQL endpoint availability check for statusnet-scoffoni-net took 0.00011706352233886719s
Availability | VoID file availability check for statusnet-scoffoni-net took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for statusnet-scoffoni-net took 0.3007063865661621s
Reputation | Calculation of the PageRank for statusnet-scoffoni-net took 0.02203369140625s
Interlinking | Calculation of Degree of Connection for statusnet-scoffoni-net took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for statusnet-scoffoni-net took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for statusnet-scoffoni-net took 0.0001049041748046875s
Believability | Calculation of trust value for statusnet-scoffoni-net took 1.3589859008789062e-05s
INFO | --- Analysis for statusnet-scoffoni-net took 2.7030200958251953s
Availability | SPARQL endpoint availability check for statusnet-sebseb01-net took 9.226799011230469e-05s
Availability | VoID file availability check for statusnet-sebseb01-net took 0.0006299018859863281s
Completeness | Calculation of interlinking completeness for statusnet-sebseb01-net took 0.2984166145324707s
Reputation | Calculation of the PageRank for statusnet-sebseb01-net took 0.020718812942504883s
Interlinking | Calculation of Degree of Connection for statusnet-sebseb01-net took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-sebseb01-net took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for statusnet-sebseb01-net took 6.794929504394531e-05s
Believability | Calculation of trust value for statusnet-sebseb01-net took 1.3828277587890625e-05s
INFO | --- Analysis for statusnet-sebseb01-net took 2.718440055847168s
Availability | SPARQL endpoint availability check for statusnet-shnoulle-net took 4.6253204345703125e-05s
Availability | VoID file availability check for statusnet-shnoulle-net took 0.0005769729614257812s
Completeness | Calculation of interlinking completeness for statusnet-shnoulle-net took 0.3155515193939209s
Reputation | Calculation of the PageRank for statusnet-shnoulle-net took 0.02227783203125s
Interlinking | Calculation of Degree of Connection for statusnet-shnoulle-net took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-shnoulle-net took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for statusnet-shnoulle-net took 7.939338684082031e-05s
Believability | Calculation of trust value for statusnet-shnoulle-net took 1.4543533325195312e-05s
INFO | --- Analysis for statusnet-shnoulle-net took 8.401431798934937s
Availability | SPARQL endpoint availability check for statusnet-skilledtests-com took 9.036064147949219e-05s
Availability | VoID file availability check for statusnet-skilledtests-com took 0.0006966590881347656s
Completeness | Calculation of interlinking completeness for statusnet-skilledtests-com took 0.3046550750732422s
Reputation | Calculation of the PageRank for statusnet-skilledtests-com took 0.021116971969604492s
Interlinking | Calculation of Degree of Connection for statusnet-skilledtests-com took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-skilledtests-com took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for statusnet-skilledtests-com took 0.00022101402282714844s
Believability | Calculation of trust value for statusnet-skilledtests-com took 1.4781951904296875e-05s
INFO | --- Analysis for statusnet-skilledtests-com took 3.3239595890045166s
Availability | SPARQL endpoint availability check for statusnet-somsants-net took 8.797645568847656e-05s
Availability | VoID file availability check for statusnet-somsants-net took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for statusnet-somsants-net took 0.3291664123535156s
Reputation | Calculation of the PageRank for statusnet-somsants-net took 0.021674394607543945s
Interlinking | Calculation of Degree of Connection for statusnet-somsants-net took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for statusnet-somsants-net took 0.000782012939453125s
Interlinking | Calculation of Clustering coefficient for statusnet-somsants-net took 0.00011396408081054688s
Believability | Calculation of trust value for statusnet-somsants-net took 1.621246337890625e-05s
INFO | --- Analysis for statusnet-somsants-net took 2.793874502182007s
Availability | SPARQL endpoint availability check for statusnet-soucy-cc took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-soucy-cc took 0.0005915164947509766s
Completeness | Calculation of interlinking completeness for statusnet-soucy-cc took 0.2770507335662842s
Reputation | Calculation of the PageRank for statusnet-soucy-cc took 0.02074265480041504s
Interlinking | Calculation of Degree of Connection for statusnet-soucy-cc took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-soucy-cc took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for statusnet-soucy-cc took 0.00014519691467285156s
Believability | Calculation of trust value for statusnet-soucy-cc took 1.3589859008789062e-05s
INFO | --- Analysis for statusnet-soucy-cc took 4.386564016342163s
Availability | SPARQL endpoint availability check for statusnet-spip-org took 9.179115295410156e-05s
Availability | VoID file availability check for statusnet-spip-org took 0.0006108283996582031s
Completeness | Calculation of interlinking completeness for statusnet-spip-org took 0.2891838550567627s
Reputation | Calculation of the PageRank for statusnet-spip-org took 0.021259069442749023s
Interlinking | Calculation of Degree of Connection for statusnet-spip-org took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for statusnet-spip-org took 0.0007836818695068359s
Interlinking | Calculation of Clustering coefficient for statusnet-spip-org took 7.009506225585938e-05s
Believability | Calculation of trust value for statusnet-spip-org took 1.4543533325195312e-05s
INFO | --- Analysis for statusnet-spip-org took 3.701439142227173s
Availability | SPARQL endpoint availability check for statusnet-spraci-org took 4.553794860839844e-05s
Availability | VoID file availability check for statusnet-spraci-org took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for statusnet-spraci-org took 0.31241631507873535s
Reputation | Calculation of the PageRank for statusnet-spraci-org took 0.020783185958862305s
Interlinking | Calculation of Degree of Connection for statusnet-spraci-org took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-spraci-org took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for statusnet-spraci-org took 6.818771362304688e-05s
Believability | Calculation of trust value for statusnet-spraci-org took 1.430511474609375e-05s
INFO | --- Analysis for statusnet-spraci-org took 7.098161697387695s
Availability | SPARQL endpoint availability check for statusnet-ssweeny-net took 8.797645568847656e-05s
Availability | VoID file availability check for statusnet-ssweeny-net took 0.0007460117340087891s
Completeness | Calculation of interlinking completeness for statusnet-ssweeny-net took 0.29294300079345703s
Reputation | Calculation of the PageRank for statusnet-ssweeny-net took 0.022991657257080078s
Interlinking | Calculation of Degree of Connection for statusnet-ssweeny-net took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for statusnet-ssweeny-net took 0.0009076595306396484s
Interlinking | Calculation of Clustering coefficient for statusnet-ssweeny-net took 0.00013256072998046875s
Believability | Calculation of trust value for statusnet-ssweeny-net took 1.4781951904296875e-05s
INFO | --- Analysis for statusnet-ssweeny-net took 5.6026389598846436s
Availability | SPARQL endpoint availability check for statusnet-status-net took 4.458427429199219e-05s
Availability | VoID file availability check for statusnet-status-net took 0.0006949901580810547s
Completeness | Calculation of interlinking completeness for statusnet-status-net took 0.3048820495605469s
Reputation | Calculation of the PageRank for statusnet-status-net took 0.021559953689575195s
Interlinking | Calculation of Degree of Connection for statusnet-status-net took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-status-net took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for statusnet-status-net took 0.00022840499877929688s
Believability | Calculation of trust value for statusnet-status-net took 1.3828277587890625e-05s
INFO | --- Analysis for statusnet-status-net took 3.941349506378174s
Availability | SPARQL endpoint availability check for statusnet-sweetiebelle-net took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-sweetiebelle-net took 0.00048089027404785156s
Completeness | Calculation of interlinking completeness for statusnet-sweetiebelle-net took 0.3081052303314209s
Reputation | Calculation of the PageRank for statusnet-sweetiebelle-net took 0.02138352394104004s
Interlinking | Calculation of Degree of Connection for statusnet-sweetiebelle-net took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-sweetiebelle-net took 0.0008745193481445312s
Interlinking | Calculation of Clustering coefficient for statusnet-sweetiebelle-net took 6.341934204101562e-05s
Believability | Calculation of trust value for statusnet-sweetiebelle-net took 1.4543533325195312e-05s
INFO | --- Analysis for statusnet-sweetiebelle-net took 2.7339611053466797s
Availability | SPARQL endpoint availability check for statusnet-tekk-com-ar took 9.703636169433594e-05s
Availability | VoID file availability check for statusnet-tekk-com-ar took 0.0006306171417236328s
Completeness | Calculation of interlinking completeness for statusnet-tekk-com-ar took 0.2895522117614746s
Reputation | Calculation of the PageRank for statusnet-tekk-com-ar took 0.02245354652404785s
Interlinking | Calculation of Degree of Connection for statusnet-tekk-com-ar took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-tekk-com-ar took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for statusnet-tekk-com-ar took 0.00010967254638671875s
Believability | Calculation of trust value for statusnet-tekk-com-ar took 1.430511474609375e-05s
INFO | --- Analysis for statusnet-tekk-com-ar took 2.82175612449646s
Availability | SPARQL endpoint availability check for statusnet-thelovebug-org took 0.00010466575622558594s
Availability | VoID file availability check for statusnet-thelovebug-org took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for statusnet-thelovebug-org took 0.314361572265625s
Reputation | Calculation of the PageRank for statusnet-thelovebug-org took 0.021159887313842773s
Interlinking | Calculation of Degree of Connection for statusnet-thelovebug-org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-thelovebug-org took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for statusnet-thelovebug-org took 0.0001316070556640625s
Believability | Calculation of trust value for statusnet-thelovebug-org took 1.71661376953125e-05s
INFO | --- Analysis for statusnet-thelovebug-org took 2.865272283554077s
Availability | SPARQL endpoint availability check for statusnet-thornton2-com took 5.269050598144531e-05s
Availability | VoID file availability check for statusnet-thornton2-com took 0.0007650852203369141s
Completeness | Calculation of interlinking completeness for statusnet-thornton2-com took 0.34109973907470703s
Reputation | Calculation of the PageRank for statusnet-thornton2-com took 0.020923137664794922s
Interlinking | Calculation of Degree of Connection for statusnet-thornton2-com took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-thornton2-com took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for statusnet-thornton2-com took 8.416175842285156e-05s
Believability | Calculation of trust value for statusnet-thornton2-com took 1.4781951904296875e-05s
INFO | --- Analysis for statusnet-thornton2-com took 7.1449363231658936s
Availability | SPARQL endpoint availability check for statusnet-timttmy-co-uk took 8.988380432128906e-05s
Availability | VoID file availability check for statusnet-timttmy-co-uk took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for statusnet-timttmy-co-uk took 0.3306899070739746s
Reputation | Calculation of the PageRank for statusnet-timttmy-co-uk took 0.022543907165527344s
Interlinking | Calculation of Degree of Connection for statusnet-timttmy-co-uk took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-timttmy-co-uk took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for statusnet-timttmy-co-uk took 0.00011014938354492188s
Believability | Calculation of trust value for statusnet-timttmy-co-uk took 1.4066696166992188e-05s
INFO | --- Analysis for statusnet-timttmy-co-uk took 3.015380382537842s
Availability | SPARQL endpoint availability check for statusnet-tl1n-com took 9.250640869140625e-05s
Availability | VoID file availability check for statusnet-tl1n-com took 0.0006458759307861328s
Completeness | Calculation of interlinking completeness for statusnet-tl1n-com took 0.3333714008331299s
Reputation | Calculation of the PageRank for statusnet-tl1n-com took 0.022574901580810547s
Interlinking | Calculation of Degree of Connection for statusnet-tl1n-com took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-tl1n-com took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for statusnet-tl1n-com took 4.7206878662109375e-05s
Believability | Calculation of trust value for statusnet-tl1n-com took 1.52587890625e-05s
INFO | --- Analysis for statusnet-tl1n-com took 3.8235907554626465s
Availability | SPARQL endpoint availability check for statusnet-tschlotfeldt-de took 9.083747863769531e-05s
Availability | VoID file availability check for statusnet-tschlotfeldt-de took 0.0004248619079589844s
Completeness | Calculation of interlinking completeness for statusnet-tschlotfeldt-de took 0.28964900970458984s
Reputation | Calculation of the PageRank for statusnet-tschlotfeldt-de took 0.021014690399169922s
Interlinking | Calculation of Degree of Connection for statusnet-tschlotfeldt-de took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-tschlotfeldt-de took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for statusnet-tschlotfeldt-de took 7.43865966796875e-05s
Believability | Calculation of trust value for statusnet-tschlotfeldt-de took 1.5974044799804688e-05s
INFO | --- Analysis for statusnet-tschlotfeldt-de took 2.9254589080810547s
Availability | SPARQL endpoint availability check for statusnet-uni-siegen-de took 8.749961853027344e-05s
Availability | VoID file availability check for statusnet-uni-siegen-de took 0.0006892681121826172s
Completeness | Calculation of interlinking completeness for statusnet-uni-siegen-de took 0.3142852783203125s
Reputation | Calculation of the PageRank for statusnet-uni-siegen-de took 0.02212381362915039s
Interlinking | Calculation of Degree of Connection for statusnet-uni-siegen-de took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-uni-siegen-de took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for statusnet-uni-siegen-de took 4.673004150390625e-05s
Believability | Calculation of trust value for statusnet-uni-siegen-de took 1.4543533325195312e-05s
INFO | --- Analysis for statusnet-uni-siegen-de took 3.6207950115203857s
Availability | SPARQL endpoint availability check for Super Terminology System(STEAK) - Linked Open Data took 0.0001125335693359375s
Availability | VoID file availability check for Super Terminology System(STEAK) - Linked Open Data took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for Super Terminology System(STEAK) - Linked Open Data took 0.32860612869262695s
Reputation | Calculation of the PageRank for Super Terminology System(STEAK) - Linked Open Data took 0.022775650024414062s
Interlinking | Calculation of Degree of Connection for Super Terminology System(STEAK) - Linked Open Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Super Terminology System(STEAK) - Linked Open Data took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Super Terminology System(STEAK) - Linked Open Data took 3.4332275390625e-05s
Believability | Calculation of trust value for Super Terminology System(STEAK) - Linked Open Data took 1.1920928955078125e-05s
INFO | --- Analysis for steak took 3.420541524887085s
Availability | SPARQL endpoint availability check for RAMEAU subject headings (STITCH) took 9.584426879882812e-05s
Availability | VoID file availability check for RAMEAU subject headings (STITCH) took 0.0007040500640869141s
Completeness | Calculation of interlinking completeness for RAMEAU subject headings (STITCH) took 0.5240037441253662s
Reputation | Calculation of the PageRank for RAMEAU subject headings (STITCH) took 0.02066516876220703s
Interlinking | Calculation of Degree of Connection for RAMEAU subject headings (STITCH) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for RAMEAU subject headings (STITCH) took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for RAMEAU subject headings (STITCH) took 6.175041198730469e-05s
Believability | Calculation of trust value for RAMEAU subject headings (STITCH) took 1.2874603271484375e-05s
INFO | --- Analysis for stitch-rameau took 4.616186857223511s
Availability | SPARQL endpoint availability check for Stone Tech Square took 0.8404126167297363s
Availability | VoID file availability check for Stone Tech Square took 0.0006377696990966797s
Completeness | Calculation of interlinking completeness for Stone Tech Square took 0.30022144317626953s
Reputation | Calculation of the PageRank for Stone Tech Square took 0.02178812026977539s
Interlinking | Calculation of Degree of Connection for Stone Tech Square took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Stone Tech Square took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Stone Tech Square took 1.4781951904296875e-05s
Believability | Calculation of trust value for Stone Tech Square took 1.4543533325195312e-05s
INFO | --- Analysis for stone-tech-square-data took 7.612524032592773s
Availability | SPARQL endpoint availability check for STW Thesaurus for Economics took 0.4121415615081787s
Availability | VoID file availability check for STW Thesaurus for Economics took 0.0006690025329589844s
Extra | Recovery of all triples for STW Thesaurus for Economics took 9.992298603057861s
Performance | Total latancy measurement for STW Thesaurus for Economics took 1.066122055053711s
Amount of data | Number of triples check for STW Thesaurus for Economics took 0.5870587825775146s
Interoperability | New terms check for STW Thesaurus for Economics took 1.7238285541534424s
Versatility | Languages check for STW Thesaurus for Economics took 1.4959921836853027s
Interpretability | Number of blank nodes check for STW Thesaurus for Economics took 0.4939708709716797s
Security | Check HTTPS for STW Thesaurus for Economics took 0.14817142486572266s
Interpretability | RDF structures check for STW Thesaurus for Economics took 0.24165678024291992s
Versatility | Serialization formats check for STW Thesaurus for Economics took 0.23388981819152832s
Availability | RDF dump link check for STW Thesaurus for Economics took 0.24117112159729004s
License | MR license check for STW Thesaurus for Economics took 0.24203944206237793s
License | HR license check for STW Thesaurus for Economics took 2.341508388519287s
Amount of data | Number of property check for STW Thesaurus for Economics took 0.23788762092590332s
Understandability | Number of label check for STW Thesaurus for Economics took 0.6154489517211914s
Understandability | URI regex check for STW Thesaurus for Economics took 0.4836404323577881s
Understandability | Vocabs check for STW Thesaurus for Economics took 0.22496771812438965s
Verifiability | Authors check for STW Thesaurus for Economics took 0.21730685234069824s
Verifiability | Publishers check for STW Thesaurus for Economics took 0.21396374702453613s
Performance | Throughput check for STW Thesaurus for Economics took 11.060944318771362s
Amount of data | Check the number of entities for STW Thesaurus for Economics took 0.8037796020507812s
Verifiability | Contribs. check for STW Thesaurus for Economics took 0.2359175682067871s
Interlinking | sameAs chians check for STW Thesaurus for Economics took 0.21686530113220215s
Interlinking | skos check for STW Thesaurus for Economics took 0.3008885383605957s
Interlinking | skos check for STW Thesaurus for Economics took 0.2927677631378174s
Timeliness | dataset update frequency check for STW Thesaurus for Economics took 0.24007391929626465s
Currency | Creation date check for STW Thesaurus for Economics took 0.46455907821655273s
Currency | Modification date check for STW Thesaurus for Economics took 0.474729061126709s
Rep.Conc. | URIs length for STW Thesaurus for Economics took 6.995391130447388s
Interoperability | New vocabularies check for STW Thesaurus for Economics took 3.0089824199676514s
Consistency | Deprecated classes/propertiers check for STW Thesaurus for Economics took 0.20503807067871094s
Accuracy | Check Functional Property for STW Thesaurus for Economics took 0.2145843505859375s
Accuracy | Check Inverse Functional Property for STW Thesaurus for Economics took 0.2258601188659668s
Accuracy | Check Empty annotation labels for STW Thesaurus for Economics took 4.568871974945068s
Accuracy | Check White space in annotation for STW Thesaurus for Economics took 1.0521774291992188s
Accuracy | Check Datatype consistency for STW Thesaurus for Economics took 2.435009002685547s
Consistency | Disjoint class check for STW Thesaurus for Economics took 0.24892568588256836s
Consistency | Check Misplaced properties for STW Thesaurus for Economics took 1.2462427616119385s
Consistency | Check Ontology hijacking for STW Thesaurus for Economics took 1.8730592727661133s
Consistency | Check Invalid usage of undefined classes for STW Thesaurus for Economics took 1.5464885234832764s
Consistency | Check Invalid usage of undefined properties for STW Thesaurus for Economics took 2.5391204357147217s
Conciseness | Check Extensional conciseness for STW Thesaurus for Economics took 1.6993441581726074s
Conciseness | Check Intensional conciseness for STW Thesaurus for Economics took 0.2579762935638428s
Security | Sign check for STW Thesaurus for Economics took 0.2309277057647705s
Availability | Check URIs Dereferenciability for STW Thesaurus for Economics took 3134.549120903015s
Completeness | Calculation of interlinking completeness for STW Thesaurus for Economics took 0.7575173377990723s
Reputation | Calculation of the PageRank for STW Thesaurus for Economics took 0.020996570587158203s
Interlinking | Calculation of Degree of Connection for STW Thesaurus for Economics took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for STW Thesaurus for Economics took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for STW Thesaurus for Economics took 0.00011897087097167969s
Interoperability | Check the re-using of existing vocabs for STW Thesaurus for Economics took 3.0954957008361816s
Believability | Calculation of trust value for STW Thesaurus for Economics took 1.5020370483398438e-05s
INFO | --- Analysis for stw-thesaurus-for-economics took 3224.546094894409s
Availability | SPARQL endpoint availability check for SudershanTech took 4.5299530029296875e-05s
Availability | VoID file availability check for SudershanTech took 0.0005972385406494141s
Completeness | Calculation of interlinking completeness for SudershanTech took 0.32679057121276855s
Reputation | Calculation of the PageRank for SudershanTech took 0.021360397338867188s
Interlinking | Calculation of Degree of Connection for SudershanTech took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for SudershanTech took 0.0008006095886230469s
Interlinking | Calculation of Clustering coefficient for SudershanTech took 3.7670135498046875e-05s
Believability | Calculation of trust value for SudershanTech took 1.621246337890625e-05s
INFO | --- Analysis for SudershanTech took 2.7888383865356445s
Availability | SPARQL endpoint availability check for Sudoc bibliographic data took 1.0505805015563965s
Availability | VoID file availability check for Sudoc bibliographic data took 0.0008435249328613281s
Completeness | Calculation of interlinking completeness for Sudoc bibliographic data took 0.3000822067260742s
Reputation | Calculation of the PageRank for Sudoc bibliographic data took 0.02142643928527832s
Interlinking | Calculation of Degree of Connection for Sudoc bibliographic data took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Sudoc bibliographic data took 0.0007996559143066406s
Interlinking | Calculation of Clustering coefficient for Sudoc bibliographic data took 5.4836273193359375e-05s
Believability | Calculation of trust value for Sudoc bibliographic data took 1.5020370483398438e-05s
INFO | --- Analysis for sudocfr took 7.861766576766968s
Availability | SPARQL endpoint availability check for Suface Forestière Mondiale 1990-2016 took 1.0640745162963867s
Availability | VoID file availability check for Suface Forestière Mondiale 1990-2016 took 0.0006911754608154297s
Extra | Recovery of all triples for Suface Forestière Mondiale 1990-2016 took 24.861109495162964s
Performance | Total latancy measurement for Suface Forestière Mondiale 1990-2016 took 2.7698521614074707s
Amount of data | Number of triples check for Suface Forestière Mondiale 1990-2016 took 1.6102497577667236s
Interoperability | New terms check for Suface Forestière Mondiale 1990-2016 took 3.0844385623931885s
Versatility | Languages check for Suface Forestière Mondiale 1990-2016 took 3.1474599838256836s
Interpretability | Number of blank nodes check for Suface Forestière Mondiale 1990-2016 took 1.3807737827301025s
Interpretability | RDF structures check for Suface Forestière Mondiale 1990-2016 took 0.5449397563934326s
Versatility | Serialization formats check for Suface Forestière Mondiale 1990-2016 took 0.5245347023010254s
Availability | RDF dump link check for Suface Forestière Mondiale 1990-2016 took 0.5410158634185791s
License | MR license check for Suface Forestière Mondiale 1990-2016 took 0.5805838108062744s
License | HR license check for Suface Forestière Mondiale 1990-2016 took 8.541045427322388s
Amount of data | Number of property check for Suface Forestière Mondiale 1990-2016 took 0.544196367263794s
Understandability | Number of label check for Suface Forestière Mondiale 1990-2016 took 0.7301764488220215s
Understandability | URI regex check for Suface Forestière Mondiale 1990-2016 took 1.1112680435180664s
Understandability | Vocabs check for Suface Forestière Mondiale 1990-2016 took 0.5313506126403809s
Verifiability | Authors check for Suface Forestière Mondiale 1990-2016 took 0.5563766956329346s
Verifiability | Publishers check for Suface Forestière Mondiale 1990-2016 took 0.5565762519836426s
Performance | Throughput check for Suface Forestière Mondiale 1990-2016 took 10.712785005569458s
Amount of data | Check the number of entities for Suface Forestière Mondiale 1990-2016 took 0.00011181831359863281s
Verifiability | Contribs. check for Suface Forestière Mondiale 1990-2016 took 0.5142543315887451s
Interlinking | sameAs chians check for Suface Forestière Mondiale 1990-2016 took 0.567826509475708s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.6076622009277344s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.5861556529998779s
Timeliness | dataset update frequency check for Suface Forestière Mondiale 1990-2016 took 0.5287225246429443s
Currency | Creation date check for Suface Forestière Mondiale 1990-2016 took 1.0602185726165771s
Currency | Modification date check for Suface Forestière Mondiale 1990-2016 took 1.1236844062805176s
Rep.Conc. | URIs length for Suface Forestière Mondiale 1990-2016 took 39.330705404281616s
Interoperability | New vocabularies check for Suface Forestière Mondiale 1990-2016 took 1.2159347534179688e-05s
Consistency | Deprecated classes/propertiers check for Suface Forestière Mondiale 1990-2016 took 0.5206947326660156s
Accuracy | Check Functional Property for Suface Forestière Mondiale 1990-2016 took 0.5351214408874512s
Accuracy | Check Inverse Functional Property for Suface Forestière Mondiale 1990-2016 took 0.5334556102752686s
Accuracy | Check Empty annotation labels for Suface Forestière Mondiale 1990-2016 took 3.028066873550415s
Accuracy | Check White space in annotation for Suface Forestière Mondiale 1990-2016 took 0.38727498054504395s
Consistency | Disjoint class check for Suface Forestière Mondiale 1990-2016 took 0.5325005054473877s
Consistency | Check Misplaced properties for Suface Forestière Mondiale 1990-2016 took 28.38068127632141s
Consistency | Misplaced classes for Suface Forestière Mondiale 1990-2016 took 9.619096994400024s
Consistency | Check Ontology hijacking for Suface Forestière Mondiale 1990-2016 took 300.45511412620544s
Consistency | Check Invalid usage of undefined properties for Suface Forestière Mondiale 1990-2016 took 19.346651077270508s
Conciseness | Check Extensional conciseness for Suface Forestière Mondiale 1990-2016 took 3.0714147090911865s
Conciseness | Check Intensional conciseness for Suface Forestière Mondiale 1990-2016 took 2.932448625564575s
Security | Sign check for Suface Forestière Mondiale 1990-2016 took 0.5484879016876221s
Availability | Check URIs Dereferenciability for Suface Forestière Mondiale 1990-2016 took 4543.744486570358s
Completeness | Calculation of interlinking completeness for Suface Forestière Mondiale 1990-2016 took 0.8366165161132812s
Reputation | Calculation of the PageRank for Suface Forestière Mondiale 1990-2016 took 0.022577285766601562s
Interlinking | Calculation of Degree of Connection for Suface Forestière Mondiale 1990-2016 took 7.200241088867188e-05s
Interlinking | Calculation of Centrality for Suface Forestière Mondiale 1990-2016 took 0.0007882118225097656s
Interlinking | Calculation of Clustering coefficient for Suface Forestière Mondiale 1990-2016 took 0.00010037422180175781s
Interoperability | Check the re-using of existing vocabs for Suface Forestière Mondiale 1990-2016 took 2.86102294921875e-06s
Believability | Calculation of trust value for Suface Forestière Mondiale 1990-2016 took 1.33514404296875e-05s
INFO | --- Analysis for Suface_Forestière_Mondiale_1990-2016 took 8103.011753559113s
Availability | SPARQL endpoint availability check for Surge Radio took 8.869171142578125e-05s
Availability | VoID file availability check for Surge Radio took 0.0004398822784423828s
Completeness | Calculation of interlinking completeness for Surge Radio took 0.27991533279418945s
Reputation | Calculation of the PageRank for Surge Radio took 0.021340131759643555s
Interlinking | Calculation of Degree of Connection for Surge Radio took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Surge Radio took 0.0007956027984619141s
Interlinking | Calculation of Clustering coefficient for Surge Radio took 0.000110626220703125s
Believability | Calculation of trust value for Surge Radio took 1.430511474609375e-05s
INFO | --- Analysis for surge-radio took 3.828718423843384s
Availability | SPARQL endpoint availability check for Soil & Water Assessment Tool took 8.940696716308594e-05s
Availability | VoID file availability check for Soil & Water Assessment Tool took 0.0008363723754882812s
Completeness | Calculation of interlinking completeness for Soil & Water Assessment Tool took 0.3293790817260742s
Reputation | Calculation of the PageRank for Soil & Water Assessment Tool took 0.020908594131469727s
Interlinking | Calculation of Degree of Connection for Soil & Water Assessment Tool took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Soil & Water Assessment Tool took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Soil & Water Assessment Tool took 3.3855438232421875e-05s
Believability | Calculation of trust value for Soil & Water Assessment Tool took 1.4066696166992188e-05s
INFO | --- Analysis for SWAT took 32.24501180648804s
Availability | SPARQL endpoint availability check for Swedish Open Cultural Heritage took 8.869171142578125e-05s
Availability | VoID file availability check for Swedish Open Cultural Heritage took 0.4985828399658203s
Completeness | Calculation of interlinking completeness for Swedish Open Cultural Heritage took 0.29126501083374023s
Reputation | Calculation of the PageRank for Swedish Open Cultural Heritage took 0.02117323875427246s
Interlinking | Calculation of Degree of Connection for Swedish Open Cultural Heritage took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Swedish Open Cultural Heritage took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Swedish Open Cultural Heritage took 7.414817810058594e-05s
Believability | Calculation of trust value for Swedish Open Cultural Heritage took 8.58306884765625e-06s
INFO | --- Analysis for swedish-open-cultural-heritage took 6.123902082443237s
Availability | SPARQL endpoint availability check for SweFN-RDF took 1.032372236251831s
Availability | VoID file availability check for SweFN-RDF took 0.0003972053527832031s
Completeness | Calculation of interlinking completeness for SweFN-RDF took 0.30207157135009766s
Reputation | Calculation of the PageRank for SweFN-RDF took 0.020737886428833008s
Interlinking | Calculation of Degree of Connection for SweFN-RDF took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for SweFN-RDF took 0.0007872581481933594s
Interlinking | Calculation of Clustering coefficient for SweFN-RDF took 4.220008850097656e-05s
Believability | Calculation of trust value for SweFN-RDF took 1.5020370483398438e-05s
INFO | --- Analysis for swefn-rdf took 5.965256214141846s
Availability | SPARQL endpoint availability check for SwetoDblp took 8.869171142578125e-05s
Availability | VoID file availability check for SwetoDblp took 0.000713348388671875s
Completeness | Calculation of interlinking completeness for SwetoDblp took 0.28119373321533203s
Reputation | Calculation of the PageRank for SwetoDblp took 0.021116018295288086s
Interlinking | Calculation of Degree of Connection for SwetoDblp took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for SwetoDblp took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for SwetoDblp took 4.100799560546875e-05s
Believability | Calculation of trust value for SwetoDblp took 1.5020370483398438e-05s
INFO | --- Analysis for sweto-dblp took 23.15895915031433s
Availability | SPARQL endpoint availability check for Swift Vocabulary took 0.5890779495239258s
Availability | VoID file availability check for Swift Vocabulary took 0.0006923675537109375s
Extra | Recovery of all triples for Swift Vocabulary took 2.0456643104553223s
Performance | Total latancy measurement for Swift Vocabulary took 1.002608060836792s
Amount of data | Number of triples check for Swift Vocabulary took 0.19206690788269043s
Interoperability | New terms check for Swift Vocabulary took 1.6374938488006592s
Versatility | Languages check for Swift Vocabulary took 0.20594525337219238s
Interpretability | Number of blank nodes check for Swift Vocabulary took 0.22903180122375488s
Interpretability | RDF structures check for Swift Vocabulary took 0.21556735038757324s
Versatility | Serialization formats check for Swift Vocabulary took 0.21848344802856445s
Availability | RDF dump link check for Swift Vocabulary took 0.17273473739624023s
License | MR license check for Swift Vocabulary took 0.19255805015563965s
License | HR license check for Swift Vocabulary took 0.17046427726745605s
Amount of data | Number of property check for Swift Vocabulary took 0.17708253860473633s
Understandability | Number of label check for Swift Vocabulary took 0.19974851608276367s
Understandability | URI regex check for Swift Vocabulary took 0.31299591064453125s
Understandability | Vocabs check for Swift Vocabulary took 0.20970892906188965s
Verifiability | Authors check for Swift Vocabulary took 0.21427559852600098s
Verifiability | Publishers check for Swift Vocabulary took 0.23543453216552734s
Performance | Throughput check for Swift Vocabulary took 10.81847071647644s
Amount of data | Check the number of entities for Swift Vocabulary took 8.058547973632812e-05s
Verifiability | Contribs. check for Swift Vocabulary took 0.21464109420776367s
Interlinking | sameAs chians check for Swift Vocabulary took 0.20827031135559082s
Interlinking | skos check for Swift Vocabulary took 0.20762848854064941s
Interlinking | skos check for Swift Vocabulary took 0.2070014476776123s
Timeliness | dataset update frequency check for Swift Vocabulary took 0.2096085548400879s
Currency | Creation date check for Swift Vocabulary took 0.45451903343200684s
Currency | Modification date check for Swift Vocabulary took 0.4262409210205078s
Rep.Conc. | URIs length for Swift Vocabulary took 0.7227432727813721s
Interoperability | New vocabularies check for Swift Vocabulary took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Swift Vocabulary took 0.21494626998901367s
Accuracy | Check Functional Property for Swift Vocabulary took 0.23306918144226074s
Accuracy | Check Inverse Functional Property for Swift Vocabulary took 0.18843293190002441s
Accuracy | Check Empty annotation labels for Swift Vocabulary took 0.3077423572540283s
Accuracy | Check White space in annotation for Swift Vocabulary took 0.0023725032806396484s
Accuracy | Check Datatype consistency for Swift Vocabulary took 0.03819537162780762s
Consistency | Disjoint class check for Swift Vocabulary took 0.20879316329956055s
Consistency | Check Misplaced properties for Swift Vocabulary took 0.46196866035461426s
Consistency | Misplaced classes for Swift Vocabulary took 0.27490663528442383s
Consistency | Check Ontology hijacking for Swift Vocabulary took 1.7170298099517822s
Consistency | Check Invalid usage of undefined classes for Swift Vocabulary took 1.4562928676605225s
Consistency | Check Invalid usage of undefined properties for Swift Vocabulary took 1.705190658569336s
Conciseness | Check Extensional conciseness for Swift Vocabulary took 0.026767492294311523s
Conciseness | Check Intensional conciseness for Swift Vocabulary took 0.1581423282623291s
Security | Sign check for Swift Vocabulary took 0.1857616901397705s
Availability | Check URIs Dereferenciability for Swift Vocabulary took 953.7992904186249s
Completeness | Calculation of interlinking completeness for Swift Vocabulary took 0.633167028427124s
Reputation | Calculation of the PageRank for Swift Vocabulary took 0.024167776107788086s
Interlinking | Calculation of Degree of Connection for Swift Vocabulary took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Swift Vocabulary took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Swift Vocabulary took 9.846687316894531e-05s
Interoperability | Check the re-using of existing vocabs for Swift Vocabulary took 2.1457672119140625e-06s
Believability | Calculation of trust value for Swift Vocabulary took 1.4781951904296875e-05s
INFO | --- Analysis for Swift took 1001.1402962207794s
Availability | SPARQL endpoint availability check for Symptoms in Chinese took 0.00010085105895996094s
Availability | VoID file availability check for Symptoms in Chinese took 0.001287221908569336s
Completeness | Calculation of interlinking completeness for Symptoms in Chinese took 0.3010129928588867s
Reputation | Calculation of the PageRank for Symptoms in Chinese took 0.020999670028686523s
Interlinking | Calculation of Degree of Connection for Symptoms in Chinese took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Symptoms in Chinese took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Symptoms in Chinese took 4.363059997558594e-05s
Believability | Calculation of trust value for Symptoms in Chinese took 3.528594970703125e-05s
INFO | --- Analysis for symptoms-in-chinese took 53.05830383300781s
Availability | SPARQL endpoint availability check for National Digital Data Archive of Hungary (partial) took 0.4018068313598633s
Availability | VoID file availability check for National Digital Data Archive of Hungary (partial) took 0.0008018016815185547s
Extra | Recovery of all triples for National Digital Data Archive of Hungary (partial) took 0.4967837333679199s
Performance | Total latancy measurement for National Digital Data Archive of Hungary (partial) took 0.9052286148071289s
Amount of data | Number of triples check for National Digital Data Archive of Hungary (partial) took 7.75749135017395s
Interoperability | New terms check for National Digital Data Archive of Hungary (partial) took 20.367072582244873s
Versatility | Languages check for National Digital Data Archive of Hungary (partial) took 0.16741085052490234s
Interpretability | Number of blank nodes check for National Digital Data Archive of Hungary (partial) took 3.378488063812256s
Security | Check HTTPS for National Digital Data Archive of Hungary (partial) took 0.12112689018249512s
Interpretability | RDF structures check for National Digital Data Archive of Hungary (partial) took 0.6262235641479492s
Versatility | Serialization formats check for National Digital Data Archive of Hungary (partial) took 0.6642980575561523s
Availability | RDF dump link check for National Digital Data Archive of Hungary (partial) took 0.16585206985473633s
License | MR license check for National Digital Data Archive of Hungary (partial) took 0.3572659492492676s
License | HR license check for National Digital Data Archive of Hungary (partial) took 54.91193389892578s
Amount of data | Number of property check for National Digital Data Archive of Hungary (partial) took 0.5177209377288818s
Understandability | Number of label check for National Digital Data Archive of Hungary (partial) took 33.703147888183594s
Understandability | URI regex check for National Digital Data Archive of Hungary (partial) took 0.3800351619720459s
Understandability | Vocabs check for National Digital Data Archive of Hungary (partial) took 0.23360538482666016s
Verifiability | Authors check for National Digital Data Archive of Hungary (partial) took 0.33283042907714844s
Verifiability | Publishers check for National Digital Data Archive of Hungary (partial) took 0.7401101589202881s
Performance | Throughput check for National Digital Data Archive of Hungary (partial) took 13.520846128463745s
Amount of data | Check the number of entities for National Digital Data Archive of Hungary (partial) took 9.894371032714844e-05s
Verifiability | Contribs. check for National Digital Data Archive of Hungary (partial) took 1.9144492149353027s
Interlinking | sameAs chians check for National Digital Data Archive of Hungary (partial) took 2.065225839614868s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.7333083152770996s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.6797873973846436s
Timeliness | dataset update frequency check for National Digital Data Archive of Hungary (partial) took 1.6358301639556885s
Currency | Creation date check for National Digital Data Archive of Hungary (partial) took 3.288106679916382s
Currency | Modification date check for National Digital Data Archive of Hungary (partial) took 3.094548225402832s
Rep.Conc. | URIs length for National Digital Data Archive of Hungary (partial) took 66.43640232086182s
Interoperability | New vocabularies check for National Digital Data Archive of Hungary (partial) took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for National Digital Data Archive of Hungary (partial) took 0.17120099067687988s
Accuracy | Check Functional Property for National Digital Data Archive of Hungary (partial) took 0.1950855255126953s
Accuracy | Check Inverse Functional Property for National Digital Data Archive of Hungary (partial) took 0.18863558769226074s
Accuracy | Check Empty annotation labels for National Digital Data Archive of Hungary (partial) took 0.2626924514770508s
Accuracy | Check White space in annotation for National Digital Data Archive of Hungary (partial) took 0.0012004375457763672s
Accuracy | Check Datatype consistency for National Digital Data Archive of Hungary (partial) took 0.001486063003540039s
Consistency | Disjoint class check for National Digital Data Archive of Hungary (partial) took 0.23415756225585938s
Consistency | Check Misplaced properties for National Digital Data Archive of Hungary (partial) took 44.23662066459656s
Consistency | Misplaced classes for National Digital Data Archive of Hungary (partial) took 0.2592902183532715s
Consistency | Check Ontology hijacking for National Digital Data Archive of Hungary (partial) took 1.7790720462799072s
Consistency | Check Invalid usage of undefined classes for National Digital Data Archive of Hungary (partial) took 1.4644174575805664s
Consistency | Check Invalid usage of undefined properties for National Digital Data Archive of Hungary (partial) took 45.53059720993042s
Conciseness | Check Extensional conciseness for National Digital Data Archive of Hungary (partial) took 0.001983642578125s
Conciseness | Check Intensional conciseness for National Digital Data Archive of Hungary (partial) took 0.43506646156311035s
Security | Sign check for National Digital Data Archive of Hungary (partial) took 0.20412516593933105s
Availability | Check URIs Dereferenciability for National Digital Data Archive of Hungary (partial) took 9.962136030197144s
Completeness | Calculation of interlinking completeness for National Digital Data Archive of Hungary (partial) took 0.3977091312408447s
Reputation | Calculation of the PageRank for National Digital Data Archive of Hungary (partial) took 0.025626420974731445s
Interlinking | Calculation of Degree of Connection for National Digital Data Archive of Hungary (partial) took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for National Digital Data Archive of Hungary (partial) took 0.00087738037109375s
Interlinking | Calculation of Clustering coefficient for National Digital Data Archive of Hungary (partial) took 0.00012564659118652344s
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.4781951904296875e-05s
INFO | --- Analysis for sztaki-lod took 489.5647156238556s
Availability | SPARQL endpoint availability check for Thesaurus for Graphic Materials (t4gm.info) took 5.435943603515625e-05s
Availability | VoID file availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.0005538463592529297s
Completeness | Calculation of interlinking completeness for Thesaurus for Graphic Materials (t4gm.info) took 0.3194084167480469s
Reputation | Calculation of the PageRank for Thesaurus for Graphic Materials (t4gm.info) took 0.021016597747802734s
Interlinking | Calculation of Degree of Connection for Thesaurus for Graphic Materials (t4gm.info) took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Thesaurus for Graphic Materials (t4gm.info) took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Thesaurus for Graphic Materials (t4gm.info) took 6.246566772460938e-05s
Believability | Calculation of trust value for Thesaurus for Graphic Materials (t4gm.info) took 1.3828277587890625e-05s
INFO | --- Analysis for t4gm-info took 3.0492310523986816s
Availability | SPARQL endpoint availability check for tags2con delicious took 4.363059997558594e-05s
Availability | VoID file availability check for tags2con delicious took 0.0007240772247314453s
Completeness | Calculation of interlinking completeness for tags2con delicious took 0.32231593132019043s
Reputation | Calculation of the PageRank for tags2con delicious took 0.022305965423583984s
Interlinking | Calculation of Degree of Connection for tags2con delicious took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for tags2con delicious took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for tags2con delicious took 4.7206878662109375e-05s
Believability | Calculation of trust value for tags2con delicious took 1.5020370483398438e-05s
INFO | --- Analysis for tags2con-delicious took 49.94951772689819s
Availability | SPARQL endpoint availability check for Taiwan geographic names took 263.0747535228729s
Availability | VoID file availability check for Taiwan geographic names took 0.0009160041809082031s
Completeness | Calculation of interlinking completeness for Taiwan geographic names took 0.2996079921722412s
Reputation | Calculation of the PageRank for Taiwan geographic names took 0.021254777908325195s
Interlinking | Calculation of Degree of Connection for Taiwan geographic names took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Taiwan geographic names took 0.000885009765625s
Interlinking | Calculation of Clustering coefficient for Taiwan geographic names took 6.937980651855469e-05s
Believability | Calculation of trust value for Taiwan geographic names took 1.430511474609375e-05s
INFO | --- Analysis for taiwan-geographic-names took 667.1581366062164s
Availability | SPARQL endpoint availability check for Open Library data mirror in the Talis Platform took 8.678436279296875e-05s
Availability | VoID file availability check for Open Library data mirror in the Talis Platform took 0.0006697177886962891s
Completeness | Calculation of interlinking completeness for Open Library data mirror in the Talis Platform took 0.2930014133453369s
Reputation | Calculation of the PageRank for Open Library data mirror in the Talis Platform took 0.0269620418548584s
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.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Open Library data mirror in the Talis Platform took 0.00010085105895996094s
Believability | Calculation of trust value for Open Library data mirror in the Talis Platform took 1.4543533325195312e-05s
INFO | --- Analysis for talis-openlibrary took 4.126392841339111s
Availability | SPARQL endpoint availability check for TaxonConcept Knowledge Base took 1.0127792358398438s
Availability | VoID file availability check for TaxonConcept Knowledge Base took 0.0005631446838378906s
Completeness | Calculation of interlinking completeness for TaxonConcept Knowledge Base took 0.31334638595581055s
Reputation | Calculation of the PageRank for TaxonConcept Knowledge Base took 0.020751953125s
Interlinking | Calculation of Degree of Connection for TaxonConcept Knowledge Base took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for TaxonConcept Knowledge Base took 0.0007951259613037109s
Interlinking | Calculation of Clustering coefficient for TaxonConcept Knowledge Base took 0.00013303756713867188s
Believability | Calculation of trust value for TaxonConcept Knowledge Base took 1.52587890625e-05s
INFO | --- Analysis for taxonconcept took 13.600693464279175s
Availability | SPARQL endpoint availability check for taxonconcept-assets took 9.655952453613281e-05s
Availability | VoID file availability check for taxonconcept-assets took 0.00058746337890625s
Completeness | Calculation of interlinking completeness for taxonconcept-assets took 0.29663753509521484s
Reputation | Calculation of the PageRank for taxonconcept-assets took 0.021353960037231445s
Interlinking | Calculation of Degree of Connection for taxonconcept-assets took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for taxonconcept-assets took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for taxonconcept-assets took 8.845329284667969e-05s
Believability | Calculation of trust value for taxonconcept-assets took 1.5497207641601562e-05s
INFO | --- Analysis for taxonconcept-assets took 3.024601459503174s
Availability | SPARQL endpoint availability check for taxonconcept-occurences took 4.38690185546875e-05s
Availability | VoID file availability check for taxonconcept-occurences took 0.0006289482116699219s
Completeness | Calculation of interlinking completeness for taxonconcept-occurences took 0.305617094039917s
Reputation | Calculation of the PageRank for taxonconcept-occurences took 0.0207822322845459s
Interlinking | Calculation of Degree of Connection for taxonconcept-occurences took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for taxonconcept-occurences took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for taxonconcept-occurences took 5.602836608886719e-05s
Believability | Calculation of trust value for taxonconcept-occurences took 1.5735626220703125e-05s
INFO | --- Analysis for taxonconcept-occurences took 3.1035609245300293s
Availability | SPARQL endpoint availability check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 21.25311803817749s
Availability | VoID file availability check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.0006501674652099609s
Completeness | Calculation of interlinking completeness for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.2813856601715088s
Reputation | Calculation of the PageRank for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.02114248275756836s
Interlinking | Calculation of Degree of Connection for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 5.9604644775390625e-05s
Believability | Calculation of trust value for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 1.3828277587890625e-05s
INFO | --- Analysis for taxref-ld took 75.38248133659363s
Availability | SPARQL endpoint availability check for The Cancer Genome Atlas took 262.3660132884979s
Availability | VoID file availability check for The Cancer Genome Atlas took 0.0007257461547851562s
Completeness | Calculation of interlinking completeness for The Cancer Genome Atlas took 0.2966320514678955s
Reputation | Calculation of the PageRank for The Cancer Genome Atlas took 0.02171158790588379s
Interlinking | Calculation of Degree of Connection for The Cancer Genome Atlas took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for The Cancer Genome Atlas took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for The Cancer Genome Atlas took 5.4836273193359375e-05s
Believability | Calculation of trust value for The Cancer Genome Atlas took 1.52587890625e-05s
INFO | --- Analysis for tcga took 540.8412606716156s
Availability | SPARQL endpoint availability check for TCGA Roadmap took 0.3620305061340332s
Availability | VoID file availability check for TCGA Roadmap took 0.0008442401885986328s
Completeness | Calculation of interlinking completeness for TCGA Roadmap took 0.2962617874145508s
Reputation | Calculation of the PageRank for TCGA Roadmap took 0.020978212356567383s
Interlinking | Calculation of Degree of Connection for TCGA Roadmap took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for TCGA Roadmap took 0.0008428096771240234s
Interlinking | Calculation of Clustering coefficient for TCGA Roadmap took 8.344650268554688e-05s
Believability | Calculation of trust value for TCGA Roadmap took 1.3113021850585938e-05s
INFO | --- Analysis for tcga-roadmap took 7.246830940246582s
Availability | SPARQL endpoint availability check for TCMGeneDIT Dataset took 1.430326223373413s
Availability | VoID file availability check for TCMGeneDIT Dataset took 0.0006344318389892578s
Completeness | Calculation of interlinking completeness for TCMGeneDIT Dataset took 0.3345499038696289s
Reputation | Calculation of the PageRank for TCMGeneDIT Dataset took 0.021105527877807617s
Interlinking | Calculation of Degree of Connection for TCMGeneDIT Dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for TCMGeneDIT Dataset took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for TCMGeneDIT Dataset took 0.00011396408081054688s
Believability | Calculation of trust value for TCMGeneDIT Dataset took 1.4543533325195312e-05s
INFO | --- Analysis for tcmgenedit_dataset took 138.83403897285461s
Availability | SPARQL endpoint availability check for TDS took 0.00010061264038085938s
Availability | VoID file availability check for TDS took 0.0007073879241943359s
Completeness | Calculation of interlinking completeness for TDS took 0.3162047863006592s
Reputation | Calculation of the PageRank for TDS took 0.021397829055786133s
Interlinking | Calculation of Degree of Connection for TDS took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for TDS took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for TDS took 4.482269287109375e-05s
Believability | Calculation of trust value for TDS took 1.5497207641601562e-05s
INFO | --- Analysis for tds took 4.940392971038818s
Availability | SPARQL endpoint availability check for TEKORD took 8.940696716308594e-05s
Availability | VoID file availability check for TEKORD took 0.0007598400115966797s
Completeness | Calculation of interlinking completeness for TEKORD took 0.34102344512939453s
Reputation | Calculation of the PageRank for TEKORD took 0.020746946334838867s
Interlinking | Calculation of Degree of Connection for TEKORD took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for TEKORD took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for TEKORD took 5.14984130859375e-05s
Believability | Calculation of trust value for TEKORD took 1.5020370483398438e-05s
INFO | --- Analysis for tekord took 5.467621326446533s
Availability | SPARQL endpoint availability check for Telegraphis Linked Data took 2.5835442543029785s
Availability | VoID file availability check for Telegraphis Linked Data took 0.0004458427429199219s
Completeness | Calculation of interlinking completeness for Telegraphis Linked Data took 0.2886044979095459s
Reputation | Calculation of the PageRank for Telegraphis Linked Data took 0.021947383880615234s
Interlinking | Calculation of Degree of Connection for Telegraphis Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Telegraphis Linked Data took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Telegraphis Linked Data took 0.00012040138244628906s
Believability | Calculation of trust value for Telegraphis Linked Data took 1.0967254638671875e-05s
INFO | --- Analysis for telegraphis took 8.937825441360474s
Availability | SPARQL endpoint availability check for Temple ov thee Lemur took 6.580352783203125e-05s
Availability | VoID file availability check for Temple ov thee Lemur took 0.0006806850433349609s
Completeness | Calculation of interlinking completeness for Temple ov thee Lemur took 0.29396700859069824s
Reputation | Calculation of the PageRank for Temple ov thee Lemur took 0.021100282669067383s
Interlinking | Calculation of Degree of Connection for Temple ov thee Lemur took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Temple ov thee Lemur took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Temple ov thee Lemur took 7.343292236328125e-05s
Believability | Calculation of trust value for Temple ov thee Lemur took 1.4066696166992188e-05s
INFO | --- Analysis for temple-ov-thee-lemur-datasets took 16.28929328918457s
Availability | SPARQL endpoint availability check for Ontology took 9.989738464355469e-05s
Availability | VoID file availability check for Ontology took 0.0006897449493408203s
Completeness | Calculation of interlinking completeness for Ontology took 0.30700111389160156s
Reputation | Calculation of the PageRank for Ontology took 0.02086186408996582s
Interlinking | Calculation of Degree of Connection for Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Ontology took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Ontology took 3.24249267578125e-05s
Believability | Calculation of trust value for Ontology took 1.3828277587890625e-05s
INFO | --- Analysis for Terrorist_attack took 3.406944513320923s
Availability | SPARQL endpoint availability check for Terrorist Attack1 took 4.458427429199219e-05s
Availability | VoID file availability check for Terrorist Attack1 took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for Terrorist Attack1 took 0.3046717643737793s
Reputation | Calculation of the PageRank for Terrorist Attack1 took 0.021579504013061523s
Interlinking | Calculation of Degree of Connection for Terrorist Attack1 took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Terrorist Attack1 took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Terrorist Attack1 took 3.528594970703125e-05s
Believability | Calculation of trust value for Terrorist Attack1 took 9.298324584960938e-06s
INFO | --- Analysis for Terrorist_Attack_1 took 2.7293319702148438s
Availability | SPARQL endpoint availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 8.988380432128906e-05s
Availability | VoID file availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.000682830810546875s
Completeness | Calculation of interlinking completeness for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.2956724166870117s
Reputation | Calculation of the PageRank for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.022430896759033203s
Interlinking | Calculation of Degree of Connection for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.00078582763671875s
Interlinking | Calculation of Clustering coefficient for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 3.504753112792969e-05s
Believability | Calculation of trust value for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 1.52587890625e-05s
INFO | --- Analysis for Tesla_Deaths took 4.9332685470581055s
Availability | SPARQL endpoint availability check for test took 5.221366882324219e-05s
Availability | VoID file availability check for test took 0.0005810260772705078s
Completeness | Calculation of interlinking completeness for test took 0.31322646141052246s
Reputation | Calculation of the PageRank for test took 0.021084070205688477s
Interlinking | Calculation of Degree of Connection for test took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for test took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for test took 3.4332275390625e-05s
Believability | Calculation of trust value for test took 1.3828277587890625e-05s
INFO | --- Analysis for test took 2.7207255363464355s
Availability | SPARQL endpoint availability check for Test took 4.649162292480469e-05s
Availability | VoID file availability check for Test took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for Test took 0.31699562072753906s
Reputation | Calculation of the PageRank for Test took 0.02078700065612793s
Interlinking | Calculation of Degree of Connection for Test took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Test took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for Test took 3.6716461181640625e-05s
Believability | Calculation of trust value for Test took 1.3828277587890625e-05s
INFO | --- Analysis for Test took 2.7474687099456787s
Availability | SPARQL endpoint availability check for test-svu took 20.194174766540527s
Availability | VoID file availability check for test-svu took 0.0005025863647460938s
Completeness | Calculation of interlinking completeness for test-svu took 0.27792811393737793s
Reputation | Calculation of the PageRank for test-svu took 0.023117542266845703s
Interlinking | Calculation of Degree of Connection for test-svu took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for test-svu took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for test-svu took 3.743171691894531e-05s
Believability | Calculation of trust value for test-svu took 1.0728836059570312e-05s
INFO | --- Analysis for test-svu took 52.8774471282959s
Availability | SPARQL endpoint availability check for Test took 4.4345855712890625e-05s
Availability | VoID file availability check for Test took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for Test took 0.33118462562561035s
Reputation | Calculation of the PageRank for Test took 0.021959781646728516s
Interlinking | Calculation of Degree of Connection for Test took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Test took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Test took 3.361701965332031e-05s
Believability | Calculation of trust value for Test took 1.239776611328125e-05s
INFO | --- Analysis for Test_ took 2.721078634262085s
Availability | SPARQL endpoint availability check for xxxxx took 261.44936203956604s
Availability | VoID file availability check for xxxxx took 0.0008993148803710938s
Completeness | Calculation of interlinking completeness for xxxxx took 0.404252290725708s
Reputation | Calculation of the PageRank for xxxxx took 0.021335124969482422s
Interlinking | Calculation of Degree of Connection for xxxxx took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for xxxxx took 0.0008039474487304688s
Interlinking | Calculation of Clustering coefficient for xxxxx took 6.0558319091796875e-05s
Believability | Calculation of trust value for xxxxx took 9.298324584960938e-06s
INFO | --- Analysis for testee took 796.6121153831482s
Availability | SPARQL endpoint availability check for tharawat magazine took 8.845329284667969e-05s
Availability | VoID file availability check for tharawat magazine took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for tharawat magazine took 0.28211522102355957s
Reputation | Calculation of the PageRank for tharawat magazine took 0.0209047794342041s
Interlinking | Calculation of Degree of Connection for tharawat magazine took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for tharawat magazine took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for tharawat magazine took 0.00011682510375976562s
Believability | Calculation of trust value for tharawat magazine took 1.5497207641601562e-05s
INFO | --- Analysis for tharawat-magazine-com took 3.43056583404541s
Availability | SPARQL endpoint availability check for The Drug Interaction Knowledge Base took 1.517646312713623s
Availability | VoID file availability check for The Drug Interaction Knowledge Base took 0.0007357597351074219s
Completeness | Calculation of interlinking completeness for The Drug Interaction Knowledge Base took 0.31355929374694824s
Reputation | Calculation of the PageRank for The Drug Interaction Knowledge Base took 0.021898269653320312s
Interlinking | Calculation of Degree of Connection for The Drug Interaction Knowledge Base took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The Drug Interaction Knowledge Base took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for The Drug Interaction Knowledge Base took 3.528594970703125e-05s
Believability | Calculation of trust value for The Drug Interaction Knowledge Base took 1.430511474609375e-05s
INFO | --- Analysis for the-drug-interaction-knowledge-base took 7.976329803466797s
Availability | SPARQL endpoint availability check for The European Library Open Dataset took 3.3150312900543213s
Availability | VoID file availability check for The European Library Open Dataset took 0.0007555484771728516s
Extra | Recovery of all triples for The European Library Open Dataset took 6.972062826156616s
Performance | Total latancy measurement for The European Library Open Dataset took 15.995562553405762s
Amount of data | Number of triples check for The European Library Open Dataset took 63.39567446708679s
Interoperability | New terms check for The European Library Open Dataset took 59.69797897338867s
Versatility | Languages check for The European Library Open Dataset took 3.300859212875366s
Interpretability | Number of blank nodes check for The European Library Open Dataset took 3.2055420875549316s
Interpretability | RDF structures check for The European Library Open Dataset took 3.204285144805908s
Versatility | Serialization formats check for The European Library Open Dataset took 3.199983596801758s
Availability | RDF dump link check for The European Library Open Dataset took 3.196458578109741s
License | MR license check for The European Library Open Dataset took 3.2054381370544434s
License | HR license check for The European Library Open Dataset took 3.1975815296173096s
Amount of data | Number of property check for The European Library Open Dataset took 3.2031829357147217s
Understandability | Number of label check for The European Library Open Dataset took 3.7291412353515625s
Understandability | URI regex check for The European Library Open Dataset took 6.379448890686035s
Understandability | Vocabs check for The European Library Open Dataset took 3.2003517150878906s
Verifiability | Authors check for The European Library Open Dataset took 3.2028255462646484s
Verifiability | Publishers check for The European Library Open Dataset took 3.1949031352996826s
Performance | Throughput check for The European Library Open Dataset took 32.00193643569946s
Amount of data | Check the number of entities for The European Library Open Dataset took 7.414817810058594e-05s
Verifiability | Contribs. check for The European Library Open Dataset took 3.200774908065796s
Interlinking | sameAs chians check for The European Library Open Dataset took 3.3191776275634766s
Interlinking | skos check for The European Library Open Dataset took 3.220719575881958s
Interlinking | skos check for The European Library Open Dataset took 3.2320289611816406s
Timeliness | dataset update frequency check for The European Library Open Dataset took 3.1907777786254883s
Currency | Creation date check for The European Library Open Dataset took 6.393854141235352s
Currency | Modification date check for The European Library Open Dataset took 6.400924921035767s
Rep.Conc. | URIs length for The European Library Open Dataset took 123.23461151123047s
Interoperability | New vocabularies check for The European Library Open Dataset took 4.76837158203125e-06s
Consistency | Deprecated classes/propertiers check for The European Library Open Dataset took 0.352797269821167s
Accuracy | Check Empty annotation labels for The European Library Open Dataset took 3.5379717350006104s
Accuracy | Check White space in annotation for The European Library Open Dataset took 0.026294231414794922s
Accuracy | Check Datatype consistency for The European Library Open Dataset took 0.02952885627746582s
Consistency | Disjoint class check for The European Library Open Dataset took 3.231581449508667s
Consistency | Check Misplaced properties for The European Library Open Dataset took 67.29385709762573s
Consistency | Misplaced classes for The European Library Open Dataset took 3.2690865993499756s
Consistency | Check Ontology hijacking for The European Library Open Dataset took 4.978907585144043s
Consistency | Check Invalid usage of undefined classes for The European Library Open Dataset took 1.4537878036499023s
Consistency | Check Invalid usage of undefined properties for The European Library Open Dataset took 65.38948392868042s
Conciseness | Check Extensional conciseness for The European Library Open Dataset took 0.03406095504760742s
Conciseness | Check Intensional conciseness for The European Library Open Dataset took 3.1911556720733643s
Security | Sign check for The European Library Open Dataset took 3.2023239135742188s
Availability | Check URIs Dereferenciability for The European Library Open Dataset took 10.89583420753479s
Completeness | Calculation of interlinking completeness for The European Library Open Dataset took 0.5703983306884766s
Reputation | Calculation of the PageRank for The European Library Open Dataset took 0.0212094783782959s
Interlinking | Calculation of Degree of Connection for The European Library Open Dataset took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for The European Library Open Dataset took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for The European Library Open Dataset took 7.677078247070312e-05s
Interoperability | Check the re-using of existing vocabs for The European Library Open Dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for The European Library Open Dataset took 1.4066696166992188e-05s
INFO | --- Analysis for the-european-library-open-dataset took 909.8436770439148s
Availability | SPARQL endpoint availability check for The Eurostat Linked Data took 60.04177188873291s
Availability | VoID file availability check for The Eurostat Linked Data took 0.0008218288421630859s
Completeness | Calculation of interlinking completeness for The Eurostat Linked Data took 0.33353376388549805s
Reputation | Calculation of the PageRank for The Eurostat Linked Data took 0.0217897891998291s
Interlinking | Calculation of Degree of Connection for The Eurostat Linked Data took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for The Eurostat Linked Data took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for The Eurostat Linked Data took 0.00011968612670898438s
Believability | Calculation of trust value for The Eurostat Linked Data took 1.0967254638671875e-05s
INFO | --- Analysis for the-eurostat-linked-data took 243.0154836177826s
Availability | SPARQL endpoint availability check for The Living LOD Cloud took 5.817413330078125e-05s
Availability | VoID file availability check for The Living LOD Cloud took 0.00040149688720703125s
Completeness | Calculation of interlinking completeness for The Living LOD Cloud took 0.294619083404541s
Reputation | Calculation of the PageRank for The Living LOD Cloud took 0.02160954475402832s
Interlinking | Calculation of Degree of Connection for The Living LOD Cloud took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for The Living LOD Cloud took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for The Living LOD Cloud took 8.606910705566406e-05s
Believability | Calculation of trust value for The Living LOD Cloud took 1.5020370483398438e-05s
INFO | --- Analysis for the-living-lod-cloud took 45.05132818222046s
Availability | SPARQL endpoint availability check for The View From took 5.284800052642822s
Availability | VoID file availability check for The View From took 0.0002994537353515625s
Completeness | Calculation of interlinking completeness for The View From took 0.3092372417449951s
Reputation | Calculation of the PageRank for The View From took 0.021039247512817383s
Interlinking | Calculation of Degree of Connection for The View From took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for The View From took 0.0008077621459960938s
Interlinking | Calculation of Clustering coefficient for The View From took 9.34600830078125e-05s
Believability | Calculation of trust value for The View From took 1.4066696166992188e-05s
INFO | --- Analysis for the-view-from took 15.781965255737305s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.520766735076904s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.3253912925720215s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.023421525955200195s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.001153707504272461s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 4.744529724121094e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 1.4543533325195312e-05s
INFO | --- Analysis for The_Central_Bank_of_the_Republic_of_Uzbekistan took 73.41144943237305s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.29665780067444s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0007798671722412109s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.3051300048828125s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.021403789520263672s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007908344268798828s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 5.054473876953125e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 1.52587890625e-05s
INFO | --- Analysis for The_Respublic_of_Uzbekistan took 103.54843091964722s
Availability | SPARQL endpoint availability check for The Content Wrangler took 9.202957153320312e-05s
Availability | VoID file availability check for The Content Wrangler took 0.0005424022674560547s
Completeness | Calculation of interlinking completeness for The Content Wrangler took 0.29256153106689453s
Reputation | Calculation of the PageRank for The Content Wrangler took 0.020746707916259766s
Interlinking | Calculation of Degree of Connection for The Content Wrangler took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for The Content Wrangler took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for The Content Wrangler took 0.00011420249938964844s
Believability | Calculation of trust value for The Content Wrangler took 1.4066696166992188e-05s
INFO | --- Analysis for thecontentwrangler-com took 4.712175607681274s
Availability | SPARQL endpoint availability check for Thesaurus Datenwissen took 4.792213439941406e-05s
Availability | VoID file availability check for Thesaurus Datenwissen took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for Thesaurus Datenwissen took 0.3685293197631836s
Reputation | Calculation of the PageRank for Thesaurus Datenwissen took 0.02094888687133789s
Interlinking | Calculation of Degree of Connection for Thesaurus Datenwissen took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Thesaurus Datenwissen took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Thesaurus Datenwissen took 3.5762786865234375e-05s
Believability | Calculation of trust value for Thesaurus Datenwissen took 1.3589859008789062e-05s
INFO | --- Analysis for thesaurus-datenwissen took 2.9196386337280273s
Availability | SPARQL endpoint availability check for Thesaurus W for Local Archives took 0.6022458076477051s
Availability | VoID file availability check for Thesaurus W for Local Archives took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for Thesaurus W for Local Archives took 0.31804680824279785s
Reputation | Calculation of the PageRank for Thesaurus W for Local Archives took 0.022214412689208984s
Interlinking | Calculation of Degree of Connection for Thesaurus W for Local Archives took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Thesaurus W for Local Archives took 0.0008442401885986328s
Interlinking | Calculation of Clustering coefficient for Thesaurus W for Local Archives took 9.369850158691406e-05s
Believability | Calculation of trust value for Thesaurus W for Local Archives took 1.4066696166992188e-05s
INFO | --- Analysis for thesaurus-w took 4.199466705322266s
Availability | SPARQL endpoint availability check for theses.fr took 9.5367431640625e-05s
Availability | VoID file availability check for theses.fr took 0.0005848407745361328s
Completeness | Calculation of interlinking completeness for theses.fr took 0.310443639755249s
Reputation | Calculation of the PageRank for theses.fr took 0.020784854888916016s
Interlinking | Calculation of Degree of Connection for theses.fr took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for theses.fr took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for theses.fr took 5.14984130859375e-05s
Believability | Calculation of trust value for theses.fr took 1.2159347534179688e-05s
INFO | --- Analysis for thesesfr took 4.466445684432983s
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.00048279762268066406s
Completeness | Calculation of interlinking completeness for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.27968740463256836s
Reputation | Calculation of the PageRank for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.023041725158691406s
Interlinking | Calculation of Degree of Connection for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 3.647804260253906e-05s
Believability | Calculation of trust value for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 1.3589859008789062e-05s
INFO | --- Analysis for Thinkphile took 2.662490129470825s
Availability | SPARQL endpoint availability check for ThIST took 266.54877400398254s
Availability | VoID file availability check for ThIST took 0.0006003379821777344s
Completeness | Calculation of interlinking completeness for ThIST took 0.3174715042114258s
Reputation | Calculation of the PageRank for ThIST took 0.02121710777282715s
Interlinking | Calculation of Degree of Connection for ThIST took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for ThIST took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for ThIST took 9.441375732421875e-05s
Believability | Calculation of trust value for ThIST took 1.5735626220703125e-05s
INFO | --- Analysis for thist took 565.3835344314575s
Availability | SPARQL endpoint availability check for TIP took 40.034939765930176s
Availability | VoID file availability check for TIP took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for TIP took 0.29454922676086426s
Reputation | Calculation of the PageRank for TIP took 0.021219730377197266s
Interlinking | Calculation of Degree of Connection for TIP took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for TIP took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for TIP took 0.00011897087097167969s
Believability | Calculation of trust value for TIP took 1.4543533325195312e-05s
INFO | --- Analysis for tip took 102.77991008758545s
Availability | SPARQL endpoint availability check for Topography based Hydrological Model took 5.1021575927734375e-05s
Availability | VoID file availability check for Topography based Hydrological Model took 0.0008444786071777344s
Completeness | Calculation of interlinking completeness for Topography based Hydrological Model took 0.31020092964172363s
Reputation | Calculation of the PageRank for Topography based Hydrological Model took 0.021875858306884766s
Interlinking | Calculation of Degree of Connection for Topography based Hydrological Model took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Topography based Hydrological Model took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Topography based Hydrological Model took 4.6253204345703125e-05s
Believability | Calculation of trust value for Topography based Hydrological Model took 1.33514404296875e-05s
INFO | --- Analysis for TOPMODEL took 26.324239492416382s
Availability | SPARQL endpoint availability check for Observation dataset of forest ecosystems  took 3.440849781036377s
Availability | VoID file availability check for Observation dataset of forest ecosystems  took 0.0005474090576171875s
Completeness | Calculation of interlinking completeness for Observation dataset of forest ecosystems  took 0.29018616676330566s
Reputation | Calculation of the PageRank for Observation dataset of forest ecosystems  took 0.02235722541809082s
Interlinking | Calculation of Degree of Connection for Observation dataset of forest ecosystems  took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Observation dataset of forest ecosystems  took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Observation dataset of forest ecosystems  took 4.1484832763671875e-05s
Believability | Calculation of trust value for Observation dataset of forest ecosystems  took 1.4781951904296875e-05s
INFO | --- Analysis for TP-data took 7.63852071762085s
Availability | SPARQL endpoint availability check for Traditional Korean Medicine Ontology took 0.3506944179534912s
Availability | VoID file availability check for Traditional Korean Medicine Ontology took 0.0008180141448974609s
Completeness | Calculation of interlinking completeness for Traditional Korean Medicine Ontology took 0.321364164352417s
Reputation | Calculation of the PageRank for Traditional Korean Medicine Ontology took 0.02075028419494629s
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.0007238388061523438s
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.7404556274414062e-05s
INFO | --- Analysis for traditional-korean-medicine took 3.649380922317505s
Availability | SPARQL endpoint availability check for Traffic Scotland took 0.2598447799682617s
Availability | VoID file availability check for Traffic Scotland took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for Traffic Scotland took 0.28849172592163086s
Reputation | Calculation of the PageRank for Traffic Scotland took 0.02109360694885254s
Interlinking | Calculation of Degree of Connection for Traffic Scotland took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Traffic Scotland took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Traffic Scotland took 3.910064697265625e-05s
Believability | Calculation of trust value for Traffic Scotland took 1.1682510375976562e-05s
INFO | --- Analysis for traffic-scotland took 3.0328421592712402s
Availability | SPARQL endpoint availability check for Transparency International Linked Data took 0.09175777435302734s
Availability | VoID file availability check for Transparency International Linked Data took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for Transparency International Linked Data took 0.31033802032470703s
Reputation | Calculation of the PageRank for Transparency International Linked Data took 0.020785093307495117s
Interlinking | Calculation of Degree of Connection for Transparency International Linked Data took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Transparency International Linked Data took 0.0007996559143066406s
Interlinking | Calculation of Clustering coefficient for Transparency International Linked Data took 0.00011372566223144531s
Believability | Calculation of trust value for Transparency International Linked Data took 1.0251998901367188e-05s
INFO | --- Analysis for transparency-linked-data took 2.917880058288574s
Availability | SPARQL endpoint availability check for transport.data.gov.uk took 0.7107388973236084s
Availability | VoID file availability check for transport.data.gov.uk took 0.0005614757537841797s
Completeness | Calculation of interlinking completeness for transport.data.gov.uk took 0.2997877597808838s
Reputation | Calculation of the PageRank for transport.data.gov.uk took 0.020790576934814453s
Interlinking | Calculation of Degree of Connection for transport.data.gov.uk took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for transport.data.gov.uk took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for transport.data.gov.uk took 9.918212890625e-05s
Believability | Calculation of trust value for transport.data.gov.uk took 1.1682510375976562e-05s
INFO | --- Analysis for transport-data-gov-uk took 4.293581247329712s
Availability | SPARQL endpoint availability check for Trelios took 9.632110595703125e-05s
Availability | VoID file availability check for Trelios took 0.0005869865417480469s
Completeness | Calculation of interlinking completeness for Trelios took 0.29268407821655273s
Reputation | Calculation of the PageRank for Trelios took 0.02119922637939453s
Interlinking | Calculation of Degree of Connection for Trelios took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Trelios took 0.00079345703125s
Interlinking | Calculation of Clustering coefficient for Trelios took 1.5020370483398438e-05s
Believability | Calculation of trust value for Trelios took 1.4781951904296875e-05s
INFO | --- Analysis for Trelios took 2.7349040508270264s
Availability | SPARQL endpoint availability check for Twarql took 10.624316930770874s
Availability | VoID file availability check for Twarql took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for Twarql took 0.3066823482513428s
Reputation | Calculation of the PageRank for Twarql took 0.020923614501953125s
Interlinking | Calculation of Degree of Connection for Twarql took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Twarql took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Twarql took 7.152557373046875e-05s
Believability | Calculation of trust value for Twarql took 1.33514404296875e-05s
INFO | --- Analysis for twarql took 13.370791912078857s
Availability | SPARQL endpoint availability check for TWC Data-gov took 6.127357482910156e-05s
Availability | VoID file availability check for TWC Data-gov took 0.0007112026214599609s
Completeness | Calculation of interlinking completeness for TWC Data-gov took 0.27918553352355957s
Reputation | Calculation of the PageRank for TWC Data-gov took 0.020488262176513672s
Interlinking | Calculation of Degree of Connection for TWC Data-gov took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for TWC Data-gov took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for TWC Data-gov took 3.4809112548828125e-05s
Believability | Calculation of trust value for TWC Data-gov took 1.0251998901367188e-05s
INFO | --- Analysis for twc-data-gov took 13.076105117797852s
Availability | SPARQL endpoint availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.1399075984954834s
Availability | VoID file availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.0007941722869873047s
Completeness | Calculation of interlinking completeness for HealthData.gov Platform (HDP) on the Semantic Web took 0.30965352058410645s
Reputation | Calculation of the PageRank for HealthData.gov Platform (HDP) on the Semantic Web took 0.022194862365722656s
Interlinking | Calculation of Degree of Connection for HealthData.gov Platform (HDP) on the Semantic Web took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for HealthData.gov Platform (HDP) on the Semantic Web took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for HealthData.gov Platform (HDP) on the Semantic Web took 4.3392181396484375e-05s
Believability | Calculation of trust value for HealthData.gov Platform (HDP) on the Semantic Web took 1.0967254638671875e-05s
INFO | --- Analysis for twc-healthdata took 16.522369861602783s
Availability | SPARQL endpoint availability check for Instance Hub (all) took 4.197463512420654s
Availability | VoID file availability check for Instance Hub (all) took 0.0004417896270751953s
Completeness | Calculation of interlinking completeness for Instance Hub (all) took 0.31124377250671387s
Reputation | Calculation of the PageRank for Instance Hub (all) took 0.021107912063598633s
Interlinking | Calculation of Degree of Connection for Instance Hub (all) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Instance Hub (all) took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Instance Hub (all) took 7.486343383789062e-05s
Believability | Calculation of trust value for Instance Hub (all) took 1.52587890625e-05s
INFO | --- Analysis for twc-hub took 78.05483913421631s
Availability | SPARQL endpoint availability check for IEEE VIS Source Data took 0.13887810707092285s
Availability | VoID file availability check for IEEE VIS Source Data took 0.0006198883056640625s
Completeness | Calculation of interlinking completeness for IEEE VIS Source Data took 0.4188663959503174s
Reputation | Calculation of the PageRank for IEEE VIS Source Data took 0.02128767967224121s
Interlinking | Calculation of Degree of Connection for IEEE VIS Source Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for IEEE VIS Source Data took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for IEEE VIS Source Data took 0.000118255615234375s
Believability | Calculation of trust value for IEEE VIS Source Data took 1.5020370483398438e-05s
INFO | --- Analysis for twc-ieeevis took 108.8520278930664s
Availability | SPARQL endpoint availability check for TWC: Linking Open Government Data took 8.940696716308594e-05s
Availability | VoID file availability check for TWC: Linking Open Government Data took 0.00048041343688964844s
Completeness | Calculation of interlinking completeness for TWC: Linking Open Government Data took 0.28331589698791504s
Reputation | Calculation of the PageRank for TWC: Linking Open Government Data took 0.020941495895385742s
Interlinking | Calculation of Degree of Connection for TWC: Linking Open Government Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for TWC: Linking Open Government Data took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for TWC: Linking Open Government Data took 9.274482727050781e-05s
Believability | Calculation of trust value for TWC: Linking Open Government Data took 1.1205673217773438e-05s
INFO | --- Analysis for twc-logd took 2.820448160171509s
Availability | SPARQL endpoint availability check for twc-opendap took 0.11949706077575684s
Availability | VoID file availability check for twc-opendap took 0.0005848407745361328s
Completeness | Calculation of interlinking completeness for twc-opendap took 0.2831461429595947s
Reputation | Calculation of the PageRank for twc-opendap took 0.020987749099731445s
Interlinking | Calculation of Degree of Connection for twc-opendap took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for twc-opendap took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for twc-opendap took 8.082389831542969e-05s
Believability | Calculation of trust value for twc-opendap took 1.5497207641601562e-05s
INFO | --- Analysis for twc-opendap took 50.82358407974243s
Availability | SPARQL endpoint availability check for typepad took 4.863739013671875e-05s
Availability | VoID file availability check for typepad took 0.0006806850433349609s
Completeness | Calculation of interlinking completeness for typepad took 0.3201925754547119s
Reputation | Calculation of the PageRank for typepad took 0.02091836929321289s
Interlinking | Calculation of Degree of Connection for typepad took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for typepad took 0.0007941722869873047s
Interlinking | Calculation of Clustering coefficient for typepad took 5.793571472167969e-05s
Believability | Calculation of trust value for typepad took 1.4781951904296875e-05s
INFO | --- Analysis for typepad took 3.486056327819824s
Availability | SPARQL endpoint availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.9097390174865723s
Availability | VoID file availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.0006241798400878906s
Completeness | Calculation of interlinking completeness for Linked Data Service der Universitätsbibliothek Mannheim took 0.30822038650512695s
Reputation | Calculation of the PageRank for Linked Data Service der Universitätsbibliothek Mannheim took 0.02104926109313965s
Interlinking | Calculation of Degree of Connection for Linked Data Service der Universitätsbibliothek Mannheim took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Linked Data Service der Universitätsbibliothek Mannheim took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Linked Data Service der Universitätsbibliothek Mannheim took 4.744529724121094e-05s
Believability | Calculation of trust value for Linked Data Service der Universitätsbibliothek Mannheim took 1.5020370483398438e-05s
INFO | --- Analysis for ub-mannheim-linked-data took 4.9188232421875s
Availability | SPARQL endpoint availability check for Uberblic.org took 0.08689522743225098s
Availability | VoID file availability check for Uberblic.org took 0.0003151893615722656s
Completeness | Calculation of interlinking completeness for Uberblic.org took 0.28792643547058105s
Reputation | Calculation of the PageRank for Uberblic.org took 0.020459890365600586s
Interlinking | Calculation of Degree of Connection for Uberblic.org took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Uberblic.org took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Uberblic.org took 0.00011110305786132812s
Believability | Calculation of trust value for Uberblic.org took 1.430511474609375e-05s
INFO | --- Analysis for uberblic took 3.595141649246216s
Availability | SPARQL endpoint availability check for UDante in LiLa took 0.6028876304626465s
Availability | VoID file availability check for UDante in LiLa took 0.0007340908050537109s
Completeness | Calculation of interlinking completeness for UDante in LiLa took 0.3088054656982422s
Reputation | Calculation of the PageRank for UDante in LiLa took 0.022623777389526367s
Interlinking | Calculation of Degree of Connection for UDante in LiLa took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for UDante in LiLa took 0.0009992122650146484s
Interlinking | Calculation of Clustering coefficient for UDante in LiLa took 4.553794860839844e-05s
Believability | Calculation of trust value for UDante in LiLa took 1.4066696166992188e-05s
INFO | --- Analysis for UDante took 4.482053518295288s
Availability | SPARQL endpoint availability check for Unified Foundational Ontology took 1.0016767978668213s
Availability | VoID file availability check for Unified Foundational Ontology took 0.0006308555603027344s
Completeness | Calculation of interlinking completeness for Unified Foundational Ontology took 0.29265260696411133s
Reputation | Calculation of the PageRank for Unified Foundational Ontology took 0.021356582641601562s
Interlinking | Calculation of Degree of Connection for Unified Foundational Ontology took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Unified Foundational Ontology took 0.0009684562683105469s
Interlinking | Calculation of Clustering coefficient for Unified Foundational Ontology took 4.8160552978515625e-05s
Believability | Calculation of trust value for Unified Foundational Ontology took 1.52587890625e-05s
INFO | --- Analysis for ufo took 5.001067638397217s
Availability | SPARQL endpoint availability check for Uganda Disasters took 4.553794860839844e-05s
Availability | VoID file availability check for Uganda Disasters took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for Uganda Disasters took 0.3071770668029785s
Reputation | Calculation of the PageRank for Uganda Disasters took 0.020783424377441406s
Interlinking | Calculation of Degree of Connection for Uganda Disasters took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Uganda Disasters took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Uganda Disasters took 5.316734313964844e-05s
Believability | Calculation of trust value for Uganda Disasters took 1.2874603271484375e-05s
INFO | --- Analysis for Uganda-Disasters-rdf-data_ took 2.806649684906006s
Availability | SPARQL endpoint availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.06967449188232422s
Availability | VoID file availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for UNESCO Institute for Statistics (UIS) Linked Data took 0.3280980587005615s
Reputation | Calculation of the PageRank for UNESCO Institute for Statistics (UIS) Linked Data took 0.020796775817871094s
Interlinking | Calculation of Degree of Connection for UNESCO Institute for Statistics (UIS) Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for UNESCO Institute for Statistics (UIS) Linked Data took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for UNESCO Institute for Statistics (UIS) Linked Data took 0.00010848045349121094s
Believability | Calculation of trust value for UNESCO Institute for Statistics (UIS) Linked Data took 1.4543533325195312e-05s
INFO | --- Analysis for uis-linked-data took 2.7859127521514893s
Availability | SPARQL endpoint availability check for UK Legislation took 5.936622619628906e-05s
Availability | VoID file availability check for UK Legislation took 0.0006291866302490234s
Completeness | Calculation of interlinking completeness for UK Legislation took 0.2805817127227783s
Reputation | Calculation of the PageRank for UK Legislation took 0.02093791961669922s
Interlinking | Calculation of Degree of Connection for UK Legislation took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for UK Legislation took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for UK Legislation took 9.584426879882812e-05s
Believability | Calculation of trust value for UK Legislation took 1.0013580322265625e-05s
INFO | --- Analysis for uk-legislation-api took 4.067249059677124s
Availability | SPARQL endpoint availability check for UK Postcodes took 8.940696716308594e-05s
Availability | VoID file availability check for UK Postcodes took 0.0007781982421875s
Completeness | Calculation of interlinking completeness for UK Postcodes took 0.3460862636566162s
Reputation | Calculation of the PageRank for UK Postcodes took 0.021247386932373047s
Interlinking | Calculation of Degree of Connection for UK Postcodes took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UK Postcodes took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for UK Postcodes took 6.151199340820312e-05s
Believability | Calculation of trust value for UK Postcodes took 1.4543533325195312e-05s
INFO | --- Analysis for uk-postcodes took 22.834097623825073s
Availability | SPARQL endpoint availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 9.608268737792969e-05s
Availability | VoID file availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0005886554718017578s
Completeness | Calculation of interlinking completeness for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.32254600524902344s
Reputation | Calculation of the PageRank for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.020673274993896484s
Interlinking | Calculation of Degree of Connection for UMBEL (Upper Mapping and Binding Exchange Layer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.00013256072998046875s
Believability | Calculation of trust value for UMBEL (Upper Mapping and Binding Exchange Layer) took 1.33514404296875e-05s
INFO | --- Analysis for umbel took 6.775989294052124s
Availability | SPARQL endpoint availability check for German environmental thesaurus UMTHES took 4.482269287109375e-05s
Availability | VoID file availability check for German environmental thesaurus UMTHES took 0.0006167888641357422s
Completeness | Calculation of interlinking completeness for German environmental thesaurus UMTHES took 0.3037729263305664s
Reputation | Calculation of the PageRank for German environmental thesaurus UMTHES took 0.0213015079498291s
Interlinking | Calculation of Degree of Connection for German environmental thesaurus UMTHES took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for German environmental thesaurus UMTHES took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for German environmental thesaurus UMTHES took 4.9591064453125e-05s
Believability | Calculation of trust value for German environmental thesaurus UMTHES took 1.0013580322265625e-05s
INFO | --- Analysis for umthes took 3.7533438205718994s
Availability | SPARQL endpoint availability check for UN Hazardous Materials Numbers took 1.883422613143921s
Availability | VoID file availability check for UN Hazardous Materials Numbers took 0.0007836818695068359s
Completeness | Calculation of interlinking completeness for UN Hazardous Materials Numbers took 0.29785871505737305s
Reputation | Calculation of the PageRank for UN Hazardous Materials Numbers took 0.0212399959564209s
Interlinking | Calculation of Degree of Connection for UN Hazardous Materials Numbers took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for UN Hazardous Materials Numbers took 0.0012679100036621094s
Interlinking | Calculation of Clustering coefficient for UN Hazardous Materials Numbers took 4.315376281738281e-05s
Believability | Calculation of trust value for UN Hazardous Materials Numbers took 1.0251998901367188e-05s
INFO | --- Analysis for un-hazardous-numbers took 11.638611555099487s
Availability | SPARQL endpoint availability check for UniProt took 4.793441534042358s
Availability | VoID file availability check for UniProt took 0.0006711483001708984s
Extra | Recovery of all triples for UniProt took 22.938923597335815s
Performance | Total latancy measurement for UniProt took 9.859017610549927s
Amount of data | Number of triples check for UniProt took 1.1018621921539307s
Interoperability | New terms check for UniProt took 1.9315941333770752s
Versatility | Languages check for UniProt took 2.0521159172058105s
Interpretability | Number of blank nodes check for UniProt took 3.7557361125946045s
Interpretability | RDF structures check for UniProt took 1.935030460357666s
Versatility | Serialization formats check for UniProt took 2.751150131225586s
Availability | RDF dump link check for UniProt took 0.4072723388671875s
License | MR license check for UniProt took 1.4983975887298584s
License | HR license check for UniProt took 300.1596462726593s
Amount of data | Number of property check for UniProt took 0.10484647750854492s
Understandability | Number of label check for UniProt took 55.38834500312805s
Understandability | URI regex check for UniProt took 1.3152179718017578s
Understandability | Vocabs check for UniProt took 1.4970347881317139s
Verifiability | Authors check for UniProt took 1.7366917133331299s
Verifiability | Publishers check for UniProt took 1.6829633712768555s
Performance | Throughput check for UniProt took 44.53509283065796s
Amount of data | Check the number of entities for UniProt took 7.295608520507812e-05s
Verifiability | Contribs. check for UniProt took 1.1151549816131592s
Interlinking | sameAs chians check for UniProt took 0.8626339435577393s
Interlinking | skos check for UniProt took 2.014347553253174s
Interlinking | skos check for UniProt took 0.08761811256408691s
Timeliness | dataset update frequency check for UniProt took 1.8340692520141602s
Currency | Creation date check for UniProt took 2.966735363006592s
Currency | Modification date check for UniProt took 2.077146530151367s
Rep.Conc. | URIs length for UniProt took 146.8341817855835s
Interoperability | New vocabularies check for UniProt took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for UniProt took 0.7557797431945801s
Accuracy | Check Functional Property for UniProt took 0.6589572429656982s
Accuracy | Check Inverse Functional Property for UniProt took 0.7161374092102051s
Accuracy | Check Empty annotation labels for UniProt took 23.443201541900635s
Accuracy | Check White space in annotation for UniProt took 2.5463292598724365s
Accuracy | Check Datatype consistency for UniProt took 7.5590949058532715s
Consistency | Disjoint class check for UniProt took 0.6629440784454346s
Consistency | Check Misplaced properties for UniProt took 2.404144763946533s
Consistency | Check Ontology hijacking for UniProt took 8.668762922286987s
Consistency | Check Invalid usage of undefined classes for UniProt took 25400.881092071533s
Consistency | Check Invalid usage of undefined properties for UniProt took 2.1978366374969482s
Conciseness | Check Extensional conciseness for UniProt took 2.7197980880737305s
Conciseness | Check Intensional conciseness for UniProt took 1.608154535293579s
Security | Sign check for UniProt took 2.586784601211548s
Availability | Check URIs Dereferenciability for UniProt took 4.544049978256226s
Completeness | Calculation of interlinking completeness for UniProt took 0.8096389770507812s
Reputation | Calculation of the PageRank for UniProt took 0.022871971130371094s
Interlinking | Calculation of Degree of Connection for UniProt took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for UniProt took 4.9114227294921875e-05s
Interoperability | Check the re-using of existing vocabs for UniProt took 1.9073486328125e-06s
Believability | Calculation of trust value for UniProt took 1.3828277587890625e-05s
INFO | --- Analysis for UniProt took 26529.5180413723s
Availability | SPARQL endpoint availability check for UniProt took 4.685192346572876s
Availability | VoID file availability check for UniProt took 0.000621795654296875s
Extra | Recovery of all triples for UniProt took 20.573553800582886s
Performance | Total latancy measurement for UniProt took 11.917884826660156s
Amount of data | Number of triples check for UniProt took 1.311302661895752s
Versatility | Languages check for UniProt took 3.011096715927124s
Interpretability | Number of blank nodes check for UniProt took 4.580472469329834s
Security | Check HTTPS for UniProt took 0.18797993659973145s
Interpretability | RDF structures check for UniProt took 0.17763543128967285s
Versatility | Serialization formats check for UniProt took 0.2004256248474121s
Availability | RDF dump link check for UniProt took 0.2179272174835205s
License | MR license check for UniProt took 0.19937467575073242s
License | HR license check for UniProt took 0.20532703399658203s
Amount of data | Number of property check for UniProt took 0.17843890190124512s
Understandability | Number of label check for UniProt took 0.3584461212158203s
Understandability | URI regex check for UniProt took 0.6851058006286621s
Understandability | Vocabs check for UniProt took 0.1788032054901123s
Verifiability | Authors check for UniProt took 0.16988706588745117s
Verifiability | Publishers check for UniProt took 0.1678462028503418s
Performance | Throughput check for UniProt took 50.20976424217224s
Amount of data | Check the number of entities for UniProt took 0.0001327991485595703s
Verifiability | Contribs. check for UniProt took 0.24562406539916992s
Interlinking | sameAs chians check for UniProt took 0.18062806129455566s
Interlinking | skos check for UniProt took 0.1848151683807373s
Interlinking | skos check for UniProt took 0.1527726650238037s
Timeliness | dataset update frequency check for UniProt took 0.17409658432006836s
Currency | Creation date check for UniProt took 0.3556337356567383s
Currency | Modification date check for UniProt took 0.3760700225830078s
Rep.Conc. | URIs length for UniProt took 186.96260905265808s
Interoperability | New vocabularies check for UniProt took 2.384185791015625e-07s
Consistency | Deprecated classes/propertiers check for UniProt took 0.16569232940673828s
Accuracy | Check Datatype consistency for UniProt took 7.552663564682007s
Consistency | Disjoint class check for UniProt took 0.18675661087036133s
Consistency | Check Ontology hijacking for UniProt took 0.18610525131225586s
Consistency | Check Invalid usage of undefined properties for UniProt took 2.4376564025878906s
Conciseness | Check Extensional conciseness for UniProt took 2.75508189201355s
Security | Sign check for UniProt took 0.1639871597290039s
Availability | Check URIs Dereferenciability for UniProt took 4.092021226882935s
Completeness | Calculation of interlinking completeness for UniProt took 0.4438180923461914s
Reputation | Calculation of the PageRank for UniProt took 0.021073102951049805s
Interlinking | Calculation of Degree of Connection for UniProt took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for UniProt took 6.532669067382812e-05s
Interoperability | Check the re-using of existing vocabs for UniProt took 7.152557373046875e-07s
Believability | Calculation of trust value for UniProt took 1.4066696166992188e-05s
INFO | --- Analysis for uniprot took 859.4777340888977s
Availability | SPARQL endpoint availability check for uniprot-metadata took 0.00030231475830078125s
Availability | VoID file availability check for uniprot-metadata took 0.0006594657897949219s
Completeness | Calculation of interlinking completeness for uniprot-metadata took 0.3010711669921875s
Reputation | Calculation of the PageRank for uniprot-metadata took 0.021230220794677734s
Interlinking | Calculation of Degree of Connection for uniprot-metadata took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for uniprot-metadata took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for uniprot-metadata took 6.794929504394531e-05s
Believability | Calculation of trust value for uniprot-metadata took 1.4066696166992188e-05s
INFO | --- Analysis for uniprot-metadata took 4.008976697921753s
Availability | SPARQL endpoint availability check for UniProtKB took 4.904642581939697s
Availability | VoID file availability check for UniProtKB took 0.0005819797515869141s
Extra | Recovery of all triples for UniProtKB took 18.42826008796692s
Performance | Total latancy measurement for UniProtKB took 8.477440357208252s
Amount of data | Number of triples check for UniProtKB took 0.8346850872039795s
Interoperability | New terms check for UniProtKB took 2.162393569946289s
Versatility | Languages check for UniProtKB took 2.41638445854187s
Interpretability | Number of blank nodes check for UniProtKB took 5.602253675460815s
Interpretability | RDF structures check for UniProtKB took 3.084726333618164s
Versatility | Serialization formats check for UniProtKB took 3.625459909439087s
Availability | RDF dump link check for UniProtKB took 0.4588475227355957s
License | MR license check for UniProtKB took 1.744943618774414s
License | HR license check for UniProtKB took 300.12572383880615s
Amount of data | Number of property check for UniProtKB took 0.1478133201599121s
Understandability | Number of label check for UniProtKB took 63.1476948261261s
Understandability | URI regex check for UniProtKB took 1.334066390991211s
Understandability | Vocabs check for UniProtKB took 1.6060967445373535s
Verifiability | Authors check for UniProtKB took 2.4704513549804688s
Verifiability | Publishers check for UniProtKB took 2.121990919113159s
Performance | Throughput check for UniProtKB took 50.555899143218994s
Amount of data | Check the number of entities for UniProtKB took 7.009506225585938e-05s
Verifiability | Contribs. check for UniProtKB took 1.1883456707000732s
Interlinking | sameAs chians check for UniProtKB took 0.7096571922302246s
Interlinking | skos check for UniProtKB took 1.5464744567871094s
Interlinking | skos check for UniProtKB took 0.08811616897583008s
Timeliness | dataset update frequency check for UniProtKB took 2.4175426959991455s
Currency | Creation date check for UniProtKB took 2.6638987064361572s
Currency | Modification date check for UniProtKB took 2.4409077167510986s
Rep.Conc. | URIs length for UniProtKB took 165.99933290481567s
Interoperability | New vocabularies check for UniProtKB took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for UniProtKB took 0.5173532962799072s
Accuracy | Check Functional Property for UniProtKB took 0.6501169204711914s
Accuracy | Check Inverse Functional Property for UniProtKB took 0.7389445304870605s
Accuracy | Check Empty annotation labels for UniProtKB took 17.189030647277832s
Accuracy | Check White space in annotation for UniProtKB took 2.550272226333618s
Accuracy | Check Datatype consistency for UniProtKB took 7.5997841358184814s
Consistency | Disjoint class check for UniProtKB took 0.7772696018218994s
Consistency | Check Misplaced properties for UniProtKB took 2.9371089935302734s
Consistency | Check Ontology hijacking for UniProtKB took 10.6484854221344s
Consistency | Check Invalid usage of undefined classes for UniProtKB took 25577.873242139816s
Consistency | Check Invalid usage of undefined properties for UniProtKB took 2.258000373840332s
Conciseness | Check Extensional conciseness for UniProtKB took 2.765509605407715s
Conciseness | Check Intensional conciseness for UniProtKB took 0.8330674171447754s
Security | Sign check for UniProtKB took 1.7665355205535889s
Availability | Check URIs Dereferenciability for UniProtKB took 4.543029069900513s
Completeness | Calculation of interlinking completeness for UniProtKB took 0.8745312690734863s
Reputation | Calculation of the PageRank for UniProtKB took 0.021814823150634766s
Interlinking | Calculation of Degree of Connection for UniProtKB took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for UniProtKB took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for UniProtKB took 8.106231689453125e-05s
Interoperability | Check the re-using of existing vocabs for UniProtKB took 2.384185791015625e-06s
Believability | Calculation of trust value for UniProtKB took 1.430511474609375e-05s
INFO | --- Analysis for uniprotkb took 26802.638617277145s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek took 9.179115295410156e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek took 0.0007753372192382812s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek took 0.31775808334350586s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek took 0.020991086959838867s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek took 4.935264587402344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek took 1.4543533325195312e-05s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek took 13.755911350250244s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 4.5299530029296875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0008220672607421875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.29203009605407715s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.020767688751220703s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek-PROIEL took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0008337497711181641s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek-PROIEL took 5.173683166503906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek-PROIEL took 1.4781951904296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek-proiel took 4.2301270961761475s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Arabic took 9.632110595703125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Arabic took 0.0007729530334472656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Arabic took 0.3000171184539795s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Arabic took 0.020876407623291016s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Arabic took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Arabic took 0.0007894039154052734s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Arabic took 4.4345855712890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Arabic took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-arabic took 13.572468519210815s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Basque took 8.940696716308594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Basque took 0.0008625984191894531s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Basque took 0.2927968502044678s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Basque took 0.021287918090820312s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Basque took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Basque took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Basque took 4.8160552978515625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Basque took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-basque took 13.540518760681152s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Bulgarian took 9.822845458984375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Bulgarian took 0.0007281303405761719s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Bulgarian took 0.31398892402648926s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Bulgarian took 0.020627975463867188s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Bulgarian took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Bulgarian took 0.0007936954498291016s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Bulgarian took 4.744529724121094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Bulgarian took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-bulgarian took 13.407392740249634s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Catalan took 4.6253204345703125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Catalan took 0.0006992816925048828s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Catalan took 0.2917006015777588s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Catalan took 0.021151065826416016s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Catalan took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Catalan took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Catalan took 4.8160552978515625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Catalan took 1.1205673217773438e-05s
INFO | --- Analysis for universal-dependencies-treebank-catalan took 13.45433497428894s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Chinese took 4.458427429199219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Chinese took 0.0006759166717529297s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Chinese took 0.2905006408691406s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Chinese took 0.022549152374267578s
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.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Chinese took 4.553794860839844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Chinese took 1.4066696166992188e-05s
INFO | --- Analysis for universal-dependencies-treebank-chinese took 4.29165244102478s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Coptic took 4.57763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Coptic took 0.0007405281066894531s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Coptic took 0.34258556365966797s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Coptic took 0.02161693572998047s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Coptic took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Coptic took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Coptic took 4.76837158203125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Coptic took 1.3828277587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-coptic took 13.386855363845825s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Croatian took 9.751319885253906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Croatian took 0.0008604526519775391s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Croatian took 0.42554807662963867s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Croatian took 0.021335124969482422s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Croatian took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Croatian took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Croatian took 4.935264587402344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Croatian took 1.4543533325195312e-05s
INFO | --- Analysis for universal-dependencies-treebank-croatian took 13.575645446777344s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech took 9.179115295410156e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech took 0.0007627010345458984s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech took 0.3026094436645508s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech took 0.02087712287902832s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech took 4.506111145019531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech took 1.430511474609375e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech took 13.549102067947388s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CAC took 4.482269287109375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CAC took 0.0008413791656494141s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CAC took 0.3132643699645996s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CAC took 0.02097940444946289s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CAC took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CAC took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CAC took 4.4345855712890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CAC took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech-cac took 13.276898384094238s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CLTT took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CLTT took 0.0007305145263671875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CLTT took 0.28302931785583496s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CLTT took 0.021073579788208008s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CLTT took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CLTT took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CLTT took 4.5299530029296875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CLTT took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech-cltt took 13.34449315071106s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Danish took 9.226799011230469e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Danish took 0.0006966590881347656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Danish took 0.29551124572753906s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Danish took 0.020960569381713867s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Danish took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Danish took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Danish took 4.57763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Danish took 1.430511474609375e-05s
INFO | --- Analysis for universal-dependencies-treebank-danish took 4.250607013702393s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch took 4.4345855712890625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch took 0.0008759498596191406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch took 0.30318212509155273s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch took 0.02088475227355957s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch took 0.0008070468902587891s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch took 4.792213439941406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch took 1.430511474609375e-05s
INFO | --- Analysis for universal-dependencies-treebank-dutch took 13.50654649734497s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch-LassySmall took 8.988380432128906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch-LassySmall took 0.0006959438323974609s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch-LassySmall took 0.2813103199005127s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch-LassySmall took 0.021614789962768555s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch-LassySmall took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch-LassySmall took 0.0008089542388916016s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch-LassySmall took 5.078315734863281e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch-LassySmall took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-dutch-lassysmall took 13.385375022888184s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English took 0.0007531642913818359s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English took 0.2918863296508789s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English took 0.02108311653137207s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English took 4.4345855712890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-english took 13.445193767547607s
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.0007426738739013672s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-ESL took 0.30340051651000977s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-ESL took 0.022199153900146484s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-ESL took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-ESL took 0.0010607242584228516s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-ESL took 5.4836273193359375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-ESL took 1.4781951904296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-english-esl took 13.343404054641724s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-LinES took 9.250640869140625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-LinES took 0.0008044242858886719s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-LinES took 0.31125450134277344s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-LinES took 0.022172927856445312s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-LinES took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-LinES took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-LinES took 4.8160552978515625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-LinES took 1.430511474609375e-05s
INFO | --- Analysis for universal-dependencies-treebank-english-lines took 13.237034797668457s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Estonian took 9.202957153320312e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Estonian took 0.0007238388061523438s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Estonian took 0.27804017066955566s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Estonian took 0.022857666015625s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Estonian took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Estonian took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Estonian took 4.506111145019531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Estonian took 1.4066696166992188e-05s
INFO | --- Analysis for universal-dependencies-treebank-estonian took 13.434144496917725s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish took 6.532669067382812e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish took 0.0006728172302246094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish took 0.27759504318237305s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish took 0.020887136459350586s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish took 4.410743713378906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish took 1.4781951904296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-finnish took 4.129635334014893s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish-FTB took 9.250640869140625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish-FTB took 0.0007164478302001953s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish-FTB took 0.2802441120147705s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish-FTB took 0.022518396377563477s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish-FTB took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish-FTB took 0.001129150390625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish-FTB took 5.650520324707031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish-FTB took 1.4781951904296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-finnish-ftb took 13.258086919784546s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank French took 4.57763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank French took 0.0007212162017822266s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank French took 0.2916727066040039s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank French took 0.02303767204284668s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank French took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank French took 0.0007834434509277344s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank French took 4.792213439941406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank French took 1.4781951904296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-french took 13.43151068687439s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician took 9.250640869140625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician took 0.0007774829864501953s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician took 0.3333292007446289s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician took 0.021024227142333984s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician took 4.267692565917969e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician took 1.430511474609375e-05s
INFO | --- Analysis for universal-dependencies-treebank-galician took 13.721763610839844s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician-TreeGal took 9.036064147949219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician-TreeGal took 0.0006430149078369141s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician-TreeGal took 0.2916421890258789s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician-TreeGal took 0.02148127555847168s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician-TreeGal took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician-TreeGal took 0.0007956027984619141s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician-TreeGal took 4.57763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician-TreeGal took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-galician-treegal took 3.9298512935638428s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank German took 9.1552734375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank German took 0.0006840229034423828s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank German took 0.3290262222290039s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank German took 0.020917654037475586s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank German took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank German took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank German took 4.601478576660156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank German took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-german took 4.225973129272461s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Gothic took 4.5299530029296875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Gothic took 0.0007498264312744141s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Gothic took 0.3039073944091797s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Gothic took 0.020741939544677734s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Gothic took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Gothic took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Gothic took 4.482269287109375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Gothic took 1.3589859008789062e-05s
INFO | --- Analysis for universal-dependencies-treebank-gothic took 4.165751934051514s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Greek took 8.797645568847656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Greek took 0.0006203651428222656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Greek took 0.2858245372772217s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Greek took 0.02079463005065918s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Greek took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Greek took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Greek took 4.3392181396484375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Greek took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-greek took 4.119580268859863s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hebrew took 4.57763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hebrew took 0.0007042884826660156s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hebrew took 0.31084561347961426s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hebrew took 0.020899295806884766s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hebrew took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hebrew took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hebrew took 4.482269287109375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hebrew took 1.3828277587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-hebrew took 13.537265539169312s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hindi took 0.00010561943054199219s
Availability | VoID file availability check for Universal Dependencies Treebank Hindi took 0.0007207393646240234s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hindi took 0.3175027370452881s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hindi took 0.02107834815979004s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hindi took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hindi took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hindi took 4.410743713378906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hindi took 1.3589859008789062e-05s
INFO | --- Analysis for universal-dependencies-treebank-hindi took 13.54550290107727s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hungarian took 8.869171142578125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hungarian took 0.0006623268127441406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hungarian took 0.29195380210876465s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hungarian took 0.020814895629882812s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hungarian took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hungarian took 0.0007951259613037109s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hungarian took 4.410743713378906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hungarian took 1.3828277587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-hungarian took 4.267727375030518s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Indonesian took 4.506111145019531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Indonesian took 0.0008821487426757812s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Indonesian took 0.3060293197631836s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Indonesian took 0.02274155616760254s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Indonesian took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Indonesian took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Indonesian took 5.316734313964844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Indonesian took 1.3828277587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-indonesian took 13.347258806228638s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Irish took 4.506111145019531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Irish took 0.0006134510040283203s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Irish took 0.29184675216674805s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Irish took 0.021105289459228516s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Irish took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Irish took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Irish took 4.38690185546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Irish took 1.4543533325195312e-05s
INFO | --- Analysis for universal-dependencies-treebank-irish took 4.082862854003906s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Italian took 4.506111145019531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Italian took 0.0007097721099853516s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Italian took 0.2914314270019531s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Italian took 0.020782470703125s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Italian took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Italian took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Italian took 4.553794860839844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Italian took 9.059906005859375e-06s
INFO | --- Analysis for universal-dependencies-treebank-italian took 13.538735151290894s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese took 4.5299530029296875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese took 0.0007193088531494141s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese took 0.33289122581481934s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese took 0.023119688034057617s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese took 4.673004150390625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese took 1.4543533325195312e-05s
INFO | --- Analysis for universal-dependencies-treebank-japanese took 13.526590585708618s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese-KTC took 9.489059448242188e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese-KTC took 0.00080108642578125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese-KTC took 0.3314249515533447s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese-KTC took 0.021226167678833008s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese-KTC took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese-KTC took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese-KTC took 4.220008850097656e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese-KTC took 1.5020370483398438e-05s
INFO | --- Analysis for universal-dependencies-treebank-japanese-ktc took 4.0195088386535645s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Kazakh took 9.226799011230469e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Kazakh took 0.0007617473602294922s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Kazakh took 0.30246734619140625s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Kazakh took 0.02089977264404297s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Kazakh took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Kazakh took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Kazakh took 4.8160552978515625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Kazakh took 1.5020370483398438e-05s
INFO | --- Analysis for universal-dependencies-treebank-kazakh took 13.451696395874023s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin took 0.00011730194091796875s
Availability | VoID file availability check for Universal Dependencies Treebank Latin took 0.0006952285766601562s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin took 0.28046464920043945s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin took 0.021502017974853516s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin took 0.0010499954223632812s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin took 5.340576171875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin took 1.4543533325195312e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin took 4.08340048789978s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-ITTB took 4.601478576660156e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-ITTB took 0.0007176399230957031s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-ITTB took 0.4123215675354004s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-ITTB took 0.021529674530029297s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-ITTB took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-ITTB took 0.000797271728515625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-ITTB took 4.673004150390625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-ITTB took 1.3828277587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin-ittb took 13.44360613822937s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-PROIEL took 0.0001621246337890625s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-PROIEL took 0.0007476806640625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-PROIEL took 0.2990577220916748s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-PROIEL took 0.02108001708984375s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-PROIEL took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-PROIEL took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-PROIEL took 5.054473876953125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-PROIEL took 1.3828277587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin-proiel took 13.413703680038452s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latvian took 4.744529724121094e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latvian took 0.0007607936859130859s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latvian took 0.30644941329956055s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latvian took 0.02085399627685547s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latvian took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latvian took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latvian took 4.410743713378906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latvian took 1.3828277587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-latvian took 13.440728425979614s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Norwegian took 9.489059448242188e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Norwegian took 0.0007452964782714844s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Norwegian took 0.32280492782592773s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Norwegian took 0.020793676376342773s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Norwegian took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Norwegian took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Norwegian took 4.3392181396484375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Norwegian took 1.5974044799804688e-05s
INFO | --- Analysis for universal-dependencies-treebank-norwegian took 13.359935522079468s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Old_Church_Slavonic took 5.91278076171875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Old_Church_Slavonic took 0.0009074211120605469s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Old_Church_Slavonic took 0.3338906764984131s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Old_Church_Slavonic took 0.02100372314453125s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Old_Church_Slavonic took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Old_Church_Slavonic took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Old_Church_Slavonic took 4.363059997558594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Old_Church_Slavonic took 1.52587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-old-church-slavonic took 13.456296682357788s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Persian took 0.00010466575622558594s
Availability | VoID file availability check for Universal Dependencies Treebank Persian took 0.0006871223449707031s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Persian took 0.2796018123626709s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Persian took 0.021155595779418945s
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.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Persian took 4.3392181396484375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Persian took 1.4781951904296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-persian took 4.361876010894775s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Polish took 9.012222290039062e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Polish took 0.000774383544921875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Polish took 0.2841837406158447s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Polish took 0.020964384078979492s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Polish took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Polish took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Polish took 5.1021575927734375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Polish took 1.5497207641601562e-05s
INFO | --- Analysis for universal-dependencies-treebank-polish took 13.585971593856812s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese took 4.76837158203125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese took 0.0007462501525878906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese took 0.27327990531921387s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese took 0.020658493041992188s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese took 4.696846008300781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-portuguese took 13.105446815490723s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-Bosque took 4.744529724121094e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-Bosque took 0.0007164478302001953s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-Bosque took 0.28142690658569336s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-Bosque took 0.020775794982910156s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-Bosque took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-Bosque took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-Bosque took 4.57763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-Bosque took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-bosque took 13.29475712776184s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-BR took 9.202957153320312e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-BR took 0.0008034706115722656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-BR took 0.2924923896789551s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-BR took 0.020819664001464844s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-BR took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-BR took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-BR took 4.9591064453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-BR took 1.5735626220703125e-05s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-br took 13.394883155822754s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 9.226799011230469e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0007779598236083984s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.27602529525756836s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.020647287368774414s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 4.363059997558594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-romanian took 13.431987524032593s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian took 4.839897155761719e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian took 0.0007162094116210938s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian took 0.33277201652526855s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian took 0.02112603187561035s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian took 4.8160552978515625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian took 9.5367431640625e-06s
INFO | --- Analysis for universal-dependencies-treebank-russian took 13.431981563568115s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian-SynTagRus took 5.4836273193359375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian-SynTagRus took 0.0007112026214599609s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian-SynTagRus took 0.2885451316833496s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian-SynTagRus took 0.02199077606201172s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian-SynTagRus took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian-SynTagRus took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian-SynTagRus took 4.363059997558594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian-SynTagRus took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-russian-syntagrus took 4.071684837341309s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Sanskrit took 9.250640869140625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Sanskrit took 0.0007703304290771484s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Sanskrit took 0.31073999404907227s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Sanskrit took 0.02118706703186035s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Sanskrit took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Sanskrit took 0.0008389949798583984s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Sanskrit took 5.364418029785156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Sanskrit took 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-sanskrit took 13.428323984146118s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovak took 8.988380432128906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovak took 0.0008211135864257812s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovak took 0.30415964126586914s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovak took 0.021606922149658203s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovak took 2.6941299438476562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovak took 0.0011751651763916016s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovak took 6.4849853515625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovak took 1.52587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-slovak took 13.551403045654297s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian took 4.57763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian took 0.0007183551788330078s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian took 0.30133581161499023s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian took 0.021093368530273438s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian took 5.030632019042969e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-slovenian took 13.55290961265564s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian-SST took 9.5367431640625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian-SST took 0.0007033348083496094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian-SST took 0.3368802070617676s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian-SST took 0.02106332778930664s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian-SST took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian-SST took 0.0007915496826171875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian-SST took 5.3882598876953125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian-SST took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-slovenian-sst took 13.479690551757812s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish took 0.00014328956604003906s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish took 0.0008685588836669922s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish took 0.29041624069213867s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish took 0.020621299743652344s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish took 4.2438507080078125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish took 1.71661376953125e-05s
INFO | --- Analysis for universal-dependencies-treebank-spanish took 13.424808263778687s
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.0007150173187255859s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish-AnCora took 0.3422112464904785s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish-AnCora took 0.02091813087463379s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish-AnCora took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish-AnCora took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish-AnCora took 4.410743713378906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish-AnCora took 1.430511474609375e-05s
INFO | --- Analysis for universal-dependencies-treebank-spanish-ancora took 13.410820007324219s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish took 9.202957153320312e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish took 0.0006783008575439453s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish took 0.2760281562805176s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish took 0.021058320999145508s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish took 4.363059997558594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish took 1.4066696166992188e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish took 4.361487150192261s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish-LinES took 6.103515625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish-LinES took 0.0006749629974365234s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish-LinES took 0.31984877586364746s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish-LinES took 0.021058082580566406s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish-LinES took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish-LinES took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish-LinES took 4.5299530029296875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish-LinES took 1.4066696166992188e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish-lines took 3.9193146228790283s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish_Sign_Language took 9.393692016601562e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish_Sign_Language took 0.0007457733154296875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish_Sign_Language took 0.2909085750579834s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish_Sign_Language took 0.02092456817626953s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish_Sign_Language took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish_Sign_Language took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish_Sign_Language took 4.9591064453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish_Sign_Language took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish-sign-language took 13.466763734817505s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Tamil took 9.179115295410156e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Tamil took 0.0008151531219482422s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Tamil took 0.2832975387573242s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Tamil took 0.020891666412353516s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Tamil took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Tamil took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Tamil took 4.458427429199219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Tamil took 1.430511474609375e-05s
INFO | --- Analysis for universal-dependencies-treebank-tamil took 13.373981952667236s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Turkish took 4.601478576660156e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Turkish took 0.0007276535034179688s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Turkish took 0.34029626846313477s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Turkish took 0.02202463150024414s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Turkish took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Turkish took 0.0008244514465332031s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Turkish took 4.744529724121094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Turkish took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-turkish took 13.575791120529175s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ukrainian took 9.846687316894531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ukrainian took 0.0008413791656494141s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ukrainian took 0.30704331398010254s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ukrainian took 0.021306753158569336s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ukrainian took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ukrainian took 0.0008418560028076172s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ukrainian took 5.626678466796875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ukrainian took 9.059906005859375e-06s
INFO | --- Analysis for universal-dependencies-treebank-ukrainian took 13.559412002563477s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Uyghur took 9.036064147949219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Uyghur took 0.0007114410400390625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Uyghur took 0.3753201961517334s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Uyghur took 0.020755290985107422s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Uyghur took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Uyghur took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Uyghur took 4.38690185546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Uyghur took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-uyghur took 13.656059741973877s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Vietnamese took 9.179115295410156e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Vietnamese took 0.0007429122924804688s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Vietnamese took 0.29343461990356445s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Vietnamese took 0.021261215209960938s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Vietnamese took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Vietnamese took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Vietnamese took 4.57763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Vietnamese took 1.4543533325195312e-05s
INFO | --- Analysis for universal-dependencies-treebank-vietnamese took 13.402028799057007s
Availability | SPARQL endpoint availability check for Universidad de Cuenca - LinkedData took 5.507469177246094e-05s
Availability | VoID file availability check for Universidad de Cuenca - LinkedData took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for Universidad de Cuenca - LinkedData took 0.30332040786743164s
Reputation | Calculation of the PageRank for Universidad de Cuenca - LinkedData took 0.0209195613861084s
Interlinking | Calculation of Degree of Connection for Universidad de Cuenca - LinkedData took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universidad de Cuenca - LinkedData took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Universidad de Cuenca - LinkedData took 7.152557373046875e-05s
Believability | Calculation of trust value for Universidad de Cuenca - LinkedData took 1.3589859008789062e-05s
INFO | --- Analysis for universidad-de-cuenca-linkeddata took 6.713369846343994s
Availability | SPARQL endpoint availability check for University of Plymouth Reading Lists took 0.00010395050048828125s
Availability | VoID file availability check for University of Plymouth Reading Lists took 0.00072479248046875s
Completeness | Calculation of interlinking completeness for University of Plymouth Reading Lists took 0.3228616714477539s
Reputation | Calculation of the PageRank for University of Plymouth Reading Lists took 0.020938396453857422s
Interlinking | Calculation of Degree of Connection for University of Plymouth Reading Lists took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for University of Plymouth Reading Lists took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for University of Plymouth Reading Lists took 5.269050598144531e-05s
Believability | Calculation of trust value for University of Plymouth Reading Lists took 1.52587890625e-05s
INFO | --- Analysis for university-plymouth-reading-lists took 3.351844549179077s
Availability | SPARQL endpoint availability check for University of Sussex Reading Lists took 9.107589721679688e-05s
Availability | VoID file availability check for University of Sussex Reading Lists took 0.0006749629974365234s
Completeness | Calculation of interlinking completeness for University of Sussex Reading Lists took 0.31364917755126953s
Reputation | Calculation of the PageRank for University of Sussex Reading Lists took 0.021393775939941406s
Interlinking | Calculation of Degree of Connection for University of Sussex Reading Lists took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for University of Sussex Reading Lists took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for University of Sussex Reading Lists took 3.790855407714844e-05s
Believability | Calculation of trust value for University of Sussex Reading Lists took 1.4543533325195312e-05s
INFO | --- Analysis for university-sussex-reading-lists took 3.087400436401367s
Availability | SPARQL endpoint availability check for UNODC - Statistics on criminal justice took 8.35539960861206s
Availability | VoID file availability check for UNODC - Statistics on criminal justice took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for UNODC - Statistics on criminal justice took 0.5776503086090088s
Reputation | Calculation of the PageRank for UNODC - Statistics on criminal justice took 0.020871400833129883s
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.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for UNODC - Statistics on criminal justice took 7.724761962890625e-05s
Believability | Calculation of trust value for UNODC - Statistics on criminal justice took 1.4781951904296875e-05s
INFO | --- Analysis for unodc took 20.999903202056885s
Availability | SPARQL endpoint availability check for Super Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Super Ontology took 0.0006887912750244141s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.28965139389038086s
Reputation | Calculation of the PageRank for Super Ontology took 0.021579980850219727s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 9.059906005859375e-05s
Believability | Calculation of trust value for Super Ontology took 1.4781951904296875e-05s
INFO | --- Analysis for upper-ontology took 3.8938260078430176s
Availability | SPARQL endpoint availability check for Sup_Ont: An Upper Ontology took 1.5742394924163818s
Availability | VoID file availability check for Sup_Ont: An Upper Ontology took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for Sup_Ont: An Upper Ontology took 0.2960240840911865s
Reputation | Calculation of the PageRank for Sup_Ont: An Upper Ontology took 0.022764205932617188s
Interlinking | Calculation of Degree of Connection for Sup_Ont: An Upper Ontology took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Sup_Ont: An Upper Ontology took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Sup_Ont: An Upper Ontology took 4.1484832763671875e-05s
Believability | Calculation of trust value for Sup_Ont: An Upper Ontology took 1.52587890625e-05s
INFO | --- Analysis for Upper_Ontology took 5.529499292373657s
Availability | SPARQL endpoint availability check for Urban Atlas dataset took 0.00013375282287597656s
Availability | VoID file availability check for Urban Atlas dataset took 0.0005781650543212891s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset took 0.30451440811157227s
Reputation | Calculation of the PageRank for Urban Atlas dataset took 0.021906137466430664s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset took 3.552436828613281e-05s
Believability | Calculation of trust value for Urban Atlas dataset took 1.3828277587890625e-05s
INFO | --- Analysis for Urban_Atlas_ took 2.752422571182251s
Availability | SPARQL endpoint availability check for Urban Atlas dataset @PSNC took 0.5725595951080322s
Availability | VoID file availability check for Urban Atlas dataset @PSNC took 0.0006649494171142578s
Extra | Recovery of all triples for Urban Atlas dataset @PSNC took 106.47957134246826s
Performance | Total latancy measurement for Urban Atlas dataset @PSNC took 0.9482719898223877s
Amount of data | Number of triples check for Urban Atlas dataset @PSNC took 9.341423749923706s
Interoperability | New terms check for Urban Atlas dataset @PSNC took 14.600485563278198s
Versatility | Languages check for Urban Atlas dataset @PSNC took 300.17758560180664s
Interpretability | Number of blank nodes check for Urban Atlas dataset @PSNC took 2.396754026412964s
Interpretability | RDF structures check for Urban Atlas dataset @PSNC took 0.37650251388549805s
Versatility | Serialization formats check for Urban Atlas dataset @PSNC took 11.90213394165039s
Availability | RDF dump link check for Urban Atlas dataset @PSNC took 0.3374934196472168s
License | MR license check for Urban Atlas dataset @PSNC took 0.8358573913574219s
License | HR license check for Urban Atlas dataset @PSNC took 300.1971309185028s
Amount of data | Number of property check for Urban Atlas dataset @PSNC took 0.21869158744812012s
Understandability | Number of label check for Urban Atlas dataset @PSNC took 3.2073793411254883s
Understandability | URI regex check for Urban Atlas dataset @PSNC took 1.1598758697509766s
Understandability | Vocabs check for Urban Atlas dataset @PSNC took 0.6114373207092285s
Verifiability | Authors check for Urban Atlas dataset @PSNC took 0.20695137977600098s
Verifiability | Publishers check for Urban Atlas dataset @PSNC took 0.2422795295715332s
Performance | Throughput check for Urban Atlas dataset @PSNC took 11.470967531204224s
Amount of data | Check the number of entities for Urban Atlas dataset @PSNC took 7.43865966796875e-05s
Verifiability | Contribs. check for Urban Atlas dataset @PSNC took 0.18673181533813477s
Interlinking | sameAs chians check for Urban Atlas dataset @PSNC took 0.18691635131835938s
Interlinking | skos check for Urban Atlas dataset @PSNC took 0.43009352684020996s
Interlinking | skos check for Urban Atlas dataset @PSNC took 0.42519068717956543s
Timeliness | dataset update frequency check for Urban Atlas dataset @PSNC took 7.017056941986084s
Currency | Creation date check for Urban Atlas dataset @PSNC took 0.5126371383666992s
Currency | Modification date check for Urban Atlas dataset @PSNC took 0.26855945587158203s
Rep.Conc. | URIs length for Urban Atlas dataset @PSNC took 155.35425543785095s
Interoperability | New vocabularies check for Urban Atlas dataset @PSNC took 1.3589859008789062e-05s
Consistency | Deprecated classes/propertiers check for Urban Atlas dataset @PSNC took 0.21883845329284668s
Accuracy | Check Functional Property for Urban Atlas dataset @PSNC took 0.5327441692352295s
Accuracy | Check Inverse Functional Property for Urban Atlas dataset @PSNC took 0.48923802375793457s
Accuracy | Check Empty annotation labels for Urban Atlas dataset @PSNC took 42.76435089111328s
Accuracy | Check White space in annotation for Urban Atlas dataset @PSNC took 2.795692205429077s
Accuracy | Check Datatype consistency for Urban Atlas dataset @PSNC took 2.780163526535034s
Consistency | Disjoint class check for Urban Atlas dataset @PSNC took 0.1982431411743164s
Consistency | Check Misplaced properties for Urban Atlas dataset @PSNC took 86.57438063621521s
Consistency | Misplaced classes for Urban Atlas dataset @PSNC took 8.813257217407227s
Consistency | Check Ontology hijacking for Urban Atlas dataset @PSNC took 34.04947543144226s
Consistency | Check Invalid usage of undefined classes for Urban Atlas dataset @PSNC took 1.5789189338684082s
Consistency | Check Invalid usage of undefined properties for Urban Atlas dataset @PSNC took 87.33584403991699s
Conciseness | Check Extensional conciseness for Urban Atlas dataset @PSNC took 2.791675090789795s
Conciseness | Check Intensional conciseness for Urban Atlas dataset @PSNC took 0.536339282989502s
Security | Sign check for Urban Atlas dataset @PSNC took 1.4942290782928467s
Availability | Check URIs Dereferenciability for Urban Atlas dataset @PSNC took 10.349933385848999s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset @PSNC took 0.517960786819458s
Reputation | Calculation of the PageRank for Urban Atlas dataset @PSNC took 0.02332925796508789s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset @PSNC took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset @PSNC took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset @PSNC took 4.696846008300781e-05s
Interoperability | Check the re-using of existing vocabs for Urban Atlas dataset @PSNC took 2.6226043701171875e-06s
Believability | Calculation of trust value for Urban Atlas dataset @PSNC took 1.3113021850585938e-05s
INFO | --- Analysis for Urban_Atlas_Dataset took 2280.9998691082s
Availability | SPARQL endpoint availability check for URIBurner took 0.9727048873901367s
Availability | VoID file availability check for URIBurner took 0.0007436275482177734s
Extra | Recovery of all triples for URIBurner took 120.70981693267822s
Performance | Total latancy measurement for URIBurner took 2.7917706966400146s
Amount of data | Number of triples check for URIBurner took 3.4395337104797363s
Interoperability | New terms check for URIBurner took 37.89003849029541s
Versatility | Languages check for URIBurner took 123.82702279090881s
Interpretability | Number of blank nodes check for URIBurner took 1.8867106437683105s
Security | Check HTTPS for URIBurner took 0.9829258918762207s
Interpretability | RDF structures check for URIBurner took 2.347808599472046s
Versatility | Serialization formats check for URIBurner took 6.535399675369263s
Availability | RDF dump link check for URIBurner took 46.08129811286926s
License | MR license check for URIBurner took 1.3357183933258057s
License | HR license check for URIBurner took 123.07424521446228s
Amount of data | Number of property check for URIBurner took 0.8187479972839355s
Understandability | Number of label check for URIBurner took 3.5604746341705322s
Understandability | URI regex check for URIBurner took 1.3675827980041504s
Understandability | Vocabs check for URIBurner took 0.6349203586578369s
Verifiability | Authors check for URIBurner took 0.7924144268035889s
Verifiability | Publishers check for URIBurner took 0.6651208400726318s
Performance | Throughput check for URIBurner took 11.110869407653809s
Amount of data | Check the number of entities for URIBurner took 9.417533874511719e-05s
Verifiability | Contribs. check for URIBurner took 0.6554660797119141s
Interlinking | sameAs chians check for URIBurner took 1.3204009532928467s
Interlinking | skos check for URIBurner took 0.7872457504272461s
Interlinking | skos check for URIBurner took 0.5498080253601074s
Timeliness | dataset update frequency check for URIBurner took 1.1011438369750977s
Currency | Creation date check for URIBurner took 3.2473461627960205s
Currency | Modification date check for URIBurner took 0.7382504940032959s
Rep.Conc. | URIs length for URIBurner took 113.26748251914978s
Interoperability | New vocabularies check for URIBurner took 118.68061828613281s
Consistency | Deprecated classes/propertiers check for URIBurner took 0.6466951370239258s
Accuracy | Check Functional Property for URIBurner took 0.6058921813964844s
Accuracy | Check Inverse Functional Property for URIBurner took 0.5844790935516357s
Accuracy | Check Empty annotation labels for URIBurner took 56.141045570373535s
Accuracy | Check White space in annotation for URIBurner took 0.1919574737548828s
Consistency | Disjoint class check for URIBurner took 0.6782383918762207s
Consistency | Check Misplaced properties for URIBurner took 446.92945170402527s
Consistency | Misplaced classes for URIBurner took 57.66384434700012s
Consistency | Check Ontology hijacking for URIBurner took 57.52873992919922s
Consistency | Check Invalid usage of undefined properties for URIBurner took 59.10580348968506s
Conciseness | Check Extensional conciseness for URIBurner took 0.0002052783966064453s
Conciseness | Check Intensional conciseness for URIBurner took 109.91194152832031s
Security | Sign check for URIBurner took 0.7906999588012695s
Completeness | Calculation of interlinking completeness for URIBurner took 0.7262518405914307s
Reputation | Calculation of the PageRank for URIBurner took 0.021620988845825195s
Interlinking | Calculation of Degree of Connection for URIBurner took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for URIBurner took 0.0008103847503662109s
Interlinking | Calculation of Clustering coefficient for URIBurner took 0.00010538101196289062s
Interoperability | Check the re-using of existing vocabs for URIBurner took 119.28427195549011s
Believability | Calculation of trust value for URIBurner took 1.430511474609375e-05s
INFO | --- Analysis for uriburner took 11620.845996141434s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 4.673004150390625e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0003783702850341797s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.30092883110046387s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.020968914031982422s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 3.7670135498046875e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 9.298324584960938e-06s
INFO | --- Analysis for urn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976 took 2.649217367172241s
Availability | SPARQL endpoint availability check for Legija Stranaca took 4.363059997558594e-05s
Availability | VoID file availability check for Legija Stranaca took 0.0005116462707519531s
Completeness | Calculation of interlinking completeness for Legija Stranaca took 0.2746591567993164s
Reputation | Calculation of the PageRank for Legija Stranaca took 0.02206277847290039s
Interlinking | Calculation of Degree of Connection for Legija Stranaca took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Legija Stranaca took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Legija Stranaca took 3.457069396972656e-05s
Believability | Calculation of trust value for Legija Stranaca took 1.621246337890625e-05s
INFO | --- Analysis for Uros_Legija_Susa took 2.6943881511688232s
Availability | SPARQL endpoint availability check for Legija took 9.059906005859375e-05s
Availability | VoID file availability check for Legija took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for Legija took 0.3071460723876953s
Reputation | Calculation of the PageRank for Legija took 0.02063751220703125s
Interlinking | Calculation of Degree of Connection for Legija took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Legija took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Legija took 3.1948089599609375e-05s
Believability | Calculation of trust value for Legija took 1.4543533325195312e-05s
INFO | --- Analysis for Uros_Susa took 2.6884262561798096s
Availability | SPARQL endpoint availability check for USAGE review corpus took 0.5358729362487793s
Availability | VoID file availability check for USAGE review corpus took 0.0006709098815917969s
Completeness | Calculation of interlinking completeness for USAGE review corpus took 0.33438682556152344s
Reputation | Calculation of the PageRank for USAGE review corpus took 0.020928144454956055s
Interlinking | Calculation of Degree of Connection for USAGE review corpus took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for USAGE review corpus took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for USAGE review corpus took 3.933906555175781e-05s
Believability | Calculation of trust value for USAGE review corpus took 1.4781951904296875e-05s
INFO | --- Analysis for usage-review-corpus took 4.046417713165283s
Availability | SPARQL endpoint availability check for Universidad Técnica Particular de Loja - Linked Open Data took 4.168702602386475s
Availability | VoID file availability check for Universidad Técnica Particular de Loja - Linked Open Data took 0.0005426406860351562s
Completeness | Calculation of interlinking completeness for Universidad Técnica Particular de Loja - Linked Open Data took 0.29871177673339844s
Reputation | Calculation of the PageRank for Universidad Técnica Particular de Loja - Linked Open Data took 0.02068924903869629s
Interlinking | Calculation of Degree of Connection for Universidad Técnica Particular de Loja - Linked Open Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universidad Técnica Particular de Loja - Linked Open Data took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for Universidad Técnica Particular de Loja - Linked Open Data took 8.296966552734375e-05s
Believability | Calculation of trust value for Universidad Técnica Particular de Loja - Linked Open Data took 1.430511474609375e-05s
INFO | --- Analysis for utpl-lod took 10.885688304901123s
Availability | SPARQL endpoint availability check for terrorist attack took 8.511543273925781e-05s
Availability | VoID file availability check for terrorist attack took 0.0006775856018066406s
Completeness | Calculation of interlinking completeness for terrorist attack took 0.3055236339569092s
Reputation | Calculation of the PageRank for terrorist attack took 0.0211031436920166s
Interlinking | Calculation of Degree of Connection for terrorist attack took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for terrorist attack took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for terrorist attack took 3.552436828613281e-05s
Believability | Calculation of trust value for terrorist attack took 1.049041748046875e-05s
INFO | --- Analysis for varsha took 4.548227787017822s
Availability | SPARQL endpoint availability check for VA took 4.7206878662109375e-05s
Availability | VoID file availability check for VA took 0.0003414154052734375s
Completeness | Calculation of interlinking completeness for VA took 0.27801084518432617s
Reputation | Calculation of the PageRank for VA took 0.02087569236755371s
Interlinking | Calculation of Degree of Connection for VA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for VA took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for VA took 3.218650817871094e-05s
Believability | Calculation of trust value for VA took 9.298324584960938e-06s
INFO | --- Analysis for Vehicule_Autonome took 2.8138437271118164s
Availability | SPARQL endpoint availability check for Velez (1744) Index Totius Artis in LiLa took 0.6133520603179932s
Availability | VoID file availability check for Velez (1744) Index Totius Artis in LiLa took 0.00041985511779785156s
Completeness | Calculation of interlinking completeness for Velez (1744) Index Totius Artis in LiLa took 0.30173277854919434s
Reputation | Calculation of the PageRank for Velez (1744) Index Totius Artis in LiLa took 0.02095937728881836s
Interlinking | Calculation of Degree of Connection for Velez (1744) Index Totius Artis in LiLa took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Velez (1744) Index Totius Artis in LiLa took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for Velez (1744) Index Totius Artis in LiLa took 4.482269287109375e-05s
Believability | Calculation of trust value for Velez (1744) Index Totius Artis in LiLa took 9.5367431640625e-06s
INFO | --- Analysis for VelezIndexTotiusArtis took 4.283901929855347s
Availability | SPARQL endpoint availability check for Verrijkt Koninkrijk took 6.6078386306762695s
Availability | VoID file availability check for Verrijkt Koninkrijk took 0.0004456043243408203s
Completeness | Calculation of interlinking completeness for Verrijkt Koninkrijk took 0.3365039825439453s
Reputation | Calculation of the PageRank for Verrijkt Koninkrijk took 0.020747900009155273s
Interlinking | Calculation of Degree of Connection for Verrijkt Koninkrijk took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Verrijkt Koninkrijk took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Verrijkt Koninkrijk took 9.34600830078125e-05s
Believability | Calculation of trust value for Verrijkt Koninkrijk took 1.33514404296875e-05s
INFO | --- Analysis for verrijktkoninkrijk took 15.918404579162598s
Availability | SPARQL endpoint availability check for VIAF: The Virtual International Authority File took 8.893013000488281e-05s
Availability | VoID file availability check for VIAF: The Virtual International Authority File took 0.00066375732421875s
Completeness | Calculation of interlinking completeness for VIAF: The Virtual International Authority File took 0.3038899898529053s
Reputation | Calculation of the PageRank for VIAF: The Virtual International Authority File took 0.02102494239807129s
Interlinking | Calculation of Degree of Connection for VIAF: The Virtual International Authority File took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for VIAF: The Virtual International Authority File took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for VIAF: The Virtual International Authority File took 0.00018334388732910156s
Believability | Calculation of trust value for VIAF: The Virtual International Authority File took 1.0013580322265625e-05s
INFO | --- Analysis for viaf took 20.60920023918152s
Availability | SPARQL endpoint availability check for Vihar Exports took 0.00010085105895996094s
Availability | VoID file availability check for Vihar Exports took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for Vihar Exports took 0.27562737464904785s
Reputation | Calculation of the PageRank for Vihar Exports took 0.02348804473876953s
Interlinking | Calculation of Degree of Connection for Vihar Exports took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Vihar Exports took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Vihar Exports took 3.457069396972656e-05s
Believability | Calculation of trust value for Vihar Exports took 1.5735626220703125e-05s
INFO | --- Analysis for Vihar_Exports took 2.638950824737549s
Availability | SPARQL endpoint availability check for VIVO took 0.00012993812561035156s
Availability | VoID file availability check for VIVO took 0.0009186267852783203s
Completeness | Calculation of interlinking completeness for VIVO took 0.32338738441467285s
Reputation | Calculation of the PageRank for VIVO took 0.02109217643737793s
Interlinking | Calculation of Degree of Connection for VIVO took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for VIVO took 0.0007994174957275391s
Interlinking | Calculation of Clustering coefficient for VIVO took 7.748603820800781e-05s
Believability | Calculation of trust value for VIVO took 6.580352783203125e-05s
INFO | --- Analysis for vivo took 5.221270799636841s
Availability | SPARQL endpoint availability check for VIVO Cornell took 8.988380432128906e-05s
Availability | VoID file availability check for VIVO Cornell took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for VIVO Cornell took 0.3017716407775879s
Reputation | Calculation of the PageRank for VIVO Cornell took 0.02071976661682129s
Interlinking | Calculation of Degree of Connection for VIVO Cornell took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for VIVO Cornell took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for VIVO Cornell took 8.606910705566406e-05s
Believability | Calculation of trust value for VIVO Cornell took 1.0251998901367188e-05s
INFO | --- Analysis for vivo-cornell-university took 6.490461826324463s
Availability | SPARQL endpoint availability check for VIVO Indiana took 8.7738037109375e-05s
Availability | VoID file availability check for VIVO Indiana took 0.0006251335144042969s
Completeness | Calculation of interlinking completeness for VIVO Indiana took 0.2791464328765869s
Reputation | Calculation of the PageRank for VIVO Indiana took 0.021016359329223633s
Interlinking | Calculation of Degree of Connection for VIVO Indiana took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for VIVO Indiana took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for VIVO Indiana took 8.440017700195312e-05s
Believability | Calculation of trust value for VIVO Indiana took 1.2636184692382812e-05s
INFO | --- Analysis for vivo-indiana-university took 3.266303062438965s
Availability | SPARQL endpoint availability check for VIVO Ponce took 9.107589721679688e-05s
Availability | VoID file availability check for VIVO Ponce took 0.0006201267242431641s
Completeness | Calculation of interlinking completeness for VIVO Ponce took 0.30223608016967773s
Reputation | Calculation of the PageRank for VIVO Ponce took 0.020754098892211914s
Interlinking | Calculation of Degree of Connection for VIVO Ponce took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for VIVO Ponce took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for VIVO Ponce took 3.981590270996094e-05s
Believability | Calculation of trust value for VIVO Ponce took 9.059906005859375e-06s
INFO | --- Analysis for vivo-ponce took 3.2072980403900146s
Availability | SPARQL endpoint availability check for VIVO Scripps Research Institute took 9.274482727050781e-05s
Availability | VoID file availability check for VIVO Scripps Research Institute took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for VIVO Scripps Research Institute took 0.33816099166870117s
Reputation | Calculation of the PageRank for VIVO Scripps Research Institute took 0.02081918716430664s
Interlinking | Calculation of Degree of Connection for VIVO Scripps Research Institute took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for VIVO Scripps Research Institute took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for VIVO Scripps Research Institute took 4.220008850097656e-05s
Believability | Calculation of trust value for VIVO Scripps Research Institute took 1.3828277587890625e-05s
INFO | --- Analysis for vivo-scripps-research-institute took 3.2179453372955322s
Availability | SPARQL endpoint availability check for VIVO University of Florida took 4.76837158203125e-05s
Availability | VoID file availability check for VIVO University of Florida took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for VIVO University of Florida took 0.2905900478363037s
Reputation | Calculation of the PageRank for VIVO University of Florida took 0.02074146270751953s
Interlinking | Calculation of Degree of Connection for VIVO University of Florida took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for VIVO University of Florida took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for VIVO University of Florida took 0.00010013580322265625s
Believability | Calculation of trust value for VIVO University of Florida took 1.4781951904296875e-05s
INFO | --- Analysis for vivo-university-of-florida took 2.909677505493164s
Availability | SPARQL endpoint availability check for VIVO Weill Cornell Medical College took 4.6253204345703125e-05s
Availability | VoID file availability check for VIVO Weill Cornell Medical College took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for VIVO Weill Cornell Medical College took 0.2929420471191406s
Reputation | Calculation of the PageRank for VIVO Weill Cornell Medical College took 0.02071857452392578s
Interlinking | Calculation of Degree of Connection for VIVO Weill Cornell Medical College took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for VIVO Weill Cornell Medical College took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for VIVO Weill Cornell Medical College took 4.220008850097656e-05s
Believability | Calculation of trust value for VIVO Weill Cornell Medical College took 8.821487426757812e-06s
INFO | --- Analysis for vivo-weill-cornell-medical-college took 3.269460916519165s
Availability | SPARQL endpoint availability check for VIVO WUSTL took 4.458427429199219e-05s
Availability | VoID file availability check for VIVO WUSTL took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for VIVO WUSTL took 0.277965784072876s
Reputation | Calculation of the PageRank for VIVO WUSTL took 0.020564794540405273s
Interlinking | Calculation of Degree of Connection for VIVO WUSTL took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for VIVO WUSTL took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for VIVO WUSTL took 3.933906555175781e-05s
Believability | Calculation of trust value for VIVO WUSTL took 1.5020370483398438e-05s
INFO | --- Analysis for vivo-wustl took 3.0650346279144287s
Availability | SPARQL endpoint availability check for vivo2doi took 4.506111145019531e-05s
Availability | VoID file availability check for vivo2doi took 0.0006139278411865234s
Completeness | Calculation of interlinking completeness for vivo2doi took 0.3100292682647705s
Reputation | Calculation of the PageRank for vivo2doi took 0.021103620529174805s
Interlinking | Calculation of Degree of Connection for vivo2doi took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for vivo2doi took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for vivo2doi took 4.9591064453125e-05s
Believability | Calculation of trust value for vivo2doi took 9.059906005859375e-06s
INFO | --- Analysis for vivo2doi took 25.77206563949585s
Availability | SPARQL endpoint availability check for WordNet 3.0 (VU Amsterdam) took 5.221366882324219e-05s
Availability | VoID file availability check for WordNet 3.0 (VU Amsterdam) took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for WordNet 3.0 (VU Amsterdam) took 0.2672429084777832s
Reputation | Calculation of the PageRank for WordNet 3.0 (VU Amsterdam) took 0.02080225944519043s
Interlinking | Calculation of Degree of Connection for WordNet 3.0 (VU Amsterdam) took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for WordNet 3.0 (VU Amsterdam) took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for WordNet 3.0 (VU Amsterdam) took 7.343292236328125e-05s
Believability | Calculation of trust value for WordNet 3.0 (VU Amsterdam) took 1.049041748046875e-05s
INFO | --- Analysis for vu-wordnet took 14.913254976272583s
Availability | SPARQL endpoint availability check for vulnerapedia took 0.09052276611328125s
Availability | VoID file availability check for vulnerapedia took 0.0002841949462890625s
Completeness | Calculation of interlinking completeness for vulnerapedia took 0.2902224063873291s
Reputation | Calculation of the PageRank for vulnerapedia took 0.02121710777282715s
Interlinking | Calculation of Degree of Connection for vulnerapedia took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for vulnerapedia took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for vulnerapedia took 7.462501525878906e-05s
Believability | Calculation of trust value for vulnerapedia took 1.3828277587890625e-05s
INFO | --- Analysis for vulnerapedia took 3.3084826469421387s
Availability | SPARQL endpoint availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.00011587142944335938s
Availability | VoID file availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0005326271057128906s
Completeness | Calculation of interlinking completeness for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.29867076873779297s
Reputation | Calculation of the PageRank for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.02058124542236328s
Interlinking | Calculation of Degree of Connection for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.4066696166992188e-05s
Believability | Calculation of trust value for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.4066696166992188e-05s
INFO | --- Analysis for VVASIAK took 2.715393543243408s
Availability | SPARQL endpoint availability check for Statybu imone - Vyvasta took 9.393692016601562e-05s
Availability | VoID file availability check for Statybu imone - Vyvasta took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for Statybu imone - Vyvasta took 0.33041834831237793s
Reputation | Calculation of the PageRank for Statybu imone - Vyvasta took 0.022067785263061523s
Interlinking | Calculation of Degree of Connection for Statybu imone - Vyvasta took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Statybu imone - Vyvasta took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Statybu imone - Vyvasta took 3.2901763916015625e-05s
Believability | Calculation of trust value for Statybu imone - Vyvasta took 1.0728836059570312e-05s
INFO | --- Analysis for Vyvasta took 2.778231143951416s
Availability | SPARQL endpoint availability check for W3C took 8.7738037109375e-05s
Availability | VoID file availability check for W3C took 0.0007479190826416016s
Completeness | Calculation of interlinking completeness for W3C took 0.30672645568847656s
Reputation | Calculation of the PageRank for W3C took 0.020700693130493164s
Interlinking | Calculation of Degree of Connection for W3C took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for W3C took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for W3C took 0.0001437664031982422s
Believability | Calculation of trust value for W3C took 1.2874603271484375e-05s
INFO | --- Analysis for w3c took 3.006530284881592s
Availability | SPARQL endpoint availability check for WordNet 2.0 (W3C) took 4.506111145019531e-05s
Availability | VoID file availability check for WordNet 2.0 (W3C) took 0.0009374618530273438s
Completeness | Calculation of interlinking completeness for WordNet 2.0 (W3C) took 0.29424285888671875s
Reputation | Calculation of the PageRank for WordNet 2.0 (W3C) took 0.020983457565307617s
Interlinking | Calculation of Degree of Connection for WordNet 2.0 (W3C) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for WordNet 2.0 (W3C) took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for WordNet 2.0 (W3C) took 0.00011897087097167969s
Believability | Calculation of trust value for WordNet 2.0 (W3C) took 9.775161743164062e-06s
INFO | --- Analysis for w3c-wordnet took 3.9162471294403076s
Availability | SPARQL endpoint availability check for WarSampo took 0.35561227798461914s
Availability | VoID file availability check for WarSampo took 0.0003809928894042969s
Extra | Recovery of all triples for WarSampo took 25.975436449050903s
Performance | Total latancy measurement for WarSampo took 0.8084092140197754s
Amount of data | Number of triples check for WarSampo took 17.96690058708191s
Interoperability | New terms check for WarSampo took 3.97318959236145s
Versatility | Languages check for WarSampo took 50.26474142074585s
Interpretability | Number of blank nodes check for WarSampo took 17.352013111114502s
Security | Check HTTPS for WarSampo took 0.41120195388793945s
Interpretability | RDF structures check for WarSampo took 0.19781017303466797s
Versatility | Serialization formats check for WarSampo took 0.20430207252502441s
Availability | RDF dump link check for WarSampo took 0.88496994972229s
License | MR license check for WarSampo took 0.20679450035095215s
License | HR license check for WarSampo took 44.58285403251648s
Amount of data | Number of property check for WarSampo took 0.20101070404052734s
Understandability | Number of label check for WarSampo took 9.184366226196289s
Understandability | URI regex check for WarSampo took 0.35342979431152344s
Understandability | Vocabs check for WarSampo took 0.16238665580749512s
Verifiability | Authors check for WarSampo took 0.20468735694885254s
Verifiability | Publishers check for WarSampo took 0.2097797393798828s
Performance | Throughput check for WarSampo took 10.925686836242676s
Amount of data | Check the number of entities for WarSampo took 17.121253490447998s
Verifiability | Contribs. check for WarSampo took 0.1907355785369873s
Interlinking | sameAs chians check for WarSampo took 0.20093703269958496s
Interlinking | skos check for WarSampo took 0.20667076110839844s
Interlinking | skos check for WarSampo took 0.16361236572265625s
Timeliness | dataset update frequency check for WarSampo took 0.15341496467590332s
Currency | Creation date check for WarSampo took 0.36348390579223633s
Currency | Modification date check for WarSampo took 0.37850260734558105s
Rep.Conc. | URIs length for WarSampo took 50.583895206451416s
Interoperability | New vocabularies check for WarSampo took 1.3589859008789062e-05s
Consistency | Deprecated classes/propertiers check for WarSampo took 0.1954798698425293s
Accuracy | Check Functional Property for WarSampo took 0.20262861251831055s
Accuracy | Check Inverse Functional Property for WarSampo took 0.16873884201049805s
Accuracy | Check Empty annotation labels for WarSampo took 11.861454963684082s
Accuracy | Check White space in annotation for WarSampo took 2.2777516841888428s
Accuracy | Check Datatype consistency for WarSampo took 5.616418838500977s
Consistency | Disjoint class check for WarSampo took 0.1889810562133789s
Consistency | Check Misplaced properties for WarSampo took 21.12690043449402s
Consistency | Check Ontology hijacking for WarSampo took 20.176117658615112s
Consistency | Check Invalid usage of undefined classes for WarSampo took 1.5821607112884521s
Consistency | Check Invalid usage of undefined properties for WarSampo took 1.8074007034301758s
Conciseness | Check Extensional conciseness for WarSampo took 2.9126687049865723s
Conciseness | Check Intensional conciseness for WarSampo took 0.3095073699951172s
Security | Sign check for WarSampo took 0.16902995109558105s
Availability | Check URIs Dereferenciability for WarSampo took 2.6196625232696533s
Completeness | Calculation of interlinking completeness for WarSampo took 0.501732349395752s
Reputation | Calculation of the PageRank for WarSampo took 0.021671056747436523s
Interlinking | Calculation of Degree of Connection for WarSampo took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for WarSampo took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for WarSampo took 9.72747802734375e-05s
Interoperability | Check the re-using of existing vocabs for WarSampo took 2.6226043701171875e-06s
Believability | Calculation of trust value for WarSampo took 1.5020370483398438e-05s
INFO | --- Analysis for warsampo took 973.9079828262329s
Availability | SPARQL endpoint availability check for WASABI RDF Knowledge Graph took 20.46326184272766s
Availability | VoID file availability check for WASABI RDF Knowledge Graph took 0.0005950927734375s
Completeness | Calculation of interlinking completeness for WASABI RDF Knowledge Graph took 0.3281290531158447s
Reputation | Calculation of the PageRank for WASABI RDF Knowledge Graph took 0.02171945571899414s
Interlinking | Calculation of Degree of Connection for WASABI RDF Knowledge Graph took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for WASABI RDF Knowledge Graph took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for WASABI RDF Knowledge Graph took 9.250640869140625e-05s
Believability | Calculation of trust value for WASABI RDF Knowledge Graph took 1.4781951904296875e-05s
INFO | --- Analysis for wasabi took 54.80962061882019s
Availability | SPARQL endpoint availability check for FAO water areas classification as linked data @PSNC took 0.614924430847168s
Availability | VoID file availability check for FAO water areas classification as linked data @PSNC took 0.0005879402160644531s
Extra | Recovery of all triples for FAO water areas classification as linked data @PSNC took 111.08659982681274s
Performance | Total latancy measurement for FAO water areas classification as linked data @PSNC took 0.968764066696167s
Amount of data | Number of triples check for FAO water areas classification as linked data @PSNC took 9.021802186965942s
Interoperability | New terms check for FAO water areas classification as linked data @PSNC took 14.349437236785889s
Versatility | Languages check for FAO water areas classification as linked data @PSNC took 300.2537705898285s
Interpretability | Number of blank nodes check for FAO water areas classification as linked data @PSNC took 2.0928163528442383s
Interpretability | RDF structures check for FAO water areas classification as linked data @PSNC took 0.3257617950439453s
Versatility | Serialization formats check for FAO water areas classification as linked data @PSNC took 12.065203666687012s
Availability | RDF dump link check for FAO water areas classification as linked data @PSNC took 0.3758533000946045s
License | MR license check for FAO water areas classification as linked data @PSNC took 0.9915118217468262s
License | HR license check for FAO water areas classification as linked data @PSNC took 300.2399227619171s
Amount of data | Number of property check for FAO water areas classification as linked data @PSNC took 0.2098851203918457s
Understandability | Number of label check for FAO water areas classification as linked data @PSNC took 2.9274041652679443s
Understandability | URI regex check for FAO water areas classification as linked data @PSNC took 1.1980798244476318s
Understandability | Vocabs check for FAO water areas classification as linked data @PSNC took 0.5950901508331299s
Verifiability | Authors check for FAO water areas classification as linked data @PSNC took 0.20699143409729004s
Verifiability | Publishers check for FAO water areas classification as linked data @PSNC took 0.24747562408447266s
Performance | Throughput check for FAO water areas classification as linked data @PSNC took 11.19634222984314s
Amount of data | Check the number of entities for FAO water areas classification as linked data @PSNC took 8.20159912109375e-05s
Verifiability | Contribs. check for FAO water areas classification as linked data @PSNC took 0.20241713523864746s
Interlinking | sameAs chians check for FAO water areas classification as linked data @PSNC took 0.1938316822052002s
Interlinking | skos check for FAO water areas classification as linked data @PSNC took 0.48559141159057617s
Interlinking | skos check for FAO water areas classification as linked data @PSNC took 0.40253281593322754s
Timeliness | dataset update frequency check for FAO water areas classification as linked data @PSNC took 8.12245488166809s
Currency | Creation date check for FAO water areas classification as linked data @PSNC took 0.4709901809692383s
Currency | Modification date check for FAO water areas classification as linked data @PSNC took 0.2321164608001709s
Rep.Conc. | URIs length for FAO water areas classification as linked data @PSNC took 152.3058614730835s
Interoperability | New vocabularies check for FAO water areas classification as linked data @PSNC took 1.239776611328125e-05s
Consistency | Deprecated classes/propertiers check for FAO water areas classification as linked data @PSNC took 0.208939790725708s
Accuracy | Check Functional Property for FAO water areas classification as linked data @PSNC took 0.4467020034790039s
Accuracy | Check Inverse Functional Property for FAO water areas classification as linked data @PSNC took 0.435976505279541s
Accuracy | Check Empty annotation labels for FAO water areas classification as linked data @PSNC took 43.63793325424194s
Accuracy | Check White space in annotation for FAO water areas classification as linked data @PSNC took 2.6855087280273438s
Accuracy | Check Datatype consistency for FAO water areas classification as linked data @PSNC took 2.8041207790374756s
Consistency | Disjoint class check for FAO water areas classification as linked data @PSNC took 0.1839122772216797s
Consistency | Check Misplaced properties for FAO water areas classification as linked data @PSNC took 86.02681159973145s
Consistency | Misplaced classes for FAO water areas classification as linked data @PSNC took 8.679119110107422s
Consistency | Check Ontology hijacking for FAO water areas classification as linked data @PSNC took 37.20436644554138s
Consistency | Check Invalid usage of undefined classes for FAO water areas classification as linked data @PSNC took 1.5425846576690674s
Consistency | Check Invalid usage of undefined properties for FAO water areas classification as linked data @PSNC took 87.56133532524109s
Conciseness | Check Extensional conciseness for FAO water areas classification as linked data @PSNC took 2.7907705307006836s
Conciseness | Check Intensional conciseness for FAO water areas classification as linked data @PSNC took 0.5867593288421631s
Security | Sign check for FAO water areas classification as linked data @PSNC took 1.456244707107544s
Availability | Check URIs Dereferenciability for FAO water areas classification as linked data @PSNC took 10.764169931411743s
Completeness | Calculation of interlinking completeness for FAO water areas classification as linked data @PSNC took 0.46822690963745117s
Reputation | Calculation of the PageRank for FAO water areas classification as linked data @PSNC took 0.02182602882385254s
Interlinking | Calculation of Degree of Connection for FAO water areas classification as linked data @PSNC took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for FAO water areas classification as linked data @PSNC took 0.0007967948913574219s
Interlinking | Calculation of Clustering coefficient for FAO water areas classification as linked data @PSNC took 5.936622619628906e-05s
Interoperability | Check the re-using of existing vocabs for FAO water areas classification as linked data @PSNC took 2.86102294921875e-06s
Believability | Calculation of trust value for FAO water areas classification as linked data @PSNC took 1.4066696166992188e-05s
INFO | --- Analysis for Water_Areas_Classification took 2280.362453699112s
Availability | SPARQL endpoint availability check for Water buffer dataset from Czech Republic @PSNC took 0.1967611312866211s
Availability | VoID file availability check for Water buffer dataset from Czech Republic @PSNC took 0.0005595684051513672s
Extra | Recovery of all triples for Water buffer dataset from Czech Republic @PSNC took 132.58397245407104s
Performance | Total latancy measurement for Water buffer dataset from Czech Republic @PSNC took 1.0181374549865723s
Amount of data | Number of triples check for Water buffer dataset from Czech Republic @PSNC took 8.918515920639038s
Interoperability | New terms check for Water buffer dataset from Czech Republic @PSNC took 14.581459760665894s
Versatility | Languages check for Water buffer dataset from Czech Republic @PSNC took 300.2436218261719s
Interpretability | Number of blank nodes check for Water buffer dataset from Czech Republic @PSNC took 2.175922155380249s
Interpretability | RDF structures check for Water buffer dataset from Czech Republic @PSNC took 0.3102753162384033s
Versatility | Serialization formats check for Water buffer dataset from Czech Republic @PSNC took 9.337822914123535s
Availability | RDF dump link check for Water buffer dataset from Czech Republic @PSNC took 0.3970448970794678s
License | MR license check for Water buffer dataset from Czech Republic @PSNC took 0.8222200870513916s
License | HR license check for Water buffer dataset from Czech Republic @PSNC took 300.25086998939514s
Amount of data | Number of property check for Water buffer dataset from Czech Republic @PSNC took 0.2134110927581787s
Understandability | Number of label check for Water buffer dataset from Czech Republic @PSNC took 2.7994918823242188s
Understandability | URI regex check for Water buffer dataset from Czech Republic @PSNC took 1.1059417724609375s
Understandability | Vocabs check for Water buffer dataset from Czech Republic @PSNC took 0.5579426288604736s
Verifiability | Authors check for Water buffer dataset from Czech Republic @PSNC took 0.20901989936828613s
Verifiability | Publishers check for Water buffer dataset from Czech Republic @PSNC took 0.26627445220947266s
Performance | Throughput check for Water buffer dataset from Czech Republic @PSNC took 11.34670352935791s
Amount of data | Check the number of entities for Water buffer dataset from Czech Republic @PSNC took 9.608268737792969e-05s
Verifiability | Contribs. check for Water buffer dataset from Czech Republic @PSNC took 0.18633389472961426s
Interlinking | sameAs chians check for Water buffer dataset from Czech Republic @PSNC took 0.22257375717163086s
Interlinking | skos check for Water buffer dataset from Czech Republic @PSNC took 0.5144240856170654s
Interlinking | skos check for Water buffer dataset from Czech Republic @PSNC took 0.42345690727233887s
Timeliness | dataset update frequency check for Water buffer dataset from Czech Republic @PSNC took 5.042401313781738s
Currency | Creation date check for Water buffer dataset from Czech Republic @PSNC took 0.5020875930786133s
Currency | Modification date check for Water buffer dataset from Czech Republic @PSNC took 0.22169923782348633s
Rep.Conc. | URIs length for Water buffer dataset from Czech Republic @PSNC took 156.11602139472961s
Interoperability | New vocabularies check for Water buffer dataset from Czech Republic @PSNC took 1.2636184692382812e-05s
Consistency | Deprecated classes/propertiers check for Water buffer dataset from Czech Republic @PSNC took 0.2033979892730713s
Accuracy | Check Functional Property for Water buffer dataset from Czech Republic @PSNC took 0.42313051223754883s
Accuracy | Check Inverse Functional Property for Water buffer dataset from Czech Republic @PSNC took 0.44231319427490234s
Accuracy | Check Empty annotation labels for Water buffer dataset from Czech Republic @PSNC took 45.23607540130615s
Accuracy | Check White space in annotation for Water buffer dataset from Czech Republic @PSNC took 2.7277276515960693s
Accuracy | Check Datatype consistency for Water buffer dataset from Czech Republic @PSNC took 2.7319464683532715s
Consistency | Disjoint class check for Water buffer dataset from Czech Republic @PSNC took 0.18926119804382324s
Consistency | Check Misplaced properties for Water buffer dataset from Czech Republic @PSNC took 86.27170991897583s
Consistency | Misplaced classes for Water buffer dataset from Czech Republic @PSNC took 8.532185316085815s
Consistency | Check Ontology hijacking for Water buffer dataset from Czech Republic @PSNC took 36.312867879867554s
Consistency | Check Invalid usage of undefined classes for Water buffer dataset from Czech Republic @PSNC took 1.515718936920166s
Consistency | Check Invalid usage of undefined properties for Water buffer dataset from Czech Republic @PSNC took 88.1837248802185s
Conciseness | Check Extensional conciseness for Water buffer dataset from Czech Republic @PSNC took 2.8140931129455566s
Conciseness | Check Intensional conciseness for Water buffer dataset from Czech Republic @PSNC took 0.50101637840271s
Security | Sign check for Water buffer dataset from Czech Republic @PSNC took 1.231156587600708s
Availability | Check URIs Dereferenciability for Water buffer dataset from Czech Republic @PSNC took 9.687702178955078s
Completeness | Calculation of interlinking completeness for Water buffer dataset from Czech Republic @PSNC took 1.2474865913391113s
Reputation | Calculation of the PageRank for Water buffer dataset from Czech Republic @PSNC took 0.021716833114624023s
Interlinking | Calculation of Degree of Connection for Water buffer dataset from Czech Republic @PSNC took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Water buffer dataset from Czech Republic @PSNC took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Water buffer dataset from Czech Republic @PSNC took 5.984306335449219e-05s
Interoperability | Check the re-using of existing vocabs for Water buffer dataset from Czech Republic @PSNC took 2.6226043701171875e-06s
Believability | Calculation of trust value for Water buffer dataset from Czech Republic @PSNC took 1.5735626220703125e-05s
INFO | --- Analysis for Water_Buffer took 2293.9640464782715s
Availability | SPARQL endpoint availability check for WebIsALOD took 0.20664119720458984s
Availability | VoID file availability check for WebIsALOD took 0.0008180141448974609s
Extra | Recovery of all triples for WebIsALOD took 1.4682223796844482s
Performance | Total latancy measurement for WebIsALOD took 0.4359591007232666s
Amount of data | Number of triples check for WebIsALOD took 36.337581634521484s
Interoperability | New terms check for WebIsALOD took 22.929585933685303s
Versatility | Languages check for WebIsALOD took 60.7172646522522s
Interpretability | Number of blank nodes check for WebIsALOD took 0.11746454238891602s
Interpretability | RDF structures check for WebIsALOD took 0.23383688926696777s
Versatility | Serialization formats check for WebIsALOD took 0.13089394569396973s
Availability | RDF dump link check for WebIsALOD took 1.5441820621490479s
License | MR license check for WebIsALOD took 0.10522174835205078s
License | HR license check for WebIsALOD took 53.127973794937134s
Amount of data | Number of property check for WebIsALOD took 0.12058758735656738s
Understandability | Number of label check for WebIsALOD took 0.33626699447631836s
Understandability | URI regex check for WebIsALOD took 0.18390154838562012s
Understandability | Vocabs check for WebIsALOD took 0.11761307716369629s
Verifiability | Authors check for WebIsALOD took 0.14461803436279297s
Verifiability | Publishers check for WebIsALOD took 0.12054848670959473s
Performance | Throughput check for WebIsALOD took 10.49549388885498s
Amount of data | Check the number of entities for WebIsALOD took 8.106231689453125e-05s
Verifiability | Contribs. check for WebIsALOD took 0.11757373809814453s
Interlinking | sameAs chians check for WebIsALOD took 0.17078280448913574s
Interlinking | skos check for WebIsALOD took 0.11829948425292969s
Interlinking | skos check for WebIsALOD took 0.08877253532409668s
Timeliness | dataset update frequency check for WebIsALOD took 0.08117818832397461s
Currency | Creation date check for WebIsALOD took 0.2651631832122803s
Currency | Modification date check for WebIsALOD took 0.23190855979919434s
Rep.Conc. | URIs length for WebIsALOD took 83.077308177948s
Interoperability | New vocabularies check for WebIsALOD took 17.37738275527954s
Consistency | Deprecated classes/propertiers check for WebIsALOD took 0.10938525199890137s
Accuracy | Check Functional Property for WebIsALOD took 0.1458730697631836s
Accuracy | Check Inverse Functional Property for WebIsALOD took 0.10082745552062988s
Accuracy | Check Empty annotation labels for WebIsALOD took 0.4405505657196045s
Accuracy | Check White space in annotation for WebIsALOD took 0.030144691467285156s
Accuracy | Check Datatype consistency for WebIsALOD took 0.030356407165527344s
Consistency | Disjoint class check for WebIsALOD took 0.10411834716796875s
Consistency | Check Misplaced properties for WebIsALOD took 60.96109867095947s
Consistency | Misplaced classes for WebIsALOD took 0.2489795684814453s
Consistency | Check Ontology hijacking for WebIsALOD took 2.213118314743042s
Consistency | Check Invalid usage of undefined classes for WebIsALOD took 1.7099609375s
Consistency | Check Invalid usage of undefined properties for WebIsALOD took 63.57504487037659s
Conciseness | Check Extensional conciseness for WebIsALOD took 0.03258085250854492s
Conciseness | Check Intensional conciseness for WebIsALOD took 0.1599893569946289s
Security | Sign check for WebIsALOD took 0.09942150115966797s
Availability | Check URIs Dereferenciability for WebIsALOD took 10.020500898361206s
Completeness | Calculation of interlinking completeness for WebIsALOD took 0.46556591987609863s
Reputation | Calculation of the PageRank for WebIsALOD took 0.021327972412109375s
Interlinking | Calculation of Degree of Connection for WebIsALOD took 7.319450378417969e-05s
Interlinking | Calculation of Centrality for WebIsALOD took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for WebIsALOD took 0.0001068115234375s
Interoperability | Check the re-using of existing vocabs for WebIsALOD took 18.213029384613037s
Believability | Calculation of trust value for WebIsALOD took 1.4781951904296875e-05s
INFO | --- Analysis for webisalod took 672.5706086158752s
Availability | SPARQL endpoint availability check for webnmasunotraveler took 4.57763671875e-05s
Availability | VoID file availability check for webnmasunotraveler took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for webnmasunotraveler took 0.3112306594848633s
Reputation | Calculation of the PageRank for webnmasunotraveler took 0.025132417678833008s
Interlinking | Calculation of Degree of Connection for webnmasunotraveler took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for webnmasunotraveler took 0.0010938644409179688s
Interlinking | Calculation of Clustering coefficient for webnmasunotraveler took 5.269050598144531e-05s
Believability | Calculation of trust value for webnmasunotraveler took 1.430511474609375e-05s
INFO | --- Analysis for webnmasunotraveler took 8.995740413665771s
Availability | SPARQL endpoint availability check for Whisky Circle took 9.107589721679688e-05s
Availability | VoID file availability check for Whisky Circle took 0.0005321502685546875s
Completeness | Calculation of interlinking completeness for Whisky Circle took 0.29044532775878906s
Reputation | Calculation of the PageRank for Whisky Circle took 0.021880149841308594s
Interlinking | Calculation of Degree of Connection for Whisky Circle took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Whisky Circle took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Whisky Circle took 0.00010704994201660156s
Believability | Calculation of trust value for Whisky Circle took 1.4781951904296875e-05s
INFO | --- Analysis for whisky-circle-info took 3.277369737625122s
Availability | SPARQL endpoint availability check for Corona Virus Infected Cases Ontology took 9.899352312088013s
Availability | VoID file availability check for Corona Virus Infected Cases Ontology took 0.0007371902465820312s
Completeness | Calculation of interlinking completeness for Corona Virus Infected Cases Ontology took 0.30905699729919434s
Reputation | Calculation of the PageRank for Corona Virus Infected Cases Ontology took 0.031407833099365234s
Interlinking | Calculation of Degree of Connection for Corona Virus Infected Cases Ontology took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Corona Virus Infected Cases Ontology took 0.0011119842529296875s
Interlinking | Calculation of Clustering coefficient for Corona Virus Infected Cases Ontology took 5.245208740234375e-05s
Believability | Calculation of trust value for Corona Virus Infected Cases Ontology took 1.6450881958007812e-05s
INFO | --- Analysis for WHOnto took 26.851089239120483s
Availability | SPARQL endpoint availability check for COvid-19 statistics Ontology took 9.417533874511719e-05s
Availability | VoID file availability check for COvid-19 statistics Ontology took 0.0007300376892089844s
Completeness | Calculation of interlinking completeness for COvid-19 statistics Ontology took 0.2847900390625s
Reputation | Calculation of the PageRank for COvid-19 statistics Ontology took 0.02073216438293457s
Interlinking | Calculation of Degree of Connection for COvid-19 statistics Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for COvid-19 statistics Ontology took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for COvid-19 statistics Ontology took 3.409385681152344e-05s
Believability | Calculation of trust value for COvid-19 statistics Ontology took 1.4781951904296875e-05s
INFO | --- Analysis for whonto took 8.631213426589966s
Availability | SPARQL endpoint availability check for Wikidata took 0.5711369514465332s
Availability | VoID file availability check for Wikidata took 0.0007092952728271484s
Extra | Recovery of all triples for Wikidata took 31.754330158233643s
Performance | Total latancy measurement for Wikidata took 1.3883707523345947s
Amount of data | Number of triples check for Wikidata took 65.18194699287415s
Interoperability | New terms check for Wikidata took 2.056830883026123s
Versatility | Languages check for Wikidata took 60.21352005004883s
Interpretability | Number of blank nodes check for Wikidata took 0.3343172073364258s
Interpretability | RDF structures check for Wikidata took 0.16953682899475098s
Versatility | Serialization formats check for Wikidata took 0.3294837474822998s
Availability | RDF dump link check for Wikidata took 0.18127965927124023s
License | MR license check for Wikidata took 0.20094799995422363s
License | HR license check for Wikidata took 65.18329620361328s
Amount of data | Number of property check for Wikidata took 1.078195333480835s
Understandability | Number of label check for Wikidata took 60.20890760421753s
Understandability | URI regex check for Wikidata took 0.44086623191833496s
Understandability | Vocabs check for Wikidata took 0.18538880348205566s
Verifiability | Authors check for Wikidata took 0.18555164337158203s
Verifiability | Publishers check for Wikidata took 0.16187286376953125s
Amount of data | Check the number of entities for Wikidata took 7.390975952148438e-05s
Verifiability | Contribs. check for Wikidata took 0.2224729061126709s
Interlinking | sameAs chians check for Wikidata took 20.978910446166992s
Interlinking | skos check for Wikidata took 0.17395257949829102s
Interlinking | skos check for Wikidata took 0.07108712196350098s
Timeliness | dataset update frequency check for Wikidata took 0.18332624435424805s
Currency | Creation date check for Wikidata took 0.37963175773620605s
Currency | Modification date check for Wikidata took 0.4510214328765869s
Rep.Conc. | URIs length for Wikidata took 86.85313630104065s
Interoperability | New vocabularies check for Wikidata took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for Wikidata took 0.18056130409240723s
Accuracy | Check Datatype consistency for Wikidata took 4.7213134765625s
Consistency | Disjoint class check for Wikidata took 0.22765111923217773s
Consistency | Misplaced classes for Wikidata took 9.531116962432861s
Consistency | Check Ontology hijacking for Wikidata took 35.77423715591431s
Consistency | Check Invalid usage of undefined classes for Wikidata took 1.4789869785308838s
Consistency | Check Invalid usage of undefined properties for Wikidata took 17.991368770599365s
Conciseness | Check Extensional conciseness for Wikidata took 2.887662410736084s
Conciseness | Check Intensional conciseness for Wikidata took 1.5852856636047363s
Security | Sign check for Wikidata took 0.36581873893737793s
Availability | Check URIs Dereferenciability for Wikidata took 8.985568046569824s
Completeness | Calculation of interlinking completeness for Wikidata took 0.5012979507446289s
Reputation | Calculation of the PageRank for Wikidata took 0.02039051055908203s
Interlinking | Calculation of Degree of Connection for Wikidata took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Wikidata took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Wikidata took 0.00029158592224121094s
Interoperability | Check the re-using of existing vocabs for Wikidata took 1.6689300537109375e-06s
Believability | Calculation of trust value for Wikidata took 6.9141387939453125e-06s
INFO | --- Analysis for wikidata took 874.2298908233643s
Availability | SPARQL endpoint availability check for Wikilinks RDF/NIF took 4.410743713378906e-05s
Availability | VoID file availability check for Wikilinks RDF/NIF took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for Wikilinks RDF/NIF took 0.3314642906188965s
Reputation | Calculation of the PageRank for Wikilinks RDF/NIF took 0.020238637924194336s
Interlinking | Calculation of Degree of Connection for Wikilinks RDF/NIF took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Wikilinks RDF/NIF took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Wikilinks RDF/NIF took 7.104873657226562e-05s
Believability | Calculation of trust value for Wikilinks RDF/NIF took 1.33514404296875e-05s
INFO | --- Analysis for wikilinks-rdf-nif took 2.865628480911255s
Availability | SPARQL endpoint availability check for wiktionary.dbpedia.org took 0.29009580612182617s
Availability | VoID file availability check for wiktionary.dbpedia.org took 0.0006866455078125s
Completeness | Calculation of interlinking completeness for wiktionary.dbpedia.org took 0.2866942882537842s
Reputation | Calculation of the PageRank for wiktionary.dbpedia.org took 0.02151942253112793s
Interlinking | Calculation of Degree of Connection for wiktionary.dbpedia.org took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for wiktionary.dbpedia.org took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for wiktionary.dbpedia.org took 8.606910705566406e-05s
Believability | Calculation of trust value for wiktionary.dbpedia.org took 1.7642974853515625e-05s
INFO | --- Analysis for wiktionary-dbpedia-org took 4.575959205627441s
Availability | SPARQL endpoint availability check for The World Literature Knowledge Graph took 1.2808027267456055s
Availability | VoID file availability check for The World Literature Knowledge Graph took 0.0002760887145996094s
Completeness | Calculation of interlinking completeness for The World Literature Knowledge Graph took 0.2707209587097168s
Reputation | Calculation of the PageRank for The World Literature Knowledge Graph took 0.02056741714477539s
Interlinking | Calculation of Degree of Connection for The World Literature Knowledge Graph took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The World Literature Knowledge Graph took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for The World Literature Knowledge Graph took 3.361701965332031e-05s
Believability | Calculation of trust value for The World Literature Knowledge Graph took 1.4066696166992188e-05s
INFO | --- Analysis for wl-kg took 4.126450538635254s
Availability | SPARQL endpoint availability check for Wordnet-Wikipedia/DBpedia instance mapping took 9.107589721679688e-05s
Availability | VoID file availability check for Wordnet-Wikipedia/DBpedia instance mapping took 0.0006952285766601562s
Completeness | Calculation of interlinking completeness for Wordnet-Wikipedia/DBpedia instance mapping took 0.2991483211517334s
Reputation | Calculation of the PageRank for Wordnet-Wikipedia/DBpedia instance mapping took 0.02161550521850586s
Interlinking | Calculation of Degree of Connection for Wordnet-Wikipedia/DBpedia instance mapping took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Wordnet-Wikipedia/DBpedia instance mapping took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Wordnet-Wikipedia/DBpedia instance mapping took 7.367134094238281e-05s
Believability | Calculation of trust value for Wordnet-Wikipedia/DBpedia instance mapping took 1.3113021850585938e-05s
INFO | --- Analysis for wn-wiki-instances took 3.5236523151397705s
Availability | SPARQL endpoint availability check for World Loanword Database took 0.3578629493713379s
Availability | VoID file availability check for World Loanword Database took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for World Loanword Database took 0.28266310691833496s
Reputation | Calculation of the PageRank for World Loanword Database took 0.021764755249023438s
Interlinking | Calculation of Degree of Connection for World Loanword Database took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for World Loanword Database took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for World Loanword Database took 7.700920104980469e-05s
Believability | Calculation of trust value for World Loanword Database took 1.2874603271484375e-05s
INFO | --- Analysis for wold took 3.0247998237609863s
Availability | SPARQL endpoint availability check for Wood Trick LLC took 4.8160552978515625e-05s
Availability | VoID file availability check for Wood Trick LLC took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for Wood Trick LLC took 0.2856931686401367s
Reputation | Calculation of the PageRank for Wood Trick LLC took 0.021271467208862305s
Interlinking | Calculation of Degree of Connection for Wood Trick LLC took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Wood Trick LLC took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Wood Trick LLC took 3.5762786865234375e-05s
Believability | Calculation of trust value for Wood Trick LLC took 1.4781951904296875e-05s
INFO | --- Analysis for woodtrick took 3.242006778717041s
Availability | SPARQL endpoint availability check for Word Formation Latin (WFL) in LiLa took 0.4914693832397461s
Availability | VoID file availability check for Word Formation Latin (WFL) in LiLa took 0.0006544589996337891s
Completeness | Calculation of interlinking completeness for Word Formation Latin (WFL) in LiLa took 0.3096351623535156s
Reputation | Calculation of the PageRank for Word Formation Latin (WFL) in LiLa took 0.022474288940429688s
Interlinking | Calculation of Degree of Connection for Word Formation Latin (WFL) in LiLa took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Word Formation Latin (WFL) in LiLa took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Word Formation Latin (WFL) in LiLa took 4.3392181396484375e-05s
Believability | Calculation of trust value for Word Formation Latin (WFL) in LiLa took 1.0728836059570312e-05s
INFO | --- Analysis for WordFormationLatin took 4.276884078979492s
Availability | SPARQL endpoint availability check for WordLift Blog EN took 5.53131103515625e-05s
Availability | VoID file availability check for WordLift Blog EN took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for WordLift Blog EN took 0.30001068115234375s
Reputation | Calculation of the PageRank for WordLift Blog EN took 0.0212857723236084s
Interlinking | Calculation of Degree of Connection for WordLift Blog EN took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for WordLift Blog EN took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for WordLift Blog EN took 0.000110626220703125s
Believability | Calculation of trust value for WordLift Blog EN took 1.3828277587890625e-05s
INFO | --- Analysis for wordlift-io-blog-en took 5.228877782821655s
Availability | SPARQL endpoint availability check for WordLift IT took 9.083747863769531e-05s
Availability | VoID file availability check for WordLift IT took 0.00029754638671875s
Completeness | Calculation of interlinking completeness for WordLift IT took 0.32976865768432617s
Reputation | Calculation of the PageRank for WordLift IT took 0.020863771438598633s
Interlinking | Calculation of Degree of Connection for WordLift IT took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for WordLift IT took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for WordLift IT took 0.00011181831359863281s
Believability | Calculation of trust value for WordLift IT took 1.4543533325195312e-05s
INFO | --- Analysis for wordlift-io-blog-it took 6.277977228164673s
Availability | SPARQL endpoint availability check for WordNet-RDF took 9.107589721679688e-05s
Availability | VoID file availability check for WordNet-RDF took 0.0005812644958496094s
Completeness | Calculation of interlinking completeness for WordNet-RDF took 0.2899479866027832s
Reputation | Calculation of the PageRank for WordNet-RDF took 0.021477937698364258s
Interlinking | Calculation of Degree of Connection for WordNet-RDF took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for WordNet-RDF took 0.0009961128234863281s
Interlinking | Calculation of Clustering coefficient for WordNet-RDF took 0.00010633468627929688s
Believability | Calculation of trust value for WordNet-RDF took 1.0251998901367188e-05s
INFO | --- Analysis for wordnet-rdf took 2.7168867588043213s
Availability | SPARQL endpoint availability check for wordpress took 4.57763671875e-05s
Availability | VoID file availability check for wordpress took 0.0008127689361572266s
Completeness | Calculation of interlinking completeness for wordpress took 0.30254077911376953s
Reputation | Calculation of the PageRank for wordpress took 0.021071434020996094s
Interlinking | Calculation of Degree of Connection for wordpress took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for wordpress took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for wordpress took 0.00010514259338378906s
Believability | Calculation of trust value for wordpress took 1.5020370483398438e-05s
INFO | --- Analysis for wordpress took 3.2141060829162598s
Availability | SPARQL endpoint availability check for World Bank Linked Data took 0.10172843933105469s
Availability | VoID file availability check for World Bank Linked Data took 0.0005915164947509766s
Completeness | Calculation of interlinking completeness for World Bank Linked Data took 0.2779428958892822s
Reputation | Calculation of the PageRank for World Bank Linked Data took 0.020673513412475586s
Interlinking | Calculation of Degree of Connection for World Bank Linked Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for World Bank Linked Data took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for World Bank Linked Data took 0.0001518726348876953s
Believability | Calculation of trust value for World Bank Linked Data took 1.0967254638671875e-05s
INFO | --- Analysis for world-bank-linked-data took 2.883291244506836s
Availability | SPARQL endpoint availability check for World Factbook (FU Berlin) took 1.2361509799957275s
Availability | VoID file availability check for World Factbook (FU Berlin) took 0.0006279945373535156s
Completeness | Calculation of interlinking completeness for World Factbook (FU Berlin) took 0.303525447845459s
Reputation | Calculation of the PageRank for World Factbook (FU Berlin) took 0.02063465118408203s
Interlinking | Calculation of Degree of Connection for World Factbook (FU Berlin) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for World Factbook (FU Berlin) took 0.0008096694946289062s
Interlinking | Calculation of Clustering coefficient for World Factbook (FU Berlin) took 9.34600830078125e-05s
Believability | Calculation of trust value for World Factbook (FU Berlin) took 1.430511474609375e-05s
INFO | --- Analysis for world-factbook-fu-berlin took 5.798444747924805s
Availability | SPARQL endpoint availability check for World Wide Web Foundation took 9.489059448242188e-05s
Availability | VoID file availability check for World Wide Web Foundation took 0.0006918907165527344s
Completeness | Calculation of interlinking completeness for World Wide Web Foundation took 0.3115427494049072s
Reputation | Calculation of the PageRank for World Wide Web Foundation took 0.02062821388244629s
Interlinking | Calculation of Degree of Connection for World Wide Web Foundation took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for World Wide Web Foundation took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for World Wide Web Foundation took 9.202957153320312e-05s
Believability | Calculation of trust value for World Wide Web Foundation took 6.4373016357421875e-06s
INFO | --- Analysis for world-wide-web-foundation took 3.4068057537078857s
Availability | SPARQL endpoint availability check for World War 1 as Linked Open Data took 0.3800184726715088s
Availability | VoID file availability check for World War 1 as Linked Open Data took 0.0006191730499267578s
Extra | Recovery of all triples for World War 1 as Linked Open Data took 5.137171745300293s
Performance | Total latancy measurement for World War 1 as Linked Open Data took 0.8444139957427979s
Amount of data | Number of triples check for World War 1 as Linked Open Data took 0.2473764419555664s
Interoperability | New terms check for World War 1 as Linked Open Data took 1.6406548023223877s
Versatility | Languages check for World War 1 as Linked Open Data took 0.3487424850463867s
Interpretability | Number of blank nodes check for World War 1 as Linked Open Data took 0.2610146999359131s
Security | Check HTTPS for World War 1 as Linked Open Data took 0.38971519470214844s
Interpretability | RDF structures check for World War 1 as Linked Open Data took 0.29265713691711426s
Versatility | Serialization formats check for World War 1 as Linked Open Data took 0.25135064125061035s
Availability | RDF dump link check for World War 1 as Linked Open Data took 6.6076579093933105s
License | MR license check for World War 1 as Linked Open Data took 0.21803998947143555s
License | HR license check for World War 1 as Linked Open Data took 1.653890609741211s
Amount of data | Number of property check for World War 1 as Linked Open Data took 0.19432997703552246s
Understandability | Number of label check for World War 1 as Linked Open Data took 0.5340197086334229s
Understandability | URI regex check for World War 1 as Linked Open Data took 0.38074421882629395s
Understandability | Vocabs check for World War 1 as Linked Open Data took 0.37401747703552246s
Verifiability | Authors check for World War 1 as Linked Open Data took 0.20552897453308105s
Verifiability | Publishers check for World War 1 as Linked Open Data took 0.19095492362976074s
Performance | Throughput check for World War 1 as Linked Open Data took 11.163294792175293s
Amount of data | Check the number of entities for World War 1 as Linked Open Data took 0.0754239559173584s
Verifiability | Contribs. check for World War 1 as Linked Open Data took 0.19541239738464355s
Interlinking | sameAs chians check for World War 1 as Linked Open Data took 0.2446279525756836s
Interlinking | skos check for World War 1 as Linked Open Data took 0.19767093658447266s
Interlinking | skos check for World War 1 as Linked Open Data took 0.1886439323425293s
Timeliness | dataset update frequency check for World War 1 as Linked Open Data took 0.18613815307617188s
Currency | Creation date check for World War 1 as Linked Open Data took 0.3843801021575928s
Currency | Modification date check for World War 1 as Linked Open Data took 0.19231486320495605s
Rep.Conc. | URIs length for World War 1 as Linked Open Data took 2.008056163787842s
Interoperability | New vocabularies check for World War 1 as Linked Open Data took 34.378588914871216s
Consistency | Deprecated classes/propertiers check for World War 1 as Linked Open Data took 0.22237539291381836s
Accuracy | Check Functional Property for World War 1 as Linked Open Data took 0.20048069953918457s
Accuracy | Check Inverse Functional Property for World War 1 as Linked Open Data took 0.1594250202178955s
Accuracy | Check Empty annotation labels for World War 1 as Linked Open Data took 1.1902921199798584s
Accuracy | Check White space in annotation for World War 1 as Linked Open Data took 0.04992055892944336s
Accuracy | Check Datatype consistency for World War 1 as Linked Open Data took 0.32238221168518066s
Consistency | Disjoint class check for World War 1 as Linked Open Data took 0.193572998046875s
Consistency | Check Misplaced properties for World War 1 as Linked Open Data took 0.6162152290344238s
Consistency | Check Ontology hijacking for World War 1 as Linked Open Data took 2.160008668899536s
Consistency | Check Invalid usage of undefined classes for World War 1 as Linked Open Data took 1.4543895721435547s
Consistency | Check Invalid usage of undefined properties for World War 1 as Linked Open Data took 1.6901886463165283s
Conciseness | Check Extensional conciseness for World War 1 as Linked Open Data took 0.19485139846801758s
Security | Sign check for World War 1 as Linked Open Data took 0.18181300163269043s
Availability | Check URIs Dereferenciability for World War 1 as Linked Open Data took 5.22703742980957s
Completeness | Calculation of interlinking completeness for World War 1 as Linked Open Data took 0.2903151512145996s
Reputation | Calculation of the PageRank for World War 1 as Linked Open Data took 0.020966529846191406s
Interlinking | Calculation of Degree of Connection for World War 1 as Linked Open Data took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for World War 1 as Linked Open Data took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for World War 1 as Linked Open Data took 9.5367431640625e-05s
Interoperability | Check the re-using of existing vocabs for World War 1 as Linked Open Data took 37.40034294128418s
Believability | Calculation of trust value for World War 1 as Linked Open Data took 1.0967254638671875e-05s
INFO | --- Analysis for ww1lod took 154.8817901611328s
Availability | SPARQL endpoint availability check for xLiD-Lexica took 0.3545069694519043s
Availability | VoID file availability check for xLiD-Lexica took 0.00033664703369140625s
Completeness | Calculation of interlinking completeness for xLiD-Lexica took 0.2746868133544922s
Reputation | Calculation of the PageRank for xLiD-Lexica took 0.020677566528320312s
Interlinking | Calculation of Degree of Connection for xLiD-Lexica took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for xLiD-Lexica took 0.0007863044738769531s
Interlinking | Calculation of Clustering coefficient for xLiD-Lexica took 7.343292236328125e-05s
Believability | Calculation of trust value for xLiD-Lexica took 1.4543533325195312e-05s
INFO | --- Analysis for xlid-lexica took 4.34994912147522s
Availability | SPARQL endpoint availability check for Open Multilingual Wordnet took 8.869171142578125e-05s
Availability | VoID file availability check for Open Multilingual Wordnet took 0.0003108978271484375s
Completeness | Calculation of interlinking completeness for Open Multilingual Wordnet took 0.2910287380218506s
Reputation | Calculation of the PageRank for Open Multilingual Wordnet took 0.02162790298461914s
Interlinking | Calculation of Degree of Connection for Open Multilingual Wordnet took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Open Multilingual Wordnet took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Open Multilingual Wordnet took 4.3392181396484375e-05s
Believability | Calculation of trust value for Open Multilingual Wordnet took 9.775161743164062e-06s
INFO | --- Analysis for xwn took 2.9889490604400635s
Availability | SPARQL endpoint availability check for xxx took 8.940696716308594e-05s
Availability | VoID file availability check for xxx took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for xxx took 0.27903175354003906s
Reputation | Calculation of the PageRank for xxx took 0.020821332931518555s
Interlinking | Calculation of Degree of Connection for xxx took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for xxx took 0.0007836818695068359s
Interlinking | Calculation of Clustering coefficient for xxx took 3.504753112792969e-05s
Believability | Calculation of trust value for xxx took 1.4066696166992188e-05s
INFO | --- Analysis for xx took 2.7162914276123047s
Availability | SPARQL endpoint availability check for YAGO took 9.012222290039062e-05s
Availability | VoID file availability check for YAGO took 0.0008213520050048828s
Completeness | Calculation of interlinking completeness for YAGO took 0.3502006530761719s
Reputation | Calculation of the PageRank for YAGO took 0.020907163619995117s
Interlinking | Calculation of Degree of Connection for YAGO took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for YAGO took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for YAGO took 0.00013780593872070312s
Believability | Calculation of trust value for YAGO took 3.0994415283203125e-05s
INFO | --- Analysis for yago took 4.680760383605957s
Availability | SPARQL endpoint availability check for Yahoo Geoplanet RDF took 2.7568199634552s
Availability | VoID file availability check for Yahoo Geoplanet RDF took 0.0006153583526611328s
Completeness | Calculation of interlinking completeness for Yahoo Geoplanet RDF took 0.3088371753692627s
Reputation | Calculation of the PageRank for Yahoo Geoplanet RDF took 0.020559072494506836s
Interlinking | Calculation of Degree of Connection for Yahoo Geoplanet RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Yahoo Geoplanet RDF took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Yahoo Geoplanet RDF took 8.106231689453125e-05s
Believability | Calculation of trust value for Yahoo Geoplanet RDF took 1.4781951904296875e-05s
INFO | --- Analysis for yahoo_geoplanet took 29.478889226913452s
Availability | SPARQL endpoint availability check for Yale Senselab took 0.16419410705566406s
Availability | VoID file availability check for Yale Senselab took 0.00031065940856933594s
Completeness | Calculation of interlinking completeness for Yale Senselab took 0.3207077980041504s
Reputation | Calculation of the PageRank for Yale Senselab took 0.020806550979614258s
Interlinking | Calculation of Degree of Connection for Yale Senselab took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Yale Senselab took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for Yale Senselab took 4.3392181396484375e-05s
Believability | Calculation of trust value for Yale Senselab took 1.049041748046875e-05s
INFO | --- Analysis for yale_senselab took 11.375197410583496s
Availability | SPARQL endpoint availability check for test-dapp-2 took 4.458427429199219e-05s
Availability | VoID file availability check for test-dapp-2 took 0.0003056526184082031s
Completeness | Calculation of interlinking completeness for test-dapp-2 took 0.29764461517333984s
Reputation | Calculation of the PageRank for test-dapp-2 took 0.021192312240600586s
Interlinking | Calculation of Degree of Connection for test-dapp-2 took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for test-dapp-2 took 0.0009303092956542969s
Interlinking | Calculation of Clustering coefficient for test-dapp-2 took 3.9577484130859375e-05s
Believability | Calculation of trust value for test-dapp-2 took 9.298324584960938e-06s
INFO | --- Analysis for yordhis took 2.716390609741211s
Availability | SPARQL endpoint availability check for Yovisto - academic video search took 0.8329765796661377s
Availability | VoID file availability check for Yovisto - academic video search took 0.0006136894226074219s
Completeness | Calculation of interlinking completeness for Yovisto - academic video search took 0.28595900535583496s
Reputation | Calculation of the PageRank for Yovisto - academic video search took 0.020699024200439453s
Interlinking | Calculation of Degree of Connection for Yovisto - academic video search took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Yovisto - academic video search took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Yovisto - academic video search took 7.581710815429688e-05s
Believability | Calculation of trust value for Yovisto - academic video search took 6.67572021484375e-06s
INFO | --- Analysis for yovisto took 24.197973489761353s
Availability | SPARQL endpoint availability check for YSA - General Finnish Thesaurus took 4.482269287109375e-05s
Availability | VoID file availability check for YSA - General Finnish Thesaurus took 0.0007796287536621094s
Completeness | Calculation of interlinking completeness for YSA - General Finnish Thesaurus took 0.295682430267334s
Reputation | Calculation of the PageRank for YSA - General Finnish Thesaurus took 0.021187305450439453s
Interlinking | Calculation of Degree of Connection for YSA - General Finnish Thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for YSA - General Finnish Thesaurus took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for YSA - General Finnish Thesaurus took 3.886222839355469e-05s
Believability | Calculation of trust value for YSA - General Finnish Thesaurus took 1.049041748046875e-05s
INFO | --- Analysis for ysa took 4.176075458526611s
Availability | SPARQL endpoint availability check for YSO - General Finnish Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for YSO - General Finnish Ontology took 0.0007994174957275391s
Completeness | Calculation of interlinking completeness for YSO - General Finnish Ontology took 0.32016992568969727s
Reputation | Calculation of the PageRank for YSO - General Finnish Ontology took 0.021002531051635742s
Interlinking | Calculation of Degree of Connection for YSO - General Finnish Ontology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for YSO - General Finnish Ontology took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for YSO - General Finnish Ontology took 8.511543273925781e-05s
Believability | Calculation of trust value for YSO - General Finnish Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for yso took 4.482117414474487s
Availability | SPARQL endpoint availability check for yso-fi-allars took 4.649162292480469e-05s
Availability | VoID file availability check for yso-fi-allars took 0.00036144256591796875s
Completeness | Calculation of interlinking completeness for yso-fi-allars took 0.31052684783935547s
Reputation | Calculation of the PageRank for yso-fi-allars took 0.020745515823364258s
Interlinking | Calculation of Degree of Connection for yso-fi-allars took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for yso-fi-allars took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for yso-fi-allars took 3.8623809814453125e-05s
Believability | Calculation of trust value for yso-fi-allars took 9.775161743164062e-06s
INFO | --- Analysis for yso-fi-allars took 3.3188209533691406s
Availability | SPARQL endpoint availability check for yso-fi-ysa took 4.38690185546875e-05s
Availability | VoID file availability check for yso-fi-ysa took 0.0013401508331298828s
Completeness | Calculation of interlinking completeness for yso-fi-ysa took 0.290081262588501s
Reputation | Calculation of the PageRank for yso-fi-ysa took 0.021147966384887695s
Interlinking | Calculation of Degree of Connection for yso-fi-ysa took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for yso-fi-ysa took 0.0008180141448974609s
Interlinking | Calculation of Clustering coefficient for yso-fi-ysa took 4.124641418457031e-05s
Believability | Calculation of trust value for yso-fi-ysa took 2.5272369384765625e-05s
INFO | --- Analysis for yso-fi-ysa took 3.2359514236450195s
Availability | SPARQL endpoint availability check for YSO places took 0.6992862224578857s
Availability | VoID file availability check for YSO places took 0.0006911754608154297s
Completeness | Calculation of interlinking completeness for YSO places took 0.31696605682373047s
Reputation | Calculation of the PageRank for YSO places took 0.022168636322021484s
Interlinking | Calculation of Degree of Connection for YSO places took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for YSO places took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for YSO places took 3.647804260253906e-05s
Believability | Calculation of trust value for YSO places took 1.33514404296875e-05s
INFO | --- Analysis for yso-paikat took 4.452005624771118s
Availability | SPARQL endpoint availability check for Datos Abiertos de Zaragoza took 4.506111145019531e-05s
Availability | VoID file availability check for Datos Abiertos de Zaragoza took 0.0006923675537109375s
Completeness | Calculation of interlinking completeness for Datos Abiertos de Zaragoza took 0.35950732231140137s
Reputation | Calculation of the PageRank for Datos Abiertos de Zaragoza took 0.020860910415649414s
Interlinking | Calculation of Degree of Connection for Datos Abiertos de Zaragoza took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Datos Abiertos de Zaragoza took 0.0007913112640380859s
Interlinking | Calculation of Clustering coefficient for Datos Abiertos de Zaragoza took 4.076957702636719e-05s
Believability | Calculation of trust value for Datos Abiertos de Zaragoza took 5.9604644775390625e-06s
INFO | --- Analysis for zaragoza-datosabiertos took 6.424133539199829s
Availability | SPARQL endpoint availability check for zaragoza_turruta took 4.5299530029296875e-05s
Availability | VoID file availability check for zaragoza_turruta took 0.0005743503570556641s
Completeness | Calculation of interlinking completeness for zaragoza_turruta took 0.28786253929138184s
Reputation | Calculation of the PageRank for zaragoza_turruta took 0.020864486694335938s
Interlinking | Calculation of Degree of Connection for zaragoza_turruta took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for zaragoza_turruta took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for zaragoza_turruta took 3.981590270996094e-05s
Believability | Calculation of trust value for zaragoza_turruta took 1.239776611328125e-05s
INFO | --- Analysis for zaragoza_turruta took 3.021228790283203s
Availability | SPARQL endpoint availability check for ZBW Labs took 9.179115295410156e-05s
Availability | VoID file availability check for ZBW Labs took 0.0006361007690429688s
Completeness | Calculation of interlinking completeness for ZBW Labs took 0.28456830978393555s
Reputation | Calculation of the PageRank for ZBW Labs took 0.021512508392333984s
Interlinking | Calculation of Degree of Connection for ZBW Labs took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for ZBW Labs took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for ZBW Labs took 7.486343383789062e-05s
Believability | Calculation of trust value for ZBW Labs took 1.430511474609375e-05s
INFO | --- Analysis for zbw-labs took 3.8299343585968018s
Availability | SPARQL endpoint availability check for 20th Century Press Archives took 0.17990732192993164s
Availability | VoID file availability check for 20th Century Press Archives took 0.0006840229034423828s
Extra | Recovery of all triples for 20th Century Press Archives took 20.6830415725708s
Performance | Total latancy measurement for 20th Century Press Archives took 0.7993121147155762s
Amount of data | Number of triples check for 20th Century Press Archives took 1.149585485458374s
Interoperability | New terms check for 20th Century Press Archives took 1.7996814250946045s
Versatility | Languages check for 20th Century Press Archives took 3.3007678985595703s
Interpretability | Number of blank nodes check for 20th Century Press Archives took 0.958437442779541s
Interpretability | RDF structures check for 20th Century Press Archives took 0.15479445457458496s
Versatility | Serialization formats check for 20th Century Press Archives took 0.13578057289123535s
Availability | RDF dump link check for 20th Century Press Archives took 0.16276121139526367s
License | MR license check for 20th Century Press Archives took 0.15333008766174316s
License | HR license check for 20th Century Press Archives took 5.420140743255615s
Amount of data | Number of property check for 20th Century Press Archives took 0.16239190101623535s
Understandability | Number of label check for 20th Century Press Archives took 0.6088137626647949s
Understandability | URI regex check for 20th Century Press Archives took 0.31247806549072266s
Understandability | Vocabs check for 20th Century Press Archives took 0.12894272804260254s
Verifiability | Authors check for 20th Century Press Archives took 0.1317615509033203s
Verifiability | Publishers check for 20th Century Press Archives took 0.16761445999145508s
Performance | Throughput check for 20th Century Press Archives took 10.546078205108643s
Amount of data | Check the number of entities for 20th Century Press Archives took 3.266334533691406e-05s
Verifiability | Contribs. check for 20th Century Press Archives took 0.14683127403259277s
Interlinking | sameAs chians check for 20th Century Press Archives took 0.13081789016723633s
Interlinking | skos check for 20th Century Press Archives took 0.18465876579284668s
Interlinking | skos check for 20th Century Press Archives took 0.20834970474243164s
Timeliness | dataset update frequency check for 20th Century Press Archives took 0.14202213287353516s
Currency | Creation date check for 20th Century Press Archives took 0.3085191249847412s
Currency | Modification date check for 20th Century Press Archives took 0.2718470096588135s
Rep.Conc. | URIs length for 20th Century Press Archives took 15.919176816940308s
Interoperability | New vocabularies check for 20th Century Press Archives took 1.1682510375976562e-05s
Consistency | Deprecated classes/propertiers check for 20th Century Press Archives took 0.14784884452819824s
Accuracy | Check Functional Property for 20th Century Press Archives took 0.14859628677368164s
Accuracy | Check Inverse Functional Property for 20th Century Press Archives took 0.15445470809936523s
Accuracy | Check Empty annotation labels for 20th Century Press Archives took 5.6542603969573975s
Accuracy | Check White space in annotation for 20th Century Press Archives took 0.8875024318695068s
Accuracy | Check Datatype consistency for 20th Century Press Archives took 4.1791253089904785s
Consistency | Disjoint class check for 20th Century Press Archives took 0.1886894702911377s
Consistency | Check Misplaced properties for 20th Century Press Archives took 2.266395092010498s
Consistency | Check Ontology hijacking for 20th Century Press Archives took 2.699960947036743s
Consistency | Check Invalid usage of undefined classes for 20th Century Press Archives took 7.179700613021851s
Consistency | Check Invalid usage of undefined properties for 20th Century Press Archives took 3.727297067642212s
Conciseness | Check Extensional conciseness for 20th Century Press Archives took 2.850369691848755s
Security | Sign check for 20th Century Press Archives took 0.14829015731811523s
Availability | Check URIs Dereferenciability for 20th Century Press Archives took 975.7529125213623s
Completeness | Calculation of interlinking completeness for 20th Century Press Archives took 0.5658502578735352s
Reputation | Calculation of the PageRank for 20th Century Press Archives took 0.021473407745361328s
Interlinking | Calculation of Degree of Connection for 20th Century Press Archives took 7.152557373046875e-05s
Interlinking | Calculation of Centrality for 20th Century Press Archives took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for 20th Century Press Archives took 0.00011873245239257812s
Interoperability | Check the re-using of existing vocabs for 20th Century Press Archives took 9.298324584960938e-06s
Believability | Calculation of trust value for 20th Century Press Archives took 2.0503997802734375e-05s
INFO | --- Analysis for zbw-pressemappe20 took 1092.4983382225037s
Availability | SPARQL endpoint availability check for zhishi.lemon took 4.506111145019531e-05s
Availability | VoID file availability check for zhishi.lemon took 0.0007784366607666016s
Completeness | Calculation of interlinking completeness for zhishi.lemon took 0.3229517936706543s
Reputation | Calculation of the PageRank for zhishi.lemon took 0.02126169204711914s
Interlinking | Calculation of Degree of Connection for zhishi.lemon took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for zhishi.lemon took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for zhishi.lemon took 4.8160552978515625e-05s
Believability | Calculation of trust value for zhishi.lemon took 1.33514404296875e-05s
INFO | --- Analysis for zhishi-lemon took 25.30805492401123s
Availability | SPARQL endpoint availability check for Zhishi.me took 10.08483338356018s
Availability | VoID file availability check for Zhishi.me took 0.0005931854248046875s
Completeness | Calculation of interlinking completeness for Zhishi.me took 0.2958846092224121s
Reputation | Calculation of the PageRank for Zhishi.me took 0.02064061164855957s
Interlinking | Calculation of Degree of Connection for Zhishi.me took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Zhishi.me took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Zhishi.me took 7.462501525878906e-05s
Believability | Calculation of trust value for Zhishi.me took 1.4781951904296875e-05s
INFO | --- Analysis for zhishi-me took 15.312448501586914s
Availability | SPARQL endpoint availability check for MusicBrainz (zitgist.com) took 9.179115295410156e-05s
Availability | VoID file availability check for MusicBrainz (zitgist.com) took 0.0006051063537597656s
Completeness | Calculation of interlinking completeness for MusicBrainz (zitgist.com) took 0.3244357109069824s
Reputation | Calculation of the PageRank for MusicBrainz (zitgist.com) took 0.020899057388305664s
Interlinking | Calculation of Degree of Connection for MusicBrainz (zitgist.com) took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for MusicBrainz (zitgist.com) took 0.0010156631469726562s
Interlinking | Calculation of Clustering coefficient for MusicBrainz (zitgist.com) took 8.034706115722656e-05s
Believability | Calculation of trust value for MusicBrainz (zitgist.com) took 1.4066696166992188e-05s
INFO | --- Analysis for zitgist-musicbrainz took 3.4355151653289795s
Availability | SPARQL endpoint availability check for 红色经典歌曲关联数据集 took 5.364418029785156e-05s
Availability | VoID file availability check for 红色经典歌曲关联数据集 took 0.0008041858673095703s
Completeness | Calculation of interlinking completeness for 红色经典歌曲关联数据集 took 0.27937841415405273s
Reputation | Calculation of the PageRank for 红色经典歌曲关联数据集 took 0.0210878849029541s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲关联数据集 took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲关联数据集 took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲关联数据集 took 3.504753112792969e-05s
Believability | Calculation of trust value for 红色经典歌曲关联数据集 took 1.430511474609375e-05s
INFO | --- Analysis for 红色经典歌曲关联数据集 took 2.988093852996826s
Availability | SPARQL endpoint availability check for performing-arts.ch took 0.3608396053314209s
Availability | VoID file availability check for performing-arts.ch took 0.0005261898040771484s
Extra | Recovery of all triples for performing-arts.ch took 18.38120412826538s
Performance | Total latancy measurement for performing-arts.ch took 0.7736363410949707s
Amount of data | Number of triples check for performing-arts.ch took 37.03033113479614s
Interoperability | New terms check for performing-arts.ch took 1.6976499557495117s
Versatility | Languages check for performing-arts.ch took 60.153905391693115s
Interpretability | Number of blank nodes check for performing-arts.ch took 60.15394973754883s
Interpretability | RDF structures check for performing-arts.ch took 0.15586566925048828s
Versatility | Serialization formats check for performing-arts.ch took 0.1485741138458252s
Availability | RDF dump link check for performing-arts.ch took 0.17072081565856934s
License | MR license check for performing-arts.ch took 0.18132472038269043s
License | HR license check for performing-arts.ch took 47.075626373291016s
Amount of data | Number of property check for performing-arts.ch took 0.17540311813354492s
Understandability | Number of label check for performing-arts.ch took 3.9789206981658936s
Understandability | URI regex check for performing-arts.ch took 0.2977304458618164s
Understandability | Vocabs check for performing-arts.ch took 0.16239666938781738s
Verifiability | Authors check for performing-arts.ch took 0.16395998001098633s
Verifiability | Publishers check for performing-arts.ch took 0.16080784797668457s
Performance | Throughput check for performing-arts.ch took 10.728589296340942s
Amount of data | Check the number of entities for performing-arts.ch took 0.00013947486877441406s
Verifiability | Contribs. check for performing-arts.ch took 0.17841696739196777s
Interlinking | sameAs chians check for performing-arts.ch took 0.599076509475708s
Interlinking | skos check for performing-arts.ch took 0.15593409538269043s
Interlinking | skos check for performing-arts.ch took 0.15626811981201172s
Timeliness | dataset update frequency check for performing-arts.ch took 0.1479625701904297s
Currency | Creation date check for performing-arts.ch took 0.28664445877075195s
Currency | Modification date check for performing-arts.ch took 0.32236409187316895s
Rep.Conc. | URIs length for performing-arts.ch took 25.136028051376343s
Interoperability | New vocabularies check for performing-arts.ch took 1.1682510375976562e-05s
Consistency | Deprecated classes/propertiers check for performing-arts.ch took 0.15486860275268555s
Accuracy | Check Functional Property for performing-arts.ch took 0.15474557876586914s
Accuracy | Check Inverse Functional Property for performing-arts.ch took 0.16944503784179688s
Accuracy | Check Empty annotation labels for performing-arts.ch took 10.95836877822876s
Accuracy | Check White space in annotation for performing-arts.ch took 2.5715863704681396s
Accuracy | Check Datatype consistency for performing-arts.ch took 6.037030935287476s
Consistency | Disjoint class check for performing-arts.ch took 0.15397429466247559s
Consistency | Check Misplaced properties for performing-arts.ch took 0.4207940101623535s
Consistency | Misplaced classes for performing-arts.ch took 8.773735284805298s
Consistency | Check Ontology hijacking for performing-arts.ch took 42.28414583206177s
Consistency | Check Invalid usage of undefined classes for performing-arts.ch took 21733.39999938011s
Consistency | Check Invalid usage of undefined properties for performing-arts.ch took 2.083340883255005s
Conciseness | Check Extensional conciseness for performing-arts.ch took 2.9812276363372803s
Conciseness | Check Intensional conciseness for performing-arts.ch took 0.30844831466674805s
Security | Sign check for performing-arts.ch took 0.15847420692443848s
Availability | Check URIs Dereferenciability for performing-arts.ch took 3.5678226947784424s
Completeness | Calculation of interlinking completeness for performing-arts.ch took 0.7920153141021729s
Reputation | Calculation of the PageRank for performing-arts.ch took 0.021442413330078125s
Interlinking | Calculation of Degree of Connection for performing-arts.ch took 2.384185791015625e-05s
Interlinking | Calculation of Centrality for performing-arts.ch took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for performing-arts.ch took 1.430511474609375e-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.5020370483398438e-05s
INFO | --- Analysis for performing-arts.ch took 22558.645054101944s
Availability | SPARQL endpoint availability check for The Art & Architecture Thesaurus took 3.0148143768310547s
Availability | VoID file availability check for The Art & Architecture Thesaurus took 0.0006134510040283203s
Completeness | Calculation of interlinking completeness for The Art & Architecture Thesaurus took 0.3119328022003174s
Reputation | Calculation of the PageRank for The Art & Architecture Thesaurus took 0.02099299430847168s
Interlinking | Calculation of Degree of Connection for The Art & Architecture Thesaurus took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for The Art & Architecture Thesaurus took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for The Art & Architecture Thesaurus took 1.5020370483398438e-05s
Believability | Calculation of trust value for The Art & Architecture Thesaurus took 1.3589859008789062e-05s
INFO | --- Analysis for The-AA-Thesaurus took 9.073345422744751s
Availability | SPARQL endpoint availability check for MiMoTextBase took 1.6975188255310059s
Availability | VoID file availability check for MiMoTextBase took 0.0007679462432861328s
Completeness | Calculation of interlinking completeness for MiMoTextBase took 0.294506311416626s
Reputation | Calculation of the PageRank for MiMoTextBase took 0.021178722381591797s
Interlinking | Calculation of Degree of Connection for MiMoTextBase took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for MiMoTextBase took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for MiMoTextBase took 1.9311904907226562e-05s
Believability | Calculation of trust value for MiMoTextBase took 1.52587890625e-05s
INFO | --- Analysis for MiMoTextBase took 6.4409284591674805s
Availability | SPARQL endpoint availability check for National Library of Sweden took 0.5377962589263916s
Availability | VoID file availability check for National Library of Sweden took 0.000659942626953125s
Extra | Recovery of all triples for National Library of Sweden took 5.620612859725952s
Performance | Total latancy measurement for National Library of Sweden took 1.0190513134002686s
Amount of data | Number of triples check for National Library of Sweden took 29.539401531219482s
Interoperability | New terms check for National Library of Sweden took 17.797214031219482s
Versatility | Languages check for National Library of Sweden took 0.20787954330444336s
Interpretability | Number of blank nodes check for National Library of Sweden took 300.2277545928955s
Interpretability | RDF structures check for National Library of Sweden took 0.2707939147949219s
Versatility | Serialization formats check for National Library of Sweden took 0.22038507461547852s
Availability | RDF dump link check for National Library of Sweden took 0.19597148895263672s
License | MR license check for National Library of Sweden took 0.22220993041992188s
License | HR license check for National Library of Sweden took 0.25716066360473633s
Amount of data | Number of property check for National Library of Sweden took 0.21927881240844727s
Understandability | Number of label check for National Library of Sweden took 0.2270674705505371s
Understandability | URI regex check for National Library of Sweden took 0.456923246383667s
Understandability | Vocabs check for National Library of Sweden took 0.20646047592163086s
Verifiability | Authors check for National Library of Sweden took 0.21561908721923828s
Verifiability | Publishers check for National Library of Sweden took 0.21565508842468262s
Performance | Throughput check for National Library of Sweden took 10.197365999221802s
Amount of data | Check the number of entities for National Library of Sweden took 7.510185241699219e-05s
Verifiability | Contribs. check for National Library of Sweden took 0.2062358856201172s
Interlinking | sameAs chians check for National Library of Sweden took 0.2167339324951172s
Interlinking | skos check for National Library of Sweden took 0.19529008865356445s
Interlinking | skos check for National Library of Sweden took 0.20769762992858887s
Timeliness | dataset update frequency check for National Library of Sweden took 0.19803071022033691s
Currency | Creation date check for National Library of Sweden took 0.38956570625305176s
Currency | Modification date check for National Library of Sweden took 0.45761990547180176s
Rep.Conc. | URIs length for National Library of Sweden took 89.91985774040222s
Interoperability | New vocabularies check for National Library of Sweden took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for National Library of Sweden took 0.20650553703308105s
Accuracy | Check Functional Property for National Library of Sweden took 0.22835421562194824s
Accuracy | Check Inverse Functional Property for National Library of Sweden took 0.27224206924438477s
Accuracy | Check Datatype consistency for National Library of Sweden took 0.286618709564209s
Consistency | Disjoint class check for National Library of Sweden took 0.19367337226867676s
Consistency | Check Misplaced properties for National Library of Sweden took 70.45155310630798s
Consistency | Misplaced classes for National Library of Sweden took 1.1573197841644287s
Consistency | Check Ontology hijacking for National Library of Sweden took 3.2715437412261963s
Consistency | Check Invalid usage of undefined classes for National Library of Sweden took 1.4270620346069336s
Consistency | Check Invalid usage of undefined properties for National Library of Sweden took 71.72600150108337s
Conciseness | Check Extensional conciseness for National Library of Sweden took 0.2879307270050049s
Conciseness | Check Intensional conciseness for National Library of Sweden took 0.35091471672058105s
Security | Sign check for National Library of Sweden took 0.22658777236938477s
Availability | Check URIs Dereferenciability for National Library of Sweden took 10.534386157989502s
Completeness | Calculation of interlinking completeness for National Library of Sweden took 0.4166250228881836s
Reputation | Calculation of the PageRank for National Library of Sweden took 0.02117753028869629s
Interlinking | Calculation of Degree of Connection for National Library of Sweden took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for National Library of Sweden took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for National Library of Sweden took 1.8835067749023438e-05s
Interoperability | Check the re-using of existing vocabs for National Library of Sweden took 2.1457672119140625e-06s
Believability | Calculation of trust value for National Library of Sweden took 1.621246337890625e-05s
INFO | --- Analysis for NLS took 1405.5108680725098s
Availability | SPARQL endpoint availability check for Japan Search took 1.8527510166168213s
Availability | VoID file availability check for Japan Search took 0.0005435943603515625s
Extra | Recovery of all triples for Japan Search took 3.884003162384033s
Performance | Total latancy measurement for Japan Search took 2.6794753074645996s
Amount of data | Number of triples check for Japan Search took 5.097320079803467s
Interoperability | New terms check for Japan Search took 3.3131439685821533s
Versatility | Languages check for Japan Search took 0.7674546241760254s
Interpretability | Number of blank nodes check for Japan Search took 12.299335718154907s
Interpretability | RDF structures check for Japan Search took 0.8529226779937744s
Versatility | Serialization formats check for Japan Search took 0.4084045886993408s
Availability | RDF dump link check for Japan Search took 1.0128982067108154s
License | MR license check for Japan Search took 0.5557305812835693s
License | HR license check for Japan Search took 11.203568696975708s
Amount of data | Number of property check for Japan Search took 0.31160497665405273s
Understandability | Number of label check for Japan Search took 2.389326572418213s
Understandability | URI regex check for Japan Search took 1.0331478118896484s
Understandability | Vocabs check for Japan Search took 0.3092513084411621s
Verifiability | Authors check for Japan Search took 0.35457706451416016s
Verifiability | Publishers check for Japan Search took 0.2890458106994629s
Performance | Throughput check for Japan Search took 11.971690654754639s
Amount of data | Check the number of entities for Japan Search took 7.677078247070312e-05s
Verifiability | Contribs. check for Japan Search took 0.26474881172180176s
Interlinking | sameAs chians check for Japan Search took 0.26589512825012207s
Interlinking | skos check for Japan Search took 0.3146069049835205s
Interlinking | skos check for Japan Search took 0.3099074363708496s
Timeliness | dataset update frequency check for Japan Search took 0.3929314613342285s
Currency | Creation date check for Japan Search took 0.5309197902679443s
Currency | Modification date check for Japan Search took 0.5735025405883789s
Rep.Conc. | URIs length for Japan Search took 13.663022518157959s
Interoperability | New vocabularies check for Japan Search took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for Japan Search took 0.26410531997680664s
Accuracy | Check Empty annotation labels for Japan Search took 0.6175212860107422s
Accuracy | Check White space in annotation for Japan Search took 0.029267311096191406s
Accuracy | Check Datatype consistency for Japan Search took 0.029514074325561523s
Consistency | Disjoint class check for Japan Search took 0.2624979019165039s
Consistency | Check Misplaced properties for Japan Search took 11.246751308441162s
Consistency | Misplaced classes for Japan Search took 1.080594778060913s
Consistency | Check Ontology hijacking for Japan Search took 2.756006956100464s
Consistency | Check Invalid usage of undefined classes for Japan Search took 1.4504969120025635s
Consistency | Check Invalid usage of undefined properties for Japan Search took 11.749951362609863s
Conciseness | Check Extensional conciseness for Japan Search took 0.03535628318786621s
Conciseness | Check Intensional conciseness for Japan Search took 0.9951255321502686s
Security | Sign check for Japan Search took 0.7244129180908203s
Availability | Check URIs Dereferenciability for Japan Search took 8.720141172409058s
Completeness | Calculation of interlinking completeness for Japan Search took 0.3227391242980957s
Reputation | Calculation of the PageRank for Japan Search took 0.02104020118713379s
Interlinking | Calculation of Degree of Connection for Japan Search took 7.891654968261719e-05s
Interlinking | Calculation of Centrality for Japan Search took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Japan Search took 2.3126602172851562e-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.4781951904296875e-05s
INFO | --- Analysis for Japan-Search took 403.2493097782135s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection took 1.1315765380859375s
Availability | VoID file availability check for Rijksmuseum Collection took 0.0005369186401367188s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection took 0.3031587600708008s
Reputation | Calculation of the PageRank for Rijksmuseum Collection took 0.0216064453125s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection took 1.4543533325195312e-05s
Believability | Calculation of trust value for Rijksmuseum Collection took 1.5735626220703125e-05s
INFO | --- Analysis for Rijksmuseum took 5.085994243621826s
Availability | SPARQL endpoint availability check for Finnish Public Libraries took 0.681053638458252s
Availability | VoID file availability check for Finnish Public Libraries took 0.0004744529724121094s
Extra | Recovery of all triples for Finnish Public Libraries took 36.685627460479736s
Performance | Total latancy measurement for Finnish Public Libraries took 1.5644614696502686s
Amount of data | Number of triples check for Finnish Public Libraries took 60.204413175582886s
Interoperability | New terms check for Finnish Public Libraries took 18.1726233959198s
Versatility | Languages check for Finnish Public Libraries took 60.202653884887695s
Interpretability | Number of blank nodes check for Finnish Public Libraries took 60.22859716415405s
Interpretability | RDF structures check for Finnish Public Libraries took 0.43077659606933594s
Versatility | Serialization formats check for Finnish Public Libraries took 0.2187800407409668s
Availability | RDF dump link check for Finnish Public Libraries took 0.13707351684570312s
License | MR license check for Finnish Public Libraries took 0.35826611518859863s
License | HR license check for Finnish Public Libraries took 49.95366048812866s
Amount of data | Number of property check for Finnish Public Libraries took 0.3057260513305664s
Understandability | Number of label check for Finnish Public Libraries took 17.08860731124878s
Understandability | URI regex check for Finnish Public Libraries took 0.6394343376159668s
Understandability | Vocabs check for Finnish Public Libraries took 0.1862788200378418s
Verifiability | Authors check for Finnish Public Libraries took 0.13468098640441895s
Verifiability | Publishers check for Finnish Public Libraries took 0.11730098724365234s
Performance | Throughput check for Finnish Public Libraries took 11.250806331634521s
Amount of data | Check the number of entities for Finnish Public Libraries took 6.961822509765625e-05s
Verifiability | Contribs. check for Finnish Public Libraries took 0.12738871574401855s
Interlinking | sameAs chians check for Finnish Public Libraries took 0.4088778495788574s
Interlinking | skos check for Finnish Public Libraries took 0.12782645225524902s
Interlinking | skos check for Finnish Public Libraries took 0.11775565147399902s
Timeliness | dataset update frequency check for Finnish Public Libraries took 0.11874794960021973s
Currency | Creation date check for Finnish Public Libraries took 0.33902502059936523s
Currency | Modification date check for Finnish Public Libraries took 0.24962234497070312s
Rep.Conc. | URIs length for Finnish Public Libraries took 85.78721952438354s
Interoperability | New vocabularies check for Finnish Public Libraries took 4.76837158203125e-06s
Consistency | Deprecated classes/propertiers check for Finnish Public Libraries took 0.31069326400756836s
Accuracy | Check Empty annotation labels for Finnish Public Libraries took 9.299502611160278s
Accuracy | Check White space in annotation for Finnish Public Libraries took 2.256380558013916s
Accuracy | Check Datatype consistency for Finnish Public Libraries took 4.582122325897217s
Consistency | Disjoint class check for Finnish Public Libraries took 0.13428115844726562s
Consistency | Check Misplaced properties for Finnish Public Libraries took 60.28530764579773s
Consistency | Check Ontology hijacking for Finnish Public Libraries took 19.36693525314331s
Consistency | Check Invalid usage of undefined classes for Finnish Public Libraries took 1.8373794555664062s
Consistency | Check Invalid usage of undefined properties for Finnish Public Libraries took 62.080668687820435s
Conciseness | Check Extensional conciseness for Finnish Public Libraries took 2.8224940299987793s
Security | Sign check for Finnish Public Libraries took 0.32094883918762207s
Availability | Check URIs Dereferenciability for Finnish Public Libraries took 1.0000214576721191s
Completeness | Calculation of interlinking completeness for Finnish Public Libraries took 0.5151076316833496s
Reputation | Calculation of the PageRank for Finnish Public Libraries took 0.021528244018554688s
Interlinking | Calculation of Degree of Connection for Finnish Public Libraries took 2.6702880859375e-05s
Interlinking | Calculation of Centrality for Finnish Public Libraries took 0.0021076202392578125s
Interlinking | Calculation of Clustering coefficient for Finnish Public Libraries took 6.461143493652344e-05s
Interoperability | Check the re-using of existing vocabs for Finnish Public Libraries took 7.3909759521484375e-06s
Believability | Calculation of trust value for Finnish Public Libraries took 1.4543533325195312e-05s
INFO | --- Analysis for FI-Library took 709.8240587711334s
Availability | SPARQL endpoint availability check for Shanghai Library Open Data Platform took 2.660334587097168s
Availability | VoID file availability check for Shanghai Library Open Data Platform took 0.00029969215393066406s
Extra | Recovery of all triples for Shanghai Library Open Data Platform took 10.183733940124512s
Performance | Total latancy measurement for Shanghai Library Open Data Platform took 3.500791549682617s
Amount of data | Number of triples check for Shanghai Library Open Data Platform took 1.2379484176635742s
Interoperability | New terms check for Shanghai Library Open Data Platform took 5.331511497497559s
Versatility | Languages check for Shanghai Library Open Data Platform took 60.69009351730347s
Interpretability | Number of blank nodes check for Shanghai Library Open Data Platform took 16.453301668167114s
Interpretability | RDF structures check for Shanghai Library Open Data Platform took 1.4566762447357178s
Versatility | Serialization formats check for Shanghai Library Open Data Platform took 1.0331206321716309s
Availability | RDF dump link check for Shanghai Library Open Data Platform took 0.7746400833129883s
License | MR license check for Shanghai Library Open Data Platform took 1.1317269802093506s
License | HR license check for Shanghai Library Open Data Platform took 36.80220818519592s
Amount of data | Number of property check for Shanghai Library Open Data Platform took 0.6986360549926758s
Understandability | Number of label check for Shanghai Library Open Data Platform took 1.5372099876403809s
Understandability | URI regex check for Shanghai Library Open Data Platform took 1.6551389694213867s
Understandability | Vocabs check for Shanghai Library Open Data Platform took 0.788102388381958s
Verifiability | Authors check for Shanghai Library Open Data Platform took 0.8668861389160156s
Verifiability | Publishers check for Shanghai Library Open Data Platform took 0.8218019008636475s
Performance | Throughput check for Shanghai Library Open Data Platform took 14.291677474975586s
Amount of data | Check the number of entities for Shanghai Library Open Data Platform took 3.4809112548828125e-05s
Verifiability | Contribs. check for Shanghai Library Open Data Platform took 0.7702522277832031s
Interlinking | sameAs chians check for Shanghai Library Open Data Platform took 0.7625100612640381s
Interlinking | skos check for Shanghai Library Open Data Platform took 1.1162092685699463s
Interlinking | skos check for Shanghai Library Open Data Platform took 0.6688928604125977s
Timeliness | dataset update frequency check for Shanghai Library Open Data Platform took 0.8220117092132568s
Currency | Creation date check for Shanghai Library Open Data Platform took 1.5545775890350342s
Currency | Modification date check for Shanghai Library Open Data Platform took 1.5582168102264404s
Rep.Conc. | URIs length for Shanghai Library Open Data Platform took 11.64897084236145s
Interoperability | New vocabularies check for Shanghai Library Open Data Platform took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Shanghai Library Open Data Platform took 0.7668435573577881s
Accuracy | Check Functional Property for Shanghai Library Open Data Platform took 0.753089189529419s
Accuracy | Check Inverse Functional Property for Shanghai Library Open Data Platform took 0.7269551753997803s
Accuracy | Check Empty annotation labels for Shanghai Library Open Data Platform took 3.7308108806610107s
Accuracy | Check White space in annotation for Shanghai Library Open Data Platform took 0.1511683464050293s
Accuracy | Check Datatype consistency for Shanghai Library Open Data Platform took 0.14954257011413574s
Consistency | Disjoint class check for Shanghai Library Open Data Platform took 0.9049994945526123s
Consistency | Check Misplaced properties for Shanghai Library Open Data Platform took 6.281858444213867s
Consistency | Misplaced classes for Shanghai Library Open Data Platform took 1.372074842453003s
Consistency | Check Ontology hijacking for Shanghai Library Open Data Platform took 5.4558069705963135s
Consistency | Check Invalid usage of undefined classes for Shanghai Library Open Data Platform took 1.8217880725860596s
Consistency | Check Invalid usage of undefined properties for Shanghai Library Open Data Platform took 7.44926118850708s
Conciseness | Check Extensional conciseness for Shanghai Library Open Data Platform took 0.16275787353515625s
Conciseness | Check Intensional conciseness for Shanghai Library Open Data Platform took 1.2511138916015625s
Security | Sign check for Shanghai Library Open Data Platform took 1.0410959720611572s
Availability | Check URIs Dereferenciability for Shanghai Library Open Data Platform took 10.550982236862183s
Completeness | Calculation of interlinking completeness for Shanghai Library Open Data Platform took 0.36572766304016113s
Reputation | Calculation of the PageRank for Shanghai Library Open Data Platform took 0.021477460861206055s
Interlinking | Calculation of Degree of Connection for Shanghai Library Open Data Platform took 2.5272369384765625e-05s
Interlinking | Calculation of Centrality for Shanghai Library Open Data Platform took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Shanghai Library Open Data Platform took 2.7179718017578125e-05s
Interoperability | Check the re-using of existing vocabs for Shanghai Library Open Data Platform took 2.1457672119140625e-06s
Believability | Calculation of trust value for Shanghai Library Open Data Platform took 1.0251998901367188e-05s
INFO | --- Analysis for Shanghai-Library-Open-Data-Platform took 343.86885356903076s
Availability | SPARQL endpoint availability check for National Library Netherlands took 1.3535330295562744s
Availability | VoID file availability check for National Library Netherlands took 0.0005497932434082031s
Extra | Recovery of all triples for National Library Netherlands took 0.6247453689575195s
Performance | Total latancy measurement for National Library Netherlands took 0.7856864929199219s
Amount of data | Number of triples check for National Library Netherlands took 0.14014887809753418s
Interoperability | New terms check for National Library Netherlands took 1.6945524215698242s
Versatility | Languages check for National Library Netherlands took 58.12791347503662s
Interpretability | Number of blank nodes check for National Library Netherlands took 0.17367982864379883s
Interpretability | RDF structures check for National Library Netherlands took 0.15538239479064941s
Versatility | Serialization formats check for National Library Netherlands took 0.16404342651367188s
Availability | RDF dump link check for National Library Netherlands took 0.155015230178833s
License | MR license check for National Library Netherlands took 0.16370940208435059s
License | HR license check for National Library Netherlands took 0.2048335075378418s
Amount of data | Number of property check for National Library Netherlands took 0.15180206298828125s
Understandability | Number of label check for National Library Netherlands took 0.15862488746643066s
Understandability | URI regex check for National Library Netherlands took 0.30002903938293457s
Understandability | Vocabs check for National Library Netherlands took 0.17053818702697754s
Verifiability | Authors check for National Library Netherlands took 0.1708519458770752s
Verifiability | Publishers check for National Library Netherlands took 0.15329551696777344s
Performance | Throughput check for National Library Netherlands took 10.945159673690796s
Amount of data | Check the number of entities for National Library Netherlands took 8.130073547363281e-05s
Verifiability | Contribs. check for National Library Netherlands took 0.14403152465820312s
Interlinking | sameAs chians check for National Library Netherlands took 0.1455979347229004s
Interlinking | skos check for National Library Netherlands took 0.157334566116333s
Interlinking | skos check for National Library Netherlands took 0.13268494606018066s
Timeliness | dataset update frequency check for National Library Netherlands took 0.15946555137634277s
Currency | Creation date check for National Library Netherlands took 0.31534457206726074s
Currency | Modification date check for National Library Netherlands took 0.3470635414123535s
Rep.Conc. | URIs length for National Library Netherlands took 0.7334907054901123s
Interoperability | New vocabularies check for National Library Netherlands took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for National Library Netherlands took 0.16578960418701172s
Accuracy | Check Functional Property for National Library Netherlands took 0.16316938400268555s
Accuracy | Check Inverse Functional Property for National Library Netherlands took 0.1727743148803711s
Accuracy | Check Empty annotation labels for National Library Netherlands took 0.44863438606262207s
Accuracy | Check White space in annotation for National Library Netherlands took 0.02738809585571289s
Accuracy | Check Datatype consistency for National Library Netherlands took 0.029455900192260742s
Consistency | Disjoint class check for National Library Netherlands took 0.15540194511413574s
Consistency | Check Misplaced properties for National Library Netherlands took 0.3402283191680908s
Consistency | Check Ontology hijacking for National Library Netherlands took 2.0836308002471924s
Consistency | Check Invalid usage of undefined classes for National Library Netherlands took 1.6446385383605957s
Consistency | Check Invalid usage of undefined properties for National Library Netherlands took 1.8297169208526611s
Conciseness | Check Extensional conciseness for National Library Netherlands took 0.031388044357299805s
Security | Sign check for National Library Netherlands took 0.1598207950592041s
Availability | Check URIs Dereferenciability for National Library Netherlands took 1759.990163564682s
Completeness | Calculation of interlinking completeness for National Library Netherlands took 0.7595174312591553s
Reputation | Calculation of the PageRank for National Library Netherlands took 0.023073196411132812s
Interlinking | Calculation of Degree of Connection for National Library Netherlands took 3.266334533691406e-05s
Interlinking | Calculation of Centrality for National Library Netherlands took 0.0008199214935302734s
Interlinking | Calculation of Clustering coefficient for National Library Netherlands took 2.4557113647460938e-05s
Interoperability | Check the re-using of existing vocabs for National Library Netherlands took 2.6226043701171875e-06s
Believability | Calculation of trust value for National Library Netherlands took 1.5735626220703125e-05s
INFO | --- Analysis for National-Library-Netherlands took 1867.5602004528046s
Availability | SPARQL endpoint availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.5058631896972656s
Availability | VoID file availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0007231235504150391s
Completeness | Calculation of interlinking completeness for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.3143939971923828s
Reputation | Calculation of the PageRank for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.021684885025024414s
Interlinking | Calculation of Degree of Connection for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0007975101470947266s
Interlinking | Calculation of Clustering coefficient for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 2.193450927734375e-05s
Believability | Calculation of trust value for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.8358230590820312e-05s
INFO | --- Analysis for Antique-Renaissance took 6.387115001678467s
Availability | SPARQL endpoint availability check for ARTSDATA.CA took 4.377626419067383s
Availability | VoID file availability check for ARTSDATA.CA took 0.0007021427154541016s
Completeness | Calculation of interlinking completeness for ARTSDATA.CA took 0.2795381546020508s
Reputation | Calculation of the PageRank for ARTSDATA.CA took 0.021462678909301758s
Interlinking | Calculation of Degree of Connection for ARTSDATA.CA took 2.3603439331054688e-05s
Interlinking | Calculation of Centrality for ARTSDATA.CA took 0.0009505748748779297s
Interlinking | Calculation of Clustering coefficient for ARTSDATA.CA took 1.5735626220703125e-05s
Believability | Calculation of trust value for ARTSDATA.CA took 1.5020370483398438e-05s
INFO | --- Analysis for ARTSDATA-CA took 9.683332920074463s
Availability | SPARQL endpoint availability check for Architecture of Knowledge took 0.2561357021331787s
Availability | VoID file availability check for Architecture of Knowledge took 0.00058746337890625s
Completeness | Calculation of interlinking completeness for Architecture of Knowledge took 0.3014237880706787s
Reputation | Calculation of the PageRank for Architecture of Knowledge took 0.022496938705444336s
Interlinking | Calculation of Degree of Connection for Architecture of Knowledge took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Architecture of Knowledge took 0.0008840560913085938s
Interlinking | Calculation of Clustering coefficient for Architecture of Knowledge took 1.5497207641601562e-05s
Believability | Calculation of trust value for Architecture of Knowledge took 1.4543533325195312e-05s
INFO | --- Analysis for ArCo took 3.8371148109436035s
Availability | SPARQL endpoint availability check for ConfermentSampo took 0.3632774353027344s
Availability | VoID file availability check for ConfermentSampo took 0.0002911090850830078s
Extra | Recovery of all triples for ConfermentSampo took 18.092358350753784s
Performance | Total latancy measurement for ConfermentSampo took 0.8187389373779297s
Amount of data | Number of triples check for ConfermentSampo took 9.178596496582031s
Interoperability | New terms check for ConfermentSampo took 2.9164233207702637s
Versatility | Languages check for ConfermentSampo took 26.6646785736084s
Interpretability | Number of blank nodes check for ConfermentSampo took 8.509986639022827s
Security | Check HTTPS for ConfermentSampo took 0.44343113899230957s
Interpretability | RDF structures check for ConfermentSampo took 0.21963930130004883s
Versatility | Serialization formats check for ConfermentSampo took 0.23112201690673828s
Availability | RDF dump link check for ConfermentSampo took 3.0225727558135986s
License | MR license check for ConfermentSampo took 0.2052135467529297s
License | HR license check for ConfermentSampo took 0.23761749267578125s
Amount of data | Number of property check for ConfermentSampo took 0.19899749755859375s
Understandability | Number of label check for ConfermentSampo took 5.426006078720093s
Understandability | URI regex check for ConfermentSampo took 0.37671589851379395s
Understandability | Vocabs check for ConfermentSampo took 0.16785383224487305s
Verifiability | Authors check for ConfermentSampo took 0.21065449714660645s
Verifiability | Publishers check for ConfermentSampo took 0.2025442123413086s
Performance | Throughput check for ConfermentSampo took 11.124878406524658s
Amount of data | Check the number of entities for ConfermentSampo took 4.400308132171631s
Verifiability | Contribs. check for ConfermentSampo took 0.17739224433898926s
Interlinking | sameAs chians check for ConfermentSampo took 0.39830660820007324s
Interlinking | skos check for ConfermentSampo took 0.16548919677734375s
Interlinking | skos check for ConfermentSampo took 0.1575641632080078s
Timeliness | dataset update frequency check for ConfermentSampo took 0.1666727066040039s
Currency | Creation date check for ConfermentSampo took 0.3691856861114502s
Currency | Modification date check for ConfermentSampo took 0.360584020614624s
Rep.Conc. | URIs length for ConfermentSampo took 35.19516134262085s
Interoperability | New vocabularies check for ConfermentSampo took 1.2636184692382812e-05s
Consistency | Deprecated classes/propertiers check for ConfermentSampo took 0.20402169227600098s
Accuracy | Check Functional Property for ConfermentSampo took 0.2062244415283203s
Accuracy | Check Inverse Functional Property for ConfermentSampo took 0.16489887237548828s
Accuracy | Check Empty annotation labels for ConfermentSampo took 15.504272937774658s
Accuracy | Check White space in annotation for ConfermentSampo took 3.013558864593506s
Accuracy | Check Datatype consistency for ConfermentSampo took 5.302834987640381s
Consistency | Disjoint class check for ConfermentSampo took 0.17427873611450195s
Consistency | Check Misplaced properties for ConfermentSampo took 6.7444868087768555s
Consistency | Check Ontology hijacking for ConfermentSampo took 16.082244634628296s
Consistency | Check Invalid usage of undefined classes for ConfermentSampo took 1.7053587436676025s
Consistency | Check Invalid usage of undefined properties for ConfermentSampo took 1.8057856559753418s
Conciseness | Check Extensional conciseness for ConfermentSampo took 2.8919291496276855s
Conciseness | Check Intensional conciseness for ConfermentSampo took 0.19554710388183594s
Security | Sign check for ConfermentSampo took 0.1568307876586914s
Availability | Check URIs Dereferenciability for ConfermentSampo took 1475.0736651420593s
Completeness | Calculation of interlinking completeness for ConfermentSampo took 0.3996772766113281s
Reputation | Calculation of the PageRank for ConfermentSampo took 0.026447296142578125s
Interlinking | Calculation of Degree of Connection for ConfermentSampo took 3.0994415283203125e-05s
Interlinking | Calculation of Centrality for ConfermentSampo took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for ConfermentSampo took 1.8835067749023438e-05s
Interoperability | Check the re-using of existing vocabs for ConfermentSampo took 6.4373016357421875e-06s
Believability | Calculation of trust value for ConfermentSampo took 1.52587890625e-05s
INFO | --- Analysis for ConfermentSampo took 1778.5584383010864s
Availability | SPARQL endpoint availability check for Museum Finland took 0.18738436698913574s
Availability | VoID file availability check for Museum Finland took 0.0005514621734619141s
Extra | Recovery of all triples for Museum Finland took 4.547948598861694s
Performance | Total latancy measurement for Museum Finland took 0.8236565589904785s
Amount of data | Number of triples check for Museum Finland took 0.3540184497833252s
Interoperability | New terms check for Museum Finland took 2.4598522186279297s
Versatility | Languages check for Museum Finland took 0.6863818168640137s
Interpretability | Number of blank nodes check for Museum Finland took 0.3339052200317383s
Security | Check HTTPS for Museum Finland took 0.24244070053100586s
Interpretability | RDF structures check for Museum Finland took 0.4924952983856201s
Versatility | Serialization formats check for Museum Finland took 0.22395801544189453s
Availability | RDF dump link check for Museum Finland took 0.187758207321167s
License | MR license check for Museum Finland took 0.2686593532562256s
License | HR license check for Museum Finland took 0.8832688331604004s
Amount of data | Number of property check for Museum Finland took 0.20153188705444336s
Understandability | Number of label check for Museum Finland took 0.34223175048828125s
Understandability | URI regex check for Museum Finland took 0.3209538459777832s
Understandability | Vocabs check for Museum Finland took 0.15975666046142578s
Verifiability | Authors check for Museum Finland took 0.17284655570983887s
Verifiability | Publishers check for Museum Finland took 0.15988516807556152s
Performance | Throughput check for Museum Finland took 11.10030746459961s
Amount of data | Check the number of entities for Museum Finland took 0.00010156631469726562s
Verifiability | Contribs. check for Museum Finland took 0.15889501571655273s
Interlinking | sameAs chians check for Museum Finland took 0.20740318298339844s
Interlinking | skos check for Museum Finland took 0.17503952980041504s
Interlinking | skos check for Museum Finland took 0.15613842010498047s
Timeliness | dataset update frequency check for Museum Finland took 0.15920186042785645s
Currency | Creation date check for Museum Finland took 0.3520991802215576s
Currency | Modification date check for Museum Finland took 0.38542890548706055s
Rep.Conc. | URIs length for Museum Finland took 3.6857283115386963s
Interoperability | New vocabularies check for Museum Finland took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Museum Finland took 0.18613505363464355s
Accuracy | Check Functional Property for Museum Finland took 0.1511220932006836s
Accuracy | Check Inverse Functional Property for Museum Finland took 0.16569066047668457s
Accuracy | Check Empty annotation labels for Museum Finland took 1.009228229522705s
Accuracy | Check White space in annotation for Museum Finland took 0.06261587142944336s
Accuracy | Check Datatype consistency for Museum Finland took 1.0263111591339111s
Consistency | Disjoint class check for Museum Finland took 0.1610116958618164s
Consistency | Check Misplaced properties for Museum Finland took 0.638678789138794s
Consistency | Check Ontology hijacking for Museum Finland took 2.8025245666503906s
Consistency | Check Invalid usage of undefined classes for Museum Finland took 1.8563940525054932s
Consistency | Check Invalid usage of undefined properties for Museum Finland took 2.040376663208008s
Conciseness | Check Extensional conciseness for Museum Finland took 0.6906986236572266s
Conciseness | Check Intensional conciseness for Museum Finland took 0.23695683479309082s
Security | Sign check for Museum Finland took 0.16768217086791992s
Availability | Check URIs Dereferenciability for Museum Finland took 2648.656085729599s
Completeness | Calculation of interlinking completeness for Museum Finland took 0.8525757789611816s
Reputation | Calculation of the PageRank for Museum Finland took 0.02178049087524414s
Interlinking | Calculation of Degree of Connection for Museum Finland took 2.6941299438476562e-05s
Interlinking | Calculation of Centrality for Museum Finland took 0.0007874965667724609s
Interlinking | Calculation of Clustering coefficient for Museum Finland took 1.430511474609375e-05s
Interoperability | Check the re-using of existing vocabs for Museum Finland took 2.384185791015625e-06s
Believability | Calculation of trust value for Museum Finland took 1.5497207641601562e-05s
INFO | --- Analysis for FI-Museum took 2707.0789890289307s
Availability | SPARQL endpoint availability check for Mapping Manuscript Migrations took 0.24861979484558105s
Availability | VoID file availability check for Mapping Manuscript Migrations took 0.0007708072662353516s
Extra | Recovery of all triples for Mapping Manuscript Migrations took 15.972901344299316s
Performance | Total latancy measurement for Mapping Manuscript Migrations took 0.991657018661499s
Amount of data | Number of triples check for Mapping Manuscript Migrations took 30.04008650779724s
Interoperability | New terms check for Mapping Manuscript Migrations took 4.955389499664307s
Versatility | Languages check for Mapping Manuscript Migrations took 74.87931680679321s
Interpretability | Number of blank nodes check for Mapping Manuscript Migrations took 29.162292957305908s
Security | Check HTTPS for Mapping Manuscript Migrations took 0.39432668685913086s
Interpretability | RDF structures check for Mapping Manuscript Migrations took 0.19112658500671387s
Versatility | Serialization formats check for Mapping Manuscript Migrations took 0.1975858211517334s
Availability | RDF dump link check for Mapping Manuscript Migrations took 0.18163371086120605s
License | MR license check for Mapping Manuscript Migrations took 0.22577309608459473s
License | HR license check for Mapping Manuscript Migrations took 1.8327713012695312s
Amount of data | Number of property check for Mapping Manuscript Migrations took 0.18825340270996094s
Understandability | Number of label check for Mapping Manuscript Migrations took 8.727590560913086s
Understandability | URI regex check for Mapping Manuscript Migrations took 0.3588728904724121s
Understandability | Vocabs check for Mapping Manuscript Migrations took 0.16083288192749023s
Verifiability | Authors check for Mapping Manuscript Migrations took 0.19832682609558105s
Verifiability | Publishers check for Mapping Manuscript Migrations took 0.20090341567993164s
Performance | Throughput check for Mapping Manuscript Migrations took 11.040409088134766s
Amount of data | Check the number of entities for Mapping Manuscript Migrations took 1.1559479236602783s
Verifiability | Contribs. check for Mapping Manuscript Migrations took 0.16120171546936035s
Interlinking | sameAs chians check for Mapping Manuscript Migrations took 0.5082809925079346s
Interlinking | skos check for Mapping Manuscript Migrations took 0.15374755859375s
Interlinking | skos check for Mapping Manuscript Migrations took 0.18117761611938477s
Timeliness | dataset update frequency check for Mapping Manuscript Migrations took 0.16020631790161133s
Currency | Creation date check for Mapping Manuscript Migrations took 0.35994839668273926s
Currency | Modification date check for Mapping Manuscript Migrations took 0.1882939338684082s
Rep.Conc. | URIs length for Mapping Manuscript Migrations took 52.50157189369202s
Interoperability | New vocabularies check for Mapping Manuscript Migrations took 1.1920928955078125e-05s
Consistency | Deprecated classes/propertiers check for Mapping Manuscript Migrations took 0.15340900421142578s
Accuracy | Check Functional Property for Mapping Manuscript Migrations took 0.1678316593170166s
Accuracy | Check Inverse Functional Property for Mapping Manuscript Migrations took 0.15957212448120117s
Accuracy | Check Empty annotation labels for Mapping Manuscript Migrations took 11.23645806312561s
Accuracy | Check White space in annotation for Mapping Manuscript Migrations took 2.4380857944488525s
Accuracy | Check Datatype consistency for Mapping Manuscript Migrations took 5.8869688510894775s
Consistency | Disjoint class check for Mapping Manuscript Migrations took 0.18166851997375488s
Consistency | Check Misplaced properties for Mapping Manuscript Migrations took 22.408427715301514s
Consistency | Check Ontology hijacking for Mapping Manuscript Migrations took 17.180840492248535s
Consistency | Check Invalid usage of undefined classes for Mapping Manuscript Migrations took 1.8695297241210938s
Consistency | Check Invalid usage of undefined properties for Mapping Manuscript Migrations took 1.813187599182129s
Conciseness | Check Extensional conciseness for Mapping Manuscript Migrations took 2.932814836502075s
Conciseness | Check Intensional conciseness for Mapping Manuscript Migrations took 0.22414350509643555s
Security | Sign check for Mapping Manuscript Migrations took 0.15317964553833008s
Availability | Check URIs Dereferenciability for Mapping Manuscript Migrations took 1749.2604575157166s
Completeness | Calculation of interlinking completeness for Mapping Manuscript Migrations took 0.5107414722442627s
Reputation | Calculation of the PageRank for Mapping Manuscript Migrations took 0.02125692367553711s
Interlinking | Calculation of Degree of Connection for Mapping Manuscript Migrations took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for Mapping Manuscript Migrations took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for Mapping Manuscript Migrations took 1.430511474609375e-05s
Interoperability | Check the re-using of existing vocabs for Mapping Manuscript Migrations took 2.384185791015625e-06s
Believability | Calculation of trust value for Mapping Manuscript Migrations took 1.5974044799804688e-05s
INFO | --- Analysis for MMM took 2159.812213420868s
Availability | SPARQL endpoint availability check for Semantic Kalevala took 0.19150781631469727s
Availability | VoID file availability check for Semantic Kalevala took 0.0005137920379638672s
Extra | Recovery of all triples for Semantic Kalevala took 5.775826454162598s
Performance | Total latancy measurement for Semantic Kalevala took 1.4695816040039062s
Amount of data | Number of triples check for Semantic Kalevala took 0.4485623836517334s
Interoperability | New terms check for Semantic Kalevala took 1.7639837265014648s
Versatility | Languages check for Semantic Kalevala took 0.9860420227050781s
Interpretability | Number of blank nodes check for Semantic Kalevala took 0.37244415283203125s
Security | Check HTTPS for Semantic Kalevala took 0.3991575241088867s
Interpretability | RDF structures check for Semantic Kalevala took 0.26469969749450684s
Versatility | Serialization formats check for Semantic Kalevala took 0.1906895637512207s
Availability | RDF dump link check for Semantic Kalevala took 0.16140127182006836s
License | MR license check for Semantic Kalevala took 0.1998131275177002s
License | HR license check for Semantic Kalevala took 1.1148896217346191s
Amount of data | Number of property check for Semantic Kalevala took 0.18784213066101074s
Understandability | Number of label check for Semantic Kalevala took 1.0111110210418701s
Understandability | URI regex check for Semantic Kalevala took 0.33489990234375s
Understandability | Vocabs check for Semantic Kalevala took 0.1875913143157959s
Verifiability | Authors check for Semantic Kalevala took 0.15290141105651855s
Verifiability | Publishers check for Semantic Kalevala took 0.16057157516479492s
Performance | Throughput check for Semantic Kalevala took 10.57039475440979s
Amount of data | Check the number of entities for Semantic Kalevala took 3.2901763916015625e-05s
Verifiability | Contribs. check for Semantic Kalevala took 0.15463590621948242s
Interlinking | sameAs chians check for Semantic Kalevala took 0.20891761779785156s
Interlinking | skos check for Semantic Kalevala took 0.268343448638916s
Interlinking | skos check for Semantic Kalevala took 0.15742945671081543s
Timeliness | dataset update frequency check for Semantic Kalevala took 0.18375301361083984s
Currency | Creation date check for Semantic Kalevala took 0.34903407096862793s
Currency | Modification date check for Semantic Kalevala took 0.5325841903686523s
Rep.Conc. | URIs length for Semantic Kalevala took 9.824124813079834s
Interoperability | New vocabularies check for Semantic Kalevala took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for Semantic Kalevala took 0.22086644172668457s
Accuracy | Check Functional Property for Semantic Kalevala took 0.18765616416931152s
Accuracy | Check Inverse Functional Property for Semantic Kalevala took 0.16668391227722168s
Accuracy | Check Empty annotation labels for Semantic Kalevala took 1.8783109188079834s
Accuracy | Check White space in annotation for Semantic Kalevala took 0.30080533027648926s
Accuracy | Check Datatype consistency for Semantic Kalevala took 1.4762670993804932s
Consistency | Disjoint class check for Semantic Kalevala took 0.16038966178894043s
Consistency | Check Misplaced properties for Semantic Kalevala took 0.7892346382141113s
Consistency | Check Ontology hijacking for Semantic Kalevala took 2.5445220470428467s
Consistency | Check Invalid usage of undefined classes for Semantic Kalevala took 1.6599819660186768s
Consistency | Check Invalid usage of undefined properties for Semantic Kalevala took 1.8568263053894043s
Conciseness | Check Extensional conciseness for Semantic Kalevala took 0.9294033050537109s
Conciseness | Check Intensional conciseness for Semantic Kalevala took 0.23012208938598633s
Security | Sign check for Semantic Kalevala took 0.16161227226257324s
Availability | Check URIs Dereferenciability for Semantic Kalevala took 2312.101146697998s
Completeness | Calculation of interlinking completeness for Semantic Kalevala took 0.879467248916626s
Reputation | Calculation of the PageRank for Semantic Kalevala took 0.6891536712646484s
Interlinking | Calculation of Degree of Connection for Semantic Kalevala took 2.5272369384765625e-05s
Interlinking | Calculation of Centrality for Semantic Kalevala took 0.0008969306945800781s
Interlinking | Calculation of Clustering coefficient for Semantic Kalevala took 1.5497207641601562e-05s
Interoperability | Check the re-using of existing vocabs for Semantic Kalevala took 2.6226043701171875e-06s
Believability | Calculation of trust value for Semantic Kalevala took 1.5735626220703125e-05s
INFO | --- Analysis for Semantic-Kalevala took 2381.381363391876s
Availability | SPARQL endpoint availability check for Smithsonian American Art Museum took 1.1483502388000488s
Availability | VoID file availability check for Smithsonian American Art Museum took 0.0008609294891357422s
Extra | Recovery of all triples for Smithsonian American Art Museum took 279.1604013442993s
Performance | Total latancy measurement for Smithsonian American Art Museum took 3.777543544769287s
Amount of data | Number of triples check for Smithsonian American Art Museum took 0.5798168182373047s
Interoperability | New terms check for Smithsonian American Art Museum took 3.365257740020752s
Versatility | Languages check for Smithsonian American Art Museum took 27.381831407546997s
Interpretability | Number of blank nodes check for Smithsonian American Art Museum took 0.5856306552886963s
Security | Check HTTPS for Smithsonian American Art Museum took 0.37830686569213867s
Interpretability | RDF structures check for Smithsonian American Art Museum took 0.8474488258361816s
Versatility | Serialization formats check for Smithsonian American Art Museum took 0.6488208770751953s
Availability | RDF dump link check for Smithsonian American Art Museum took 0.5789158344268799s
License | MR license check for Smithsonian American Art Museum took 0.6073305606842041s
License | HR license check for Smithsonian American Art Museum took 17.487975358963013s
Amount of data | Number of property check for Smithsonian American Art Museum took 0.5744767189025879s
Understandability | Number of label check for Smithsonian American Art Museum took 0.573383092880249s
Understandability | URI regex check for Smithsonian American Art Museum took 1.1255948543548584s
Understandability | Vocabs check for Smithsonian American Art Museum took 0.5983693599700928s
Verifiability | Authors check for Smithsonian American Art Museum took 0.587397575378418s
Verifiability | Publishers check for Smithsonian American Art Museum took 0.6477975845336914s
Performance | Throughput check for Smithsonian American Art Museum took 11.580332517623901s
Amount of data | Check the number of entities for Smithsonian American Art Museum took 7.05718994140625e-05s
Verifiability | Contribs. check for Smithsonian American Art Museum took 0.5882720947265625s
Interlinking | sameAs chians check for Smithsonian American Art Museum took 0.5846662521362305s
Interlinking | skos check for Smithsonian American Art Museum took 0.5666630268096924s
Interlinking | skos check for Smithsonian American Art Museum took 0.5743036270141602s
Timeliness | dataset update frequency check for Smithsonian American Art Museum took 0.6006515026092529s
Currency | Creation date check for Smithsonian American Art Museum took 1.2787106037139893s
Currency | Modification date check for Smithsonian American Art Museum took 1.2064015865325928s
Rep.Conc. | URIs length for Smithsonian American Art Museum took 105.29872488975525s
Interoperability | New vocabularies check for Smithsonian American Art Museum took 1.239776611328125e-05s
Consistency | Deprecated classes/propertiers check for Smithsonian American Art Museum took 0.5724353790283203s
Accuracy | Check Empty annotation labels for Smithsonian American Art Museum took 20.948620319366455s
Accuracy | Check White space in annotation for Smithsonian American Art Museum took 0.5011472702026367s
Accuracy | Check Datatype consistency for Smithsonian American Art Museum took 4.342117786407471s
Consistency | Disjoint class check for Smithsonian American Art Museum took 0.5759329795837402s
Consistency | Check Misplaced properties for Smithsonian American Art Museum took 3.9886040687561035s
Consistency | Check Ontology hijacking for Smithsonian American Art Museum took 100.40854740142822s
Consistency | Check Invalid usage of undefined classes for Smithsonian American Art Museum took 1.8670196533203125s
Consistency | Check Invalid usage of undefined properties for Smithsonian American Art Museum took 4.897646903991699s
Conciseness | Check Extensional conciseness for Smithsonian American Art Museum took 2.9538350105285645s
Conciseness | Check Intensional conciseness for Smithsonian American Art Museum took 0.6090512275695801s
Security | Sign check for Smithsonian American Art Museum took 0.5697507858276367s
Availability | Check URIs Dereferenciability for Smithsonian American Art Museum took 6.220773220062256s
Completeness | Calculation of interlinking completeness for Smithsonian American Art Museum took 0.48119044303894043s
Reputation | Calculation of the PageRank for Smithsonian American Art Museum took 0.021876811981201172s
Interlinking | Calculation of Degree of Connection for Smithsonian American Art Museum took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Smithsonian American Art Museum took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Smithsonian American Art Museum took 1.430511474609375e-05s
Interoperability | Check the re-using of existing vocabs for Smithsonian American Art Museum took 2.86102294921875e-06s
Believability | Calculation of trust value for Smithsonian American Art Museum took 1.430511474609375e-05s
INFO | --- Analysis for Smithsonian took 651.6265449523926s
Availability | SPARQL endpoint availability check for Zeri Photo Archive took 0.23950719833374023s
Availability | VoID file availability check for Zeri Photo Archive took 0.0006854534149169922s
Completeness | Calculation of interlinking completeness for Zeri Photo Archive took 0.31918811798095703s
Reputation | Calculation of the PageRank for Zeri Photo Archive took 0.02083110809326172s
Interlinking | Calculation of Degree of Connection for Zeri Photo Archive took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Zeri Photo Archive took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Zeri Photo Archive took 1.4543533325195312e-05s
Believability | Calculation of trust value for Zeri Photo Archive took 1.5735626220703125e-05s
INFO | --- Analysis for Zeri-Photo-Archive took 6.865567922592163s
Availability | SPARQL endpoint availability check for Archives Hub took 20.5824933052063s
Availability | VoID file availability check for Archives Hub took 0.0006074905395507812s
Completeness | Calculation of interlinking completeness for Archives Hub took 0.2820863723754883s
Reputation | Calculation of the PageRank for Archives Hub took 0.0208740234375s
Interlinking | Calculation of Degree of Connection for Archives Hub took 2.4318695068359375e-05s
Interlinking | Calculation of Centrality for Archives Hub took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Archives Hub took 1.4066696166992188e-05s
Believability | Calculation of trust value for Archives Hub took 1.52587890625e-05s
INFO | --- Analysis for Archives-Hub took 54.00974798202515s
Availability | SPARQL endpoint availability check for Yale centre of British Art took 1.582674264907837s
Availability | VoID file availability check for Yale centre of British Art took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for Yale centre of British Art took 0.2789952754974365s
Reputation | Calculation of the PageRank for Yale centre of British Art took 0.020743370056152344s
Interlinking | Calculation of Degree of Connection for Yale centre of British Art took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Yale centre of British Art took 0.0007920265197753906s
Interlinking | Calculation of Clustering coefficient for Yale centre of British Art took 1.33514404296875e-05s
Believability | Calculation of trust value for Yale centre of British Art took 1.4066696166992188e-05s
INFO | --- Analysis for Yale took 4.901998043060303s
Availability | SPARQL endpoint availability check for Alexandria Digital Library Gazetteer took 263.5869576931s
Availability | VoID file availability check for Alexandria Digital Library Gazetteer took 0.0005400180816650391s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library Gazetteer took 0.32767391204833984s
Reputation | Calculation of the PageRank for Alexandria Digital Library Gazetteer took 0.02115607261657715s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library Gazetteer took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Alexandria Digital Library Gazetteer took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library Gazetteer took 2.002716064453125e-05s
Believability | Calculation of trust value for Alexandria Digital Library Gazetteer took 1.3828277587890625e-05s
INFO | --- Analysis for ADL took 538.6204879283905s
Availability | SPARQL endpoint availability check for MusicKG took 0.7989587783813477s
Availability | VoID file availability check for MusicKG took 0.0008790493011474609s
Completeness | Calculation of interlinking completeness for MusicKG took 0.29247450828552246s
Reputation | Calculation of the PageRank for MusicKG took 0.021301746368408203s
Interlinking | Calculation of Degree of Connection for MusicKG took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for MusicKG took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for MusicKG took 1.2636184692382812e-05s
Believability | Calculation of trust value for MusicKG took 1.52587890625e-05s
INFO | --- Analysis for MusicKG took 4.606601238250732s
Availability | SPARQL endpoint availability check for CIDOC-CRM took 0.7805659770965576s
Availability | VoID file availability check for CIDOC-CRM took 0.0005941390991210938s
Completeness | Calculation of interlinking completeness for CIDOC-CRM took 0.32062435150146484s
Reputation | Calculation of the PageRank for CIDOC-CRM took 0.02094244956970215s
Interlinking | Calculation of Degree of Connection for CIDOC-CRM took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for CIDOC-CRM took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for CIDOC-CRM took 1.3589859008789062e-05s
Believability | Calculation of trust value for CIDOC-CRM took 7.343292236328125e-05s
INFO | --- Analysis for CIDOC-CRM took 4.201724290847778s
Availability | SPARQL endpoint availability check for Mondis took 262.46360039711s
Availability | VoID file availability check for Mondis took 0.0005743503570556641s
Completeness | Calculation of interlinking completeness for Mondis took 0.2924983501434326s
Reputation | Calculation of the PageRank for Mondis took 0.02155780792236328s
Interlinking | Calculation of Degree of Connection for Mondis took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Mondis took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Mondis took 1.6689300537109375e-05s
Believability | Calculation of trust value for Mondis took 1.430511474609375e-05s
INFO | --- Analysis for Mondis took 265.85564851760864s
Availability | SPARQL endpoint availability check for DigitalNZ took 3.381063938140869s
Availability | VoID file availability check for DigitalNZ took 0.0007116794586181641s
Completeness | Calculation of interlinking completeness for DigitalNZ took 0.29376721382141113s
Reputation | Calculation of the PageRank for DigitalNZ took 0.021605491638183594s
Interlinking | Calculation of Degree of Connection for DigitalNZ took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for DigitalNZ took 0.0008873939514160156s
Interlinking | Calculation of Clustering coefficient for DigitalNZ took 1.3589859008789062e-05s
Believability | Calculation of trust value for DigitalNZ took 1.4066696166992188e-05s
INFO | --- Analysis for DigitalNZ took 7.666112422943115s
Availability | SPARQL endpoint availability check for Fondazione Zeri took 0.15866446495056152s
Availability | VoID file availability check for Fondazione Zeri took 0.0013515949249267578s
Completeness | Calculation of interlinking completeness for Fondazione Zeri took 0.30551695823669434s
Reputation | Calculation of the PageRank for Fondazione Zeri took 0.020778656005859375s
Interlinking | Calculation of Degree of Connection for Fondazione Zeri took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Fondazione Zeri took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Fondazione Zeri took 1.3828277587890625e-05s
Believability | Calculation of trust value for Fondazione Zeri took 1.5020370483398438e-05s
INFO | --- Analysis for Fondazione-Zeri took 3.5625386238098145s
Availability | SPARQL endpoint availability check for Digital Public Library of America took 0.15698456764221191s
Availability | VoID file availability check for Digital Public Library of America took 0.0007295608520507812s
Completeness | Calculation of interlinking completeness for Digital Public Library of America took 0.3193659782409668s
Reputation | Calculation of the PageRank for Digital Public Library of America took 0.022654056549072266s
Interlinking | Calculation of Degree of Connection for Digital Public Library of America took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Digital Public Library of America took 0.0008084774017333984s
Interlinking | Calculation of Clustering coefficient for Digital Public Library of America took 1.52587890625e-05s
Believability | Calculation of trust value for Digital Public Library of America took 1.5497207641601562e-05s
INFO | --- Analysis for Library-of-America took 4.235167980194092s
Availability | SPARQL endpoint availability check for Auckland Museum took 2.033250331878662s
Availability | VoID file availability check for Auckland Museum took 0.0007219314575195312s
Completeness | Calculation of interlinking completeness for Auckland Museum took 0.29226160049438477s
Reputation | Calculation of the PageRank for Auckland Museum took 0.021449565887451172s
Interlinking | Calculation of Degree of Connection for Auckland Museum took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Auckland Museum took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Auckland Museum took 1.4066696166992188e-05s
Believability | Calculation of trust value for Auckland Museum took 1.52587890625e-05s
INFO | --- Analysis for Auckland-Museum took 6.816499710083008s
Availability | SPARQL endpoint availability check for National Library of Spain took 4.003169536590576s
Availability | VoID file availability check for National Library of Spain took 0.00057220458984375s
Completeness | Calculation of interlinking completeness for National Library of Spain took 0.2881124019622803s
Reputation | Calculation of the PageRank for National Library of Spain took 0.022463321685791016s
Interlinking | Calculation of Degree of Connection for National Library of Spain took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for National Library of Spain took 0.0007863044738769531s
Interlinking | Calculation of Clustering coefficient for National Library of Spain took 1.3828277587890625e-05s
Believability | Calculation of trust value for National Library of Spain took 1.0728836059570312e-05s
INFO | --- Analysis for BNE took 7.301281929016113s
Availability | SPARQL endpoint availability check for National Library of Korea took 1.2787389755249023s
Availability | VoID file availability check for National Library of Korea took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for National Library of Korea took 0.3053581714630127s
Reputation | Calculation of the PageRank for National Library of Korea took 0.02084040641784668s
Interlinking | Calculation of Degree of Connection for National Library of Korea took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for National Library of Korea took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for National Library of Korea took 1.3113021850585938e-05s
Believability | Calculation of trust value for National Library of Korea took 1.6450881958007812e-05s
INFO | --- Analysis for Korea-Library took 4.447505950927734s
Availability | SPARQL endpoint availability check for The State Russian Museum took 1.7816641330718994s
Availability | VoID file availability check for The State Russian Museum took 0.00043463706970214844s
Completeness | Calculation of interlinking completeness for The State Russian Museum took 0.3001697063446045s
Reputation | Calculation of the PageRank for The State Russian Museum took 0.020931720733642578s
Interlinking | Calculation of Degree of Connection for The State Russian Museum took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for The State Russian Museum took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for The State Russian Museum took 1.33514404296875e-05s
Believability | Calculation of trust value for The State Russian Museum took 1.4066696166992188e-05s
INFO | --- Analysis for Russian-Museum took 5.277555704116821s
Availability | SPARQL endpoint availability check for National Library of Scotland took 1.2457919120788574s
Availability | VoID file availability check for National Library of Scotland took 0.0007078647613525391s
Completeness | Calculation of interlinking completeness for National Library of Scotland took 0.31464648246765137s
Reputation | Calculation of the PageRank for National Library of Scotland took 0.021273136138916016s
Interlinking | Calculation of Degree of Connection for National Library of Scotland took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for National Library of Scotland took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for National Library of Scotland took 1.621246337890625e-05s
Believability | Calculation of trust value for National Library of Scotland took 1.1444091796875e-05s
INFO | --- Analysis for National-Library-of-Scotland took 6.799089670181274s
Availability | SPARQL endpoint availability check for Epigraphic Database Heidelberg took 207.48551201820374s
Availability | VoID file availability check for Epigraphic Database Heidelberg took 0.0007932186126708984s
Completeness | Calculation of interlinking completeness for Epigraphic Database Heidelberg took 0.5047667026519775s
Reputation | Calculation of the PageRank for Epigraphic Database Heidelberg took 0.021199464797973633s
Interlinking | Calculation of Degree of Connection for Epigraphic Database Heidelberg took 2.9325485229492188e-05s
Interlinking | Calculation of Centrality for Epigraphic Database Heidelberg took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for Epigraphic Database Heidelberg took 2.0265579223632812e-05s
Believability | Calculation of trust value for Epigraphic Database Heidelberg took 1.430511474609375e-05s
INFO | --- Analysis for Epigraphic-Database-Heidelberg took 258.21862506866455s
Availability | SPARQL endpoint availability check for OntoComedySources took 0.2864820957183838s
Availability | VoID file availability check for OntoComedySources took 0.0006685256958007812s
Completeness | Calculation of interlinking completeness for OntoComedySources took 0.3036055564880371s
Reputation | Calculation of the PageRank for OntoComedySources took 0.02074456214904785s
Interlinking | Calculation of Degree of Connection for OntoComedySources took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for OntoComedySources took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for OntoComedySources took 1.430511474609375e-05s
Believability | Calculation of trust value for OntoComedySources took 1.5020370483398438e-05s
INFO | --- Analysis for OntoComedySources took 4.34340500831604s
Availability | SPARQL endpoint availability check for OntoCeramic 2.0 took 0.19293546676635742s
Availability | VoID file availability check for OntoCeramic 2.0 took 0.0007500648498535156s
Completeness | Calculation of interlinking completeness for OntoCeramic 2.0 took 0.2901740074157715s
Reputation | Calculation of the PageRank for OntoCeramic 2.0 took 0.020771503448486328s
Interlinking | Calculation of Degree of Connection for OntoCeramic 2.0 took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for OntoCeramic 2.0 took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for OntoCeramic 2.0 took 1.52587890625e-05s
Believability | Calculation of trust value for OntoCeramic 2.0 took 1.4066696166992188e-05s
INFO | --- Analysis for OntoCeramic-2.0 took 4.7078328132629395s
Availability | SPARQL endpoint availability check for SaintGall Ontology took 0.17928433418273926s
Availability | VoID file availability check for SaintGall Ontology took 0.0007550716400146484s
Completeness | Calculation of interlinking completeness for SaintGall Ontology took 0.30327701568603516s
Reputation | Calculation of the PageRank for SaintGall Ontology took 0.02168726921081543s
Interlinking | Calculation of Degree of Connection for SaintGall Ontology took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for SaintGall Ontology took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for SaintGall Ontology took 1.5974044799804688e-05s
Believability | Calculation of trust value for SaintGall Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for SaintGall-Ontology took 3.417133092880249s
Availability | SPARQL endpoint availability check for Linguistic Phenomena Ontology took 0.7158033847808838s
Availability | VoID file availability check for Linguistic Phenomena Ontology took 0.0009279251098632812s
Completeness | Calculation of interlinking completeness for Linguistic Phenomena Ontology took 0.2986133098602295s
Reputation | Calculation of the PageRank for Linguistic Phenomena Ontology took 0.02100086212158203s
Interlinking | Calculation of Degree of Connection for Linguistic Phenomena Ontology took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Linguistic Phenomena Ontology took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for Linguistic Phenomena Ontology took 1.52587890625e-05s
Believability | Calculation of trust value for Linguistic Phenomena Ontology took 1.4543533325195312e-05s
INFO | --- Analysis for Linguistic-Phenomena-Ontology took 4.237610816955566s
Availability | SPARQL endpoint availability check for ICON took 0.2674992084503174s
Availability | VoID file availability check for ICON took 0.0006382465362548828s
Completeness | Calculation of interlinking completeness for ICON took 0.3068549633026123s
Reputation | Calculation of the PageRank for ICON took 0.021007299423217773s
Interlinking | Calculation of Degree of Connection for ICON took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for ICON took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for ICON took 1.239776611328125e-05s
Believability | Calculation of trust value for ICON took 1.4781951904296875e-05s
INFO | --- Analysis for ICON took 4.765559911727905s
Availability | SPARQL endpoint availability check for Polifonia took 0.2687089443206787s
Availability | VoID file availability check for Polifonia took 0.0013606548309326172s
Completeness | Calculation of interlinking completeness for Polifonia took 0.28517937660217285s
Reputation | Calculation of the PageRank for Polifonia took 0.022710800170898438s
Interlinking | Calculation of Degree of Connection for Polifonia took 2.384185791015625e-05s
Interlinking | Calculation of Centrality for Polifonia took 0.0012619495391845703s
Interlinking | Calculation of Clustering coefficient for Polifonia took 1.5020370483398438e-05s
Believability | Calculation of trust value for Polifonia took 1.5020370483398438e-05s
INFO | --- Analysis for Polifonia took 4.584789276123047s
Availability | SPARQL endpoint availability check for Atlas of Paths Ontology - Italian Application Profile took 0.2561354637145996s
Availability | VoID file availability check for Atlas of Paths Ontology - Italian Application Profile took 0.0005908012390136719s
Completeness | Calculation of interlinking completeness for Atlas of Paths Ontology - Italian Application Profile took 0.29113006591796875s
Reputation | Calculation of the PageRank for Atlas of Paths Ontology - Italian Application Profile took 0.0211484432220459s
Interlinking | Calculation of Degree of Connection for Atlas of Paths Ontology - Italian Application Profile took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Atlas of Paths Ontology - Italian Application Profile took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Atlas of Paths Ontology - Italian Application Profile took 1.4781951904296875e-05s
Believability | Calculation of trust value for Atlas of Paths Ontology - Italian Application Profile took 1.5497207641601562e-05s
INFO | --- Analysis for Atlas-of-Paths took 4.2456910610198975s
Availability | SPARQL endpoint availability check for Music Note Ontology took 0.18822336196899414s
Availability | VoID file availability check for Music Note Ontology took 0.0006453990936279297s
Completeness | Calculation of interlinking completeness for Music Note Ontology took 0.28907155990600586s
Reputation | Calculation of the PageRank for Music Note Ontology took 0.021411418914794922s
Interlinking | Calculation of Degree of Connection for Music Note Ontology took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Music Note Ontology took 0.00081634521484375s
Interlinking | Calculation of Clustering coefficient for Music Note Ontology took 1.3589859008789062e-05s
Believability | Calculation of trust value for Music Note Ontology took 1.239776611328125e-05s
INFO | --- Analysis for Music-Note-Ontology took 8.41638994216919s
Availability | SPARQL endpoint availability check for HaMSE took 0.18292522430419922s
Availability | VoID file availability check for HaMSE took 0.0005824565887451172s
Completeness | Calculation of interlinking completeness for HaMSE took 0.2911105155944824s
Reputation | Calculation of the PageRank for HaMSE took 0.021030426025390625s
Interlinking | Calculation of Degree of Connection for HaMSE took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for HaMSE took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for HaMSE took 1.2874603271484375e-05s
Believability | Calculation of trust value for HaMSE took 1.4066696166992188e-05s
INFO | --- Analysis for HaMSE took 5.088560581207275s
Availability | SPARQL endpoint availability check for FOOD: FOod in Open Data took 0.1515202522277832s
Availability | VoID file availability check for FOOD: FOod in Open Data took 0.00054931640625s
Completeness | Calculation of interlinking completeness for FOOD: FOod in Open Data took 0.29895567893981934s
Reputation | Calculation of the PageRank for FOOD: FOod in Open Data took 0.020984172821044922s
Interlinking | Calculation of Degree of Connection for FOOD: FOod in Open Data took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for FOOD: FOod in Open Data took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for FOOD: FOod in Open Data took 1.3589859008789062e-05s
Believability | Calculation of trust value for FOOD: FOod in Open Data took 9.298324584960938e-06s
INFO | --- Analysis for FOod took 5.077272891998291s
Availability | SPARQL endpoint availability check for The ATLAS of Italian Digital Cultural Heritage took 0.6345953941345215s
Availability | VoID file availability check for The ATLAS of Italian Digital Cultural Heritage took 0.0006618499755859375s
Completeness | Calculation of interlinking completeness for The ATLAS of Italian Digital Cultural Heritage took 0.2841329574584961s
Reputation | Calculation of the PageRank for The ATLAS of Italian Digital Cultural Heritage took 0.020510196685791016s
Interlinking | Calculation of Degree of Connection for The ATLAS of Italian Digital Cultural Heritage took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for The ATLAS of Italian Digital Cultural Heritage took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for The ATLAS of Italian Digital Cultural Heritage took 1.3828277587890625e-05s
Believability | Calculation of trust value for The ATLAS of Italian Digital Cultural Heritage took 1.0728836059570312e-05s
INFO | --- Analysis for ATLAS-Italian-Digital-CH took 5.448079347610474s
Availability | SPARQL endpoint availability check for ARIADNEplus Knowledge Base took 1.6227829456329346s
Availability | VoID file availability check for ARIADNEplus Knowledge Base took 0.0006878376007080078s
Completeness | Calculation of interlinking completeness for ARIADNEplus Knowledge Base took 0.2909700870513916s
Reputation | Calculation of the PageRank for ARIADNEplus Knowledge Base took 0.02102947235107422s
Interlinking | Calculation of Degree of Connection for ARIADNEplus Knowledge Base took 1.52587890625e-05s
Interlinking | Calculation of Centrality for ARIADNEplus Knowledge Base took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for ARIADNEplus Knowledge Base took 1.2636184692382812e-05s
Believability | Calculation of trust value for ARIADNEplus Knowledge Base took 9.5367431640625e-06s
INFO | --- Analysis for ARIADNE took 6.72612452507019s
Availability | SPARQL endpoint availability check for Odeuropa Ontology took 0.3506767749786377s
Availability | VoID file availability check for Odeuropa Ontology took 0.00028204917907714844s
Completeness | Calculation of interlinking completeness for Odeuropa Ontology took 0.2835361957550049s
Reputation | Calculation of the PageRank for Odeuropa Ontology took 0.020931005477905273s
Interlinking | Calculation of Degree of Connection for Odeuropa Ontology took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Odeuropa Ontology took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Odeuropa Ontology took 1.2874603271484375e-05s
Believability | Calculation of trust value for Odeuropa Ontology took 1.2874603271484375e-05s
INFO | --- Analysis for Odeuropa took 3.650054931640625s

--- Total time for analysis:509578.23566937447s ---
--- Total time for analysis:141.54950990815956 hours ---